Home/ Questions/Q 4121134
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T23:18:43+00:00

I made a mistake with my git repositories(edited files from the main one), and

  • 0

I made a mistake with my git repositories(edited files from the “main” one), and I had to use “git push -f” to force my “main” repository to accept my local revision. I went back to my remote main repository and did a git status.

I see that the changes to be committed are old and do not reflect my actual local repository status (the one that pushed -f). So, if I do a git commit on the main, it works fine, but the two repositories differ.

The situation is not resolved since a new standard git push shows an error:

 ! [rejected]        master -> master (non-fast-forward)

How can this be resolved so that my main repos has the same content as my local copy ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should normally not do a git push to a non-bare repository, i.e. a repository which has a working copy attached. The reason is that git push does not update the working directory (it can’t reliably do this), and thus either the HEAD gets out of sync with its branch, or out of sync with its working copy.

    If you want to push to some repository, let this be a bare repository without working copy. Otherwise, use fetch and pull to get the changes to your repository (used at this repository itself).

    • 0