- 06 Apr, 2017 2 commits
-
-
Sean McGivern authored
Fix for three open redirect vulns using redirect_to url_for(params.merge))) See merge request !2082
-
Regis Boudinot authored
-
- 05 Apr, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 25 Mar, 2017 1 commit
-
-
Sam Rose authored
-
- 21 Mar, 2017 2 commits
-
-
Oswaldo Ferreira authored
-
DJ Mountney authored
fix for render json include leaks See merge request !2074
-
- 20 Mar, 2017 1 commit
-
-
Sam Rose authored
-
- 13 Mar, 2017 7 commits
-
-
Bob Van Landuyt authored
That way the check is the same in the service & the controller
-
Bob Van Landuyt authored
merge_request_for_resolving_discussions -> merge_request_to_resolve_discussions_of
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
And deduplicate the finding of MR's & discussions. Now the searching is done in the service, istead of the controller & the API.
-
Bob Van Landuyt authored
Delegate a discussion in a merge request into a new issue. The discussion wil be marked as resolved and a system note will be added linking to the newly created issue.
-
- 24 Feb, 2017 1 commit
-
-
Felipe Artur authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- 21 Feb, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 16 Feb, 2017 3 commits
-
-
blackst0ne authored
-
blackst0ne authored
-
blackst0ne authored
-
- 09 Feb, 2017 1 commit
-
-
Felipe Artur authored
-
- 07 Feb, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 20 Jan, 2017 2 commits
-
-
Mike Greiling authored
-
Mike Greiling authored
-
- 23 Dec, 2016 1 commit
-
-
Tiago Botelho authored
-
- 21 Dec, 2016 2 commits
-
-
Tiago Botelho authored
-
Tiago Botelho authored
-
- 05 Dec, 2016 1 commit
-
-
Bob Van Landuyt authored
When a merge request can only be merged when all discussions are resolved. This feature allows to easily delegate those discussions to a new issue, while marking them as resolved in the merge request. The user is presented with a new issue, prepared with mentions of all unresolved discussions, including the first unresolved note of the discussion, time and link to the note. When the issue is created, the discussions in the merge request will get a system note directing the user to the newly created issue.
-
- 19 Nov, 2016 1 commit
-
-
Ruben Davila authored
-
- 17 Nov, 2016 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
- 28 Oct, 2016 1 commit
-
-
Guilherme Salazar authored
fix issues pointed out in !6527 add task completion status feature to CHANGELOG
-
- 19 Oct, 2016 5 commits
-
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
- 06 Oct, 2016 1 commit
-
-
Stan Hu authored
The Sortable concern has a default scope that adds ORDER BY to all queries. EXPLAIN ANALYZE shows that this additional ORDER BY statement causes the SQL optimizer to use the wrong index, which leads to a load time of 2.9 s vs 0.073 ms just for the SELECT call. The minimal change here is to re-implement find_by using where and reorder to remove the ORDER BY clause in IssuesController#index. Closes #23075
-