Why might cherry-picking multiple commits cause duplicate commits in history, and how can this be avoided?

hard📝 Conceptual Q10 of 15

Git - Cherry-Pick and Advanced Merging

ABecause cherry-pick deletes original commits; avoid by using reset

BBecause cherry-pick rewrites commit hashes; avoid by rebasing instead

CBecause cherry-pick creates new commits; avoid by merging branches instead

DBecause cherry-pick merges branches; avoid by using revert

Step-by-Step Solution

Solution:

Step 1: Understand cherry-pick commit creation
Cherry-pick applies commits by creating new commits with new hashes, duplicating changes in history.
Step 2: Avoid duplication by merging
Merging branches preserves commit history without duplication, avoiding duplicate commits.
Final Answer:
Because cherry-pick creates new commits; avoid by merging branches instead -> Option C
Quick Check:
Cherry-pick duplicates commits; merge to avoid [OK]

Quick Trick: Cherry-pick duplicates commits; merge to keep history clean [OK]

Common Mistakes:

Master "Cherry-Pick and Advanced Merging" in Git

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Git Quizzes