
When a new installation is added, code review is disabled for all repositories by default. You control which repositories Qodo actively covers.
Connection health
The Connection health column shows the current connection health for each repository.A newly added repository under an already-healthy installation shows Pending until its own connection check completes, rather than inheriting the installation’s status. This reflects the repository’s own state instead of assuming it is healthy.
PR history indexing
Qodo indexes a repository’s merged pull request history in the background to power learning features such as Rule Miner and Relevance. The PR history indexing column is the visibility into that process, showing whether history has finished indexing, is still catching up, or failed. See Understanding PR history indexing for how Qodo uses this history once indexed.Manage code review in bulk
Enable or disable code review for multiple repositories at once from the Repositories tab.1
Select repositories
Select the checkbox next to each repository, or select the checkbox in the table’s top row to select every repository at once.

2
Select an action
Select Enable code review or Disable code review from the bar that appears at the bottom of the table. The action applies immediately to every selected repository.
Repository sidebar
Click any row to open the sidebar for that repository. The sidebar has three sections:- Overview: Enable or disable code review for the repository, and open it directly in your Git provider.
- PR history indexing: Indexing detail for the repository’s pull request history. See PR history indexing detail below.
- Cross repository relationships: All relationships defined for that repository. See Cross repository relationships below.
PR history indexing detail
The repository sidebar’s PR history indexing section shows:When a repository’s status is Not started, indexing starts automatically once the repository’s first pull request is opened.
Cross repository relationships
For each relationship, you can see the linked repository, relationship type, description, and status. To add or remove relationships, see Manage cross-repository relationships.Best practices
- Check connection health regularly: A repository showing an error means Qodo cannot review pull requests in it. Scanning the Connection health column as part of your operational review helps catch a broken connection before it causes gaps in coverage.
- Use filters to audit coverage: Filter by installation or provider to verify that all expected repositories are connected and have code review enabled. This is especially useful after adding a new installation.
- Be deliberate about what you enable: New installations default to code review disabled. Onboard repositories intentionally rather than activating Qodo everywhere at once, so you can track rollout and keep your connection inventory accurate. When code review is disabled, indexing continues so the repository remains available for cross-repo context.
Next steps
- Manage Git installations: Add installations and resolve connection errors.
- Audit cross-repository relationships: Audit cross-repository relationships across your organization.
- Rule Miner: See how PR history indexing turns into rules.
- Relevance: See how PR history indexing helps prioritize findings.