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

# GitHub

> Connect GitHub to work with repositories, issues, and pull requests

![GitHub integration](https://mintcdn.com/adapt-fa4ae803/TqVXLLIw_8VWNrel/images/integrations/github.png?fit=max\&auto=format\&n=TqVXLLIw_8VWNrel\&q=85\&s=87d2b9c37067f072470ca562807d7675)

Connect Adapt to GitHub to read code, analyze repositories, and understand your development workflow.

## Setup

**1. Go to Integrations**

Navigate to **Settings > Integrations > GitHub**

**2. Install GitHub App**

Click **Connect** to install the Adapt GitHub App

**3. Select repositories**

Choose which repositories Adapt can access

### Permissions

The GitHub App requests:

* **Read access**: Code, issues, PRs, commits, actions
* **Write access**: Issues, PR comments (for creating issues and commenting)

## Capabilities

Adapt can access your GitHub data through its sandbox environment, using the
GitHub CLI (`gh`) and REST API. Open PRs, review code, and more.

![GitHub and Slack integration](https://mintcdn.com/adapt-fa4ae803/w3unAW-Ua-45-ZG7/images/integrations/github-slack.png?fit=max\&auto=format\&n=w3unAW-Ua-45-ZG7\&q=85\&s=5948a303fedcb524683f95093548f9d2)

### Examples

Understand your codebase:

```
Can you explain how OAuth login works in our app.
```

Open up PRs to add new features:

```
Please open a PR to add Microsoft as a login method for our app.
```

With Linear connected, open a PR that closes a Linear issue:

```
Please open a PR for ENG-654
```

## Automated PR reviews

Once GitHub is connected, Adapt reviews your pull requests automatically. When a PR is opened — or a draft is marked ready for review — Adapt reads the diff and posts a review straight to GitHub, no @-mention required.

Each review includes:

* **Confidence Score (0–5)** — how safe the change is to merge at a glance.
* **Summary** — what the PR does and whether it's correct.
* **Important Files Changed** — a per-file overview of what changed and any concerns.
* **Inline findings** — actionable comments anchored to specific lines in the diff.

Adapt reacts with 👀 when it starts, skips draft PRs until they're ready, and never reviews bot-authored PRs (including its own). Reviews post as real GitHub reviews, so Adapt appears in the **Reviewers** sidebar.

To ask a follow-up, @-mention Adapt in a PR comment or reply inside one of its inline review threads. Adapt picks the conversation back up with full context on the PR.

### Re-run a review after new commits

Adapt reviews each PR automatically once. New pushes don't trigger another full review, so you decide when a fresh pass is worth running. To re-review the PR's latest commit, either:

* Click **↻ Re-run review** in the footer of Adapt's review (requires being signed in to Adapt), or
* Post a PR comment containing only `@adaptcom review`. Other @-mentions start a conversation instead of a full review.

The re-run reviews the current head commit, refreshes the confidence score, and updates Adapt's existing review in place. The footer's **Reviewed** link shows exactly which commits the latest pass covered. A given commit can be re-reviewed at most once every 10 minutes.

### Gate merges with the Adapt Review check

Each automated review runs as a GitHub check named **Adapt Review** on the PR's head commit. The check passes when the review's confidence score is 3/5 or higher, fails below that, and concludes as neutral when a review is skipped or doesn't produce a verdict — neutral never blocks a merge.

To require it before merging:

1. In your repository, go to **Settings** > **Rules** > **Rulesets** and create a branch ruleset targeting your default branch.
2. Enable **Require status checks to pass**.
3. Click **Add checks** and select **Adapt Review**.

The merge button stays disabled until the check passes. Bot-authored PRs and cancelled runs conclude as neutral, so the required check never leaves a PR stuck.

GitHub evaluates required checks against the PR's latest commit, and pushes don't start a new **Adapt Review** check on their own. If you push after the first review, [re-run the review](#re-run-a-review-after-new-commits) to run the check on the new head commit before merging.

> [!NOTE]
>
> Automated reviews run for repositories your GitHub installation can access. If you connected GitHub before this shipped, reconnect so Adapt picks up pull request events.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.