Find a file

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
app	Advanced logging for post-receive worker	2013-01-29 11:32:05 +02:00
config	log fatal errors that we catch	2013-02-01 10:23:23 +00:00
db
doc	update api documentation for delete team member	2013-02-01 14:20:51 +00:00
features	Merge pull request #2153 from koenpunt/commit-diff-views	2013-01-27 11:41:23 -08:00
lib	Creating MR comment without a note returns status code 400 (Bad request)	2013-02-06 17:02:30 +01:00
log
public
script
spec	Creating MR comment without a note returns status code 400 (Bad request)	2013-02-06 17:02:30 +01:00
tmp
vendor
.foreman
.gitignore
.rspec
.simplecov
.travis.yml
CHANGELOG
config.ru
CONTRIBUTING.md
Gemfile
Gemfile.lock
Guardfile
LICENSE
Procfile	Do gitolite calls async. Remove satellite with project remove	2013-01-28 17:22:45 +02:00
Rakefile
README.md	set link to gitlab-ci	2013-01-29 14:49:10 +02:00
ROADMAP.md
VERSION