diff options
| author | Yuriy Andamasov <yuriy@vyos.io> | 2026-05-12 09:29:41 +0300 |
|---|---|---|
| committer | Yuriy Andamasov <yuriy@vyos.io> | 2026-05-12 09:29:41 +0300 |
| commit | 31b3fc6e189dc96de1afcd2f474de63f414265d0 (patch) | |
| tree | 9e827c90d732fae2f2ae34a31669d355b5c38c70 | |
| parent | ca31829cb21fd2d79a883d3c6a098aec6de8ea16 (diff) | |
| download | mergify-31b3fc6e189dc96de1afcd2f474de63f414265d0.tar.gz mergify-31b3fc6e189dc96de1afcd2f474de63f414265d0.zip | |
T8782: set defaults.actions.backport.ignore_conflicts: false
Flip Mergify default from "commit conflict markers and open PR labeled
`conflicts`" to "fail the backport, comment on source PR, create no
destination PR." See in-file comment for the 2026-05-12 incident in
vyos/vyos-documentation (#1994 → #1998/#1999 → conf.py markers merged →
RTD `SyntaxError`) that drove this.
Also fix stale `mergify-config` references in the header comment to
match the repo rename (2026-05-09).
This default is dormant for any repo until it adopts `extends: mergify`
in its own `.mergify.yml`. The ~140 existing per-repo configs from
T8531/T8615 are unaffected by this change.
🤖 Generated by [robots](https://vyos.io)
| -rw-r--r-- | .mergify.yml | 23 |
1 files changed, 21 insertions, 2 deletions
diff --git a/.mergify.yml b/.mergify.yml index 3557c80..029faa6 100644 --- a/.mergify.yml +++ b/.mergify.yml @@ -1,8 +1,8 @@ # yaml-language-server: $schema=https://docs.mergify.com/configuration/file-format/ # Central Mergify configuration for the `vyos` GitHub organization. # -# This file lives at vyos/mergify-config:.mergify.yml and is referenced from -# every vyos/<repo>/.mergify.yml via `extends: mergify-config`. +# This file lives at vyos/mergify:.mergify.yml and is referenced from +# every vyos/<repo>/.mergify.yml via `extends: mergify`. # # Inheritance semantics (verbatim from docs.mergify.com/configuration/sharing): # 1. "The configuration from the specified repository will be loaded and @@ -15,6 +15,25 @@ # 3. "Values in the `shared` key will not be merged and shared between # local and remote configurations." — define YAML anchors locally only. +defaults: + actions: + backport: + # Fail the backport loudly on conflict instead of committing literal + # git conflict markers (<<<<<<< / ======= / >>>>>>>) into the destination + # branch and opening a PR labeled `conflicts`. With this set to false, + # Mergify posts an error comment on the source PR and creates no + # destination PR — the operator handles the conflict manually. + # + # Incident driving this default (2026-05-12): + # vyos/vyos-documentation#1994 was backported via `@Mergifyio backport + # sagitta circinus`. Cherry-pick conflicted in docs/conf.py; Mergify's + # default (ignore_conflicts: true) committed the markers, the resulting + # PRs (#1998, #1999) were merged anyway, and RTD builds on both branches + # failed with `SyntaxError: invalid syntax (conf.py)`. Fix-forwards + # #2000 (circinus) and #2001 (sagitta) removed the markers and + # re-applied the patch correctly. + ignore_conflicts: false + pull_request_rules: - name: Label conflicting pull requests description: Add a label to a pull request with conflict to spot it easily |