Find a file
2014-12-30 14:00:07 +01:00
app Merge branch 'user_ssh_keys_on_admin' into 'master' 2014-12-30 12:02:16 +00:00
bin Revert "Delete mailer queue" 2014-09-10 15:28:58 +02:00
config Merge branch 'user_ssh_keys_on_admin' into 'master' 2014-12-30 12:02:16 +00:00
db Merge branch 'master' into developer_can_push_to_protected_branches_option 2014-12-29 09:30:55 +01:00
doc Add group filtering by name for API 2014-12-30 11:46:47 +02:00
docker Merge pull request #8458 from kfei/docker/reduce-image-size 2014-12-20 20:16:48 +02:00
features Fix the ssh keys test. 2014-12-30 11:47:13 +01:00
lib Clearer message if adding comment to commit via api fails. 2014-12-30 14:00:07 +01:00
log init commit 2011-10-09 00:36:38 +03:00
public Merge pull request #6879 from arantir/patch-1 2014-05-01 22:51:56 +03:00
spec Merge pull request #7675 from yglukhov/patch_notes_api 2014-12-29 21:06:49 +02:00
tmp Make sure important directories exist in git 2014-03-30 22:45:28 -04:00
vendor/assets remove 'vendor/plugins' dir 2014-12-27 19:23:21 +04:00
.foreman complete hooks for post receive 2012-01-08 13:20:20 +02:00
.gitignore Sort .gitignore. 2014-11-29 10:48:19 +01:00
.hound.yml Make houndci prefer single quotes. 2014-07-16 09:38:42 +03:00
.pkgr.yml Added cmake and pkg-config as build dependency for pkgr 2014-09-05 19:25:45 +02:00
.rspec Remove --drb from .rspec 2014-03-24 08:55:27 -04:00
.ruby-version ruby 2.1.5 in .ruby-version 2014-12-14 12:45:49 -08:00
.simplecov organize simplecov 2013-01-07 22:23:13 +02:00
.teatro.yml teatro setup 2014-06-17 11:21:49 +03:00
CHANGELOG Added changelog item 2014-12-29 16:41:50 +01:00
config.ru Check specifically for Unicorn in rack config.ru file 2014-01-23 18:24:31 +01:00
CONTRIBUTING.md Note what has to be updated for new packages. 2014-12-24 11:45:03 +01:00
Gemfile Merge branch 'check_browser_version' of https://github.com/vicvega/gitlabhq into vicvega-check_browser_version 2014-12-28 22:13:31 +02:00
Gemfile.lock Merge branch 'check_browser_version' of https://github.com/vicvega/gitlabhq into vicvega-check_browser_version 2014-12-28 22:13:31 +02:00
GITLAB_SHELL_VERSION Bump gitlab-shell 2014-11-24 12:06:42 +00:00
Guardfile Updated the spring gem and fixed the guard file 2014-08-16 14:30:44 +02:00
LICENSE Change the license to B.V. 2014-05-23 15:01:02 +02:00
MAINTENANCE.md Update docs to markdown style guide. 2014-06-03 23:16:31 +02:00
PROCESS.md Rephrase of the text 2014-12-15 10:41:30 +01:00
Procfile Fix sidekiq for development 2014-12-29 17:56:29 +02:00
Rakefile init commit 2011-10-09 00:36:38 +03:00
README.md Include default credentials in the readme and make all headers the same. 2014-12-17 11:07:10 +01:00
VERSION Let's start 7.7.0.pre 2014-12-28 22:52:17 +01:00

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

Canonical source

Code status

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

  • Build Status

  • Code Climate

  • Coverage Status

  • PullReview stats

Website

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

Requirements

  • Ubuntu/Debian/CentOS/RHEL**
  • ruby 2.0+
  • git 1.7.10+
  • redis 2.0+
  • MySQL or PostgreSQL

** More details are in the requirements doc.

Installation

Please see the installation page on the GitLab website for the various options. Since a manual installation is a lot of work and error prone we strongly recommend the fast and reliable Omnibus package installation (deb/rpm). You can access 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 applications and API wrappers for GitLab. Find them on our website.

New versions

Since 2011 a minor or major version of GitLab is released on the 22nd of every month. Patch and security releases come out 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 the Omnibus installation please see the update documentation. For manual installations there is an upgrader script and there are upgrade guides.

Install a development environment

We recommend setting up your development environment with the GitLab Development Kit. If you do not use the GitLab Development 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.