- 03 2月, 2016 1 次提交
-
-
由 Robert Speicher 提交于
[ci skip]
-
- 02 2月, 2016 3 次提交
-
-
由 Michi302 提交于
-
由 Robert Speicher 提交于
[ci skip]
-
由 Stan Hu 提交于
Closes https://github.com/gitlabhq/gitlabhq/issues/9265
-
- 01 2月, 2016 3 次提交
-
-
由 Yorick Peterse 提交于
Instead of running ClosingIssueExtractor for every commit in a merge request we can gather all the commit messages (and the merge request description), concatenate all this together and then run ClosingIssueExtractor only once. The result of this is that MergeRequest#closes_issues is now between 3.5x and 4x faster than the old setup. Using a merge request with 10 commits (each referencing a number of issues to close) this reduced the call duration from around 200 milliseconds to around 50 milliseconds. As a result of these changes the Jira related tests for MergeRequest#closes_issues have been removed. These tests stubbed Commit#closes_issues meaning that the only code that was really tested was the call to Array#uniq to filter out duplicate issues. As this code is no longer used (nor present) the corresponding tests were removed. Related: gitlab-org/gitlab-ce#12419
-
由 Robert Speicher 提交于
-
由 Robert Speicher 提交于
[ci skip]
-
- 30 1月, 2016 2 次提交
-
-
由 Stan Hu 提交于
-
由 Douwe Maan 提交于
-
- 29 1月, 2016 4 次提交
-
-
由 Drew Blessing 提交于
-
由 Josh Frye 提交于
-
由 Josh Frye 提交于
-
由 Robert Speicher 提交于
This partially reverts 6a5cd3ca - we keep the migration and add a new migration that reverts it in order to keep migration history intact.
-
- 28 1月, 2016 5 次提交
-
-
由 Douwe Maan 提交于
-
由 Dmitriy Zaporozhets 提交于
* Follow REST for merge request API route * Remove repeating comments API for MR Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Robert Speicher 提交于
[ci skip]
-
由 Robert Speicher 提交于
[ci skip]
-
由 Douwe Maan 提交于
-
- 27 1月, 2016 7 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Kamil Trzcinski 提交于
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 提交于
-
由 Robert Speicher 提交于
[ci skip]
-
由 Blake Hitchcock 提交于
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 提交于
This has been fixed in Workhorse [ci skip]
-
- 26 1月, 2016 6 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Fixes #3951 Warning style the same as the warning a user sees on a archived project.
-
由 Rémy Coutable 提交于
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 提交于
Introduced by me through !2005
-
-
由 Grzegorz Bizon 提交于
-
由 Robert Speicher 提交于
[ci skip]
-
- 24 1月, 2016 1 次提交
-
-
由 Benedict Etzel 提交于
Closes #12517
-
- 23 1月, 2016 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Stan Hu 提交于
Leaving out the -I option in "git grep" would cause an Error 500 because the resulting line would include "Binary file X matches"
-
- 22 1月, 2016 1 次提交
-
-
由 Achilleas Pipinellis 提交于
[ci skip]
-
- 21 1月, 2016 4 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Robert Speicher 提交于
[ci skip]
-
由 Kamil Trzcinski 提交于
-
由 James Lopez 提交于
-
- 20 1月, 2016 1 次提交
-
-
由 Stan Hu 提交于
Closes #6077
-