If you've been wondering whether GitHub Copilot can tank your pull request, the answer is sitting right there in the documentation — and it might surprise you. Copilot's code review feature always submits as a Comment review, never an Approve, and critically, never a Request Changes. That means it doesn't count toward any required approval thresholds your repository has configured.

What GitHub Actually Says About It

The documentation is refreshingly direct on this point: Copilot reviews are advisory only. The AI flags potential issues, suggests improvements, and raises concerns — but it has no gatekeeping power over your merge button. Your branch protection rules remain entirely in human hands. If you need two approvals to merge, Copilot's review doesn't move that needle one bit.

Why Developers Keep Getting This Wrong

The confusion seems to stem from a few directions. First, Copilot's comments can look alarming — it flags bugs, security issues, and style problems with enough authority that it's easy to treat them as blockers. Second, some teams have configured automation that responds to code review activity in ways that blur the lines. But at its core, GitHub has drawn a clear boundary: Copilot is a collaborator offering perspective, not an automated gatekeeper.

Practical Implications for Your Workflow

This design choice makes sense when you think about it from an infrastructure standpoint. Letting an AI block production deployments would require a level of reliability and accountability that doesn't exist yet — and honestly, probably shouldn't exist until we've got better mechanisms for holding AI systems responsible for their recommendations. As it stands today, Copilot's value is in surfacing issues human reviewers might miss, not in making final calls on code quality.

Key Takeaways

  • Copilot reviews always post as Comments, never Approve or Request Changes
  • Reviews do not count toward branch protection approval thresholds
  • The merge button remains under human control regardless of Copilot activity
  • This is intentional design, documented explicitly in GitHub's official docs

The Bottom Line

Treat Copilot's code reviews like comments from a knowledgeable colleague — useful signals to consider, not gates you must pass. If your team is treating them as blockers without understanding this distinction, it's time to update your internal documentation before someone wastes hours waiting for an AI permission that was never going to come.