Act uses github.event.inputs.variable_name but Github Actions uses inputs.variable_name? #1303
Unanswered
robertherber
asked this question in
Q&A
Replies: 2 comments 3 replies
-
|
The event |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Well, If workflow_dispatch is not supported - what's the recommended way to test workflows..? I thought that'd be the most natural way to test one-off workflows. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I just started using act. It's great to be able to test workflows locally.
But one things I just can't seem to get my head around is the inconsistency between act requiring
github.event.inputsfor inputs and Github Actions using justinputsfor workflow_dispatch (tried with both workflow_dispatch and workflow_call on the GA side). What am I missing here? Is there a reason for this and is there a way around it?Live example here. My current workaround is renaming all references to
inputsto match Github Actions, but now I can obviously not run my workflows locally:github.event.inputsBeta Was this translation helpful? Give feedback.
All reactions