vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 09:20:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: configure Mantis bot comment identity (#76839)

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-03 18:20:43 +01:00
committed by GitHub
parent d763b83854
commit 0ff09c4e49
2 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/mantis-discord-status-reactions.yml vendored
View File

@@ -287,7 +287,7 @@ jobs:
ARTIFACT_URL: ${{ steps.upload_artifact.outputs.artifact-url }}
BASELINE_SHA: ${{ needs.validate_refs.outputs.baseline_revision }}
CANDIDATE_SHA: ${{ needs.validate_refs.outputs.candidate_revision }}
MANTIS_COMMENT_BOT_LOGIN: openclaw-mantis-qa[bot]
MANTIS_COMMENT_BOT_LOGIN: ${{ vars.MANTIS_GITHUB_APP_BOT_LOGIN || 'openclaw-mantis-qa[bot]' }}
shell: bash
run: |
set -euo pipefail

8
docs/concepts/mantis.md
View File

@@ -355,9 +355,11 @@ messages, and other bulky evidence stay in the Actions artifact.
Production workflows should post those comments with the Mantis GitHub App, not
with `github-actions[bot]`. Store the app id and private key as
`MANTIS_GITHUB_APP_ID` and `MANTIS_GITHUB_APP_PRIVATE_KEY` GitHub Actions
secrets. The workflow should update an existing Mantis-owned comment when one
exists; if only an older `github-actions[bot]` comment exists, it should create a
new Mantis-owned comment instead of rewriting the legacy bot comment.
secrets. If the app is renamed, set `MANTIS_GITHUB_APP_BOT_LOGIN` as a GitHub
Actions variable to the new bot login, for example `openclaw-mantis[bot]`. The
workflow should update an existing Mantis-owned comment when one exists; if only
an older `github-actions[bot]` comment exists, it should create a new
Mantis-owned comment instead of rewriting the legacy bot comment.
The PR comment should be short and visual: