In this post we'll consider some ways people evaluate or represent productivity, and I ask for your thoughts on what you track and what you think matters. Read on
In this post, we have a handy reference guide to explain some potentially confusing terms, especially if you're new to GitLab.
Please let us know about your favourite swag, from stickers to surprises, and don’t forget to share your #swagportrait.
In this article I’ll give you an overview of how we release our product and how it helps our team improve process and documentation.
Users requested a few customizations to help the UI better fit their daily use. We are happy to share new user preferences in GitLab 8.1.
Six good reasons why you should review code before it's being deployed/ released/ merged.
Have you ever wondered how GitLab employees use GitLab? Well read this article and get the inside scoop!
Take a moment to view some highlights of the reasons why deploying on-premises in SAAS era is not such a bad idea after all.
Moving to a single code coolaboration tool streamlines process and allows you to free up valuable resources. Learn more here!
Working on an open source projects we receive many merge and pull requests and see a number of different git personalities. Do you recognize yourself?
In this post we discuss the advantages of running GitLab Enterprise Edition, our paid version of GitLab.
This blog post will give a short overview on how GitLab bugs are handled, and what you can do after you identify a potential bug in GitLab.
At GitLab we believe that by preventing force pushes and by stimulating code review practices, mistakes can be easily avoided and code quality will improve.
Sometimes you need additional control over pushes to your repository. For each project you can have unique Git Hooks.
GitLab groups allow you to group projects into directories and give users access to several projects at once.
We are excited to show you some of the possibilities in our new screencast.