don't delete existing environment module files when using --dump-env-script with --force or --rebuild
#4512
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
This option should only require `--force` when the env file exists. Otherwise, when the module already exists `--force` should not be required. In any case the module file must not be deleted.
Flamefire
force-pushed
the
fix-dump-env-script
branch
from
551aa5d
to
45ad228
Compare
Flamefire
changed the title
boegel
changed the title
--dump-env-script with --force or --rebuild
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.
This option should only require
--forcewhen the env file exists.Otherwise, when the module already exists
--forceshould not be required.In any case the module file must not be deleted.