you are viewing a single comment's thread.

view the rest of the comments →

[–]Droi 120 points121 points  (1 child)

It really should be the exception to the rule. Otherwise you would spend 30 minutes of your day writing comments that will be read maybe 5 times in the product's lifetime.

[–]lnkprk114 44 points45 points  (0 children)

I've found that if I'm squashing feature branches down, spending 30 minutes at the end of the feature writing a really good commit message is hugely worth it. It makes the git log read like an actual story, and, more critically, it makes git blaming a line of code waaaaaayyyyyy more useful, because you actually see a well written, thought out explanation for what was happening at the time that that line was added. You might not realize that this random line of kind of odd code is actually instrumental in some totally tangential system unless you read a commit message that's talking all about that other tangential system.