Find a file
Bob Van Landuyt 8ad9c4e873 Rename create_merge_request permissions
So we can distinguish between the permissions on the source and the
target project.

- `create_merge_request_from` indicates a user can create a merge
  request with the project as a source_project
- `create_merge_request_in` indicates a user can create a merge
  request with the project as a target_project
2018-04-11 10:51:15 +02:00
.github
.gitlab Merge branch 'docs-add-qa-step-to-database-mr-template' into 'master' 2018-04-03 16:34:21 +00:00
app Rename create_merge_request permissions 2018-04-11 10:51:15 +02:00
bin [Rails5] Allow using RAILS5 env with rspec 2018-04-03 10:01:34 +11:00
builds
changelogs Revert "Merge branch 'improve-jobs-queuing-time-metric' into 'master'" 2018-04-10 10:41:08 +00:00
config Projects and groups badges settings UI 2018-04-08 10:20:05 +00:00
db Rename create_merge_request permissions 2018-04-11 10:51:15 +02:00
doc Update documentation 2018-04-11 09:29:27 +02:00
docker
features Migrate features/project/project.feature to RSpec and reorganize several Project feature specs 2018-04-09 18:04:09 -05:00
fixtures/emojis
generator_templates Run plugins as separate process and pass data via STDIN 2018-02-26 16:06:49 +02:00
lib Rename delete_protected_branch ability to push_to_delete_protected_branch to prevent confusion with destroy_protected_branch 2018-04-10 15:46:20 +02:00
locale Merge branch 'bvl-port-translations-from-ee' into 'master' 2018-04-05 17:39:34 +00:00
log
plugins/examples Reorganize plugins dir structure 2018-02-26 16:06:49 +02:00
public Add the /help page in robots.txt 2018-03-22 10:55:02 +01:00
qa Remove unnecessary section looking in admin settings qa 2018-04-03 18:09:53 +03:00
rubocop Add cop for has_many :through without disabled autoloading 2018-04-09 12:47:04 +01:00
scripts Use standard codequality job 2018-04-04 10:01:52 +00:00
shared
spec Rename create_merge_request permissions 2018-04-11 10:51:15 +02:00
symbol
tmp
vendor Override the Prometheus server name 2018-04-05 13:03:38 -04:00
.babelrc prettify all node scripts 2018-03-23 11:52:54 -05:00
.codeclimate.yml Don't run RuboCop nor ESLint checks in the codequality job as this is already done by the static-analysis job 2018-04-04 17:27:32 +02:00
.csscomb.json
.eslintignore update eslintignore for node scripts 2018-03-23 11:53:12 -05:00
.eslintrc Prettier Phase 1: Prettier Configuration, Prettifying of files and documentation 2018-03-14 19:32:36 +00:00
.flayignore Make all workhorse gitaly calls opt-out, take 2 2018-03-28 14:13:06 +02:00
.foreman
.gitignore gitignore for vscode config file 2018-03-28 18:13:42 +11:00
.gitlab-ci.yml Update Security Products jobs definitions 2018-04-10 12:59:22 +00:00
.haml-lint.yml
.mailmap
.nvmrc
.pkgr.yml
.prettierignore ensure stylesheets are included as well, make prettierrc even more inclusive 2018-03-23 12:56:57 -05:00
.prettierrc ensure stylesheets are included as well, make prettierrc even more inclusive 2018-03-23 12:56:57 -05:00
.rubocop.yml Merge branch 'fj-15329-services-callbacks-ssrf' into 'security-10-6' 2018-03-21 14:39:21 +00:00
.rubocop_todo.yml Moved o_auth/saml/ldap modules under gitlab/auth 2018-02-28 16:53:02 +01:00
.ruby-version Bump .ruby-version from 2.3.6 to 2.3.7 2018-04-09 06:47:08 -07:00
.scss-lint.yml Web IDE blob image + default fallback 2018-04-06 17:49:06 +00:00
CHANGELOG.md Update CHANGELOG.md for 10.6.4 2018-04-09 15:57:21 -05:00
config.ru Increase the memory limits used in the unicorn killer 2018-03-22 17:21:10 -07:00
CONTRIBUTING.md Merge branch 'patch-28-docs' into 'master' 2018-03-09 11:33:29 +00:00
doc_styleguide.md
docker-compose.yml
Gemfile Use Goldiloader for handling N+1 queries 2018-04-09 11:58:06 +01:00
Gemfile.lock Use Goldiloader for handling N+1 queries 2018-04-09 11:58:06 +01:00
Gemfile.rails5 [Rails5] Add Gemfile.rails5 2018-03-15 09:50:16 +11:00
Gemfile.rails5.lock [Rails5] Add rails-controller-testing gem 2018-04-08 15:55:08 +11:00
GITALY_SERVER_VERSION Use Gitaly 0.95.0 2018-04-09 14:43:07 +02:00
GITLAB_PAGES_VERSION Update GitLab Pages 2018-04-05 15:46:48 +01:00
GITLAB_SHELL_VERSION Use gitlab-shell 7.1.2 2018-04-09 15:28:46 +02:00
GITLAB_WORKHORSE_VERSION Upgrade Workhorse to 4.0.0 2018-03-07 16:48:58 +01:00
LICENSE
MAINTENANCE.md
package.json Update GitLab SVGs version 2018-04-09 09:54:12 +01:00
PROCESS.md Clarify that the Pick Into X.Y label is added after approval 2018-03-08 10:29:53 +00:00
Procfile Launch mail_room manually and remove foreman reference 2018-03-21 11:52:05 -05:00
Rakefile
README.md
VERSION Update VERSION to 10.7.0-pre 2018-03-22 08:59:44 +01:00
yarn.lock Update GitLab SVGs version 2018-04-09 09:54:12 +01:00

GitLab

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

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 getting started 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.