unrelated - git pull
git refusing to fetch into current branch (4)
I set up a remote repository and I can push new changes to it, but I cannot fetch from it, I always get the (rather cryptic) error message:
fatal: Refusing to fetch into current branch refs/heads/master of non-bare repository fatal: The remote end hung up unexpectedly
What does it mean? What should I do to enable fetching?
(Note that this remote repo is only used as a backup repo, so it should be pretty much an exact copy of my local repository. I really can't understand why I can push to it but not fetch from it...)
My config looks like:
[remote "origin"] url = ssh://blablablah fetch = +refs/*:refs/* mirror = true
Also this this should work if you are in master branch and wants to get latest try this
git pull origin master
Are you actually typing Git commands into the command line, or are you running the Git executable from your own code?
If you're running it from code, are you sure that Git is trying to fetch into the correct local directory?
There are two possible ways to do this:
Use the options provided by your programming language to set the correct working directory before executing Git
(C# example, because that's what I'm using)
Always pass the
-Cparameter to Git to specify the directory with the local repo.
I have a project where I'm calling the Git executable from C# code, and I got the same error message like in the question when I accidentally forgot to set the
I've had this problem when I thoughtlessly cloned a repository instead of fetching it, so that both repositories were masters. If you have done no work on the remote repository, you can fix things with the basic git commands as follows: (1) delete the remote repository, (2) copy the local repository to where the remote one was, (3) delete the local one, and then (4) set up the local repository using
git init; git fetch $REMOTE_GIT_REPOSITORY_URL
git pull and
git push will do the right things. The advantage of avoiding
git remote, per Michael's more efficient and principled answer, is that you don't need to think about the semantics of tracking branches.
In case anyone finds this because they specifically want to fetch into the current branch, you can use the
--update-head-ok flag. From the docs:
By default git fetch refuses to update the head which corresponds to the current branch. This flag disables the check. This is purely for the internal use for git pull to communicate with git fetch, and unless you are implementing your own Porcelain you are not supposed to use it.
In some cases we do want to implement our own porcelain commands, e.g., automation and tooling.