Allow a "yes" option to force run #90
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
|
Use case: I'd like an hourly cron to run environment:deploy so I don't need to manually deploy. |
|
Wow, that's excellent! I was wondering how we could use interactivity similar to Thanks a ton! |
jonpugh
added a commit
that referenced
this pull request
Aug 25, 2015
Allow a "yes" option to force run
|
cc:@jlyon: You did some other work to make Is that work needed anymore now that we have global "--yes"? |
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.
PR for #89. This is based off of the work done in platformsh/legacy-cli#123, which they implemented a --yes and --no option. Any ConfirmationQuestion asked using the helper should used the value of --yes or --no versus its default.