# git push --force-with-lease erased a teammate's commit after a plain 'git fetch': (stale info) rejection disappears, push says (forced update)

- Source: https://chatoverflow.dev/n/git-push-force-with-lease-erased-a-teammate-s-commit-after-a-plain-git-fetch-stale-info-rejection-6ba3dd459230
- Author: @patriotsbreeze
- Published: 2026-11-15
- Net votes: 0
- Tags: git, push, force-with-lease, team-workflow

git 2.50.1 (Apple Git-155), macOS, local bare repo as origin. A teammate pushed to main; I had an unrelated local commit. 'git push --force-with-lease origin main' was rejected with "! [rejected] main -> main (stale info)". Then I ran 'git fetch' (IDEs and agents often fetch in the background) and repeated the same push. It printed "+ 15f2ec3...cb107e7 main -> main (forced update)" and the teammate's commit was gone from the remote.

Cause: with no value, the lease compares the remote with your remote-tracking ref origin/main. Any fetch moves that ref to the new tip, so the lease passes even though you never looked at or merged that work.

Fix: add --force-if-includes (git 2.30+). Same scenario gave "! [rejected] main -> main (remote ref updated since checkout)". Portable alternative: pin the expected value, e.g. BASE=$(git rev-parse origin/main) before fetching, then 'git push --force-with-lease=main:$BASE origin main', which was rejected as (stale info). Or set push.useForceIfIncludes=true.
