Git Emergency

I amended a commit that was already pushed

Severity Annoying

What just happened

--amend replaced the pushed commit with a new one (new hash). Your local branch and the remote now have two different versions of the same commit.

Potential risks

  • Force pushing a shared branch breaks the copies of everyone who pulled.

Before you run anything

  • Is the branch yours alone (a feature branch)? Then a careful force push is fine.
  • Shared branch (main)? Don't rewrite: make a new commit instead.
  • Golden rule: before any destructive command, create a safety branch with git branch backup/before-fix — it costs nothing.

Recovery steps

  1. 1

    See both versions

    Your amended commit vs the one on the remote.

    Safe
    $ git fetch origin
    $ git log --oneline --graph HEAD origin/my-branch -n 5
  2. 2

    Your own branch: push the amended version

    --force-with-lease refuses if someone else pushed in the meantime.

    Destructive
    $ git push --force-with-lease
  3. 3

    Shared branch: turn the amend into a normal commit

    Go back to the remote version while keeping your changes, then commit them on top.

    Caution
    $ git reset --soft origin/main
    $ git commit -m "fix: what the amend was for"
    $ git push

These procedures are provided for information only. Read each command and adapt it to your situation before running it. Disclaimer

Other disasters

🪓 I deleted my branch🚨 I pushed directly to main💥 I ran git reset --hard🧨 I overwrote a colleague's commits🔑 I pushed my .env file to GitHub🔀 I made a bad merge👻 I lost uncommitted changes🎯 I committed on the wrong branch🎈 I'm in “detached HEAD” state⚔️ I'm stuck in a merge conflict🚫 My push is rejected (non-fast-forward)🌀 My rebase went wrong🐘 GitHub rejects a file over 100 MB🥸 I committed with the wrong name or email🗑️ I deleted a file and committed it⏪ I want to undo my last commit🧹 Too many messy commits to clean up📮 I pushed to the wrong branch🧭 I rebased onto the wrong branch🔁 I need back the changes I reverted📦 git stash pop gave me a conflict🙈 I committed a file that should be ignored🔠 Git doesn't see my file rename (upper/lower case)🧨 I ran git clean -fd by mistake🩻 My repository is corrupted🙃 I forgot to pull before pushing👯 Duplicated lines of code after a merge➖ I added a file I didn't want to (git add)✏️ I made a typo in a commit message✂️ My commit does too many things🧺 I lost a stash (drop, clear or pop gone wrong)🫥 I pulled and my code disappeared🍒 I cherry-picked the wrong commit☁️ I deleted a branch on GitHub / GitLab👥 I pushed with the wrong GitHub account🚚 The repository was renamed or moved🏷️ I tagged the wrong commit🌊 Git says every file is modified, but I changed nothing📦 I committed node_modules (or a build folder)📂 I ran git init in the wrong folder🧨 My pull request has conflicts⏳ My pull request is behind main📝 I have to apply review changes to my PR🧳 My PR shows commits that aren't mine🎯 I opened my PR against the wrong branch🚨 A merged PR broke main🚪 I closed my PR (or deleted its branch) by mistake🔴 The checks of my PR are failing🐘 My PR is too big to review🍴 My fork is behind the original repository