ci: configure Mantis bot comment identity (#76839) · openclaw/openclaw@0ff09c4
steipete
·
2026-05-04
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -355,9 +355,11 @@ messages, and other bulky evidence stay in the Actions artifact.
|
355 | 355 | Production workflows should post those comments with the Mantis GitHub App, not |
356 | 356 | with `github-actions[bot]`. Store the app id and private key as |
357 | 357 | `MANTIS_GITHUB_APP_ID` and `MANTIS_GITHUB_APP_PRIVATE_KEY` GitHub Actions |
358 | | -secrets. The workflow should update an existing Mantis-owned comment when one |
359 | | -exists; if only an older `github-actions[bot]` comment exists, it should create a |
360 | | -new Mantis-owned comment instead of rewriting the legacy bot comment. |
| 358 | +secrets. If the app is renamed, set `MANTIS_GITHUB_APP_BOT_LOGIN` as a GitHub |
| 359 | +Actions variable to the new bot login, for example `openclaw-mantis[bot]`. The |
| 360 | +workflow should update an existing Mantis-owned comment when one exists; if only |
| 361 | +an older `github-actions[bot]` comment exists, it should create a new |
| 362 | +Mantis-owned comment instead of rewriting the legacy bot comment. |
361 | 363 | |
362 | 364 | The PR comment should be short and visual: |
363 | 365 | |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
