6 ms·
Totally agree with you. We already know what changed: it's the diff! We need to know why you're making the what. The message should address why the diff is ne
by hermitdev 3y ago
Totally agree with you.
We already know what changed: it's the diff! We need to know why you're making the what.
The message should address why the diff is necessary. Was it a bug fix? Ok, what's the bug you're fixing? What's the evidence that you think they diff addresses it? Is it a new feature? What's the requirement? I can already tell what you did by the diff, but I can't tell from the diff alone if it actually matches the requirement!
- joshuamorton 3y agoThis is true of the overall commit message, but we're talking about the first line. If I'm browsing git-log short or whatever, I don't have the diff, I have an ordered list of commit hashes and one line summaries, and I'm trying to decide which diffs I actually want to look more closely at.