mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2501] Input default values are not interpreted in step conditional when using external actions #1157
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#1157
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?
Originally created by @philipreinken on GitHub (Oct 23, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2501
Bug report info
gh act --bug-report
Command used with act
Describe issue
Hi all 👋
I stumbled upon this behaviour, which I think might be a bug - given the following step:
The inputs default value is set as expected when evaluating the expression for setting the
FOO_VALenvironment variable:This is not the case when the step execution conditional is interpreted:
This results in the step being skipped.
I'd expect the expressions to be interpreted the same way.
This is by the way only the case for the step referencing an external action, the
runstep right below is executed.I've referenced a repo where this behaviour can be reproduced.
Link to GitHub repository
https://github.com/philipreinken/20241023-2007-debug-act
Workflow content
Relevant log output
gh act --verbose
Additional information
No response
@github-actions[bot] commented on GitHub (Apr 22, 2025):
Issue is stale and will be closed in 14 days unless there is new activity
@beta-ziliani commented on GitHub (May 15, 2025):
I hit this problem today :'-(