> ## 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.

# Pull Request Reviews

> Enable repository-level AI reviews for incoming pull requests and track them through the PR review and agent-session surfaces.

# Pull Request Reviews

Pull Request Reviews are repository-level, agent-backed reviews of incoming pull requests.

They are not enabled automatically when you connect a Git provider. The repository itself has to be
configured for review.

## Where To Turn It On

1. Open `Settings` -> `Integrations` -> `Git`
2. Open the integration
3. Open a repository under that integration
4. Enable PR reviews for that repository
5. Pick the review agent if the UI prompts for one

That matches the current repository settings UI and the PR review service in the backend.

## What Happens When A Review Runs

When a configured repository receives a pull request event:

* Cloudgeni creates or updates a review session linked to that PR
* Review history is exposed through `Pull Requests` -> `Reviews`
* The review is stored as an agent-session-backed record, not as a separate system

This matters because the PR review view and the agent session infrastructure are intentionally tied
together in the codebase.

## What It Depends On

* An active Git integration
* A repository with PR reviews enabled
* Working provider-side access and webhook or event delivery

If the repository is connected but PR reviews never appear, check the repository setting first.

## Provider Notes

* GitHub: works through the GitHub integration path
* GitLab: works through the GitLab integration path and project-level webhook model
* Azure DevOps: works through the Azure DevOps integration path

## What To Expect From The Output

Use PR reviews for:

* Security and compliance feedback before merge
* Another pair of eyes on infrastructure changes
* Review history attached to the PR lifecycle

Do not use PR reviews as a substitute for initial repository onboarding. If the repository itself is
not connected and healthy, the review feature has nothing reliable to attach to.

## Related Pages

<CardGroup cols={2}>
  <Card title="Connect Git" icon="code-branch" href="/getting-started/connect-git-provider">
    Start with the provider connection and repository list.
  </Card>

  <Card title="AI DevOps" icon="robot" href="/features/ai-devops">
    Use interactive sessions when you want to drive the change instead of only review it.
  </Card>
</CardGroup>