@kevins8 More stuff that comes to mind for additional benefits around GitLab land: - You also can have things like private GitLab Pages for private repos, where a user has to have permissions to the repo to be able to see the GitLab Pages content. - I've used GitLab Pages projects as ways to be able to also easily preview what an MR/PR is modifying/rendering on a site. Forks can generate their own GitLab Pages sites so that you can view them before merging changes. Also compatible with private repos, forks, and private GitLab Pages - GitLab CI allows for you to create CI templates that can then be referenced from other projects, in case you are standardizing on how you run segments of CI/CD. I suppose when you create a GitHub Action that can be called/used by others, this is similar functionality in a way maybe? - GitLab has the concept of "Groups" rather than just how GitHub has "Organizations" - you can have nested groups that all have their own fine-grained permissions model. For an example, I work on Salt Project, with projects in

/saltstack/

, and docs for our open source published sites can be found in

/saltstack/open/docs

-> https://gitlab.com/saltstack/open/docs - Companies that have policies around using open source internally may result in inner sourcing in order to secure and properly replicate the supply chain of software. This could mean making use of internal, private source control systems and CI/CD, of which GitLab I know is used at many places - GitHub Actions is catching up more and more, mostly having taken notes from how GitLab does their stuff it feels like when it comes to their CI