Amending Commits

Amending replaces the most recent commit with a new one. The commit hash changes, but the branch pointer moves forward as if the old commit never existed.

This is meant for local, unpublished commits only.

To change only the last commit message:
Git opens the editor to modify the message.

If you forgot to include files in the last commit:
The new commit will include both old and new changes.

To keep the existing commit message:
Useful when:
• Fixing typos
• Adding missing files
• Minor corrections

Amending rewrites history. If the commit was already pushed:
• The remote history diverges
• Requires force push
• Can break teammates' work
Avoid amending pushed commits on shared branches.

• Use amend for small fixes to the latest commit
• Use a new commit for logical, standalone changes
Avoid amending pushed commits on shared branches.

• git commit --amend replaces the latest commit.
• Amending changes the commit hash.
• Safe only for local, unpushed commits.
• --no-edit keeps the existing message.
• Never amend commits already shared with others.