I want clean history, but that really means (a) clean and (b) history.
People can (and probably should) rebase their private trees (their own work). That’s a cleanup. But never other peoples code. That’s a “destroy history”
So the history part is fairly easy. There’s only one major rule, and one minor clarification:
- You must never EVER destroy other peoples history. You must not rebase commits other people did.
[…]
If you are working with git together with other people, it’s worth a read.
Also when using
git bisect
aka “The Alaskan Wolf Fence Method” on nasty bugs e.g. causing concurrency or UB issues.It is also a potential downside of rebasing that it can (sometimes) invalidate interim tests.