mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2002] Event payload provided via .json not respected by act #962
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#962
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 @chamaoskurumi on GitHub (Sep 11, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/2002
Bug report info
Command used with act
Describe issue
I want to mimic a pull_request from a branch with
randomnameinto themasterbranch.Given the workflow, the job/workflow should not be triggered, because it requires the branch to be named
feature/*.Expected
I expect
act pull_request -e my_act_event.jsonor justact -e my_act_event.jsonnot to trigger the workflow and skip.Observed
act -e my_act_event.jsontriggers act to run the workflowReproducible Example
git clone git@github.com:cplee/github-actions-demo.gitChange the workflow
main.ymlto the one decribed below.And add a event payload as json in root:
my_act_event.json
Link to GitHub repository
https://github.com/cplee/github-actions-demo
Workflow content
Relevant log output
Additional information
Seems like the whole event payload is not respeced by act, despite it being read
@sudomf commented on GitHub (Sep 30, 2023):
Experiencing the same issue for pull_request.json
@MattFaz commented on GitHub (Nov 9, 2023):
Same issue for me
@github-actions[bot] commented on GitHub (Aug 14, 2024):
Issue is stale and will be closed in 14 days unless there is new activity
@ipatch commented on GitHub (Nov 8, 2024):
🤨 is this still an ongoing issue? i ask because i didn't see a mention a PR attempting to fix this issue, and only noticed being closed due to it being stale.