Why hackers moved from GitHub Actions to Concourse CI
1 hacker described this switch in public comments. Their words, with links to the originals.
What hackers said about the move
“That’s why we switched from GitHub actions: the dashboard.”brian_cunnie, 2025-12-17original comment ↗
Use GitHub Actions? Get alerted when hackers criticize it.
Tell us the tools in your stack. When hackers start criticizing one of them, or moving to an alternative, you will hear about it first.
GitHub Actions vs Concourse CI
| GitHub Actions | Concourse CI | |
|---|---|---|
| Hackers who recommend | 2 | 1 |
| Hackers who criticize | 6 | 1 |
| Moved away from it | 2 | 1 |
| Moved to it | 1 | 1 |
Counts are distinct hackers in the sampled comments, not market share.
Criticism of GitHub Actions
“Hopefully the steady drumbeat of failure will keep it that way.”macintux, 2026-08-06original comment ↗
“It spawns ephemeral EC2/Azure instances, which is a lot cheaper than the GitHub actions runners we used before that.”Jarred, 2026-07-27original comment ↗
“I recently switched from GitHub Actions to Buildkite + self-hosted runners.”ElFitz, 2026-05-26original comment ↗
“even on our Dev environment there are so many hickups with GitHub.”jeena, 2026-04-29original comment ↗
“I gave GH actions a chance when our org moved from Bamboo but I still hate it.”msie, 2026-01-12original comment ↗
Praise for Concourse CI
No further praise for Concourse CI captured yet.