jobs.<job_id>.env

Use jobs.<job_id>.env to define env variables for all steps in a standard job.

Usage example

Use env to set variables for an entire workflow or individual step.

env variables with the same name follow specificity precedence. In the following example, the environment variable SERVER: development defined in a step overrides SERVER: production defined in my-job, while the step executes.

my-job:
  env:
    SERVER: production
  steps:
    - name: My first step
      env:
        SERVER: development
      uses: docker://alpine:3.18
      run: echo "Hello $SERVER" #prints "Hello development"
    - name: My second step
      uses: docker://alpine:3.18
      run: echo "Hello $SERVER" #prints "Hello production"▼