Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
GitLab is version control for your server
branch: master
Failed to load latest commit information.
app Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce
bin Updated rspec to rspec 3.x syntax
config Merge branch 'timeout' into 'master'
db Issue #595: Support Slack notifications upon issue and merge request …
doc Merge branch 'web_hook_extend' into 'master'
docker Update Dockerfile for GitLab 7.8.1
features Spelling change Commit Statistics
lib Merge branch 'timeout' into 'master'
log v1.0
public Increase timeout for Git-over-HTTP requests.
safe Dont show gitlab.com import for gitlab.com :)
spec Add merge and issue event notification for HipChat
tmp Make sure important directories exist in git
vendor/assets Diff headers made sticky
.foreman complete hooks for post receive
.gitattributes Use gitattribute merge=union to reduce CHANGELOG merge conflicts.
.gitignore Sort .gitignore.
.hound.yml Make houndci prefer single quotes.
.pkgr.yml Use new way of defining services on packager.io
.rspec Remove --drb from .rspec
.rubocop.yml Enable ParenthesesAsGroupedExpression rule
.ruby-version GitLab does not work well with Ruby 2.2 yet
.simplecov organize simplecov
.teatro.yml teatro setup
CHANGELOG Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce
CONTRIBUTING.md Advise on how to help others.
GITLAB_SHELL_VERSION Bump gitlab-shell to 2.5.4
Gemfile Merge branch 'timeout' into 'master'
Gemfile.lock Merge pull request #8915 from gemnasium/update-gemnasium-to-0-2-5
Guardfile Updated the spring gem and fixed the guard file
LICENSE Change the license to B.V.
MAINTENANCE.md Update docs to markdown style guide.
PROCESS.md Escape process text
Procfile Fix sidekiq for development
README.md Remove pull-review badge since we dont use it
Rakefile v1.0
VERSION Time for 7.9.0.pre
config.ru Check specifically for Unicorn in rack config.ru file

README.md

logo GitLab

Open source software to collaborate on code

Animated screenshots

  • 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

Editions

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 get access to the EE and support please become a subscriber.

Canonical source

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

Code status

  • build status on ci.gitlab.org (master branch)

  • Build Status

  • Code Climate

  • Coverage Status

Website

On about.gitlab.com you can find more information about:

Requirements

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.

Installation

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 5iveL!fe, 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.

Upgrading

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.

Documentation

All documentation can be found on doc.gitlab.com/ce/.

Getting help

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

Is it any good?

Yes

Is it awesome?

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

Something went wrong with that request. Please try again.