[core] GraphQL: Skip prompts in non-interactive/CI environment #2277
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.
Type of change (check at least one)
Does this change require a documentation update? (Check one)
Current behavior
When you run
sanity graphql deploy
in a CI or non-interactive prompt (egsanity graphql deploy | grep foo
), it will stall because of prompts waiting for an answer (do you want a playground? do you want to proceed despite dangerous changes?).Description
This PR checks for CI/non-interactive environments and skips the prompts if true:
true
otherwise--force
)--force
)There's a slight change in behavior for interactive environments, too: for the playground prompt, it defaults to the current value. I think that's better than explicitly having to answer "no" each time you deploy.
Note for release
sanity graphql deploy
in non-interactive environmentsChecklist
[some-package] PR title (#123)