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 /python | |
| 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)
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions
