From 14d40c0e43be40ef103bbfcb4599e999c9d08248 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=9C=89=E6=84=8F=E4=B9=89?= <3407842232@qq.com>
Date: Tue, 6 Oct 2026 16:29:57 +0800
Subject: [PATCH] Document merge queue bypass for restricted creations

---
 .../managing-rulesets/available-rules-for-rulesets.md           | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md
index 1600b36770dc..4fdc9cfcfb5d 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md
@@ -26,6 +26,8 @@ For more information on creating rulesets and bypass permissions, see {% ifversi
 
 If selected, only users with bypass permissions can create branches or tags whose name matches the pattern you specify.
 
+If you apply this rule to all branches, add the **GitHub Merge Queue** app to the bypass list. Merge queue branches use the `gh-readonly-queue/{base_branch}` naming pattern and must be allowed to be created.
+
 ## Restrict updates
 
 If selected, only users with bypass permissions can push to branches or tags whose name matches the pattern you specify.