Find a file
Pierre de La Morinerie 466b768bb3 Send notification emails to the "project", and put people in Cc
This fixes email threading in Mail.app, that doesn't like when a thread
doesn't have stable recipients.

For instance, here is a possible sender-recipient combinations before:

From: A
To: Me
New issue

From: B
To: Me
Reply on new issue

From: A
To: Me
Another reply

Mail.app doesn't see B as a participant to the original email thread,
and decides to break the thread: it will group all messages from A
together, and separately all messages from B.

This commit makes the thread look like this:

From: A
To: gitlab/project
Cc: Me
New issue

From: B
To: gitlab/project
Cc: Me
Reply on new issue

From: A
To: gitlab/project
Cc: Me
Another reply

Mail.app sees a common recipient, and group the thread correctly.
2014-06-10 17:09:15 +02:00
app Send notification emails to the "project", and put people in Cc 2014-06-10 17:09:15 +02:00
bin Move from script to bin directory. 2014-05-27 17:14:41 +02:00
config Add users to /:id route 2014-06-07 15:06:55 +03:00
db
doc Merge branch 'https_documentation' into 'master' 2014-06-10 12:32:25 +00:00
features Revert "Revert "Fix for failing specs"" 2014-06-06 09:01:17 +03:00
lib Update check task and add to monthly release doc lines about gitlab_shell_version file. 2014-06-10 11:16:47 +02:00
log
public
spec Send notification emails to the "project", and put people in Cc 2014-06-10 17:09:15 +02:00
tmp
vendor
.foreman
.gitignore add smtp_settings.rb to gitignore file 2014-06-03 01:05:07 +08:00
.pkgr.yml
.rspec
.simplecov
.travis.yml Splitted the Spinach tests to prevent time-outs 2014-06-04 22:55:27 +02:00
CHANGELOG Fix typo 2014-06-07 16:39:48 +00:00
config.ru
CONTRIBUTING.md Update docs to markdown style guide. 2014-06-03 23:16:31 +02:00
Gemfile Revert "Revert "Fix for failing specs"" 2014-06-06 09:01:17 +03:00
Gemfile.lock Gem update for database_cleaner 2014-06-06 18:58:38 +02:00
GITLAB_SHELL_VERSION Add gitlab shell version file. 2014-06-10 10:00:12 +02:00
Guardfile
LICENSE Change the license to B.V. 2014-05-23 15:01:02 +02:00
MAINTENANCE.md Update docs to markdown style guide. 2014-06-03 23:16:31 +02:00
PROCESS.md Update docs to markdown style guide. 2014-06-03 23:16:31 +02:00
Procfile
Rakefile
README.md Update docs to markdown style guide. 2014-06-03 23:16:31 +02:00
VERSION Lets start 7.0 development 2014-05-22 20:34:03 +03:00

GitLab

Self hosted Git management software

logo

animated-screenshots

Open source software to collaborate on code

  • 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

Canonical source

Code status

  • build status on ci.gitlab.org (master branch)

  • Code Climate

  • Coverage Status

  • PullReview stats

Resources

Requirements

  • Ubuntu/Debian/CentOS/RHEL**
  • ruby 2.0+
  • git 1.7.10+
  • redis 2.0+
  • MySQL or PostgreSQL

** More details are in the requirements doc.

Installation

Please see the installation page on the GitLab website.

New versions

Since 2011 a minor or major version of GitLab is released on the 22nd of every month. Patch and security releases come out 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 updating the the Omnibus installation please see the update documentation. For manual installations there is an upgrader script and there are upgrade guides.

Run in production mode

The Installation guide contains instructions on how to download an init script and run it automatically on boot. You can also start the init script manually:

sudo service gitlab start

or by directly calling the script:

 sudo /etc/init.d/gitlab start

Please login with root / 5iveL!fe.

Install a development environment

We recommend setting up your development environment with the cookbook. If you do not use the cookbook you might need to copy the example development unicorn configuration file

cp config/unicorn.rb.example.development config/unicorn.rb

Run in development mode

Start it with Foreman

bundle exec foreman start -p 3000

or start each component separately:

bundle exec rails s
bin/background_jobs start

And surf to localhost:3000 and login with root / 5iveL!fe.

Run the tests

  • Run all tests:

    bundle exec rake test
    
  • RSpec unit and functional tests.

    All RSpec tests: bundle exec rake spec

    Single RSpec file: bundle exec rspec spec/controllers/commit_controller_spec.rb

  • Spinach integration tests.

    All Spinach tests: bundle exec rake spinach

    Single Spinach test: bundle exec spinach features/project/issues/milestones.feature

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.