From ef86b697b3e403a34ddf405426f441d808b2f2c0 Mon Sep 17 00:00:00 2001
From: Jorge Calvar <jorge.calvar@databricks.com>
Date: Tue, 9 Jun 2026 16:09:15 +0200
Subject: [PATCH 1/2] ci: post evals-monitor link comment on new PRs
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Add a workflow that comments once on each opened/reopened PR with a small
link to the evals-monitor PR page, where the author can start an eval.
This replaces the direct CI-trigger approach (see closed #428): GitHub
Actions runners can't reach the dogfood.staging workspace, so the app —
which runs inside dogfood — performs the actual trigger instead.

Co-authored-by: Isaac
Signed-off-by: Jorge Calvar <jorge.calvar@databricks.com>
---
 .github/workflows/eval-pr-comment.yml | 48 +++++++++++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 .github/workflows/eval-pr-comment.yml

diff --git a/.github/workflows/eval-pr-comment.yml b/.github/workflows/eval-pr-comment.yml
new file mode 100644
index 00000000..dfff78e1
--- /dev/null
+++ b/.github/workflows/eval-pr-comment.yml
@@ -0,0 +1,48 @@
+name: Eval PR Comment
+
+# Posts a small comment on every new PR with a link to the evals-monitor app,
+# where the author can start an eval for their PR. We post a link rather than
+# triggering the job from CI because GitHub Actions runners cannot reach the
+# dogfood.staging workspace (network perimeter).
+on:
+  pull_request:
+    types: [opened, reopened]
+    branches: [main]
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  post-eval-link:
+    name: Post eval link comment
+    runs-on:
+      group: databricks-protected-runner-group
+      labels: linux-ubuntu-latest
+    steps:
+      - name: Post eval link comment
+        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7.0.1
+        with:
+          script: |
+            const marker = "<!-- pr-eval-link -->";
+            const { owner, repo } = context.repo;
+            const issue_number = context.issue.number;
+            const url = `https://evals-monitor-6051921418418893.staging.aws.databricksapps.com/prs/appkit/${issue_number}`;
+
+            // Idempotent: skip if we've already commented on this PR.
+            const comments = await github.paginate(github.rest.issues.listComments, {
+              owner,
+              repo,
+              issue_number,
+              per_page: 100,
+            });
+            if (comments.some((c) => c.body?.includes(marker))) return;
+
+            const body = `${marker}\n> 🧪 &nbsp;**Run evals on this PR** &nbsp;·&nbsp; [**Start eval →**](${url})`;
+
+            await github.rest.issues.createComment({
+              owner,
+              repo,
+              issue_number,
+              body,
+            });

From 166311300f33085f6c8f1e6699be8a7ba3c79a68 Mon Sep 17 00:00:00 2001
From: Jorge Calvar <jorge.calvar@databricks.com>
Date: Tue, 9 Jun 2026 16:29:28 +0200
Subject: [PATCH 2/2] ci: refine eval PR comment (microscope emoji, 'Go to
 Evals Monitor' link)

Co-authored-by: Isaac
Signed-off-by: Jorge Calvar <jorge.calvar@databricks.com>
---
 .github/workflows/eval-pr-comment.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/eval-pr-comment.yml b/.github/workflows/eval-pr-comment.yml
index dfff78e1..9f88e20a 100644
--- a/.github/workflows/eval-pr-comment.yml
+++ b/.github/workflows/eval-pr-comment.yml
@@ -38,7 +38,7 @@ jobs:
             });
             if (comments.some((c) => c.body?.includes(marker))) return;
 
-            const body = `${marker}\n> 🧪 &nbsp;**Run evals on this PR** &nbsp;·&nbsp; [**Start eval →**](${url})`;
+            const body = `${marker}\n> 🔬 &nbsp;**Run evals on this PR** &nbsp;·&nbsp; [**Go to Evals Monitor →**](${url})`;
 
             await github.rest.issues.createComment({
               owner,