Urgent.News

650+ sources. One page. See who else covered it.

Editions

Tech

GitHub Actions' free macOS minutes, explained

GitHub Actions is GitHub's built-in CI/CD system — it spins up a fresh virtual machine, runs whatever commands you tell it to, and tears the machine down when it's done. It supports Linux, Windows, and macOS runners. The macOS runners are the interesting part here, because they're actual macOS machines with Xcode's command-line build tools available, which means they can build and sign iOS apps —…

GitHub Actions is a built-in Continuous Integration/Continuous Deployment system offered by GitHub. This system spins up a fresh virtual machine, runs the commands you specify, and then tears down the machine once it's done. GitHub's CI/CD system supports Linux, Windows, and macOS runners.

The virtual macOS machines have Xcode's command-line build tools, enabling them to build and sign iOS apps. This is what sets them apart from Linux and Windows runners. On a public repository, standard GitHub-hosted runners - including macOS runners - are free, regardless of the plan you're on. This includes the free plan, which is a genuine free tier, not a trial or limited allowance.

However, this unlimited free usage doesn't apply to private repositories. Instead, private repositories receive a monthly allowance of free minutes based on your plan: 2,000 free minutes for Pro and Team plans, both with 3,000 minutes included. The catch is that macOS runners, which are needed for iOS builds, cost roughly 10 times more than Linux runners. Therefore, a 6-minute macOS build consumes the same allowance as roughly 60 minutes of Linux CI.

This means a private repo effectively gets around 200 macOS-runner-minutes worth of free build time per month on a free plan, before any additional charges apply. The same applies to Pro and Team plans, which get around 300 free macOS-runner-minutes per month.

The visibility of your repository (public or private) only changes the pricing of CI minutes, not the functionality of your pipeline. Signing certificates and credentials are kept secure in encrypted GitHub secrets, regardless of visibility. However, the Apple Developer Program fee, which costs $99/year, is a separate cost that you pay directly to Apple and is not related to GitHub's billing.

This explanation does not cover other costs like the Apple Developer Program fee, storage and artifact retention, or changes in GitHub's billing numbers. For the most accurate and up-to-date information, please refer to GitHub's current billing documentation.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why your TestFlight build doesn't show up after a successful upload

You push, the build runs, the archive and export steps succeed, the upload step succeeds, the workflow finishes green. You open App Store Connect to check on it and TestFlight shows...

  • Build number must change with each upload, even if marketing version stays same
  • Use github.runnumber in GitHub Actions for dynamic build number
  • Verify dynamic build number substitution in archive step

The actual cost of shipping an iOS app in 2026

"How much does it cost to put an app on the App Store" gets answered inconsistently online because most answers either only count Apple's fee, or only count hardware, or quietly assume you're renting…

  • Mandatory $99/year fee for Apple Developer Program membership
  • Building and signing requires Mac, cloud Mac, or GitHub Actions
  • Public repository with GitHub Actions is most cost-effective at $99/year

A Context Object Should Carry Its Receipt

A stored fact can be wrong in a quiet way. The answer still reads clean. A preference from an old exchange gets reused, the message goes out with confidence, and later nobody can tell why that detail…

More from Sunday 16 August →