Why Git won’t let you push to non-bare repositories The original poster says: One solution is to run the following command: git config receive.denyCurrentBranch ignore After this it works, but I would like to know why I need to use this option. Is this the only option? What are the consequences of doing this? As … Read more
For those who found this searching for an answer to fatal: ‘origin/remote-branch-name’ is not a commit and a branch ‘local-branch-name’ cannot be created from it, you may also want to try this first: git fetch –all If you run git checkout -b local-branch-name origin/remote-branch-name without fetching first, you can run into that error. The reason … Read more
Best Option Probably the cleanest, least confusing, and safest way to push into your non-bare remote repository, is to push to dedicated branches in the remote that represent your laptop branches. Let’s look at the simplest case, and assume you have just one branch in each repo: master. When you push to the remote repo … Read more
In short: replace the contents of repo with the contents of repo/.git, then tell the repository that it is now a bare repository. To do this, execute the following commands: cd repo mv .git ../repo.git # renaming just for clarity cd .. rm -fr repo cd repo.git git config –bool core.bare true Note that this … Read more
Just do: git push origin <your_branch_name> –force or if you have a specific repo: git push https://git…. –force This will delete your previous commit(s) and push your current one. It may not be proper, but if anyone stumbles upon this page, thought they might want a simple solution… Short flag Also note that -f is … Read more