Greptile Docs

Appearance

5-Minute Quickstart ​

Fresh

Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first pull request.

This guide covers GitHub/GitLab setup, repository configuration, and your first automated code review.

Installation & Setup ​

GitHub or GitLab users can follow the outlined steps to successfully enable Greptile within their repositories.

Log in to your Greptile account or sign up via email, Google, Github, or GitLab.

Ensure you have the required permissions to allow the AI code reviewer access to all or specific repos. Each platform offers a different procedure for integration.

GitHub App installation ​

The GitHub app gives Greptile access to your repositories and lets it post reviews on pull requests.

Open Code Providers ​

Go to **Code Providers**. Click <kbd>Connect GitHub Cloud</kbd> or <kbd>Add Provider</kbd>, then select GitHub.

!GitHub installation page listing accounts and organizations for Greptile Apps

  <figcaption>Open the Greptile Apps installer in GitHub</figcaption>

Choose a GitHub account or organization ​

In GitHub, choose the account or organization where you want to install **Greptile Apps**. Use **Configure** for an existing installation.

!GitHub Greptile Apps install page with account and organization options

  <figcaption>Choose a GitHub account or organization</figcaption>

Grant repository access ​

Select which repositories GitHub lets Greptile access:

* **All repositories**: Grant access to all current and future repositories in the account or organization.
* **Only select repositories**: Grant access only to selected repositories. Select at least one repository.

Click <kbd>Install</kbd> or <kbd>Update access</kbd>.

!GitHub App install page with repository access and permissions

  <figcaption>Install Greptile Apps in GitHub</figcaption>

After you click <kbd>Install</kbd>, GitHub automatically returns you to Greptile. Select the GitHub organization, then click <kbd>Link</kbd>.

You can add more organizations later from **Code Providers**.

!Greptile onboarding screen for selecting a GitHub organization to link

  <figcaption>Link a GitHub organization to Greptile</figcaption>

Tip

  If your GitHub organization is missing from this list, see [Troubleshooting: GitHub organization not listed](/reference/troubleshooting#github-organization-not-listed).

Enable repositories for review ​

Select the repositories you want Greptile to review, then click <kbd>Enable</kbd>.

Use <kbd>Enable All</kbd> to turn on all repositories that GitHub granted access to.

!Greptile onboarding screen for enabling GitHub repositories for review

  <figcaption>Enable GitHub repositories for review</figcaption>

GitLab Integration ​

The GitLab integration uses a project or group access token. The token must use the Developer role and the api scope.

Open GitLab integration ​

Go to **Code Providers** in Greptile and click **Add Provider**, then select GitLab. Greptile shows the token requirements and a field for the generated token.

!Greptile modal with GitLab integration token instructions

  <figcaption>Add GitLab integration in Greptile</figcaption>

Open access tokens in GitLab ​

In GitLab, open your project or group, then go to **Settings** → **Access tokens**.

!GitLab project access tokens page with Add new token button

  <figcaption>Open GitLab access tokens</figcaption>

Create the access token ​

Create a token with:

* **Token name**: `Greptile`
* **Role**: `Developer`
* **Scope**: `api`
* **Expiration date**: the latest allowed date

!GitLab project access token form with Developer role and api scope selected

  <figcaption>Create a GitLab access token</figcaption>

Copy the generated token ​

Copy the token. GitLab only shows it once.

!GitLab page showing the newly created project access token

  <figcaption>Copy the generated GitLab token</figcaption>

Submit the token in Greptile ​

Paste the token into the GitLab integration modal, then click <kbd>Submit</kbd>.

!Greptile GitLab integration modal with token field and Submit button

  <figcaption>Submit the GitLab token in Greptile</figcaption>

Select the GitLab group, then click <kbd>Link</kbd>.

!Greptile onboarding screen for selecting a GitLab group to link

  <figcaption>Link a GitLab group to Greptile</figcaption>

Enable repositories for review ​

Select the GitLab repositories you want Greptile to review, then click <kbd>Enable</kbd>.

Use <kbd>Enable All</kbd> to turn on every listed repository.

!Greptile onboarding screen for enabling GitLab repositories for review

  <figcaption>Enable GitLab repositories for review</figcaption>

Repository Selection & Configuration ​

The following configuration steps are common to GitHub and GitLab:

Enable repository indexing by Greptile ​

1. Go to your team's **Repositories** page
2. Click **Manage Repos** (or **Enable Repositories** if no repos are enabled yet)
3. Select the repos you want reviewed, then click **Enable Repos** (or use **Enable All**)

To automatically enable future repos, go to **Code Review Settings** and toggle **Auto-enable New Repos**.

!Repo Settings modal for enabling and disabling repositories

  <figcaption>Enable or disable repositories</figcaption>

Configure PR Summary ​

Customize how Greptile summarizes pull requests:

* **PR Summary**: Include a text summary of the changes
* **Confidence Score**: Show confidence levels for each PR
* **Issue Table**: Show important changed files with ratings
* **Sequence Diagram**: Add a diagram of the changes

[Learn more about PR summaries →](/code-review/first-pr-review#pr-summary)

!PR Summary settings in Code Review Settings

  <figcaption>PR summary settings</figcaption>

Control Review Behavior ​

Fine-tune what Greptile comments on in **Code Review Settings**:

* **Strictness Level**: Adjust how often Greptile comments
* **Auto-review on new commits**: Review new commits after a PR is opened
* **Review draft pull requests**: Review drafts before they are marked ready
* **File change limit**: Set the largest PR Greptile reviews automatically

[Learn more about controlling nitpickiness →](/code-review/controlling-nitpickiness)

!When Greptile Reviews settings with strictness level and review trigger options

  <figcaption>When Greptile reviews</figcaption>

Add Filters ​

Set when Greptile comments in **Code Review Settings** under **Greptile Comments**:

* **Labels**: Only review PRs with specific labels (e.g., "needs-review")
* **Authors**: Include/exclude specific developers or bots
* **Branches**: Target specific branches (e.g., main, develop)
* **Keywords**: Trigger on PR title/description keywords

[Learn more about triggers →](/code-review/controlling-nitpickiness#trigger-configuration)

!Greptile Comments filter settings with Add Filter button

  <figcaption>Add review filters</figcaption>

After a repository has been indexed (typically 1-2 hours for very large repos), any new pull/merge request will initiate automated code reviews by Greptile.

Create Your First Test PR ​

Try Greptile on a test pull request to see it in action:

Create a pull request ​

Make a test PR to your indexed repo with some code changes.

Wait for review (~3 minutes) ​

Greptile analyzes your PR with full codebase context and posts a comprehensive review.

!PR Summary

  <figcaption>Greptile PR Comment</figcaption>

Review the feedback ​

You'll see a summary of changes, inline comments on issues, and suggested fixes.

!pr summary

  <figcaption>PR Summary</figcaption>

When issues are spotted, Greptile suggests potential code fixes:

!code fixes

Suggest code fixes

Note

You can trigger a code review manually by tagging @greptileai with a comment. This is helpful for reviewing older PRs from before Greptile was integrated.

What's next? ​

Source

Mirrored from the official Greptile documentation. Self-contained reference copy.