My GitHub Account is actually my second one. The first I created in 2010 after I was introduced to Git the OG way, you know, like one did back in the day:

Beer in hand from a fellow nerd, saying: There’s this new thing from the Linux guy where you can track source code not like Subversion does by sending in files and counting up numbers, but by hashing the contents of the code and syncing it that way.

Back then you couldn’t have private repos with the free tier while BitBucket did allow them (you could even choose between Git and Mercurial repos back then, now I feel old). Because of that all my projects lived in BitBucket and I deleted the GitHub account again.

About a year later, after almost all open source projects had gravitated towards GitHub, I signed up again and used it to keep track and contribute to other people’s code.

I have since gone full circle via GitLab Self-Hosted, GitLab, and back to GitHub. Even work now takes place for me on GitHub.

But as of late I’m more and more irritated by GitHub. Their constant push for their AI features, their janky Token settings, Actions reliability and Package Registry behaviour are a constant pain. And them forcing you to log in to browse public code or download artifacts doesn’t make it any more palatable.

Gitea

Since I had set up a Gitea-instance that privately runs and mirrors various upstream mirrors (and writes them into a single data directory that I then can back up properly), I had slowly started to use it to host small non-mirror repos, like my Dotfiles and Dockerfile repos. It was ultra reliable and performant so that I moved more and more of my code there.

There’s a renovate-bot to check dependencies and I got Gitea Actions running builds better than they ever did on GitHub. The only reason to keep my GitHub account now is for work and contributing to other people’s repos.

So, from now on if you’re searching for a repo of mine you will find it over there, but I won’t delete my account (yet).