Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mashkovd wants to merge 1 commit into from
Closed

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions platform-gitops/services/labs/claude-remote/STEWARD_CANARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# pr-steward escalation canary

Throwaway artifact to exercise the pr-steward escalation path once.

This file exists only so a `feat/agents-canary` PR is in scope for the
in-cluster pr-steward (branch prefix `feat/agents-`). It carries no
configuration and is not read by Helm or any manifest.

Purpose: drive one full watch -> decision -> ready-to-merge Telegram ping
cycle from the in-cluster steward. `merge_mode` is `never`; this PR is not
to be merged. Close it after the escalation tick is observed.