BetaMulti-tenantSingle-tenant
Cross-repo code review extends Qodo’s code review to catch breaking changes across repository boundaries before they reach production. In distributed systems, these are the hardest bugs to find: a function signature change in a shared library, an API contract shift, or a schema evolution can all pass single-repository review cleanly because the reviewer has no visibility into the other repositories in the relationship.
Teams define relationships between repositories, and every relevant pull request (PR) is reviewed across repository boundaries automatically. Relationships can span Git providers, so teams working across multiple platforms are covered by a single review process.
How cross-repo code review works
- PR opens: A developer opens a PR in a repository with a defined relationship.
- Qodo identifies connected repositories: Qodo identifies the connected repositories in the relationship.
- Agent traces impact: The agent reads the related repositories and traces the impact in both directions: code that depends on the change, and code in the PR that may conflict with the other repository (for example, by passing the wrong parameters).
- Finding surfaces: If a breaking change is detected, a
Cross-repoconflict finding appears in the PR with a direct link to the affected lines in the related repository. - Developer acts: The developer reviews the impact and decides how to proceed: update their changes, coordinate with the affected team, or accept the breaking change.
When a cross-repo code review runs
When you add a relationship, Qodo analyzes both repositories and classifies the type automatically. It uses that context to determine what to check on every subsequent PR. You do not need to configure triggers. A review runs when a PR modifies a component covered by a defined relationship, for example:- An exported function or class in a shared library or SDK.
- A REST API endpoint signature or response contract.
- A database schema or data model consumed by other services.
- An infrastructure or configuration file used across repositories.
- A pipeline or build artifact consumed downstream.
Relationship types
When Qodo classifies a relationship, it assigns one of the following types. The type is informational and does not change what the agent checks. The agent uses the full relationship context to detect breaking changes.| Type | Description |
|---|---|
| Code | One repository imports, calls, or depends on code exported by the other, such as a shared library, SDK, or utility package. |
| Service | One repository calls an API or service exposed by the other, such as a frontend calling a backend REST API. |
| Data | Both repositories share a database, schema, or data store, such as two services reading from the same database. |
| Pipeline | One repository depends on a build artifact, container image, or pipeline output produced by the other. |
| Other | The relationship does not fit one of the above types. |
Where cross-repo findings appear
Cross-repo findings appear alongside standard Qodo review findings in the PR, tagged asCross-repo.
Next steps
- To define relationships between your repositories, see Manage cross-repository relationships.
- To view and manage your repositories and installations, see Manage code review across repositories.
- To monitor cross-repo findings across your organization, see Monitor organization-wide PR findings.