Git thread branches and thread tags - with or without the v prefix

Question

I have seen many conflicting definitions on various git-stream sites. Is there a formal recommendation or the only source of truth?

Branches: release-1.2.3 or release-v1.2.3

Tags: 1.2.3 or v1.2.3

Answer 1

Well, basically it's a matter of preference, but I prefer the version with v , since Semver does it like that and I try to follow this specification as close as possible to get the right version control.

It also simplifies the filtering of these tags, as you can press v and then TAB -key to autocomplete: all tags (and possibly several branches) will be listed here, while there are several numbers a tag can start with.

---

See also: Is there a standard naming convention for git tags?

Answer 2

Since v stands for version, tags are usually called vX.YZ, and XYZ follows Semantic Versioning 2.0.0 .

This allows XYZ branches to coexist with these tags without having to deal with an error message such as "fatal: Ambiguous name name" (as in " Ambiguous Names with GIT? ").

Note that the tags for Git itself have recently been "adapted" for an amazing reason: see "Code Modification Rules", "Rules ".