Repository navigation
feat(nodeenv): read DEST_DIR from env_dir in the config - #468
Merged
Merged
Conversation
env_dir in the [nodeenv] section of the config file sets DEST_DIR for runs that pass neither DEST_DIR nor -p. DEST_DIR on the command line and -p take precedence. The value is used as is, a relative path is taken from the current directory. Fixes #377
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.
env_dirin the[nodeenv]section of the config file sets DEST_DIR forruns that pass neither DEST_DIR nor
-p. DEST_DIR on the command line and-ptake precedence.~is not expanded, a relative path is takenfrom the current directory, like DEST_DIR on the command line.
env_dir = Nonedoesn't endup in it. Until fix(config): make default configuration examples copyable #433 lands,
--dump-config-defaultsprintsenv_dir = None.Fixes #377