Skip to content

Docs(PE-1694): describe Greptile auto-approve - #54

Merged
plain-thinh-tran merged 1 commit into
mainfrom
PE-1694/document-greptile-auto-approve
Oct 29, 2026
Merged

plain-thinh-tran merged 1 commit into
mainfrom
PE-1694/document-greptile-auto-approve

Conversation

@plain-thinh-tran

Copy link
Copy Markdown
Contributor

Fixes PE-1694

Adds a short Code Review section to README.md that explains when Greptile auto-approves a PR in this repo.

Why

This PR documents the auto-approve policy next to the rest of the contributor docs, so people know which PRs can merge without a human. It is also the smoke test for that policy: it only touches README.md, so Greptile should approve it on its own after a 5/5 Low risk review.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@plain-thinh-tran plain-thinh-tran self-assigned this Oct 29, 2026
@plain-thinh-tran
plain-thinh-tran requested a review from a team as a code owner October 29, 2026 16:20
@cursor

cursor Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Documentation-only change to README with no runtime or security impact.

Overview
Adds a Code review section to README.md that documents when Greptile can auto-approve PRs: 5/5 score and Low risk.

It also states exceptions—changes under .greptile/ and release Version Packages bot PRs still require a human reviewer because Greptile skips bot-opened PRs.

Reviewed by Cursor Bugbot for commit f7dc6a7. Bugbot is set up for automated code reviews on this repo. Configure here.

@greptile-apps

greptile-apps Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] This documentation-only PR appears safe to merge.

Reviews (1) · Last reviewed commit: "Docs(PE-1694): describe Greptile auto-ap..." · Reviewed by Greptile

@plain-thinh-tran
plain-thinh-tran merged commit 8d5a9ad into main Oct 29, 2026
11 checks passed
@plain-thinh-tran
plain-thinh-tran deleted the PE-1694/document-greptile-auto-approve branch October 29, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant