ci(qa): upsert Mantis PR comments by marker · openclaw/openclaw@e387764
steipete
·
2026-05-04
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -377,9 +377,9 @@ messages, and other bulky evidence stay in the Actions artifact.
|
377 | 377 | Production workflows should post those comments with the Mantis GitHub App, not |
378 | 378 | with `github-actions[bot]`. Store the app id and private key as |
379 | 379 | `MANTIS_GITHUB_APP_ID` and `MANTIS_GITHUB_APP_PRIVATE_KEY` GitHub Actions |
380 | | -secrets. The workflow resolves the bot login from the GitHub App token, updates |
381 | | -an existing Mantis-owned comment when one exists, and creates a new Mantis-owned |
382 | | -comment instead of rewriting older `github-actions[bot]` comments. |
| 380 | +secrets. The workflow uses a hidden marker as the upsert key, updates that |
| 381 | +comment when the token can edit it, and creates a new Mantis-owned comment when |
| 382 | +an older bot-owned marker cannot be edited. |
383 | 383 | |
384 | 384 | The PR comment should be short and visual: |
385 | 385 | |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
