Find a file
connorshea 3a196317ab Add "sprite" parameter to emoji_icon helper
The emoji_icon helper used to display the award emoji in Issue and
Merge Request views. By default the spritesheet is used, but passing
`sprite: false` to the `emoji_icon` helper makes the emoji render as
separate images.

For award emoji displayed by default (e.g. thumbs-up, thumbs-down, and
any that have been awarded to the issue/MR) the independent images are
used. Only when the full emoji menu is opened does the full spritesheet
load.

On a normal issue this change decreases the page load by 670KB or 250KB
depending on pixel density.

Resolves #14334.
2016-04-08 17:38:31 -06:00
app Add "sprite" parameter to emoji_icon helper 2016-04-08 17:38:31 -06:00
bin
builds
config Remove dumb debug statement and add many tests. 2016-04-07 08:47:29 -04:00
db Remove "Congratulations!" tweet button on newly-created project. 2016-03-31 17:09:36 -06:00
doc Merge branch 'master' of https://gitlab.com/gitlab-org/gitlab-ce into no-gc-auto 2016-04-07 12:43:35 +02:00
docker
features Revert "Merge branch 'new-navigation-prototype' into 'master'" 2016-04-07 21:20:16 +00:00
fixtures/emojis Pre-calculate Emoji digests 2016-03-30 19:29:17 +02:00
lib Merge branch 'api-filter-milestone' into 'master' 2016-04-07 08:45:35 +00:00
log
public
scripts
shared
spec Merge branch 'issue_14012' into 'master' 2016-04-07 15:19:56 +00:00
tmp
vendor/assets Fix broken functionality in sidebar after merge. 2016-03-25 09:48:12 -04:00
.csscomb.json Fixes last remaining lints and enables scss-lint test for GitLab CI. 2016-03-22 15:01:31 -06:00
.flayignore
.foreman
.gitattributes
.gitignore
.gitlab-ci.yml Optimise .gitlab-ci.yml 2016-04-06 15:56:06 +02:00
.hound.yml
.pkgr.yml
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml Add comments to the SCSS Lint config file [ci skip] 2016-04-04 17:48:24 -06:00
.simplecov
.teatro.yml
CHANGELOG Add "sprite" parameter to emoji_icon helper 2016-04-08 17:38:31 -06:00
config.ru
CONTRIBUTING.md
doc_styleguide.md
docker-compose.yml
Gemfile Update coveralls from 0.8.9 to 0.8.13 and simplecov from 0.10.0 to 0.11.2 2016-04-06 23:54:28 -06:00
Gemfile.lock Update coveralls from 0.8.9 to 0.8.13 and simplecov from 0.10.0 to 0.11.2 2016-04-06 23:54:28 -06:00
GITLAB_SHELL_VERSION Updated gitlab-shell to 2.7 2016-03-29 15:46:47 +02:00
GITLAB_WORKHORSE_VERSION
LICENSE
MAINTENANCE.md
PROCESS.md
Procfile
Rakefile
README.md
VERSION Bump VERSION 2016-03-26 11:16:25 +01:00

GitLab

build status Build Status Code Climate Coverage Status

Canonical source

The source of GitLab Community Edition is hosted on GitLab.com and there are mirrors to make contributing as easy as possible.

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
  • 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

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.

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
  • Ruby (MRI) 2.1
  • Git 2.7.4+
  • Redis 2.8+
  • MySQL or PostgreSQL

For more information please see the architecture documentation.

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