From 11e0f6e7e8de0733571cd49fc2768a48aec30092 Mon Sep 17 00:00:00 2001 From: Dylan Duan Date: Wed, 28 Oct 2026 09:22:55 -0700 Subject: [PATCH] Note merge queue plan availability in "Managing a branch protection rule" Fixes #46506 --- .../managing-a-branch-protection-rule.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule.md index 71fe71cf5fba..a32739744283 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule.md @@ -74,7 +74,11 @@ When you create a branch rule, the branch you specify doesn't have to exist yet 1. Optionally, select **Require conversation resolution before merging**. 1. Optionally, select **Require signed commits**. 1. Optionally, select **Require linear history**. -1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %} +1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. + + > [!NOTE] + > {% ifversion fpt or ghec %}Pull request merge queues are available in any public repository owned by an organization, or in private repositories owned by organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}{% elsif ghes %}Pull request merge queues are available in any organization-owned repository on {% data variables.product.prodname_ghe_server %}.{% endif %} {% data reusables.pull_requests.merge-queue-references %} + 1. Optionally, to choose which environments the changes must be successfully deployed to before merging, select **Require deployments to succeed before merging**, then select the environments. 1. Optionally, make the branch read-only. * Select **Lock branch**.