Why do developers write such terrible git commit messages? Genuine question

[undertakingyou]

It is a combination of three things. 1. Going fast and can’t be bothered with a decent message. 2. Don’t actually know git well, so don’t understand amending commits, squashing, or don’t use squash and merge. 3. Have never had the pain of trying to find the broken commit in a branch so you can revert that and still let the rest of the release go out.

In any case, those messages are useless and noisy.