mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[PR #1458] [MERGED] fix: step env is unavailable in with property expr #1956
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1956
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/nektos/act/pull/1458
Author: @ChristopherHX
Created: 11/23/2022
Status: ✅ Merged
Merged: 12/6/2022
Merged by: @mergify[bot]
Base:
master← Head:fix-step-env-in-with-property📝 Commits (4)
3e72103fix: step env is unavailable in with property expra843e67don't run the test on windows354f545fix: composite action add missing shelld44f6b4Merge branch 'master' into fix-step-env-in-with-property📊 Changes
5 files changed (+40 additions, -2 deletions)
View changed files
📝
pkg/runner/expression.go(+5 -1)📝
pkg/runner/runner_test.go(+1 -0)📝
pkg/runner/step.go(+11 -1)➕
pkg/runner/testdata/inputs-via-env-context/action.yml(+8 -0)➕
pkg/runner/testdata/inputs-via-env-context/push.yml(+15 -0)📄 Description
Weird inputs and env are both evaluated in the env context. This change delays the evaluation of INPUT_ env vars and makes the step env available. This feels like a hack to make act do what we expect.
Related to #1421, but more bugs are mentioned there
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.