I've Moved Back to GitHub

19 July 2026  |  4 min read

Back in May, I wrote a post about how I'd migrated all my repos away from GitHub. This ended up being a combination of my self-hosted Git server on my Synology (for my private repos) and Codeberg for my public ones.

Well, since then Codeberg has just given me problem after problem. I had issues working with repos via SSH for weeks. It just kept timing out, or taking an age to actually do anything. So I switched to HTTPS instead, which seemed a little better, albeit still generally very slow.

This morning I came to do a bit of work on some issues and PRs that have been logged against the Pure Comments repo and (unsurprisingly at this point), I was greeted with this:

I've been trying to get to the repo for around 30 minutes now, and it just keeps failing. I can't work like this - I'm a busy guy, so when I do get time to work on these fun side projects, my shit needs to work.

People give GitHub a hard time for outages, scraping, etc. but in all the years I've used it, I've never had an issue. It has always been quick, and it always worked.

In my boredom while waiting for Codeberg to sort themselves out, I decided to peruse my RSS feeds and I came across this post by Sal. It seems he's been having similar problems with Gitlab.

Moving back

This was the final straw. I've had enough of battling with Codeberg, so I've switched back to GitHub. Some may not like this decision as Codeberg is generally considered the more community friends code hub, but I need to make a pragmatic choice here as the constant issues are sapping most the fun out of these projects.

I'll continue to host my private projects on the Synology, as that works great. But as of right now, we're back on GitHub for all [my projects. I think I've caught all references to Codeberg across the various sites and docs (thanks to Gemini), but if you see a problem, please log an issue.

There is 1 final update on Codeberg for both Pure Blog and Pure Comments. This points the updater back to GitHub, from then on, subsequent releases will be on GitHub.

What about...

I'm bound to get some comments and suggestions about other options other than moving back to GitHub, so I'll try and hit them before you take the time to comment/email with recommendations:

1. What about a self-hosted Forgejo instance?
   Absolutely not. I don't have time to maintain something like that. I'd rather spend my free time working on fun projects than managing infrastructure.

2. But GitHub are really bad because of [reason(s)] what about [other tool]?
   Nope, sorry. I don't want to use other platforms that potentially introduce the same issues I've been having with Codeberg. Look at Sal's post further up - he was on Gitlab and having similar problems to me.

3. This is disappointing, are you sure about your decision?
   I'm very sure. It is disappointing, I agree. But I've given it a lot of thought over the last few weeks and I'd rather go with the tool that I know will work, than the one I have to battle with. Plus, this is all public code, so I don't think I'm giving anything away by switching back.

4. I'll NEVER use GitHub. I'm gonna stop using [project] now.
   That's a shame, but it's your call.

Pure Blog Pure Comments Opinion

Reply by email