Migrate to Codeberg #305
Replies: 5 comments 3 replies
|
One downside of migration to codeberg is losing all that free CI running. |
3 replies
|
there's also Tangled, which runs off of the same protocol behind Bluesky, ATProto. could be an option what with some of the focus Fluxer has on Bluesky |
0 replies
|
Codeberg does have a Woodpecker CI instance, but it'll require applying for access first (anti-abuse measure): |
0 replies
|
I support this too. While there is a downside of losing on free CI, the upside is that Codeberg does not put a bandwidth limit on LFS objects, which is currently an issue on this repo (#117) |
0 replies
|
We may set up a codeberg, tangled, gitea, etc... backup in the future, but at this time we have no plans to migrate off of Github. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
Just a potential suggestion. Microsoft sucks, we shouldn't be giving them our business. Codeberg can support organizations, codeberg pages (like github pages), repo restrictions and more. Codeberg is non-profit, EU based.
Proposed solution
Codeberg is non-profit, EU based. Not a US tech giant.
Codeberg also has an option to migrate repos directly too. But not sure if it will migrate PRs and issues though. So that might be kind of annoying. If we don't think this is worth the effort, then maybe we shouldn't. But.. might as well do it while we're early before it's way later in the project potentially.
Notes (optional)
No response
Checks
All reactions