From 9b8a34b412ba116342b9feb5abd53f5c20d63256 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Sat, 26 Sep 2026 00:45:07 +0000
Subject: [PATCH 1/2] docs: note open comments warning in editor publish menu

---
 editor/review.mdx    | 2 ++
 es/editor/review.mdx | 2 ++
 fr/editor/review.mdx | 2 ++
 zh/editor/review.mdx | 2 ++
 4 files changed, 8 insertions(+)

diff --git a/editor/review.mdx b/editor/review.mdx
index 6f75f6f09..c5c850137 100644
--- a/editor/review.mdx
+++ b/editor/review.mdx
@@ -42,6 +42,8 @@ To point a teammate at a specific page on a branch, click <Icon icon="ellipsis"
 
 When your branch has a pull request, the publish menu shows its changed files and review status, like **Draft in progress**, **Review required**, **Changes requested**, or **Approved**. Click **View request** to open the pull request in your Git provider.
 
+If the branch still has unresolved comment threads, the publish menu shows a warning with the number of open comments in place of **Ready to publish** or **Approved**. You can still merge and publish. The warning reminds you to resolve feedback first.
+
 1. Click **Publish** in the top bar, then click **Request review**. This marks the pull request ready for review.
 1. Reviewers approve the pull request in your Git provider.
 1. Click **Publish**, then click **Merge and publish**. The editor merges the pull request, deploys your changes, and switches you back to your deployment branch.
diff --git a/es/editor/review.mdx b/es/editor/review.mdx
index 5c1915221..f31db33f7 100644
--- a/es/editor/review.mdx
+++ b/es/editor/review.mdx
@@ -62,6 +62,8 @@ Para dirigir a un compañero a una página concreta de una branch, haga clic en
 
 Cuando su branch tiene una pull request, el menú de publicación muestra sus archivos modificados y el estado de revisión, como **Draft in progress**, **Review required**, **Changes requested** o **Approved**. Haga clic en **View request** para abrir la pull request en su proveedor de Git.
 
+Si la branch todavía tiene hilos de comentarios sin resolver, el menú de publicación muestra una advertencia con el número de comentarios abiertos en lugar de **Ready to publish** o **Approved**. Aún puede fusionar y publicar. La advertencia le recuerda que primero debe resolver los comentarios.
+
 1. Haga clic en **Publish** en la barra superior y luego en **Request review**. Esto marca la pull request como lista para revisión.
 1. Los revisores aprueban la pull request en su proveedor de Git.
 1. Haga clic en **Publish** y luego en **Merge and publish**. El editor hace merge de la pull request, despliega sus cambios y le devuelve a su deployment branch.
diff --git a/fr/editor/review.mdx b/fr/editor/review.mdx
index 62363d3eb..e7f6ca2d2 100644
--- a/fr/editor/review.mdx
+++ b/fr/editor/review.mdx
@@ -62,6 +62,8 @@ Pour diriger un collègue vers une page précise d'une branch, cliquez sur <Icon
 
 Lorsque votre branch comporte une pull request, le menu de publication affiche ses fichiers modifiés et son état de révision, comme **Draft in progress**, **Review required**, **Changes requested** ou **Approved**. Cliquez sur **View request** pour ouvrir la pull request chez votre fournisseur Git.
 
+Si la branch comporte encore des fils de commentaires non résolus, le menu de publication affiche un avertissement indiquant le nombre de commentaires ouverts à la place de **Ready to publish** ou **Approved**. Vous pouvez toujours fusionner et publier. L’avertissement vous rappelle de traiter les retours au préalable.
+
 1. Cliquez sur **Publish** dans la barre supérieure, puis sur **Request review**. Cela marque la pull request comme prête à être relue.
 1. Les relecteurs approuvent la pull request chez votre fournisseur Git.
 1. Cliquez sur **Publish**, puis sur **Merge and publish**. L'éditeur fusionne la pull request, déploie vos modifications et vous ramène sur votre deployment branch.
diff --git a/zh/editor/review.mdx b/zh/editor/review.mdx
index 759f6074e..cd9ded537 100644
--- a/zh/editor/review.mdx
+++ b/zh/editor/review.mdx
@@ -62,6 +62,8 @@ keywords: ["review", "preview", "live preview", "pull request", "request review"
 
 当你的分支存在 pull request 时，发布菜单会显示其已更改的文件和审阅状态，例如 **Draft in progress**、**Review required**、**Changes requested** 或 **Approved**。点击 **View request** 可在你的 Git 提供方中打开该 pull request。
 
+如果分支仍有未解决的评论线程，发布菜单会显示一条警告，列出未解决评论的数量，以替代 **Ready to publish** 或 **Approved**。你仍然可以合并并发布。该警告用于提醒你先处理反馈。
+
 1. 点击顶部栏中的 **Publish**，然后点击 **Request review**。这会将 pull request 标记为可供审阅。
 1. 审阅者在你的 Git 提供方中批准 pull request。
 1. 点击 **Publish**，然后点击 **Merge and publish**。编辑器会合并 pull request，部署你的更改，并把你切换回 deployment branch。

From 1187d9c082aa80cba1b106b79f72dde1bb8426eb Mon Sep 17 00:00:00 2001
From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Date: Mon, 28 Sep 2026 08:25:03 -0700
Subject: [PATCH 2/2] Apply suggestion from @ethanpalm

---
 editor/review.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/editor/review.mdx b/editor/review.mdx
index c5c850137..4d7d9cd65 100644
--- a/editor/review.mdx
+++ b/editor/review.mdx
@@ -42,7 +42,9 @@ To point a teammate at a specific page on a branch, click <Icon icon="ellipsis"
 
 When your branch has a pull request, the publish menu shows its changed files and review status, like **Draft in progress**, **Review required**, **Changes requested**, or **Approved**. Click **View request** to open the pull request in your Git provider.
 
-If the branch still has unresolved comment threads, the publish menu shows a warning with the number of open comments in place of **Ready to publish** or **Approved**. You can still merge and publish. The warning reminds you to resolve feedback first.
+<Tip>
+  If the branch has unresolved comment threads, the publish menu shows a warning with the number of open comments in place of **Ready to publish** or **Approved**. You can still merge and publish. The warning reminds you to resolve feedback first.
+</Tip>
 
 1. Click **Publish** in the top bar, then click **Request review**. This marks the pull request ready for review.
 1. Reviewers approve the pull request in your Git provider.