repo_structure update for Directories as Environment #24
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
Removing the dev env file from the prod folder and the prod env file from the dev folder.
|
@tchia04 thanks a ton for you contribution here, and my apologies for not getting back to you sooner. I've been meaning to write up some more information about this for some time. I just pushed an update to the docs explaining the reasoning a bit more. I hope the current version explains it better now, but of course feel free to submit another PR if have ideas on how to improve it. |
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.
Removing the dev env file from the prod folder and the prod env file from the dev folder for
Directories as Environment
Directories as Environments with a Single Module
It's confusing to see "prod-us-west-2.env" under the dev folder and "dev-us-west-2.env" under the prod folder.