You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using gitversion for a while now and I understand it's really powerfull and flexibel. On the opposite side there is a hugh complexity involved in getting it to work in a way that one might like.
The thing that troubles me most is that it seems hard(impossible?) to use a PreReleaseLabel without a PreReleaseNumber. The PreReleaseLabel can be configured in a really powerful way by the branches.xyz.tag configuration. But it will always come with an additional postfix of a PreReleaseNumber, that seems to be out of control.
In my use-case I would really love to use just the fixed string 'SNAPSHOT' as a prelease-label (combined with {BranchName}), but i do not want this prerelease to get a PreReleaseNumber Postfix.
Another imho valid use case is just about the opposite, use a PreReleaseNumber, but dont't add a PreReleaseLabel, check this issue for the details: #2347
So, do we have any chance to use PreReleaseLabel and PreReleaseNumber indepently of each other? In effect we'd like to have more control over the resulting PreReleaseTag.
The rationale/logic behind the current behaviour is explained briefly here: #1646
By the looks of it, this sounds related to what's being discussed in #2065. Could you please read through that discussion and comment on whether it could be adjusted to also support your use-case? The discussion in #2199 may also prove relevant, although from a different perspective.
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.
We have been using gitversion for a while now and I understand it's really powerfull and flexibel. On the opposite side there is a hugh complexity involved in getting it to work in a way that one might like.
The thing that troubles me most is that it seems hard(impossible?) to use a PreReleaseLabel without a PreReleaseNumber. The PreReleaseLabel can be configured in a really powerful way by the
branches.xyz.tag
configuration. But it will always come with an additional postfix of a PreReleaseNumber, that seems to be out of control.In my use-case I would really love to use just the fixed string 'SNAPSHOT' as a prelease-label (combined with {BranchName}), but i do not want this prerelease to get a PreReleaseNumber Postfix.
Another imho valid use case is just about the opposite, use a PreReleaseNumber, but dont't add a PreReleaseLabel, check this issue for the details: #2347
So, do we have any chance to use PreReleaseLabel and PreReleaseNumber indepently of each other? In effect we'd like to have more control over the resulting PreReleaseTag.
The rationale/logic behind the current behaviour is explained briefly here:
#1646
actual result
desired result
The text was updated successfully, but these errors were encountered: