From e211380fd71c412952956d29b897c092ba889350 Mon Sep 17 00:00:00 2001 From: Aniruddha Adak Date: Thu, 24 Sep 2026 20:53:28 +0530 Subject: [PATCH] docs(rulesets): clarify auto-merge bypass behavior Closes #45265 --- .../managing-rulesets/creating-rulesets-for-a-repository.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md index 783fae2c4fb5..f3df82d5c926 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md @@ -67,6 +67,9 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot {% data reusables.repositories.rulesets-bypass-step %} {% data reusables.repositories.rulesets-branch-tag-bypass-optional-step %} +> [!NOTE] +> If a bypass actor is used to satisfy a pull request rule, the bypass is not currently honored when auto-merge completes the merge. Use a direct merge request instead of enabling auto-merge when relying on that actor. + ### Choosing which branches or tags to target {% data reusables.repositories.rulesets-target-branches %}