This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
Add EnsureEnv helper to automate credential process #212
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
7 tasks
katiedavis
approved these changes
Jul 7, 2019
Closed
tanema
approved these changes
Jul 8, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR introduces an EnsureEnv task that can be added as a prerequisite to commands to ensure that a
.envfile exists before the command runs. If it doesn't, it will ask the user for their credentials and create the file. This allows us to remove the .env requirement from the creation flow, along with the .env fixes in shopify_app v11.0.1 (Shopify/shopify_app#776).Closes #156