Don't consider "tag-prefix" as optional if it's explicitly specified to main
#3296
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To correctly calculate the next version with the prefix.
For example, we develop the main product and some its plugin in the same repository and have the following git tags list:
The expected next plugin version is
0.1.2
not0.2.2
(plugin_
prefix will be prepended before setting the tag).Description
Related Issue
3282
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Checklist: