Why we use GitLab

Mar 27, 2018 · 3 min read


We use GitLab instead of GitHub, and you can find some of our projects here.

We’re often asked by our users and investors why our GitHub is so empty. Or if anybody is even working on this project.

The answer is simple: Yes, we are very actively working on Brickblock every day. We just use GitLab as our central code collaboration platform instead of GitHub. Let me tell you why.

Free CI/CD pipeline included

GitLab comes with a powerful and well-integrated Continuous Integration (CI) and Continuous Deployment (CD) pipeline. With GitHub, we would have to pay for and manually integrate an external CI service such as CircleCI.

Free container registry

We’re big believers in dockerizing everything. GitLab has a built-in docker registry for each repository, no configuration required. With GitHub, we’d again have to set up and pay for a third-party service to manage our docker images.

Kubernetes integration

We love how Kubernetes simplifies our infrastructure management. So we were more than excited when GitLab released their Kubernetes integration because it’s a natural fit for our workflow.

Review apps

We deploy every branch on every commit into its own review app. This is an immense improvement to our QA workflow because we can conduct all quality assurance directly in the actual feature branch before merging it back to the master branch. We’ve found that this process brought our QA and Dev team closer together and made the collaboration much more efficient.

Better project management

While GitHub does offer some project management tools, we find GitLab’s boards and issue management more extensive and better suited to our workflows. Some examples would be burndown charts, group milestones, issue due dates, moving issues between projects, or the issue CSV export.

Superior data portability

GitLab can import projects and issues from more sources than GitHub and it allows us to export our projects to other systems.

Integrated monitoring

GitLab helps us collect performance metrics for both servers as well as our applications. It quickly lets us determine the impact of merging a particular branch and keep an eye on our production systems without ever leaving GitLab.

Quick actions

We love GitLab’s quick actions and frequently catch ourselves trying to use them on GitHub as well — only to find that they don’t work 😢.

Inline commenting and discussion resolution

We find reviewing merge requests (“MRs”) with GitLab more effective due to the discussion resolution feature, which allows us to keep a more manageable overview about which code review feedback has already been addressed, and what’s still left to do.

Because gitlab.com isn’t perfect either, we’re running our own GitLab instance to have full control over the backup process in case shit hits the fan.

You can check out some of the projects we’re working on over at here and here.

Or take a look at our npm profile and check out some of our publicly available npm packages.

Oh, and if you like what you see, we’re hiring :)


Written by

Brickblock uses blockchain technology and smart contracts to make real estate investments easier, cheaper, and more accessible.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade