Manage code review across repositories

The Repositories page provides engineering leads and admins a centralized view of Qodo’s coverage across the organization. See every Git installation connected to Qodo, monitor connection health across all repositories, turn code review on or off per repository, and manage cross-repo relationships, all without touching configuration files or involving individual developers. To access it, select Repositories from the left navigation menu in the Qodo portal.

​

Manage repositories centrally

As organizations scale across more teams, more repositories, and multiple Git providers, keeping track of where Qodo is active becomes increasingly difficult. Connections can degrade silently, and teams add new repositories without enabling code review. The Repositories page gives you the visibility and control to stay on top of this:

• Visibility: See every Git installation and repository Qodo is connected to, across all providers, in one place. Know exactly where Qodo is running and where it isn’t.
• Connection health: Monitor the health of every installation and repository connection. Spot errors before they cause gaps in review coverage.
• Centralized control: Enable or disable code review per repository without touching repository-level settings, configuration files, or involving the development team.

The page has three tabs: Installations, Repositories, and Relationships.

​

Installations tab

The Installations tab lists all Git integrations connected to Qodo. A Git installation is the fundamental connection unit, representing a single connection that grants Qodo access to a defined set of repositories. Once an installation is complete, Qodo automatically tests the connection to verify both API access and webhook delivery. Use the search bar to find a specific installation by name. To view all repositories under a specific installation, select Manage repos from the three-dot menu, or click the row directly. Connection tests run automatically on a regular schedule. The last test result is shown for each installation.

​

Error types

When an installation shows an error, the error type indicates what went wrong and who can resolve it.

​

Add a new installation

Click New Installation to connect an additional Git account or organization. This takes you to the Integrations page where you can set up a new installation using the guided wizard.

​

Delete an installation

From the three-dot menu, select Delete installation to permanently remove it. Qodo displays a confirmation dialog before deleting.

Azure DevOps: additional step required

If you are deleting your last Qodo installation from an Azure DevOps organization, deleting it in Qodo is not enough to fully remove Qodo from your organization. You must also manually remove the Qodo service principal user. Go to https://dev.azure.com/{org_id}/_settings/users and remove the user from there.

​

Repositories tab

The Repositories tab lists all repositories Qodo has access to, across all your installations and providers. Each repository belongs to a single installation. The Repository status column shows the current connection state for each repository.

​

Filter and search

Use the Filters menu to narrow repositories by installation or provider. Use the Search bar to find a repository by name.

​

Repository sidebar

Click any row to open the sidebar for that repository. From the sidebar you can enable or disable code review for the repository and open it directly in your Git provider. The Cross repository relationships section lists all relationships defined for that repository. For each relationship, you can see the linked repository, relationship type, description, and status. To add or remove relationships, see Manage cross-repository relationships.

​

Relationships tab

The Relationships tab shows all cross-repo relationships defined across your organization. Use it to audit coverage, check relationship status, and manage connections between repositories. Toggle between List and Graph view using the controls at the top left of the tab. In Graph view, click any repository to open the repository sidebar, where you can view its relationships and add new ones. 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 Repository status 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

• To understand how Qodo uses relationships to detect breaking changes across repositories, see Cross-repository code review.
• If your repositories do not appear on this page, see the migration guide for your Git provider.
• To connect a new Git installation, see Connect your Git integration.