0
I understand why developers like a tidy commit history, but I’m less sure when rebasing is safe on a branch that other people have already pulled. If one person rewrites the branch and pushes it, teammates can end up with duplicate-looking commits or confusing histories.
How does your team decide whether to rebase a shared branch or merge changes instead? I’d like to hear what rules work in practice, especially for a small team that reviews feature branches before they reach the main branch.
