GitHub Actions Free Minutes and Limits Answered for Pakistani Teams

Majid Khan
13 Min Read

GitHub-hosted runners cost nothing on public repositories. Put the same code in a private repository on the Free plan and you get 2,000 Linux minutes a month, 500 MB of artifact storage, and a pipeline that goes silent when the counter hits zero. That ceiling is the single most common reason a small team in Lahore or Karachi ends up running CI on a spare office machine. The January 1, 2026 price cuts made overage considerably cheaper, but they left the free quota exactly where it was. What follows is github actions free minutes limits explained in the terms that matter to a team billing in rupees: the quotas, the per-minute rates, the fee that was announced and then shelved, and the point at which running your own hardware starts to pay.

How many free GitHub Actions minutes do you actually get?

A private repository on the GitHub Free plan gets 2,000 Linux runner minutes and 500 MB of artifact and log storage each month, while standard GitHub-hosted runners on public repositories carry no charge at all.

The 2,000 figure is not really a time allowance. GitHub’s billing and usage documentation for Actions describes the included usage as compute credit — $12 a month — expressed in Linux minutes at the standard rate. The number of minutes you actually see depends on which runner you pick, a point cicdcalculator’s free-tier breakdown sets out in detail.

2,000
Linux runner minutes a month on private repositories
GitHub Docs
500 MB
artifact and log storage on the Free plan
GitHub Docs
$12
monthly compute credit the 2,000 minutes represent
GitHub Docs

For a Node or Laravel repository with a three-minute test job, 2,000 minutes is comfortable: a few hundred runs. For a Flutter or React Native repository that builds both platforms on every push, the same allowance disappears inside a fortnight, because the runners those builds need are priced far above Linux.

Why do Windows and macOS runners burn the quota so much faster?

The quota is money, not time, so a macOS job spends it roughly ten times faster than an identical Linux job.

Runner Rate before 2026 Rate from Jan 1, 2026 Minutes from $12 credit
Linux 2-core $0.008/min $0.006/min about 2,000
Windows 2-core $0.016/min $0.010/min about 1,200
macOS 3/4-core $0.080/min $0.062/min about 193

Those rates come from GitHub’s own account of the 2026 pricing changes and are corroborated by Avrea’s pricing rundown. Read the right-hand column and the design decision writes itself for any cross-platform mobile shop: keep lint, unit tests and Android assembly on Linux, and reserve macOS runners for iOS compilation and signing. Three hundred minutes of macOS CI a month is already past the free allowance on its own. The same discipline applies on the desk, where Android Studio system requirements in 2026 decide how much of the build you can shift off the cloud entirely.

What changed in the January 2026 price cuts?

Prices fell; quotas did not. On January 1, 2026 GitHub reduced hosted runner prices by up to 39 percent — Linux 2-core down 25 percent, Windows 2-core down 38 percent, macOS 3/4-core down 23 percent.

The driver was competition and scale rather than generosity. Third-party runner providers had been undercutting GitHub-hosted compute for years, and GitHub’s own volumes changed the arithmetic: it reported processing 7.4 billion commits a month in October 2026, against 65 million a month in 2024, with agentic tooling committing code at machine pace. Absorbing that load took roughly 4 million additional CPU cores, largely on Azure, plus 160 petabytes of fast storage. At that volume, per-minute unit costs drop, and GitHub passed some of it on.

Who benefited is narrower than the headline suggests. If your team was already paying overage, your bill fell by a quarter or more. If you live inside the 2,000 minutes, January 2026 changed nothing for you.

Did the self-hosted runner fee ever take effect?

No. GitHub announced a $0.002-per-minute platform fee for self-hosted runners on private repositories, then postponed it indefinitely. Self-hosted runners carry no GitHub per-minute charge.

The sequence: the fee appeared in a GitHub changelog post on December 16, 2025 with a start date of March 1, 2026. Developers objected loudly, and the objection had a sharp edge to it — the fee would have taxed precisely the teams who had gone out and bought cheaper compute elsewhere, which looked less like simpler pricing than a penalty for shopping around. GitHub said it would re-evaluate its approach and pulled the date.

That outcome matters more here than in most markets. A software house in Karachi or Lahore running its CI on a rack in the office, or on a local VPS costing a fraction of hosted runner rates, was the exact customer the fee would have hit. And the only reason that pattern is so common is the 2,000-minute ceiling it exists to dodge.

Postponed, not withdrawn

The $0.002-per-minute self-hosted runner fee announced in December 2025 was postponed indefinitely, not cancelled. Budget for the possibility that it returns, and keep your workflow definitions portable.

What happens when you run out of minutes?

Workflow runs stop. Jobs no longer queue, pull request checks sit unstarted, and nothing resumes until the next billing cycle or until someone raises the spending limit — which is how most teams find out the quota exists in the first place. Having github actions free minutes limits explained before that happens is cheaper than discovering it on a release day.

Three ways out, with the numbers:

The Team plan costs $4 per user per month and includes 3,000 minutes, according to Activepieces’ 2026 GitHub pricing comparison. For a five-person team that’s $20 a month, roughly Rs 5,600 at rates near Rs 280 to the dollar — and it buys 1,000 extra minutes, which heavy pipelines exhaust quickly.

Overage runs at $0.006 a Linux minute. Burn 10,000 minutes beyond your allowance and the bill is $60, about Rs 16,800 a month, on top of the card’s conversion and transaction charges. Against a local VPS at a few thousand rupees a month, the comparison stops being close once the pipeline gets busy, which is why so many of Pakistani startups and the funding behind them end up self-hosting their CI early.

Either way, set a spending limit deliberately. A limit of zero means your builds halt; an unlimited one means a runaway matrix job can spend real money overnight.

Which limits besides minutes can stop a workflow?

Minutes are one ceiling among several. GitHub’s Actions limits reference documents caps that apply on every plan, paid or free.

Usage limits that apply regardless of plan

  • Maximum job execution time
  • Maximum total workflow run time
  • Queue time before a job is cancelled
  • Concurrent jobs allowed per plan
  • API requests per repository per hour
  • Matrix jobs per workflow run
  • Artifact and log storage — 500 MB on the Free plan

Two of these bite hardest for agencies here. Concurrency is the first: one organisation account serving six client repositories means jobs queue behind each other, and a release build waits while someone else’s test suite finishes. The second is that 500 MB of artifact storage, which a single Android APK plus Docker layers can swallow in a handful of runs. Cut artifact retention to a few days and the problem mostly goes away.

When is a self-hosted runner the cheaper choice?

Self-hosting starts paying once a private repository consistently pushes past 2,000 Linux minutes a month on long jobs — Docker image builds, end-to-end test suites, Android compilation. Those are the workloads that measure in tens of minutes per run, and today they carry no GitHub per-minute charge.

The costs that rarely reach the spreadsheet are operational. Somebody patches the runner, rotates its tokens and keeps dependencies pinned — GitHub made Actions Lockfiles generally available on November 6, 2026 to let teams cryptographically pin workflow dependencies against supply-chain attacks, and that work falls on you. DeployHQ’s comparison of hosted, self-hosted and larger runners lays out the maintenance burden you take on. Add the local one: a runner that reboots mid-build fails the build, so plan backup power for a machine that has to stay up before you move your pipeline onto it.

There is an exit, too. GitLab CI/CD charges no variable platform fee for self-hosted runners, and the December 2025 announcement sent a number of teams to go price it.

Does any of this work differently from Pakistan?

The quotas are identical worldwide. You get the same 2,000 minutes and the same $0.006 Linux rate whether the account is billed from Boston or Bahawalpur, and runner regions don’t shift with your location.

The differences sit at the edges. GitHub’s promotions are geographically restricted: when the GH-700 certification beta opened in November 2026 with an 80 percent discount for early testers, Pakistan was excluded, alongside India, Turkey and China. Billing adds friction of its own, since dollar-denominated overage on a Pakistani card arrives with conversion spread and bank charges stacked on the $0.006.

So the practical answer is the same here as anywhere, only with less room for error: set a spending limit before you need one, keep macOS runners narrowed to the jobs that genuinely require macOS, and decide self-hosting on the size of your workload rather than on how the last pricing announcement made you feel.

Share This Article
Leave a Comment

Leave a Reply

Your email address will not be published. Required fields are marked *