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
How do I need to configure my action to have this tagging when I commit on any branch but master?
Example:
Previous version is v2.2.1
I create a PR, and every commit in the PR should be tagged like this : v2.2.2-dev.0 , v2.2.2-dev.1, v2.2.2-dev.2
Then when I merge the PR to master, I have would like to have : v2.2.2
I'm almost sure this is possible, since I've seen similar stuff on reported issues, but I can find de correct way to configure the action to even add a suffix.
Thank you
The text was updated successfully, but these errors were encountered:
To be more exact, I am trying to do the following:
Let's say the last tag on production is v1.1.0.
Now, we have a release branch with release candidates under test like so: v1.2.0-rc.0, v1.2.0-rc.1, v1.2.0-rc.2, etc.
Assuming there are only PATCH changes to a release candidate, only the number in the end shall be incremented.
The actual release would then be tagged with v1.2.0 of course.
The idea here is to keep a clean semver history for production tags and not to have a jump from v1.1.0 to let's say v1.2.2. And use PATCH releases only for an actual hotfix.
From what I am seeing by testing and also looking at the source code, this behaviour cannot be enforced right now. Since the detected bump will always be used for the prerelease tag.
Example:
Current tag: v1.1.0
commit with MINOR change on release branch, e.g. "feat: foo" -> pre-release tag set to v1.2.0-rc.0
commit with PATCH change on release branch, e.g. "fix: bar" -> pre-release tag set to v1.2.1-rc.0
another commit with MINOR change on release branch, e.g. "feat: baz" -> pre-release tag set to v1.3.0-rc.0
I am using the following config right now for testing:
How do I need to configure my action to have this tagging when I commit on any branch but master?
Example:
Previous version is v2.2.1
I create a PR, and every commit in the PR should be tagged like this : v2.2.2-dev.0 , v2.2.2-dev.1, v2.2.2-dev.2
Then when I merge the PR to master, I have would like to have : v2.2.2
I'm almost sure this is possible, since I've seen similar stuff on reported issues, but I can find de correct way to configure the action to even add a suffix.
Thank you
The text was updated successfully, but these errors were encountered: