Fix incorrect Git Comments

Fix incorrect Git Comments


In software development, using Git for version control is ubiquitous. However, even the most seasoned developers can sometimes make a typo or leave out crucial information in a commit message. Fortunately, Git offers a straightforward way to fix these mistakes. This article provides a comprehensive guide on how to amend Git commit messages.

Why Amend Commit Messages?

Amending commit messages is essential for maintaining a clear and accurate project history. Whether it’s correcting typos, adding missing details, or clarifying the purpose of the commit, a well-crafted commit message is invaluable for team collaboration and future reference.

Amending the Most Recent Commit

Step 1: Identifying the Commit

First, ensure that the commit you want to amend is the most recent. If it’s not, you’ll need a different approach, which we’ll cover later.

Step 2: The Amend Command

Use the git commit --amend command. This command opens your commit in the default text editor set for Git, allowing you to modify the message.

git commit --amend

Step 3: Editing the Message

  • In the text editor, simply edit the commit message.
  • Save and close the editor to apply the changes.

Step 4: Pushing the Amended Commit

If you haven’t pushed the original commit to the remote repository, just perform a regular push:

git push

You must force-push the amended commit if you’ve already pushed the initial commit. Be cautious, as this can overwrite changes in the remote repository:

git push --force

Amending Older Commits

Step 1: Interactive Rebase

For older commits, you’ll need to use git rebase in interactive mode (-i). Start by specifying how far back in history you want to go with a commit hash or by counting back the commits (e.g., HEAD~3 for the last three commits).

git rebase -i HEAD~3

Step 2: Marking the Commit for Amending

  • You’ll see a list of commits in the text editor that opens.
  • Find the commit you want to change and replace pick with reword.
  • Save and close the editor.

Step 3: Amending the Message

  • Git will now re-open the commit in the text editor.
  • Edit the commit message, save, and close the editor.

Step 4: Completing the Rebase

  • Once the rebase is complete, push the changes to the remote repository.
  • If these commits were already pushed, you’d need to force push:

git push --force

Best Practices and Warnings

Collaboration Caution

  • Amending and force-pushing commits shared with others can cause confusion and merge conflicts. It’s best to avoid amending pushed commits in collaborative projects unless necessary.

Commit Integrity

  • Remember that amending a commit replaces it with a new commit with a different ID. This changes the project’s history.


  • Before performing operations like interactive rebase or force push, it’s a good idea to create a backup branch.


Amending Git commit messages is a handy skill that helps keep your project history clear and meaningful. For recent commits, the process is simple and straightforward. For older commits, interactive rebase is a powerful tool, but it should be used cautiously, especially in collaborative environments. By following these steps and best practices, you can ensure that your project’s history reflects accurate and helpful information.


Hi, my name is Stephen Finchett. I have been a software engineer for over 30 years and worked on complex, business critical, multi-user systems for all of my career. For the last 15 years, I have been concentrating on web based solutions using the Microsoft Stack including ASP.Net, C#, TypeScript, SQL Server and running everything at scale within Kubernetes.