Yeah that's pretty much what everybody says when you make an argument to stop rebasing.https://twitter.com/triketora/status/909016603450363905 …
-
-
IMO depends on what you want out of your commit history. Easily-followed history of features? Twists/turns/false starts? Both can be useful.
-
I think the latter is good (and what I want) but I don't need to see commits with debuggers I pushed at EOD before running home.
-
Yeah. A commit history is documentation, worth putting some thoughtful design into like any other documentation. :)
-
I've always seen it differently. Commit history is history. It's what actually happened. We lie to ourselves when we change it.
-
me, too. but i will think about expressing that in terms of the "why" i did it. that idea has merit.
-
A merge commit message is an excellent place for expressing a "why" at a point in time when branches merge.
-
Great idea! I've been relying on default merge message. Missed opportunity to explain why the merge was made instead.
-
People gloss over merge commits like they are useless. I understand why. But it's a missed opportunity.
- 5 more replies
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.
