What's interesting to me about the rebase thing is it's usually a few engineers pushing everybody else to do it.
-
-
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.
-
I think a big part of the trouble is people *think* of git history as a linear log instead of a graph. We are guided by our mental models.
-
It sounds like you think of commit history more as a data store from which insights could be extracted, rather than a constructed narrative?
- 3 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.