An error occurred fetching the project authors.
- 19 Sep, 2017 1 commit
-
-
Andrew Newdigate authored
-
- 06 Sep, 2017 2 commits
-
-
Tiago Botelho authored
-
micael.bergeron authored
this will remove the need make N queries (per-note) at the cost of having to mark notes with an attribute this opens up the possibility for other special roles for notes
-
- 05 Sep, 2017 1 commit
-
-
Yorick Peterse authored
This changes the issue and MR index pages so the pagination system re-uses the output of the COUNT(*) query used to calculate the number of rows per state (opened, closed, etc). This removes the need for an additional COUNT(*) on both pages.
-
- 28 Aug, 2017 2 commits
-
-
Oswaldo Ferreira authored
-
Oswaldo Ferreira authored
-
- 15 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 07 Aug, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 26 Jul, 2017 1 commit
-
-
Tim Zallmann authored
-
- 14 Jul, 2017 1 commit
-
-
Filipa Lacerda authored
-
- 05 Jul, 2017 1 commit
-
-
Douwe Maan authored
-
- 28 Jun, 2017 1 commit
-
-
Douwe Maan authored
-
- 21 Jun, 2017 3 commits
-
-
Nick Thomas authored
-
Grzegorz Bizon authored
-
Nick Thomas authored
-
- 23 May, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 18 May, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 15 May, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 12 May, 2017 1 commit
-
-
Sean McGivern authored
I don't know why this happens exactly, but given an upstream and fork repository from a customer, both of which required GC, resolving conflicts would corrupt the fork so badly that it couldn't be cloned. This isn't a perfect fix for that case, because the MR may still need to be merged manually, but it does ensure that the repository is at least usable. My best guess is that when we generate the index for the conflict resolution (which we previously did in the target project), we obtain a reference to an OID that doesn't exist in the source, even though we already fetch the refs from the target into the source. Explicitly setting the source project as the place to get the merge index from seems to prevent repository corruption in this way.
-
- 09 May, 2017 2 commits
-
-
kushalpandya authored
-
Fatih Acet authored
-
- 03 May, 2017 1 commit
-
-
Douwe Maan authored
-
- 12 Apr, 2017 1 commit
-
-
- 11 Apr, 2017 1 commit
-
-
- 10 Apr, 2017 1 commit
-
-
Douwe Maan authored
-
- 08 Apr, 2017 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 06 Apr, 2017 3 commits
-
-
Toon Claes authored
Also poll for pipeline changes on: - Pipeline table on commit page - Pipeline table on merge request page - Pipeline table on new merge request page
-
Toon Claes authored
Do not check if coverage is enabled, just show it when it is available.
-
Sean McGivern authored
Fix for three open redirect vulns using redirect_to url_for(params.merge))) See merge request !2082
-
- 05 Apr, 2017 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 02 Apr, 2017 1 commit
-
-
Stan Hu authored
See !10263
-
- 27 Mar, 2017 1 commit
-
-
Sean McGivern authored
The instance variables set in this action are only used by the JSON response. Visiting `merge_requests/:iid/diffs` in a browser always loads the `show` action, so we don't need to find an MR diff, or an environment, in that case.
-
- 23 Mar, 2017 3 commits
-
-
Sanster authored
-
Shinya Maeda authored
-
Shinya Maeda authored
Use detailed_status effectively. Remove unnecesarry context(nest). Add new context in merge_requests_controller_spec.rb and fix a bug. Correct description of spec.
-