Yeah, I've honestly largely given up on visual representations of branch history on real world repositories. You can make a lot more work for yourself trying to

Yeah, I've honestly largely given up on visual representations of branch history on real world repositories. You can make a lot more work for yourself trying to keep them sane, but the reality is you're just shoving a workload better suited to a computer into your own brain where it's frustrating and slow. Better to learn how to do meaningful queries against the tree (is branch X in branch Y, what's the merge base of X, Y, Z, etc.) and let the computer understand it for you. And usually what I want to see when I do git log these days is either --first-only on master or master.. on a topic branch.