GitHub Copilot Code Review: Actions Minutes Billing Starting June 1, 2026

GitHub Copilot Code Review Adds Actions Minutes to Billing Starting June 1

GitHub has announced that its Copilot code review feature will begin consuming GitHub Actions minutes starting June 1, 2026 — a significant billing change that affects private repositories across all paid Copilot plans.

How the New Billing Works

Under the updated model, each Copilot code review run will be billed in two ways simultaneously. First, all Copilot usage — including code reviews — will be charged as GitHub AI Credits, the new token-based currency replacing the existing premium request units (PRUs) system. Second, the code review execution itself will consume GitHub Actions minutes from the plan's existing monthly entitlement, since Copilot's agentic review architecture runs on GitHub Actions using GitHub-hosted runners.

Usage beyond the included Actions minutes allotment will be charged at standard GitHub Actions rates. Organizations already monitoring their Actions spend will need to account for Copilot review runs in their budget projections.

What Stays the Same

The change applies only to private repositories. Public repositories continue to benefit from free GitHub Actions minutes, so open-source projects and public repos are unaffected. Additionally, self-hosted runners do not consume GitHub Actions minutes, giving teams using custom runner infrastructure a way to avoid the additional Actions cost.

Transition Timeline and Preview Tools

GitHub is giving teams roughly five weeks to prepare. A preview bill experience is planned for early May 2026, surfacing projected costs on the Billing Overview page before the transition takes effect. This gives both individual users and organization administrators the opportunity to adjust usage budgets, review current Actions consumption, and configure runner settings proactively.

Developer Reaction

The announcement arrived alongside the broader news that GitHub Copilot is moving to usage-based billing across all features, replacing fixed subscription allowances with monthly AI Credits. Community reaction has been sharply critical. Developers in GitHub's community forums described the shift as reducing the value of paid subscriptions without lowering the price — one comment widely cited: "You will get less, but pay the same price." Several developers announced they had already canceled their subscriptions and were exploring alternatives. The double-billing aspect — paying both AI Credits and Actions minutes for a single review — drew particular scrutiny, with some describing the combined cost model as unexpectedly complex compared to the previous flat-request model.

What Teams Should Do Now

Organizations and individual developers using Copilot code review should:

• Review current GitHub Actions usage against plan entitlements
• Set or adjust spending budgets for GitHub Actions to account for Copilot review runs
• Monitor the Billing Overview page in early May when the preview bill experience launches
• Evaluate whether switching to self-hosted runners reduces projected Actions costs
• Brief billing administrators on the change before June 1