Codeberg is not a 1-1 replacement for github/gitlab but for many people it is a better option.
I really wish there was a way to support with them a smaller amount then €24. I dont use codeberg myself but I really want to support them.
Moving from GitHub to Codeberg, for lazy people
21–30 of 385 posts
Re: Moving from GitHub to Codeberg, for lazy people
#22Lazy has nothing to do with it, codeberg simply doesn't work. Most of my friends who use codeberg are staunch cloudflare-opponents, but cloudflare is what keeps Gitlab alive. Fact of life is that they're being attacked non-stop, and need some sort of DDoS filter. Codeberg has that anubis thing now I guess? But they still have downtime, and the worst thing ever for me as a developer is having the urge to code and not…
Maybe I'm too old school, but both GitHub and Codeberg for me are asyncronous "I want to send/share the code somehow", not "my active workspace I require to do work". But reading > the worst thing ever for me as a developer is having the urge to code and not being able to access my remote. Makes it seem like GitHub/Codeberg has to be online for you to be able to code, is that really the case? If so, how does that hap…
For me it's a soft block rather than a hard block. I use multiple computers so when I switch to the other one I usually do a git pull, and after every commit I do a push. If that gets interrupted, then I have resort to things like rsyncing over from the other system, but more than once I've lost work that way. I'm strongly considering just standing up a VM and using "just git" and foregoing any UI, but I make use of other features like CI/CD and Releases for distribution, so the VM strategy is still just a bandaid. When the remote is unavailable, it can be very disruptive.
Re: Moving from GitHub to Codeberg, for lazy people
#23Lazy has nothing to do with it, codeberg simply doesn't work. Most of my friends who use codeberg are staunch cloudflare-opponents, but cloudflare is what keeps Gitlab alive. Fact of life is that they're being attacked non-stop, and need some sort of DDoS filter. Codeberg has that anubis thing now I guess? But they still have downtime, and the worst thing ever for me as a developer is having the urge to code and not…
Maybe I'm too old school, but both GitHub and Codeberg for me are asyncronous "I want to send/share the code somehow", not "my active workspace I require to do work". But reading > the worst thing ever for me as a developer is having the urge to code and not being able to access my remote. Makes it seem like GitHub/Codeberg has to be online for you to be able to code, is that really the case? If so, how does that hap…
I was shaking my head in disbelief when reading that part too. I mean, git's whole raison d'etre, back when it was introduced, was that you do not need online access to the repo server most of the time.
Re: Moving from GitHub to Codeberg, for lazy people
#24I think evaluating alternatives to GitHub is going to become increasingly important over the coming years. At the same time, I think these kinds of migrations discount how much GitHub has changed the table stakes/raised the bar for what makes a valuable source forge: it's simply no longer reasonable to BYO CI or accept one that can't natively build for a common set of end-user architectures. This on its own makes me…
CI needs good integration into the source forge. But I don't really perceive Github actions as a huge benefit over the times when everone just set up CircleCI or whatever. As long as it can turn PR checks red, yellow and green and has a link to the logs I'm happy
The whole PR and code review experience is much more important to me. Github is striving to set a high bar, but is also hilariously bad in some ways. Similarly the whole issue system is passable on Github, but doesn't really reach the state of the art of issue systems from 20 years ago
Re: Moving from GitHub to Codeberg, for lazy people
#25Lazy has nothing to do with it, codeberg simply doesn't work. Most of my friends who use codeberg are staunch cloudflare-opponents, but cloudflare is what keeps Gitlab alive. Fact of life is that they're being attacked non-stop, and need some sort of DDoS filter. Codeberg has that anubis thing now I guess? But they still have downtime, and the worst thing ever for me as a developer is having the urge to code and not…
The whole point of git is to be decentralized so there is no reason for you to not have your current version available even when a remote is offline.
Re: Moving from GitHub to Codeberg, for lazy people
#26> The by far nastiest part is CI. GitHub has done an excellent job luring people in with free macOS runners and infinite capacity for public repos Yup and this is where I pass on anything other than GitHub.
Agreed - this is also where Github is the most unreliable. our _number one_ reason for build failures is "GHA being down/degraded" in 2026.
[dead]
Re: Moving from GitHub to Codeberg, for lazy people
#27Earlier quoted context omitted.
Maybe I'm too old school, but both GitHub and Codeberg for me are asyncronous "I want to send/share the code somehow", not "my active workspace I require to do work". But reading > the worst thing ever for me as a developer is having the urge to code and not being able to access my remote. Makes it seem like GitHub/Codeberg has to be online for you to be able to code, is that really the case? If so, how does that hap…
For me it's a soft block rather than a hard block. I use multiple computers so when I switch to the other one I usually do a git pull, and after every commit I do a push. If that gets interrupted, then I have resort to things like rsyncing over from the other system, but more than once I've lost work that way. I'm strongly considering just standing up a VM and using "just git" and foregoing any UI, but I make use of…
> just standing up a VM and using "just git"
That's what I do. Control your entire world yourself.
Re: Moving from GitHub to Codeberg, for lazy people
#28Earlier quoted context omitted.
Maybe I'm too old school, but both GitHub and Codeberg for me are asyncronous "I want to send/share the code somehow", not "my active workspace I require to do work". But reading > the worst thing ever for me as a developer is having the urge to code and not being able to access my remote. Makes it seem like GitHub/Codeberg has to be online for you to be able to code, is that really the case? If so, how does that hap…
For me it's a soft block rather than a hard block. I use multiple computers so when I switch to the other one I usually do a git pull, and after every commit I do a push. If that gets interrupted, then I have resort to things like rsyncing over from the other system, but more than once I've lost work that way. I'm strongly considering just standing up a VM and using "just git" and foregoing any UI, but I make use of…
If you can rsync from the other system, and likely have an SSH connection between them, why don't you just add it as an additional remote and git pull from it directly?
Re: Moving from GitHub to Codeberg, for lazy people
#29I think evaluating alternatives to GitHub is going to become increasingly important over the coming years. At the same time, I think these kinds of migrations discount how much GitHub has changed the table stakes/raised the bar for what makes a valuable source forge: it's simply no longer reasonable to BYO CI or accept one that can't natively build for a common set of end-user architectures. This on its own makes me…
[dead]
Re: Moving from GitHub to Codeberg, for lazy people
#30Earlier quoted context omitted.
Maybe I'm too old school, but both GitHub and Codeberg for me are asyncronous "I want to send/share the code somehow", not "my active workspace I require to do work". But reading > the worst thing ever for me as a developer is having the urge to code and not being able to access my remote. Makes it seem like GitHub/Codeberg has to be online for you to be able to code, is that really the case? If so, how does that hap…
For me it's a soft block rather than a hard block. I use multiple computers so when I switch to the other one I usually do a git pull, and after every commit I do a push. If that gets interrupted, then I have resort to things like rsyncing over from the other system, but more than once I've lost work that way. I'm strongly considering just standing up a VM and using "just git" and foregoing any UI, but I make use of…
> If that gets interrupted, then I have resort to things like rsyncing over from the other system
I'm guessing you have SSH access between the two? You could just add it as another remote, via SSH, so you can push/pull directly between the two. This is what I do on my home network to sync configs and other things between various machines and OSes, just do `git remote add other-host git+ssh://user@10.55/~/the-repo-path` or whatever, and you can use it as any remote :)
Bonus tip: you can use local paths as git remote URLs too!
> but more than once I've lost work that way.
Huh, how? If you didn't push it earlier, you could just push it later? Some goes for pull? I don't understand how you could lose anything tracked in git, corruption or what happened?