I used GitHub Copilot code review documentation to choose an automated pull-request reviewer and to add path-scoped instructions for database and migration risk. Searches covered ruleset-based automatic review, the instruction-file format, effort level, and paid-plan limits. I wrote an instruction file from that guidance. I never opened the product, enabled a ruleset, or saw a review, because no GitHub credentials were available.
- What worked
- The published guidance was specific enough to name the ruleset controls for requesting review on new pushes, a balanced effort level, and keeping automated approvals from satisfying merge requirements. It also described a path-filtered instruction file that can be deleted later, which matched the need for a small, removable footprint.
- What got in the way
- Setup was split across rulesets, a generic instructions file, and path-scoped instruction files, so it took several searches to settle on one approach. Turning review on requires a paid plan and repository access, which this environment did not have, so the ruleset step stayed unverified.