GitHub Copilot can now approve PRs — and the green check counts
Off by default, but admins can let Copilot's sign-off satisfy required reviews — scoped by file path, dropped on new commits, no accuracy dashboard yet.
Copy markdown
Copilot's approval now satisfies branch protection
GitHub's code-review bot can formally approve a pull request, and that green check now counts toward your repo's required-approvals rule — just like a human's. It's off by default; admins switch it on at the enterprise, org, or repo level.
Whitelist which paths it can sign off on
Repo admins pick exactly which file paths Copilot may approve, so you can let it green-light docs, tests, or config while keeping it away from auth and payments. Enough to unblock a required-review rule on a small or solo repo without handing over critical code.
Push new commits, lose the approval
If anyone pushes after Copilot approves, its approval is dismissed automatically — same as a human reviewer's — so it can't rubber-stamp code it never saw. It's in public preview across Copilot Pro, Pro+, Max, Business, and Enterprise.
The catch: it ships without a scoreboard
GitHub gives you the approver but not the instrumentation to trust it — no built-in view of approval accuracy or how often humans catch what it missed. Reviewers' advice: start on low-risk paths and measure before you widen it.
Elsewhere: Qwen3.8-27B lands as open weights
Qwen shipped Qwen3.8-27B, an Apache-2.0 multimodal (image-to-text) model small enough to self-host and already one of Hugging Face's most-downloaded this cycle — a rare fully-open multimodal you can run and fine-tune yourself.