Inicio > Git > Git Cherry-pick Guía rápida

Git Cherry-pick Guía rápida

Copy specific commits between branches when you need targeted fixes without merging everything.

What this cheat sheet is for

This git cherry-pick reference helps you complete common developer tasks quickly and avoid repeated trial-and-error when working under deadlines.

  • When you need a reliable command or pattern during debugging and incident response.
  • When you are implementing a feature and want a known-good syntax example immediately.
  • When onboarding teammates and documenting repeatable workflows for daily use.
  • When reviewing pull requests and verifying that command usage follows best practices.
  • Backport one bug fix from main to release branch.
  • Move a hotfix commit across environment branches.
  • Select only approved commits for a patch release.

Pick single or multiple commits

Cherry-pick one commit

git cherry-pick

Example:

git cherry-pick a1b2c3d d4e5f6g

Cherry-pick a range

git cherry-pick old^..new

Example:

git log --oneline

Handle conflicts

Continue after conflict resolution

git add .
git cherry-pick --continue

Example:

git cherry-pick --abort

Skip problematic commit

git cherry-pick --skip

Example:

git status

Audit picked commits

Show picked commit metadata

git show HEAD

Example:

git log --oneline --decorate

Append source reference

git cherry-pick -x

Example:

git log --grep="cherry picked"

Common mistakes / Errores comunes

  • Cherry-picking dependent commits without prerequisites can break builds.
  • Repeated cherry-picks across branches create duplicate commit history.
  • For large feature sync, merge or rebase is often cleaner than many picks.

Relacionado Guía rápidas

Last updated: February 2026