Skip to main content
Cherry-picking is a powerful Git technique that allows you to apply a specific commit from one branch onto another without merging all the changes from the source branch. This method is especially useful when you need an isolated change from another branch without incorporating all of its commits.

​
When to Use Cherry-Picking

If you’re working on the master branch and identify a single commit in a feature branch (for example, the Sarah branch) that introduces a vital fix or enhancement, cherry-picking enables you to import that specific change without merging the entirety of the feature branch.
Before proceeding with cherry-picking, ensure that your target branch is up-to-date and that you understand how the changes from the commit will integrate with your current code base.

​
How to Cherry-Pick a Commit

To cherry-pick a commit, you’ll use the commit’s unique hash value. In the scenario where you wish to apply the changes from a commit on the Sarah branch to your master branch, follow these steps:
  1. Switch to your master branch.
  2. Execute the cherry-pick command with the hash of the desired commit.
Below is an example command to cherry-pick the commit with the hash aaba5: 
$ git cherry-pick aaba5
After running this command, the changes introduced in that specific commit will be applied to your current branch (master).
Cherry-picking only transfers the changes from the specified commit. Other commits and modifications from the source branch remain separate.

​
Summary

Cherry-picking is an essential Git strategy for applying targeted changes across branches. It streamlines the process of integrating critical updates from one branch to another without merging entire branches. For a deeper dive into Git commands and workflows, consider exploring the official Git documentation. Happy coding!

Watch Video

Practice Lab