docs(review): Greptile is not a merge requirement — trial credits are exhausted - #43
Merged
Merged
Conversation
… exhausted The protocol document still named Greptile the required automated status gate and told agents not to merge while its review was pending. That requirement cannot be satisfied and would block every merge indefinitely. It also recorded the wrong cause. It said the app was 'likely not installed'; the app IS installed and does respond, with a 50-credit trial-limit notice and zero check runs. Observed on PR #37 on 2026-08-13, and again on PR #42, which carries the notice twice. An uninstalled app is a setup gap; an exhausted quota is a reviewer that answers and says nothing. A quota notice is never a pass. Three claims corrected against measured state: * Greptile as required status check -> withdrawn 2026-08-13, verified against branch protection, which requires exactly test (20), test (22) and Four-path producer conformance * 'Require code owner review: currently required' -> disabled; require_code_owner_reviews is false * the Greptile-premised remediation sequence -> both of its first two steps have already executed, and the outcome is that no reviewer requirement remains at all docs/repository-settings.md already recorded all of this accurately on 2026-08-13. This document had drifted away from its own sibling, which is the defect: two files in one repository disagreeing about whether a merge gate exists. The .greptile/ rules are kept. They are correct and cost nothing while dormant, and credits are the only thing standing between them and running again.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
qmarcelle has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
Reviewer's GuideUpdates the review/merge protocol documentation so that Greptile is correctly described as non-required, reconciles it with the authoritative repository-settings doc, and clarifies the actual governance and agent merge rules now that the Greptile gate has been withdrawn due to exhausted trial credits. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- The Greptile section now mixes current-state guidance with a detailed historical narrative; consider trimming the historical timeline into a short “history” note or moving it elsewhere so the merge protocol stays easy to scan for agents.
- There are multiple “authoritative” references to
docs/repository-settings.md; to avoid future drift, you might explicitly state at the top of this document that it defers torepository-settings.mdfor all settings and only describes agent behavior, reducing repeated cross-check details in individual sections.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The Greptile section now mixes current-state guidance with a detailed historical narrative; consider trimming the historical timeline into a short “history” note or moving it elsewhere so the merge protocol stays easy to scan for agents.
- There are multiple “authoritative” references to `docs/repository-settings.md`; to avoid future drift, you might explicitly state at the top of this document that it defers to `repository-settings.md` for all settings and only describes agent behavior, reducing repeated cross-check details in individual sections.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
qmarcelle has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
qmarcelle has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.github/REVIEW-MERGE-PROTOCOL.mdstill named Greptile the required automated status gate and instructed agents not to merge while its review was pending. That requirement cannot be satisfied, so as written it blocks every merge indefinitely.The cause was also recorded wrong
The document said the Greptile app "is likely not installed on this repository. This is absence, not a failed review."
The app is installed on the organization and does respond. It posts:
…and emits zero check runs. Observed on PR #37 (2026-08-13) and again on PR #42, which carries the notice twice.
The distinction matters. An uninstalled app is a setup gap you can close. An exhausted quota is a reviewer that answers and says nothing — and a quota notice must never be dispositioned as a pass.
Three claims corrected against measured state
Greptile— "Planned (not yet required)"test (20),test (22),Four-path producer conformancerequire_code_owner_reviews: falseEach verified against the API rather than assumed.
This was a document disagreeing with its sibling
docs/repository-settings.mdalready recorded all of it accurately on 2026-08-13 — the credit limit, the withdrawal, the zero check runs on PR #37, and the resulting "no reviewer requirement of any kind." The protocol document had drifted away from it. Two files in one repository disagreeing about whether a merge gate exists is the actual defect; this makes the protocol defer to the settings document, which stays authoritative.What replaces the gate
Nothing is being invented to fill the hole. The document now states the real position: current-head required CI, conversation resolution, normative governance tests, and the release-boundary gates carry merge authorization; Sourcery and the other reviewers are defense-in-depth.
Sourcery does emit a
Sourcery reviewcheck run bound to the current head — the mechanical half of the re-admission bar thatrepository-settings.mdsets. Promoting it is deliberately not done here: that needs its own calibration evidence on the same terms Greptile was held to, andworkspacejson/cli'sREVIEW.mdalready rules the same way.Kept
The
.greptile/rules stay. They are correct, they cost nothing while dormant, and credits are the only thing between them and running again.Not changed
workspacejson/clineeds no equivalent fix — itsREVIEW.mdalready recordsGreptile Reviewas not required "by measured decision."Summary by Sourcery
Update the review and merge protocol to reflect the measured repository state and remove Greptile as an effective merge requirement.
Bug Fixes:
Enhancements:
Documentation: