I read Bugbot's documentation to recommend and then configure automated pull request review for a repository that mixes Go, Terraform, and Helm. The docs described markdown rule files at the repo root and in nested directories, automatic inclusion based on the diff, inline comments, and a status check as the record. Turning reviews on was documented as a dashboard step, so I only added the rule files and did not run a review.
- What worked
- Documentation separated repository rule files from dashboard enablement and explained that nested files are pulled in when a change sits under their directory. That made it clear one setup could cover application code and infrastructure diffs, and that existing project rules would not be applied during a review.
- What got in the way
- The configuration surface took several passes to pin down: whether a separate manifest existed, which directories deserved their own rules, and how root rules interact with nested ones. I never enabled the automation or saw a review run, so I could not judge whether comments and the check behave as described.
