Cheat Sheets · Git Cheat Sheet · Git Cherry Pick — Apply a Specific Commit Elsewhere

Git Cherry Pick — Apply a Specific Commit Elsewhere

git cherry-pick <sha>

Apply a single commit onto current branch

git cherry-pick <sha-1> <sha-2>

Apply multiple specific commits in sequence

git cherry-pick <old>..<new>

Apply a range of commits (exclusive of old)

git cherry-pick -n <sha>

Apply diff into working tree without committing (-n / --no-commit)

Cherry pick commands

CommandEffect
git cherry-pick <sha>Apply a single commit onto current branch
git cherry-pick <sha-1> <sha-2>Apply multiple specific commits in sequence
git cherry-pick <old>..<new>Apply a range of commits (exclusive of old)
git cherry-pick -n <sha>Apply diff into working tree without committing (-n / --no-commit)

Handling conflicts during cherry pick

CommandAction
git cherry-pick --continueResume cherry-pick after resolving conflicts and staging files
git cherry-pick --abortCancel cherry-pick and restore branch to pre-pick state
git cherry-pick --skipSkip the current problematic commit in a multi-commit pick

Cherry-picking copies the diff introduced by a specific commit from one branch and commits it directly onto your current branch with a new SHA.

Related Git recipes

Undo Last Commit — 3 Safe Ways Discard Local Changes — Safely and Completely Delete a Branch — Local and Remote Stash — Park Changes Without Committing Amend the Last Commit Undo a Pushed Commit — The Safe Way (git revert) Rename Local Branch — Safely & Quickly Rename Remote Branch — Complete 3-Step Process Squash Last N Commits — Combine Multiple Commits Sync Fork with Upstream — Step-by-Step Delete Remote Tag — Local and Remote Change Commit Author — Email & Name Unstage File — Remove from Staging Area Log Graph — Visual Commit History in Terminal Clean Untracked Files — Remove Clutter Safely Switch Branch — Modern Branch Navigation Create Branch from Commit — Branch Off History Stash Untracked Files (-u and -a Flags) Force Pull — Overwrite Local Changes with Remote Resolve Merge Conflict — Complete Workflow Show Commit — Inspect Changes in a Commit Tag a Release — Lightweight & Annotated Tags

FAQ

Does cherry-pick delete the commit from the original branch?
No. Cherry-pick duplicates the changes. The original commit stays completely untouched on its source branch.

Why does cherry-pick give a new commit SHA?
Because commit SHAs are hashes of their tree, message, timestamp, AND parent commit. Changing parents means a new SHA.

What if I cherry-pick an already merged commit?
Git detects an empty patch and prompts you to skip it with git cherry-pick --skip.

Stop memorizing — build it interactively

Try cherry-pick in the Git Builder

Full reference: Git Cheat Sheet