问题
I have seen multiple contradicting definitions on various git flow related websites. Is there an official recommendation or single source of truth?
Branches: release-1.2.3 or release-v1.2.3
Tags: 1.2.3 or v1.2.3
回答1:
Well, basically it is a matter of preference, but I prefer the version with the v, as Semver does it that way and I try to follow that specification as close as possible to get a sane versioning.
It also makes filtering for those Tags easier, as you can press v and then the TAB-key for autocompletion: This will list all the tags (and maybe a few branches), whereas there are several digits a tag could start with.
See also: Is there a standard naming convention for git tags?
回答2:
Since v stands for version, tags are generally named vX.Y.Z, with X.Y.Z following Semantic Versioning 2.0.0.
This allows for branches X.Y.Z to co-exist with those tags, without having to deal with error message like "fatal: Ambiguous object name" (as in "Ambiguous Names with GIT?").
Note that the tags for Git itself have recently been "adapted" for a surprising reason: see "Code version change “rules”".
来源：https://stackoverflow.com/questions/21639437/git-flow-release-branches-and-tags-with-or-without-v-prefix