Make dotenv run forward flags to given command
#607
+53
−4
Conversation
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
Changes for users:
- (BREAKING) Forward flags passed after `dotenv run` to the given
command instead of interpreting them.
- This means that an invocation such as `dotenv run ls --help` will
show the help page of `ls` instead of that of `dotenv run`.
- To pass flags to `dotenv run` itself, pass them right after `run`:
`dotenv run --help` or `dotenv run --override ls`.
- As usual, generic options should be passed right after `dotenv`:
`dotenv --file path/to/env run ls`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes for users:
dotenv runto the given command instead of interpreting them.dotenv run ls --helpwill show the help page oflsinstead of that ofdotenv run.dotenv runitself, pass them right afterrun:dotenv run --helpordotenv run --override ls.dotenv:dotenv --file path/to/env run lsThis supersedes #592 which only fixes this problem for commands with one component.