2 ms·
In my case, a lot of the complexity of Git is in the edge cases. Like, I rarely if ever have to revert, but when I do, it's very stressful to remember everythin
by stronglikedan 4y ago
In my case, a lot of the complexity of Git is in the edge cases. Like, I rarely if ever have to revert, but when I do, it's very stressful to remember everything to get it right. This will certainly eliminate that occasional, but monumental, stress.
- jonfw 4y agoThe revert command is a good, easy solution- "git revert <commit-hash" run "git log" to grab the commit hash The really challenging parts of git IMO are around maintaining branches. Merge vs rebase, squash or no squash, when to back-merge, etc.
- zikduruqe 4y agoThat's what tig is for. https://jonas.github.io/tig/ https://jonas.github.io/tig/
- dahart 4y agoRevert is normally extremely safe, I’m curious why it’s ‘monumentally’ stressful? The best thing to learn about git is what the safety nets are, what commands do destructive edits, vs what commands do things you can undo. Once you know how to recover from all the non-destructive commands, you never have to stress about them again! The reflog is weird and confusing at first, but once you know it’s here and a little about how to use it, all of a sudden you realize it’s pretty hard to lose things, as long as you commit them.