We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Hi! I tried adding a strict: false flag to the pipeline but the PATCH version seems to not increment when there are no matching keywords.
strict: false
Output with debug [ paste output of the command with -d flag here ]
-d
Expected behavior
If the strict flag is false, the PATCH number should increment without matching keywords.
Additional context
!params.varStrict
if !params.varStrict && !s.Force.Strict { s.Semver.Patch++ debugPrint(fmt.Sprintln("Incrementing patch (DEFAULT) on ", strings.TrimSuffix(commit.Message, "\n"), "| Semver:", s.getSemver())) }
The text was updated successfully, but these errors were encountered:
Could you try doing the same with the strict mode in yaml file?
For example
version: 1 force: major: 1 existing: false strict: false wording: patch: - update - initial - fix minor: - change - improve major: - breaking release: - release-candidate
Sorry, something went wrong.
Released update (1.10.109), now, the strict mode should work if the parameter is supplied :)
Sorry this was my bad, I had the strict flag set to true in the config file and false in the action. Now it works great!
Not a problem - at least motivated me to add the missing flags to the action as well :)
lukaszraczylo
No branches or pull requests
Describe the bug
Hi! I tried adding a
strict: false
flag to the pipeline but the PATCH version seems to not increment when there are no matching keywords.Output with debug
[ paste output of the command with
-d
flag here ]Expected behavior
If the strict flag is false, the PATCH number should increment without matching keywords.
Additional context
!params.varStrict
in code should be without negation?The text was updated successfully, but these errors were encountered: