-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename tag to label #1054
Comments
Maybe just We can probably include this change in v4 if we move on it soon. Thoughts @asbjornu |
@JakeGinnivan: What SemVer says about this that I can find, is:
And:
So it seems to call these pre-release strings for labels or identifiers. Perhaps |
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. |
If no one objects, I'd like to conclude this discussion with renaming |
I like your idea to rename it to label. :) |
tag-pre-release-weight, tag-prefix, continuous-delivery-fallback-tag, tag-number-pattern, tag
tag-pre-release-weight, tag-prefix, continuous-delivery-fallback-tag, tag-number-pattern, tag
tag-pre-release-weight, tag-prefix, continuous-delivery-fallback-tag, tag-number-pattern, tag
Implement #1054 - renamed tag => label
tag-pre-release-weight, tag-prefix, continuous-delivery-fallback-tag, tag-number-pattern, tag
tag-pre-release-weight, tag-prefix, continuous-delivery-fallback-tag, tag-number-pattern, tag
tag-pre-release-weight, tag-prefix, continuous-delivery-fallback-tag, tag-number-pattern, tag
🎉 This issue has been resolved in version 6.0.0 🎉 Your GitReleaseManager bot 📦🚀 |
In GitVersion, a
tag
is not the same thing as a Git tag, which I find a bit confusing. Wanting to reference a Git tag and use it as the value of the pre-release tag makes it even more confusing. It is currently not possible to do this, but discussions on Gitter might indicate that something like this would be very handy:However, it would be easier to understand if we renamed the pre-release
tag
tolabel
:This would allow for alternating pre-release labels on the same branch, such that a
beta
could be promoted torc
and stay atrc
without having to tag every commit on that branch.Thoughts?
The text was updated successfully, but these errors were encountered: