将at标签分配给Github发行版也将其分配给Commit [英] Will assigning at tag to a Github Release also assign it to the Commit

问题描述

假设指定的commit还没有标签，是否会在标签(例如v1.1.0)处分配给Github release并将其分配给commit?如果是这样，它是lightweight还是annotated标签?

Will assigning at tag (e.g. v1.1.0) to a Github release also assign it to the commit, assuming that the specified commit doesn't already have a tag? If so, will it be a lightweight or annotated tag?

推荐答案

将在标签(例如v1.1.0)处分配给Github release，还将其分配给commit

Will assigning at tag (e.g. v1.1.0) to a Github release also assign it to the commit

是的.

如果是，是lightweight还是annotated标签?

一个轻巧的东西.

您可以查看此 示例发行版 .该存储库以前没有任何标签.

You can take a look at this sample release that I've created through GitHub UI for the sake of answering this question. This repository wasn't previously bearing any tag.

在本地获取内容后，您可以看到上游已添加了一个新标签.

Once locally fetched, one can see that a new tag has been added upstream.

$ ls .git/refs/tags/
v0.1

该标签直接指向一个提交(即，这是一个轻量级标签，而不是带注释的标签).

And that this tag directly points to a commit (ie. It's a lightweight tag, not an annotated one).

$ cat .git/refs/tags/v0.1
485750d2def0e01f5653534659d1785be0ff73db

$ git cat-file -t 48575
commit

这篇关于将at标签分配给Github发行版也将其分配给Commit的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！