mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2489] act push includes runs that specify branches that don't match my current branch #1152
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#1152
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 @alunduil-gs on GitHub (Oct 17, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2489
Bug report info
Command used with act
Describe issue
I expected workflows that were not applicable (such as those restricted to master) to not be listed as part of the run, but they are included which means some merge to master flows will be attempted.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
I've stripped the workflow description to only the selection criteria but let me know if that's too stripped back and I can work to find a better reproduction for this.
I may also just be having incorrect expectations since I want to use act to run workflows as a sanity check instead of other local testing methodologies but we have quite complex workflows defined currently.
@kinson-liu commented on GitHub (Nov 24, 2024):
I also got this issue. I see the code, the planner just loads workflows and filter the events. It doesn't check the branches in the push event.
@ChristopherHX commented on GitHub (Nov 24, 2024):
If these would be skipped without notice, what would you do if you want to run them?
There is
-Wto select a single workflow yaml file, for example this commandact -W .github/workflows/merge_to_master.yml pushmay just do nothing.I need a clear proposal, until then this is an incomplete feature request (packed into a bug report) that cannot be added to my backlog
@john-tipper commented on GitHub (Apr 11, 2025):
I added a PR that goes a long way to resolving this - there's an optional opt-in flag to have Act perform filtering of workflows based on the event, including examining the event file if supplied to perform the work of the GHA on.<> filters for push, pull_request and pull_request_target events.