- 02 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 28 Feb, 2015 1 commit
-
-
Sytse Sijbrandij authored
Mention audit events ee feature in logs documentation. Related to gitlab/gitlabhq#1979 See merge request !1609
-
- 27 Feb, 2015 14 commits
-
-
Dmitriy Zaporozhets authored
Add 'confirm' option to users api For #1990 Based on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/129 See merge request !1610
-
Dmitriy Zaporozhets authored
Conflicts: lib/api/users.rb
-
Marin Jankovski authored
-
Job van der Voort authored
Remove CI sections related to release tool, update steps in monthly and patch release documentation. See merge request !1608
-
Marin Jankovski authored
Remove CI sections related to release tool, update steps in monthly and patch release documentation.
-
Dmitriy Zaporozhets authored
Update project_milestone_path update route. See merge request !1605
-
Dmitriy Zaporozhets authored
Redirect old note attachment path to new uploads path. See https://gitlab.com/gitlab-org/gitlab-ce/commit/0d884ff2b1beae085050fe6729bd88783891fc71#note_891797 See merge request !1607
-
Dmitriy Zaporozhets authored
Fix and test user contributed projects. Fixes #2077. See merge request !1606
-
Douwe Maan authored
-
Douwe Maan authored
-
Dmitriy Zaporozhets authored
Include number of affected people in all/group mention autocomplete item. As mentioned in #2054. To minimize misuse of all/group mentions, the autocomplete title includes the number of members this mention will notify, so users will be more considerate what groups they mention. Example: at-all "**all** All Project and Group Members (12)" at-gitlab "**gitlab** GitLab (12)" See merge request !1596
-
Dmitriy Zaporozhets authored
Introduce shortcuts for routing helpers See merge request !1600
-
Dmitriy Zaporozhets authored
-
Marin Jankovski authored
-
- 26 Feb, 2015 24 commits
-
-
Marin Jankovski authored
Filter icons look like proper buttons The filter icons (Push events, Merge events, Comments, Team) now have a border that signifies they can be pushed. This not only keeps it in line with the rest of the application buttons, but it makes it more obvious, especially for the Merge events button with a checkbox icon. Fixes #1993 See merge request !1576
-
Marin Jankovski authored
Fixes grammatical consistency and small changes This commit adds consistency to small things like periods, commas, and gives additional information to buttons and headers, etc. Fixes #2002, #2005, #2003. See merge request !1570
-
Marin Jankovski authored
Added information to tooltips Tooltips now have meaning by mentioning their function ("Filter by..."). Fixes #1992 See merge request !1571
-
Dmitriy Zaporozhets authored
Fix import status page project links for new Rails. Fixes #2059. See merge request !1593
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Add z index for diff header so sticky header stays on top on diff comments. See merge request !1603
-
Dmitriy Zaporozhets authored
Allow mass-unassigning of issues
-
Marin Jankovski authored
-
Dmitriy Zaporozhets authored
Fix GitLab && Gitorious importers. Hide already imported projects Fixes #2060 See merge request !1594
-
Douwe Maan authored
-
Dmitriy Zaporozhets authored
Small fixes Fixes #2062 and #2061 See merge request !1601
-
Dmitriy Zaporozhets authored
-
Robert Speicher authored
Fixes #867 [ci skip]
-
Robert Speicher authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Make test element selection more specific to fix constantly failing test. Fixes #2051. The problem was that there were two `.note-text` elements matching `.files [id^=diff]:nth-child(2) .note-text`, one for the new comment, and one for the (currently hidden) new comment form. The latter one was selected but currently invisible, triggering the following error in poltergeist: > The element you are trying to interact with is either not part of the DOM, or is not currently visible on the page (perhaps display: none is set). It's possible the element has been replaced by another element and you meant to interact with the new element. If so you need to do a new 'find' in order to get a reference to the new element. This caused the test to fail. See merge request !1592
-
Dmitriy Zaporozhets authored
Prevent another migration from failing due to indirect use of model columns not yet created See https://github.com/gitlabhq/gitlabhq/issues/8817#issuecomment-76007077 cc @marin See merge request !1597
-