news.volyx.in

Moving from GitHub to Codeberg, for lazy people (unterwaditzer.net)

638 points by jslakro · 112 days ago · 352 comments on HN

Article summary

The article discusses the author's experience of migrating repositories from GitHub to Codeberg, highlighting the ease of importing issues, pull requests, and releases, but noting the challenges of setting up Continuous Integration (CI) due to the lack of free macOS runners. The author recommends using Forgejo Actions, which has a similar UI and YAML syntax to GitHub Actions. The article also touches on the issue of what to do with the old repository on GitHub, suggesting archiving it or maintaining a read-only mirror. The author's goal is to provide a starting point for others who want to make the switch.

Main themes

  • GitHub vs Codeberg
  • CI/CD challenges
  • Repository migration
  • Open-source development
  • Self-hosting
  • Git workflow

What commenters say

  • Some developers are hesitant to leave GitHub due to its free CI services, particularly macOS runners, which are not available on Codeberg.
  • Codeberg's lack of support for private repositories is a significant drawback for some users, who may need to consider alternative solutions.
  • The reliance on online access to GitHub or Codeberg can be a problem for developers who prefer to work offline or experience downtime, highlighting the importance of self-hosting or using local repositories.
  • The use of GitHub or Codeberg as a primary remote can lead to issues with availability and reliability, and some developers prefer to use their own cloud storage or remote volumes as their primary remote.
  • The importance of CI/CD services is debated, with some arguing that they are essential for development and others suggesting that they can be self-hosted or replaced with alternative solutions.
  • The design and intended use of Git as a distributed version control system is discussed, with some arguing that it is meant to be used offline and others using it as a centralized repository.
  • Codeberg's availability and reliability issues are a significant concern for some users, who have experienced downtime and difficulties accessing their repositories.
  • The integration of issue trackers with repositories is seen as important by some developers, who prefer to have a centralized location for their project's documentation and issues.