An error occurred fetching the project authors.
- 01 Feb, 2016 3 commits
-
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/9265
-
Robert Speicher authored
-
Robert Speicher authored
[ci skip]
-
- 29 Jan, 2016 4 commits
-
-
Douwe Maan authored
-
Drew Blessing authored
-
Josh Frye authored
-
Josh Frye authored
-
- 28 Jan, 2016 3 commits
-
-
Robert Speicher authored
This partially reverts 6a5cd3ca - we keep the migration and add a new migration that reverts it in order to keep migration history intact.
-
Douwe Maan authored
-
Dmitriy Zaporozhets authored
* Follow REST for merge request API route * Remove repeating comments API for MR Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 Jan, 2016 8 commits
-
-
Robert Speicher authored
[ci skip]
-
Robert Speicher authored
[ci skip]
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Kamil Trzcinski authored
Due to broken implementation of attribute_for_keys the runner information was not updated correctly. This MR adds test to check that such scenario will never happen again.
-
James Lopez authored
-
Robert Speicher authored
[ci skip]
-
- 26 Jan, 2016 8 commits
-
-
Blake Hitchcock authored
The pattern in the `::reference_pattern` class method in the ExternalIssue model does not match all valid forms of JIRA project names. I have updated the regex to match JIRA project names with numbers and underscores. More information on valid JIRA project names can be found here: https://confluence.atlassian.com/jira/changing-the-project-key-format-192534.html * The first character must be a letter, * All letters used in the project key must be from the Modern Roman Alphabet and upper case, and * Only letters, numbers or the underscore character can be used.
-
Grzegorz Bizon authored
This has been fixed in Workhorse [ci skip]
-
Zeger-Jan van de Weg authored
Fixes #3951 Warning style the same as the warning a user sees on a archived project.
-
Rémy Coutable authored
When using ActiveRecord::Base.connection.active? without a DB connection, we get a "PG::ConnectionBad: could not connect to server" error because ActiveRecord::Base.connection doesn't exist. By using ActiveRecord::Base.connected? we ensure we don't get this error if the connection is missing, which is the all point of the Gitlab::CurrentSettings#connect_to_db? method!
-
Zeger-Jan van de Weg authored
Introduced by me through !2005
-
Douglas Barbosa Alexandre authored
-
Grzegorz Bizon authored
-
Robert Speicher authored
[ci skip]
-
- 23 Jan, 2016 1 commit
-
-
Benedict Etzel authored
Closes #12517
-
- 22 Jan, 2016 3 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Stan Hu authored
Leaving out the -I option in "git grep" would cause an Error 500 because the resulting line would include "Binary file X matches"
-
Achilleas Pipinellis authored
[ci skip]
-
- 21 Jan, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 20 Jan, 2016 6 commits
-
-
Robert Speicher authored
[ci skip]
-
Kamil Trzcinski authored
-
James Lopez authored
-
Stan Hu authored
Closes #6077
-
Tomasz Maczukin authored
-
Douglas Barbosa Alexandre authored
-
- 19 Jan, 2016 3 commits
-
-
Robert Speicher authored
- Add attribution for Anton Baklanov - Remove attributions for employees [ci skip]
-
Anton Baklanov authored
Fixes #2098
-
Rémy Coutable authored
This commits also fixes two minor issues: - Ensure notes that the current user is not allowed to see are not returned in the AJAX notes loading - Ensure the notes counter badge is decremented of 1 instead of 2
-