Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
GitLab is version control for your server
Ruby HTML CoffeeScript Cucumber CSS JavaScript Shell

Merge branch 'rake-update-commit-count' into 'master'

Add rake task 'gitlab:update_commit_count'

Starting with migration `20150717130904` commit count is stored in the
database. For existing projects it defaults to `0` and is updated to the
correct value when commits are pushed.

The newly introduced rake task updates the commit count for all projects
which have not been updated yet.

![gitlab-rake-update-commit-count](https://gitlab.com/gitlab-org/gitlab-ce/uploads/4785009e0f3fc4c3199fe65dfb8e60e0/gitlab-rake-update-commit-count.png)

Refs !986, !989, #2040, #2089.

See merge request !1040
latest commit 4a8076a35f
@vsizov vsizov authored
Failed to load latest commit information.
app Merge branch 'rs-dev-issue-306' into 'master'
bin Move prepare_build script to scripts dir.
config Allow custom label to be set for authentication providers.
db Check if session_expire_delay column exists before adding the column.
doc Add "Manage merge requests" permission to docs
docker Merge branch 'chef-docker' into 'master'
features Allow custom label to be set for authentication providers.
lib Merge branch 'rake-update-commit-count' into 'master'
log v1.0
public Replace old logo with new one
scripts Added missing packages required by docker builds
spec Merge branch 'rs-dev-issue-306' into 'master'
tmp Make sure important directories exist in git
vendor/assets Add nice scroll for sidebar
.foreman complete hooks for post receive
.gitattributes Use gitattribute merge=union to reduce CHANGELOG merge conflicts.
.gitignore Remove the volumes from the single image to keep it simple.
.gitlab-ci.yml Remove jasmine:ci task, execute teaspoon directly on CI
.hound.yml Make houndci prefer single quotes.
.pkgr.yml Use new way of defining services on packager.io
.rspec Make Fuubar the default rspec formatter
.rubocop.yml Enable rubocop for tests too
.ruby-version ruby 2.1.6
.simplecov organize simplecov
.teatro.yml teatro setup
CHANGELOG Merge branch 'rake-update-commit-count' into 'master'
CONTRIBUTING.md [ci skip] Changed the reference from gitlab cloud to gitlab.com becau…
GITLAB_SHELL_VERSION GitLab shell version to 2.6.3.
Gemfile Only load byebug on MRI
Gemfile.lock Bump coveralls version, remove explicit rest-client dependency
LICENSE LICENSE year update
MAINTENANCE.md Add note about semantic versioning not being absolute.
PROCESS.md Escape process text
Procfile Archive repositories in background worker.
README.md Clean up editions paragraph
Rakefile v1.0
VERSION Its 7.13 time :)
config.ru Disable Unicorn::WorkerKiller in non-production environments
doc_styleguide.md update documentation styleguide

README.md

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.

Included with the GitLab Omnibus Packages is GitLab CI that can easily build, test and deploy code.

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.0 or 2.1
  • Git 1.7.10+
  • Redis 2.0+
  • 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

Since 2011 a minor or major version of GitLab is released on the 22nd of every month. Patch and security releases are published when needed. New features are detailed on the blog and in the changelog. For more information about the release process see the release documentation. Features that will likely be in the next releases can be found on the feature request forum with the status started and completed.

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.

Something went wrong with that request. Please try again.