Add a command option to set environment variables #11
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
|
I saw the CI failure and fixed the js formatting. I think it'll pass now 🤞 |
pvsr
force-pushed
the
env
branch
2 times, most recently
from
cf6f224 to
3665b86
Compare
|
I figured out how to run the CI in my fork and got the tests passing in the CI env, so now it should work for real 😅 |
pvsr
force-pushed
the
env
branch
2 times, most recently
from
4014884 to
b84a35a
Compare
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.
Adds
SetEnvironment(List(#(String, String)))toCommandOpt, where the contents of the list are key-value pairs to set as environment variables in the child process. I tested across erlang, node, and deno.