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
Click the Connect button with the GitHub icon to link your GitHub account in the Settings dashboard.
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.
GitLab Integration
The following steps will help you connect Greptile with GitLab:1
Connect to GitLab
Select GitLab in the dropdown button at the top right corner, in the Settings dashboard.
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.
4
Configure Webhook on GitLab
Greptile generates details needed to create a GitLab webhook; a URL, secret token and triggers.
- 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
Ensure you have enabled Greptile to index all or selected repositories.
2
Configure PR Summary
Customize how Greptile summarizes pull requests:
- Summary: Choose if you want summaries of changes
- Include diagrams: Add sequence diagrams for complex changes
- Confidence scores: Show/hide confidence levels for each PR
3
Control Review Behavior
Fine-tune what Greptile comments on:
- Severity threshold: Low (more comments) → High (critical only)
- Comment types: Toggle logic, syntax, and style issues
4
Add Filters
Set when Greptile automatically reviews:
- 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
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.
3
Review the feedback
You’ll see a summary of changes, inline comments on issues, and suggested 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?
- For developers: Learn how to work with Greptile reviews →
- For team admins: Set up team access and permissions →
- Deep dive: Understand the anatomy of a review →