Find a file
Rémy Coutable e484a06472 Retrieve PR comments only when we know there are any
The Pull Request resource doesn't include the `comments` field, while
the Issue resource does. And since we're looping through all issues
anyway, we can freely check if the issue is a PR and has comments and in
this case only fetch comments for it.

That means if you have 1000 PRs but only 200 with comments, you will do
200 API requests instead of 1000. :notbad:

Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-09-26 19:17:00 +02:00
.github
.gitlab
app Merge branch 'avatar_n_plus_one' into 'master' 2017-09-26 17:06:49 +00:00
bin
builds
changelogs Merge branch 'dm-simple-project-avatar-url' into 'master' 2017-09-26 14:28:38 +00:00
config Move new nav into main CSS folder 2017-09-25 10:11:42 -07:00
db Remove an unneeded index on ci_builds left in some databases 2017-09-26 11:33:20 +02:00
doc Merge branch 'doc-license-wtfpl-rejected' into 'master' 2017-09-26 15:18:18 +00:00
docker
features Improve list of sorting options 2017-09-23 11:46:53 +11:00
fixtures/emojis
generator_templates
lib Retrieve PR comments only when we know there are any 2017-09-26 19:17:00 +02:00
locale Add unextracted strings for i18n 2017-09-21 14:24:26 +05:30
log
public
qa
rubocop
scripts Check for exec permissions also in app/ 2017-09-25 10:59:25 +02:00
shared
spec Merge branch 'dm-simple-project-avatar-url' into 'master' 2017-09-26 14:28:38 +00:00
symbol Resolve "Better SVG Usage in the Frontend" 2017-09-22 08:39:47 +00:00
tmp
vendor
.babelrc
.codeclimate.yml
.csscomb.json
.eslintignore Resolve "Better SVG Usage in the Frontend" 2017-09-22 08:39:47 +00:00
.eslintrc
.flayignore
.foreman
.gitignore
.gitlab-ci.yml Do not clone the repo when running the review-docs jobs 2017-09-21 16:19:24 +02:00
.haml-lint.yml
.mailmap
.nvmrc
.pkgr.yml
.rubocop.yml
.rubocop_todo.yml
.ruby-version
.scss-lint.yml
CHANGELOG.md Update CHANGELOG.md for 10.0.1 2017-09-23 20:56:52 -04:00
config.ru
CONTRIBUTING.md
doc_styleguide.md
docker-compose.yml
Gemfile Update omniauth-azure-oauth2 to 0.0.9 (Support Office 365 Germany) 2017-09-26 12:30:48 +02:00
Gemfile.lock Update omniauth-azure-oauth2 to 0.0.9 (Support Office 365 Germany) 2017-09-26 12:30:48 +02:00
GITALY_SERVER_VERSION Migrate Gitlab::Git::Repository#diff to Gitaly 2017-09-21 11:05:06 +02:00
GITLAB_PAGES_VERSION
GITLAB_SHELL_VERSION Update gitlab-shell to 5.9.2 2017-09-22 13:15:17 +00:00
GITLAB_WORKHORSE_VERSION
LICENSE
MAINTENANCE.md
package.json Resolve "Better SVG Usage in the Frontend" 2017-09-22 08:39:47 +00:00
PROCESS.md
Procfile
Rakefile
README.md
VERSION Bump VERSION to 10.1.0-pre 2017-09-21 20:28:58 +00:00
yarn.lock Resolve "Better SVG Usage in the Frontend" 2017-09-22 08:39:47 +00: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.