Strong disagree. Commit messages that are only one sentence long should be reserved for truly trivial things. Signed, someone who regularly comes back to 18+ year old commits and enjoys the valuable details that would have been lost.
Comment on I've lately been making my git commit messages with AI
biddy@feddit.nl 10 months ago
If it’s faster to get an AI to write your commit messages than to write them yourself, your commit messages are too long. They should be one sentence.
Alphare@lemmy.world 10 months ago
learningduck@programming.dev 10 months ago
How about prefixing your commit with a ticket number?
If a commit message has too much information, then the commit has too much changes
IAm_A_Complete_Idiot@sh.itjust.works 10 months ago
Not having to swap over to a ticketing system just to see the context of a change is really nice (Or to add context on why changes are done a certain way). One line that says what you changed, then any context such as why it was done that way, and important notes about that change works wonders. It’s pretty much the exact model the Linux kernel uses, and it makes looking at changes great for anyone down the line.
learningduck@programming.dev 10 months ago
Good idea
kablammy@sh.itjust.works 10 months ago
And if one sentence isn’t enough, the commit has too many changes
lauha@lemmy.one 10 months ago
Good old "various changes*
glad_cat@lemmy.sdf.org 10 months ago
The worst commit history:
Tathas@programming.dev 10 months ago
x