It’s a question of workflow. Git doesn’t guide you (it’s really workflow agnostic) and I find it easier to taillor CLI to fit my exact need, or use whatever was recently added (like worktrees a few years ago). I have yet to find a GUI/TUI that I’m not frustrated with at one point but everyone has its own preferences.
If you use the git command line (and I do) you should spam git log --graph (usualy with --oneline).
And for your filesystem example I sure do hope you use tree!
It’s so anoying that at $WORK we have multiple git repos with symbolic link that points above their respective .git to each other and need to be in sync. So of course git workree and git bisect don’t work that well…
For those who don’t know (I assume you do), you can git bisect run some_command and git will automatically run git bisect until it finds the falty commit. It’s amazing.
I reread that article every years for a few years. Each time my understanding of git improved significantly.
I reread that article every years for a few years. Each time my understanding of git improved significantly.
It was when I read the git parable.
I have a non-breaking space on my layout since 10 years, and a friend recently added a non-breaking hyphen to his. Appart from search that doesn’t do automatic conversion I didn’t noticed issues.
That’s a really good explanation. I would just add that I find easier to search for orphans with git log --graph --reflog than using `git reflog directly, especially if it’s one of the top entries in the reflog.
IIRC the orbit of Mercure doesn’t work with Newton Model, and astronomers were predicted the discovery of Vulcain a small planet between Mercure and the Sun. So a new model had to be invented since Vulcain couldn’t be found.
I use win+arrow key quite a lot too.
git worktreecould become your new friend then :)