2 ms·
Commits are indeed pointless...if you do merge/pull requests (or the equivalent on whatever collaboration platform you use). Interesting code that requires con
by nunez 4y ago
Commits are indeed pointless...if you do merge/pull requests (or the equivalent on whatever collaboration platform you use).
Interesting code that requires context should live in a discussion and be pointed out in the PR body.
Since the artifact of a PR is a squash-merge commit back to mainline and the PR allows for very rich discussion and automated checks and annotations, it makes no sense to add those details into messages that will get lost.
If you DON'T use PRs/MRs for code management (though you really should!!!), then commit messages are EVERYTHING.
- erik_seaberg 4y agoAt 3 AM, I need to scroll through a hundred commit messages to find the three that might have caused a problem. Paging through a hundred browser tabs of discussion is a lot more to read, assuming they still exist and weren’t discarded during a Jira migration or something. I assume commits are more durable and better reviewed than anything else.
- nunez 4y agoBut the scrolling and search for context would happen regardless, and non-technical users are more likely to contribute context into Jira or a GitHub PR than submit Git commits. better than searching through email!