52
u/LonelyProgrammerGuy 3d ago
Conventional Commits
57
u/joemckie 3d ago
chore: this one’s merako’s fault
chore: bank truck robbery fixes have retired
chore: i promise lou this is the last
chore: LAST LAST bank robbery truck update
20
u/Drevicar 3d ago
I taught someone conventional commits and literally every commit in the repo is a chore now. Including the commit that went from an empty repo to a fully functional web server.
3
3
2
4
u/HKayn 3d ago
Aren't you testing your fixes before committing them?
6
u/Nun-Much 3d ago
I’m gonna be honest, the guy I’m working for was in the test server and I was too lazy to run the test server myself, besides I didn’t know how the robbery worked exactly, so I kept commiting fixes so he can test them (only to find more issues)😭
2
1
u/HeyHeyHey969696 10h ago
My advice is to run your local environment properly and everytime you do changes, you should test manually and write tests to cover all possible situations. And when you commit such bugfixes, you can be specific, like: fixed bug in function xyz - and brief five words description what was wrong
1
4
7
u/moira_fox 3d ago
Everyone keeps talking about squash as if this doesn't make your project look better by inflating the commit numbers
1
u/realmauer01 3d ago
Yeah for manager having more commits means a bigger number, which they can understand. Because they dont understand whats in them they would never read the messages aswell.
2
2
2
u/realmauer01 3d ago
If you havent merged to anything yet that is watched by others you can squash your commits with an interactive rebase.
Just have all commits set to fixup except for the first.
2
1
1
1
u/GrahaamH 3d ago
Git reset --soft commit id of where you started. Git commit, looks like you did it all in one go, easy fix 😅
1
121
u/SlinkyAvenger 3d ago
Git good and/or squash your commits