fix(cli): Fix global flag parsing interference #235
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes the release failures such as https://github.com/getsentry/sentry/runs/2591288014?check_suite_focus=true. The culprit is #224 where we switched the global `--no-input` and `--dry-run` flags from boolean to string args. This now causes `craft prepare --no-input "21.5.0"` to be interpreted as `craft prepare --no-input=21.5.0`. This patch fixes the issue.
HazAT
approved these changes
May 17, 2021
BYK
added a commit
to getsentry/action-prepare-release
that referenced
this pull request
May 17, 2021
Provides a temporary fix until getsentry/craft#235 lands. It is also no longer needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes the release failures such as https://github.com/getsentry/sentry/runs/2591288014?check_suite_focus=true.
The culprit is #224 where we switched the global
--no-inputand--dry-runflags from boolean to string args.This now causes
craft prepare --no-input "21.5.0"to be interpretedas
craft prepare --no-input=21.5.0.This patch fixes the issue.