Cross-Repo Analysis is available on the Enterprise plan.
Overview
Gitar checks your pull request against other repositories in your organization and reports what the change breaks in them. Repositories are related by more than imports. A route path, an event name, or a database column that two repositories have to agree on ties them together, with no shared package between them.Automatic scanning
Every relevant repository in your organization, on every review. Nothing to link.
Unlimited repositories
Unlimited linked repositories, discovered automatically as the organization grows.
Beyond imports
A route, an event name, or an error code ties two repositories together. No shared package required.
Any code host
A service in a GitHub repository and a client in a GitLab repository are asserted against each other.
What it catches
How it works
1
Gitar scans every repository in your organization
It narrows the whole organization down to the repositories your change can reach.
2
Gitar asserts your diff against those repositories
Each impact is verified against your PR before you see it.
3
Gitar reports what breaks and how to keep it working
Each finding is anchored on the line in your PR that changed the contract, names the affected repository and the file and function in it that breaks, and gives your options: keep the change backward compatible, or sequence the rollout so nothing breaks at runtime.A finding says which end to fix. Some are yours to hold in this PR, some are a follow-up in the other repository, and some need a change at both ends to land safely.
Findings are labeled Cross-Repo and post inline like any other code review finding.
Inspect Cross-repo findings
Enterprise organization members can open Dashboard -> Cross-repo to explore repository connections and filter findings by repository, status, or fix location. Only admins can change the feature setting. Admins use the Cross-repo toggle on that page to turn the feature on or off. Turning it off stops future processing and retains its history. Select a finding to inspect the changed and affected repositories. Expand Technical details to see the original finding and suggested fix location.Coverage
Gitar builds a summary of a repository the first time it reviews one, and refreshes it as the repository changes. Nothing to enrol, no backfill to run. Coverage therefore builds as Gitar sees more of your organization. A review opened the day the feature is turned on may not reach everything yet.Repository visibility
A pull request is only ever matched against repositories its readers could already see. A private repository is matched against every repository in your organization. A public one is matched only against other public repositories, plus itself. A public pull request therefore never surfaces a finding that names a private repository or describes its contents.Naming and excluding repositories
Gitar gets this right in most cases. To customize it, commit.gitar/cross-repo.md and describe the relationships in natural language: which repositories depend on this one, what has to stay consistent between them, and what to leave alone.
Related
For interactions between related open PRs, use Cross-PR Analysis. Cross-Repo Analysis checks shared contracts. Knowledge supplies team conventions and connected context, while Functional Validation checks the requirements the PR claims to implement.Code Review
How findings are posted, resolved, and tracked
Insights
Where the Cross-Repo category is reported across your organization
The Gitar Dashboard
The comment the Code Review section lives in
Plans
What each plan includes