Git: "wildcard refspec" without matching on the remote when pulling

I installed the new Git repository in cloufforge and have some unusual problems.

When I do a git pull origin master From https://dndigital.git.cloudforge.com/project * branch master -> FETCH_HEAD Already up-to-date. 

But if a colleague does the same thing, he continues to repeat the same message again and again, without receiving “Already updated”

 remote: Counting objects: 85, done. remote: Compressing objects: 100% (58/58), done. remote: Total 76 (delta 59), reused 19 (delta 13) Unpacking objects: 100% (76/76), done. From https://dndigital.git.cloudforge.com/project * branch master -> FETCH_HEAD There are no candidates for merging among the refs that you just fetched. Generally this means that you provided a wildcard refspec which had no matches on the remote end. 

Why is this happening?

Update:

I tried the suggested answer and see no problem. But the problem seems to be that we are using different Git clients. It seems that different versions of Git clients can be problematic. It is really hard. Is there a way to limit Git's capabilities to a specific version of Git so that the earliest Git client can work?

 [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = https:// username@dndigital.git.cloudforge.com /project.git [branch "master"] remote = origin merge = refs/heads/master [user] name = email = [giggle] file-view-path = agile/includes/SiteConfig.php [gui] wmstate = zoomed geometry = 787x379+512+242 248 420 
+7
source share
2 answers

Take a look at your colleague .git/config , it seems that git does not know that the remote origin/master branch should be merged with its local master branch.

You should have something like this set up

 [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = ... [branch "master"] remote = origin merge = refs/heads/master 

Note that git pull does a git fetch , and then a git merge under the hood. You can try step by step to understand what is wrong.

 git checkout master git fetch origin git merge origin/master 
+7
source

Hey, I had the same problem, but it was caused by a lack of destination. You can help check this out if nothing works.

+4
source

All Articles