{"slug": "forgejo-actions", "name": "Forgejo Actions", "category": "infra", "category_name": "Infrastructure and DevOps", "description": "", "recommenders": 5, "commenters": 7, "warners": 1, "score": 3.541, "rising": -1.64, "first": "2025-11-30", "latest": "2026-06-10", "why": "One of the nice things about switching to Forgejo Actions is that the runner is lightweight, fast, and reliable", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 5, "neutral": 1, "compare": 0, "warn": 1}, "spark": [1, 2, 1, 0, 0, 1, 0, 0, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "One of the nice things about switching to Forgejo Actions is that the runner is lightweight, fast, and reliable", "kind": "", "icon": true, "domain": "forgejo.org", "github_repo": null, "official_url": "https://forgejo.org", "pricing": "", "aliases": ["Forgejo Actions"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 767172864, "item_id": 47948304, "url": "https://news.ycombinator.com/item?id=47948304", "by": "bsza", "date": "2026-04-29", "version": null, "stance": "recommend", "quote": "It's also probably easier to migrate to if you have complex workflows", "excerpt": "It's also probably easier to migrate to if you have complex workflows as Forgejo Actions is designed to be similar to GH Actions. (Never actually tried it myself though, I switched to Woodpecker long ago.)", "context": "", "use_case": "CI workflows", "switched_from": "", "story": "Ghostty is leaving GitHub"}, {"id": 747907120, "item_id": 46744195, "url": "https://news.ycombinator.com/item?id=46744195", "by": "bramhaag", "date": "2026-01-24", "version": null, "stance": "recommend", "quote": "Forgejo has an integrated CI/CD solution, Forgejo Actions [1], that is very similar to GitHub Actions", "excerpt": "Forgejo has an integrated CI/CD solution, Forgejo Actions [1], that is very similar to GitHub Actions (and thus not so similar to GitLab CI). This is what you'll probably use if you self-host. Codeberg (a public Forgejo-based forge) also offers Woodpecker CI. Their hosted Forgejo Actions is still in beta AFAIK, but you can also use your self-hosted runners. [1] https://forgejo.org/docs/next/user/actions/quick-start/", "context": "", "use_case": "Self-hosted CI/CD", "switched_from": "", "story": "I Like GitLab"}, {"id": 738135088, "item_id": 46133443, "url": "https://news.ycombinator.com/item?id=46133443", "by": "alexrp", "date": "2025-12-03", "version": null, "stance": "recommend", "quote": "One of the nice things about switching to Forgejo Actions is that the runner is lightweight, fast, and reliable", "excerpt": "Our CI workflow literally just invokes a plain old shell script (which is runnable outside CI). We really don't need an overcomplicated professional CI/CD solution. One of the nice things about switching to Forgejo Actions is that the runner is lightweight, fast, and reliable - none of which I can say for the GitHub Actions runner. But even then, it's still more bloated than we'd ideally like; we don't need all the c", "context": "", "use_case": "CI runner", "switched_from": "GitHub Actions", "story": "Zig quits GitHub, says Microsoft's AI obsession has ruined the service"}, {"id": 737701600, "item_id": 46106350, "url": "https://news.ycombinator.com/item?id=46106350", "by": "mlugg", "date": "2025-12-01", "version": null, "stance": "recommend", "quote": "we've migrated to Forgejo Actions", "excerpt": "Zig team member here: we've migrated to Forgejo Actions [0], which is a system built into Forgejo (the Git forge used by Codeberg) which is very similar to GitHub Actions. In fact, while 1-to-1 compatibility is a non-goal, it's almost compatible---many GHA workflows will run with minimal (or no!) changes, and most Actions written for GHA will work fine (e.g. my setup-zig Action [1] worked without changes). I don't ne", "context": "Zig team member", "use_case": "CI for Zig project", "switched_from": "", "story": "Ask YN: What CI do you use instead of GitHub Actions?"}, {"id": 737567200, "item_id": 46097950, "url": "https://news.ycombinator.com/item?id=46097950", "by": "iamkonstantin", "date": "2025-11-30", "version": null, "stance": "recommend", "quote": "It's quite straightforward if you're already familiar with Github Actions.", "excerpt": "We use them in our shop. It's quite straightforward if you're already familiar with Github Actions. The Forgejo runner is tiny and you can build it even on unsupported platforms (https://code.forgejo.org/forgejo/runner) e.g. we've setup our CI to also run on Macs (by https://www.oakhost.net) for App Store related builds. It's really quite a joy :)", "context": "uses it in their shop", "use_case": "CI including macOS builds", "switched_from": "", "story": "Migrating Dillo from GitHub"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 767136530, "item_id": 47946033, "url": "https://news.ycombinator.com/item?id=47946033", "by": "notpushkin", "date": "2026-04-29", "version": null, "stance": "warn", "quote": "Forgejo Actions are Linux only.", "excerpt": "And yet, GitHub Actions are notoriously broken, and serious customers are self-hosting their runners. Codeberg does have some free CI runners, although I\u2019m not sure what capacity they currently have, and how well it would work out if everybody decides to switch from GitHub today. They do encourage you to pick the smallest runner that works for you, and keep the workflows lean: https://codeberg.org/actions/meta Or you", "context": "", "use_case": "", "switched_from": "", "story": "Before GitHub"}]}], "who": [{"by": "mlugg", "context": "Zig team member", "url": "https://news.ycombinator.com/item?id=46106350", "date": "2025-12-01"}, {"by": "iamkonstantin", "context": "uses it in their shop", "url": "https://news.ycombinator.com/item?id=46097950", "date": "2025-11-30"}], "tags": [], "use_cases": ["ci workflows", "self-hosted ci/cd", "ci runner", "ci for zig project", "ci including macos builds"], "compared": [{"slug": "github-actions", "name": "GitHub Actions", "co": 6, "switched_from": 1, "switched_to": 0}, {"slug": "woodpecker-ci", "name": "Woodpecker CI", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48468370", "title": "Surprise Pay $1000", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47939579", "title": "Ghostty is leaving GitHub", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47940921", "title": "Before GitHub", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46742432", "title": "I Like GitLab", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46131406", "title": "Zig quits GitHub, says Microsoft's AI obsession has ruined the service", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46103040", "title": "Ask YN: What CI do you use instead of GitHub Actions?", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 1}, "2025-12": {"recommend": 2}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {"warn": 1, "recommend": 1}, "2026-05": {}, "2026-06": {"neutral": 1}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 775639619, "item_id": 48477476, "url": "https://news.ycombinator.com/item?id=48477476", "by": "sshine", "date": "2026-06-10", "version": null, "stance": "neutral", "quote": "here's a Forgejo Actions that compiles its own CI runner image", "excerpt": "I have a ton of write-up that I haven't published. It's Talos Linux on Hetzner VMs where all resources are managed via kubenix, and all CI runners are running NixOS. So... extremely affordable and extremely performant, but very complicated. Drop me an email if you want the writeup when I get around to making it. Until then, here's a Forgejo Actions that compiles its own CI runner image: https://git.shine.town/infra/r", "context": "", "use_case": "", "switched_from": "", "story": "Surprise Pay $1000"}, {"id": 767172864, "item_id": 47948304, "url": "https://news.ycombinator.com/item?id=47948304", "by": "bsza", "date": "2026-04-29", "version": null, "stance": "recommend", "quote": "It's also probably easier to migrate to if you have complex workflows", "excerpt": "It's also probably easier to migrate to if you have complex workflows as Forgejo Actions is designed to be similar to GH Actions. (Never actually tried it myself though, I switched to Woodpecker long ago.)", "context": "", "use_case": "CI workflows", "switched_from": "", "story": "Ghostty is leaving GitHub"}, {"id": 767136530, "item_id": 47946033, "url": "https://news.ycombinator.com/item?id=47946033", "by": "notpushkin", "date": "2026-04-29", "version": null, "stance": "warn", "quote": "Forgejo Actions are Linux only.", "excerpt": "And yet, GitHub Actions are notoriously broken, and serious customers are self-hosting their runners. Codeberg does have some free CI runners, although I\u2019m not sure what capacity they currently have, and how well it would work out if everybody decides to switch from GitHub today. They do encourage you to pick the smallest runner that works for you, and keep the workflows lean: https://codeberg.org/actions/meta Or you", "context": "", "use_case": "", "switched_from": "", "story": "Before GitHub"}, {"id": 747907120, "item_id": 46744195, "url": "https://news.ycombinator.com/item?id=46744195", "by": "bramhaag", "date": "2026-01-24", "version": null, "stance": "recommend", "quote": "Forgejo has an integrated CI/CD solution, Forgejo Actions [1], that is very similar to GitHub Actions", "excerpt": "Forgejo has an integrated CI/CD solution, Forgejo Actions [1], that is very similar to GitHub Actions (and thus not so similar to GitLab CI). This is what you'll probably use if you self-host. Codeberg (a public Forgejo-based forge) also offers Woodpecker CI. Their hosted Forgejo Actions is still in beta AFAIK, but you can also use your self-hosted runners. [1] https://forgejo.org/docs/next/user/actions/quick-start/", "context": "", "use_case": "Self-hosted CI/CD", "switched_from": "", "story": "I Like GitLab"}, {"id": 738135088, "item_id": 46133443, "url": "https://news.ycombinator.com/item?id=46133443", "by": "alexrp", "date": "2025-12-03", "version": null, "stance": "recommend", "quote": "One of the nice things about switching to Forgejo Actions is that the runner is lightweight, fast, and reliable", "excerpt": "Our CI workflow literally just invokes a plain old shell script (which is runnable outside CI). We really don't need an overcomplicated professional CI/CD solution. One of the nice things about switching to Forgejo Actions is that the runner is lightweight, fast, and reliable - none of which I can say for the GitHub Actions runner. But even then, it's still more bloated than we'd ideally like; we don't need all the c", "context": "", "use_case": "CI runner", "switched_from": "GitHub Actions", "story": "Zig quits GitHub, says Microsoft's AI obsession has ruined the service"}, {"id": 737701600, "item_id": 46106350, "url": "https://news.ycombinator.com/item?id=46106350", "by": "mlugg", "date": "2025-12-01", "version": null, "stance": "recommend", "quote": "we've migrated to Forgejo Actions", "excerpt": "Zig team member here: we've migrated to Forgejo Actions [0], which is a system built into Forgejo (the Git forge used by Codeberg) which is very similar to GitHub Actions. In fact, while 1-to-1 compatibility is a non-goal, it's almost compatible---many GHA workflows will run with minimal (or no!) changes, and most Actions written for GHA will work fine (e.g. my setup-zig Action [1] worked without changes). I don't ne", "context": "Zig team member", "use_case": "CI for Zig project", "switched_from": "", "story": "Ask YN: What CI do you use instead of GitHub Actions?"}, {"id": 737567200, "item_id": 46097950, "url": "https://news.ycombinator.com/item?id=46097950", "by": "iamkonstantin", "date": "2025-11-30", "version": null, "stance": "recommend", "quote": "It's quite straightforward if you're already familiar with Github Actions.", "excerpt": "We use them in our shop. It's quite straightforward if you're already familiar with Github Actions. The Forgejo runner is tiny and you can build it even on unsupported platforms (https://code.forgejo.org/forgejo/runner) e.g. we've setup our CI to also run on Macs (by https://www.oakhost.net) for App Store related builds. It's really quite a joy :)", "context": "uses it in their shop", "use_case": "CI including macOS builds", "switched_from": "", "story": "Migrating Dillo from GitHub"}]}