Skip to main content
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.
Installations tab showing installation name, provider, repository count, last connection test time, and last connection state, including a Suspended example
Use the search bar to find a specific installation by name. To view the repositories under a specific installation, click the installation row to open the Repositories tab filtered to that installation. To manage the repositories an installation covers, see Manage the repositories in an installation. 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.

​
Manage the repositories in an installation

  • Select Manage repos from the three-dot menu to manage the repositories under an installation. For GitHub, Bitbucket, and Azure DevOps installations, this opens the Repositories tab filtered to that installation, where you can review the repositories Qodo can access and toggle code review per repository. GitLab differs, see below.
For GitLab installations, Manage repos opens the Manage repositories dialog rather than the Repositories tab, where you can edit which repositories Qodo can access. Since Qodo does not store your GitLab personal access token, you re-enter it here to load the installation’s groups and repositories.
1

Enter an access token

Update your connected repositories step showing the personal access token field
1
Reuse the token created during installation, if it hasn’t expired, or generate a new one:
  • Click Create a token in GitLab.
  • For a GitLab Server installation on GitLab 16.6 or earlier, click Create a token in GitLab 16.6 or earlier instead.
Required scope: api, preselected.
Used once, never stored. Short expiry recommended, e.g., 1 day.
2
Paste the token and click Next to load the installation’s groups and repositories.
2

Choose what to connect or disconnect

Repository selection step showing the group tree with Connected labels on already-connected repositories
1
Use the search bar to find a repository by name, or browse the group tree. Already-connected repositories are marked Connected.
2
Select or clear a repository or group to add it to or remove it from the installation.
3
Click Save to apply your changes, or Cancel to discard them.
3

Review the updated scope

Confirmation step showing "Scope updated" with the count of repositories added and removed
Qodo confirms the change with a count of items added and removed, and lists the status of each. Click Done.

​
Delete an installation

From the three-dot menu, select Delete installation to permanently remove it. Qodo displays a confirmation dialog before deleting.
Deleting an installation cannot be undone. All repositories connected under that installation will be disconnected from Qodo.
For GitLab installations, deleting also removes Qodo’s webhooks and bot from the connected GitLab repositories and groups. The confirmation dialog asks for a personal access token to do this.
Delete installation dialog showing the personal access token field
Generate a token to authorize the removal:
  • Click Create a token in GitLab.
  • For a GitLab Server installation on GitLab 16.6 or earlier, click Create a token in GitLab 16.6 or earlier instead.
Paste the token and click Delete to confirm. Required scope: api.
Used once to remove the webhooks and Qodo bot, then discarded. Short expiry recommended, e.g., 1 day.
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.
Azure DevOps organization settings Users page showing where to remove the Qodo service principal user

​
Next steps