I’m a bit skeptical about GitHub Copilot, but now that I’ve really tried it out for the first time, I’m amazed by its capabilities. Copilot doesn’t replace programming, but it does take a lot of the work out of it. What works well, for example, is the completion of comments in the code.

GitHub has a new web-based editor based on Visual Studio Code. For me, this fulfills one use case in particular: if you want to browse code to see how certain things were implemented in other projects, this editor now allows you to easily jump to references. This way you don’t have to tediously open many tabs and manually search for files. And it is probably also much easier to look at pull requests this way.

GitHub finally has a dark mode. You can enable it in the settings. There are three options: system (automatic light or dark based on the system preferences), light and dark. Now I can better scroll through code at night or early in the morning. ☺️ Gitea (my preferred code hosting system) has a dark-mode too, but it’s more like a grey-green mode.

There are times when you want to look at something on GitHub on the go. The previous mobile web experience was terrible, but with the latest redesign, the new mobile web experience is finally usable. 🎉 By usable I mean usable, but not necessarily good. I think GitHub still has some room for improvement.

After reading this tutorial about how to mirror a Gitea repository to other Git hosting services like GitHub, I decided to follow a new strategy regarding my projects. I will use my main Gitea instance for all my public repositories and then mirror them on Codeberg and GitHub. I will also migrate projects from GitHub and Codeberg to my Gitea instance and replace the repos with mirrors. The first repo is this one with a mirror on Codeberg and a second mirror on GitHub.

This method gives me full control over my projects and I can create new mirrors or remove old mirrors at any time and I am not dependent on any service.

Yesterday GitHub had an outage and it also resulted in some failures in the build pipeline for this blog. That’s why I decided to host myself a second Gitea instance on a VPS just for this purpose, where I mirror all the dependencies that are needed for a successful build, host some private repos or backup mirrors.

Having two Gitea instances (one at home, one on the VPS - both are backuped daily) also enables me to not have to use Codeberg for not-open-source things. And if I have a sudden internet outage at home, I can still update my blog (the blog repo was hosted at home until today).