Developers and engineering teams worldwide use GitHub Copilot for high-quality, agent-powered code reviews on every pull request. We understand that any change is significant to our customers, especially when it relates to billing, so we are sharing this update early to help you plan and prepare. The sections below outline what is changing, why, and how to plan accordingly.

What’s changing

Last month, we shared how GitHub Copilot code review runs on agentic tool-calling architecture, allowing the code review agent to pull in broader repository context and produce more relevant feedback on each pull request. That agentic architecture runs on GitHub Actions using GitHub-hosted runners (Note: GitHub Copilot code review also supports self-hosted runners and GitHub-hosted larger runners which are billed at different rates than standard GitHub-hosted runners.)

Starting June 1, 2026, each Copilot code review will be billed in two ways:

• All Copilot usage (including code reviews) will be billed as AI Credits under the new usage-based billing model (see the usage-based billing announcement for additional details).
• GitHub Actions minutes will be consumed from your existing plan entitlement for each review that is run on private repositories, with any usage beyond your included minutes billed at standard GitHub Actions rates. You or your organization administrator (for GitHub Teams and Enterprise) can use budgets to manage spending on GitHub Actions. There are no changes to public repositories, where Actions minutes remain free.

This change applies to the following plans:

• GitHub Copilot Pro
• GitHub Copilot Pro+
• GitHub Copilot Business
• GitHub Copilot Enterprise

This includes Copilot code reviews from non-licensed users and billed via direct org billing.

When it takes effect

This change takes effect on June 1, 2026. Until that day, Copilot code review usage will continue to draw only from your existing Copilot premium request unit (PRU) allowance and will not consume GitHub Actions minutes.

What you need to do

To prepare for the billing change, we recommend the following.

Review billing and usage

1. Review your current GitHub Actions usage. Billing managers can view minute consumption and entitlements in your account or organization billing settings.
2. Check your budget on spending limits. Confirm that your personal or organizational budget for Actions aligns with your expected usage. You or your organization administrators (for GitHub Teams and Enterprise) can adjust spending limits for GitHub Actions at any time.
3. Monitor your Copilot and Actions usage over time via GitHub Copilot usage metrics, GitHub Actions metrics, and Billing Usage Report.
4. Review the usage-based billing announcement to understand how Copilot usage itself is being measured going forward.
5. Share this update with your billing administrators and engineering leads so they are aware of the new usage pattern before June 1, 2026.

Review runner settings

• No additional setup is required if you already have GitHub-hosted Runners enabled on your repository.
• If you would like to customize your GitHub Hosted Runner environment, see Upgrade to larger GitHub-hosted Runners.
• Self-hosted Runners setup is available.

Learn more about these changes in our documentation.

And join the discussion within GitHub Community.