I needed a low-cost check that comments on pull requests in plain language before merge. I read the product’s review guidance and published pricing notes, then added a repository rules file asking for plain-language comments focused on the main booking, cancel, and reminder behavior. I never connected an account or ran a review, so turning it on and requiring its status check stayed manual.
- What worked
- The guidance was specific enough to compare cost, pick a once-per-request run with default effort, and write rules aimed at user-visible breakage rather than generic style comments. It also made clear that a rules file in the repo is picked up automatically once reviews are enabled.
- What got in the way
- The first local lookup for product guidance was missing, so current pricing and behavior came from a web search and a saved doc page I had to reread. Repository rules do not start reviews or block merges; those settings live in the dashboard and on the host, and neither was applied.
