-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
act push includes runs that specify branches that don't match my current branch #2489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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. |
If these would be skipped without notice, what would you do if you want to run them? There is 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 |
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. |
…y-events-john nektos#2489 filter workflows by events john
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
I'm not sure this is relevant, but will include it if necessary.
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.
The text was updated successfully, but these errors were encountered: