-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reusable workflow uses workflow_dispatch default instead of passed input value #2464
Comments
Do you have already a plan when or how this could be tackled? |
Hello, if the issue is not taken then I am interested to contribute. I would greatly appreciate any guidance or direction from a regular contributor to help me get started effectively. |
act/pkg/runner/reusable_workflow.go Lines 116 to 144 in 03a4480
From initial investigation I found out, for reusable workflow Before initializing the This fix still doesn't resolve the issue. Now the event is correct I am still figuring out where the values from main workflow is passed to the reuse workflow. |
Yes you can take this issue, this doesn't fit into my capacity for act to work on this year
Reusable workflows in act are unfinished and unmaintained, after those working on them left
Yes this is confusing, especially if someone uses the I assume |
…workflow_dispatch inputs Closes: nektos#2464
Bug report info
Command used with act
Describe issue
When using a reusable workflow that defines the same input parameter in both its workflow_call and workflow_dispatch events, the workflow incorrectly uses the default value from the workflow_dispatch event instead of the value passed from the calling workflow.
Steps to reproduce:
See the Dockerfile for repro
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
Dockerfile to repro the issue easily:
The text was updated successfully, but these errors were encountered: