An error occurred fetching the project authors.
  1. 23 Sep, 2013 1 commit
  2. 18 Jul, 2013 2 commits
    • Izaak Alpert's avatar
      Style changes from review with @randx · d9959427
      Izaak Alpert authored
      -Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow
      
      Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
      d9959427
    • Izaak Alpert's avatar
      Merge Request on forked projects · 3d7194f0
      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
      3d7194f0
  3. 12 Jul, 2013 1 commit
  4. 08 Jul, 2013 1 commit
  5. 22 Jun, 2013 1 commit
  6. 06 Jun, 2013 1 commit
  7. 23 May, 2013 1 commit
  8. 14 May, 2013 1 commit
  9. 07 May, 2013 1 commit
  10. 06 May, 2013 2 commits
  11. 02 May, 2013 1 commit
  12. 01 May, 2013 1 commit
  13. 10 Apr, 2013 1 commit
  14. 01 Apr, 2013 1 commit
  15. 25 Mar, 2013 1 commit
  16. 05 Mar, 2013 2 commits
  17. 27 Feb, 2013 3 commits
  18. 21 Feb, 2013 2 commits
  19. 20 Feb, 2013 2 commits
  20. 16 Feb, 2013 1 commit
    • Sebastian Ziebell's avatar
      API: fixes visibility of project hook · e9d3b965
      Sebastian Ziebell authored
      When a user is not authorized to see the list of hooks for a project, he is
      still able to access the hooks separately. For example if access to
      `GET /projects/:id/hooks` fails and returns a `403 Unauthorized` error it is
      still possible to access a hook directly via `GET /projects/:id/hooks/:hook_id`.
      
      Fixes access, also added tests to check access and status codes of hooks.
      e9d3b965
  21. 14 Feb, 2013 4 commits
  22. 13 Feb, 2013 4 commits
  23. 12 Feb, 2013 1 commit
    • Sebastian Ziebell's avatar
      API: changed status codes for project hooks functions · 7cc4339f
      Sebastian Ziebell authored
      Different status codes in the API lib are returned on hook creation, update or deletion.
      If a required parameter is not given (e.g. `url` in `/projects/:id/hooks/:hook_id`) status
      code 400 (Bad request) is returned. On hook deletion a 200 status code is returned, regardless if
      the hook is present or not. This makes the DELETE function an idempotent operation. Appropriate tests
      are added to check these status codes.
      7cc4339f
  24. 08 Feb, 2013 4 commits