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
..
admin	Add optional signup.	2013-01-18 11:57:31 +01:00
api	Creating or updating a MR returns more informative status codes.	2013-02-06 16:57:00 +01:00
atom	Fixed dashboard show specs	2013-01-27 13:20:23 +02:00
security	Fix security spec	2013-01-05 00:49:43 +02:00
gitlab_flavored_markdown_spec.rb	should be green build now :)	2013-01-15 19:18:52 +02:00
issues_spec.rb	Continue refactoring. Use repostory and team	2013-01-04 08:43:25 +02:00
notes_on_merge_requests_spec.rb	Fix spec/requests/notes_on_merge_requests_spec.r	2013-01-15 18:20:58 +02:00
notes_on_wall_spec.rb	fix notes_on_wall specs	2013-01-15 15:04:22 +02:00
projects_deploy_keys_spec.rb	Rspec fixes	2013-01-04 18:50:31 +02:00
projects_spec.rb	A bit of spinach tests	2013-01-09 08:14:05 +03:00
search_spec.rb	Rspec fixes	2013-01-04 18:50:31 +02:00
snippets_spec.rb	Rspec fixes	2013-01-04 18:50:31 +02:00