Fix invalid use of secrets context in step-level if expression#14
Merged
Conversation
GitHub Actions does not expose the `secrets` context inside step-level `if:` expressions, so referencing `secrets.github_token` there caused the workflow to fail to parse with "Unrecognized named-value: 'secrets'". Map the secret to a step-scoped `env.GH_TOKEN` and gate the step on the env var instead. The `run` block now consumes the token via the env var rather than interpolating the secret directly into the shell command. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6da40de to
5575e94
Compare
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
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.
GitHub Actions does not expose the
secretscontext inside step-levelif:expressions, so referencingsecrets.github_tokenthere caused the workflow to fail to parse with "Unrecognized named-value: 'secrets'".Map the secret to a step-scoped
env.GH_TOKENand gate the step on the env var instead. Therunblock now consumes the token via the env var rather than interpolating the secret directly into the shell command.