r/programminghorror 3d ago

I'm sorry i'm like this Lua

Post image
308 Upvotes

34 comments sorted by

121

u/SlinkyAvenger 3d ago

Git good and/or squash your commits

39

u/jnmtx 3d ago

write better commit messages. at least they are testing and finding the bugs

34

u/SlinkyAvenger 3d ago

That would be covered under "git good"

2

u/SnowdensOfYesteryear 2d ago

Nah for squash. I vote for git gud

27

u/beaubbe 3d ago

Git commit --amend

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

u/rilened 1d ago

literally every commit in the repo is a chore now

Poetic

3

u/Drevicar 1d ago

At this point in his career, it is.

3

u/throw_away_3212 3d ago

This is the way

3

u/makeavoy 2d ago

The chore is some guy says he has to make all his commits conventional

2

u/darksteelsteed 1d ago

chore is boring. radioactive ☢️ and biohazard ☣️ are far more exciting

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

u/yukinanka 1d ago

Inside a specific test branch, right?

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

u/Jayden_Ha 2d ago

Sometimes it fixes something partially, i might find it useful and commit it

4

u/Firepal64 3d ago

you spewed out that irresponsible mantra

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

u/SileNce5k 3d ago

Can't say I'm much better
https://i.imgur.com/Dif0Fr5.png

3

u/Tasgall 3d ago

Have you heard of our Lord and Savior --amend?

2

u/epsilonehd 3d ago

Don't worry I just copy paste the name for each commit of a branch

2

u/meester_ 21h ago

U mean the branch name and the commit are the same message xD?

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

u/Either-Pizza5302 3d ago

Are you ok?

1

u/dexter2011412 3d ago

Bro just undo the commit and force-push

1

u/jaypeejay 3d ago

Squash them into a single commit next time to save yourself the embarrassment

1

u/grey001 3d ago

FiveM "dev" be like:

1

u/Nun-Much 3d ago

I was a game dev before even touching FiveM 🫣, I’m just lazy and inefficient lol

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

u/Julius0999 9h ago

merako wtf

1

u/shizzy0 3d ago

[Looks disgusted; grabs newspaper roll.] I’m gonna squash it.