mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #490] Can't access to input variables on 'workflow_dispatch' event #334
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#334
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 @matiasalbarello on GitHub (Jan 19, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/490
I have this action:
When executing
act workflow_dispatch -j simple-taskI get the following error:ERRO[0000] Unable to interpolate string '${{ github.event.inputs.delay_seconds }}' - [TypeError: Cannot access member 'delay_seconds' of undefined]The workflow works fine on github.
@pauliusm commented on GitHub (Jan 22, 2021):
Looks like same as https://github.com/nektos/act/issues/295
@github-actions[bot] commented on GitHub (Feb 22, 2021):
Issue is stale and will be closed in 14 days unless there is new activity
@benc-uk commented on GitHub (Mar 23, 2021):
Any workaround for this?
I've tried adding a JSON payload like this
It doesn't work
@benc-uk commented on GitHub (Mar 23, 2021):
Ahhh got it working with simply
The docs/README are a little unclear on how to format the JSON, it's implied from the provided example, that the top level keys are the event types, but this isnt the case
@ryuheechul commented on GitHub (Jul 2, 2021):
@benc-uk Thanks for your comment and I agree with you. This should be either fixed to work like other events or this exception should be clearly stated in README because this behaviour wasn't inferable for me by reading https://github.com/nektos/act#events