Skip to content
Snippets Groups Projects
  1. Oct 09, 2013
  2. Aug 28, 2013
    • Alex Van't Hof's avatar
      Standardize commit diff api url, change blob api url, add get single commit · 59f428dc
      Alex Van't Hof authored
      Use "/commits/:sha/diff" as opposed to "/commit/:sha", keeping in line
      with existing api urls (e.g. "/projects/:id", etc.)
      
      Fix 500 error resulting from a diff api call with an invalid commit hash
      
      Move "/commits/:sha/blob" to "/blobs/:sha", leaving the old path for
      backwards compatibility.
      
      Add ability to get a single commit via "/commits/:sha"
      59f428dc
  3. Aug 27, 2013
  4. Aug 25, 2013
  5. Aug 14, 2013
  6. Jul 30, 2013
  7. Jul 18, 2013
    • Izaak Alpert's avatar
      Refactor merge api create · fae3f466
      Izaak Alpert authored
      -Made the api method a little more readable
      -removed some missed extra newline's
      
      Change-Id: Ic38baafc813aaeda0a8b283f39916182c8ec37d5
      fae3f466
    • Izaak Alpert's avatar
      MR on Fork multiple fixes · 489fa5d7
      Izaak Alpert authored
      -Disable observers post test run
      -Allow db:seed_fu RAILS_ENV=test to be run more than once without error
      -fix diffs_in_between, was passing in the default_options for grit, but grit in this case doesn't take options, fixed the test to actually fail if the incorrect diffs are returned
      -make notes/commits render against proper project
      -MR discussion file links should reference note's project
      -Added tests for commit links on edit merge request
      -fixes edit issues (canceling an edited mr, updating an edited mr)
      -updates tests with checks for source code updates
      -still forked_merge_requests.feature (project_forked_merge_requests) test not passing (commented out -- "stable" not being set)
      
      MR API: error on bad target_project
      
      -If the target project id is specified and it is not the same as the project the request is being made on (the source), and the it isn't a fork of that project, error out, otherwise use it as the target
      -Fixes some busted (but hidden) test cases
      
      Conflicts:
      	app/views/merge_requests/show/_diffs.html.haml
      	spec/features/notes_on_merge_requests_spec.rb
      
      Change-Id: I20e595c156d0e8a63048baaead7be6330c738a05
      489fa5d7
    • 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
  8. Jul 16, 2013
  9. Jul 12, 2013
  10. Jul 08, 2013
  11. Jun 18, 2013
  12. Jun 12, 2013
  13. Jun 11, 2013
  14. Jun 06, 2013
  15. Jun 04, 2013
  16. Jun 03, 2013
  17. May 29, 2013
    • Drew Blessing's avatar
      Update api docs and remove old attribute from User entity. · 07fd95f3
      Drew Blessing authored
      The API docs incorrectly referenced a few attributes associated with users. The 'blocked' attribute has been replaced with 'state'. Also, 'dark_scheme' seems to no longer be available in the User model so it should be removed from the exposed attributes in the API User entity.
      
      Add color scheme ID to API User entity
      07fd95f3
  18. May 27, 2013
  19. May 23, 2013
Loading