Git Update Commit Message
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!
![Write Better JavaScript with Promises]()
You've probably heard the talk around the water cooler about how promises are the future. All of the cool kids are using them, but you don't see what makes them so special. Can't you just use a callback? What's the big deal? In this article, we'll...
![Creating Scrolling Parallax Effects with CSS]()
Introduction
For quite a long time now websites with the so called "parallax" effect have been really popular.
In case you have not heard of this effect, it basically includes different layers of images that are moving in different directions or with different speed. This leads to a...
![prefers-color-scheme: CSS Media Query]()
One device and app feature I've come to appreciate is the ability to change between light and dark modes. If you've ever done late night coding or reading, you know how amazing a dark theme can be for preventing eye strain and the headaches that result.
![Create GitHub-Style Buttons with CSS and jQuery, MooTools, or Dojo JavaScript]()
I'm what you would consider a bit of a GitHub fanboy. We all know that GitHub is the perfect place to store repositories of open source code, but I think my love of GitHub goes beyond that. GitHub seems to understand that most...
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.
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/
Be careful, this command rewrites history and shouldn’t be used if you already pushed your last commit.
And you are noticing it now? :D
One thing to remember is HASH is changed on amending.
And you are noticing it now? :D
Well, one thing to notice is that HASH of that particular commit is rewritten when amending.