Was digging through a project at work today where some guy in 2014 made 100+ commits in a single day and the only one that had a comment said “upgrading to v4.0”.
git commit -m “minor tweaks”
+3,276 -4,724
Bug fixes. Too many to count.
deleted by creator
I try to follow https://www.conventionalcommits.org/en/v1.0.0/
For me, the need it: when production is on fire, as a responsible person, I want to be able to understand why the change of this commit has been made. Perhaps also what were the drivers of the implementation.
I also have this onliner to commit and push each 10min:
watch -n 60 'git add . ; git commit --allow-empty-message -m "" ; git push'But those commits would never be merge as they are to master or main. It’s just if I loose work on my laptop. Worst case a
git rebase HEAD~has to be done before the PR review.Like the default Merge messages that git creates.
“Add some new feature” “Fix this and that” “Refactor XY code”
Not “Adding”, “fixed”, “Refactors” or anything…
Developer Initials - Jira ticket number which includes the project abbreviation and the ticket number - brief description:
DA - HHGTTG-42 - fix question answer format
If you need details you look in the ticket.
Developer intials seems a tad redundant since the commit is tied to author(s). But I guess it is only 2 extra char
Conventional commits all the way! Even if I don’t use the keywords (feat, fix, etc.) I always write the comment in imperative tense; the message should tell you what happens if you merge it.
That’s pretty neat. Is there a forked version that adds ticket number as a mandatory first class citizen? Cause that’d be darn near perfect.
