Git Update Commit Message

By  on  

One of my faults as a professional developer is that my commit messages aren't always as descriptive as they could be.  Sometimes I even notice a spelling error in them.  Bleh -- that's not cool, man.  When I do catch that my last commit message isn't good enough, I find the following git command useful:

The command below rewrites the message for the previous commit.  You can omit the -m and message to go into the commit shell instead.

git commit --amend -m "This is the new message"

Do realize, however, that performing this after you've pushed to a remote repo is considered bad as it rewrites history. If you haven't pushed, however, the command above is gold!

Recent Features

  • By
    How to Create a Twitter Card

    One of my favorite social APIs was the Open Graph API adopted by Facebook.  Adding just a few META tags to each page allowed links to my article to be styled and presented the way I wanted them to, giving me a bit of control...

  • By
    fetch API

    One of the worst kept secrets about AJAX on the web is that the underlying API for it, XMLHttpRequest, wasn't really made for what we've been using it for.  We've done well to create elegant APIs around XHR but we know we can do better.  Our effort to...

Incredible Demos

  • By
    WebKit Marquee CSS:  Bringin’ Sexy Back

    We all joke about the days of Web yesteryear.  You remember them:  stupid animated GIFs (flames and "coming soon" images, most notably), lame counters, guestbooks, applets, etc.  Another "feature" we thought we had gotten rid of was the marquee.  The marquee was a rudimentary, javascript-like...

  • By
    Xbox Live Gamer API

    My sharpshooter status aside, I've always been surprised upset that Microsoft has never provided an API for the vast amount of information about users, the games they play, and statistics within the games. Namely, I'd like to publicly shame every n00b I've baptized with my...

Discussion

  1. This is one of the things I do more frequently :-/

    The good thing is that, with amend, you can also include in the commit new changes (provided that you have added them to the staging area).

    The drawback is that it’s **bad** to amend a commit that has already been pushed to a remote repository.

  2. May I point you to an article of my own, in which I describe some more solutions on how to change commit messages:

    http://www.gamez.name/change-commit-message-git/

  3. Dorian Marchal

    Be careful, this command rewrites history and shouldn’t be used if you already pushed your last commit.

  4. And you are noticing it now? :D

    One thing to remember is HASH is changed on amending.

  5. And you are noticing it now? :D

    Well, one thing to notice is that HASH of that particular commit is rewritten when amending.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!