mirror-canary.git/.github/mergify.yml, branch rollingCanary repo for the mirror pipeline Rollout 1a — App-token end-to-end test target. Safe to delete after Rollout 1a verification. (mirror of https://github.com/vyos/mirror-canary.git)
https://git.amelek.net/vyos/mirror-canary.git/atom?h=rolling2026-05-26T08:15:17+00:00fix(canary): add explicit local pull_request_rule to register with Mergify2026-05-26T08:15:17+00:00Yuriy Andamasovyuriy@vyos.io2026-05-26T08:15:17+00:00urn:sha1:4ee3b7c711960234577ea15d954f99a2381da00c
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)
fix(canary): move Mergify config to .github/mergify.yml (org convention)2026-05-26T06:13:56+00:00Yuriy Andamasovyuriy@vyos.io2026-05-26T06:13:56+00:00urn:sha1:f7980601779c2ccfc08fcdb657a25ad49f98cf2e
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)