I’ve already spoken about how I don’t like big tech companies moving towards AI, and GitHub is no exception. Last month, they automatically allowed Copilot to be trained on your code, which was the last straw for me, on top of its increasing unreliability.
Where my code is going
From now on, all of my new public projects will go onto either Codeberg or on my cgit.
A lot of my private repositories are already stored on my own server. You can have private repositories on Codeberg, but I prefer to keep my experiments and temporary things separate.
One day I might run Forgejo, which is what Codeberg uses under the hood, but only if I need the collaboration features. My website’s repository is still on GitHub to build it automatically, and I’ll still need to use GitHub to interact with other peoples’ repositories.
Setting up a Codeberg page
I have been looking at setting up my own Codeberg page (source) to be eventually used for my own programming notes. This site is set up to use Hugo (what this site also uses), with a self hosted Forgejo runner to build it. I used this guide to help me get started.
If you don’t have your own server, you can either put HTML pages in the pages repository (using a webhook) or use one of Codeberg’s own runners to build your site, but these are limited.