Q: Despite having mirror/s, the project will still continue to be operated from GitHub for development, so having yet another mirror doesn't solve anything.
A: You can create issues, contribute, view the repos on there without going to GitHub! Example:
Q: My repos are very bandwidth-intensive projects, and I have my doubts as to whether the owner(s) of Codeberg would be prepared for such a massive bandwidth rate increase. I've also had individual projects be disabled on small sites before due to taking too much bandwidth.
I believe you should mirror your repo to Codeberg because:
Here are some sources for you:
Many front-ends also are living on Codeberg at the moment:
FAQ
Q: - GitHub Actions -- this is a huge time saver for me
A: As I said, we only just mirror. The repo will be available and contributable on both sites.
Q: - Transferring issues -- is this possible? Issues here represent a technical knowledge base we can't live without
A: Yes, it is possible. a. Example for issues:
b. Example for commits:
c. Example for wiki:
Q: Despite having mirror/s, the project will still continue to be operated from GitHub for development, so having yet another mirror doesn't solve anything.
A: You can create issues, contribute, view the repos on there without going to GitHub! Example:
Q: How does Codeberg mirror comments from GitHub?
A: It uses Access Token.
Q: My repos are very bandwidth-intensive projects, and I have my doubts as to whether the owner(s) of Codeberg would be prepared for such a massive bandwidth rate increase. I've also had individual projects be disabled on small sites before due to taking too much bandwidth.
A: Oh.. I think you should directly ask https://docs.codeberg.org/contact/ about if they are ready for massive bandwidth rate increase.