> I think, as the original commenter also wrote, this might be worth it in much slower paces projects that is run in another cadence / over mailing lists. Very

> I think, as the original commenter also wrote, this might be worth it in much slower paces projects that is run in another cadence / over mailing lists. Very much this. If I'm modifying some rather obvious and ovreall simple thing like an obvious config of a grafana, adding a customer to a config and such things... it's hard to really bother with a long commit message. Also, with modern tools like VSCode with the Gremlin plugin, I don't think I'd have spent many words on removing a weird whitespace from a code base, to be honest. On the other hand, if I've spent 4 hours thinking and 2 of those hours discussing the change with another DBA changing a 2 into an 8 in the config of an SLA-critical postgres cluster... spending 10 minutes on a commit message in the config management is - with regard to time - a footnote, irrelevant and inconsequential. But it can be worth more than gold down the road if you ask "Why 8? Why not 6!"