this git rebase mania is pure dogma. "clean history", "ugly merge bubbles" and "extra commits" are aesthetic, not technical justifications.
@glyphobet how about “easier-to-understand commit history”? surely you see some value in communicating with your team better.
-
-
@levity Still dogma. I doubt there are programmers who can’t understand a DAG. If there are, I don’t want them on my team to begin with. -
@glyphobet I’m talking about commit history as documentation. Poorly-commented, stream-of-consciousness commits obscure intent. - 2 more replies
New conversation -
-
-
@levity better explanation of why you shouldn’t use git merge –rebase: https://blog.glyphobet.net/essay/2504 -
@glyphobet that makes a lot of sense, thanks for the writeup.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
