VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling 2026-05-12T09:23:13+00:00 2026-05-12T09:23:13+00:00 Yuriy Andamasov yuriy@vyos.io 2026-05-12T09:23:13+00:00 urn:sha1:b7e665bccda17336d8393e3e769a787722012723 Follow-up to #5191 — the original PR landed without this flag, which means the per-repo `.coderabbit.yaml` was REPLACING the central baseline (`vyos/coderabbit:.coderabbit.yaml`) instead of merging with it. Per https://docs.coderabbit.ai/configuration/configuration-inheritance: > Inheritance is disabled by default. You must explicitly enable it > by adding `inheritance: true`. > > Without inheritance, only the highest-priority source is used. > > Each level with `inheritance: true` merges with its parent. The > chain stops at the first level where `inheritance: false` or unset. Today, every PR review on this repo is using ONLY the contents of `.coderabbit.yaml` (this file) — the central baseline's review profile, tools, chat ACL, finishing-touches settings, etc. are all dropped. Adding `inheritance: true` restores merging. Caught by CodeRabbit's auto-review on the sibling per-repo PR VyOS-Networks/next-js-cpd#1. Did not surface on the original #5191 because CodeRabbit's OSS-security policy ignores YAML config changes from the PR itself on public repos — it reviews against the base branch, which didn't have this file yet. 🤖 Generated by [robots](https://vyos.io) 2026-05-12T08:28:02+00:00 Yuriy Andamasov yuriy@vyos.io 2026-05-12T08:28:02+00:00 urn:sha1:f15fdee615bf54954a6b066696ae7aff36c080a0 Add `.coderabbit.yaml` at repo root with the minimum override needed to (a) opt the VyOS-Networks mirror into the central Jira integration and (b) scope it to the VD (VyOS Dev) project. Cross-org behavior using `usage: auto`: * On `vyos/vyos-1x` (this repo, public): `auto` self-disables on public repos, so no Jira context is fetched. The vyos-org CodeRabbit install has no Atlassian OAuth grant anyway — CodeRabbit allows one GitHub-org → Jira-tenant link per install, and that link is attached to the `VyOS-Networks` org. * On `VyOS-Networks/vyos-1x` (gen-1 mirror, private/internal): `auto` activates the integration and `project_keys: [VD]` restricts the context to VD tickets only — matching the project keys used in release-train work tracked there. Everything else (review profile, tools, chat ACL, path filters, finishing-touches behavior, etc.) continues to inherit from the respective central baseline: - https://github.com/vyos/coderabbit/blob/production/.coderabbit.yaml - https://github.com/VyOS-Networks/coderabbit/blob/production/.coderabbit.yaml Pattern note: this is the canary for the source-of-truth-on-vyos approach. Once it lands clean, the same file (with the same or slightly different `project_keys`) should be mirrored to the other vyos-org source repos that have VyOS-Networks mirrors. 🤖 Generated by [robots](https://vyos.io)