Repository navigation
ci(greptile): stop labelling pull requests for Greptile - #30
Merged
nissa-seru merged 1 commit intoOct 21, 2026
Merged
Conversation
Greptile reviews only pull requests labelled greptile here (.greptile/config.json), and greptile-label.yml gave that label to each open, non-draft pull request past 400 changed lines that didn't carry no-greptile. New pull requests aren't meant to get a Greptile review, of any size, so the workflow goes. It has been disabled in GitHub Actions since 2026-10-21 19:58 UTC. .greptile/config.json stays: it keeps Greptile to labelled pull requests, and its statusCommentsEnabled: false keeps Greptile from commenting on the others. Older pull requests keep their labels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Automated review
Recommendation: merge. The review found nothing of medium or high severity.
Reviewed commit 8082163 with claude-opus-5-5, by reading the code. It did not run the code or look at the checks.
Does this change belong in the project?
It fits the project. The change deletes one repository-maintenance CI workflow and leaves the protocol spec and the Greptile config as they were. The project's documents don't cover review tooling, so this is the maintainers' call, and nothing they state conflicts with it.
3 reasons with sources
- The project is a protocol specification, and its README says nothing about automated review tooling, so removing this workflow touches none of its stated scope. The README covers MCPL's features, SPEC.md, the RFC status and the license. It never mentions CI or Greptile. (README.md)
- The change is one coherent deletion, and the config that limits Greptile to labelled pull requests stays. The config still lists labels ["greptile"] and disabledLabels ["no-greptile"], so a review can still be asked for by adding the label by hand. Nothing else in the repository refers to the deleted workflow. (.greptile/config.json)
- It lowers the maintenance load: a scheduled job with write permission on pull requests goes away. The deleted file ran every 30 minutes with pull-requests: write. Its own comments note that GitHub disables scheduled workflows after 60 days without activity, which is extra upkeep the project no longer has. (.github/workflows/greptile-label.yml)
Findings
No findings of medium or high severity.
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.
Problem
New pull requests aren't meant to get a Greptile review, of any size. Here Greptile reviews only pull requests labelled
greptile(.greptile/config.json), andgreptile-label.ymlgave that label to each open, non-draft pull request past 400 changed lines that didn't carryno-greptile.Changes
.github/workflows/greptile-label.yml. It has been disabled in GitHub Actions since 2026-10-21 19:58 UTC..greptile/config.json. It keeps Greptile to pull requests labelledgreptile, and itsstatusCommentsEnabled: falsekeeps Greptile from commenting on the others.Tests
Not verified
greptilelabel added by hand would still start a review. Nothing in the repository prevents it.Written by Ramona-2416 (Claude Opus 5.5), using the Rookery's tooling.
Description checked and posted by Daniel-2612 (Claude Opus 5.5).