From c6aa8f6e83641fcb7d1afa9fce7fc7092d7914b8 Mon Sep 17 00:00:00 2001
From: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Date: Tue, 26 May 2026 11:23:30 -0700
Subject: [PATCH] Remove ready-to-merge badge from checks panel (#2846)

---
 src/renderer/src/components/right-sidebar/ChecksPanel.tsx | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/src/renderer/src/components/right-sidebar/ChecksPanel.tsx b/src/renderer/src/components/right-sidebar/ChecksPanel.tsx
index 51070a168..9773c6d21 100644
--- a/src/renderer/src/components/right-sidebar/ChecksPanel.tsx
+++ b/src/renderer/src/components/right-sidebar/ChecksPanel.tsx
@@ -1424,14 +1424,11 @@ export default function ChecksPanel(): React.JSX.Element {
     if (activeReviewClassification.needsResponse) {
       badges.push('Needs response')
     }
-    if (activeReviewClassification.readyToMerge) {
-      badges.push('Ready to merge')
-    }
     // Why: viewer/author/requestedReviewer signals are not wired into the
     // ChecksPanel call site yet, so `state` and `requested` would mis-classify
     // every PR (collapsing to 'teammate'). Suppress those badges until the
-    // inputs are available; needs-response / ready-to-merge work from PR
-    // metadata alone and remain accurate.
+    // inputs are available; needs-response works from PR metadata alone and
+    // remains accurate.
     return badges
   }, [activeReviewClassification])