-
Notifications
You must be signed in to change notification settings - Fork 59.1k
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
No doc of on.merge_group.<branches|branches-ignore>
#32879
Comments
@muzimuzhi Thank you for opening this issue! I'll get this triaged for review ✨ |
Sorry but I don't think this has been resolved. |
@muzimuzhi Apologies on behalf of our overzealous bot! I'll reopen this 💛 |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
👋 I can confirm on behalf of the Actions team that I validated this with two workflows - one on a regular on:
merge_group:
branches-ignore: ["main"] In this image, pull request 8 is the PR that added the |
Thank you very much for confirming, @joshmgross! ✨
@SiaraMist Howdy! 👋 Do we have a preference on either approach for updating this doc? |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions
What part(s) of the article would you like to see updated?
GitHub Actions
merge_group
trigger supportsbranches
filter since its beta release in Aug 2022, but it's not documented till now.I guess the symmetric
branches-ignore
filter is also supported but didn't check it myself.One option is to extend current section
on.<pull_request|pull_request_target>.<branches|branches-ignore>
to covermerge_group
and taking care of old anchor name redirection. Or add a separateon.merge_group.<branches|branches-ignore>
section.Additional information
Relevant GitHub Blogs
Related
The text was updated successfully, but these errors were encountered: