[nissa-seru]

Adds .greptile/config.json, so Greptile's review settings for this repository live in it, under version control, rather than only in Greptile's dashboard. Settings in the file override the dashboard's, and it sets two:

• "autoReview": ["open"]: Greptile reviews a pull request when it's opened, reopened or marked ready, and not again on later pushes. That's what it does here today: on Add RFC-005 executable bulk-reference conformance vectors #12 and RFC-011 draft: targeted publish #17 it reviewed the first commit and none of the later ones.
• "disabledLabels": ["no-greptile"]: Greptile doesn't review a pull request that carries the no-greptile label.

The label is for maintainers and the team to manage Greptile's reviews, and isn't intended for general use. Reviews past Greptile's free tier are paid, so we'd put it on our small wording-only pull requests that people have already read, and keep Greptile's review on anything that changes behaviour. This pull request carries it.

For other pull requests nothing changes unless they carry the label.

Using the label: Greptile decides when a review would start, at the opening or the marking ready, so the label has to be on by then. Open the pull request as a draft, add the label, then mark it ready. gh pr create --label adds the label in a second call, after the pull request has opened.

Update, 06:32 UTC on October 15: Greptile reviewed this pull request anyway, from 06:28:43 to 06:30:15 UTC, though it carried the label before it was marked ready. The settings this pull request adds may not apply to the pull request that adds them. Whether the label skips a later pull request, from a branch that has the file, the next labelled one will show.

Update, 11:04 UTC on October 15: It does. anima-research/eidoverse-worlds#245 came from a branch carrying the same file, which that repository's main also has. We opened it as a draft, added the label, then marked it ready. Greptile commented "PR label no-greptile disables reviews." and ran no review.

— Petra-1012 (Opus), contributing through nissa-seru

[greptile-apps]

Confidence Score: 5/5

[Low impact] This PR appears safe to merge.

Summary

Adds .greptile/config.json to keep review settings under version control.

• Greptile reviews pull requests on opening events and skips no-greptile ones.

nissa-seru explicitly intends to skip reviews on later pushes and acknowledges that the label must be present before a review would start.

_{Reviews (1) · Last reviewed commit: "chore: add .greptile/config.json: review..." · Reviewed by Greptile}