HootinNHollerin@lemmy.world to Programmer Humor@lemmy.ml · 13 days agoWhich one are you reaching for today?lemmy.worldimagemessage-square52fedilinkarrow-up1536
arrow-up1536imageWhich one are you reaching for today?lemmy.worldHootinNHollerin@lemmy.world to Programmer Humor@lemmy.ml · 13 days agomessage-square52fedilink
minus-squareBougieBirdielinkfedilinkEnglisharrow-up9·13 days agoI’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
minus-squaregnutrino@programming.devlinkfedilinkEnglisharrow-up14·13 days ago“Fixed stuff” … “Fixed for real this time”
minus-squareblaue_Fledermaus@mstdn.iolinkfedilinkarrow-up3·13 days agoForcing myself to write in the format of Conventional Commits has helped me a lot to write better commit messages.
minus-squareFunbreaker@lemmy.ziplinkfedilinkarrow-up1·edit-213 days agoLooking 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
minus-squareCanadaPlus@lemmy.sdf.orglinkfedilinkarrow-up3·edit-213 days agoWhat 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.
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
“Fixed stuff”
…
“Fixed for real this time”
Forcing 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
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 -i