From c40f89414c179918069752ba2f2279622d072b34 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 3 May 2026 17:39:46 +0100 Subject: [PATCH] ci: summarize Mantis bug proof comments Clarify that Mantis screenshot proof belongs on the bug/fix PR and add a top summary to inline evidence comments. --- .../workflows/mantis-discord-status-reactions.yml | 4 +++- docs/concepts/mantis.md | 13 +++++++++---- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/.github/workflows/mantis-discord-status-reactions.yml b/.github/workflows/mantis-discord-status-reactions.yml index 5213ed4ffcf..f06de7e8238 100644 --- a/.github/workflows/mantis-discord-status-reactions.yml +++ b/.github/workflows/mantis-discord-status-reactions.yml @@ -14,7 +14,7 @@ on: default: main type: string pr_number: - description: Optional PR number to receive the QA evidence comment + description: Optional bug or fix PR number to receive the QA evidence comment required: false type: string @@ -334,6 +334,8 @@ jobs: ## Mantis Discord Status Reactions QA + Summary: Mantis reran Discord status reactions against the known queued-only baseline and the candidate ref. The baseline reproduced the bug, while the candidate showed the expected queued -> thinking -> done reaction sequence. + - Scenario: \`discord-status-reactions-tool-only\` - Run: https://github.com/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID} - Artifact: ${ARTIFACT_URL} diff --git a/docs/concepts/mantis.md b/docs/concepts/mantis.md index 7003fa496d8..50d61266e74 100644 --- a/docs/concepts/mantis.md +++ b/docs/concepts/mantis.md @@ -346,16 +346,21 @@ after the new secret has been stored. ## GitHub Artifacts And PR Comments Mantis workflows should upload the full evidence bundle as a short-lived Actions -artifact. When the workflow is run for a PR, it should also publish the redacted -PNG screenshots to the `qa-artifacts` branch and upsert a PR comment with inline -before/after screenshots. Raw logs, observed messages, and other bulky evidence -stay in the Actions artifact. +artifact. When the workflow is run for a bug report or fix PR, it should also +publish the redacted PNG screenshots to the `qa-artifacts` branch and upsert a +comment on that bug or fix PR with inline before/after screenshots. Do not post +the primary proof only on a generic QA automation PR. Raw logs, observed +messages, and other bulky evidence stay in the Actions artifact. The PR comment should be short and visual: ```md Mantis Discord Status Reactions QA +Summary: Mantis reran the reported Discord status-reaction bug against the known +bad baseline and the candidate fix. The baseline reproduced the bug, while the +candidate showed the expected queued -> thinking -> done sequence. + - Scenario: `discord-status-reactions-tool-only` - Run: - Artifact: