Skip to main content
Cross-repo analysis is enabled per organization on the Enterprise plan. Contact support to turn it on for your organization.

​
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

No cap, no per-repository slots, no setup as your 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.
Findings are labeled Cross-Repo and post inline like any other code review finding.

​
Coverage

Coverage builds as Gitar sees more of your organization, so a review opened the day the feature is turned on may not reach everything yet.

​
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.
Put the file in your configuration repository to apply it across the organization, or in a single repository to scope it there. When both exist, the organization’s rules load first and the repository’s file adds to them.

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