Cross-repo reviewsbeta
Link related repositories so an AI Review can check shared APIs, schemas, docs, and release work across them.
Cross-repo reviews help Angada catch changes that need a matching update in another repository. Link related repositories so reviews can check shared APIs, schemas, docs, or release work.
Both repositories must be installed in the same Angada GitHub App installation. You need the Admin role to add, edit, or remove repository links. Members can see the configured links but cannot change them. See Roles and permissions for details.
private beta — Cross-repo reviews are available to workspaces with beta access. Contact Angada support to ask whether access is available for your workspace.
How it works
When Angada reviews a pull request in either linked repository, it:
- Checks whether the link applies — Uses the changed files and your guidance to decide whether the linked repository matters for the PR.
- Reads the linked repository when needed — If the link applies, Angada inspects the shared code or contract being changed.
- Posts cross-repo findings — Adds comments to the reviewed PR with citations to affected files in the linked repository.
- Tracks companion fixes — If the reviewed PR description references a PR in the linked repository, Angada updates the finding when the companion PR addresses it.
Cross-repo checks run as part of the normal AI Review. You do not need to start a separate review.
Setting up cross-repo reviews
- Open Settings → Review and select the repository you want to configure.
- Find the Cross-repo reviews card and select Add link.
- Choose the related repository from the picker. Only repositories in the same installation appear.
- Write one or two sentences describing what the repositories share and which changes need coordinated updates, then select Link repository.
Repository links work in both directions. Configure a pair once, and Angada can use the link when reviewing either repository.
Managing repository links
Open the Cross-repo reviews card for either linked repository. Select the pencil icon to update the review guidance, or select the trash icon and confirm to remove the link. Because links work in both directions, editing or removing a link affects reviews in both repositories.
Limits and access
- Each repository can link to up to 5 other repositories. To link more, contact Angada support.
- Guidance is capped at 80 words. Angada reads it verbatim, so concise guidance works best.
- Both repositories must be in the same GitHub App installation. Cross-installation links are not supported.
- Archived repositories, repositories Angada no longer has access to, and repositories that have moved installations show an inaccessible badge and are skipped during review.
Writing good guidance
Guidance tells the reviewer when another repository matters. Name the shared surface and the kinds of changes that need coordination.
Good examples
Frontend and backend share an HTTP API; route or response-shape changes need coordinated updates on both sides.
Both services read from the same Postgres database. Schema migrations and column renames require matching updates in both repositories.
The shared @acme/types package is consumed by both repositories. Breaking changes to exported types require updates wherever they're imported.
What doesn't work
They're related.
This is too vague to be useful. Angada may skip the linked repository or check it too often.
Name the shared surface (API, schema, types, events) and the coordination rule (what changes need a matching update). Specific guidance makes relevance checks more accurate.
Referencing companion PRs
Companion PR references are optional. They let Angada track fixes across repositories, but Angada can find cross-repo issues without them.
When your change spans two repositories, add the companion PR to the reviewed PR description. Angada recognizes two formats:
- Full URL:
https://github.com/myorg/backend/pull/456 - Shorthand:
myorg/backend#456
The referenced PR must be in a repository linked from Cross-repo reviews. Bare #456 shorthand is intentionally not matched because same-repo references cannot be companions.
Editing the PR description re-runs discovery, so you can add or remove companion references at any time.
What you'll see in reviews
Cross-repo findings appear inline on the reviewed PR, the same way other AI Review comments do. Each finding includes a citation pointing at the affected file in the linked repository, so you can jump to the code that needs a matching change.
When the companion PR pushes new commits that address the cited issue, Angada edits the original comment to show the addressed state and the commit SHA that fixed it. If a comment cites multiple cross-repo concerns and only some are addressed, the comment shows a partial resolution so you know what remains.
Troubleshooting
For other supported repository configuration options, see Configure with .angada.yml.