| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
(TEMPORARY; restored to @production post-canary)
|
|
verified)
|
|
|
|
|
|
(admin-fix GREEN)
|
|
verified: A+B+C pass)
|
|
round-5 re-canary)
|
|
|
|
|
|
Rollout 2 canary verification PASSED (5 sub-tests: workflow_dispatch +
pull_request_target + kill-switch + mirror-skipped high-watermark +
canary-typo guard negative test). Restore the wrapper pin to
@production per Plan Task 3 Step 8.
Comment block updated to describe the canary's steady-state behavior
rather than the per-rollout window (the canary will be repointed
again for future rollouts that need it).
🤖 Generated by [robots](https://vyos.io)
|
|
TEMPORARY canary pin for Rollout 2 verification per Plan Task 3 Step 2.
Original snapshot at /tmp/rollout-2/canary-wrapper-original.yml (was
pinned to @feature/rollout-1-app-tokens, the still-live 1b feature
branch). Plan Task 3 Step 8 restores this to @production after the
canary passes.
🤖 Generated by [robots](https://vyos.io)
|
|
Adds AGENTS.md at repo root and .github/copilot-instructions.md symlink
for GitHub Copilot code review compatibility (per T8595 spec).
🤖 Generated by [robots](https://vyos.io)
|
|
extends-only config left Mergify with check-suites stuck queued (never
processed). Per Mergify dashboard returning 'org home redirect' on the
canary repo URLs, Mergify wasn't seeing these as configured repos.
Adding an explicit (no-op-when-no-label) pull_request_rule to give
Mergify a recognizable trigger surface.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1a-expanded-canary-tests.md A.3 (additional fix mid-execution)
|
|
Mergify check-suite stuck queued with 0 check-runs after we added the
config at .mergify.yml (root). Empirically, this org's prod consumers use
.github/mergify.yml and Mergify processes those correctly. Move the
canary config to the same path + add merge_protections_settings.reporting_method
to match prod convention exactly.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1a-expanded-canary-tests.md A.3 (fixed mid-execution after A.4.3 stall)
|
|
Source canary default branch renamed current → rolling per plan A.1.1.
Wrapper's pull_request_target.branches filter follows.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1a-expanded-canary-tests.md A.1.2
|
|
Plan template's 'permissions: contents: read' is insufficient; reusable
declares contents/pull-requests/issues all write. Existing prod wrappers
use full permissions. Adopt convention. Caught at runs 26422487063,
26422563526, 26422679283 (startup_failure).
|
|
Pin to vyos/.github@feature/rollout-1-app-tokens for Rollout 1a
end-to-end canary verification.
Plan: ~/.claude/plans/2026-05-17-mirror-pipeline-rollout-1a-canary-pair.md Task 3
|
