- 29 7月, 2013 1 次提交
-
-
由 Johannes Schleifenbaum 提交于
-
- 18 7月, 2013 1 次提交
-
-
由 Izaak Alpert 提交于
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
-
- 22 6月, 2013 3 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
- 20 6月, 2013 4 次提交
-
-
由 Dirk Hörner 提交于
Besides specifying http and https url's as the import-url when creating a new project, you can now use git://... url's to import via the git protocol.
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
- 19 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 14 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 13 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 11 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 25 5月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Ronald van Eede 提交于
-
- 22 5月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
- 09 5月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Javier Castro 提交于
-
- 08 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 06 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 16 4月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 15 4月, 2013 1 次提交
-
-
由 Angus MacArthur 提交于
-
- 11 4月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 05 4月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 03 4月, 2013 3 次提交
-
-
由 Andrey Kumanyaev 提交于
-
由 Andrey Kumanyaev 提交于
-
由 Andrey Kumanyaev 提交于
-
- 01 4月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Also specify separate project factory for project with filled repo
-
由 Dmitriy Zaporozhets 提交于
-
- 31 3月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
Use existing methods for branch names: Ex use @repository.branch_names instead of @repository.heads.map(&:name)
-
- 28 3月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 25 3月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Andrew8xx8 提交于
-
- 22 3月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 19 3月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 15 3月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 28 2月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Andrew8xx8 提交于
-