Migrating from GitHub Actions to Sourcehut Builds
The article discusses the author's migration from GitHub Actions to SourceHut Builds for their private repositories. The author highlights the benefits of SourceHut, including faster performance and more control over the deployment process. They provide examples of the configuration files used in both systems to illustrate the migration process.
- ▪The author moved from GitHub to SourceHut due to dissatisfaction with GitHub's push for AI features.
- ▪SourceHut offers faster builds and runs closer to the author's infrastructure in the EU.
- ▪The article includes examples of configuration files for deploying a Deno app via SSH.
Opening excerpt (first ~120 words) tap to expand
Migrating from GitHub Actions to SourceHut Builds May, 2026 Faster, more ethical, no AI, and EU-based. After a couple of years running Gitea and Forgejo, I moved my private repos back to GitHub, because my instance was DDoS'd a couple of times and I found myself spending more time than I had wanted upgrading and maintaining it. I didn't like it, and soon after they started pushing hard for Copilot and AI everywhere, I started looking for alternatives again. Codeberg became the obvious choice for mirroring public repos (I'm still in the process of doing this), but their terms don't allow private, non-FOSS projects, so I eventually chose SourceHut for those, and I've been a very happy customer for a few months, now! I'd like to share how I migrated a couple of Github Actions for a Deno app…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Onbrn.
Discussion
0 commentsMore from Onbrn
