- 21 Oct, 2017 1 commit
-
-
Guilherme Vieira authored
-
- 19 Oct, 2017 1 commit
-
-
Guilherme Vieira authored
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 25 Jan, 2017 1 commit
-
-
Robert Speicher authored
-
- 11 Oct, 2016 1 commit
-
-
Sean McGivern authored
We need to do two things to support this: 1. Simplify the regex capture in the routing for the CommitsController to not exclude the '.atom' suffix. That's a perfectly valid git branch name, so we shouldn't blow up if we get it. 2. Because Rails now can't automatically detect the request format, add some code to do so in `ExtractPath` when there is no path. This means that, given branches 'foo' and 'foo.atom', the Atom feed for the former is unroutable. To fix this: don't do that! Give the branches different names!
-
- 09 Aug, 2016 1 commit
-
-
tiagonbotelho authored
-
- 19 Feb, 2016 1 commit
-
-
Robert Speicher authored
-
- 23 Jun, 2015 1 commit
-
-
Stan Hu authored
-
- 14 Feb, 2015 1 commit
-
-
Vinnie Okada authored
Make the following changes to deal with new behavior in Rails 4.1.2: * Use nested resources to avoid slashes in arguments to path helpers.
-
- 12 Feb, 2015 1 commit
-
-
Jeroen van Baarsen authored
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 26 May, 2014 1 commit
-
-
Marin Jankovski authored
-
- 23 May, 2014 1 commit
-
-
Earle Bunao & Neil Calabroso authored
-
- 22 Jan, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
* project_with_code -> project * project -> ermpty_project Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 12 Sep, 2013 1 commit
-
-
Hiroyuki Sato 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
-
- 23 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 01 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 06 Mar, 2013 1 commit
-
-
Sato Hiroyuki authored
It is linked to #2598.
-
- 04 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 23 Nov, 2012 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 26 Sep, 2012 1 commit
-
-
Robert Speicher authored
-