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.
Apparently it was easier than I anticipated. This should address #21.
I'm not sure if you wanted to standardize around
env
or using theinputs/
withfeature. I went with
inputs` because it allowed for a more explicit default value if it is not provided, and at the end of the day I think it all gets exposed the same way.I also played with doing a more consolidated change to the bash file (not using
if
), but this way seems cleaner when it comes to non-zero exit codes fromgit commit
.I did test this with my own site, and confirmed it works as expected when making website changes, when making non-website changes, and when the parameter is not defined (as it will be for pretty much everyone using this once it's released).