描述有点简洁。我只是在我的本地 master 分支上添加了一个文件，然后将其推送回远程仓库。知道为什么会出现这种情况吗？

warning: updating the current branch
warning: Updating the currently checked out branch may cause confusion,
warning: as the index and work tree do not reflect changes that are in HEAD.
warning: As a result, you may see the changes you just pushed into it
warning: reverted when you run 'git diff' over there, and you may want
warning: to run 'git reset --hard' before starting to work to recover.
warning: 
warning: You can set 'receive.denyCurrentBranch' configuration variable to
warning: 'refuse' in the remote repository to forbid pushing into its
warning: current branch.
warning: To allow pushing into the current branch, you can set it to 'ignore';
warning: but this is not recommended unless you arranged to update its work
warning: tree to match what you pushed in some other way.
warning: 
warning: To squelch this message, you can set it to 'warn'.
warning: 
warning: Note that the default will change in a future version of git
warning: to refuse updating the current branch unless you have the
warning: configuration variable set to either 'ignore' or 'warn'.   

最佳答案

使用 Git 2.3.0(2015 年 2 月之后)

如果没有人在那个远程非裸仓库中工作，那么应该可以推送到已 checkout 的分支。

但为了在该操作中更加安全，您现在可以(使用 Git 2.3.0，2015 年 2 月)，在该远程仓库中执行以下操作:

git config receive.denyCurrentBranch updateInstead

它比配置 receive.denyCurrentBranch=ignore 更安全:只有当您没有覆盖正在进行的修改时，它才会允许推送。

参见 commit 1404bcb通过 Johannes Schindelin (dscho) :

receive-pack: add another option for receive.denyCurrentBranch

When synchronizing between working directories, it can be handy to update the current branch via 'push' rather than 'pull', e.g. when pushing a fix from inside a VM, or when pushing a fix made on a user's machine (where the developer is not at liberty to install an ssh daemon let alone know the user's password).

The common workaround – pushing into a temporary branch and then merging on the other machine – is no longer necessary with this patch.

The new option is:

updateInstead

Update the working tree accordingly, but refuse to do so if there are any uncommitted changes.

commit 4d7a5ce添加更多测试，并提到:

The previous one tests only the case where a path to be updated by the push-to-deploy has an incompatible change in the target's working tree that has already been added to the index, but the feature itself wants to require the working tree to be a lot cleaner than what is tested.

Add a handful more tests to protect the feature from future changes that mistakenly (from the viewpoint of the inventor of the feature) loosens the cleanliness requirement, namely:

• A change only to the working tree but not to the index is still a change to be protected;
• An untracked file in the working tree that would be overwritten by a push-to-deploy needs to be protected;
• A change that happens to make a file identical to what is being pushed is still a change to be protected (i.e. the feature's cleanliness requirement is more strict than that of checkout).

Also, test that a stat-only change to the working tree is not a reason to reject a push-to-deploy.

使用 Git < 2.3.0(2015="" 年="" 2="">

最常见的方法是从非裸仓库创建一个裸仓库，并将远程/本地非裸仓库指向新创建的裸仓库。

关于git - 将更改推送到远程存储库时，此 Git 警告消息是什么？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/804545/