A merge commit message is an excellent place for expressing a "why" at a point in time when branches merge.
-
-
I don't think I said that either. This isn't about what git inherently is or even it's affordances. It's about our intent when using it.
-
I wasn't implying anything about what you were saying -- the convo was just becoming really hard to follow -- because too meta ;p
-
Concrete question: do you think it's appropriate to use rebase to clean up things like console.log before merging?
-
I wouldn't say "appropriate" or "not appropriate". I would say "I never feel the need to do that."
-
For the record, my personal working style is to be very intentional with commits. So I don't see nearly as much post-facto "clean up."
-
I would go further and say my bias in this convo is I don't like that people do messy commits in the first place.
-
A commit isn't just a cmd-s on the last thing you were typing. I think of it as an intentional unit of change to the system.
-
I'm super messy when I code, just like everyone else. But I do that first, and then think about how I want to commit it as a separate loop.
- 11 more replies
New conversation -
-
-
We surely aren't arguing about whether it's appropriate to edit things before committing to them, are we?
-
auto-save + auto-git-commit after every pause in editing. It's the only way to have an accurate history of the project. Don't @ me.
#troll
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.