Skip to content

config: enable CodeRabbit Multi-Repo Analysis #586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rsoaresd wants to merge 2 commits into
base: master
Choose a base branch
from
+12 −0
Open

config: enable CodeRabbit Multi-Repo Analysis #586

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7e62efb
config: enable CodeRabbit Multi-Repo Analysis
rsoaresd Mar 19, 2026
0b27c88
Merge branch 'master' into coderrabit_multi_repo_r
rsoaresd Mar 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .coderabbit.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
inheritance: true
knowledge_base:
linked_repositories:
- repository: 'codeready-toolchain/toolchain-common'
Copy link
Contributor

@mfrancisc mfrancisc Mar 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

even here probably changes we do in registration service should be compatible with host-operator logic, but I guess it's fine to start with toolchain-common.

instructions: >
toolchain-common contains shared controllers, utilities, and libraries used by registration-service.

When reviewing registration-service changes:
- Check if registration-service is using deprecated or outdated patterns from toolchain-common when newer/better utilities exist.
- Verify behavioral assumptions — if registration-service expects specific return values or side effects from toolchain-common functions, check if that behavior is actually implemented.
- If registration-service duplicates logic that already exists in toolchain-common (pkg/cluster, pkg/condition, pkg/configuration, pkg/status), suggest using the shared implementation instead.
- Flag if registration-service is making assumptions about toolchain-common's internal state or behavior that isn't documented or guaranteed.
Loading