# GitHub CLI CI on GitHub Actions: build times and cost per run on GitHub vs Sengi runners (Nov 2026)

Source: https://sengi.run/benchmarks/cli

By Sengi · Last checked November 17, 2026

## How long does GitHub CLI CI take on GitHub Actions, and what does a build cost?

Measured November 17, 2026 on GitHub CLI (cli/cli, commit fc4b137): Unit and integration tests with the race detector, then a build. Results at 4 vCPU, GitHub-hosted 4 vCPU took 184 s median over 4 runs, $0.042 a build; Sengi Basic 4 vCPU took 163 s median over 3 runs, $0.006 a build, 11% less time and 86% less cost against GitHub-hosted 4 vCPU; Sengi Premium 4 vCPU took 161 s median over 3 runs, $0.018 a build, 12% less time and 57% less cost against GitHub-hosted 4 vCPU. No Sengi runner of GitHub’s size (4 vCPU) took more median time than GitHub-hosted 4 vCPU on GitHub CLI where there were enough runs to compare. Not like-for-like with GitHub’s 4 vCPU runner: Sengi Basic 2 vCPU and Sengi Premium 2 vCPU took more time than GitHub-hosted 4 vCPU. Times are median job seconds, printed only with at least 3 runs; these results cover this build only. No GitHub CLI job failed in this round.

Measured November 17, 2026, last checked November 17, 2026. This page shows one project from the [12-project benchmark](https://sengi.run/benchmarks). Every number is in [one JSON file](https://sengi.run/data/github-actions-benchmarks.json) and [a CSV file](https://sengi.run/data/github-actions-benchmarks.csv), and every median links to its run log in the public repository [sengirunners/benchmarks](https://github.com/sengirunners/benchmarks/tree/e73c896795525a61b47ce9f44657a1a045b0a98b).

## GitHub CLI results at 4 vCPU: GitHub’s runner, Sengi Basic 4 vCPU and Sengi Premium 4 vCPU

One row per runner. Time is the median job run time in seconds, from the job’s start to its end, over the runs counted; min and max are the fastest and slowest of those runs. Cost per build is the median of the runs’ billed minutes, each job rounded up to a whole minute, at the runner’s list price. A cell with fewer than 3 runs prints “not enough runs”.

**GitHub CLI: median job time, run count and cost per build at 4 vCPU, measured November 17, 2026**

| Project | Commit | Runner | Runs | Median time (s) | Min–max (s) | Cost per build (USD) | Time against GitHub | Cost against GitHub |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| GitHub CLI | `fc4b137` | GitHub-hosted 4 vCPU | 4 | [184](https://github.com/sengirunners/benchmarks/actions/runs/44043756102/job/133907139240) | 170–198 | $0.042 | baseline | baseline |
| GitHub CLI | `fc4b137` | Sengi Basic 4 vCPU | 3 | [163](https://github.com/sengirunners/benchmarks/actions/runs/44066983499/job/133986501687) | 161–185 | $0.006 | 11% less time | 86% less cost |
| GitHub CLI | `fc4b137` | Sengi Premium 4 vCPU | 3 | [161](https://github.com/sengirunners/benchmarks/actions/runs/44069088421/job/133992956299) | 153–167 | $0.018 | 12% less time | 57% less cost |

## GitHub CLI median job time at 4 vCPU

GitHub CLI median job time in seconds, measured November 17, 2026. Sengi runners in blue, GitHub-hosted 4 vCPU in grey. The same rows as the table above.

## Not like-for-like: Sengi Basic 2 vCPU and Sengi Premium 2 vCPU

Sengi Basic 2 vCPU has half the cores of GitHub’s 4 vCPU runner. Sengi Premium 2 vCPU has half the cores of GitHub’s 4 vCPU runner. These Sengi runners were run on the same project; they are not a like-for-like comparison, and no GitHub runner of their size was measured. The last two columns still set each against GitHub-hosted 4 vCPU.

**GitHub CLI, not like-for-like: median job time, run count and cost per build on Sengi Basic 2 vCPU (half the cores of GitHub’s 4 vCPU runner) and Sengi Premium 2 vCPU (half the cores of GitHub’s 4 vCPU runner), measured November 17, 2026**

| Project | Commit | Runner | Runs | Median time (s) | Min–max (s) | Cost per build (USD) | Time against GitHub | Cost against GitHub |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| GitHub CLI | `fc4b137` | Sengi Basic 2 vCPU | 4 | [349](https://github.com/sengirunners/benchmarks/actions/runs/44061963873/job/133971409406) | 340–455 | $0.006 | 90% more time | 86% less cost |
| GitHub CLI | `fc4b137` | Sengi Premium 2 vCPU | 4 | [311](https://github.com/sengirunners/benchmarks/actions/runs/44075890696/job/134020472191) | 305–329 | $0.018 | 69% more time | 57% less cost |

## Where did Sengi take more time on GitHub CLI?

Every GitHub CLI result where a Sengi runner’s median was above GitHub’s is printed in the tables above and listed here.

### At 4 vCPU, the same size as GitHub’s runner

Nowhere on GitHub CLI at 4 vCPU in this round: wherever the runs were enough to compare, the median of each Sengi runner of GitHub’s size was at or below GitHub’s.

### Not like-for-like: smaller or larger Sengi runners against GitHub’s 4 vCPU runner

- **GitHub CLI, Sengi Basic 2 vCPU:** 349 s against 184 s on GitHub’s runner, 90% more time, at $0.006 a build against $0.042.
- **GitHub CLI, Sengi Premium 2 vCPU:** 311 s against 184 s on GitHub’s runner, 69% more time, at $0.018 a build against $0.042.

## What was left out of the GitHub CLI medians?

No GitHub CLI job failed in this round, so every measured GitHub CLI run is in a median above. The first run of each runner class is a warm-up that fills its dependency caches and is not measured.

## How was GitHub CLI measured?

- **Time:** Job run time, start to end, from the GitHub API. Queue time is kept apart.
- **Runs:** Median of the measured runs, with n, min and max; a median needs n >= 3.
- **Cost:** Billed minutes (each job rounded up to a whole minute) times the runner's list price per minute.
- **GitHub cost:** GitHub does not bill public repositories for this runner; its cost is what a private repository pays at GitHub's listed rate for the measured size.
- **Order:** One runner class at a time; at most four jobs at once within a run. One warm-up run per class first fills dependency caches.
- **Selection:** The project list is the whole workload list of an existing open-source CI benchmark suite, adopted before running it here. Each project is pinned to a release commit.
- **Exclusions:** Every run is listed. A job is left out of the medians only for the reason given next to it.
- **Dates:** 2026-11-17 to 2026-11-17.
- **Runner size:** the vCPU count printed for each runner was read with `nproc` inside the job, not taken from a label.
- **Prices:** GitHub-hosted 4 vCPU $0.012, Sengi Basic 2 vCPU $0.001, Sengi Premium 2 vCPU $0.003, Sengi Basic 4 vCPU $0.002 and Sengi Premium 4 vCPU $0.006 a minute. GitHub does not bill public repositories for its standard runner, which is 4 vCPU there. The GitHub column is priced at GitHub’s listed rate for its 4 vCPU Linux larger runner (sold to Team and Enterprise Cloud organizations), $0.012 a minute: what a private repository pays for these minutes beyond its plan’s included usage.
- **Queue time** is recorded for every run in the data files and is not part of the times above.

| Project | Repository | Language | What the job runs | Commit |
| --- | --- | --- | --- | --- |
| GitHub CLI | cli/cli | Go | Unit and integration tests with the race detector, then a build | `fc4b137cdef0a6bd28fd461b7cf9c84a5812a8cd` |

The benchmark workflows are at commit `e73c896795525a61b47ce9f44657a1a045b0a98b` of [sengirunners/benchmarks](https://github.com/sengirunners/benchmarks/tree/e73c896795525a61b47ce9f44657a1a045b0a98b). GitHub CLI is not affiliated with Sengi; its name identifies the code that was built.

## Other projects in the benchmark

The same measurement for the other 11 projects, and [all 12 on one page](https://sengi.run/benchmarks).

- [Black CI build time and cost](https://sengi.run/benchmarks/black)
- [Codex CLI CI build time and cost](https://sengi.run/benchmarks/codex)
- [Mastodon CI build time and cost](https://sengi.run/benchmarks/mastodon)
- [Flask CI build time and cost](https://sengi.run/benchmarks/flask)
- [Guava CI build time and cost](https://sengi.run/benchmarks/guava)
- [AI SDK CI build time and cost](https://sengi.run/benchmarks/vercel-ai)
- [Pydantic CI build time and cost](https://sengi.run/benchmarks/pydantic)
- [TypeScript CI build time and cost](https://sengi.run/benchmarks/typescript)
- [Vite CI build time and cost](https://sengi.run/benchmarks/vite)
- [Vue CI build time and cost](https://sengi.run/benchmarks/vue)
- [fd CI build time and cost](https://sengi.run/benchmarks/fd)

## Where is the data?

- [`/data/github-actions-benchmarks.json`](https://sengi.run/data/github-actions-benchmarks.json): runners, projects and commits, the summary rows, exclusions and every run with its log URL.
- [`/data/github-actions-benchmarks.csv`](https://sengi.run/data/github-actions-benchmarks.csv): one line per project and runner, with the project commit, the cost per build and the median run’s log URL.

Prices per minute for every runner are on [Sengi pricing](https://sengi.run/pricing) and in the [runner comparison](https://sengi.run/compare).

## Frequently asked questions

### How long does GitHub CLI CI take on GitHub Actions and on Sengi?

Measured November 17, 2026, at commit fc4b137 of cli/cli: GitHub-hosted 4 vCPU took 184 s median over 4 runs, $0.042 a build; Sengi Basic 4 vCPU took 163 s median over 3 runs, $0.006 a build, 11% less time and 86% less cost against GitHub-hosted 4 vCPU; Sengi Premium 4 vCPU took 161 s median over 3 runs, $0.018 a build, 12% less time and 57% less cost against GitHub-hosted 4 vCPU. Times are median job seconds at 4 vCPU, printed only with at least 3 runs.

### What does one GitHub CLI build cost?

Cost is billed minutes, each job rounded up to a whole minute, at the list price: GitHub-hosted 4 vCPU $0.012 a minute, Sengi Basic 4 vCPU $0.002 a minute and Sengi Premium 4 vCPU $0.006 a minute. Per build: GitHub-hosted 4 vCPU $0.042, Sengi Basic 4 vCPU $0.006, Sengi Premium 4 vCPU $0.018.

### What does the GitHub CLI job run?

Unit and integration tests with the race detector, then a build. Language: Go. Repository: cli/cli, pinned to commit fc4b137cdef0a6bd28fd461b7cf9c84a5812a8cd.

### Did Sengi take more time than GitHub’s runner on GitHub CLI?

No Sengi runner of GitHub’s size (4 vCPU) took more median time than GitHub-hosted 4 vCPU on GitHub CLI where there were enough runs to compare. Not like-for-like with GitHub’s 4 vCPU runner: Sengi Basic 2 vCPU and Sengi Premium 2 vCPU took more time than GitHub-hosted 4 vCPU. Every result is in the tables on this page.

### Why does the comparison use 4 vCPU?

The benchmark runs in a public repository so that every run log is public, and GitHub’s ubuntu-24.04 runner measured 4 vCPU there (nproc inside each job). Sengi runners with the same vCPU count are compared with it directly; Sengi Basic 2 vCPU has half the cores of GitHub’s 4 vCPU runner, and Sengi Premium 2 vCPU has half the cores of GitHub’s 4 vCPU runner, so they are shown separately and not as a like-for-like comparison.

### Why is GitHub’s runner priced if public repositories are not billed for it?

GitHub does not bill public repositories for its standard runner, which is 4 vCPU there. The GitHub column is priced at GitHub’s listed rate for its 4 vCPU Linux larger runner (sold to Team and Enterprise Cloud organizations), $0.012 a minute: what a private repository pays for these minutes beyond its plan’s included usage.

### Can I check the GitHub CLI numbers?

Yes. Every printed median links to the log of the run nearest that median in the public repository sengirunners/benchmarks, at commit e73c896. Every run, failed ones included, is in the JSON file on this page, and the CSV file has one line per project and runner.
