blocks|key|1367569|text|就我所知没有。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1367570|但是Git不允许同时使用标签和同名分支，所以如果你有一个用于1.1+works的分支"1.1“，不要放置标签"1.1"，例如使用"v1.1”。|offset|length|style|CODE|1367571|entityMap^0|0|U|3|17|3|1J|3|1T|4|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|I|$]]

Not that I know of. 
But Git will not allow a tag and a branch of the same name at the same time, so if you have a branch "<code>1.1</code>" for <code>1.1</code> works, do not put a tag "<code>1.1</code>", use for instance "<code>v1.1</code>"

blocks|key|1152488|text|我们分别使用分支和标记进行特定于版本的工作，然后是实际的版本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1152489|o---o-----o---o---o---+...+++master
+++++\+++/+++++++/
++++++\+/+++++++/
+++++++o-------o---+...++++++1.6+branch|code-block|syntax|javascript|1152490|每个开发人员都会在心理上做出决定，他们将要提交的工作是只适用于master，还是也与分支相关。您可以看到，对分支所做的更改被合并回master上，但是master上的一些更改永远不会出现在分支上(即，在本例中，那些不是1.6版本的更改)。|1152491|当我们准备好发布时，我们标记它，然后最后一次合并回来，我们用与分支相同的名称命名标记，但使用额外的标识符来说明它是什么特定版本，例如"1.6-+release“或"1.6-beta”或"1.6-rc2"，等等。|1152492|...+------o---o---o--o---o---+...+++master
+++++++++/+++++++/
++++++++/+++++++/
...+---o------(*)---+...++++++1.6+branch
++++++++++1.6-release|1152493|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

We use branches and tags for release-specific work followed by the actual release, respectively:

<pre><code>o---o-----o---o---o--- ... master
 \ / /
 \ / /
 o-------o--- ... 1.6 branch
</code></pre>

Every developer makes a mental decision about whether the work they're about to commit is applicable just to master or if it's also relevant to the branch. You can see that changes that are made to the branch are merged back on master, but some changes on master will never go on the branch (that is, those not intended for the 1.6 release, in this example).

When we're ready to release, we tag it and then merge back one last time, and we name the tag with the same name as the branch, but with an extra identifier about what particular version it is, e.g. "1.6-release" or "1.6-beta" or "1.6-rc2", et cetera.

<pre><code>... ------o---o---o--o---o--- ... master
 / /
 / /
... ---o------(*)--- ... 1.6 branch
 1.6-release
</code></pre>

blocks|key|1367674|text|我不知道有什么标准。我只是简单地选择我的标记名，这样我就可以将|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1367675|VERSION+=+`git+describe+--tags`|code-block|syntax|javascript|1367676|在我的构建脚本中。因此，标记命名约定实际上取决于项目的版本命名约定。|1367677|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 don't know of any standards. I simply choose my tag names such that I can stick a 

<pre><code>VERSION = `git describe --tags`
</code></pre>

in my build scripts. So, the tag naming convention actually depends on the version naming convention of the project.

blocks|key|1367723|text|前述“v”的原因是历史的。较旧的SCCS+(cvs、rcs)无法区分标签标识符和修订号。标签标识符被限制为不能以数字值开头，以便可以检测修订号。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1367724|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|$]]

The reason for the preceding 'v' is historical. Older SCCS (cvs,rcs) could not distinguish between a tag identifier and a revision number. Tag identifiers were restricted to not begin with a numeric value so that revision numbers could be detected.

I've seen a lot of projects using <code>v1.2.3</code> as the naming convention for tags in git. I've also seen some use <code>1.2.3</code>. Is there an officially endorsed style, or are there any good arguments for using either?

Is there a standard naming convention for git tags?

我见过很多项目使用v1.2.3作为git中标签的命名约定。我也见过一些人使用1.2.3。有没有官方认可的风格，或者有什么好的论据可以使用它们？

问git标签有没有标准的命名约定？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git标签有没有标准的命名约定？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git标签有没有标准的命名约定？
EN