3 ms·
In my experience commit messages shouldn't describe what was changed, they should describe why the change was made.
by naavis 6y ago
In my experience commit messages shouldn't describe what was changed, they should describe why the change was made.
- nikivi 6y agothat is why you shouldn't waste time writing commit messages for where this not much to `why` something has changed. (i.e. docs, refactors..)
- bithaze 6y agoIt's really not that much time though. "templates" and ".github" are examples of such vague commit messages that they _require_ looking at the commit to understand what changed. With a short, descriptive commit message, you can just glance through the commit log.