JIYIK CN >

When working in Git, we want to integrate a specific single commit from one branch into our current HEADbranch. This could be because a customer wants some changes to the product or any reported bugs.

Either we committed it by mistake, or we don't want it in our previous branch anymore and want it in our current HEADbranch instead.

The answer to the above question is CHERRY PICK. Therefore, in the next section, we will discuss cherry-pickthe command in detail.

Copy commits from another branch in Git

Extracting a specific commit from one branch and copying it into our current HEADbranch is called cherry picking.

Git has a specific command for this, the git- cherry-pickcherry-picking command. Another use of cherry-picking is to apply specific changes before we merge or develop a pull request.

This is useful for undoing changes.

This article will discuss cherry-picking a specific commit from one branch to another.

Use git logthe command to view the commit

First, we'll use git logto investigate the commit we want to select. Here are git logthe branch results from the command:

d23216 - 953222	- 953219 - aa3s36 - 532d37 [master]
           \
            76cada - 66ecb3	- b886a0 [feature]

In featurethe branch, there is a commit from another branch 66ecb3that we only want in our masterbranch.

Let's cherry-pick that particular commit and move it to our current branch, masterthe branch. We can then use that commit changes for our project in the future.

Run git cherry-pickthe command to copy the commit

Here, git cherry-pickwill help us. 66ecb3is the cherry, we want to pick it from the huge number of pushes that have been done in the past.

Let's pick it from another branch by running the following command.

git checkout master
git cherry-pick 66ecb3

Once the commands listed above run successfully, 66ecb3will now be available as a new commit in our master branch.

So Git copies the commit we need, mastercontaining the same commit message and changes on the branch. Finally, a new commit is created with a new ID.

Use git resetthe command to clean up other branches

If we switch to featurethe branch, we'll see the same commit in its old location. This is because Git has copied it to another branch instead of moving it.

It does not touch the original branch.

Now, to clean up and undo, we will use the command after checking out the desired branch git reset.

$ git checkout Test
Switched to branch 'Test'
$ git reset --hard HEAD~1
HEAD is now at 66ecb3 Change the title and delete the error page