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.
2 outlets in our directory ran this story, first to last over 23 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ GitHub Actions down again today — Githubstatus
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Onbrn |
| Canonical URL | https://news.onbrn.com/migrating-from-github-actions-to-sourcehut-builds/ |
| Publication time | Mon, 25 May 2026 13:19:57 +0000 |
| Retrieval time | 2026-05-25T13:37:37.815Z |
| Last seen | 2026-05-25T13:37:37.815Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | DVJ8zexSgPo7 · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
