Software Publico / Gitlab

02 Apr, 2014

1 commit

09d24a1f Better title suggestion for new MR ... Browse File »

Ex. if branch named "refactor-models" then title will be "Refactor models"

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

2014-04-02 14:16:37 +0300

24 Mar, 2014

1 commit

394737b2 Use humanize instead of titleize for MR title suggestion ... Browse File »
```
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
```
Dmitriy Zaporozhets
2014-03-24 16:15:57 +0200

27 Feb, 2014

1 commit

6dcfc104 Issue box restyle ... Browse File »
```
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
```
Dmitriy Zaporozhets
2014-02-27 21:04:44 +0200

24 Feb, 2014

1 commit

9439cb55 By default, target original repository if fork when creating new MR. Browse File »

Jacob Carlborg
2014-02-24 22:06:25 +0100

18 Feb, 2014

1 commit

88b8b15d Improve UI for Issue/MR ... Browse File »
```
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
```
Dmitriy Zaporozhets
2014-02-18 22:05:44 +0200

12 Dec, 2013

1 commit

432018f8 Use MR#source_project_path method instead of merge_request.source_project.path_with_namespace ... Browse File »
```
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
```
Dmitriy Zaporozhets
2013-12-12 11:52:10 +0200

17 Jul, 2013

3 commits

539c70c7 Update emails to describe path using for_fork? ... Browse File »

Forked MR's will print

Project:Branch <source_project_with_path>:<source_branch> -> <target_project_with_path>:<target_branch>

Non forked MR's will print

Branch <source_branch> -> <target_branch>

Change-Id: I89399aec2e7fde8e4b64b110a48099a95ae4f038

2013-07-17 22:48:03 -0400

d9959427 Style changes from review with @randx ... Browse File »

-Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow

Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150

2013-07-17 22:48:03 -0400

3d7194f0 Merge Request on forked projects ... Browse File »

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