# GitHub Actions

234 Hacker News commenters recommended GitHub Actions and 741 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months; owners who said how long report a median of 2 years (21 owners).

**Verdict:** Recommended as a convenient hosted CI built into GitHub, with easy cross-platform matrix builds, though many find workflows hard to debug locally and complain about outages and security footguns.

## Why people recommend it

- Easy cross-platform matrix builds (3 comments): "There’s a great deal to be said for having (inter alia) matrices, job dependencies, and cross-platform runners already working and available." ([source](https://news.ycombinator.com/item?id=50056982)) "the added value of being able to access, build, and publish releases for Windows, macOS, and Linux on BOTH x64 and ARM cannot be overstated" ([source](https://news.ycombinator.com/item?id=50060629)) "then I learned how to use the GitHub Actions matrix feature and supporting multiple versions is suddenly easy" ([source](https://news.ycombinator.com/item?id=47559950))
- Fully managed, no infrastructure (3 comments): "Part of the advantage is a fully hosted service where you don't need to worry about a control plane managing and scheduling jobs." ([source](https://news.ycombinator.com/item?id=46321630)) "if we were ever going to move off of GitHub Actions, it wouldn't be to a service that required use to manage our own VMs/images" ([source](https://news.ycombinator.com/item?id=46921372)) "Github actions definitely has its warts and missing features, but I'll take managed build services over Jenkins every time." ([source](https://news.ycombinator.com/item?id=46135518))
- Better than most CI alternatives (4 comments): "It has just the right amount of abstractions. I've used many CIs in the past and I'd definitely prefer GA over any of them." ([source](https://news.ycombinator.com/item?id=46910472)) "Github actions definitely has its warts and missing features, but I'll take managed build services over Jenkins every time." ([source](https://news.ycombinator.com/item?id=46135518)) "Github Actions is actually one of the better CI options out there, even if on an absolute scale it is still pretty bad." ([source](https://news.ycombinator.com/item?id=46191636))
- Simple, powerful automation (4 comments): "GitHub Action workflow runs weekly to pull in the latest OS images, update and roll over a smoke test VM, monitor, roll over the rest or rollback and ping me in Slack." ([source](https://news.ycombinator.com/item?id=46969820)) "It's fantastic for simple jobs, I use it for my hobbyist projects because I just need 20 to 30 lines to build and deploy a web build." ([source](https://news.ycombinator.com/item?id=46910763)) "A nice thing that is not obvious on the main page is that the dataset and analysis are updated daily using Github Actions" ([source](https://news.ycombinator.com/item?id=49466938))

## What people warn about

- Hard to debug or run locally (5 comments): "they're a pain to debug. A lot of the time, it feels like I'm tinkering with this huge script then holding my breath" ([source](https://news.ycombinator.com/item?id=47939700)) "there’s still seemingly no way to actually debug workflows, run them locally, or rapidly iterate on them in any way" ([source](https://news.ycombinator.com/item?id=46616050)) "All this needing to SSH into runners or needing self-hosted runners or needing act to emulate GitHub Actions is really a failure of the developer experience." ([source](https://news.ycombinator.com/item?id=46593963))
- Frequent outages and flaky jobs (5 comments): "Every month something at GitHub (especially Actions) will go down to the point where you might as well have a prediction market over that." ([source](https://news.ycombinator.com/item?id=48973653)) "Most random errors in Github Actions (e.g. jobs just randomly failing or getting stuck and requiring a manual restart, or just being plain slow)" ([source](https://news.ycombinator.com/item?id=47947800)) "GitHub Actions being down this often is still less expensive than the cost of switching everything somewhere else" ([source](https://news.ycombinator.com/item?id=49201101))
- Security and supply-chain footguns (5 comments): "It's an unfortunately common problem with GitHub Actions, it's easy to set things up to where any PR that's opened against your repo runs the workflows as defined in the branch." ([source](https://news.ycombinator.com/item?id=46090841)) "the fact that a read-only workflow can poison GitHub Actions' cache such that other less-restricted workflows execute arbitrary code is an unexpected footgun" ([source](https://news.ycombinator.com/item?id=47273601)) "Even when you pin the full commit SHA for an action, that action may still pull in transitive dependencies (other actions) that aren't pinned." ([source](https://news.ycombinator.com/item?id=47499640))
- Self-hosted runner billing changes (4 comments): "Paying it and counting it against our total allocated minutes when we bought the machine is going too far though." ([source](https://news.ycombinator.com/item?id=46303222)) "Charging by the minute for the user's own resources gives the impression that GitHub is actually trying to disincentivize third-party runners." ([source](https://news.ycombinator.com/item?id=46291915)) "This change is a very weird one. Because the teams that are capable of setting up their own runners have the means to easily jump ship to another CI platform" ([source](https://news.ycombinator.com/item?id=46312501))

## Alternatives hackers recommend

- [Jenkins](https://hackerapproved.com/p/jenkins.md): 67 recommend
- [GitLab CI](https://hackerapproved.com/p/gitlab-ci.md): 56 recommend
- [Dagger](https://hackerapproved.com/p/dagger.md): 43 recommend
- [Woodpecker CI](https://hackerapproved.com/p/woodpecker-ci.md): 37 recommend
- [Buildkite](https://hackerapproved.com/p/buildkite.md): 33 recommend

## Where to get it

- [Visit the official site](https://github.com/features/actions)

## Cite as

Hacker Approved, "GitHub Actions", https://hackerapproved.com/p/github-actions/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).
