22 Jan, 2014

1 commit


04 Dec, 2013

1 commit


26 Nov, 2013

1 commit


18 Nov, 2013

1 commit


06 Nov, 2013

1 commit


09 Oct, 2013

1 commit


23 Sep, 2013

1 commit


17 Jul, 2013

2 commits

  • -Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow
    
    Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
    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
    Izaak Alpert
     

12 Jul, 2013

1 commit


10 Jul, 2013

1 commit


08 Jul, 2013

1 commit


22 Jun, 2013

1 commit


06 Jun, 2013

1 commit


04 Jun, 2013

1 commit


23 May, 2013

1 commit


14 May, 2013

1 commit


07 May, 2013

2 commits


06 May, 2013

1 commit


02 May, 2013

1 commit


01 May, 2013

1 commit


10 Apr, 2013

1 commit


01 Apr, 2013

1 commit


25 Mar, 2013

1 commit


07 Mar, 2013

1 commit


06 Mar, 2013

1 commit


05 Mar, 2013

2 commits


27 Feb, 2013

3 commits


21 Feb, 2013

2 commits


20 Feb, 2013

5 commits


16 Feb, 2013

1 commit

  • 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.
    Sebastian Ziebell