From f7980601779c2ccfc08fcdb657a25ad49f98cf2e Mon Sep 17 00:00:00 2001 From: Yuriy Andamasov Date: Tue, 26 May 2026 09:13:56 +0300 Subject: fix(canary): move Mergify config to .github/mergify.yml (org convention) 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) --- .github/mergify.yml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 .github/mergify.yml (limited to '.github') diff --git a/.github/mergify.yml b/.github/mergify.yml new file mode 100644 index 0000000..6faffd8 --- /dev/null +++ b/.github/mergify.yml @@ -0,0 +1,9 @@ +# yaml-language-server: $schema=https://docs.mergify.com/configuration/file-format/ +# Mergify configuration for vyos/mirror-canary (Rollout 1a canary). +# Inherits the central baseline from vyos/mergify:.mergify.yml via extends:. +# Matches the production-consumer convention at .github/mergify.yml (the root +# .mergify.yml path is documented but not picked up by Mergify on this org's +# repos — empirically verified during 1a expansion). +extends: mergify +merge_protections_settings: + reporting_method: check-runs -- cgit v1.2.3