An error occurred fetching the project authors.
- 21 May, 2015 2 commits
-
-
Jeroen van Baarsen authored
**Why was this needed?** The changes are pulled in 7.12.0 but where mistakenly put under 7.11.0 [skip-ci] Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
Alex Connor authored
-
- 19 May, 2015 1 commit
-
-
Marin Jankovski authored
-
- 18 May, 2015 2 commits
-
-
Jakub Jirutka authored
-
Nikita Verkhovin authored
-
- 16 May, 2015 2 commits
-
-
Vinnie Okada authored
Tell new users when their password reset token expires and provide a link to get a new one.
-
Jakub Jirutka authored
-
- 15 May, 2015 2 commits
-
-
Fotis Gimian authored
-
Douwe Maan authored
-
- 14 May, 2015 5 commits
-
-
afc163 authored
Fixes #5825
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Stan Hu authored
Closes #1598
-
- 13 May, 2015 2 commits
-
-
Jacob Vosmaer authored
This makes the memory growth-triggered Sidekiq restarts more reliable by reducing the chance that Sidekiq ends up in a state where it is not accepting new jobs but also not shutting down: SIGKILL is more likely to work than SIGTERM.
-
Arthur Gautier authored
Call merge request web hook every times a new commit hits the source branch Signed-off-by: Arthur Gautier <baloo@gandi.net>
-
- 12 May, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 09 May, 2015 3 commits
-
-
Robert Speicher authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 08 May, 2015 2 commits
-
-
Maran authored
-
bugagazavr authored
-
- 07 May, 2015 4 commits
-
-
Stan Hu authored
This would result in a 404 error in certain views. The `save` call was being rolled back due to an error in the validation step. Relax the validation step so that this works. Closes #1570
-
Jacob Vosmaer authored
It looks like SIGTERM may not be enough to shut down a Sidekiq process when its RSS has gotten too big. This change will allow us to experiment with sending SIGKILL instead of SIGTERM to Sidekiq processes on gitlab.com.
-
Hannes Rosenögger authored
-
Robert Speicher authored
[ci skip]
-
- 06 May, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Stan Hu authored
In an empty repository, pushing a new branch not called "master" would leave HEAD in an unknown state, causing ambiguity if another branch were pushed. This could in turn cause a new protected branch to be created and cause the default branch to change. * Closes #1561 * Closes #1576 * Closes https://github.com/gitlabhq/gitlabhq/issues/8883
-
- 05 May, 2015 3 commits
-
-
Alex Lossent authored
Diffs with a large number of changed lines time out (504 HTTP error) or generate a HTML page that's so heavy web browsers struggle with it. https://github.com/gitlabhq/gitlabhq/pull/5014 introduced limits on commit line count so that only a safe portion is rendered. This was later undone by code refactoring in be5b6db8, e0eb4803 and c741fcab. This patch re-introduces a safe limit on number of lines.
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Valery Sizov authored
-
- 04 May, 2015 2 commits
-
-
Stan Hu authored
Bump gitlab_git to 7.1.11 to fix bug where viewing a tag on a project with submodules would return a 500 error Closes https://github.com/gitlabhq/gitlabhq/issues/8411
-
Sven Selberg authored
-
- 03 May, 2015 1 commit
-
-
Ben Bodenmiller authored
-
- 02 May, 2015 4 commits
-
-
Onur Küçük authored
-
Stan Hu authored
This feature was requested long ago: http://feedback.gitlab.com/forums/176466-general/suggestions/4118466-ability-to-register-only-from-ceratain-domains This MR is based off !253 but changed to use application settings and use wildcard strings to give more flexibility in pattern matching. Regexps seemed overkill and easy to get wrong. Only restrict e-mail addresses upon creation
-
jubianchi authored
-
Stan Hu authored
sent through Devise Fix test case that was passing due to a broken `around` statement. Closes #1556
-
- 30 Apr, 2015 1 commit
-
-
Dominik Sander authored
This groups milestones by title for issue views like it has been done for the milestone dashboard/project overview. Before milestones with the same title would show up multiple times in the filter dropdown and one could only filter per project and milestone. Now the milestone filter is based on the title of the milestone, i.e. all issues marked with the same milestone title are shown.
-