What is the WORST commit message you have ever authored?

Question

I mean, we've all done it, making some changes and the checking them in with messages such as "made some changes" or "fixed a bug." Messages so inane, so pointless, you might as well have written "magical fun bus" in their place (of this, I am guilty), as it would be, perhaps, more descriptive. I ask you then, what is the most pointless, most off topic, strangest, or just WORST commit message you have ever authored?

Answer 1

The worst must be no comment at all. And I am guilty... :-)

Answer 2

[insert friends name] is the bomb.

when you fix one of their errors. Became some sort of hype among friends after one started it when fixing useless stupid errors. Though the projects were not that big :).

Answer 3

Just checked git log and I found Corrected mistakes (committed by me!) which I think is not a good commit message as it does not shed light on what mistakes have been corrected. I should have added a description.

Answer 4

This is something like:

Updated

Answer 5

Switched off unit test X because the build had to go out now and there was no time to fix it properly.

Answer 6

• Committed some changes
• Some bugs fixed
• Minor updates
• Added missing file in previous commit

I feel really sorry most of them were in school projects I promise :-(

Answer 7

My usual nondescript commit message:

oops

This usually results from committing more than was intended with svn commit. However, now that I use Git, this essentially never happens. Not only do I not generally make the mistake of committing more than was intended (I don't use git commit -a), but Git allows me to fix the bad commit before pushing the commit anywhere else!

Answer 8

"fixed errors in the previous commit"

Says it all really.. i.e. stuffed up one commit, then failed to even describe what was wrong (and what was corrected)..

Answer 9

Much worse than no message at all is the message that looks right but is wrong in subtle and misleading ways.

Answer 10

STUFF!!!!!11

For my master thesis' latex repository.

Answer 11

"." or "changes"

Answer 12

Can't take full credit for this one, but one of the web designers was tasked with adding corporate advertising to the internal homepage. Check-in message:

Added a banner to the default admin page. Please have mercy on me =(

Answer 13

'hmmmmmm'

Added that once when I couldn't even be bothered to think of something crap to write as a comment. very bad.

Answer 14

Not the worst, but

oops, forgot to add the file

is close enough.

Answer 15

"work in progress"

Answer 16

i see these:

bug fix

(the file has been there for 1 year and gone through 60 revisions... so "bug fix" doesn't mean anything).

typo

(when i check the diff, there actually is a bug fix. so i wonder, is "typo" just to make the mistake look not so bad).

[blank]

(the CEO and CTO like to use empty comment).

Answer 17

A cursory look at a project I've been doing the past one year where I did not use git seriously for the initial three quarters of the project year, revealed these among other commit messages:

• minor changes
• some brief changes
• assorted changes
• lots and lots of changes
• another big bag of changes
• lots of changes after a lot of time
• LOTS of changes. period

Answer 18

"Nothing to see here, move along" - When there were actually some major canges within the project. I just couldnt be bothered writing something useful.

Answer 19

“Obligatory placeholder commit message”.

Yeah, I wasn't lazy to type it out, but I was lazy enough to think of something better.

Answer 20

Alex made me do it

Answer 21

A long time ago, in a galaxy far far away...

Answer 22

"Test commit. Please ignore"

Answer 23

"fix" for a 7 kb commit ... oops :-)

Answer 24

Whooohoo Revision 666!

On a pointless change of course.

Answer 25

"committed changes"

Answer 26

"Fixed the build"

While that does get to the point of why I'm commiting the change, it doesn't say anything about what I did change. That's why we have file diffs, right?

Answer 27

"put code that worked where the code that didn't used to be"

Answer 28

"I'm just a grunt. Don't blame me for this awful PoS."

Answer 29

Revision 1024!!

Answer 30

I feel this is just too good not to share. It was a programming assignment for our algorithms class. Apparently, we did most of the work after midnight; presented below are the more random/profane git commit messages:

• JOSH, WE WENT OVER THIS. EXPANDTAB.
• STEVE, WE WENT OVER THIS. C++ IO SUCKS.
• Some shit.
• add actual words
• I CAN HAZ COMMENTZ.
• giggle.
• Whatever.
• Finished fondling.
• FONDLED THE CODE
• this is how we generate our shit.
• unh
• don't be retarded.
• It works!
• unionfind is no longer being molested.
• Well, it's doing something.
• I'M PUSHING.
• Whee.
• Whee, good night.
• It'd be nice if type errors caused the compiler to issue a type error
• Fucking templates.
• I hate this fucking language.
• marks
• that coulda been bad
• hoo boy
• Fucking egotistical bastard. adds expandtab to vimrc
• if you're not using et, fuck off
• WHO THE FUCK CAME UP WITH MAKE?
• fix some fucking errors
• first blush
• uhhhhhh
• forgot we're not using a smart language
• include shit
• things occurred
• i dunno, maybe this works
• 8==========D
• whooooooooooooooooooooooooooo
• clarify further the brokenness of C++. why the fuck are we using C++?

Answer 31

the IT guy noticed revision 666 was coming up and wanted to make it special.

I convinced him that: "needs more cow bell" would be ideal.

a few months later the head of production was rather distraught because she thought the client had requested it.

Answer 32

One of my worst was quite recent:

I am even stupider than I thought

Answer 33

PROJ-1254: Some reasonable message

Turns out I made 4-5 commits with a completely wrong ticket id, it should have been PROJ-2154

Even worse: our issue tracking software looks up related code changes from the repository. Therefore, if somebody ever looks at that 6-month-old issue they will find a lot of random code commits that don't even make sense tied to it.

Oops.

Answer 34

Ready for it?.....

I did it for the lulz!

We checked in an interface:

public interface ICanHasState

...this is in a respectable business package, no less. If it weren't for obfuscation, someone might actually find that.

Answer 35

The following are all real commits made by me on one project:

• A fix I believe, not like I tested or anything
• Useful text
• pgsql is being a pain
• pgsql is more strict, increase the hackiness up to 11
• c&p fail
• syntax
• ericflo sucks
• ERICFLO SUCKS
• fix
• someone fails and it isn't me
• Gross hack because eric doesn't know how to code
• totally more readable
• better grepping
• fix
• fix bug, for realz
• fix /sigh
• Does this work
• MOAR BIFURCATION
• bifurcation
• REALLY FUCKING FIXED
• FIX
• better ignores
• More ignore
• more ignores
• more ignores
• more ignores
• more ignores
• more ignores
• more ignored words
• more fixes
• really ignore ignored worsd
• fixes
• /sigh
• fix
• fail
• pointless limitation
• eppic fail eric
• ajax-loader hotness, oh yeah
• ericflo broke the regex, lame
• small is a real HTML tag, who knew.
• WTF is this.
• Do things better, faster, stronger
• Fixed a bug cause brosner said to
• Use a real JS construct, WTF knows why this works in chromium.

Answer 36

WARNING xyz.php doesn't work in this checkout.

Answer 37

Back in 90's when we didn't have a revision control system, we were used to put change log entries at the top of the source code. Below are some of my entries from our GUI library. Jury shall consider that the defendant was 17 years old and a beginner in English back then :)

// 25th Sep 93 - 01:17 - I must sleep... it's working... in just three hours...
// 26th May 94 - 02:05 - SSG DID IT AGAIN!!!! THE ULTIMATE CHANGELINE
//                       DETECTION ROUTINES!!!!...
// 19th Aug 95 - 18:26 - I was wrong...
//  2nd Apr 94 - 21:12 - Completed with no bugs...
//  6th Aug 94 - 20:34 - Fixed a little bug...
// 10th Dec 94 - 02:11 - Fixed a bug in NoteLineCount... not seriously...
// 27th Aug 97 - 23:58 - woa!! this one was really HARD!
// 29th Jun 97 - 00:48 - Made it to compile...
// 13th Dec 94 - 01:04 - changed things...
// 26th Dec 94 - 00:22 - touched... (cs=2626)
// 31st Dec 94 - 00:21 - i think i fixed a bug... (cs=2605)
//  7th Oct 96 - 14:25 - perfect...
// 29th Nov 93 - 02:50 - Moved something to somewhere... goodnight...

Answer 38

Detailed description of an other change, which I made earlier to another file, simply because my IDE remembers the message I entered for that other commit. IMO this is much worse than a meaningless or empty message, since it's misleading.

Answer 39

"I'll explain this when I'm sober .. or revert it" .. thanks to git, I can't give a link.

Answer 40

got few times comments in foreign languages,,, good ones are the ones in which programmer speaks to the code ie. "got it bitch" ...

Answer 41

when i had improved performance of slow code,i changed engine started as ferrari engine started

Answer 42

oops

Looking back in the commit log, I did this 3 times in a row, about a month ago :-/

Answer 43

fixed a [insert guilty coworker's name here] bug....

Answer 44

git commit -m "Inital Commit"

No description, and too often used... something more useful/creative?

Answer 45

here are some choice ones from our commit log:

• missing functions
• tightened up the java in my service call
• adding my
• story commit to release lock for joe

Answer 46

(\ /)
(O.o)
(> <) Bunny approves these changes.

Answer 47

"good stuff only" .. but it's better in Swedish: "bara bra grejjor".

You know, like, it's good stuff, like. That's why I committed it, like. ;)

Answer 48

Classic for me and the other developer in the office used to be:

"Continued development..."

Answer 49

The worst I’ve personally done (a few times) was the following:

That’s not actually blank because a commit message was required, so I entered a non-breaking space (&nbsp / 0160).

I know, I know; it’s cheating. But to be fair, I’m the only one using this system, and the changes were really trivial.

Answer 50

"Does anyone read this? I'll be at the coffee shop accross the street."

Answer 51

That's just how I roll

Answer 52

Joel - 20/07/09

And the most prolific commit message I've used -

.

Answer 53

Besides the obligatory "Fixed some bugs" I had some "Final version" messages in my bachelor thesis svn repository logs. There were about 30 of them, evenly distributed among the last two days before the final deadline.

Answer 54

This isn't one I did, but one I saw:

D

Although this looks like a typo, what it really meant is "Converted source from using Guardian C system calls to using our proprietary D-series procedure wrappers."

Answer 55

-Various changes

Answer 56

(m)

Which means "minor change".

bugfix

then

Why has the +"*ç%&/ Visual Studio not added the file?

Although I have to admit that I don't regard any of these as bad: In the log, an "(m)" usually indicates: You don't need to look into this revision, the significant changes have been done before or after. The "Why has +"*ç...." indicates: This change has actually been explained in the last commit, so don't be surprised not to find it there.

Answer 57

No matter how often I asked, educated & pleaded, I used to work with someone who kept entering:

I change some files

She left before I killed her.

Answer 58

(This space intentionally left blank)

Answer 59

On revision 2013 of my current project:

We made it past 2012 and the world did not end!

Answer 60

fortune -o | cvs ci -m

Answer 61

"lol it almost works sharks with lazerbeams on their foreheads"

Answer 62

Sometimes I run these for shits and giggles:

git log --oneline | grep WTF
git log --oneline | grep thingy
git log --oneline | grep oops

It's usually good for a laugh.

Answer 63

My favorite: Frist!