blocks|key|1228473|text|这就完成了我的工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1228474|git+gc+--prune=now|code-block|syntax|javascript|1228475|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This did the job for me:

<pre><code>git gc --prune=now
</code></pre>

blocks|key|1013969|text|我遇到了同样的问题，并通过转到它出错的文件来解决它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1013970|\repo\.git\refs\remotes\origin\master|code-block|syntax|javascript|1013971|这个文件全是空的，我用来自github的最新引用替换了它。|1013972|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had this same issue and solved it by going to the file it was erroring on:

<pre><code>\repo\.git\refs\remotes\origin\master
</code></pre>

This file was full of nulls, I replaced it with the latest ref from github.

blocks|key|1228579|text|也发生在我身上。在我的例子中，糟糕的裁判是master，我做了以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1228580|rm+.git/refs/remotes/origin/master
git+fetch|code-block|syntax|javascript|1228581|这使得git恢复了ref文件。在那之后，一切都像预期的那样工作。|1228582|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Happened to me as well. In my case, the bad ref was master, and I did the following:

<pre><code>rm .git/refs/remotes/origin/master
git fetch
</code></pre>

This made git restore the ref file. After that everything worked as expected again.

blocks|key|1014096|text|对于我来说，我有一个名为feature/phase2的本地分支和一个名为feature/phase2/data-model的远程分支。命名冲突是问题的原因，所以我删除了我的本地分支(如果它有任何需要保留的东西，可以重命名)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1014097|entityMap^0|C|E|10|P|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

For me, I had a local branch named <code>feature/phase2</code> and the remote branch was named <code>feature/phase2/data-model</code>. The naming conflict was the cause of the problem, so I deleted my local branch (you could rename it if it had anything you needed to keep)

blocks|key|1228705|text|对我来说，它的工作是从文件夹.git/refs/remotes/origin/中删除抛出错误的文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1228706|entityMap^0|E|P|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

For me, it worked to remove the files that are throwing errors from the folder <code>.git/refs/remotes/origin/</code>.

blocks|key|1014218|text|我在composer更新时也遇到了同样的问题。但对我来说，它只在我清除作曲家缓存和删除供应商文件夹的内容后才起作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1014219|rm+-rf+vendor/*
git+gc+--prune=now
git+pull
composer+clear-cache
composer+update+my/package|code-block|syntax|javascript|1014220|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had the same problem with composer update. But for me it only worked after I cleared the composer cache and after deleting the content of the vendor folder:

<pre><code>rm -rf vendor/*
git gc --prune=now
git pull
composer clear-cache
composer update my/package
</code></pre>

blocks|key|1228818|text|我能够和我一起|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1228819|git+remote+update+--prune|code-block|syntax|javascript|1228820|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I was able to work with 

<pre><code>git remote update --prune
</code></pre>

blocks|key|1014295|text|我也有同样的问题。我遵循以下步骤|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1014296|1)将发生问题的分支切换到其他分支|1014297|2)删除该分支|1014298|3)再次结帐。|1014299|注意：-您可以隐藏未提交的更改，然后再将其放回原处。|1014300|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I had same issue. i follow following steps 

1)switch your branch which having issue to other branch 

2) delete that branch 

3) checkout again.

Note:- You can stash you uncommitted changes and put it back again.

blocks|key|1014364|text|在尝试从git+bundle创建的文件克隆时遇到此问题，其他答案都不起作用，因为我无法克隆存储库(所以git+gc和删除/编辑文件是不可能的)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1014365|然而，还有另一种方法来解决这个问题--+.bundle文件的源文件以如下开头：|1014366|#+v2+git+bundle
9a3184e2f983ba13cc7f40a820df8dd8cf20b54d+HEAD
9a3184e2f983ba13cc7f40a820df8dd8cf20b54d+refs/heads/master
9a3184e2f983ba13cc7f40a820df8dd8cf20b54d+refs/heads/master

PACK.......p..x...Kj.0...:+(and+so+on...)|code-block|syntax|javascript|1014367|只需用vim删除第四行就解决了这个问题。|1014368|entityMap^0|4|A|1F|6|0|K|7|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

Got this issue when trying to clone from a <code>git bundle</code> created file, none of the other answers worked because I couldn't clone the repo (so <code>git gc</code> and removing/editing files was out of the question).

There was however another way to fix this - the source file of a <code>.bundle</code> file was begining with:

<pre><code># v2 git bundle
9a3184e2f983ba13cc7f40a820df8dd8cf20b54d HEAD
9a3184e2f983ba13cc7f40a820df8dd8cf20b54d refs/heads/master
9a3184e2f983ba13cc7f40a820df8dd8cf20b54d refs/heads/master

PACK.......p..x...Kj.0...: (and so on...)
</code></pre>

Simply removing the fourth line with vim fixed the issue.

blocks|key|1014449|text|简而言之，当你的本地有一些关于遥控器的信息，并且有人更改了一些东西，使得遥控器和你的更改不同步时，就会出现这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1014450|我得到这个问题是因为有人删除了远程分支，并使用相同的名称再次创建。|1014451|要处理此类问题，请从远程执行一次pull或fetch。|1014452|git+remote+prune+origin|code-block|syntax|javascript|1014453|或者，如果您使用的是任何GUI，则执行从远程获取。|1014454|​|1014455|📷|atomic|offset|length|1014456|1014457|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/3a7c585e97049523e680e26e623a3482.png|imageAlt^0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|16|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|19|8|@]|9|@$R|1A|S|1B|1|1C]]|A|$]]|$1|T|3|N|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]]]

To Answer this in very short, this issue comes when your local has some information about the remote and someone changes something which makes remote and your changes unsync. 

I was getting this issue because someone has deleted remote branch and again created with the same name.

For dealing with such issues, do a pull or fetch from remote.

<pre><code>git remote prune origin
</code></pre>

or if you are using any GUI, do a fetch from remote.

<a href="https://i.stack.imgur.com/MhlrQ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/MhlrQ.png" alt="enter image description here"></a>

blocks|key|1229066|text|我在使用SourceTree时遇到了这个问题。我试着再拉一次，它成功了。我想我切换分支(结账)太快了:)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229067|我的情况与发帖者的略有不同，因为我的存储库一直相对合作，没有任何明显的损坏。|1229068|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had this issue while using SourceTree. I tried to pull again and it worked. I think I Was witching branches (checkout) too fast :).

My situation is a bit different from the poster's because my repository has been relatively cooperative, without any apparent corruption.

blocks|key|1014554|text|在我的例子中，这个问题在我删除了.git目录下的所有删除引用文件之后就解决了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1014555|如果您查看该消息，它会告诉您需要删除哪些文件(特别是)。|1014556|要删除的文件位于.git/refs/remotes下。|1014557|我刚刚删除了那里的所有文件，并运行了gc+prune|1014558|git+gc+--prune=now|code-block|syntax|javascript|1014559|在那之后，一切都很好。|1014560|entityMap^0|G|4|0|0|8|H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|11|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|12|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|13|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|T|$]]

In my case, the problem was solved after I've deleted all the remove reference files under the directory <code>.git</code>.

If you look at the message, it would tell you which files you need to delete (specifically).

The files to delete sit under <code>.git/refs/remotes</code>.

I've just deleted all the files there, and ran gc prune

<pre><code>git gc --prune=now
</code></pre>

After that, everything works just fine.

blocks|key|1229146|text|有相同的msg，但有一个目录，在拉入时得到失败的msg。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229147|git+--prone对我也没什么帮助。原来有一个与远程创建的目录同名的文件。|1229148|我不得不去.git\logs\refs\remotes\origin并清除语言环境文件--然后再拉一次，一切正常。|1229149|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Had the same msg but with a directory, got a failed msg on pull.

git --prone did not help me either.
Turns out there was a file with the same name as a directory created remotely.

Had to go to .git\logs\refs\remotes\origin and erase the locale file - then pull again, all good.

blocks|key|1229178|text|如果git+gc+--prune=now不帮你。(像我一样倒霉)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1229179|我所做的是在本地删除项目，然后重新克隆整个项目。|1229180|entityMap^0|2|I|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

If <code>git gc --prune=now</code> dosen't help you. (bad luck like me)

What I did is remove the project in local, and re clone the whole project again.

blocks|key|1229219|text|试试这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229220|git+pull+origin+Branch_Name|code-block|syntax|javascript|1229221|Branch_Name，您当前所在的分支。|offset|length|style|CODE|1229222|如果您只执行一个git+pull，它也会拉取所有其他创建的分支名称。|1229223|这就是你得到这个的原因：|1229224|!+[new+branch]++++++split-css++->+origin/split-css++(unable+to+update+local+ref)|1229225|entityMap^0|0|0|0|B|0|8|8|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@$I|10|J|11|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

Try this:

<pre><code>git pull origin Branch_Name
</code></pre>

<code>Branch_Name</code>, the branch which you are currently on.

If you do only a <code>git pull</code>, it pulls all other created branch name as well.

So is the reason you are getting this:

<pre><code>! [new branch] split-css -&gt; origin/split-css (unable to update local ref)
</code></pre>

blocks|key|1014671|text|git+fetch+--prune为我修复了这个错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1014672|[marc.zych@marc-desktop]+-+[~/code/driving]+-+[Wed+May+10,+02:58:25]
[I]>+git+fetch
error:+cannot+lock+ref+'refs/remotes/origin/user/janek/integration/20170505':+'refs/remotes/origin/user/janek/integration'+exists;+cannot+create+'refs/remotes/origin/user/janek/integration/20170505'
From+github.com:zooxco/driving
+!+[new+branch]++++++++++++user/janek/integration/20170505+->+origin/user/janek/integration/20170505++(unable+to+update+local+ref)
From+github.com:zooxco/driving
[marc.zych@marc-desktop]+-+[~/code/driving]+-+[Wed+May+10,+02:58:30]
[I]>+git+fetch+--prune
+-+[deleted]+++++++++++++++(none)+++++->+origin/user/janek/integration|code-block|syntax|javascript|1014673|但是，这假设在远程服务器上删除了违规分支。|1014674|您还可以将其添加到~/.gitconfig，以便在运行git+fetch时自动修剪|1014675|[fetch]
++++prune+=+true|1014676|entityMap^0|0|H|0|0|0|9|C|R|9|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|P|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

<code>git fetch --prune</code> fixed this error for me:
<pre><code>[marc.zych@marc-desktop] - [~/code/driving] - [Wed May 10, 02:58:25]
[I]&gt; git fetch
error: cannot lock ref 'refs/remotes/origin/user/janek/integration/20170505': 'refs/remotes/origin/user/janek/integration' exists; cannot create 'refs/remotes/origin/user/janek/integration/20170505'
From github.com:zooxco/driving
 ! [new branch] user/janek/integration/20170505 -&gt; origin/user/janek/integration/20170505 (unable to update local ref)
From github.com:zooxco/driving
[marc.zych@marc-desktop] - [~/code/driving] - [Wed May 10, 02:58:30]
[I]&gt; git fetch --prune
 - [deleted] (none) -&gt; origin/user/janek/integration
</code></pre>
This assumes that the offending branch was deleted on the remote, though.
You can also add this to <code>~/.gitconfig</code> to automatically prune when running <code>git fetch</code>:
<pre><code>[fetch]
 prune = true
</code></pre>

blocks|key|1014694|text|+#+remove+the+reference+file+of+the+branch+"lost"
+rm+-fv+./.git/refs/remotes/origin/feature/v1.6.9-api-token-bot-reader

+#+get+all+the+branches+from+the+master
+git+fetch+--all

+#+git+will+"know"+how-to+handle+the+issue+from+now+on
+#+++++From+github.com:futurice/senzoit-www-server
+#+*+[new+branch]++++++feature/v1.6.9-api-token-bot-reader+->
+#+origin/feature/v1.6.9-api-token-bot-reader

+#+and+push+your+local+changes
+git+push|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1014695|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code> # remove the reference file of the branch "lost"
 rm -fv ./.git/refs/remotes/origin/feature/v1.6.9-api-token-bot-reader

 # get all the branches from the master
 git fetch --all

 # git will "know" how-to handle the issue from now on
 # From github.com:futurice/senzoit-www-server
 # * [new branch] feature/v1.6.9-api-token-bot-reader -&gt;
 # origin/feature/v1.6.9-api-token-bot-reader

 # and push your local changes
 git push
</code></pre>

blocks|key|1229318|text|今天才碰到这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229319|故障排除方法:在Windows服务器上使用SourceTree，您可以尝试以管理员身份运行它。这解决了我在域中的Windows+Server+2012+R2上的Atlassian+Source+Tree+2.1.2.5上“无法更新本地ref”的问题。|1229320|如果您也可以复制这种情况，这证明了问题是由权限问题引起的。最好深入研究并找出根本原因--可能某些特定的文件归其他用户所有等等--否则会有一个不受欢迎的副作用:您将不得不以管理员身份运行SourceTree。|1229321|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Just ran into the problem today.

Troubleshooting method:
With SourceTree on Windows Servers, you may try to run it as an Administrator. That fixes my problem of "unable to update local ref" on Atlassian Source Tree 2.1.2.5 on a Windows Server 2012 R2 in domain.

If you can too replicate this situation, it proves that the problem is caused by permission issue. It's better to drill down and find the root cause - probably some particular files are owned by other users and such - otherwise there's an unwelcome side-effect: you'll have to run SourceTree as Administrator for the rest of eternity.

blocks|key|1229350|text|我使用了git+prune+origin，它完成了这项工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1229351|entityMap^0|4|G|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I used <code>git prune origin</code> and that did the work.

blocks|key|1014814|text|写下一个可能导致这个问题的具体案例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1014815|有一天，我推送了一个名为"feature/subfeature“的分支，而"feature”分支位于远程。|1014816|该操作运行良好，我这边没有任何错误，但当我的同事获取和/或拉出任何分支时，他们都有完全相同的错误消息unable+to+update+local+ref，cannot+lock+ref+'refs/remotes/origin/feature/subfeature。|offset|length|style|CODE|1014817|解决方法是删除remote(git+push+--delete+origin+feature)上的feature分支，然后在我同事的存储库上运行git+remote+prune+origin，这会生成包括*+[pruned]+origin/feature在内的消息。|1014818|所以，我猜测git+fetch试图在git上的feature文件夹(.git/...)中创建subfeature引用，但是创建文件夹失败了，因为已经有feature引用了。|1014819|entityMap^0|0|0|1E|Q|25|1J|0|E|W|1D|7|20|N|2U|P|0|6|9|N|7|1A|A|23|7|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@$F|S|G|T|H|I]|$F|U|G|V|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@$F|X|G|Y|H|I]|$F|Z|G|10|H|I]|$F|11|G|12|H|I]|$F|13|G|14|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@$F|16|G|17|H|I]|$F|18|G|19|H|I]|$F|1A|G|1B|H|I]|$F|1C|G|1D|H|I]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|O|$]]

Writing down a specific case that might cause this problem.

One day I pushed a branch named "feature/subfeature", while having "feature" branch on remote.

That operation worked fine without any error on my side, but when my co-workers fetched and/or pulled any branch, they all had the exact same error message <code>unable to update local ref</code>, <code>cannot lock ref 'refs/remotes/origin/feature/subfeature</code>.

This was solved by deleting <code>feature</code> branch on remote(<code>git push --delete origin feature</code>) and then running <code>git remote prune origin</code> on my co-workers' repo, which generated messages including <code>* [pruned] origin/feature</code>.

So, my guess is <code>git fetch</code> was trying to create <code>subfeature</code> ref in <code>feature</code> folder on git internally(.git/...), but creating folder failed because there was <code>feature</code> ref already.

blocks|key|1229410|text|试试看：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229411|git+gc+--prune=now

git+remote+prune+origin

git+pull|code-block|syntax|javascript|1229412|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Try it:

<pre><code>git gc --prune=now

git remote prune origin

git pull
</code></pre>

blocks|key|1229476|text|当Mac上的开发人员创建了一个分支名称中包含大于">“符号的分支时，我们遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229477|这在TeamCity和运行SourceTree的本地Windows型计算机上造成了问题。BitBucket毫不费力地让它通过了。|1229478|若要解决此问题，请删除该分支并重新创建它。这很好也很简单。|1229479|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

We got this issue when a developer on Mac created a branch with a greater than ">" symbol in the branch name.

That caused problems in TeamCity, and on local Windows based computers running SourceTree. BitBucket let it through without any problems.

To resolve the user removed the branch and recreated it. Which was nice and easy.

blocks|key|1014939|text|我使用的是塔式，出于某种原因，我的文件夹名是.git/refs/remotes/origin/Github。将其更改为小写的.git/refs/remotes/origin/github解决了问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1014940|entityMap^0|M|V|1Q|V|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I'm using Tower and for some reason my folder name was <code>.git/refs/remotes/origin/Github</code>. Changing it to lowercase <code>.git/refs/remotes/origin/github</code> solved the issue.

blocks|key|1229589|text|如果有人觉得这很有用，我会长期关注这个问题，尽管不是经常，因为我在Dropbox中有git目录，从Dropbox中删除了它，一切都很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229590|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In case anyone finds this useful, I was getting this issue chronically, although not constantly, and it was because I had git directory within Dropbox, removed it from Dropbox and all was fine.

blocks|key|1229622|text|试试这个：git+branch+--unset-upstream|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1229623|我之前遇到了这个问题，但当我在终端上看到这个命令时，我刚刚解决了这个问题。|1229624|entityMap^0|5|R|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Try this: <code>git branch --unset-upstream</code>
I was facing the problem earlier but I just solved it when I saw this command on the terminal.

blocks|key|1015062|text|错误:无法锁定引用“只是意味着/refs中的信息已损坏，Git无法继续创建index.lock文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1015063|快速修复:删除并重新添加remote。|1015064|复制现有遥控器的-1+\f25+SSH+git+URL+-1\f6。您可以使用以下命令将其打印到终端：|1015065|git+remote+-v|offset|length|style|CODE|1015066|2-从本地git存储库中删除遥控器：|1015067|git+remote+rm+origin|1015068|3-将遥控器添加回本地存储库：|1015069|git+remote+add+origin+git@server-address.org:your-username/repo-name.git|1015070|4-在线论坛中的远程源用户报告以下命令对他们有效：|1015071|git+remote+prune+origin|1015072|5-清理和优化本地存储库git+gc+--prune=now|1015073|你可以在这篇文章上找到更多信息：https://linuxpip.org/git-error-cannot-lock-ref/|1015074|entityMap|0|LINK|mutability|MUTABLE|url|https://linuxpip.org/git-error-cannot-lock-ref/^0|0|0|0|0|D|0|0|0|K|0|0|0|20|0|0|0|N|0|C|I|0|G|1B|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1B|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1C|8|@$H|1D|I|1E|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1F|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1G|8|@$H|1H|I|1I|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1J|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1K|8|@$H|1L|I|1M|J|K]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1N|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1O|8|@$H|1P|I|1Q|J|K]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1R|8|@$H|1S|I|1T|J|K]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1U|8|@]|9|@$H|1V|I|1W|1|1X]]|A|$]]|$1|11|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18]]]]

Error: cannot lock ref&quot; simply means information in /refs are corrupted and Git cannot continue to create index.lock file.
Quick fix : Remove and re-add remote.
-1 Copy the SSH git URL of your existing remote. You can print it to the terminal using this command:
<code>git remote -v</code>
2- Remove the remote from your local git repo:
<code>git remote rm origin</code>
3- Add the remote back to your local repo:
<code>git remote add origin git@server-address.org:your-username/repo-name.git</code>
4- Prune remote origin
Users across online forums have reported that the command below worked for them:
<code>git remote prune origin</code>
5- Clean up and optimize local repository
<code>git gc --prune=now</code>
You can find more info on this article:
<a href="https://linuxpip.org/git-error-cannot-lock-ref/" rel="nofollow noreferrer">https://linuxpip.org/git-error-cannot-lock-ref/</a>

Using git 1.6.4.2, when I tried a <code>git pull</code> I get this error: 

<pre><code>error: unable to resolve reference refs/remotes/origin/LT558-optimize-sql: No such file or directory
From git+ssh://remoteserver/~/misk5
 ! [new branch] LT558-optimize-sql -&gt; origin/LT558-optimize-sql (unable to update local ref)
error: unable to resolve reference refs/remotes/origin/split-css: No such file or directory
 ! [new branch] split-css -&gt; origin/split-css (unable to update local ref)
</code></pre>

I've tried <code>git remote prune origin</code>, but it didn't help.

git pull fails "unable to resolve reference" "unable to update local ref"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

使用git 1.6.4.2，当我尝试一个git pull时，我得到了这个错误：error: unable to resolve reference refs/remotes/origin/LT558-optimize-sql: No such file or directoryFrom git+ssh://remote...

问git拉取失败"unable to resolve reference“"unable to update local ref”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git拉取失败"unable to resolve reference“"unable to update local ref”EN