1. 15 2月, 2015 1 次提交
    • V
      Upgrade to Rails 4.1.9 · 76aad9b7
      Vinnie Okada 提交于
      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.
      76aad9b7
  2. 03 2月, 2015 2 次提交
  3. 03 10月, 2014 1 次提交
  4. 16 8月, 2014 1 次提交
    • C
      Remove unused title parameter. · 7be7cf29
      Ciro Santilli 提交于
      It is always overridden by to humanized source branch name by
      MergeRequests::BuilService, which is used by new_project_merge_request_path.
      7be7cf29
  5. 14 6月, 2014 1 次提交
  6. 28 5月, 2014 1 次提交
  7. 02 4月, 2014 1 次提交
  8. 24 3月, 2014 1 次提交
  9. 28 2月, 2014 1 次提交
  10. 25 2月, 2014 1 次提交
  11. 19 2月, 2014 1 次提交
  12. 12 12月, 2013 1 次提交
  13. 18 7月, 2013 3 次提交
    • I
      Update emails to describe path using for_fork? · 539c70c7
      Izaak Alpert 提交于
      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
      539c70c7
    • I
      Style changes from review with @randx · d9959427
      Izaak Alpert 提交于
      -Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow
      
      Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
      d9959427
    • I
      Merge Request on forked projects · 3d7194f0
      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
      3d7194f0
  14. 06 4月, 2013 1 次提交
  15. 18 2月, 2013 1 次提交
  16. 04 1月, 2013 1 次提交
  17. 13 12月, 2012 1 次提交
  18. 11 12月, 2012 1 次提交
  19. 21 11月, 2012 1 次提交
  20. 09 10月, 2012 1 次提交
  21. 11 8月, 2012 1 次提交
  22. 27 6月, 2012 1 次提交
  23. 21 6月, 2012 1 次提交
  24. 12 6月, 2012 1 次提交
  25. 05 2月, 2012 1 次提交
  26. 28 11月, 2011 1 次提交