5 ms·
The commit message should contain all the unusual context needed to understand the change. In practice however, most people write terrible commit messages.
by tcoff91 4y ago
The commit message should contain all the unusual context needed to understand the change. In practice however, most people write terrible commit messages.
- ParetoOptimal 4y agoMany never even use multi-line commit messages.
- bornfreddy 4y agoIt's not just that. Commit messages have a property that they get overwritten. When I refactor some code for performance reasons, I don't want to remove documentation - which is exactly what happens if I make a commit. True, older commit messages are available in the history, but... not conveniently available.
- conradfr 4y agoAnd ideally the id of the ticket associated to the code change.