- 26 May, 2015 4 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
Except for Note, which still overrides it.
-
Robert Speicher authored
Now there is a single source of information for which attribute a model uses to be referenced, and its special character.
-
- 15 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 06 Feb, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 06 Oct, 2014 1 commit
-
-
Vinnie Okada authored
Make the Markdown parser recognize "[x]" or "[ ]" at the beginning of a list item and turn it into a checkbox input. Users who can modify the issue or MR can toggle the checkboxes directly or edit the Markdown to manage the tasks. Task status is also displayed in the MR and issue lists.
-
- 02 Oct, 2014 1 commit
-
-
Kirill Zaitsev authored
-
- 22 Sep, 2014 1 commit
-
-
Ciro Santilli authored
-
- 25 Aug, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 29 Jul, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 25 Jul, 2014 1 commit
-
-
Jeroen van Baarsen authored
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 26 Jun, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 23 May, 2014 1 commit
-
-
Earle Bunao & Neil Calabroso authored
-
- 09 Apr, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 25 Mar, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 28 Feb, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 17 Dec, 2013 1 commit
-
-
Alexey Elizarov authored
Was it correct?
-
- 13 Dec, 2013 1 commit
-
-
Drew Blessing authored
-
- 02 Oct, 2013 1 commit
-
-
Drew Blessing authored
Labels are saved in the database with the case they were originally created with. Before this change if a user created a label with the same text but different case the label would use the original case and no new label would be created in the database. With this change, labels are now case-sensitive. Steps to test: 1. Before this change, create a new issue with a new label "FIxMe" 2. Edit the issue and change the label to "FixMe" 3. Note that the label reverted to "FIxMe" 4. Apply this change 5. Edit the issue again and change the label to "FixMe" Note that the new case was preserved. If you also look in the database in the "tags" table you will see that both labels are present - "FIxMe" and "FixMe".
-
- 09 Sep, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 25 Aug, 2013 1 commit
-
-
ash wilson authored
Any mention of Issues, MergeRequests, or Commits via GitLab-flavored markdown references in descriptions, titles, or attached Notes creates a back-reference Note that links to the original referencer. Furthermore, pushing commits with commit messages that match a (configurable) regexp to a project's default branch will close any issues mentioned by GFM in the matched closing phrase. If accepting a merge request would close any Issues in this way, a banner is appended to the merge request's main panel to indicate this.
-
- 21 Aug, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 10 Aug, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 08 Aug, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Jul, 2013 1 commit
-
-
Izaak Alpert authored
The good: - You can do a merge request for a forked commit and it will merge properly (i.e. it does work). - Push events take into account merge requests on forked projects - Tests around merge_actions now present, spinach, and other rspec tests - Satellites now clean themselves up rather then recreate The questionable: - Events only know about target projects - Project's merge requests only hold on to MR's where they are the target - All operations performed in the satellite The bad: - Duplication between project's repositories and satellites (e.g. commits_between) (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos) Fixes: Make test repos/satellites only create when needed -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap) -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually -fixed remote removal -How to merge renders properly -Update emails to show project/branches -Edit MR doesn't set target branch -Fix some failures on editing/creating merge requests, added a test -Added back a test around merge request observer -Clean up project_transfer_spec, Remove duplicate enable/disable observers -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well -Signifant speed ups for tests -Update formatting ordering in notes_on_merge_requests -Remove wiki schema update Fixes for search/search results -Search results was using by_project for a list of projects, updated this to use in_projects -updated search results to reference the correct (target) project -udpated search results to print both sides of the merge request Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
-
- 19 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 17 Jun, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 14 Jun, 2013 1 commit
-
-
Sytse Sijbrandij authored
-
- 10 Jun, 2013 1 commit
-
-
Sytse Sijbrandij authored
-
- 09 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 03 Apr, 2013 1 commit
-
-
Andrey Kumanyaev authored
-
- 15 Mar, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 28 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 19 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Feb, 2013 2 commits
-
-
Andrew8xx8 authored
-
Andrew8xx8 authored
-
- 22 Jan, 2013 1 commit
-
-
Valeriy Sizov authored
according to #2677
-