From 4ae7f41a800dc0d712236d893bfd4aeb8a31e980 Mon Sep 17 00:00:00 2001
From: rahim <rahim.alwer@gmail.com>
Date: Thu, 5 Mar 2026 11:24:25 -0800
Subject: [PATCH] fix(ci): reuse diagnosis comment per PR instead of per run
 (#740)

---
 .github/workflows/ci-diagnose.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/ci-diagnose.yml b/.github/workflows/ci-diagnose.yml
index 8cdbae1a..71b5ceeb 100644
--- a/.github/workflows/ci-diagnose.yml
+++ b/.github/workflows/ci-diagnose.yml
@@ -13,7 +13,7 @@ permissions:
   id-token: write
 
 concurrency:
-  group: ci-diagnosis-${{ github.event.workflow_run.id }}
+  group: ci-diagnosis-pr-${{ github.event.workflow_run.pull_requests[0].number || github.event.workflow_run.id }}
   cancel-in-progress: true
 
 jobs:
@@ -70,13 +70,13 @@ jobs:
             5. If the failure is only simple lint/style warnings, keep it brief and generic; do not enumerate every file.
             6. Avoid noise:
             - Do not post redundant comments.
-            - Use one comment per CI run.
-            - If a comment already exists with marker `<!-- ci-diagnosis:run-${{ github.event.workflow_run.id }} -->`, update it instead of creating a new one.
+            - Use one comment per PR.
+            - If a comment already exists with marker `<!-- ci-diagnosis:pr-${{ steps.context.outputs.pr_number }} -->`, update it instead of creating a new one.
             - Do not include stack traces or long command output in comments.
 
             Post or update a single PR comment on #${{ steps.context.outputs.pr_number }} using this template exactly:
 
-            <!-- ci-diagnosis:run-${{ github.event.workflow_run.id }} -->
+            <!-- ci-diagnosis:pr-${{ steps.context.outputs.pr_number }} -->
             ### CI Failure Diagnosis
             - Run: ${{ github.event.workflow_run.html_url }}
             - Commit: `${{ github.event.workflow_run.head_sha }}`