fix(get-next-bump): fix to permit usage of --get-next option even when update_changelog_on_bump is set to true #1301
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.
Description
With the configuration options
update_changelog_on_bumpset toTrue, the commandcz bump --get-nextcrashed, due to the mutual exclusive options--get-nextand--changelog/--changelog-to-stdout.Changing this behavior to still throw a conflict when using both CLI options, but let
--get-nexttake the precedence overupdate_changelog_on_bumpconfiguration.Checklist
./scripts/formatand./scripts/testlocally to ensure this change passes linter check and testExpected behavior
Now the configuration options
update_changelog_on_bumpcan be set to whatever you want when using thecz bump --get-nextcommand.Steps to Test This Pull Request
update_changelog_on_bumpflag set to true.cz bump --get-nextAdditional context