20 Feb, 2013
6 commits
-
The notes API documentation updated with return codes. API now returns `400 Bad Request` if required attributes are not present. Return codes are documented now, also tested in added tests. The documentation now reflects the current state of the API.
-
Conflicts: spec/requests/api/projects_spec.rb
-
Conflicts: spec/requests/api/projects_spec.rb
-
The users API updated with return codes, e.g. if required parameters are missing a `400 Bad Request` error is returned instead of `404`. Fixes return codes of functions, e.g. deletion of a ssh key is an idempotent function now. The API documentation is updated to reflect the current status of the API. Descriptions are more detailed and complete, infos to return values are added to all functions.
19 Feb, 2013
1 commit
18 Feb, 2013
1 commit
-
Information to return codes added to projects and users documentation.
15 Feb, 2013
2 commits
-
Documentation is updated with information how to handle snippets or how to access tags and commits. Nearly all project specific functions are now described in the documentation. A few previous entries have been updated with status codes, e.g. `401 Unauthorized`.
14 Feb, 2013
1 commit
-
The API documentation for projects now is structured into major sections that describe the different aspects when dealing with projects, e.g. hooks, branches, team members etc. All described methods now contain a list of possible status codes the method can return. A few methods have extra sample JSON responses and a description if a method is idempotent. Idempotent methods can be called multiple times while returning the same status code.
13 Feb, 2013
1 commit
09 Feb, 2013
1 commit
-
Instead of using funtion `error!` the function `not_found!` is used to return 404 error. Adjusted documentation accordingly.
08 Feb, 2013
1 commit
06 Feb, 2013
1 commit
-
A few fixes in the notes URI pattern (`notes` instead of `:notes`), also updated the information to status codes. If `body` attribute is missing from a POST request a status code 400 (Bad request) is returned. This reflects the code changes from the previous commit.
01 Feb, 2013
2 commits
-
correctly describes the new behavior
31 Jan, 2013
5 commits
-
Added methods to protect and unprotect branches in from the API
-
… bladealslayer-extend_user_api Conflicts: spec/requests/api/users_spec.rb
28 Jan, 2013
1 commit
-
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.
22 Dec, 2012
1 commit
21 Dec, 2012
3 commits
20 Dec, 2012
1 commit
18 Dec, 2012
1 commit
-
Also added tests.
15 Dec, 2012
1 commit
-
Removed delete section in issues API documentation
14 Dec, 2012
1 commit
12 Dec, 2012
2 commits
-
The 2 reasons are : - creation of user fail if name is empty : in after_save, it tries to create a namespace with namespace.name = user.name and namespece validates presence Namespace#name - in the web app links to team members are broken with empty User#name because they are of the form <a href'...'> user.name </a>
01 Dec, 2012
2 commits
29 Nov, 2012
3 commits
07 Nov, 2012
1 commit
-
API fixes
25 Oct, 2012
1 commit