@@ -318,10 +318,9 @@ This schema is the handoff between scenario code and GitHub comments:
318318```
319319320320Artifact `path` values are relative to the manifest directory. `targetPath`
321-values are relative paths inside the uploaded Actions artifact bundle. Mantis
322-must not publish evidence to Git branches; Git history is not artifact storage.
323-The publisher rejects path traversal and skips entries marked
324-`"required": false` when optional previews or videos are unavailable.
321+values are relative paths under the configured Mantis R2/S3 artifact prefix. The
322+publisher rejects path traversal and skips entries marked `"required": false`
323+when optional previews or videos are unavailable.
325324326325Supported artifact kinds:
327326@@ -334,11 +333,20 @@ Supported artifact kinds:
334333- `report`: Markdown report.
335334336335The reusable publisher is `scripts/mantis/publish-pr-evidence.mjs`. Workflows
337-call it with the manifest, target PR, artifact root, comment marker, Actions
338-artifact URL, run URL, and request source. The workflow uploads the declared
339-files through `actions/upload-artifact`; the publisher builds a summary-first PR
340-comment that links to that artifact and lists the bundled file names. It never
341-commits or pushes evidence files.
336+call it with the manifest, target PR, artifact target root, comment marker,
337+Actions artifact URL, run URL, and request source. It uploads declared artifacts
338+to the configured Mantis R2/S3 bucket, builds a summary-first PR comment with
339+inline images/previews and linked videos, then updates the existing marker
340+comment or creates one. The workflows publish to `openclaw-crabbox-artifacts`
341+with public URLs under `https://artifacts.openclaw.ai`. They provide bucket,
342+region, and public URL values directly. The reusable publisher requires:
343+344+- `MANTIS_ARTIFACT_R2_ACCESS_KEY_ID`
345+- `MANTIS_ARTIFACT_R2_SECRET_ACCESS_KEY`
346+- `MANTIS_ARTIFACT_R2_BUCKET`
347+- `MANTIS_ARTIFACT_R2_ENDPOINT`
348+- `MANTIS_ARTIFACT_R2_REGION`
349+- `MANTIS_ARTIFACT_R2_PUBLIC_BASE_URL`
342350343351You can also trigger the status-reactions run directly from a PR comment:
344352@@ -628,11 +636,10 @@ after the new secret has been stored.
628636629637Mantis workflows should upload the full evidence bundle as a short-lived Actions
630638artifact. When the workflow is run for a bug report or fix PR, it should also
631-upsert a comment on that bug or fix PR with a short summary and a link to the
632-Actions artifact. Do not post the primary proof only on a generic QA automation
633-PR. Do not use Git branches, tags, or commits as Mantis artifact storage. Raw
634-logs, screenshots, recordings, observed messages, and other bulky evidence stay
635-in the Actions artifact.
639+publish redacted inline media to the configured Mantis R2/S3 bucket and upsert a
640+comment on that bug or fix PR with inline before/after screenshots. Do not post
641+the primary proof only on a generic QA automation PR. Raw logs, observed
642+messages, and other bulky evidence stay in the Actions artifact.
636643637644Production workflows should post those comments with the Mantis GitHub App, not
638645with `github-actions[bot]`. Store the app id and private key as
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。