What's the worst commit message you have ever seen?

Small Fixes

Added 1800 new lines...

One senior guy managed to merge with the commit template, as is, with **Insert brief summary here** and **description goes here**

It was one with a message that someone copied from a commit I had made a full year before. It broke the build right before a release and the commit message bore no relation to the changes, of course.

Because they had copied my message, it had my initials in. I had visits from irate managers in other buildings who ranted at me for a good 5 minutes without letting me get a word in to tell them that 1) it wasn’t me, and 2) undoing a subversion commit was a one-line command and not a good reason for the stupid amount of drama (there were no database or other irrevocable changes).

The last manager to speak to me told me it was still my fault as it was a bad message in the first place. The message read “Fixing typo in the audit log”.

"A dumbass committed her email address hardcoded as a recipient for all mails, again."

-- Me, the dumbass

"fix ci" "Again" "Maybe?"

Every time I work on CIs I just lose it after 1 or 2 commits and squash merge later on. Also when integrating projects together (eg I'm working on a language and made a POC for a new parser in a separate project) I'm just like "hajzjgkzlabai yes"

git commit -m 'oops'

Two users trying to chat with each other via commit messages.

1: "Youtube bro" 2: "Ohoo thanks"

Me on feature branches when I have weird CI issues: “floopie 7”. You can guess what the previous ones are. Yes I’m aware of amend but this is easier and I just iron that stuff out when I fixed my problems

I just pushed "idefk", cause frankly, no idea what was in it, but it touched half the repo

Empty commit message. Yes it's possible. Yes it's as bad as the cli tries to prevent it

Accurate

Probably anything saying "Commit" as the main verb (apart from "Initial commit"). "Add some code" is annoying but "Commit some code" is so much worse to me. Yeah, of course, every commit is committing some code lol.

For personal stuff especially when I use git just to sync between laptop and computer most of my commits are the things that don't work and I use for new stuff ~for changes and X for broken stuff.

So a commit can be " + new feature ~logging to accommodate new feature X Edge case crashes the new feature."

Worst commit that i pushed receantly was git commit -m "._." for my personal js practice repo. I needed it because all of the content is "CRLF" but I'm using "LF" on my machine.

I use a single dot when committing to a feature branch. I will either rebase or merge --squash anyway, so what's the point really.