Stack OverflowWhat is the WORST commit message you have ever authored?
[+56] [78] rpkelly
[2009-05-26 07:16:48]
[ version-control polls fun ]

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?

This should be community wiki. - IAdapter
This should be migrated to - the_drow
[+148] [2009-05-26 07:19:58] Rune Grimstad [ACCEPTED]

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

(4) +1: exactly what I was about to write... - Fredrik Mörk
(11) Should be community wiki. Also, not the worst. Absolute worst is not using source control. But I swear, I'm changing that! - Chris Lutz
(8) Actually, an incorrect comment is much worse than an emtpy comment. E.g. "fixed comment" when you actually changed a method signature... - sleske
I do exactly the same. I just don't think about it. - Liam
Not the worst, but pretty bad. - Nate
Second worst. The worst of all is 'a'. The dev took the time to bypass the 'Comment must not be null' rule, but didn't take the time to document what the heck just went into the system. - glasnt
[+96] [2009-10-23 19:33:28] Eduramiba
(\ /)
(> <) Bunny approves these changes.

(20) +1 ha ha ha ha! (had to add 3 ha's to be enough for a valid comment) - Chris Ballance
(3) Are you sure Bunny approves? He looks a wee bit angry/scared there... o_O - glasnt
[+75] [2009-10-15 02:12:36] jleedev

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:

  • Some shit.
  • add actual words
  • giggle.
  • Whatever.
  • Finished fondling.
  • 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.
  • 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
  • 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++?

(25) "why the fuck are we using C++" best one :) - romkyns
Some of my comments look like this. - tster
Is this supposed to be one big block? - Joachim Sauer
lol @ the guy committing and saying goodnight...I saw this once. - Shawn Mclean
[+41] [2009-05-26 07:48:22] Ed Guiness

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

(4) Fully agree. There are times when no message, or something like "bug fixes", works reasonably well. If you don't have an issue tracking system (and I don't at home), you can't cross-reference to issues. If it's some minor bugfixes, you can see what happened easily enough from the version diff. - David Thornley
[+37] [2009-05-26 07:53:57] Patrick Cornelissen

"." or "changes"

(5) +1. "." was always a favorite of mine :-) - paxdiablo
(4) Surely you mean "................" as there's a trigger which checks for a minimum of 16 characters - Pete Kirkham
Pete, this depends on your setup. :-) (And the VCS you use) - Patrick Cornelissen
I prefer "x" (but in SO you have to type 15 chars) - erikkallen
In this case check Petes "solution" ;-) - Patrick Cornelissen
+1 from my muscle memory, which fondly remembers git commit -a -m '.' - ide
[+36] [2009-05-26 07:25:47] hkdk3107

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

(3) +1 - Assert.IsTrue(1 == 1) would have also worked ... - Martin
(9) That’s actually a very, very good commit message. - jleedev
[+27] [2009-10-02 15:40:56] Mike Two

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

(2) Awesome! this is going to be my next svn comment. - Jeffrey Greenham
[+23] [2009-10-16 18:03:58] Alex Gaynor

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
  • 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
  • bifurcation
  • 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.

+1 for "more ignores". And again...and again....and 'crap, I forgot to ignore that directory as well'... - richsage
Apparently this Eric fella is holding you guys down. - Omar
+1 for WTF is this. - Stephen
The weirdest thing is that I googled the last commit out of curiosity and it doesn't really change any JS code. (…) - viraptor
That commit isn't mine :) - Alex Gaynor
I laughed out loud at 'small is a real HTML tag, who knew.'! Gold. +1 - pinkgothic
[+22] [2009-10-15 02:18:01] SketchBookGames

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.

(14) I put an Ascii picture of the USS Enterprise (Original) in for revision 1701. - Alister Bulman
I got a fever, and the only prescription is more cowbell! Will Ferrell is a legend! - Jake Scott
[+22] [2009-05-26 08:41:06] Ranieri

Whooohoo Revision 666!

On a pointless change of course.

(3) Hehe, I did something similar on revision 1337 once :P - cwap
[+15] [2009-05-26 07:55:40] Mark Glorie

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 =(

(26) I thought you were going to say there was an ad in a commit message; "Fixed user login but --This commit brought to you by Burger King." - chap
[+14] [2009-10-23 19:54:00] Brian Leahy

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

[+10] [2010-09-30 13:09:21] Ed Daniel
(This space intentionally left blank)

[+10] [2009-05-26 07:25:03] mouviciel

This is something like:


[+9] [2009-10-21 10:47:49] ssg

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...
//                       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...

(13) Moved something to somewhere...LOL! - flq
(1) The dates aren't even in order - he just inserts a new comment 'somewhere' at the top. - Kirk Broadhurst
(2) Kirk, this is a compilation from multiple sources. Dates were in order for each source, at least :) - ssg
[+8] [2009-11-09 23:15:15] Chris Ballance
That's just how I roll

[+8] [2009-05-26 07:41:00] RobS

"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)..

[+8] [2009-05-26 08:22:20] community_owned

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

(1) I've used this after initially committing something that was broke then quickly committing a fix. - Chris Lively
[+7] [2009-05-26 07:40:46] Greg Hewgill

My usual nondescript commit message:


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!

(2) The good thing about "oops" is that usually looking at the commit immediately before that one tells you what it's all about. - Joachim Sauer
[+7] [2009-10-15 04:20:37] robotadam

One of my worst was quite recent:

I am even stupider than I thought

[+7] [2009-10-21 11:00:05] ammoQ

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.

[+7] [2010-10-05 21:11:33] Martin Broadhurst

fortune -o | cvs ci -m

[+6] [2009-05-26 08:14:22] hmemcpy

Not the worst, but

oops, forgot to add the file

is close enough.

[+5] [2009-05-26 08:33:38] Omry

Alex made me do it

[+5] [2009-10-21 11:01:50] Tim Post

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

[+4] [2009-10-15 04:40:41] Tullo

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.

(3) There is a serious flaw in your code, you may want to refactor it some day. It should read ICanHazState. - chiccodoro
[+4] [2009-10-15 01:35:44] thephpdeveloper

Revision 1024!!

[+4] [2009-05-26 07:49:05] bayer


For my master thesis' latex repository.

[+4] [2009-05-26 07:38:52] victor hugo
  • 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 :-(

(6) at least you used a vcs on school projects :) - SnOrfus
(2) "Added missing file in previous commit" - dont think this is too bad if previous commit was descriptive enough. - Owen
[+4] [2009-05-26 07:23:26] Alan Haggai Alavi

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.

(12) I once had a coworker who used only one commit message in two years: "updates" ;) - Aleksandar Ivanisevic
That is shocking! :-) - Alan Haggai Alavi
(6) @Aleksandar: I didn't know we had worked together.. - Chris Lively
[+4] [2011-05-03 13:38:54] Andrey Shchekin

My favorite is:

Minor refactoring.

(when changing 50-150 files)

I do not remember whether I ever committed that message, though.

[+3] [2009-05-26 08:20:34] ayaz

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

[+3] [2010-09-30 12:25:00] Kris Jenkins

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.

For some reason I had to re-read that last line several times, before I stopped reading it as, "I killed her before she left" (I think it's time to seek professional help.) - Slomojo
[+3] [2010-06-25 16:21:29] Pat

-Various changes

[+3] [2010-10-05 21:08:14] Jay

On revision 2013 of my current project:

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

[+3] [2011-05-03 09:35:01] Kevin Cantu

The best one I've seen before:

Don't stand between a bear and its cubs.

[+2] [2010-12-23 02:54:15] darvids0n

Something along the lines of: Avoided a potential nuclear disaster

When the commit was essentially fixing a "bug" which would have erased the DB table of students from the live database of a university's CMS.

[+2] [2010-10-05 21:12:47] stefan_g

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

[+2] [2010-03-16 19:00:04] Kitto

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.

[+2] [2009-10-23 19:40:53] Macke

"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. ;)

[+2] [2009-10-23 19:41:52] Gav

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

"Continued development..."

[+2] [2009-05-26 08:37:02] kevchadders

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

[+2] [2009-05-26 08:14:43] kay.herzam

"work in progress"

[+2] [2009-05-26 08:18:36] 動靜能量

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).


(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).


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

[+2] [2011-01-31 03:55:50] Slomojo


Which is about the most useless/obvious message ever.

[+1] [2011-05-04 07:38:01] furtelwart

This and that

Very thoughtful :)

[+1] [2009-05-26 08:38:19] JasonSmith

"Test commit. Please ignore"

I don't think I ever committed that to a real project but that's the one that drives me crazy. One of the benefits of distributed SCM is that you can test commit on your own and then uncommit before going public. - JasonSmith
[+1] [2009-10-02 15:47:03] Eduardo León

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

[+1] [2009-10-15 04:24:17] TM

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.


This is why I'm glad I'm also in charge of our Subversion server. If I mess up a comment badly enough, I'll temporarily modify the Subversion hooks so I can svn propedit my commit messsage ;-) - Mike Spross
(1) @Mike Spross: you don't need to use svn propedit if you're the admin, you can use svnadmin setlog - rmeador
@rmeador: I didn't know that. Time to re-read the SVN book ;-) - Mike Spross
[+1] [2009-10-23 19:49:04] Synetech inc.

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.

[+1] [2010-06-25 16:20:39] orbfish

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


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."

[+1] [2009-10-23 19:03:53] Alexander

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

[+1] [2010-08-06 15:29:17] chiccodoro

Which means "minor change".



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.

Update: Oh, and of course I forgot this one:


I've seen the bugfix one too.. no clue what was supposed to be fixed and how it was attempted to be fixed... - Andre Holzner
[+1] [2010-12-28 16:00:29] Hanno Fietz

I sometimes work quietly on some big refactoring and then commit it in one big chunk with a message like "BANG".

[+1] [2011-01-07 15:43:19] Richard J. Ross III

My favorite:


I did that after I made several minor changes to the project that really had nothing to do with the actual code :)

[+1] [2011-01-07 16:25:57] badgerr

Mine are mostly useful, but I've just found these in trac...:

  • rev. 4000 ;)
  • god knows what's changed here but i'll commit it anyway
  • backing up what i have before i break it
  • it WORKS!
  • stuff that makes this thing work
  • hjtjhgfjhbgyjtrhjggfty
  • manual merging of my branch because SVN SUCKS
  • put this here, wasn't sure where else it could go
  • oh look i found an unrelated bug =/
  • rev 6000 for the sake of it :D
  • that fix yesterday didn't work properly :(
  • some more cool shit
  • geometry switcheroo
  • fix for derek's audio problem
  • would help if i used modulus correctly too...
  • rev 7000 :D
  • uncommented important lines...
  • this is now slightly more impressive
  • crosses fingers can has lots of working job queue code? xD
  • backing up this shit before i rewrite the collisionnode class
  • accidentally disregarded my own naming convention ¬_¬
  • fracking svn
  • ho ho ho

'this is now slightly more impressive' is my favourite of the lot. XD - pinkgothic
[+1] [2010-10-05 21:16:05] Chris Lively

My favorite: Frist!

[0] [2010-12-02 14:45:45] MadMad666

Worst than the commit comment, was to find a someone's phone number in some developer's commited code! WTF!

[0] [2011-05-03 10:01:32] Abhijeet Pathak

This one is the character sequence which gets typed naturally when we have nothing in our mind:



[0] [2011-05-03 10:09:05] SpyrosP

I wrote that actually :P

'sudo reboot now - oops'

[0] [2011-01-31 03:40:09] VoodooChild

REV3 : Fixes to the fix of the fix for defect #xyz

REV2 : Fixes to the fix for defect #xyz

REV1 : Fixes for defect #xyz

they were all in within a period of 5 hours and definitely made me smile :-)

[0] [2010-10-05 21:15:15] George Mandis

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.

Needs moar rebase. - rpkelly
[0] [2009-10-23 19:08:41] David Oneill

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

[0] [2009-10-23 19:10:05] Jordan

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

[0] [2009-10-23 19:16:09] JuanZe

I always put comments on my commits, so I'm not guilty of this sin. But hundreds and thousands of commits from developers who used to work in the same company as me were commented with no message or ∗∗∗empty log message∗∗∗ (the IDE default). So annoying!

[0] [2009-10-23 19:21:30] CodeJoust

git commit -m "Inital Commit"

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

[0] [2009-10-23 19:25:45] DefyGravity

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

[0] [2009-10-21 11:05:14] eugeneK

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

[0] [2010-03-10 08:56:48] gamers2000
Joel - 20/07/09

And the most prolific commit message I've used -


[0] [2009-10-21 10:12:54] Pekka

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

[0] [2009-05-26 08:56:53] community_owned

"committed changes"

[0] [2009-10-02 15:30:00] JB King

"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?

[0] [2009-05-26 08:38:41] none

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

[0] [2009-05-26 08:30:26] apostlion

“Obligatory placeholder commit message”.

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

[0] [2009-05-26 08:06:03] Someone else


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

[0] [2009-05-26 07:23:19] bastijn

[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 :).

[0] [2011-05-03 14:15:43] Jonhnny Weslley

here there still be dragons...

[0] [2011-05-03 20:08:26] Matt H.

a handful of sundry fixes.

A bit of cheek that usually meant I was fixing someone elses fubar.