A developer shares their experience migrating repositories from GitHub to Codeberg, finding the process easier than expected. The migration of issues, pull requests, and releases proved straightforward thanks to Codeberg's GitHub import feature that preserves issue numbers, labels, and authorship. The user interface closely mirrors GitHub's, making the transition seamless for contributors.

For static site hosting, Codeberg Pages offers a GitHub Pages-like experience where you push HTML to a branch. While it lacks uptime service level agreements, the developer reports no downtime issues so far. Alternative hosting options include grebedoc.dev and statichost.eu. The most challenging aspect is continuous integration, as Codeberg doesn't offer free macOS runners or unlimited capacity for public repositories.

Forgejo Actions emerges as the recommended CI solution, offering a GitHub Actions-like experience with nearly identical YAML syntax and UI. The developer suggests self-hosting runners for cross-compilation needs. For those requiring macOS builds, they propose keeping a mirrored GitHub repository with GitHub Actions while using Forgejo Actions to sync CI status back to Codeberg. The migration concludes with archiving the old GitHub repository and updating its README.