> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudgeni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a Git Provider

> Set up GitHub, GitLab, or Azure DevOps the way the current app expects, then enable repository-level workflows from there.

# Connect a Git Provider

Git integrations are organization-scoped. Once connected, repositories from that provider become
available for static analysis, PR reviews, agent sessions, and cloud resource import handoff.

Go to `Settings` -> `Integrations` -> `Git` to start.

## Supported Providers

The current product supports:

* GitHub
* GitLab
* Azure DevOps

Bitbucket is shown in the UI as coming soon and should not be treated as available.

## What The Product Does After Connect

After a successful connection:

* The integration is stored as a Git integration for the organization
* Repositories are available under the integration detail page
* Repository-level settings become available
* PR reviews can be enabled per repository

That last point matters: pull request reviews are not a global toggle.

## Provider-Specific Flow

### GitHub

GitHub is the cleanest path in the current app.

1. Start the GitHub connection from the Git integrations page
2. Install or authorize the Cloudgeni GitHub app
3. Return to Cloudgeni and let repository sync complete
4. Open the integration and verify the repositories you actually want to use

### GitLab

GitLab has a second step after OAuth.

1. Start the GitLab connection
2. Complete OAuth
3. If the integration lands in `PENDING_USER_ACTION`, choose the namespace or project access Cloudgeni should use
4. Return to the Git integrations list when the integration becomes active

The GitLab service code is built around project-level webhook support, so keep your expectations at
the project or repository level rather than a broad group-wide review model.

### Azure DevOps

Azure DevOps also uses a follow-up confirmation flow.

1. Start the Azure DevOps connection
2. Complete the OAuth redirect
3. Finish any follow-up selection or confirmation the integration requires
4. Verify repository availability from the integration detail page

## Turn On Repository Features

Once a provider is connected, open a repository under that integration and decide what you want to
use it for.

Common next steps:

* Enable [Pull Request Reviews](/features/pull-request-reviews)
* Run [Static Analysis](/features/static-analysis)
* Use the repository in an [AI DevOps](/features/ai-devops) session

## What To Check If Something Looks Wrong

* No repositories listed: the provider connected, but the repo selection or provider-side install scope is incomplete
* Integration stuck in a transitional state: refresh the integration list and finish any pending provider-side confirmation
* PR reviews not running: check the repository-level review setting, not just the integration status

## Next

<CardGroup cols={2}>
  <Card title="Pull Request Reviews" icon="git-alt" href="/features/pull-request-reviews">
    Enable automated reviews on the repositories that need them.
  </Card>

  <Card title="Static Analysis" icon="magnifying-glass" href="/features/static-analysis">
    Use the connected repository for Checkov-backed scanning.
  </Card>
</CardGroup>