Happy we switched from GitHub to GitLab!

Item: GitLab
Rating: 9
Author: Thomas Ketchell

Use Cases and Deployment Scope

Gitlab is used across Sutori and it allows us a clear view of all the existing bugs/stories that we need to address as a company. Having everything in one centralized place is one of the reasons why we're big fans of Gitlab as it allows viewers and collaborators to all get involved in the process of fixing issues and moving to the next business item.

Pros and Cons

Ease of Use
Continuous integrations
Automated help

Onboarding some of our employees can be a bit of a drag
The backing of Gitlab can take a while

Return on Investment

Cheaper than GitHub
More user-friendly so easier to onboard
Some occasional downtime (but very rare)

Alternatives Considered

GitHub

GitLab was more affordable than GitHub and served the same purpose. The newer, cleaner and fresher design/UX of GitLab was an attractive point for us switching everything to GitLab. The built-in Web IDE is a very nice feature to edit your files online which GitHub did not offer when we were looking to switch products. We've used the groups and sub-groups for the repository as it helps to manage the repositories easily with user assignment, permissions, etc.
GitLab just makes it easier.

Likelihood to Recommend

GitLab has a full suite of tools including but not limited to repository and issue tracking, milestones and issue boards, group and user management, including project and even branch level permissions, continuous integration and scheduled jobs. All the features work together and using it to manage projects tends to pull the details together rather than fragmenting them across different spaces. The general workflow is similar enough to GitHub that most developers find it familiar. It's replaced GitHub in our organization and we haven't looked back since using GitLab.