3 ms·
I have a different opinion about favourite Git commit messages. I think commits should be small steps that display the thought process of the author. Every ind
by mo_42 3y ago
I have a different opinion about favourite Git commit messages.
I think commits should be small steps that display the thought process of the author. Every individual commit should be self-explanatory. So the commit message should not describe (again) what the changes are but why it’s necessary. Sometimes the change is not self-explanatory and then I'd put a longer description below.
Somehow I came up with this on my own, so I'd be interested if it really makes sense or if others have a similar style.
- kelnos 3y agoI just don't think this is feasible, and I think you're maybe over-estimating the diff-reading skills of others. I agree that changes should be as small and self-contained as possible, but I don't think it's reasonable to expect a later diff-reader to be able to understand what the change is just by looking at it. Certainly a commit message should include the why, but it should include -- start with, really -- the what as well.