GitHub Copilot 代码审查将开始消耗 GitHub Actions 分钟。
GitHub Copilot code review will start consuming GitHub Actions minutes

原始链接: https://github.blog/changelog/2026-04-27-github-copilot-code-review-will-start-consuming-github-actions-minutes-on-june-1-2026/

GitHub Copilot 代码审查的计费方式将于 2026 年 6 月 1 日变更。目前使用 Copilot 高级请求单元 (PRU) 计费的代码审查,之后将通过两种方式计费:通过新的基于使用量的 Copilot 计费模式下的 **AI 积分**,*以及* 消耗 **GitHub Actions 分钟**,尤其是在私有仓库的代码审查中。 对公共仓库的代码审查将继续免除 Actions 分钟的消耗。用户可以利用现有的 GitHub Actions 权益和预算来管理成本。 为做好准备,GitHub 建议查看当前的 Copilot 和 Actions 使用情况,确认预算限制,并熟悉新的 AI 积分衡量方式。这会影响所有 Copilot 计划(Pro、Pro+、Business、Enterprise),包括直接向组织计费的非授权用户的使用情况。 详细信息和资源可在文档和 GitHub 社区中找到,以确保平稳过渡。鼓励与相关团队分享此更新。

GitHub Copilot 的代码审查现在将使用 GitHub Actions 分钟数,可能会影响之前受益于免费审查的用户。这一变化引发了 Hacker News 上的讨论,用户们对成本增加表示担忧。 一些评论员指出,他们之前因为在 Copilot 审查期间意外消耗了大量 Actions 分钟数而取消了订阅,这也导致了审查过程变慢。普遍的看法是,此举标志着人工智能服务正朝着盈利方向转变,公司寻求投资回报。 一位评论员提到,有猜测称大量使用 Copilot 最终可能会使成本达到当前订阅价格的 10 倍,强调了“免费午餐”随着风险投资资金耗尽而可能结束的潜在价格上涨。Y Combinator 宣布了 2026 年夏季的申请开放。
相关文章

原文

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.

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.

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.

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

Learn more about these changes in our documentation.

And join the discussion within GitHub Community.

联系我们 contact @ memedata.com