@gertkeno Did exactly the same cockup with git rm quite a few years ago, while trying to add version control to an old demo project. Nuked the whole repo forgetting I didn’t do the initial commit. Had to use disk recovery utilities to get the files back. Fortunately only a handful of them got corrupted and I had a couple of weeks old hard backup. So I combined the two to restore the project to its original state. It took several hours. Needless to say that there was a previously arranged meeting to present this - scheduled for tomorrow.
2 Likes
I definitely have had issues that required me to revert or reset. I don’t remember losing a whole repo with git, but that’s probably because I made those errors with CVS, Clear Case or Perforce already.
1 Like
I never had any problems with git, or at least oppinon problems.
Doing web dev, i was on a team of 2 people, yeah a lot of times both of us pushed a version without pulling and whatnot, it messed us up REAL bad, luckily there’s version control, but i would say that git is a lot easier if you are the only person working on a project.
Another person I had to help out a while back made too many changes on her project before pushing, and of course the project broke, when i showed her how to use git and reverted to the latest not-messed up version, progress gone, me, no idea she forgot to save.
As long as you save often, git is extremely helpful, treat it like an NES cart.
*Never touched reset, luckily hehehhhh