Document how to use npm packages and env input #126
8000
Merged
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.
ℹ️ Updated to document
env
andprocess.env
as inputs.We've been using
actions/github-script
to glue together different build tools. We've had cases where we want to passthrough outputs of other scripts to this action –One way would be to just use an input value:
which works, but displays this warning:
Another way would be to inline the value:
but this can cause issues depending on what the value of the string is, and requires you to be aware of how your string will interact with the program:
So this PR introduces a simple
input
variable that is exposed directly to the function:It can be combined with
JSON.parse(input)
in the script to pass through stringified JSON (from other jobs or CLI tools, for example).I also made two other changes