GitHub Actions workflow-level env not visible in run-name

By Daniel Zoghalchali·Latchkey

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 "

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

1. Reference github.* or inputs.* values that are available at run-name evaluation.
2. 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

1. If the value is only known at runtime, surface it in the job summary rather than run-name.
2. Write to the step summary for a readable label.

How to prevent it

• Limit run-name expressions to github and inputs contexts.
• Use job step summaries for runtime-derived labels.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions