Document on.merge_group branches and branches-ignore filters (#32879) - #45547
sudorm-rf0 wants to merge 2 commits into
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
Thank you, @sudorm-rf0! There's another PR open for this issue, so I'll try to resolve the issue to as many people's benefit as possible. Unfortunately I can't guarantee a timeframe for a response, but we appreciate your interest in the docs 🙇 |
|
A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment. |
|
Hello again—unfortunately we've gone ahead with #43500, as it was raised before this, and was more comprehensive per the agreed contribution guidelines. Sorry this won't have been the answer you were looking for, and thank you for your interest in the GitHub docs. |
Resolves #32879 by documenting the
branchesandbranches-ignorefilters for themerge_groupevent.Both filters are supported for
merge_group— the GitHub Actions team confirmedbranches-ignoresupport directly in the issue thread (validated with abranches-ignore: ["main"]workflow).brancheshas been supported since the merge queue beta (Aug 2022).This adds a short note plus two YAML examples (include and exclude) to the end of the
## merge_groupsection ofevents-that-trigger-workflows.md, mirroring the existingbranches/branches-ignoredocumentation style used forpull_request.Note: this is an English-only content addition; localized files remain behind English, which is the allowed direction for the localization sync check.