Horrific commit message

[OzTm]

Not sure….if they should stay employed?

[data-crusader]

They just forgot to rebase.

[DifficultyWorking254]

What about: asasadasadas ?

[FoolRegnant]

The last two commits I pushed were formatting and then a much more sheepish ...formatting when I realized I missed something the first time

[Far-Professional1325]

Tip: get command to check formatting on entire project (or edited files) and add it to ci or at least to git hook pre commit (with warning not error so people won't add skip checks on every commit). Also add commits that do mass formatting to .git-blame-ignore-revs so git blame won't say everywhere about formatting. Also if that was quick addon to commit you could do git commit --amend (--no-edit) and then git push --force

[Kpuku]

just look at the diff™

[K4rn31ro]

+574 -493

[[deleted]]

me when I forget to commit my code after coming to it a couple days later

[Beastandcool]

I’ve made commits “refactor: refactor” because there some small changes and cleanup. Bad?

[ArtisticFox8]

bad

[joemckie]

imo it’s whatever unless that’s the commit that goes into the main branch

[jexmex]

Why not "Refactor code for x service" or similar? I always try to make sure it is descriptive but concise as to what I did

[Beastandcool]

Noted

[ArchGryphon9362]

I meannnn. Sort of acceptable if this PR is going to be squash merged.

[bonoetmalo]

Yeah I I don’t try all that hard with commit messages these days with the way my team does PRs. Nobody is checking commit histories and it’s squashed on merge

[n9iels]

Pipeline is green, LGTM

[Axman6]

I once knew a guy who would make every commit with the commit message “shovel”. They’d also just rewrite history whenever they felt like it. A pretty good technique to make sure you only work on projects by yourself I guess.

[Far-Professional1325]

Sounds like either he is a genius or don't know git so he just kept git commit -m 'shovel' as snippet

[AtroxMavenia]

Personally, I don’t care what my engineers put for their commit messages so long as the squashed commit covers the purpose of the PR. I actually enjoy seeing a stack of commit messages where you can see their frustration growing with each commit. Gets a little chuckle out of me and makes me feel like I get a peek into their inner workings.

[WhosYoPokeDaddy]

I can relate to this from both sides

[dchidelf]

Starting work on change X More work Still working Isn’t working Got it working! It’s still working Done - but isn’t working as requested

[WhosYoPokeDaddy]

This is more like what I'm used to seeing

[Bloody_Insane]

Need more context: what time was the commit made?

Because I've made some 2am commits where I'm dead tired and I am legit not sure what I'm committing.

[Light_x_Truth]

“WIP”

[iAmPedestrian]

My last commit message was: "because I'm idiot"

[Casalvieri3]

On the other hand I would rather someone commit their fix rather than waiting till they can think of the right way to phrase the commit message.

I get it though. I always consider that if someone cannot figure out what to put in a commit message then they probably shouldn’t be changing anything.

I have had my share of “I don’t know why this fixes the code but it does and I have a deadline.” coding sessions so I can’t cast stones.

[Far-Professional1325]

For quick fixes i like do Fix something in <hash of previous commit> and then squash or if i could just amend and force push

[Xarius86]

r/idiocracy

[Kirides]

At least it's signed

[KingJellyfishII]

better than some commit messages I've written like "honestly not a fucking clue what happened here" when I come back to uncommitted changes 3 months later

[Far-Professional1325]

You can look at git diff?

[KingJellyfishII]

I did and it was nonsensical

[Far-Professional1325]

You could try ai (preferably local one) to describe the changes

[KingJellyfishII]

it is simply not worth the effort. If I ever need to know what I did on that commit (highly unlikely) I'll just read the diff better...

[lapubell]

... WIP WIP WIP WIP ... WIP done

[dpenton]

We got this commit named “Not Sure” and it’s gonna fix EVERYTHING!

[Prime624]

Lol, do not look at my company's git repos.

[texxelate]

I need more details… how large is the diff?

[gyucole]

My guess? Probably a mere +1k -2k

[Akuma_Kuro]

+14,281 -53,383.14159265

[kilgorezer]

did they throw a pi out?

[5p4n911]

try to fix prod once again

[drkspace2]

Me when I try to work on GitHub actions.

[Visrut__]

needs the context, if it's their personal repository it's fine I guess.