Funny initial git commit messages

Whenever I start a new project, I struggle with what to put in the very first commit message. After doing a “git init” there is technically nothing there and no work done yet, so how to describe this initial step?

Initial commit” always seemed a little futile, so I started gathering some better examples on what to put in the message for the glorious start of a new project and I am sharing them here for all of you to marvel at:

This is where it all begins...
Commit committed
Version control is awful
The same thing we do every night, Pinky - try to take over the world!
Lock S-foils in attack position
This commit is a lie
I'll explain when you're older!
Here be Dragons
Reinventing the wheel. Again.
This is not the commit message you are looking for
Batman! (this commit has no parents)

Or, you know, just use

I’m always happy for comments with further ideas and will be adding to this list constantly.


  1. I liked the “Reinventing the wheel. Again.” comment. But I’m sure if it were me, it would have many more ellipsis as a sign of annoyance.


  2. I have brilliant idea for you: don’t commit empty project with no work done yet. Setup project eg. with master/detail view and commit message possibilities are endless! Fair enough? πŸ˜›

    1. Although there are legitimate reasons to start with an empty repo, I usually don’t. Most of the time it’s the bare framework and some setup code. Nevertheless I found out that usually there is not enough work done to describe it in a meaningful commit message. That’s why I came up with this list.

  3. Haha, it has always bugged me that “Initial commit” doesn’t have a period and is not an imperative statement.

Leave a Reply to Ricardo Lopes Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.