How to change git commit message after push (given that no one pulled from remote)

In Git, if you need to modify commit information that has already been pushed to a remote repository, several methods can be employed. However, note that this operation alters the commit history and should be used with caution, especially in collaborative projects with multiple contributors.

Method 1: Using git commit --amend followed by git push --force

This method applies to commits that have just been pushed and for which no other developers have based their work on since.

1. Modify the most recent commit message First, use the git commit --amend command in your local repository to modify the most recent commit message. Upon running this command, a text editor will open, allowing you to change the commit message.

   bash
   git commit --amend

2. Force push to the remote repository After modifying the commit message, since the remote repository history differs from the local one, use git push --force to push the local changes to the remote repository.

   bash
   git push --force

Method 2: Using git rebase -i for interactive rebase

If you need to modify commits that are not the most recent or multiple commits, you can use interactive rebase.

1. Start interactive rebase Assume you want to modify several previous commits; use the git rebase -i HEAD~n command (where n is the number of commits to rebase).

   bash
   git rebase -i HEAD~3

2. Select commits to modify In the opened editor, you will see the most recent n commits. Replace pick with reword (or simply r) for the commits you want to modify.

3. Modify commit messages For each commit marked as reword, the editor will open sequentially to allow you to modify the commit message.

4. Complete the rebase operation After making all modifications, save and close the editor. Git will apply the rebase.

5. Force push to the remote repository Finally, use git push --force to push the changes to the remote repository.

   bash
   git push --force

Important Considerations

• Communication and Collaboration: Before performing such operations, it's best to communicate with team members because modifying the remote repository history can affect others' work.
• Backup: Before using force push, ensure you have a backup of the current branch in case something goes wrong.