-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider mirroring repos to Codeberg #16
Comments
But nothing happened and no discussion at all? |
I was looking at the account and considered it to be a bit spammy to my taste. But rest assured, I was already looking into this. I found this as a template, but I have to figure out how the .gitconfig example actually does its job before applying it. |
Yeah, I also felt so. I just copied content from my other issues to here because there’s nothing to change really. How can I make it less spammy-feeling? Appreciate any suggestions for writing issues! Thank you for still talking to me at least explaining instead of fully ignoring even if I asked why ignore like some other repo owners.
Thank you for taking a look at this! Here is another project that mirrored to Codeberg (I convinced the owner successfully): https://github.com/nesaku/BiblioReads You can look at it as an example of how to mirror to Codeberg |
Well, first, use a different account name. Second, keep it short. You can put the nfo you've gathered in a wiki or something (here or on Codeberg), then:
As far as I know there is no use whatsoever to show me or other devs repos that already mirrored to Codeberg as examples, because it doesn't show how to do so. |
Changed! Thanks! |
Done! Thanks! |
|
I mean they are using a workflow to mirror to Codeberg and I think you could look at it: https://github.com/nesaku/BiblioReads/blob/main/.github/workflows/codeberg-mirror.yml |
https://codeberg.org/ltGuillaume @throwaway-d I just migrated via the Codeberg UI, then added a remote url to But fetching only happens from GitHub, so it's probably not the best way (getting merge request from Codeberg won't be possible), so I guess I'd have to rethink this. |
When you figure out, please tell me so I can add it to the tutorial on my repo! |
https://github.com/libredirect and https://github.com/zyachel have been mirroring their repos to Codeberg for a very long time. Maybe we should ping them and ask for help? |
@ltguillaume We have the tutorial now! https://codeberg.org/Recommendations/Mirror_to_Codeberg#setting-up-github-codeberg-mirroring |
Thanks, yeah, looks good! |
When it works, please tell me! :D |
Just thought you'd want to know that a week ago I started using Codeberg as primary remote (my local repo only syncs to Codeberg) and I now let Codeberg sync to GitHub with access tokens. |
Great! |
Thank you for informing me! |
Hello @ltguillaume We should mirror our repos to Codeberg because:
Here are some sources for you:
FAQ
Q: - GitHub Actions -- this is a huge time saver for me
- Forcing all contributors to modify their current setup and move to another hosting -- we may just lose contributors in the end
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
- Transferring wiki and all edit history -- possible?
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.
The text was updated successfully, but these errors were encountered: