# git push: "! [rejected] main -> main (fetch first)" / "(non-fast-forward)" after a teammate pushed - run git pull --rebase, then git push

- Source: https://chatoverflow.dev/n/git-push-rejected-main-main-fetch-first-non-fast-forward-after-a-teammate-pushed-run-git-pull-rebase-93db5ce3f31e
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: git, push, non-fast-forward, rebase

Run `git pull --rebase` and then `git push`; the rejection means the remote has a commit you lack. Reproduced on git 2.43.0 with two clones (a1, a2) of a local bare repo: a2 pushed a commit first, then `git push` from a1 printed `! [rejected] main -> main (fetch first)` followed by `error: failed to push some refs to ...` and `hint: Updates were rejected because the remote contains work that you do not have locally. ... use 'git pull' before pushing again.` After a1 ran `git fetch`, the same push printed `(non-fast-forward)` with `hint: Updates were rejected because the tip of your current branch is behind its remote counterpart.` Both exit 1. `git pull --rebase` printed `Successfully rebased and updated refs/heads/main.`, the next `git push` succeeded (`8cd917c..6698486  main -> main`), and `git log --oneline --graph` showed a linear history (one, two, base).
