@naj8ry ,

Yeah, when you want to access the environment variables in the command lines, the expression syntaxes are different on different shells.

For example:

env:
  MSG: Hello
jobs:
  print_env_var:
    name: Print environment variable
    runs-on: windows-latest
    steps:
    - name: Print environment variable with cmd
      run: echo "String matches %MSG%"
      shell: cmd
- name: Print environment variable with powershell
  run: echo "String matches $env:MSG"
  shell: powershell

- name: Print environment variable with bash
  run: echo "String matches $MSG"
  shell: bash

- name: Print environment variable with pwsh
  run: echo "String matches ${env:MSG}" # Use $env:MSG also can work
  shell: pwsh

- name: Print environment variable with python
  run: |
    import os
    print("String matches", os.environ['MSG'])
  shell: python

However, if the environment variables are defined by the following ways,

1. using the " env" key to define the custom environment variables in the workflow

2. using the Workflow command (::set-env name={name}::{value}) to set environment variables in the workflow

the environment variables will be added to the env context, then you can use the expression syntax " ${{ env.<env name> }}" to access the environment variables. This expression syntax almost can be available to all the shells.

For example:

env:
  MSG: Hello
jobs:
  print_env_var:
    name: Print environment variable
    runs-on: windows-latest
    steps:
    - name: Print environment variable with cmd
      run: echo "String matches ${{ env.MSG }}"
      shell: cmd
- name: Print environment variable with powershell
  run: echo "String matches ${{ env.MSG }}"
  shell: powershell

- name: Print environment variable with bash
  run: echo "String matches ${{ env.MSG }}"
  shell: bash

- name: Print environment variable with pwsh
  run: echo "String matches ${{ env.MSG }}"
  shell: pwsh

- name: Print environment variable with python
  run: print("String matches", "${{ env.MSG }}")
  shell: python