Skip to content

Commit f349fb8

Browse files
TakhoffmanTakhoffman
authored
fix(mantis): remove ambiguous github trigger mention (#83179)
1 parent 79212f9 commit f349fb8

6 files changed

Lines changed: 20 additions & 23 deletions

File tree

‎.github/workflows/mantis-discord-status-reactions.yml‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,8 @@ jobs:
4646
github.event_name == 'issue_comment' &&
4747
github.event.issue.pull_request &&
4848
(
49-
contains(github.event.comment.body, '@Mantis') ||
50-
contains(github.event.comment.body, '@mantis') ||
51-
contains(github.event.comment.body, '/mantis')
49+
contains(github.event.comment.body, '@openclaw-mantis') ||
50+
contains(github.event.comment.body, '/openclaw-mantis')
5251
)
5352
)
5453
}}
@@ -128,7 +127,7 @@ jobs:
128127
129128
const normalized = body.toLowerCase();
130129
const requested =
131-
(normalized.includes("@mantis") || normalized.includes("/mantis")) &&
130+
(normalized.includes("@openclaw-mantis") || normalized.includes("/openclaw-mantis")) &&
132131
normalized.includes("discord") &&
133132
normalized.includes("status") &&
134133
normalized.includes("reaction");

‎.github/workflows/mantis-discord-thread-attachment.yml‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,8 @@ jobs:
4646
github.event_name == 'issue_comment' &&
4747
github.event.issue.pull_request &&
4848
(
49-
contains(github.event.comment.body, '@Mantis') ||
50-
contains(github.event.comment.body, '@mantis') ||
51-
contains(github.event.comment.body, '/mantis')
49+
contains(github.event.comment.body, '@openclaw-mantis') ||
50+
contains(github.event.comment.body, '/openclaw-mantis')
5251
)
5352
)
5453
}}
@@ -128,7 +127,7 @@ jobs:
128127
129128
const normalized = body.toLowerCase();
130129
const requested =
131-
(normalized.includes("@mantis") || normalized.includes("/mantis")) &&
130+
(normalized.includes("@openclaw-mantis") || normalized.includes("/openclaw-mantis")) &&
132131
normalized.includes("discord") &&
133132
normalized.includes("thread") &&
134133
(normalized.includes("attachment") ||

‎.github/workflows/mantis-telegram-live.yml‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,8 @@ jobs:
5656
github.event_name == 'issue_comment' &&
5757
github.event.issue.pull_request &&
5858
(
59-
contains(github.event.comment.body, '@Mantis') ||
60-
contains(github.event.comment.body, '@mantis') ||
61-
contains(github.event.comment.body, '/mantis')
59+
contains(github.event.comment.body, '@openclaw-mantis') ||
60+
contains(github.event.comment.body, '/openclaw-mantis')
6261
)
6362
)
6463
}}
@@ -141,7 +140,7 @@ jobs:
141140
142141
const normalized = body.toLowerCase();
143142
const requested =
144-
(normalized.includes("@mantis") || normalized.includes("/mantis")) &&
143+
(normalized.includes("@openclaw-mantis") || normalized.includes("/openclaw-mantis")) &&
145144
normalized.includes("telegram");
146145
if (!requested) {
147146
core.notice("Comment mentioned Mantis but did not request Telegram live QA.");

‎docs/channels/discord.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1631,7 +1631,7 @@ openclaw logs --follow
16311631
// Molty listens to all bot-authored Discord messages.
16321632
allowBots: true,
16331633
mentionAliases: {
1634-
// Lets Molty write "@Mantis" and send a real Discord mention.
1634+
// Lets Molty write a Mantis Discord mention with the configured user id.
16351635
Mantis: "MANTIS_DISCORD_USER_ID",
16361636
},
16371637
botLoopProtection: {

‎docs/concepts/mantis.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ Telegram Web login state is not required for normal Mantis automation.
252252

253253
`Mantis Telegram Desktop Proof` is the agentic native Telegram Desktop
254254
before/after wrapper. A maintainer can trigger it from a PR comment with
255-
`@Mantis telegram desktop proof`, from the Actions UI with freeform
255+
`@openclaw-mantis telegram desktop proof`, from the Actions UI with freeform
256256
instructions, or through the generic `Mantis Scenario` dispatcher. The workflow
257257
hands the PR, baseline ref, candidate ref, and maintainer instructions to Codex.
258258
The agent reads the PR, decides what Telegram-visible behavior proves the
@@ -351,7 +351,7 @@ region, and public URL values directly. The reusable publisher requires:
351351
You can also trigger the status-reactions run directly from a PR comment:
352352

353353
```text
354-
@Mantis discord status reactions
354+
@openclaw-mantis discord status reactions
355355
```
356356

357357
The comment trigger is intentionally narrow. It only runs on pull request
@@ -361,15 +361,15 @@ and the current PR head SHA as the candidate. Maintainers can override either
361361
ref:
362362

363363
```text
364-
@Mantis discord status reactions baseline=origin/main candidate=HEAD
364+
@openclaw-mantis discord status reactions baseline=origin/main candidate=HEAD
365365
```
366366

367367
Telegram live QA can also be triggered from a PR comment:
368368

369369
```text
370-
@Mantis telegram
371-
@Mantis telegram scenario=telegram-status-command
372-
@Mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply
370+
@openclaw-mantis telegram
371+
@openclaw-mantis telegram scenario=telegram-status-command
372+
@openclaw-mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply
373373
```
374374

375375
By default it uses the current PR head SHA as the candidate and runs

‎docs/help/testing.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -335,9 +335,9 @@ start it from the Actions UI through `Mantis Scenario` (`scenario_id:
335335
telegram-live`) or directly from a pull request comment:
336336

337337
```text
338-
@Mantis telegram
339-
@Mantis telegram scenario=telegram-status-command
340-
@Mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply
338+
@openclaw-mantis telegram
339+
@openclaw-mantis telegram scenario=telegram-status-command
340+
@openclaw-mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply
341341
```
342342

343343
`Mantis Telegram Desktop Proof` is the agentic native Telegram Desktop
@@ -346,7 +346,7 @@ freeform `instructions`, through `Mantis Scenario` (`scenario_id:
346346
telegram-desktop-proof`), or from a PR comment:
347347

348348
```text
349-
@Mantis telegram desktop proof
349+
@openclaw-mantis telegram desktop proof
350350
```
351351

352352
The Mantis agent reads the PR, decides what Telegram-visible behavior proves the

0 commit comments

Comments
 (0)