summaryrefslogtreecommitdiff
path: root/docs/_static/css/code-snippets.css
diff options
context:
space:
mode:
authorYuriy Andamasov <yuriy@vyos.io>2026-05-12 15:43:23 +0300
committerMergify <37929162+mergify[bot]@users.noreply.github.com>2026-05-12 13:29:19 +0000
commitc10b317997fbf50f420479cfe914fe3f03f753e3 (patch)
treeb67d3bc91fd37918ad61bcdf7bf5eaaf7b4f9bab /docs/_static/css/code-snippets.css
parente02da126386fff90fedb50a22a3dcee3f3cdd82d (diff)
downloadvyos-documentation-c10b317997fbf50f420479cfe914fe3f03f753e3.tar.gz
vyos-documentation-c10b317997fbf50f420479cfe914fe3f03f753e3.zip
ci(mergify): disable inherited T-ID title/commit-message checks in this repo
The central baseline at vyos/mergify:.mergify.yml enforces a `T<digits>: <text>` (optional `scope: ` prefix) format on PR titles and every commit's first line — a convention from vyos/vyos-1x and sibling code repos where engineering work tracks against a Phorge task. vyos-documentation has never enforced this. Recent merged PRs use conventional-commits style (`fix(ext): …`, `ci(...): …`, `chore(deps): …`) without an upstream T-ID. After the `extends: mergify` adoption in #2005, the inherited rules started labeling every such PR `invalid-title` and `invalid-commit-title` — pure noise for this repo. Override the two rules by name (Mergify `extends:` semantics: same-name rules in the child REPLACE the parent's). Conditions are constructed to never match (`closed and -closed`), so the `toggle` action always falls into the "remove label" branch and also clears the labels from any PR that picked them up since #2005 merged. 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 3d44fe06e3a82e63b1391424860d76f95bcb97f3)
Diffstat (limited to 'docs/_static/css/code-snippets.css')
0 files changed, 0 insertions, 0 deletions