Home / Blog / Cost and billing
What is the best CI setup for a small team on GitHub in 2026?
One workflow, eight settings: a read-only token, SHA-pinned actions, Dependabot, a cache, cancelled reruns, timeouts, tests and a required check. With GitHub's page for each and a minutes budget.
For a small team on GitHub, start with GitHub Actions and one workflow that does 8 things: it reads with a read-only token, pins every action to a commit SHA, keeps actions up to date with Dependabot, caches downloads, cancels superseded runs, puts a timeout on each job, runs the tests, and is a required check on the main branch. That is a checklist, not a platform. Add a merge queue, larger runners or a different runner only when your own numbers ask for it.
- Start with GitHub Actions and one workflow with a read-only token, SHA-pinned actions and a timeout on every job.
- Keep actions up to date with Dependabot, cache downloads and cancel superseded pull request runs.
- A workflow skipped by a path filter stays pending, so a required check must not be path filtered.
- Included compute is a dollar amount: the minutes it buys depend on the runner, and each job is rounded up to a minute.
- Merge queues are for public organisation repositories and Enterprise Cloud private ones; add one later, if ever.
This post gives the checklist with the reason and GitHub’s page for each line, one workflow you can copy, and a minutes budget built from GitHub’s published rates. It names no vendor and makes no speed claim: the setup is about not paying for waste and not shipping a broken main.
What is the checklist for a small team’s CI?
| Setting | Why | GitHub's page |
|---|---|---|
| Read-only token by default | permissions: contents: read at the top of the workflow, and more only on the job that needs it. | GitHub: set the default GITHUB_TOKEN permission to read access for repository contents. |
| Actions pinned to a full commit SHA | A tag can be moved to different code; a SHA cannot. GitHub's strongest measure is a workflow dependency lockfile, which it says supersedes SHA pinning where adopted. | GitHub: for repositories that cannot adopt a lockfile, pin to a full-length commit SHA from the action's own repository. |
| Dependabot for actions | Pins need moving. Dependabot version updates open pull requests to update actions when a new version is released. | GitHub: package-ecosystem: github-actions, directory /, a schedule. |
| Cache what you download | setup-node, setup-python and the like have a cache input: one line. | Our caching post. |
| Cancel superseded runs | A newer push to the same pull request makes the older run pointless. | GitHub: concurrency with cancel-in-progress. |
| A timeout on every job | The default is 360 minutes, so a hung job can cost six hours of minutes. | GitHub: jobs.<job_id>.timeout-minutes, default 360. |
| One required check on main | A ruleset or branch rule that needs the CI job to pass before a merge. | GitHub: required status checks must be successful, skipped or neutral. |
| No path filter on a required workflow | A workflow skipped by a path filter reports nothing and stays pending. | GitHub: troubleshooting required status checks. |
Sources, all read on the date this post was last checked: Secure use reference, Keeping your actions up to date with Dependabot, Workflow syntax and Troubleshooting required status checks. The cache line is our build-cache post.
What does that workflow look like?
name: CI
on:
pull_request:
push:
branches: [main]
permissions:
contents: read
concurrency:
group: ci-${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
jobs:
test:
runs-on: ubuntu-24.04
timeout-minutes: 15
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: 22
cache: npm
- run: npm ci
- run: npm test
It passes actionlint 1.7.12; we have not run it on GitHub, and the Node steps are only the example, so replace them with your own. The SHAs are the commits behind actions/checkout v7.0.1 and actions/setup-node v7.1.0, read with git ls-remote on the date this post was last checked. Cancelling is limited to pull requests, so a run on main is never cancelled once it has started. GitHub accepts an expression for cancel-in-progress.
Which required checks can block a merge for no reason?
Two. A workflow that a paths: filter, a branch filter or a commit message skips reports nothing, so its required check stays “Pending” and blocks the pull request; GitHub’s advice is not to require a workflow that can be skipped. A job skipped by an if: reports Success, which is fine, but a job that depends on a failed job is skipped and may not block at all, so a required check that depends on other jobs needs always() in its if:. For a small team the simple rule holds: one workflow, no path filter on it, and the filtering done inside it.
How many minutes will a small team use?
A plan’s included compute is a dollar amount, so the minutes it buys depend on the runner. On a standard Linux 2-core runner, which GitHub bills at $0.006 a minute, it buys this many:
| Plan | Included each month | Minutes |
|---|---|---|
| GitHub Free | $12 | 2,000 |
| GitHub Pro | $18 | 3,000 |
| GitHub Team | $18 | 3,000 |
| GitHub Enterprise Cloud | $300 | 50,000 |
Standard runners in public repositories and self-hosted runners are free and do not touch the included amount. Each job is rounded up: “GitHub rounds the minutes and partial minutes each job uses up to the nearest whole minute.” So a run is the sum of its jobs, each rounded, not the wall-clock time of the run.
An example with made-up numbers, not a forecast: 6 developers who push 4 times a working day for 21 days make 504 runs. If each run is one job billed for 6 minutes, that is 3,024 minutes, $18.144 at the rate above, about the whole of a Team plan’s included usage. Cancelling superseded runs and caching move that figure down before anything else does. To try your own inputs, the calculator takes minutes and shows them priced; the pricing post has GitHub’s whole rate table. Our per-minute rate for every size, beside GitHub’s, is on the GitHub Actions runner pricing page.
When does a small team need a merge queue?
Later than you think, and for a private repository on a Team plan, not at all: GitHub makes merge queues available in public repositories owned by an organisation, and in private repositories owned by organisations on GitHub Enterprise Cloud. GitHub says a queue helps increase velocity on a busy branch. Until then, the setting it replaces, “Require branches to be up to date before merging”, gives the same protection at the price of a rebase. If you do turn a queue on, the workflow must also trigger on merge_group, or the required check is never reported.
When should a small team change its runner?
When a number says so. The two numbers are the wait for a machine and the minutes the bill counts; measure both before you change anything, and find the slowest step with the speed guide. Paste the workflow into the free workflow checker to see which settings make runs longer or more numerous than they need to be. If a runner change is what the numbers ask for, the switching guide lists what to check first, and the limits post what GitHub caps.
Sources
- Secure use reference (docs.github.com)
- Keeping your actions up to date with Dependabot (docs.github.com)
- Workflow syntax for GitHub Actions (docs.github.com)
- Troubleshooting required status checks (docs.github.com)
- About protected branches (docs.github.com)
- Billing and usage for GitHub Actions (docs.github.com)
- Actions runner pricing (docs.github.com)
- Managing a merge queue (docs.github.com)
Frequently asked questions
What is the best CI setup for a small team on GitHub?
GitHub Actions with one workflow that uses a read-only token, pins actions to a commit SHA, caches downloads, cancels superseded runs, sets a timeout on every job and is a required check on main. Add anything else only when your own numbers ask for it.
Should a small team pin GitHub Actions to a commit SHA?
Yes, where there is no lockfile. GitHub recommends a full-length commit SHA from the action's own repository, because a tag can be moved. Its strongest measure is a workflow dependency lockfile, which it says supersedes SHA pinning for repositories that adopt it.
Why is my required status check stuck on pending?
A workflow skipped by path filtering, branch filtering or a commit message reports no check, so a required check stays pending and blocks the merge. GitHub's advice is not to require a workflow that can be skipped.
Does a small team need a merge queue?
Rarely. Merge queues are available in public repositories owned by an organisation and in private repositories owned by organisations on GitHub Enterprise Cloud. Requiring branches to be up to date gives similar protection without one.