Day 1: You push commits C, D, E to origin/main
        teammates pull and get C, D, E

Day 2: You decide to "clean up history" with git rebase
        New commits C', D', E' are created (different hashes)
        Old commits C, D, E are now orphaned on your machine

Day 3: You force-push origin/main = C', D', E'
        Now origin/main has different history than what teammates have

Day 4: Teammates pull. They have C, D, E. The remote has C', D', E'.
        Their git pull tries to MERGE the two divergent histories.
        Conflicts everywhere. Duplicate commits in their work.
        Everyone loses a day untangling it.

# 1. Confirm only YOU have this branch
git branch -r --contains HEAD
# Should show: origin/your-branch (and maybe nothing else)

# 2. Check if anyone has pulled this branch recently
# (look at PR history, ask in chat)

# 3. If safe → rebase
git rebase main

# 4. Force-push WITH SAFETY
git push --force-with-lease

git push --force-with-lease

# Old, dangerous form:
git push --force
# (no safety check; can erase other people's work)

# Their next 'git pull' produces conflicts
# They can:

# Option 1: Rebase their local commits onto the new remote history
git fetch origin
git rebase origin/main

# Option 2: Reset their branch to match the remote (DESTRUCTIVE for them)
git reset --hard origin/main

# Option 3: Recover from reflog if work was lost
git reflog
git reset --hard HEAD@{pre-disaster-state}