mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2478] pull_request events are registered as push events when having multiple workflows that trigger on both pull and push #1145
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#1145
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 @prvg-sso on GitHub (Oct 2, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2478
Bug report info
Command used with act
Describe issue
I have two workflows (test-push-workflow.yml, test-pull_request-workflow.yml), one triggers on push events and the other trigger on pull_request events. When providing a sample pull_request event json, the workflow that triggers on the push event is executed, NOT the one that triggers on pull_request. However, If I remove the test-push-workflow.yml from the .github/workflows dir, then test-pull_request-workflow.yml is triggered with the correct pull_request event!.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
event_pr_open_simple.json:
.github/workflows/test-push-workflow.yml
@prvg-sso commented on GitHub (Oct 2, 2024):
the pull_request also doesn't work if there is a reusable workflow in .github/workflows/ dir, which is the real problem from me..
@ChristopherHX commented on GitHub (Oct 2, 2024):
This is an user error, it's impossible to reliable reverse engineer a webhook payload to an event_name. The auto detection is super basic and were initially not present.
Intially where
actaliased toact push, external contributors changed that to do trivial auto detection.You are expected to run
act pull_request --bind -e event_pr_open_simple.json --secret-file .env-devMore Details:
This doesn't fall into the capacity I allocate for act enhancements that are nice to have
@prvg-sso commented on GitHub (Oct 3, 2024):
aha, I see now it's stated quite clearly in the usage guide :). I thought
the event could be detected from the content of the payload, but apparently
not.
Thanks for helping out!.
On Thu, 3 Oct 2024 at 00:18, ChristopherHX @.***> wrote:
@github-actions[bot] commented on GitHub (Apr 2, 2025):
Issue is stale and will be closed in 14 days unless there is new activity