*Interesting* commit messages

There was a good thread in 2020 about git commit messages (which has been locked for inactivity). Reopening the subject.

I saw this today (punctuation and capitalization intact):

i changed a number

pile on, folks…

20 Likes

Looks back through our git commit history for this year and finds nothing interesting

Huh. Maybe I am teaching these students something after all.

27 Likes

“Ari got a new linux and is testing to see if the software he installed works (he likes to talk about himself in the third person)”
One line.

“Rkfjfkaevert “whoops, forgot javadoc lol””
“even MOREEEEEEEE changes”

4 Likes

Looks through commit messages of project at my workplace (well former workplace now)…


14 Likes

I promise we’ve gotten somewhat better at this, but some highlights (lowlights?) from the last few years:

  • “Fixed a problem with duct tape” (whether this was a metaphor has been lost to history)

  • “Literally two indents in the code”

  • “it builds now”

  • “try fix”

  • “LOTS OF CHANGES”

  • “this has merge conflicts”

  • “no message”

  • “from tonight”

  • “turret boiz :)”

  • “prepare for tunie”

2 Likes

image

39 Likes

My personal favorite from our 2019/20 code base: Screen Shot 2022-02-07 at 10.20.18 PM

16 Likes

Addition shenanigans from 3216:
no reloading

code cleanup

image

image

7 Likes

“Changed code to release the kraken”

“Fixed all the things”

“I did stuff”

5 Likes

Oh I have way too many of these, here are some of our best:

The frequent “last commit of the night” inevitably followed by “oops forgot this”

“very, very bad code”

“I did code”

“k”

“Cooper added a space” (this one is from @Cooper3175)

“I give up”

“so close but its 1am”

And my personal favorite:
“SWERVE WORKS FOR REAL!!!”

7 Likes

At a previous employer I was working on a project that had been handed over to us from a development team in Poland.

I’m not joking when I say that the entire Git history looked like this:

commits

Each one essentially translates to “changes” or “fixes”.

13 Likes

Some personal faves…

6 Likes

Darned mentors…

6 Likes

The moral of this thread: teach your programmers how to use git commit --amend.

14 Likes

Funny, we use The Kraken (well, GitKraken) to manage our code :slight_smile:

3 Likes

Our students usually do a push immediately after the end of day commit. doing amends after that gets… interesting?

2 Likes

Gotta learn to give yourself a buffer between committing and pushing, or else switch to a branch/PR workflow and get comfy with history rewrites. I suggest the latter approach.

4 Likes

Or interactive rebasing :wink:

3 Likes

Oh I can fix that! --force (/s, please don’t tell your students to do this)

2 Likes

Same day:

Capture

Its not actually that bad, but its not the prettiest thing in the world either. Gets the job done though…

4 Likes