Never Force-Push Shared or Protected Branches

Never Force-Push Shared or Protected Branches | BeforeMerge Rules | BeforeMerge

Why this matters

A force-push rewrites history. On a shared or protected branch (main, dev, an open PR base) it discards or orphans commits other people already pulled, breaking their clones and CI. Rewrite only your own un-pushed/un-shared branches, and prefer --force-with-lease even then.

Bad

git push --force origin main

Good

# only on your own private feature branch:
git push --force-with-lease origin feature/my-branch

Why This Matters

Related Rules

Catch this automatically on every PR

Why this matters