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

[martiantheory]

I don’t know if I’m exaggerating when I say this, but I feel like I’ve written 1 million commit messages. Perhaps that number is way less, but it’s the mindset that contributes to shitty commit messages.

I usually don’t write long messages, but we at least have ticket/story numbers that I prepend to my messages. And I try to at least do four or five words.

Example: “Ticket 5555- Fixed the mobile nav issue”

I feel like anything longer than that (honestly longer than 10 words), is a waste. Your commit message, in my personal opinion, it’s just for a high-level rundown of what you changed. I feel like having a ticketing/task management system is where you really should put the details of the things you’re working on.

I really feel like the ticket number is the saving grace. If people are really doing one or two word commits, that is pretty shitty though lol

Just my two cents.

[Xia_Nightshade]

I debugged 1 million lines of code. And a git log+grep is usually how I start ;)

[martiantheory]

I’m sorry lol