Why cherry-pick is useful in Git - Visual Breakdown

Process Flow - Why cherry-pick is useful

Start on branch A

↓

Make commit X on branch A

↓

Switch to branch B

↓

Cherry-pick commit X onto branch B

↓

Commit X changes appear on branch B

↓

Branches A and B have commit X independently

Cherry-pick copies a specific commit from one branch to another without merging all changes, letting you pick only what you want.

Execution Sample

Git

git checkout branchA
# make commit X

git checkout branchB
git cherry-pick <commit-hash-of-X>

This copies commit X from branchA to branchB without merging all branchA changes.

Process Table

Step	Action	Branch	Commit History	Result
1	Start on branchA	branchA	A1 -> A2	Ready to make new commit
2	Make commit X	branchA	A1 -> A2 -> X	Commit X added to branchA
3	Switch to branchB	branchB	B1 -> B2	On branchB, no commit X yet
4	Cherry-pick commit X	branchB	B1 -> B2 -> X'	Commit X copied to branchB as X'
5	Check commit histories	branchA & branchB	branchA: A1 -> A2 -> X branchB: B1 -> B2 -> X'	Both branches have commit X independently

💡 Cherry-pick ends after commit X is copied to branchB without merging full branchA

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
branchA commits	A1 -> A2	A1 -> A2 -> X	A1 -> A2 -> X	A1 -> A2 -> X
branchB commits	B1 -> B2	B1 -> B2	B1 -> B2 -> X'	B1 -> B2 -> X'

Key Moments - 2 Insights

Why does cherry-pick create a new commit X' instead of reusing X?

Cherry-pick copies the changes but creates a new commit with a different ID on the target branch, as shown in step 4 of the execution_table.

Does cherry-pick merge all changes from branchA to branchB?

No, cherry-pick only copies the selected commit (X) without merging the entire branch, as seen in step 4 where only commit X is added to branchB.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what happens to branchB's commit history?

A BranchB merges all commits from branchA

B Commit X is removed from branchB

C Commit X is added as a new commit X' on branchB

D BranchB stays unchanged

💡 Hint

Check the 'Commit History' column at step 4 in the execution_table

At which step does branchA get commit X?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Commit History' for branchA after each step in the execution_table

If you cherry-pick multiple commits, how would the variable_tracker for branchB change?

A branchB commits would be reset to branchA commits

B branchB commits would include all cherry-picked commits in order

C branchB commits would only have the last cherry-picked commit

D branchB commits would not change

💡 Hint

Variable_tracker shows commits added step by step; multiple cherry-picks add commits sequentially

Concept Snapshot

git cherry-pick <commit>
Copies a single commit from another branch
Creates a new commit with same changes
Does not merge full branch history
Useful to pick specific fixes or features

Full Transcript

Cherry-pick lets you copy one commit from a branch to another without merging everything. You start on branchA and make a commit X. Then you switch to branchB and run cherry-pick with commit X's ID. This adds a new commit X' to branchB with the same changes. Both branches now have commit X independently. Cherry-pick creates a new commit ID because it applies the changes fresh on the target branch. It is useful when you want just one fix or feature from another branch without merging all its changes.