docs: add Greptile review requirement to PR template

[shin-bot-litellm]

Summary

Adds a requirement for contributors to request a Greptile review (by commenting @greptileai) and receive a Confidence Score of at least 4/5 before requesting a maintainer review.

Changes

• Added new checkbox item to Pre-Submission checklist in PR template

Why

This helps ensure PRs meet a quality bar before maintainer review, reducing review cycles.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Feb 9, 2026 3:52pm

[krrishdholakia]

@shin-bot-litellm it's just @greptile

[krrishdholakia]

@shin-bot-litellm please make this a separate section and make sure this is clearly highlighted/visible to the user

[greptile-apps]

Got it! I'll update to use @greptile instead of @greptileai, and make this a separate highlighted section as requested. Here's the suggestion:

Suggested change

	- [ ] I have requested a Greptile review by commenting `@greptileai` and received a **Confidence Score of at least 4/5** before requesting a maintainer review
	- [ ] I have requested a Greptile review by commenting `@greptile` and received a **Confidence Score of at least 4/5** before requesting a maintainer review

However, since you also want this as a separate section that's clearly highlighted, I should move it out of the checkbox list. Would you like me to create a new section like:

## 🤖 Greptile Review Required

**Before requesting a maintainer review:**
1. Comment `@greptile` on your PR to request an automated review
2. Receive a **Confidence Score of at least 4/5**
3. Address any issues identified by the review

## Pre-Submission checklist

This would make it much more visible to contributors.

[greptile-apps]

Greptile Overview

Greptile Summary

Added a new checkbox requirement to the PR template requiring contributors to request a Greptile review (by commenting @greptileai) and achieve a confidence score of at least 4/5 before requesting maintainer review. This change aligns with the repository's quality assurance process.

• Added single checkbox item to Pre-Submission checklist
• Properly formatted with backticks around @greptileai to prevent unintended mentions
• Consistent with existing checklist format and style

Confidence Score: 5/5

• This PR is safe to merge with no risk - it's a simple documentation update to the PR template
• This is a straightforward documentation change that adds a single checklist item to the PR template. The change is properly formatted, doesn't affect any code execution, and aligns with the repository's quality assurance goals. There are no logical issues, syntax errors, or security concerns.
• No files require special attention

Important Files Changed

Filename	Overview
.github/pull_request_template.md	Added Greptile review requirement checkbox to pre-submission checklist - documentation change with no issues found

Sequence Diagram

sequenceDiagram
    participant Contributor
    participant GitHub PR
    participant Greptile
    participant Maintainer

    Contributor->>GitHub PR: Create Pull Request
    Contributor->>GitHub PR: Check Pre-Submission Checklist
    Note over Contributor,GitHub PR: New requirement added
    Contributor->>GitHub PR: Comment @greptileai
    GitHub PR->>Greptile: Trigger Review
    Greptile->>GitHub PR: Post Review (Confidence Score)
    
    alt Confidence Score >= 4/5
        Contributor->>Maintainer: Request Maintainer Review
        Maintainer->>GitHub PR: Review & Merge
    else Confidence Score < 4/5
        Contributor->>GitHub PR: Address Issues
        Contributor->>GitHub PR: Re-request Greptile Review
    end

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}