From 9718091f5baa5b1509a950d89d0c6391f6431c1d Mon Sep 17 00:00:00 2001
From: Air <88528265+air3ijai@users.noreply.github.com>
Date: Thu, 28 Mar 2024 19:40:31 +0200
Subject: [PATCH] Add additional clarification about the merge queue (#31844)

Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com>
---
 .../configuring-pull-request-merges/managing-a-merge-queue.md    | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
index 6421420d94..74c0d4bdf9 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
@@ -27,6 +27,7 @@ For more information on merging a pull request using a merge queue, see "[AUTOTI
 
 - A merge queue cannot be enabled with branch protection rules that use wildcard characters (`*`) in the branch name pattern.
 - A merge queue will wait for required checks to be reported before it can proceed with merging. You must update your CI configuration to trigger and report on merge group events when requiring a merge queue.
+- Merge queue and pull requests checks are coupled and configured under branch protection rules or rulesets. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#managing-a-merge-queue)."
 
 {% endnote %}