summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2026-06-01T8943: base_branches -> .* (match all); drop stale 1c current entry (#7)HEADproductionYuriy Andamasov
Replace the explicit trunk/LTS base_branches list with the .* regex so it matches all non-default base branches and the post-1c `current` entry no longer needs maintenance. Default branch is always reviewed regardless. 🤖 Generated by [robots](https://vyos.io)
2026-06-01T8943: tell CodeRabbit about the 1c current->rolling/production branch swap (#6)Yuriy Andamasov
Post-rollout-1c, repo AGENTS.md files still describe the pre-1c layout (reusables pinned @current, 'current (rolling)'), biasing CodeRabbit toward stale @current suggestions and flagging the canonical @production refs + the mirror caller's intentional permissions: contents: read. Add a .github/workflows/** path_instruction with the post-1c facts. 🤖 Generated by [robots](https://vyos.io)
2026-05-30ci: T8943: additive rolling/production base_branches for rollout 1c (#5)Yuriy Andamasov
Tracking: T8943
2026-05-25Merge pull request #4 from vyos/agents-md-T8595Yuriy Andamasov
T8595: add AGENTS.md + Copilot symlink for the vyos-org central CodeRabbit baseline
2026-05-17T8595: clarify inheritance: true behavior in AGENTS.mdYuriy Andamasov
Address CodeRabbit L5 finding (PR #4) — the original wording could be read as saying inheritance: true causes consumers to be excluded from the central baseline, when in fact it enables deep-merge with the baseline. Rewrite to state the merge contract explicitly. 🤖 Generated by [robots](https://vyos.io)
2026-05-16T8595: add AGENTS.md + Copilot symlink for the vyos-org central CodeRabbit ↵Yuriy Andamasov
baseline Authority: T8595 (AGENTS.md fleet rollout). 🤖 Generated by [robots](https://vyos.io)
2026-05-13Merge pull request #3 from vyos/yuriy/t8764-chat-non-org-members-and-bot-ignoresYuriy Andamasov
T8764: allow non-org-member chat + expand bot ignore list
2026-05-13T8764: allow non-org-member chat + expand bot ignore listYuriy Andamasov
Two changes against the org-wide CodeRabbit baseline, motivated by fleet-wide noise from bot-authored PRs and chat lockouts on the public side: 1. `chat.allow_non_org_members: false` → `true`. The `vyos` org is public-facing OSS; external contributors routinely open PRs and the previous setting blocked them from using `@coderabbitai` commands on their own PRs. This does not change auto-review eligibility — review skip rules remain governed by `reviews.auto_review`. 2. `reviews.auto_review.ignore_usernames` extended from `[mergify[bot]]` to the full bot list of `mergify`, `mergify[bot]`, `netlify`, `netlify[bot]`, `claude`, `claude[bot]`. Both the bare login and the `[bot]` suffix are listed because GitHub Apps use the `[bot]` form while service or human accounts may share the bare name; exact-match semantics per the schema mean listing both is required to cover every variant. Net effect on per-repo `.coderabbit.yaml` files: a per-repo override that listed the same bots becomes redundant after this merges. Repos that need to chat-restrict (e.g. private commercial repos) can still set `chat.allow_non_org_members: false` at the repo level since inheritance is per-field. Advances: IS-430
2026-05-12Merge pull request #2 from vyos/yuriy/t8764-ignore-mergify-botYuriy Andamasov
T8764: skip auto-review of mergify[bot] backport PRs
2026-05-12T8764: disable docstring generation org-wide, mirror unit-tests patternYuriy Andamasov
Sets `reviews.finishing_touches.docstrings.enabled: false` to match the already-disabled `unit_tests.enabled: false`. Same rationale: documentation conventions vary too much across the fleet for org-wide auto-generation to be useful — Python repos use Sphinx-style, Go repos use godoc-style, web repos use TSDoc-style. Repos that want CodeRabbit to fill in docstrings opt in via their own `.coderabbit.yaml`. 🤖 Generated by [robots](https://vyos.io)
2026-05-12T8764: lift Org-UI Web dashboard settings into central baselineYuriy Andamasov
Moves every CodeRabbit setting currently configured in the `vyos`-org Web UI dashboard ("Organization UI Settings", precedence #5) into the Central YAML (precedence #3) so the file is the single source of truth for review behavior in the `vyos` org. Once this lands, the Org-UI YAML editor can be cleared and behavior will be unchanged. Why this matters: precedence rules state that Central YAML overrides Organization UI per-field. Today they happen to agree, but any future edit to the Web UI silently drifts from the file. Consolidating into YAML makes drift a code-review-visible event. Lifted fields: * Top-level: - `early_access: false` -> `true` (matches Web UI explicit value) * `reviews:` - `high_level_summary_in_walkthrough: true` - `review_details: true` - `fail_commit_status: true` - `estimate_code_review_effort: false` - `in_progress_fortune: false` * `reviews.auto_review:` - `auto_pause_after_reviewed_commits: 0` * `reviews.finishing_touches:` - `unit_tests.enabled: true` -> `false` (matches Web UI intent; per- repo overrides re-enable where appropriate — testing stacks differ enough that fleet-wide unit-test generation is too noisy) - `simplify.enabled: true` * `reviews.tools:` disabled-linter list for stacks not in our fleet (swiftlint, detekt, rubocop, regal, pmd, circleci, shopifyThemeCheck, brakeman, blinter, smartyLint, emberTemplateLint) * `chat:` - `allow_non_org_members: false` - `integrations.{jira,linear}.usage: disabled` * `knowledge_base:` - `{jira,linear}.usage: disabled` - `mcp.usage: enabled` - `linked_repositories: ansible/ansible` — cross-repo context for the `vyos.vyos` Ansible Galaxy collection. vyos-org specific. After this PR merges: - Clear the Org-UI YAML editor in the CodeRabbit dashboard for the `vyos` org (paste back the empty schema-comment line). The Central YAML now expresses everything that was there. - Sibling change for VyOS-Networks org on its own coderabbit central repo (omits `linked_repositories` per org-specific scope; keeps `early_access: false` since VyOS-Networks Org-UI did not set it). 🤖 Generated by [robots](https://vyos.io)
2026-05-12T8764: skip auto-review of mergify[bot] backport PRsYuriy Andamasov
Adds `mergify[bot]` to `reviews.auto_review.ignore_usernames` in the central `vyos`-org CodeRabbit baseline. Mergify-opened backport PRs are mechanical cherry-picks of an already-reviewed source PR; re-reviewing them adds no signal and burns CodeRabbit's rate-limit budget. Manual `@coderabbitai review` continues to work for the rare case where a maintainer wants a fresh review on a backport PR (e.g. to confirm a conflict resolution was handled correctly after a non-clean cherry-pick). Behavior change observed today (2026-05-12): - vyos/vyos-documentation#2006 (sagitta) and #2007 (circinus) were auto-opened by Mergify as backports of #2005. Both got CodeRabbit auto-reviews despite being byte-equivalent to the already-reviewed source PR. This change suppresses that. Scope: central `vyos`-org baseline only. Mirror change on `VyOS-Networks/coderabbit:.coderabbit.yaml`. Related: T8782 (Mergify central-config rollout) — Mergify is the generator of these PRs; this is housekeeping on the CodeRabbit side. 🤖 Generated by [robots](https://vyos.io)
2026-05-09general: T8765: add central CodeRabbit baselineYuriy Andamasov