We created a tag “2012/02/16” on our git repository. We then noticed that inside of Source Tree the 2012 and 01 were represented as folders which could neatly be opened and closed to reveal and hide the tags. Having a nested hierarchy of tags seems like a nice way to organize the tags instead of just having one flat list.
Is there an issue with doing this?
When I do a git ls-remote I see the following entries:
8430572c89362b875109628c33a18e782aa38488 refs/tags/2012/02/16
d247e38159c8c4998bf8b555edfd7ffe7b945255 refs/tags/2012/02/16^{}
I’m not sure what the ^{} characters at the end of the second tag mean and I want to make sure that this behavior we stumbled upon isn’t something we should not be doing before we go and leverage it to clean up our tags.
We don’t see the ^{} characters on our “un-nested” tags.
No problem, using a slash is standard practice for example in the "git-flow" discipline. You can check the syntax rules for tag names in the manual page git-check-ref-format (1):
https://git-scm.com/docs/git-check-ref-format
The caret with brackets is something git is trying to tell you about that tag, not something you typed. You can interpret it using the manual page gitrevisions (7):
https://git-scm.com/docs/gitrevisions