Migrating from GitHub to Codeberg
Web page · https://yorickpeterse.com/articles/migrating-from-github-to-codeberg
First seen by Oriel on .
AI summary
This article documents migrating 70+ personal and Inko repositories from GitHub to Codeberg, including repository imports, Forgejo Actions, self-hosted runners, and CI limitations.
- The author migrated actively maintained or historically interesting repositories manually using Codeberg’s Forgejo importer, while archiving inactive projects on GitHub.
- The importer can silently pause at GitHub rate limits, does not link GitHub identities to Codeberg users, and cannot preserve Forgejo’s absent issue types without labels.
- Forgejo Actions provides closer integration than Woodpecker but has limited shared runners, incomplete GitHub Actions compatibility, bare-bones UI, and AMD64 Linux-only shared execution.
- Self-hosted runners use an M1 Mac Mini, a Ryzen 5 5600G Deskmini, and a small root-server runner to test Inko across operating systems and architectures.
- The resulting Inko pipeline takes 15–20 minutes, while moving all six platform-architecture runner combinations to hosted infrastructure could cost €90–€120 monthly.
#codeberg #forgejo #ci/cd #self-hosting
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 68, latest observation ; +67 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 26, latest observation ; +26 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | rhoopo | https://yorickpeterse.com/articles/migrating-from-github-to-codeberg/ Read discussion |