copilot-pr-autopilot

Run the review loop with gh CLI authenticated: it triggers Copilot review via GraphQL, triages each open thread as fix, decline, or escalate, applies fixes per repo conventions, replies citing the pushed commit SHA, and re-triggers until no threads await a reply.

Use the GraphQL requestReviewsByLogin mutation with botLogins set to copilot-pull-request-reviewer, which requires repo Triage or Write permission. Without that permission, push a substantive commit so the synchronize event auto-triggers Copilot, or click the UI re-request button.

External authors cannot trigger Copilot via any public API because requestReviewsByLogin is gated on Triage or Write permission. They can run single-iteration mode to address all current findings once, then re-trigger manually via the UI button or a substantive commit push.

The requestReviewsByLogin mutation returns FORBIDDEN when the authenticated user lacks Triage or Write permission on the repository, or when Copilot Code Review is not enabled on the repo or account. Verify permissions with gh api repos/OWNER/REPO --jq .permissions.

Avoid the loop while the PR is still under active design, since findings churn round-over-round and waste cycles. It also does not replace human reviewer feedback, and it aborts automatically if the PR state becomes CLOSED or MERGED.

A recap gate fires deterministically every 10th Copilot review submission, counted from PR history via the API rather than agent memory. The agent then recaps all prior rounds against the original PR scope and chooses CONTINUE, REVERT-AND-SHIP, or HAND-OFF.