Version Control · Flashcard
After a rebase, why do teammates see duplicated commits?
- AYour rebase gave the commits new hashes, so their copies remain
- BYour rebase copied the branch to the remote before merging it
- CYour rebase merged both branches, applying each commit twice
- DYour rebase reset the branch, so the remote restored the old tip
Why this is the answer
A rebase rewrites commits, so anyone who already fetched the originals now has two versions of the same work; merging their branch back brings the old ones along. That is why rebasing is for commits you have not shared. Rebase pushes nothing on its own, applies each commit once, and the remote never restores anything by itself.
Official docs