# Copilot code review now uses your GitHub Actions minutes: keep your CI off the meter

> Since June 1, 2026, every Copilot code review on a private repository runs on your Actions minutes, sharing the included compute with your CI. Move the CI to Skipbox: 20,000 minutes a month on 4 vCPU is $222 on GitHub, $39 flat on Skipbox.

Since June 1, 2026, every Copilot code review on a private repository runs a GitHub Actions job, and its runner time comes out of your plan's included compute. Past that, GitHub bills it at standard Actions rates. GitHub's October 8 billing options let an organization choose who pays for the review's AI credits; the Actions minutes still go to the repository.

The fix is to take your CI off GitHub's meter. Change `runs-on: ubuntu-latest` to `runs-on: skipbox`, and your builds and tests run on your own machine for a flat $39 a month, leaving the included compute to the reviews.

- 20,000 CI minutes a month on 4 vCPU: GitHub $222, Skipbox $39
- Reviews and CI no longer fight over the same included compute
- No budget to hit: Skipbox jobs use no GitHub minutes

**GitHub Actions at a flat price, unlimited minutes** Skipbox runs your GitHub Actions jobs on your own dedicated machine: $39 a month, however many minutes you run. Docker layers and dependency caches stay between jobs, so the next job starts right away.

A 4 vCPU runner, 20,000 minutes a month: GitHub $222 → Skipbox $39. You save $183 every month.

Moving takes one line: `runs-on: skipbox`.

[Start my 7-day free trial](https://app.skipbox.dev/sign-in?ref=blog-copilot-code-review-actions-minutes-en)

## What changed

GitHub's April 27 changelog said it plainly: Copilot code review "will start consuming GitHub Actions minutes on June 1, 2026." The review's agent runs on GitHub-hosted runners, and on private repositories its minutes draw on the same included compute as every other job. Public repositories are unchanged.

Three details decide who feels it:

- **The repository pays.** The minutes are attributed to the repository's owner, not to whoever asked for the review.
- **Push reviews multiply it.** With **Review new pushes** on, Copilot reviews every push to a pull request, and each review job is rounded up to a whole minute.
- **Agents push a lot.** A pull request an agent keeps fixing gets a review and a CI run on every push.

## What it costs you

The included compute is fixed: $18 a month on GitHub Team. Reviews and CI share it, and GitHub gives neither priority. Once reviews have used their part, every CI minute is billed at the runner's rate, $0.012 a minute on GitHub's 4-core runner.

| CI minutes a month (4 vCPU) | GitHub | Skipbox S | You save each month |
|---|---|---|---|
| 10,000 | $102 | $39 | **$63** |
| 20,000 | $222 | $39 | **$183** |
| 30,000 | $342 | $39 | **$303** |

GitHub's figure is the bill after GitHub Team's included compute, before any review minutes are added. Put your own minutes into the [calculator on the home page](https://skipbox.dev/?ref=blog-copilot-code-review-actions-minutes-en#cost).

The usual reaction is a budget. An Actions budget set to stop usage stops all GitHub-hosted jobs at the limit, so a busy review week can stop your builds. The other reaction, turning off push reviews, trades away the review you turned on.

## Skipbox is the move

- **Flat price, unlimited minutes.** $39, $79 or $149 a month for your CI, however many pushes your people and agents make.
- **Faster CI.** Your own machine keeps Docker layers, package caches and tools between jobs, so each run skips the downloads.
- **No budget to hit.** Skipbox runners use no GitHub minutes. Jobs over your plan's machines wait their turn.
- **No machine to manage.** Skipbox updates the image, cleans up after every job, and rebuilds a machine that fails its health check.

The review job stays on GitHub's runners. Your CI moves, and the included compute is left for the reviews.

## Moving is one line

```yaml
jobs:
  test:
    runs-on: skipbox # was ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test
```

1. Sign in to Skipbox with GitHub.
2. Install the Skipbox GitHub App and pick the repositories.
3. Change `runs-on` and push.

## Try it

The trial takes no card: 7 days or 3,000 job-minutes, whichever comes first. Move your busiest CI workflow to `runs-on: skipbox`, keep Copilot reviewing every push, and watch next month's Actions bill.

## FAQ

### Does Copilot code review use GitHub Actions minutes?

Yes, since June 1, 2026. On private repositories each review's runner time draws on your plan's included compute, and usage past it is billed at standard Actions rates. Public repositories stay free. Moving your CI to Skipbox leaves that included compute for the reviews.

### Who pays for the Actions minutes of a Copilot code review?

The repository's owner. The October 8, 2026 setting that bills a review to the member or the organization moves the AI credits only; the Actions minutes stay with the repository, on the same meter as your CI. Skipbox takes the CI off that meter for a flat $39 a month.

### Why did my GitHub Actions bill go up after June 2026?

If your private repositories use Copilot code review, each review now runs an Actions job, and with Review new pushes on, every push starts one next to your CI. Run the CI on Skipbox and the CI part of the bill becomes a flat $39 a month.

### Can I stop Copilot reviews from blocking my CI with a budget?

An Actions budget set to stop usage stops every GitHub-hosted job when it is hit, CI included, so reviews can use up the room your builds needed. Jobs on Skipbox use no GitHub minutes and don't stop at a budget.

Updated 2026-11-11 · https://skipbox.dev/blog/copilot-code-review-actions-minutes