Developer toolsGitHub Actions at a glance
Pros
- Built into GitHub with no separate account or setup
- Free standard runners for public repositories
- Monthly included compute on Free, Pro, Team and Enterprise plans
- Large marketplace of reusable actions
- Linux, Windows, macOS, Arm and GPU runners, plus self-hosted runners
Cons
- macOS and larger runners are expensive per minute
- YAML workflows can be hard to debug
- GitHub's 2025 plan to charge for self-hosted runners was postponed, not ruled out
- Usage is blocked once included compute runs out without a payment method
- Lock-in to GitHub repositories and workflow syntax
What GitHub Actions is
GitHub Actions is the continuous integration, continuous delivery and automation service built into GitHub. You describe workflows in YAML files stored in your repository, and GitHub runs them on events such as a push, a pull request, a release, a schedule or a manual trigger.
Workflows run on runners: virtual machines hosted by GitHub, or your own machines registered as self-hosted runners. Beyond building and testing code, teams use Actions to deploy applications, publish packages, label issues, run security scans and automate almost any repository task.
Who GitHub Actions is for
Actions suits any team whose code is on GitHub, from open-source maintainers, who get standard runners free on public repositories, to enterprises running thousands of pipelines. Because it lives next to pull requests, checks, environments and secrets, it removes the need for a separate CI service in most cases.
It is less compelling for teams whose code is hosted elsewhere, and some organizations with very large builds prefer specialist CI services for faster caching, better test insights or predictable pricing.
Key features
Workflows support matrix builds, which run the same job across several operating systems, language versions or configurations in parallel. Reusable workflows and composite actions let platform teams share standard pipelines across many repositories.
Environments add protection rules such as required reviewers and wait timers before deployments, and secrets and variables can be scoped to organizations, repositories or environments. OpenID Connect support lets workflows authenticate to AWS, Azure and Google Cloud without storing long-lived cloud credentials.
GitHub-hosted runners cover Linux, Windows and macOS, with Arm options and larger runners with more CPU, memory or GPUs on Team and Enterprise plans. Custom images let organizations pre-install tools to speed up jobs. Self-hosted runners give full control over hardware and network access.
The GitHub Marketplace offers a very large library of community and vendor actions for setting up languages, caching dependencies, deploying to cloud providers and more. Caching and artifacts speed up builds and pass files between jobs.
Pricing explained
Public repositories get standard GitHub-hosted runners free, which is why Actions dominates open-source CI. Private repositories draw from the monthly included compute on your plan, then pay per minute.
For most small teams, the included allowance covers Linux builds comfortably. Costs rise quickly with macOS jobs, which cost about ten times as much per minute as standard Linux, and with larger runners. Setting a budget in GitHub's billing settings prevents surprise bills.
The January 2026 price cut lowered hosted runner costs by up to 39 percent, depending on machine type. GitHub's December 2025 attempt to charge for self-hosted runners was postponed, so self-hosted minutes are free for now.
Ease of use and setup
Getting started is easy: GitHub suggests starter workflows based on your repository's language, and a basic build-and-test pipeline can run within minutes. The workflow editor provides syntax help, and logs stream live in the browser.
Complex pipelines are harder. YAML syntax, expressions, permissions and job dependencies take time to master, and debugging often means pushing a change and waiting for a run. Many developers use local runner tools or dedicated test branches to iterate faster.
Integrations
Actions integrates deeply with the rest of GitHub: pull request checks, branch protection, deployments, packages, Dependabot, code scanning and Copilot. Through the Marketplace and OpenID Connect, it connects to every major cloud provider, container registry and deployment platform.
Because workflows can call any command-line tool or API, nearly any service can be part of a pipeline. The trade-off is that third-party actions run code in your pipeline, so pin actions to specific versions or commit hashes and review what they do.
Self-hosted runner pricing controversy
In December 2025 GitHub announced lower prices for hosted runners and a new $0.002 per minute platform charge for self-hosted runners on private repositories from March 2026. GitHub said most customers would see no change in their bill and that hosted-runner revenue had been subsidizing free self-hosted use.
The reaction from developers was strongly negative, and GitHub postponed the self-hosted charge within days to re-evaluate. The hosted-runner price cut went ahead on 1 January 2026. GitHub has said it still intends to recover the cost of supporting self-hosted runners, so large self-hosted users should plan for possible future changes.
Support and reliability
Support depends on your GitHub plan: community support on Free, web-based support on Team and enterprise support options on Enterprise. Documentation is extensive, and the large user community means most errors have a documented fix.
Actions has had periodic outages and queueing delays, which are visible on GitHub's status page, and some critics cite reliability among reasons for moving projects elsewhere. For critical release pipelines, consider self-hosted or larger runners and keep a manual fallback.
What users like and dislike
Developers like having CI/CD next to their code, the free public-repository usage, the marketplace and the breadth of runner types. Independent coverage of the 2026 changes also highlights the lower hosted runner prices.
Common complaints are YAML complexity, slow feedback when debugging, costly macOS minutes, occasional outages and frustration over the handling of the self-hosted runner fee announcement.
Our verdict
If your code is on GitHub, Actions is the natural default for CI/CD and automation. It is free for open source, includes compute on every plan, and became cheaper per minute in 2026.
Watch macOS and larger-runner costs, set a budget, and keep an eye on GitHub's plans for self-hosted runners. Teams on other code hosts, or with very large builds that need specialist caching, should compare GitLab CI/CD, CircleCI and Buildkite.
GitHub Actions scores 8.5 out of 10 overall. Its strongest criterion is room to grow (9.5/10) and its weakest is ease of use (7.5/10).
GitHub Actions pricing
| Plan | Price | What you get |
|---|---|---|
| Public repositories | Free | Standard GitHub-hosted and self-hosted runners at no charge |
| GitHub Free | $0 | $12 of included Actions compute a month (2,000 Linux minutes), 500 MB artifact storage |
| GitHub Pro | $4/mo | $18 of included compute a month (3,000 Linux minutes), 1 GB storage |
| GitHub Team | $4/user/mo | $18 of included compute a month (3,000 Linux minutes), 2 GB storage |
| GitHub Enterprise Cloud | $21/user/mo | $300 of included compute a month (50,000 Linux minutes), 50 GB storage |
| Extra usage | From $0.002/min | Linux 2-core $0.006/min, Windows $0.010/min, macOS $0.062/min; storage $0.25/GB-month |
GitHub now expresses the included Actions allowance as a dollar amount rather than minutes: $12 a month on Free, $18 on Pro and Team, and $300 on Enterprise Cloud. Usage is deducted at each runner's per-minute rate, so $12 buys 2,000 minutes on a standard 2-core Linux runner but far fewer on Windows or macOS.
Standard per-minute rates in GitHub's documentation are $0.002 for a 1-core Linux runner, $0.006 for a 2-core Linux x64 runner, $0.005 for 2-core Linux Arm, $0.010 for Windows and $0.062 for macOS. Larger runners cost more and are billed even on public repositories. These rates reflect the price cut of up to 39 percent that took effect on 1 January 2026.
Artifact storage beyond your plan's allowance, shared with GitHub Packages, costs $0.25 per GB per month. Each repository gets 10 GB of cache free, with extra cache at $0.07 per GB per month. Once you use up your included amount, workflows are blocked unless you add a payment method and a budget.
Self-hosted runners are currently free. In December 2025 GitHub announced a $0.002 per minute platform charge for self-hosted runners on private repositories from March 2026, then postponed it after strong criticism to re-evaluate its approach, without ruling out a future charge. Teams that rely heavily on self-hosted runners should watch for updates.
Prices in US dollars, checked on Nov 21, 2026. Confirm on GitHub Actions's own site before you buy.

