March 26, 2026
Forks, feelings, and 500 errors
Moving from GitHub to Codeberg, for lazy people
Goodbye GitHub? Cheers, jeers, and panic over downtime, private projects, and lost Apple freebies
TLDR: A guide claims moving projects from GitHub to Codeberg is mostly painless, except for automated builds and missing Apple machines. Comments explode into a split: freedom lovers cheer leaving GitHub (and its AI vibes), while pragmatists stick with GitHub’s reliability, private project comfort, and generous free tools.
A dev writes a “lazy person’s” guide to hopping from GitHub to Codeberg, claiming the move is surprisingly smooth: issues, pull requests, and releases import cleanly, and Codeberg’s pages work “good enough.” But the comment section turned into a full-on custody battle over where code should live.
On one side, skeptics say the deal-breaker is the automated “build and test” setup (known as CI). GitHub’s free Apple computer runners and huge capacity for public projects are a siren song. As one user shrugs, “Yup and this is where I pass on anything other than GitHub.” Others warn that private projects may feel unwelcome on Codeberg, and that uptime is shaky. One cynic torched the whole experiment with, “codeberg simply doesn’t work.”
On the other side, anti-GitHub voices cheer anything that isn’t Microsoft-owned. One commenter beams, “Codeberg is great,” while others plug alternatives like SourceHut’s old-school email-based workflow. The spiciest meme of the day? A commenter blasting GitHub as “a canteen for AI agents,” accusing it of feeding code to chatbots unless you opt out. Cue dramatic music.
The original post suggests workarounds: self-host a runner for Forgejo (a GitHub-like setup), cross-compile to dodge Apple hardware, or even mirror back to GitHub just for builds. But the vibe is clear: freedom vs convenience, idealism vs uptime, and DIY vs freebies. The migration may be easy—but the comments say the breakup is messy.
Key Points
- •Codeberg’s GitHub import preserves issues, pull requests, releases, labels, and authorship, with a UI similar to GitHub’s.
- •For static sites, codeberg.page offers a GitHub Pages–like workflow but with no uptime SLO; alternatives include grebedoc.dev and statichost.eu.
- •CI is the hardest part of migration: GitHub’s free macOS runners and high capacity are not available on Codeberg.
- •The author recommends self-hosting runners and using Forgejo Actions for CI due to familiarity with GitHub Actions syntax and ecosystem.
- •For macOS-dependent builds, the author suggests keeping GitHub Actions on a mirrored repo and syncing CI status back to Codeberg via the GitHub API; archive the old GitHub repo rather than mirroring issues/PRs.