-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repository error? #1
Comments
Yes, my fault. I've completely messed up (mainly because I'm still a git novice after all these years!). |
That's really a shame, losing so much history on a project that's as old as G'MIC will have a serious impact. For future reference by the way, deleting and re-creating the repo is never the right approach to a situation like this, it's always recoverable. I've been there, trust me, but reaching out to the community to ask for a hand in sorting things out and correcting any mistake is a way better approach, and shows development and progress, rather than flying in the face of the fundamental principles of FOSS development. If you want to try and get this sorted, by the way, on Github, up to 90 days after a deletion, you can recover that repository. I'd highly recommend that you do so by following this link. I can't state just how much the loss of a project's history severely impacts developers want to contribute to it, and users trust of the project. Edit: Fixed some spelling & grammar |
I found a recent copy of the GMIC repository on my computer. It's possible to rebase the new repository onto the old one, which preserves the git history while avoiding disruption to the current repo. As an example I did that here: https://github.com/nocylah/gmic. If you're interested, I'd be happy to help you with doing the same process to the GreycLab/gmic repo. |
What happened to the commit history, tags, etc?
Was there some sort of GitHub issue that required this? The loss of a project's history, commit messages, issues, MRs, etc.. is a huge blow to the project, so I'm sorry to see this loss of yours.
The text was updated successfully, but these errors were encountered: