November 30, 2025
Repo romance gone sour
GitHub to Codeberg: My Experience
One dev leaves GitHub for Codeberg, and the crowd asks: trend or tantrum
TLDR: A dev fully migrated from GitHub to Codeberg, even moving their site and issue history. Commenters argue whether this marks a real trend, worry about costly free features like automated checks, and say GitHub’s network pull—not missing features—keeps people stuck, making this shift both bold and complicated.
A developer just packed their bags from GitHub and moved everything to Codeberg — site, issues, pull requests, the works — using Forgejo’s import tool and a lot of link rewiring. They even put “we moved!” notices on old GitHub repos and dove into CI (that’s automated checks) where Codeberg gently warns: don’t chase those green checkmarks like a dopamine casino. Cue the comments section lighting up like a server rack.
Darkamaul spots multiple projects jumping ship and asks if this is an exodus or just vibes. Emen15 drops the hottest take: features aren’t the fight — GitHub’s gravity is, thanks to all the integrations and sheer habit. IshKebab turns on cost-mode, wondering how Codeberg can possibly fund free CI runners when Microsoft burns money on them like confetti. Meanwhile, michael_michael asks the practical question: does Codeberg work for tiny teams with private stuff, or is it FOSS-only? And BrenBarn cracks a retro joke, wishing for Mercurial (the “vinyl records” of version tools) to make a comeback.
The mood? Half indie revolution, half “wait, who’s paying for this?” The memes practically write themselves: “Touch grass CI,” “Green checkmark addiction,” and “GitHub is the mall, Codeberg is the indie coffee shop.” Whether it’s a trend or a tantrum, the crowd’s got opinions — and they’re spicy.
Key Points
- •The author successfully migrated projects from GitHub to Codeberg, with the site no longer served via GitHub Pages.
- •Repositories were imported using Forgejo’s “migrate from GitHub” feature, including issues, PRs, wikis, and releases, requiring a GitHub PAT.
- •GitHub API rate limits caused parallel imports to fail, making the process manual and sequential.
- •Links and remotes were repointed to Codeberg using rg, sed, find, and git commands, followed by pushing changes.
- •GitHub repositories were stubbed and archived via a script and the GitHub CLI, and the author began porting CI with Codeberg’s guidance to avoid heavy pipelines.