Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.greptile.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

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 following steps will help you connect Greptile with GitHub:
1

Connect to GitHub

Go to Code Providers in the sidebar and click Add Provider, then select GitHub to link your account.
Link GitHub to Greptile
2

Grant Greptile access to repositories

Select the type of repository access you want to grant Greptile.
  • All repository: This grants Greptile access to all current and future repositories both public and private.
  • Only select repositories: At least one repository should be selected for access.
Authorize Greptile in repos

​
GitLab Integration

The following steps will help you connect Greptile with GitLab:
1

Connect to GitLab

Go to Code Providers in the sidebar and click Add Provider, then select GitLab.
Link Greptile to GitLab
2

Generate Personal or Group Access Token on GitLab

  • Log in to your GitLab account.
  • Go to User Settings or Group Settings to generate access token.
  • An access token should have a name, role, expiration usually one year and selected scope as api.
3

Copy GitLab Access Token

Copy the generated GitLab access token and fill it in the access token field and click Submit in Greptile Settings dashboard.
GitLab Access Token
4

Configure Webhook on GitLab

Greptile generates details needed to create a GitLab webhook; a URL, secret token and triggers.
details for gitlab webhook
  • Go to your GitLab account.
  • Click on Webhooks in your GitLab Project/Group Settings.
  • Fill in details for GitLab webhook including the Greptile generated URL, secret token, and check required triggers and click Add webhook.
  • Click on the DONE, I HAVE MADE THE CHANGES button.

​
Repository Selection & Configuration

The following configuration steps are common to GitHub and GitLab:
1

Enable repository indexing by Greptile

  1. Go to your team’s Repositories page
  2. Click Manage Repos
  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.
Manage repositories
2

Configure PR Summary

Customize how Greptile summarizes pull requests:
  • Summary: Choose if you want summaries of changes
  • Include diagrams: Add diagrams for complex changes (sequence, ER, class, or flow — auto-selected based on change type)
  • Confidence scores: Show/hide confidence levels for each PR
Learn more about PR summaries →
PR summary settings
3

Control Review Behavior

Fine-tune what Greptile comments on in Code Review Settings:
  • Strictness: Adjust the slider in the When Greptile Reviews section
  • Comment types: Toggle Syntax, Logic, and Style in What should Greptile comment on?
Learn more about controlling nitpickiness →
Code Review Settings
4

Add Filters

Set when Greptile automatically reviews in Code Review Settings under Fine-tuning:
  • 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 →
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:
1

Create a pull request

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

Wait for review (~3 minutes)

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

Review the feedback

You’ll see a summary of changes, inline comments on issues, and suggested fixes.
pr summary
When issues are spotted, Greptile suggests potential code fixes:
code fixes
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?