Moving Projects from GitHub to Codeberg: Benefits and Challenges
Summary of Migrating from GitHub to Codeberg · Open original ↗
The author moved active personal and Inko projects from GitHub to Codeberg, seeking a platform that better supports free software and avoids AI-generated spam. Codeberg offers useful features, but migration involves challenges: Forgejo Actions has limits, self-hosted runners can be time-consuming to manage, and Codeberg can be slow or experience outages. Storage limits also mean some Inko container images still use GitHub’s registry. Despite these issues, the author sees Codeberg as a promising alternative.
Quick answers
Why did the author move projects to Codeberg?
The author wanted a platform more aligned with free software and less affected by AI-generated low-quality contributions.
What challenges came with the move?
The author had to handle CI compatibility issues, manage runners, and work around slow service, outages, and storage limits.
Are all of the author’s projects now on Codeberg?
No. Some private projects are hosted on a private Forgejo instance, and some Inko container images still use GitHub’s registry.