I've found it indispensable when tracking and integrating other peoples' branches. I wouldn't use it so much if I was working solo.
Re:Git is too hard
by sethammons on Tuesday November 17, 2020 @07:44AM
(#25123078)
I've never worked solo. My teams tend to be around 6-8. Across a dozen teams, myself and nobody on the team save a couple even looked at the graph. One who loved a clean history showed it off, people thought it was pretty, and went back to work as normal. `git commit -am 'slightly helpful message' && git push origin $branch` does about 90%+ of what I've needed. When we merge the branch, squash merge works fine. History graphs, I've never felt the need for them.
Each to their own. I use it in situations where i want to know what other people are basing their branch from. Which, for projects I've worked on, can have real consequences. For instance, it may prompt me to rebase upon their work sooner, or even give them a heads up that theirs some useful change I'm submitting to the trunk.
Re:Git is too hard
by sethammons on Tuesday November 17, 2020 @05:13PM
(#25130638)
ah, that is likely part of it. We always branch from master and merge back to master. Builds prevent failing code from merging. It is rare that we branch from a branch, and that 2nd branch would never be merged before the first.
During rapid mobile and frontend development, occasionally I'll be working on someone where there's co-depending feature branches, but for the most part the team usually follow something like git-flow. But I take your point that viewing the graph isn't essential, and those aliases might look scary on a one-page crash course. (I really think `git lol` and `git lola` should be first class citizens of a git installation though)
Re:Git is too hard
by secondcoming on Tuesday November 17, 2020 @08:37AM
(#25123550)
We're the exact same except for the squashed merge (which I have no real objection to doing)
I've honestly ever felt the need, or had the requirement, to look at the graph.