Looking at the website, Conventional Commits seems a little verbose for ny tastes but it probably helps actually communicate the changes so everyone is on the same page. Thanks for the tip!
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
I’m definitely writing useless git commit messages
For work, I at least include the Jira ticket id
For personal stuff, it’s sweeping features stuffed into one commit that barely describes what was changed
What was the git flag to basically rewrite history again?
I’ve definitely been guilty of this, but if I can redo my changes in narrative form before I push I bet I won’t have to.
git rebase -iForcing myself to write in the format of Conventional Commits has helped me a lot to write better commit messages.
Looking at the website, Conventional Commits seems a little verbose for ny tastes but it probably helps actually communicate the changes so everyone is on the same page. Thanks for the tip!
Edit: Spelling
“Fixed stuff”
…
“Fixed for real this time”