Fix inherited apply usage flags - #59
Closed
brownie-ricon wants to merge 1 commit into
Closed
Conversation
Contributor
This file contains hidden or 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
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.
Summary
wp applyflags from the current argv instead of inheritedusage_*environment--yes/-yas the only non-interactive approval signal for this invocationusage_yes/usage_ycannot add Spaces headlesslyVerification
mise run test(34/34)mise run lintusage_yes=true usage_y=true bats --filter 'refuses' test/apply.batsCALLER_PWD="$PWD" mise exec -- readme build --checkbash -n .mise/tasks/apply/_default test/apply.batsgit diff --checkswift test(5/5)No real
wp apply,butthair spaces:add, Space/window movement, or desktop mutation was run; all apply coverage used mocks.