From 4eeb0ce93ac52805832953030e7f0f08f9c4072c Mon Sep 17 00:00:00 2001 From: Aniruddha Adak Date: Thu, 24 Sep 2026 19:59:05 +0530 Subject: [PATCH] docs(rulesets): document merge queue bypass for restrict creations Closes #45334 --- .../managing-rulesets/available-rules-for-rulesets.md | 3 +++ 1 file changed, 3 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 7d357280a53f..1b5941815ab1 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,9 @@ 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. +> [!NOTE] +> If you use a merge queue and enable **Restrict creations** for a ruleset that targets all branches, or for a pattern that matches the merge queue's temporary branches, add the **GitHub Merge Queue** app to the bypass list. The merge queue creates temporary branches, and without this bypass it cannot create them. For more information, see [AUTOTITLE](/pull-requests/how-tos/merge-and-close-pull-requests/merging-a-pull-request-with-a-merge-queue). + ## Restrict updates If selected, only users with bypass permissions can push to branches or tags whose name matches the pattern you specify.