Go to file
Mike Greiling ee6de1d34f ignore karma config in eslint 2017-01-10 12:30:40 -06:00
.github
.gitlab
app Correct merge conflicts 2017-01-10 12:30:39 -06:00
bin Remove trailing whitespace when generating changelog entry 2016-12-09 12:25:29 +01:00
builds
changelogs Merge branch '26226-generate-all-haml-fixtures-within-teaspoon-fixtures-task' into 'master' 2017-01-06 16:12:59 +00:00
config Swapped out teaspoon for karma 2017-01-10 12:30:40 -06:00
db Whitelist next project names: assets, profile, public 2017-01-06 11:14:17 +02:00
doc Merge branch '19966-api-call-to-move-project-to-different-group-fails-when-using-group-and-project-names-instead-of-id' into 'master' 2017-01-05 18:10:24 +00:00
docker
features Move admin deploy keys spinach to rspec 2017-01-03 13:53:42 +05:00
fixtures/emojis
generator_templates
lib Swapped out teaspoon for karma 2017-01-10 12:30:40 -06:00
log
public Rename logo, apply for Slack too 2017-01-03 15:01:28 +01:00
rubocop
scripts
shared
spec Swapped out teaspoon for karma 2017-01-10 12:30:40 -06:00
tmp
vendor Swapped out teaspoon for karma 2017-01-10 12:30:40 -06:00
.csscomb.json
.eslintignore ignore karma config in eslint 2017-01-10 12:30:40 -06:00
.eslintrc migrate all javascript asset bundles and require syntax 2017-01-10 12:30:38 -06:00
.flayignore
.foreman
.gitattributes
.gitignore
.gitlab-ci.yml move webpack asset compilation to the setup-test-env stage 2017-01-10 12:30:40 -06:00
.haml-lint.yml HAMLLint: Enable `SpaceInsideHashAttributes` rule 2016-12-31 11:48:42 +05:30
.mailmap
.pkgr.yml
.rspec
.rubocop.yml exempt node_modules from rubocop linting 2017-01-10 12:30:39 -06:00
.rubocop_todo.yml
.ruby-version
.scss-lint.yml
CHANGELOG.md Update CHANGELOG.md for 8.15.2 2016-12-28 12:31:37 +01:00
CONTRIBUTING.md Link to k8s contributing doc. 2016-12-27 13:22:02 +01:00
GITLAB_SHELL_VERSION Bump gitlab-shell to 4.1.1 2016-12-16 14:31:07 +01:00
GITLAB_WORKHORSE_VERSION Use gitlab-workhorse 1.2.1 2016-12-20 16:50:39 +01:00
Gemfile add webpack, webpack-rails, and webpack-dev-server along with a simple hello world test 2017-01-06 10:21:01 -06:00
Gemfile.lock add webpack, webpack-rails, and webpack-dev-server along with a simple hello world test 2017-01-06 10:21:01 -06:00
LICENSE
MAINTENANCE.md
PROCESS.md Remove "up-for-grabs" label from PROCESS.md 2016-12-28 11:27:51 +00:00
Procfile add webpack, webpack-rails, and webpack-dev-server along with a simple hello world test 2017-01-06 10:21:01 -06:00
README.md Update stack information and remove redundancy 2016-12-24 19:59:03 +00:00
Rakefile
VERSION Update VERSION to 8.16.0-pre 2016-12-22 14:51:57 -02:00
config.ru
doc_styleguide.md
docker-compose.yml
package.json Swapped out teaspoon for karma 2017-01-10 12:30:40 -06:00

README.md

GitLab

Build status CE coverage report Code Climate Core Infrastructure Initiative Best Practices

Canonical source

The canonical source of GitLab Community Edition is hosted on GitLab.com.

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
  • Complete continuous integration (CI) and CD pipelines to builds, test, and deploy your applications
  • Each project can also have an issue tracker, issue board, 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)

Hiring

We're hiring developers, support people, and production engineers all the time, please see our jobs page.

Editions

There are two editions of GitLab:

  • GitLab Community Edition (CE) is available freely under the MIT Expat license.
  • GitLab Enterprise Edition (EE) includes extra features that are more useful for organizations with more than 100 users. To use EE and get official support please become a subscriber.

Website

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

Requirements

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

Installation

The recommended way to install GitLab is with the Omnibus packages on our package server. 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.

Contributing

GitLab is an open source project and we are very happy to accept community contributions. Please refer to CONTRIBUTING.md for details.

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.

Software stack

GitLab is a Ruby on Rails application that runs on the following software:

  • Ubuntu/Debian/CentOS/RHEL/OpenSUSE
  • Ruby (MRI) 2.3
  • Git 2.8.4+
  • Redis 2.8+
  • PostgreSQL (preferred) or MySQL

For more information please see the architecture documentation.

UX design

Please adhere to the UX Guide when creating designs and implementing code.

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

For more information about the release process see the release documentation.

Upgrading

For upgrading information please see our update page.

Documentation

All documentation can be found on docs.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.