mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #1319] Composite action inputs clobbered #716
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#716
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 @gdw2 on GitHub (Aug 25, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1319
Originally assigned to: @KnisterPeter on GitHub.
Bug report info
Command used with act
Describe issue
In action,
${{ inputs... }}not available after 'using' actions/setup-node or actions/setup-java.Link to GitHub repository
https://github.com/gdw2/act-test
Workflow content
Relevant log output
Additional information
I would expect it to echo "TEST2 some-module", but using actions/setup-node seems to clobber
inputsso that${{ inputs.module }}is empty.When I run it verbosely, after actions/setup-node, I no longer see
INPUT_MODULEbeing set for subsequent steps.This works fine on GHA on GHE, which is why I think it might be an act issue.
@gdw2 commented on GitHub (Aug 25, 2022):
I also want to leave open the possibility that I have no idea what I'm doing.
@ChristopherHX commented on GitHub (Aug 25, 2022):
This sounds like an issue of this change
github.com/nektos/act@e360811570Does act v0.2.26 work? The release before composite logic changes.
@SolalVall commented on GitHub (Aug 26, 2022):
Hello Everyone,
I am facing the same issue and I just wanted to confirm that the issue is not present in version
0.2.26. Please find some logs below that compare a similar workflow using the action but with two different versions (0.2.26&0.2.30).Yaml samples
workflow.ymltest/action.ymlResults
using
act@v0.2.26using
act@v0.2.30Additional details
As you can observe at the end of the output when
act@0.2.30is used, inputs are replaced by the one specified in the previous action.@KnisterPeter commented on GitHub (Aug 28, 2022):
I will take care of that. Might need a week before I can start looking into it.
@ChiwanAhn commented on GitHub (Sep 6, 2022):
it works with
act@0.2.31