| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-05-26 | fix(canary): add explicit local pull_request_rule to register with Mergify | Yuriy Andamasov | |
| 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) | |||
| 2026-05-26 | fix(canary): move Mergify config to .github/mergify.yml (org convention) | Yuriy Andamasov | |
| 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) | |||
