Repository navigation
Replies: 1 comment
|
Yes. The event name remains pull_request; the “closed” part comes from the event payload's action field. Create an event.json containing at least the fields your workflow/actions read, for example: Then run: For a closed-but-not-merged PR set pull_request.merged to false. This allows conditions such as these to behave correctly: -e is the short form of --eventpath (“path to event JSON file”) in act's CLI definition. act copies that payload to GITHUB_EVENT_PATH and uses the positional pull_request argument for workflow planning. If an action reads more of the GitHub webhook schema, use a real sanitized pull_request.closed webhook payload rather than the minimal example. You can save one from GitHub's webhook delivery view or from gh api repos/OWNER/REPO/pulls/42 and wrap/add the action and repository fields. |
Uh oh!
There was an error while loading. Please reload this page.
Is there a way to specify a pull request closed event?
I am sorry if this is documented, but I looked through discussions and documentation and I'm unsure if this is possible
All reactions