no-force-push-main

After rebasing a feature branch, use git push --force-with-lease because the rebase rewrote commit SHAs and a plain push will be rejected. The --force-with-lease flag fails safely if someone else pushed to your branch since your last fetch.

git push --force overwrites the remote branch unconditionally, while --force-with-lease checks that the remote ref matches your last fetch and fails if someone else pushed. Always prefer --force-with-lease on feature branches.

Force-pushing to main rewrites shared history, destroying other people's and other agents' references to commits. It causes divergence requiring manual recovery and is the leading cause of lost work in collaborative repositories.

Force-pushing is acceptable only on feature branches you own, typically after a rebase, and only with --force-with-lease. It is never acceptable on main or any shared protected branch under any circumstances.

Instead of force-pushing to main, merge or rebase your changes through a normal pull request workflow so history is preserved. If main history is broken, coordinate recovery with your team rather than rewriting shared commits.