docs: document branch filters for merge_group workflows

[hiromieguchi802-lab]

Summary

• document �ranches and �ranches-ignore for merge_group in workflow syntax
• add matching guidance to the merge_group event docs
• update the example workflow to show filtering merge groups that target main

Fixes #32879.

Testing

• reviewed the diff for the two updated docs pages
• attempted to run lint-content, but the local environment is missing or has broken dependencies ( sx was initially unavailable, then highlight.js/lib/languages/golo could not be resolved)

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
actions/reference/workflows-and-actions/events-that-trigger-workflows.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17
actions/reference/workflows-and-actions/workflow-syntax.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@hiromieguchi802-lab I'll ask for a technical review of this for accuracy, then do a quick once-over myself for obvious places to improve grammar and flow, and then kick it over to the docs team review board for a final edit. Just to prepare you, the only one of those steps that's typically fast is the second one, although sometimes we get surprised and get a quick turnaround on the rest.

[github-actions]

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.

[github-actions]

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.

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[github-actions]

This is a gentle reminder for the Technical Content team that this PR is waiting for technical review by a subject matter expert.

[github-actions]

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.

[subatoi]

Many thanks @hiromieguchi802-lab, and thanks for your patience—this looks good as it's reproducing/duplicating existing language in the right way per the agreed guidelines for the contribution, so I'll get this merged 👍

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡