- 19 May, 2017 1 commit
-
-
tauriedavis authored
-
- 12 May, 2017 1 commit
-
-
Douwe Maan authored
-
- 11 May, 2017 1 commit
-
- 08 May, 2017 1 commit
-
-
Sam Rose authored
-
- 04 May, 2017 1 commit
-
-
Luke "Jared" Bennett authored
-
- 18 Apr, 2017 1 commit
-
-
Phil Hughes authored
Closes #30950
-
- 06 Apr, 2017 2 commits
-
-
Jose Ivan Vargas Lopez authored
-
James Edwards-Jones authored
Added changelog
-
- 03 Apr, 2017 1 commit
-
-
James Edwards-Jones authored
-
- 16 Mar, 2017 1 commit
-
-
Tiago Botelho authored
-
- 22 Feb, 2017 1 commit
-
-
wendy0402 authored
after user click delete branch, there is no processing indication, and user can click many times till. It seems flaw in UX. this will fix it fix bug in branch deletion link
-
- 09 Feb, 2017 1 commit
-
-
Phil Hughes authored
In an effort to tackle #18437 this removes 2 of the jQuery UI plugins. Highlight & autocomplete, both used once in our code. Highlight was just removed easily, autocomplete was replaced with GL dropdown
-
- 23 Jan, 2017 2 commits
-
-
Mike Greiling authored
-
Mike Greiling authored
-
- 13 Jan, 2017 1 commit
-
-
Sergey Nikitin authored
-
- 09 Jan, 2017 1 commit
-
-
Ken Ding authored
-
- 31 Dec, 2016 3 commits
-
-
Kushal Pandya authored
-
Kushal Pandya authored
-
Kushal Pandya authored
-
- 28 Dec, 2016 2 commits
-
-
Mike Greiling authored
-
Mike Greiling authored
-
- 28 Nov, 2016 1 commit
-
-
David Wagner authored
Apart from Issues and Merge Requests pages, there are other sort/filter dropdowns that needed updating. Signed-off-by: David Wagner <david@marvid.fr>
-
- 09 Nov, 2016 1 commit
-
-
Toon Claes authored
It adds a button to the branches page that the user can use to delete all the branches that are already merged. This can be used to clean up all the branches that were forgotten to delete while merging MRs. Fixes #21076.
-
- 04 Nov, 2016 1 commit
-
-
Dimitrie Hoekstra authored
-
- 28 Oct, 2016 1 commit
-
-
Alejandro Rodríguez authored
When we updated gitlab_git to 10.4.1, `tag.target` changed from pointing to the sha of the tag to the sha of the commit the tag points to. The problem is that only annotated tags have `object_sha`s, lightweight tags don't (it's nil), so (only) in their case we still need to use `tag.target`.
-
- 26 Oct, 2016 1 commit
-
-
Phil Hughes authored
Closes #23253
-
- 12 Oct, 2016 1 commit
-
-
Clement Ho authored
-
- 05 Oct, 2016 1 commit
-
-
Clement Ho authored
-
- 02 Sep, 2016 1 commit
-
-
Phil Hughes authored
If user does not have the correct permissions, the merge request button is hidden Closes #21805
-
- 24 Aug, 2016 1 commit
-
- 17 Aug, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Clement Ho authored
-
- 16 Aug, 2016 2 commits
-
-
Annabel Dunstone authored
- 15 Aug, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 11 Aug, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 28 Jul, 2016 2 commits
-
-
Alejandro Rodríguez authored
-
Herminio Torres authored
Before when you choose the way of `sort` instead it display the title correctly it was just apply the humanize helper in sort value. E.g. When you choose `Last updated` it should display the title `Last updated` instead of `Recently updated`. This fix makes this correctly displays the title. Change the implementation of the `link_to` `filter_branches_path` - Change the value of the `params[:sort]` in `link_to`. E.g. instead of using `'recently_updated'` is now using `sort_value_recently_updated`. - Change the values of the case in the `branches_sorted_by` method for the values it receives in the `params[:sort]` that are: `nil`, `'name'`, `'updated_desc'`, `'updated_asc'`.
-
- 26 Jul, 2016 1 commit
-
-
winniehell authored
-