GitHub Copilot Code Review Will Start Consuming GitHub Actions Minutes on June 1, 2026 (April 2026)
GitHub on April 27, 2026 said its agentic Copilot code review will begin consuming GitHub Actions minutes on every private-repo pull request from June 1, 2026 — billed alongside new AI Credits. Public repos stay free, but Pro, Pro+, Business, and Enterprise customers will pay on two meters.
GitHub on told developers that its agentic Copilot code review service will begin consuming GitHub Actions minutes on every private-repository pull request starting — the most concrete step yet in GitHub's broader migration of Copilot from flat-rate plans to a credit-and-minutes usage model.
What Happened
In an official changelog post titled “GitHub Copilot code review will start consuming GitHub Actions minutes on June 1, 2026,” GitHub said each Copilot code review will be billed in two ways from that date: as AI Credits under the new usage-based billing model announced earlier this month, and as Actions minutes deducted from a customer's plan entitlement on every review run on a private repo. Public repositories remain free.
The change applies to GitHub Copilot Pro, Copilot Pro+, Copilot Business, and Copilot Enterprise, and includes reviews triggered by non-licensed users on org-billed plans. GitHub said the underlying reason is architectural: Copilot code review now runs on an “agentic tool-calling architecture” on GitHub-hosted runners, which is what makes Actions minutes the natural billing unit. Self-hosted runners and larger GitHub-hosted runners are billed at their existing different rates.
Key Details
- Effective date: June 1, 2026. Until then, Copilot code review continues to draw only from existing premium request unit (PRU) allowances and does not consume Actions minutes.
- Plans affected: Copilot Pro, Pro+, Business, and Enterprise — subscription prices are unchanged, but included usage shrinks under the new credit model.
- Public repos exempt: Actions minutes remain free for public repositories. The new charges apply only to private repos.
- Two-meter billing: Each review consumes both AI Credits (Copilot side) and Actions minutes (runner side) — overage on either is billed at standard rates.
- Larger runners cost more: Customers using GitHub-hosted larger runners or self-hosted infrastructure for Copilot reviews fall under their existing per-minute rates, not the standard pool.
What Developers Are Saying
Reaction on Hacker News — where the announcement reached the front page within hours and drew 100+ comments — is sharply critical. The most upvoted thread captures the worry: as one commenter put it, “You will get less, but pay the same price.” Developers note that Copilot code review already opens an Actions run for every pull request, sometimes doubling the wall-clock time of a review compared with the older inline experience.
Visual Studio Magazine quoted users saying flat-rate predictability was a major reason their organizations bought into Copilot in the first place. On the official GitHub Community discussion for the broader usage-based-billing move, one customer calculated that their team's monthly Copilot spend would jump from under $1,000 to roughly $18,000 at projected agentic-review volumes — a figure GitHub has not publicly disputed. Several enterprise admins are asking GitHub for hard caps on AI Credits at the org level before June 1.
Defenders of the change, including GitHub staff and some commenters on Hacker News, argue that flat-rate pricing for agentic workloads is unsustainable: agents that pull broader repository context, run tools, and re-prompt themselves consume meaningfully more inference and CI compute than 2024-era inline completions, and someone has to pay for it.
What This Means for Developers
If you use Copilot code review on private repositories, you have roughly five weeks to adjust before billing changes. GitHub recommends three concrete actions in its post:
- Audit current Actions usage. Billing managers can pull minute consumption and entitlements from account or org billing settings and confirm headroom.
- Set or revisit Actions spending limits. Budgets can be capped at the user or org level — a hard cap is the only reliable way to prevent runaway agentic-review charges.
- Decide whether to move review traffic to public repos or self-hosted runners. Public repos remain free; self-hosted runners are billed differently and may make sense for high-volume teams.
Open-source maintainers and individual developers working out of public repositories see no direct cost change. Engineering leaders at private-repo orgs should expect Copilot's true monthly cost to become noticeably less predictable from June 1 onward.
What's Next
GitHub has signaled that the June 1 cut-over is part of a larger transition: the usage-based billing announcement from earlier in April applies to all Copilot usage, not just code review. Expect agent runs, agent mode chats, and other premium features to migrate onto AI Credits over the coming months. The community discussion thread is GitHub's stated channel for feedback before the rollout.
Sources
Stay up to date with Doolpa
Subscribe to Newsletter →