Introduction

If you committed on the wrong Git branch, the fix depends on whether the commit has already been pushed. Before pushing, you can usually move the commit cleanly with git switch, git cherry-pick, or git reset. After pushing, you should be more careful because history rewrites can affect other people.

If You Have Not Pushed Yet

A common clean fix is:

1. create or switch to the correct branch
2. move the commit there
3. remove it from the wrong branch if needed

For example, if the wrong branch has the commit at HEAD:

git switch -c correct-branch
git switch wrong-branch
git reset --hard HEAD~1

In collaborative work, avoid --hard unless you are certain you only want to remove your unpushed mistaken commit from that branch.

Use cherry-pick When You Need to Copy a Commit

If the correct branch already exists, copy the commit there.

git switch correct-branch
git cherry-pick <commit>

Then remove the commit from the wrong branch if appropriate.

This is often the clearest answer when you know exactly which commit should move.

Be More Careful If the Commit Was Already Pushed

Once the wrong-branch commit is pushed, rewriting branch history can disrupt teammates. In that situation, the safer answer is often to:

• cherry-pick the commit onto the right branch
• revert it on the wrong branch

That preserves shared history more safely than force-pushing a rewrite.

Common Pitfalls

• Using destructive reset commands without first checking whether the commit was pushed.
• Moving a commit to the correct branch but forgetting to remove or revert it on the wrong branch.
• Force-pushing rewritten history on a shared branch without coordination.
• Fixing the history mechanically without first deciding whether copy, move, or revert is the safer workflow.
• Panicking and running several Git commands before confirming the current branch and commit state.

Summary

• The right fix depends on whether the mistaken commit was pushed.
• For unpushed mistakes, moving or resetting is usually straightforward.
• 'git cherry-pick is the standard way to copy a commit to the correct branch.'
• For pushed commits, prefer safer history-preserving fixes such as revert plus cherry-pick.
• Check the branch and publication state before choosing the command sequence.