59 engineers on Hacker News describe using GitHub Actions first-hand: 8 endorse it, 22 regret it, 5 are mixed.
“I can't imagine using GitHub's terribly slow runners after migrating.”
regret · production · logankeenan · 2026-10-28 · source ↗ · wrong label?“I have warned that putting all the eggs in one basket and they key to the fridge in the same basket was a bad idea.”
regret · production · outworlder · 2026-10-19 · source ↗ · wrong label?“I'm still using gh and gh actions and we are mostly below the freemium layer with that. But it is kind of slow”
regret · production · jillesvangurp · 2026-05-26 · source ↗ · wrong label?“cannot think of a more clunky and hard to use system (compared to GHA, which is what we migrated to).”
endorse · production · xp84 · 2026-04-29 · source ↗ · wrong label?“At a customer we're implementing GitHub Actions and even on our Dev environment there are so many hickups with GitHub.”
regret · production · jeena · 2026-04-29 · source ↗ · wrong label?“That's why we switched from GitHub actions: the dashboard.”
regret · production · brian_cunnie · 2025-12-17 · source ↗ · wrong label?“which is less than orchestration cost for GH, that is just ridiculous.”
regret · production · manquer · 2025-12-17 · source ↗ · wrong label?“I'm happy to see they're investing in Actions... Now if only they'd let us say 'this action is required to pass _if it runs_'”
mixed · production · peterldowns · 2025-12-16 · source ↗ · wrong label?“A breath of fresh air after the unceasing misery and pain that is Gitlab and GHA.”
regret · production · regularmother · 2025-12-16 · source ↗ · wrong label?“We've self-hosted github actions in the past... it has been unstable for such a long time”
regret · production · kjuulh · 2025-12-16 · source ↗ · wrong label?“I committed the project I maintain to GitHub Actions when Actions first came out, and I'm really starting to regret it.”
regret · production · 7 yr · jnwatson · 2025-12-08 · source ↗ · wrong label?“the issues I have with GitHub's implementation are pretty much all solved in Forgejo”
regret · production · mlugg · 2025-12-01 · source ↗ · wrong label?“in terms of total availability, I believe we outperformed GHA when we did so... the response is usually lackluster.”
regret · production · deathanatos · 2025-11-18 · source ↗ · wrong label?“Github Actions provides way more resources. They are kind of "locking projects in" by being free.”
mixed · production · chubot · 2025-08-20 · source ↗ · wrong label?“I have never used a CI system more flaky and slow than GitHub Actions.”
regret · production · cjk · 2025-01-21 · source ↗ · wrong label?“I'm relying (not ideal) on the actions/cache through disk_cache blobs - it works, but storing back all blobs makes it a bit worse”
mixed · production · malkia · 2024-12-10 · source ↗ · wrong label?“the platform definitely hides it from you”
regret · production · timvdalen · 2024-09-09 · source ↗ · wrong label?“GitHub actions are as composable as it gets thanks to the ecosystem of actions.”
endorse · production · thiht · 2024-08-13 · source ↗ · wrong label?“Then we moved to Github Actions. GHA has "service containers", but unfortunately the feature is too basic to address real-world use cases”
regret · production · deathanatos · 2024-02-28 · source ↗ · wrong label?“GitHub Actions turns out to be maybe the best CI out there these days for low-friction, get-it-out-there stuff”
endorse · personal · eropple · 2023-12-19 · source ↗ · wrong label?“Github Actions->Azure Functions is pretty much the end game CI/CD experience for me.”
endorse · production · bob1029 · 2023-12-16 · source ↗ · wrong label?“I've been using github actions cache to store build artifacts (object files) between builds. It takes a bit of fiddling but it's possible.”
mixed · personal · rbultje · 2023-12-08 · source ↗ · wrong label?“GitHub actions Mac CI minutes are so expensive so we run our own setup and VM level isolation seems to be the best way”
regret · production · jamifsud · 2023-07-10 · source ↗ · wrong label?“We switched to Github Actions for our CI and it's been … mixed. It was a hell of a lot of work to switch”
mixed · production · deathanatos · 2023-03-14 · source ↗ · wrong label?“Used to use Gitlab runners, Bitrise, Github Actions, etc. They're all too slow”
regret · production · ohgodplsno · 2022-12-09 · source ↗ · wrong label?“Around one year ago we switched to GHA, which was significantly better, and cost $0.”
endorse · production · 1 yr · juanbyrge · 2022-12-08 · source ↗ · wrong label?“We tried Github Actions when Heroku CI was ahem "down" and it was slower & more expensive”
regret · personal · bvirb · 2022-06-15 · source ↗ · wrong label?“Then I got asked to build and maintain GitHub Actions CI pipelines. Never again.”
regret · production · vinceguidry · 2022-04-24 · source ↗ · wrong label?“GitHub Actions has a lot of basic usability issues, none of which are fatal but all of which irritate me on a daily basis.”
regret · production · stickfigure · 2022-04-05 · source ↗ · wrong label?“the biggest pain points we've run into with GitHub Actions are all centered around the many lacking aspects of permission handling.”
regret · production · crooked-v · 2021-08-19 · source ↗ · wrong label?“I prefer Gitlab CI/CD to Github actions (I just couldn't make sense of them).”
regret · personal · xtracto · 2021-01-26 · source ↗ · wrong label?“I've been using GitHub Actions for many interesting things apart from building Upptime, like: COVID-19 nonprofit work”
endorse · personal · anandchowdhary · 2020-12-28 · source ↗ · wrong label?“We've switched our CI/CD to GitHub Actions and love finding these useful actions that we can plug into our workflows”
endorse · production · formalsystems · 2020-09-06 · source ↗ · wrong label?“We're currently trying to use Github Actions but we've run into a few issues.”
regret · production · penagwin · 2019-12-20 · source ↗ · wrong label?“We moved off GL/GH CI for iOS apps and switched to XCode Cloud only because of the pain that Apple is w.r.t. to signing.”
neutral · production · plqbfbv · 2026-11-03 · source ↗ · wrong label?“We switched our Actions workload to blacksmith.sh (not affiliated)”
neutral · production · dneri · 2026-09-21 · source ↗ · wrong label?“Our GitHub Actions bill climbed accordingly — nobody made a bad decision, the machines just never stop typing.”
neutral · production · senoff · 2026-09-08 · source ↗ · wrong label?“mirrored _those_ to GH via actions, which had the added benefit of only failing when GitHub was down!”
neutral · production · maccard · 2026-08-17 · source ↗ · wrong label?“a lot cheaper than the GitHub actions runners we used before that.”
neutral · production · Jarred · 2026-07-27 · source ↗ · wrong label?“GitHub Actions for cleanup, validation, and spellchecking.”
neutral · production · torm · 2026-04-04 · source ↗ · wrong label?“We use commit hashes to pin actions, have the version as a comment (e.g # v4) and renovate will keep both up to date in the PRs.”
neutral · production · hanspagel · 2025-12-20 · source ↗ · wrong label?“Here's the GH action we use to run vale on our website at PR time”
neutral · production · mooreds · 2024-12-14 · source ↗ · wrong label?“running Github actions on a self-hosted microk8s meant instant pod starts and very little fuss.”
neutral · personal · mrj · 2024-03-04 · source ↗ · wrong label?“We migrated to GHA, but still use separate builders”
neutral · production · zamalek · 2024-02-07 · source ↗ · wrong label?“I've been using "Feed me up Scotty" in combination with GitHub Actions (free) to periodically fetch and build my RSS feeds.”
neutral · personal · mderazon · 2023-12-27 · source ↗ · wrong label?“We use various templates to run our CI builds and tests in GitHub Actions”
neutral · production · darknavi · 2023-12-16 · source ↗ · wrong label?“The closest I came was a GitHub actions job that did preflight checks to make sure all the right dependencies and sdks were present”
neutral · production · baby_souffle · 2023-12-05 · source ↗ · wrong label?“some in CI (GitHub Actions) as well.”
neutral · personal · Liskni_si · 2023-11-30 · source ↗ · wrong label?“All the commands in the 'run:' steps of GHA can be run locally in the devcontainer.”
neutral · production · sshine · 2023-11-12 · source ↗ · wrong label?“CI we run through Github Actions; an environment secret plus `vapor deploy` and it's on its way up”
neutral · production · ceejayoz · 2023-11-01 · source ↗ · wrong label?“automatic updates of the servers done with GitHub action”
neutral · production · erenst · 2023-03-13 · source ↗ · wrong label?“We have a Github action, triggered by a "preview" label on a PR and any subsequent commits”
neutral · production · btown · 2022-12-22 · source ↗ · wrong label?“we've moved to GitHub Actions recently. Our current setup time is almost 5 minutes for each parallel runner.”
neutral · production · quesera · 2022-10-27 · source ↗ · wrong label?“For deployment we use simple gcloud commands from github actions to update vms with new instance templates”
neutral · production · jillesvangurp · 2022-09-23 · source ↗ · wrong label?“Github actions has a dedicated lint.yaml which runs a python linter action.”
neutral · production · kortex · 2021-12-21 · source ↗ · wrong label?“we are already using GitHub Actions for some automation, it would make sense to consolidate”
neutral · production · gerhardlazu · 2020-12-27 · source ↗ · wrong label?“We run this in GitHub Actions for all of our Rust repos”
neutral · production · repi · 2019-12-26 · source ↗ · wrong label?“I'm always experimenting with other options, which has recently included GHA and Circle.”
neutral · personal · 013a · 2019-09-20 · source ↗ · wrong label?