Most documented repo moves flee GitHub — 13 of 33 landed on Codeberg, and the Forgejo family took 21 in all
Asked:
“Show me the migration of Git repos across different forges in the past year.”
An open-web scan of the year 2025-09-01 to 2026-08-31 documented 33 named project or repository migrations across 13 forge-to-forge routes. It is a documented sample, not a census: 28 moves were completed or had primary development moved, 5 were announced or in progress, and each count is the number of named projects on that route.
Where the repositories went
Documented projects per route, origin forge on the left, destination on the right. Hover a ribbon for the projects behind it.
Ribbon colour marks status:completed / primary development movedroute includes announced / in-progress moves
When each move was documented
Each dot is one project, placed at its source date — the date the move was documented, not necessarily the cutover. Filled dots are completed moves; hollow dots are announced / in progress.
GitHub was the origin for 25 of the 33 documented moves (76%), and GitHub → Codeberg was the standout route with 13 projects, led by Zig's high-profile exit. devclass.com
Community-run and self-hosted Forgejo-family destinations dominated: Codeberg received 13 projects and Forgejo 8 across all origins, including Ryubing from GitLab and Fedora Release Engineering from Pagure. discussion.fedoraproject.org
The GitHub → Forgejo route (6 projects) is the least settled: 4 of its 6 moves were still announced or in progress, among them Flathub and Rust Lightning, which was permanently banned by GitHub with no option to appeal. edgen.tech
Movement was not one-way: Baserow and Domination moved GitLab → GitHub, ratatui_ruby left SourceHut for GitHub, while Gleam went to ATProto-based Tangled and Subplot and HardenedBSD chose peer-to-peer Radicle. community.baserow.io
Every documented migration
Origin
Destination
Status
Project
Route
Status
Date
Stated reason
Source
Method: live web searches covering 2025-09-01 to 2026-08-31 used varied terms for GitHub, GitLab, Codeberg, Forgejo, SourceHut, Radicle, Tangled, Bitbucket, Pagure and self-hosted Git; results were deduplicated by project and kept only when a source clearly described a canonical/primary-development move or a concrete migration announcement in the period. 33 project rows across 13 routes. Dates are source dates when exact cutover dates were unavailable; blank reasons are preserved, not invented. Counts measure discoverable documented migrations — not global market share or total Git pushes; small, private and undated moves are undercounted.