Feature-by-feature comparison migrating from GitHub to SourceHut covering patches, TODOs, Builds, Pages, and wiki with cost breakdown.
Key Takeaways
SourceHut replaces PRs with email-based patches via a visual patchset UI; contributors need only an email, no account required.
Builds use a root-level .build.yml supporting the same triggers as GitHub Actions: pushes, cron, manual, with secrets support.
Pages hosting includes zero-config TLS and custom domains; a Jekyll deploy example deploys in under 5 minutes paired with Builds.
SourceHut is incorporating in the Netherlands and closing its US entity, removing exposure to US trade sanction enforcement.
Paid tiers start at $2/month; GitHub’s cost is framed as data and code scraping via Copilot opt-out default.
Hacker News Comment Review
Thin discussion. The one substantive thread questions whether SourceHut actually protects code from AI training since open source licenses provide no legal shield against Copilot scraping regardless of forge.
A reply notes hostile forges that actively block scrapers may offer practical friction even if not legally airtight, making forge choice a probabilistic defense rather than a guarantee.
Notable Comments
@dijit: Active scraper-blocking by a forge can reduce exposure meaningfully even without legal protection, framing it as defense-in-depth.
