GitHub to Codeberg Migration: A Practical Guide for Lazy Developers
The Great Migration: Why Developers Are Moving to Codeberg en Masse
A viral blog post titled 'Moving from GitHub to Codeberg, for lazy people' has struck a nerve in the developer community, garnering 305 points and 140 comments on Hacker News, as more developers seek alternatives to Microsoft-owned GitHub.
The Migration Experience
The author found the process easier than expected:
Easy parts:
- Repository import from GitHub 'just works' — preserves issue numbers, labels, and authorship
- UI is nearly identical to GitHub's
- Issue tracker, pull requests, and releases import seamlessly
- Codeberg Pages (codeberg.page) replaces GitHub Pages with no noticed downtime
Hard parts:
- CI is the nastiest challenge — no free macOS runners or infinite public repo capacity
- Recommended solution: Forgejo Actions over Woodpecker CI for GitHub Actions familiarity
- YAML syntax is nearly identical; just change to
- Cross-compilation recommended as an alternative to macOS runners
Why People Are Leaving
The migration reflects growing frustration with GitHub's direction:
- Microsoft ownership and corporate governance concerns
- Copilot training on open-source code without opt-in consent
- Increasing platform restrictions and policy changes
- Desire for truly open-source infrastructure
The Practical Reality
The author's honest assessment: 'You will have to give up on both of those things' (macOS runners and unlimited capacity). But for many projects, especially those targeting Linux, the trade-off is worthwhile.
Community Response
The massive HN engagement shows this is not a fringe movement. Developers are seriously evaluating alternatives, and Codeberg (built on Forgejo/Gitea) has matured enough to be a viable option for many projects and organizations.
What It Means for Open Source
A healthier, more distributed Git hosting ecosystem could benefit the open-source community long-term, reducing single-point-of-failure risks associated with GitHub's near-monopoly.