GitHub Actions workflow-level env not visible in run-name
run-name is evaluated very early, before jobs start, with access to a limited set of contexts (github, inputs). The env context is not available there, so an env reference in run-name resolves to nothing.
What this error means
The run-name shows up blank or with an unresolved expression because it references an env var.
run-name: Deploy ${{ env.TARGET }} # env not available in run-name context
env:
TARGET: production
# run shows: "Deploy "Diagnose it: print the context before you change anything
Most workflow-expression bugs are not syntax errors, they are an expression reading something that is empty. GitHub resolves a missing property to an empty string instead of failing the run, so a wrong reference looks like a logic bug rather than a mistake. Dump the contexts first and you will usually see the answer immediately.
- name: Dump contexts
run: |
echo '--- github ---' ; echo '${{ toJSON(github) }}'
echo '--- needs ---' ; echo '${{ toJSON(needs) }}'
echo '--- steps ---' ; echo '${{ toJSON(steps) }}'
echo '--- matrix ---' ; echo '${{ toJSON(matrix) }}'
echo '--- inputs ---' ; echo '${{ toJSON(inputs) }}'Check the context is allowed where you used it
Contexts are not available everywhere. The same expression can be valid in a step if and invalid in a job if, which is why an expression that works in one workflow fails when moved.
| Where you wrote it | Contexts available there |
|---|---|
run-name | github, inputs, vars |
concurrency | github, inputs, vars |
Top-level env | github, secrets, inputs, vars |
jobs.<id>.if | github, needs, vars, inputs |
jobs.<id>.steps.if | github, needs, strategy, matrix, job, runner, env, vars, steps, inputs |
jobs.<id>.outputs | Full access, including secrets |
Reusable workflow outputs | github, jobs, vars, inputs |
Common causes
env context not available in run-name
run-name only supports github and inputs contexts; env is out of scope.
Workflow env defined after evaluation timing
run-name evaluates before job env is established.
How to fix it
Use github or inputs context in run-name
- Reference github.* or inputs.* values that are available at run-name evaluation.
- Pass dynamic values via workflow_dispatch inputs when needed.
run-name: Deploy ${{ inputs.target }} by ${{ github.actor }}Set the display value inside a job instead
- If the value is only known at runtime, surface it in the job summary rather than run-name.
- Write to the step summary for a readable label.
Catch it before it reaches CI
Every failure in this cluster is statically detectable. actionlint parses workflow expressions, checks context availability against the same rules above, and validates needs references, so these bugs never need to cost you a run.
# one-off
docker run --rm -v "$(pwd):/repo" --workdir /repo rhysd/actionlint:latest -color
# as a job, before anything expensive runs
- uses: actions/checkout@v4
- run: |
bash <(curl -s https://raw.githubusercontent.com/rhysd/actionlint/main/scripts/download-actionlint.bash)
./actionlint -colorHow to prevent it
- Limit run-name expressions to github and inputs contexts.
- Use job step summaries for runtime-derived labels.