VCS Labeling - additional information needed, documentation is incomplete

Hi,

how does the VCS Labeling feature work with git?

Does it create a simple tag or annotated tag?

Will this trigger further builds if for example some configuration is watching

+:refs/tags/*

(builds are configured to create a build on each new tag)

Will this tag a build which was triggered by a new tag?

E.g.

In some config I am watching: `+:refs/tags/*` in order to build and deploy some version

Someone pushes a new tag which is a semver: 1.0.2

This triggers a build which gets the version stamp 1.0.2-12

```

"git" describe --abbrev=0 %build.vcs.number% --tags > __query.tmp
set /p result=<__query.tmp
del __query.tmp
echo ##teamcity[buildNumber '%%result%%-%build.counter%']

```

Using that buildnumber will this then tag the commit which already has tag 1.0.2 with this new tag 1.0.2-12?

Assuming that new tag is added, this would trigger a new build, because we are watching `+:refs/tags/*` and continue doing so forever?

Afaik its not possible to restrict branches in vcs root and vcs trigger configs with some regex which could avoid this loop in this scenario.

Something like this (see also:  https://regex101.com/r/EcaulX/1):

+:refs/tags/^(?<major>\d+)[.](?<minor>\d+)([.](?<patch>\d+))?
-:refs/tags/^(?<major>\d+)[.](?<minor>\d+)([.](?<patch>\d+))?([-](?<buildnumber>\d+))?