Why I'm leaving GitHub for Forgejo
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
A developer explains their migration from GitHub to a self-hosted Forgejo instance, driven by concerns about digital sovereignty rather than reliability. Key reasons include GitHub's absorption into Microsoft's CoreAI division (losing independent leadership), the April 2026 opt-out flip for Copilot training data, and unresolvable US jurisdictional risk under FISA 702 and the CLOUD Act. The post details the technical architecture: Forgejo v15 LTS on a single NUC with Postgres and Traefik, plus a hardened CI runner using KVM isolation, gVisor, weekly destructive rebuilds, nftables egress filtering, and scope-bound tokens. The Dutch government's choice of Forgejo for code.overheid.nl is cited as institutional validation. Honest trade-offs are covered: loss of GitHub's social graph, Actions ecosystem friction, no Dependabot (replaced by Renovate), and lack of enterprise support.
Table of contents
Why outages aren't actually the reasonGitHub no longer has its own CEOThe training-data default flippedThen there's the jurisdictionThe Dutch government's call: code.overheid.nlWhy Forgejo, and not GitLabWhat I built, and why it looks the way it doesWhat I gave upWhen this isn't worth itKey takeaways986.9K Impressions30 Comments