Files
gitlabhq/spec/requests/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
..
2013-01-04 18:50:31 +02:00
2013-01-04 18:50:31 +02:00
2013-01-04 18:50:31 +02:00
2013-01-18 11:57:31 +01:00