Skip to content


Subversion checkout URL

You can clone with
Download ZIP
GitLab is version control for your server
Ruby HTML CoffeeScript Cucumber CSS JavaScript Shell
Failed to load latest commit information.
app Fix redirection to home page URL for unauthorized users
bin Move prepare_build script to scripts dir.
config Add support for unlocking users in admin settings
db Change default admin password from "5iveL!fe" to "password"
doc Merge branch 'master' of
docker Change default admin password from "5iveL!fe" to "password"
features Merge branch 'improve-spinach-test-for-mr-submit' into 'master'
lib Allow user to be blocked and unblocked via the API
log v1.0
public Replace old logo with new one
scripts Added missing packages required by docker builds
spec Allow user to be blocked and unblocked via the API
tmp Make sure important directories exist in git
vendor/assets Remove jasmine-fixture, use teaspoon fixtures
.foreman complete hooks for post receive
.gitattributes Use gitattribute merge=union to reduce CHANGELOG merge conflicts.
.gitignore Remove the volumes from the single image to keep it simple.
.gitlab-ci.yml Remove jasmine:ci task, execute teaspoon directly on CI
.hound.yml Make houndci prefer single quotes.
.pkgr.yml Use new way of defining services on
.rspec Make Fuubar the default rspec formatter
.rubocop.yml Enable rubocop for tests too
.ruby-version ruby 2.1.6
.simplecov organize simplecov
.teatro.yml teatro setup
CHANGELOG Add 7.12.2 CHANGELOG entries [ci skip] Changed the reference from gitlab cloud to becau…
GITLAB_SHELL_VERSION GitLab shell version to 2.6.3.
Gemfile Merge branch 'rs-gem-security' into 'master'
Gemfile.lock Merge branch 'rs-gem-security' into 'master'
LICENSE LICENSE year update Add note about semantic versioning not being absolute. Escape process text
Procfile Archive repositories in background worker. Change default admin password from "5iveL!fe" to "password"
Rakefile v1.0
VERSION Its 7.13 time :) Disable Unicorn::WorkerKiller in non-production environments update documentation styleguide

Canonical source

The source of GitLab Community Edition is hosted on and there are mirrors to make contributing as easy as possible.

logo GitLab

Open source software to collaborate on code

To see how GitLab looks please see the features page on our website.

  • Manage Git repositories with fine grained access controls that keep your code secure
  • Perform code reviews and enhance collaboration with merge requests
  • Each project can also have an issue tracker and a wiki
  • Used by more than 100,000 organizations, GitLab is the most popular solution to manage Git repositories on-premises
  • Completely free and open source (MIT Expat license)
  • Powered by Ruby on Rails


There are two editions of GitLab. GitLab Community Edition (CE) is available without any costs under an MIT license.

GitLab Enterprise Edition (EE) includes extra features that are most useful for organizations with more than 100 users. To use EE and get official support please become a subscriber.

Code status

  • build status on (master branch)

  • Build Status

  • Code Climate

  • Coverage Status


On you can find more information about:


GitLab requires the following software:

  • Ubuntu/Debian/CentOS/RHEL
  • Ruby (MRI) 2.0 or 2.1
  • Git 1.7.10+
  • Redis 2.0+
  • MySQL or PostgreSQL

Please see the requirements documentation for system requirements and more information about the supported operating systems.


The recommended way to install GitLab is using the provided Omnibus packages. Compared to an installation from source, this is faster and less error prone. Just select your operating system, download the respective package (Debian or RPM) and install it using the system's package manager.

There are various other options to install GitLab, please refer to the installation page on the GitLab website for more information.

You can access a new installation with the login root and password password, after login you are required to set a unique password.

Third-party applications

There are a lot of third-party applications integrating with GitLab. These include GUI Git clients, mobile applications and API wrappers for various languages.

GitLab release cycle

Since 2011 a minor or major version of GitLab is released on the 22nd of every month. Patch and security releases are published when needed. New features are detailed on the blog and in the changelog. For more information about the release process see the release documentation. Features that will likely be in the next releases can be found on the feature request forum with the status started and completed.


For updating the Omnibus installation please see the update documentation. For installations from source there is an upgrader script and there are upgrade guides detailing all necessary commands to migrate to the next version.

Install a development environment

To work on GitLab itself, we recommend setting up your development environment with the GitLab Development Kit. If you do not use the GitLab Development Kit you need to install and setup all the dependencies yourself, this is a lot of work and error prone. One small thing you also have to do when installing it yourself is to copy the example development unicorn configuration file:

cp config/unicorn.rb.example.development config/unicorn.rb

Instructions on how to start GitLab and how to run the tests can be found in the development section of the GitLab Development Kit.


All documentation can be found on

Getting help

Please see Getting help for GitLab on our website for the many options to get help.

Is it any good?


Is it awesome?

Thanks for asking this question Joshua. These people seem to like it.

Something went wrong with that request. Please try again.