400 Bad Request - A required attribute of the API request is missing, e.g. the title of an issue is not given 401 Unauthorized - The user is not authenticated, a valid user token is necessary, see above For example, an API call to retrieve a ticket with an invalid ID will return a HTTP 404 status code to let you know that no such ticket exists. 405: Method not allowed: This API request used the wrong HTTP verb/method. For example an API PUT request on /api/v2/tickets endpoint will return a HTTP 405 as /api/v2/tickets allows only GET and POST ... Merge requests API Every API call to merge requests must be authenticated. List merge requests Introduced in GitLab 9.5.. Get all merge requests the authenticated user has access to.
Configure GitLab. Create a test application. To configure GitLab and enable Continuous Integration (CI), create a new project and enter the necessary GitLab CI authorization parameters. In the URL API field, enter the master node address. Retrieve it using the commanddiff --git a/lib/api/triggers.rb b/lib/api/triggers.rb index d1d07394e92847bae0e4c7ee8efd4f4914e8ee4a..9a4f1cd342f2208749fd50bd6f613b6c8c00a7f8 100644 --- a/lib/api ...