451
Commit
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Feb 2025
451 points (98.7% liked)
Programmer Humor
20033 readers
1429 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
That's not a mistake git can do that to people. Especially those who have never used git via command line.
Yeah, imagine you accidently commit over weeks of work, or hell, if it's the main branch, and you deleted the other origin branch prior to merging, it could be a lot more than a few weeks worth of work. The revert to a previous commit... shutters.
I don't know if you're joking, but in case you're not:
git reflogandgit reset --hard HEAD@{n}is your friend. You can undo almost anything. Deleted commits and branches aren't really deleted. Remotely deleted branches can be pushed again.Except for an (accidental)
git restore/git reset. Those are permanent and can't be undone.Even
git resetcan be undone by a lot of editors. At least IntelliJ has an excellent local history that works much like git. Sure it’s a pain if you touched several files but that’ll teach you to atomify your commits.Edit: Plus,
git resetitself does nothing of note really, but I’m sure you know. Needs the—hardflag to do any meaningful damage.