fix(action): read INPUT_* env vars via printenv to handle dashes#18
Merged
Conversation
The GitHub Actions runner forwards inputs as `INPUT_<NAME>` env vars
with dashes preserved verbatim — `plan-file` becomes `INPUT_PLAN-FILE`,
not `INPUT_PLAN_FILE` — because only spaces are converted to
underscores. POSIX parameter expansion can't reference names with `-`
(the dash is the default-value operator), so the previous reads of
`${INPUT_PLAN_FILE}` always saw an empty string and the entrypoint
exited with "plan-file input is required" before anything else ran.
Caught by the in-repo self-test workflow added on this branch.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Cro22
added a commit
that referenced
this pull request
Jun 9, 2026
fix(action): read INPUT_* env vars via printenv to handle dashes
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
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.
The GitHub Actions runner forwards inputs as
INPUT_<NAME>env vars with dashes preserved verbatim —plan-filebecomesINPUT_PLAN-FILE, notINPUT_PLAN_FILE— because only spaces are converted to underscores. POSIX parameter expansion can't reference names with-(the dash is the default-value operator), so the previous reads of${INPUT_PLAN_FILE}always saw an empty string and the entrypoint exited with "plan-file input is required" before anything else ran.Caught by the in-repo self-test workflow added on this branch.