- 06 Feb, 2013 3 commits
-
-
Sebastian Ziebell authored
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.
-
Sebastian Ziebell authored
-
Sebastian Ziebell authored
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.
-
- 01 Feb, 2013 3 commits
-
-
Felix Gilcher authored
correctly describes the new behavior
-
Felix Gilcher authored
The attempt to revoke project access for a user that was not member of the project results in a 500 Internal Server error where it actually should result in a 200 OK since after the operation, the user is not member of the project. This turns the operation into an idempotent call that can be repeated with no ill effects. Updated the spec and changed the code accordingly. However, the result differs slightly, as we can't return the users project access level if the user was not member. I'm not aware if anybody relies on the result of this call. Fixes #2832
-
Felix Gilcher authored
In case we rescue from a fatal error, we want the error and the backtrace to the error logged, so we can debug later on. This change injects the configured logger from the rails app to the grape API and logs error as well as backtrace in a rails-like fashion.
-
- 29 Jan, 2013 5 commits
-
-
Felix Gilcher authored
This rescues all errors and returns a proper JSON response. Fixes #2833.
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 28 Jan, 2013 14 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Fix #2790
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Lennart Rosam authored
-
Riyad Preukschas authored
remove incorrect information about the api version
-
Lennart Rosam authored
-
Lennart Rosam authored
-
Felix Gilcher authored
The API version is currently not equal to the gitlab major version number. Gitlab 4.1 still uses API version 3. Point to the lib/api.rb file instead which contains the autoritative information.
-
Dmitriy Zaporozhets authored
-
- 27 Jan, 2013 12 commits
-
-
Dmitriy Zaporozhets authored
Added swipe view for image diff
-
Koen Punt authored
Prepared diff view for multiple view modes Converted commits.js to coffeescript image info in separate coffeescript file Added swipe view mode Added onion skin viewMode
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Updates web hooks to process via queue
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Feature: Projects page
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 26 Jan, 2013 3 commits
-
-
Riyad Preukschas authored
Missing environment added to 'Try fixing it' block
-
Alex Denisov authored
-
Dmitriy Zaporozhets authored
-