Why I'm Moving Off GitHub to Self-Hosted Forgejo

A developer is migrating canonical Git hosting from GitHub to a self-hosted Forgejo v15 LTS instance, following the same April 2026 logic the Dutch Ministry of the Interior used when it launched code.overheid.nl on Forgejo: the need to own the infrastructure rather than rent it from a vendor whose incentives have shifted. Outages get most of the attention—257 incidents and 48 major ones in the year ending April 2026, capped by a merge-queue bug that silently reverted commits across 658 repositories—but the author frames them as a symptom rather than the cause. GitHub’s CTO has openly tied the reliability collapse to agentic-AI-driven load growth requiring a 30x capacity scale-up.

The structural changes matter more. In August 2025 GitHub lost its independent CEO when Thomas Dohmke departed and the company was folded into Microsoft’s CoreAI division, ending the arm’s-length arrangement that had made staying defensible since 2018. On April 24, 2026 GitHub flipped Copilot Free, Pro, and Pro+ interaction data—inputs, outputs, code snippets, surrounding context—to opt-in-by-default for AI training, with no repository-level switch; only Business and Enterprise tiers are carved out via separate DPAs. Maintainers cannot prevent contributors using consumer Copilot tiers from feeding their code into training.

Layered underneath is unresolved US jurisdictional exposure under FISA Section 702 (currently on a 45-day extension) and the 2018 CLOUD Act, which reach Microsoft-held data regardless of physical location—a risk Microsoft’s own counsel declined to rule out under oath before the French Senate. EU data residency for Enterprise Cloud doesn’t close that gap. The author’s plan is to complete the migration to code.jorijn.com and archive public GitHub repos pointing at the new home.