Menu
When I do a git push, I see the following:
warning: updating the currently checked out branch; this may cause confusion,
as the index and working tree do not reflect changes that are now in HEAD.
I Googled for this message, and all I can find is a git mailing list discussion where the authors try to decide exactly how to make this message better to communicate to me what the real problem is.
How did I cause this, and how do I fix it?
768
Checking out branches Checking out a branch updates the files in the working directory to match the version stored in that branch, and it tells Git to record all new commits on that branch. Think of it as a way to select which line of development you're working on.
The git checkout - command lets you switch to the last branch you were on without actually typing the branch name. It's like the “last” button on your remote control. This can be a bit confusing, because earlier I told you that git checkout -b <branch-name> would create a new branch and switch you to that new branch.
This happens when you are pushing to a non-bare repo. A bare repo is one that consists solely of a .git directory; a non-bare repo also includes a checkout. In general, you should not push to a non-bare repo; in fact, in future version of git, that will be forbidden. If you push to a non-bare repo, then the HEAD of that repo will be out of sync with the index and the working copy.
If you're creating a repo that people are going to want to push to, then you should create it using git init --bare (and git init --bare --shared if several user accounts need access to it), or git clone --bare if you're creating it by cloning an existing repo.
123
In short, your remote repository is no longer a bare one, and you pushing on the remote checkout branch.
See "How to publish a Git repository":
A bare repository is one without a checked out working copy of the code. It only contains the git database.
As a general rule you should never push into a repository that contains changes in the working copy.
To ensure this doesn't happen, we're making the server repository a bare repository - it has no working copy
From here:
Note that the target of a "push" is normally a bare repository (i.e., with no work tree of its own).
You can also push to a repository that has a checked-out working tree, but the working tree
will not be updated by the push.
This may lead to unexpected results if the branch you push to is the currently checked-out branch.
If a detached work tree is defined (which can for instance correspond to a web server's DocumentRoot), you need to :
post-receive hook on your remote repository (like the one described here), running "git checkout -f" and git config receive.denycurrentbranch ignore)Check, on your remote repository, the value of git config core.worktree and git config core.bare
12
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
