Sebastian Ziebell f978a71f41 Creating MR comment without a note returns status code 400 (Bad request) ... Creating a comment to an existing merge request via API without providing a note returns a status code 400 now, suggesting a bad request. The reason for this is the resource itself (MR) exists but the required property is not set.		2013-02-06 17:02:30 +01:00
..
contexts	Improve CreateContext call. Fixed test	2013-01-18 20:21:13 +02:00
controllers	remove unused autogenerated files	2013-01-24 22:31:48 +02:00
factories	simple refactoring	2013-01-24 22:31:48 +02:00
helpers	remove unused autogenerated files	2013-01-24 22:31:48 +02:00
lib	fix tests	2013-01-28 17:53:01 +02:00
mailers	Add optional signup.	2013-01-18 11:57:31 +01:00
models	fix tests	2013-01-28 08:59:34 +02:00
observers	fix key observer tests	2013-01-28 23:03:38 +02:00
requests	Creating MR comment without a note returns status code 400 (Bad request)	2013-02-06 17:02:30 +01:00
routing	Fixed dashboard show specs	2013-01-27 13:20:23 +02:00
support	Async perform for add/remove team members	2013-01-28 17:39:02 +02:00
tasks/gitlab	Fix routing issues when navigating over tree, commits etc	2012-12-25 06:14:05 +03:00
workers	sidekiq with green tests	2013-01-09 09:14:05 +03:00
factories.rb	user factory username over sequence	2013-01-28 17:46:24 +02:00
factories_spec.rb	Factories spec refactoring after #1616	2012-10-03 13:33:31 +03:00
seed_project.tar.gz	Rspec test repo replaced.\nMerge Requests improved	2012-03-13 23:54:49 +02:00
spec_helper.rb	sidekiq with green tests	2013-01-09 09:14:05 +03:00