Skip to content

test(pr-steward): escalation canary — DO NOT MERGE - #268

Closed
mashkovd wants to merge 1 commit into
mainfrom
feat/agents-canary
Closed

mashkovd wants to merge 1 commit into
mainfrom
feat/agents-canary

Conversation

@mashkovd

Copy link
Copy Markdown
Member

Purpose — throwaway canary, DO NOT MERGE

Seeds an in-scope (feat/agents-) PR so the in-cluster pr-steward can exercise the one path the first canary tick did not: the escalation send (Telegram ping).

Expected steward behavior across ticks:

  1. Discover this PR (matches head:feat/agents-), label steward:owned.
  2. Post @claude review, launch codex-watch, action=wait.
  3. On a later tick: clean review + mergeable + checks green → label steward:ready-to-merge + send the ready-to-merge Telegram ping to @MCTL_AI_bot (chat 210408407). No merge (merge_mode=never).

This file has zero manifest impact (Helm reads only values.yaml/templates). Close after the escalation tick is observed.

Throwaway PR so an in-scope (feat/agents-) PR exists for the in-cluster
pr-steward to drive one full watch -> ready-to-merge Telegram ping cycle.
No manifest impact; not to be merged (merge_mode=never).
@claude

claude Bot commented May 22, 2026 •

Copy link
Copy Markdown

Claude finished @mashkovd's task in 20s —— View job


Trivial diff — single markdown file with no manifest impact. No P1/P2 findings, good to merge (when ready to close the canary).

@mctl-claude-remote mctl-claude-remote Bot added steward:owned pr-steward owns this PR steward:ready-to-merge pr-steward: clean+green, awaiting human merge labels May 22, 2026
@mashkovd

Copy link
Copy Markdown
Member Author

Escalation canary PASSED (tick 20260522T161147Z on image 0.2.3). The App-token GraphQL hang is fixed (mctl-claude-remote #8): the tick fell back to REST for check status, read claude[bot]'s clean verdict, added steward:ready-to-merge, sent one Telegram escalation to the operator, and did NOT merge (merge_mode=never). Closing this throwaway canary PR — it was never meant to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant