- 15 Dec, 2017 3 commits
-
-
Oswaldo Ferreira authored
requests
-
Lin Jen-Shin authored
-
Annabel Dunstone Gray authored
-
- 14 Dec, 2017 3 commits
-
-
Rémy Coutable authored
I've followed the [upgrade guide](https://github.com/thoughtbot/factory_bot/blob/4-9-0-stable/UPGRADE_FROM_FACTORY_GIRL.md) and ran these two commands: ``` grep -e FactoryGirl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|FactoryGirl|FactoryBot|" grep -e factory_girl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|factory_girl|factory_bot|" ``` Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Phil Hughes authored
-
Phil Hughes authored
-
- 13 Dec, 2017 2 commits
-
-
Ahmad Sherif authored
Closes gitaly#808
-
Zeger-Jan van de Weg authored
-
- 12 Dec, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 11 Dec, 2017 4 commits
-
-
Phil Hughes authored
-
Rubén Dávila authored
The endpoint was returning 404 because it was only searching on the current members of a Group or Project and not the access requesters.
-
Matija Čupić authored
-
Phil Hughes authored
Closes #15567
-
- 08 Dec, 2017 4 commits
-
-
Douwe Maan authored
Fixes project visibility guidelines See merge request gitlab/gitlabhq!2226 (cherry picked from commit 877c42c0aaf3298d6001614c9706bc366ae4014c) e4fd1c26 Ensure project wiki visibility guidelines are met
-
Luke Bennett authored
-
Luke Bennett authored
-
Bob Van Landuyt authored
Moving the check out of the general requests, makes sure we don't have any slowdown in the regular requests. To keep the process performing this checks small, the check is still performed inside a unicorn. But that is called from a process running on the same server. Because the checks are now done outside normal request, we can have a simpler failure strategy: The check is now performed in the background every `circuitbreaker_check_interval`. Failures are logged in redis. The failures are reset when the check succeeds. Per check we will try `circuitbreaker_access_retries` times within `circuitbreaker_storage_timeout` seconds. When the number of failures exceeds `circuitbreaker_failure_count_threshold`, we will block access to the storage. After `failure_reset_time` of no checks, we will clear the stored failures. This could happen when the process that performs the checks is not running.
-
- 07 Dec, 2017 9 commits
-
-
Eric Eastwood authored
-
micael.bergeron authored
-
micael.bergeron authored
-
micael.bergeron authored
-
micael.bergeron authored
-
micael.bergeron authored
add a spec for commit merge request diff notes
-
Douwe Maan authored
-
Jarka Kadlecova authored
-
Mike Greiling authored
-
- 05 Dec, 2017 6 commits
-
-
Matija Čupić authored
-
Felipe Artur authored
-
Felipe Artur authored
-
Filipa Lacerda authored
-
Shinya Maeda authored
-
Jan Provaznik authored
* new merge request can be created by sending an email to the specific email address (similar to creating issues by email) * for the first iteration, source branch must be specified in the mail subject, other merge request parameters can not be set yet * user should enable "Receive notifications about your own activity" in user settings to receive a notification about created merge request Part of #32878
-
- 04 Dec, 2017 6 commits
-
-
bikebilly authored
-
Markus Koller authored
-
Matija Čupić authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 03 Dec, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Luke Bennett authored
-