diff options
| author | Yuriy Andamasov <yuriy@vyos.io> | 2026-05-12 11:28:02 +0300 |
|---|---|---|
| committer | Yuriy Andamasov <yuriy@vyos.io> | 2026-05-12 11:28:02 +0300 |
| commit | f15fdee615bf54954a6b066696ae7aff36c080a0 (patch) | |
| tree | b1a990f33fe3d5ddc317d49ae2ebb529320d3ffe | |
| parent | 62fdfa3fda87b12a1caba68ed6428ff8f6936a3a (diff) | |
| download | vyos-1x-f15fdee615bf54954a6b066696ae7aff36c080a0.tar.gz vyos-1x-f15fdee615bf54954a6b066696ae7aff36c080a0.zip | |
T8764: add per-repo CodeRabbit config — Jira VD project scope
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)
| -rw-r--r-- | .coderabbit.yaml | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/.coderabbit.yaml b/.coderabbit.yaml new file mode 100644 index 000000000..1e55ec2e3 --- /dev/null +++ b/.coderabbit.yaml @@ -0,0 +1,33 @@ +# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json +# +# Per-repo CodeRabbit override for vyos/vyos-1x. +# +# Most behavior is inherited from the org-level central baseline at +# https://github.com/vyos/coderabbit/blob/production/.coderabbit.yaml +# (loaded automatically because the central repo is named `coderabbit` +# under the same GitHub org as this repo). +# +# This file is also propagated to the VyOS-Networks mirror of this repo +# (`VyOS-Networks/vyos-1x`) by the gen-1 mirror pipeline. CodeRabbit's +# Atlassian/Jira OAuth grant is attached to the `VyOS-Networks` org only +# (CodeRabbit allows one GitHub-org → Jira-tenant link per install), so: +# - On the vyos source repo (public), `usage: auto` self-disables. No +# Jira context is fetched — there's no OAuth grant on this install. +# - On the VyOS-Networks mirror, `usage: auto` activates Jira (private +# repo + valid OAuth grant) and `project_keys` scopes it to VD. +# +# This makes one file the single source of truth across both orgs. + +knowledge_base: + jira: + # `auto` is the cross-org-safe value: enabled on private/internal + # mirror repos where Jira OAuth is connected, disabled on the public + # source where it is not. Avoids `enabled` (which can produce + # warnings on installs without OAuth). + usage: auto + # Restrict the Jira context CodeRabbit pulls in review summaries to + # the VyOS Dev (VD) project. PRs in this repo reference VD ticket IDs + # in titles (e.g. `T8849: ...` for Phorge tasks that have VD twins), + # so the surface area that matters is VD. + project_keys: + - VD |
