HootinNHollerin@lemmy.world to Programmer Humor@lemmy.ml · 3 months agoWhich one are you reaching for today?lemmy.worldimagemessage-square53fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageWhich one are you reaching for today?lemmy.worldHootinNHollerin@lemmy.world to Programmer Humor@lemmy.ml · 3 months agomessage-square53fedilink
minus-squareBougieBirdie@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up0·3 months 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-squareCanadaPlus@lemmy.sdf.orglinkfedilinkarrow-up0·edit-23 months 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.
minus-squareblaue_Fledermaus@mstdn.iolinkfedilinkarrow-up0·3 months agoForcing myself to write in the format of Conventional Commits has helped me a lot to write better commit messages.
minus-squaregnutrino@programming.devlinkfedilinkEnglisharrow-up0·3 months ago“Fixed stuff” … “Fixed for real this time”
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.
“Fixed stuff”
…
“Fixed for real this time”