Skip to main content
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.
1

Open Code Providers

Go to Code Providers. Click Connect GitHub Cloud or Add Provider, then select GitHub.
GitHub installation page listing accounts and organizations for Greptile Apps
2

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
3

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 Install or Update access.
GitHub App install page with repository access and permissions
4

Link the GitHub organization in Greptile

After you click Install, GitHub automatically returns you to Greptile. Select the GitHub organization, then click Link.You can add more organizations later from Code Providers.
Greptile onboarding screen for selecting a GitHub organization to link
If your GitHub organization is missing from this list, see Troubleshooting: GitHub organization not listed.
5

Enable repositories for review

Select the repositories you want Greptile to review, then click Enable.Use Enable All to turn on all repositories that GitHub granted access to.
Greptile onboarding screen for enabling GitHub repositories for review

GitLab Integration

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

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
2

Open access tokens in GitLab

In GitLab, open your project or group, then go to SettingsAccess tokens.
GitLab project access tokens page with Add new token button
3

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
4

Copy the generated token

Copy the token. GitLab only shows it once.
GitLab page showing the newly created project access token
5

Submit the token in Greptile

Paste the token into the GitLab integration modal, then click Submit.
Greptile GitLab integration modal with token field and Submit button
6

Link the GitLab group

Select the GitLab group, then click Link.
Greptile onboarding screen for selecting a GitLab group to link
7

Enable repositories for review

Select the GitLab repositories you want Greptile to review, then click Enable.Use Enable All to turn on every listed repository.
Greptile onboarding screen for enabling GitLab repositories for review

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 (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
2

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 →
PR Summary settings in Code Review Settings
3

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 →
When Greptile Reviews settings with strictness level and review trigger options
4

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 →
Greptile Comments filter settings with Add Filter button
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?