It is not standard workflow in git to change the commit history for a branch on the remote. You have to use --force
, and the next time someone pulls they also have to --force
their any local tracking branch to follow the remote. Every git guide on the internet warns against pushing a rebase for this reason.
Locally you can do whatever. I’m not familiar with Mercurial, but I assume it must work the same as git: I can do whatever I want locally, and only what I push matters. And when I’m doing stupid stuff locally as I organize my changes, rebase is handy.
I’m responding to the literal words you said that were inaccurate. Cheers.