In GitLab, everything you do can be cross-linked and referenced. This improves discoverability and reduces duplicate effort.
This tutorial will demonstrate how to get started with a CI workflow using GitLab Runner.
In GitLab 8.5 we shipped numerous performance improvements. In this article we'll take a look at some of these changes and the process involved in finding and resolving these issues.
You'd be happy to know that GitLab.com now runs an alternate git+ssh port (443) which you can use whenever you are in a place where port 22 is blocked.
In this feature highlight we look at how you can create a new file, directory, branch or tag from the file browser.
This is the start of a series of posts to get you started with GitLab and GitLab CI.
Continuous Integration of GitLab-Hosted Docker Projects with Quay.io
If you want keep code quality high, it is important that you use a code review process. In GitLab, the best way to do this is by using Merge Requests. Read how to approve merge requests here.
We replacing GitLab CI jobs with a .gitlab-ci.yml and wanted to share the details of that process with you and would love to hear what you think.
We just wrote some new documentation on how Gitlab uses Unicorn and unicorn-worker-killer, available on doc.gitlab.com. Read here!
A quick summary of the causes and solutions regarding the GitLab.com outage on 2015-05-29
We're working on a version check function for GitLab to reduce the problem of outdated servers which can be a security problem and provide a bad user experience
GitLab CI Multi-purpose Runner is yet another CI runner, but this time written in Go with a vast number of features that leverage all the latest technologies.