I’ve started moving projects off of Github and onto Gitlab. Cynically one could think it’s “because of Microsoft owning Github.” Not really.

I’ve run a Gitlab server at work before, and I like the idea that, if the need came, I would be able to move off of Gitlab.com and onto a self-hosted instance. That’s not likely to happen any time soon, but should I need to take projects with me (including issues, configurations, etc), I could. Not so with Github which is a closed-source platform. If it had been any other company than Microsoft, it would not have made a difference. This has been a long time coming for me, and I’m progressively getting in gear.

The other, more whimsical reason is because of GitLab Pages. Github only allows creating a single Pages repository per name slug - no sub-paths. So whilst I could create taikedz.github.io, I wouldn’t be able to do taikedz.github.io/bash-builder. In GitLab, I can do that, theme the sections independently as custom websites, and so-on.

Being able to have private repositories is also great - I’ve been wanting a private Kanban for my activities, and using GitLab’s built-in one, I can easily do so without having to resort ot yet-another-site. I’m also trying to explore a bit the idea of GitLab as an all-in-one CI/CD tool. I’ll be quite happy if I can control my personal deployments from this one location, rather than signing up for things like Trello and Travis etc separately, which seems to be the standard in Gtihub-land.

So yes, a focus on FOSS remains the reason, but not because of the name of the parent company.