6smarketersSoftware
Home/Developer & IT/CI/CD/GitHub Actions

GitHub Actions

CI/CD

Visit websiteCompare
★★★★☆ 4.6 / 5 on G2 · 4.7 on Capterra (300+ G2 reviews)
4.6 / 5
G2 rating [source]
2019
Launched [source]
Free
Minutes included [source]
Marketplace
20,000+ actions [source]

Quick facts

CategoryCI/CD (GitHub)
VendorGitHub (Microsoft)
Launched2019
Starts atFree minutes; usage based
Best forTeams on GitHub
DeploymentCloud and self hosted runners
Free planYes, included minutes
IntegrationsGitHub Marketplace, 20,000+ actions
G2 rating4.6 / 5
Capterra rating4.7 / 5

What is GitHub Actions?

GitHub Actions is GitHub's built in CI/CD and automation, defined in YAML workflows next to your code, with a huge marketplace of actions. Launched in 2019, it lets teams automate build, test, deployment and other workflows directly in their GitHub repositories, triggered by events like pushes and pull requests, with workflows written in YAML and steps assembled from a marketplace of more than 20,000 reusable actions. Builds run on GitHub hosted runners (Linux, Windows, macOS) or self hosted runners you provide. The natural CI/CD choice for teams already on GitHub, Actions brings automation right next to the code with minimal setup. For teams on GitHub, GitHub Actions is a leading choice.

GitHub Actions' distinction is being CI/CD built into GitHub, where most teams already host code, with a huge marketplace. There is nothing extra to integrate, workflows live with the code, trigger on repo events, and draw on 20,000 plus prebuilt actions, so teams start automating quickly. That native integration and marketplace, for the enormous GitHub user base, make it the default CI/CD for GitHub teams.

GitHub Actions at a glanceGitHub Actions is GitHub's built in CI/CD defined in YAML workflows next to your code [GitHub]. It holds about a 4.6 out of 5 rating on G2 and 4.7 on Capterra, with a marketplace of 20,000+ actions.

Who GitHub Actions is best for

GitHub Actions is best for teams already hosting code on GitHub that want CI/CD and automation built in, with minimal setup and a huge marketplace of reusable actions. It suits GitHub users of all sizes. It is a weaker fit for teams on GitLab or Azure (where the native tool fits), those wanting maximum self hosted control and plugins, where Jenkins fits, or teams needing specialised deployment or GitOps, where Argo CD, Harness or Octopus fit.

Key features

The core strengths are YAML workflows triggered by repo events, GitHub hosted runners across Linux, Windows and macOS, self hosted runner support, and a marketplace of more than 20,000 reusable actions. GitHub Actions offers matrix builds, caching, secrets, environments and deployment. Its native GitHub integration, ease of setup and marketplace are its defining advantages for GitHub teams.

GitHub Actions pricing

GitHub Actions is usage based, with a monthly allowance of free minutes included in GitHub plans (more on paid tiers), after which minutes are billed by runner type, with Linux cheapest and macOS most expensive, and self hosted runners free of minute charges. Storage for artifacts and packages also counts. Pricing scales with build minutes and runner type. Model your build volume. Confirm current figures on the GitHub pricing page.

Integrations and ecosystem

GitHub Actions integrates natively with GitHub and draws on the GitHub Marketplace of more than 20,000 reusable actions for building, testing, deploying and integrating with clouds, registries, chat and tools. Its marketplace and native GitHub integration, which let teams assemble pipelines from prebuilt actions right in their repo, are a signature strength and the core of its ease.

GitHub Actions and native integration

Native GitHub integration is the signature advantage: for the huge number of teams on GitHub, Actions puts CI/CD in the same place as the code, triggered by repo events, with workflows versioned alongside the code and a marketplace of actions, so there is no separate tool to set up. For GitHub teams, this integration and convenience are the main reason to choose Actions.

Ease of use and support

GitHub Actions is highly rated for ease of setup, the marketplace and native integration, with teams starting quickly, though reviewers note minute costs at scale and that complex pipelines can get involved. Its G2 reviews praise integration, ease and the marketplace, with build minute cost and debugging complex workflows the main considerations.

Is GitHub Actions worth it?

For teams already on GitHub that want CI/CD built in, with minimal setup and a huge marketplace, GitHub Actions is an excellent, highly rated choice. The main caution is minute costs at scale and workflow complexity for advanced cases, so teams on GitLab or Azure should use their native tool, and those wanting self hosted control Jenkins, but for GitHub teams Actions is a leader.

Pricing

Included

$0
with GitHub plan
  • Free monthly minutes
  • Hosted runners
  • Marketplace actions

Usage based

Metered
per minute
  • Extra minutes billed
  • By runner type
  • Artifact storage

Self hosted runners

$0
minutes free
  • Your own compute
  • No minute charge
  • Control

Pros and cons

Pros

  • Built into GitHub, minimal setup
  • Marketplace of 20,000+ actions
  • Hosted runners for all OSes
  • Self hosted runner option
  • Free minutes included

Cons

  • Minute costs add up at scale
  • Complex pipelines can get involved
  • Best mainly for GitHub users
  • macOS minutes expensive

GitHub Actions alternatives

These ci/cd tools come up most often against GitHub Actions.

GitHub Actions FAQ

What is GitHub Actions used for?
GitHub Actions is used to automate CI/CD and workflows in GitHub repositories: building, testing and deploying code triggered by events like pushes and pull requests, with YAML workflows and a marketplace of more than 20,000 reusable actions.
How much does GitHub Actions cost?
GitHub Actions is usage based, with free minutes included in GitHub plans, after which minutes are billed by runner type (Linux cheapest, macOS most expensive), and self hosted runners avoid minute charges. See the GitHub pricing page.
Is GitHub Actions free?
GitHub Actions includes a monthly allowance of free minutes in GitHub plans, more on paid tiers, so small projects often run free, while heavier usage is billed per minute by runner type, and self hosted runners avoid minute charges.
GitHub Actions vs Jenkins, which is better?
GitHub Actions is managed, built into GitHub and easy to start with a marketplace, while Jenkins is self hosted, open source and endlessly extensible. Actions suits teams on GitHub; Jenkins suits flexible self hosting with full control.
Can GitHub Actions use self hosted runners?
Yes. GitHub Actions supports self hosted runners you provide, which avoid per minute charges and let you control compute and environment, alongside GitHub hosted runners for Linux, Windows and macOS.
Does GitHub Actions do deployment?
Yes. GitHub Actions can handle continuous deployment with environments, approvals and secrets, deploying to clouds and services via marketplace actions, so teams run both CI and CD from their GitHub workflows.

External links