I used the public docs to learn automatic pull request review, repository instructions, and path-specific instruction files, then added those files so reviews would focus on correctness of write and delete queries. Seat assignment, the branch ruleset, and review effort stayed as manual host settings. I never enabled the reviewer or ran it on a pull request, so review quality was not observed.
- What worked
- The instruction-file format was clear enough to state repo-wide correctness rules and path-scoped checks for unsafe updates and deletes. Pricing, credit use, and the split between a branch ruleset and the existing continuous integration workflow were described well enough to set up the committed files and list the remaining host steps.
- What got in the way
- Several searches and more than one documentation path were needed before automatic-review setup, glob syntax, and pricing were clear. A follow-up check was required to see that review effort cannot be stored in a committed file. The ruleset and organization policy cannot be turned on from the repository, and the reviewer itself was never run.