4 ms·
I write descriptive commit messages because the code I check in is likely to contain a bug. This bug tends to be discovered a couple of years after I worked on
by tildef 4y ago
I write descriptive commit messages because the code I check in is likely to contain a bug. This bug tends to be discovered a couple of years after I worked on the code. By linking my commit message to an issue and having a good explanation for why I've done what I've done, I can easier get into the mindset I had when I committed the buggy code. I find my life gets less stressful this way. I do agree that just regurgitating the files/classes/methods a commit touches isn't very useful. I'll consider ceasing to write "good" commit messages when I'm confident the code I check in doesn't contain any bugs.
- rvdginste 4y ago> I'll consider ceasing to write "good" commit messages when I'm confident the code I check in doesn't contain any bugs. Please don't. As much as it is useful to fix buggy code at a later point, it is the same useful to prevent introducing buggy code at a later point! Never saw some code that looked funny at first sight, and that you considered 'fixing', then checked the commit messages and understood why the code was written the way it is? Fixing it, would have meant introducing a bug.
- wizofaus 4y agoIf every PR you put up is "likely" to contain a bug, you're doing it wrong.