From aaff7fdfeb4a50d7df6fe580aac3e5457ef9d6a1 Mon Sep 17 00:00:00 2001
From: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Date: Fri, 12 Jun 2026 00:01:31 -0700
Subject: [PATCH] Clarify polling reset comment in ChecksPanel

Update the comment to accurately refer to the entry refresh rather
than a forced fetch establishing a fresh baseline.
---
 src/renderer/src/components/right-sidebar/ChecksPanel.tsx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/renderer/src/components/right-sidebar/ChecksPanel.tsx b/src/renderer/src/components/right-sidebar/ChecksPanel.tsx
index 532ac03ec6a..ce6d0acea24 100644
--- a/src/renderer/src/components/right-sidebar/ChecksPanel.tsx
+++ b/src/renderer/src/components/right-sidebar/ChecksPanel.tsx
@@ -1920,8 +1920,8 @@ export default function ChecksPanel(): React.JSX.Element {
     const refreshComments =
       prNumber !== null && (commentsFetchedAt === undefined || commentsFetchedAt < cutoff)
 
-    // Reset polling attention state so the forced fetch's signature establishes
-    // a fresh baseline rather than colliding with the previous PR's backoff.
+    // Reset polling attention state so this entry refresh establishes a fresh
+    // baseline rather than colliding with the previous PR's backoff.
     pollIntervalRef.current = CHECKS_PANEL_BASE_POLL_INTERVAL_MS
     prevChecksRef.current = ''
     handleEntryRefresh({ refreshChecks, refreshComments })