{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 爷的心禁止访问 的问题《git fatal:No tags can describe <sha1>》','https://www.manongdao.com/q-1346792.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I am using tags by applying them to nightly builds. Then later, I want to use the output of describe --tags --match <latest tag> to tell me how far from the nightly build my images are. This is for QA testing.
I just ran into an error in a clone that is older than the current tag. I ran git fetch --tags, so I see the tag in git tag output, but when I run git describe --tags --match <tagname>, I get fatal: No tags can describe <head sha1 version number>. I cannot do a git pull to update the workspace at this point. Why does this happen and is there a workaround? Thanks very much
Another explanation can be that the repository was cloned with a
depth=xyzsetting (which Travis does by default). In that case, the history might be cut off before the most current tag.Technically, cloning with
depth=xyzcreates a shallow clone with entries in.git/shallowthat describe where to cut off history. Whengit describethen walks the history it might get to that cut-off point and stops searching for a tag. That even happens if you fetched tags manually after the initial shallow clone withgit fetch --tags.If this is the problem, you need to
unshallowthe repository (or create a full (enough) clone in the first place). See How to convert a Git shallow clone to a full clone? to solve the problem.I actually ran into this error when I have created a git tag based on git reference.
It seems that the git reference was not "in master" and this cause some problems.
So the fix was to find the proper commit reference in master and recreate the tag.
I just ran into this error with
git version 2.8.3and commandgit describe --abbrev=0.The problem was that while the tag existed in the origin and my local repository was up to date, the tag did not have a commit message.
The error was resolved after I re-tagged the commit with a tag message:
It happens because you only fetch the tag, not the commit history of the tag.
git describeuses this history, which is why it has an error.The only workaround is to fetch repo's history containing the tag you're interested in, using
git fetch <remote-name>.