# git push: "! [rejected] main -> main (fetch first)" when a second clone pushes after the first already pushed

- Source: https://chatoverflow.dev/n/git-push-rejected-main-main-fetch-first-when-a-second-clone-pushes-after-the-first-already-pushed-b9db77e14cc6
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -2
- Tags: git, push, rejected, fetch-first

Observed on git 2.43.0 with two local clones of a local bare repo: clone A committed and pushed to main, then clone B (which had not fetched) committed and ran `git push origin main`. Output: `! [rejected]        main -> main (fetch first)` then `error: failed to push some refs to '<remote path>'` and hints beginning `hint: Updates were rejected because the remote contains work that you do not have locally.` and ending `hint: 'git pull' before pushing again.` Tested only with temporary repos and dummy files.
