Repository navigation
Open
Labels
Waiting on SME reviewThe request for a technical review by a subject matter expert has stalled.The request for a technical review by a subject matter expert has stalled.builder personacontentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamneeds SMEThis proposal needs review from a subject matter expertThis proposal needs review from a subject matter expertnever-staleDo not close as staleDo not close as stalerepositoriesContent related to repositoriesContent related to repositories
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
What part(s) of the article would you like to see updated?
Explain that you need to add the GitHub Merge Queue app to the bypass list if you apply the rule to "all branches" (or anything that would match the github merge queue branch pattern)
Additional information
The github merge-queue prefix appears to be documented as gh-readonly-queue/{base_branch}:
Line 49 in 6835268
| With third-party CI providers, you will need to update your CI configuration to run when a branch that begins with the special prefix `gh-readonly-queue/{base_branch}` is pushed to. These are the temporary branches that are created on your behalf by a merge queue and contain a different `sha` from the pull request. |
Metadata
Metadata
Assignees
Labels
Waiting on SME reviewThe request for a technical review by a subject matter expert has stalled.The request for a technical review by a subject matter expert has stalled.builder personacontentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamneeds SMEThis proposal needs review from a subject matter expertThis proposal needs review from a subject matter expertnever-staleDo not close as staleDo not close as stalerepositoriesContent related to repositoriesContent related to repositories
Activity
Sharra-writes commentedon Aug 7, 2026
@jsoref Not sure if this is related to the issue about bypass lists that was opened earlier, but it's the same team, at least, so I've given it to them.
github-actions commentedon Aug 7, 2026
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀
github-actions commentedon Sep 21, 2026
This is a gentle reminder for the Technical Content team that this issue is waiting for technical review by a subject matter expert (SME).
github-actions commentedon Nov 9, 2026
This is a gentle reminder for the Technical Content team that this issue is waiting for technical review by a subject matter expert (SME).