Go to file
Rémy Coutable d361bca1d1 Don't include branch name in Knapsack report file
Otherwise, branches other than master won't benefit from Knapsack!

Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-03-28 15:23:58 +02:00
.github Address feedback about wording. 2016-06-09 11:25:47 -06:00
.gitlab documentation blurb in issue template 2017-03-17 11:43:32 +00:00
app Merge branch '23363-use-strong-params-in-wikis-controller' into 'master' 2017-03-28 07:47:35 +00:00
bin Add gitaly source installation instructions 2017-03-21 14:55:41 +01:00
builds
changelogs Merge branch '23363-use-strong-params-in-wikis-controller' into 'master' 2017-03-28 07:47:35 +00:00
config spread out webpack bundles per-line to reduce conflicts in EE 2017-03-27 16:11:02 -05:00
db Merge branch 'sh-bring-back-option-to-be-notified-of-own-activity' into 'master' 2017-03-27 15:55:47 +00:00
doc Adds entry about kebab case props in documentation 2017-03-27 22:36:58 +00:00
docker Update README.md 2016-10-13 14:43:05 +00:00
features Fix up emoji tests that should have failed :/ 2017-03-24 21:19:34 -05:00
fixtures/emojis Fix reference to node_modules in built package 2017-03-08 10:41:16 -06:00
generator_templates Support for post deployment migrations 2016-10-31 12:54:48 +01:00
lib Fix Gitlab::EeCompatCheck: use `ee_branch_found` instead of `ee_branch` 2017-03-28 09:26:47 +02:00
log
public Remove legacy build status svg for deprecated service 2017-03-01 14:51:02 +01:00
qa Merge branch 'fix/gb/gitlab-qa-start-page-cold-boot' into 'master' 2017-03-17 17:31:21 +00:00
rubocop Add cop to ensure reversibility of add_concurrent_index 2017-03-07 10:09:01 -06:00
scripts Save Knapsack reports in S3 instead of in shared cache 2017-03-24 18:18:37 +01:00
shared Add GitLab Pages 2017-01-31 22:50:39 +00:00
spec Add a new `stub_mattermost_setting` stub helper to properly stub Mattermost settings 2017-03-28 14:12:32 +02:00
tmp Add gitaly source installation instructions 2017-03-21 14:55:41 +01:00
vendor remove Cookies class from global space 2017-03-22 03:07:27 -05:00
.babelrc Only add frontend code coverage instrumentation when generating coverage report 2017-03-20 22:29:45 +00:00
.csscomb.json Remove SCSS rules for short hex chars. 2016-10-03 20:40:22 -04:00
.eslintignore ignore karma config in eslint 2017-01-10 12:30:40 -06:00
.eslintrc Adjust ESLint rule for file names 2017-03-05 20:42:49 +01:00
.flayignore [Issue sorting]Addressed review comments 2017-03-14 14:11:59 +02:00
.foreman
.gitignore add webpack bundle analyzer to production output 2017-02-21 16:29:35 -06:00
.gitlab-ci.yml Don't include branch name in Knapsack report file 2017-03-28 15:23:58 +02:00
.haml-lint.yml HAMLLint: Enable `MultilinePipe` rule 2017-01-24 10:09:28 -08:00
.mailmap Add an initial .mailmap 2016-08-06 23:21:11 +02:00
.pkgr.yml Update .pkgr.yml with Ubuntu 16.04 dependencies 2016-09-20 17:35:49 +02:00
.rspec
.rubocop.yml Ignore builds dir when run rubocop check 2017-02-28 14:13:01 +02:00
.rubocop_todo.yml Revert "Enable Style/DotPosition" 2017-02-23 09:33:19 -06:00
.ruby-version Bump ruby version 2016-12-03 15:57:20 +01:00
.scss-lint.yml Enable ColorVariable in scss-lint 2016-12-01 20:22:51 -05:00
CHANGELOG.md Move the 9.0.0 CHANGELOG entries to the top 2017-03-22 11:30:33 +01:00
CONTRIBUTING.md Creates Frontend Style guide 2017-03-22 19:30:54 +00:00
GITALY_SERVER_VERSION Bump Gitaly server version to v0.4.0 2017-03-24 13:51:43 +02:00
GITLAB_PAGES_VERSION Use GitLab Pages v0.4.0 2017-03-13 11:23:46 +00:00
GITLAB_SHELL_VERSION Update GITLAB_SHELL_VERSION to 5.0.0 2017-03-08 15:07:35 +01:00
GITLAB_WORKHORSE_VERSION Use gitlab-workhorse 1.4.2 2017-03-24 10:59:16 +01:00
Gemfile Update sentry-raven 2.0.2 -> 2.4.0 2017-03-26 20:29:41 -04:00
Gemfile.lock Update sentry-raven 2.0.2 -> 2.4.0 2017-03-26 20:29:41 -04:00
LICENSE Update LICENSE to 2017 2017-02-08 22:58:40 +00:00
MAINTENANCE.md Update MAINTENANCE.md with our latest policy 2016-07-19 09:05:56 +03:00
PROCESS.md Update PROCESS.md 2017-02-09 18:41:41 +02:00
Procfile remove changes to Procfile 2017-02-01 16:23:26 -06:00
README.md Include JavaScript test coverage in coverage badge (!10097) 2017-03-23 19:22:30 +01:00
Rakefile Load knapsack in Rakefile only when is bundled 2016-06-07 20:02:03 +02:00
VERSION Update VERSION to 8.18.0-pre 2017-02-22 11:36:02 -03:00
config.ru Increase Unicorn memory limits to 300-350 2016-01-20 11:52:01 +01:00
doc_styleguide.md Move doc_styleguide in the development directory 2016-01-12 11:57:42 +01:00
docker-compose.yml Update docker guide and add docker-compose.yml 2015-09-30 14:24:39 +02:00
package.json Adds visbilityjs lib 2017-03-23 11:10:31 +00:00
yarn.lock Adds visbilityjs lib 2017-03-23 11:10:31 +00:00

README.md

GitLab

Build status Overall test coverage Code Climate Core Infrastructure Initiative Best Practices

Test coverage

  • Ruby coverage Ruby
  • JavaScript coverage JavaScript

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.