gitlabhq/lib/api
Sebastian Ziebell 413952ff94 Creating or updating a MR returns more informative status codes.
Using the API library to create or update a merge request at the moment a 404 error is returned.
This is fine when the merge request in question does not exist, but does not provide good
information that for example a required attribute is missing.
A status code of 400 (Bad request) is returned when creating or updating a merge request
when either `source_branch` or `target_branch` is missing. A status code of 409 is returned
when `source_branch` and `target_branch` are the same. Tests are added for these cases.
2013-02-06 16:57:00 +01:00
..
entities.rb 'namespace' should be exposed via the API 2013-01-02 21:31:20 +01:00
helpers.rb Fix namespace api autocomplete 2012-12-12 12:54:28 +02:00
issues.rb Fixed missing current user for issue observer 2013-01-02 20:25:25 +02:00
merge_requests.rb Creating or updating a MR returns more informative status codes. 2013-02-06 16:57:00 +01:00
milestones.rb Remove all references tp the project code parameter from the API 2012-12-21 18:47:04 +01:00
notes.rb Rspec fixes 2013-01-04 18:50:31 +02:00
projects.rb Don't crash when removing a user that's not project member 2013-02-01 13:53:35 +00:00
session.rb API: return 401 for invalid session 2012-09-20 08:38:08 -07:00
users.rb Validates presence of User#name 2012-12-12 17:53:43 +01:00