From dd002dda8b9d308bfb62281180d9ce7b1b034b05 Mon Sep 17 00:00:00 2001
From: Ariel Deitcher <1149246+mntlty@users.noreply.github.com>
Date: Mon, 26 Sep 2022 04:11:57 -0700
Subject: [PATCH] be more explicit around merge queue configuration change
 (#31080)

---
 .../configuring-pull-request-merges/managing-a-merge-queue.md  | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

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 55a24db86e..42ca64a782 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
@@ -26,9 +26,10 @@ For information about merge methods, see "[About pull request merges](/pull-requ
 
 {% note %}
 
-**Note:**
+**Notes:**
 
 * 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.
 
 {% endnote %}