[GH-ISSUE #151] Env context is not being replaced using expressions #98

Closed
opened 2026-03-01 21:40:06 +03:00 by kerem · 1 comment
Owner

Originally created by @davidlj95 on GitHub (Mar 13, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/151

Act does not replace the env context when using expressions in workflow files

Issue

When using ${{ env.WHATEVER }} in a workflow file, act does not replace it by the actual environment variable and returns undefined

Reproducing

I've created a repo where this is easily reproducible

https://github.com/davidlj95/act-bug

You can see in the Actions tab that GitHub is replacing the env var though when running act locally it does not and returns undefined

Thanks!

Originally created by @davidlj95 on GitHub (Mar 13, 2020). Original GitHub issue: https://github.com/nektos/act/issues/151 Act does not replace the `env` context when using expressions in workflow files ## Issue When using ``${{ env.WHATEVER }}`` in a workflow file, `act` does not replace it by the actual environment variable and returns undefined ## Reproducing I've created a repo where this is easily reproducible https://github.com/davidlj95/act-bug You can see in the Actions tab that GitHub is replacing the env var though when running `act` locally it does not and returns `undefined` Thanks!
kerem 2026-03-01 21:40:06 +03:00
Author
Owner

@cplee commented on GitHub (Mar 14, 2020):

dup of https://github.com/nektos/act/issues/134

fixed on master and will be in next release

<!-- gh-comment-id:599021126 --> @cplee commented on GitHub (Mar 14, 2020): dup of https://github.com/nektos/act/issues/134 fixed on master and will be in next release
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#98
No description provided.