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
    Create a CSS Cube

    CSS cubes really showcase what CSS has become over the years, evolving from simple color and dimension directives to a language capable of creating deep, creative visuals.  Add animation and you've got something really neat.  Unfortunately each CSS cube tutorial I've read is a bit...

  • By
    CSS Filters

    CSS filter support recently landed within WebKit nightlies. CSS filters provide a method for modifying the rendering of a basic DOM element, image, or video. CSS filters allow for blurring, warping, and modifying the color intensity of elements. Let's have...

Incredible Demos

  • By
    Create Twitter-Style Buttons with the Dojo Toolkit

    I love that JavaScript toolkits make enhancing web pages incredibly easy. Today I'll cover an effect that I've already coded with MooTools: creating a Twitter-style animated "Sign In" button. Check out this five minute tutorial so you can take your static...

  • By
    AJAX For Evil:  Spyjax with jQuery

    Last year I wrote a popular post titled AJAX For Evil: Spyjax when I described a technique called "Spyjax": Spyjax, as I know it, is taking information from the user's computer for your own use — specifically their browsing habits. By using CSS and JavaScript, I...

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!