@[email protected] to Programmer [email protected] • 13 days agoWhich one are you reaching for today?lemmy.worldimagemessage-square47fedilinkarrow-up1550arrow-down12
arrow-up1548arrow-down1imageWhich one are you reaching for today?lemmy.world@[email protected] to Programmer [email protected] • 13 days agomessage-square47fedilink
minus-squareBougieBirdielinkfedilinkEnglish10•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-square@[email protected]linkfedilink3•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.
minus-squareblaue_Fledermauslinkfedilink2•13 days agoForcing myself to write in the format of Conventional Commits has helped me a lot to write better commit messages.
minus-squareFunbreakerlinkfedilink1•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
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”
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
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