Git Cherry Pick instead of Git Merge

Git Cherry Pick is a powerful command. Git Merge brings in all the commits from a branch, but Git Cherry Pick only brings in your selected commits. In this video we will go through an example how you can use Git Cherry Pick to enhance your workflow.

Get started with Open Source in 10mins

## LEARN MORE

Also join our community GitHub organisation by creating an issue with the type "invite me to the organisation" :)

I now have a 2nd YouTube channel for short video clips of 60s or less, subscribe ...

## SERVICES I USE AND RECOMMEND

Some of these might be affiliate links, no extra cost you to, but I get a little $ if you sign up, plus you might get a discount too

## COMMUNITY SPONSORS

A BIG thank you to my GitHub Sponsors:
***
***

## FIND ME ON OTHER SOCIAL PLATFORMS

Don’t forget to support my channel by subscribing below, it’s free, and also share with your friends. Subscribe now!!

Follow on other socials for behind the scenes footage, join discord to continue the conversation...

Git Cherry Pick instead of Git Merge

[AllenKenney-gwfr]

Thank you! I wanted to know if cherry-picking would preserve the original commit hash from the feature branch or not, and this answered my quesiton. [No, it's a new commit hash]

[njong_emy]

I'm Thank you so much for the video Eddie 💜 very informative seconds!

[Hamstertron]

I find this useful for when you fix a bug on your branch to facilitate your work but need to release the bugfix before your feature is due for release. You can cherry-pick the fix into the release branch.

To avoid conflicts you can do an interactive rebase to remove the cherry-picked commit from feature, then rebase onto the source branch to pick up the change. Or just solve the conflict if it's not too horrible. The conflicts are the only downside to cherry-pick.