| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Make ruby lint happysh-backport-10-3-4-security-fixes | Oswaldo Ferreira | 2018-01-17 | 1 | -0/+1 |
| | | |||||
| * | Merge branch 'sh-migrate-can-push-to-deploy-keys-projects-10-3' into ↵ | Douwe Maan | 2018-01-16 | 1 | -19/+45 |
| | | | | | | | | | | | | | 'security-10-3' [10.3] Migrate `can_push` column from `keys` to `deploy_keys_project` See merge request gitlab/gitlabhq!2276 (cherry picked from commit f6ca52d31bac350a23938e0aebf717c767b4710c) 1f2bd3c0 Backport to 10.3 | ||||
| * | API: Use defined project requirementsrs-api-use-project-requirements | Robert Schilling | 2017-08-31 | 1 | -1/+1 |
| | | |||||
| * | Conditionally destroy a ressource | Robert Schilling | 2017-08-28 | 1 | -4/+1 |
| | | |||||
| * | API: Respect the 'If-Unmodified-Since' for delete endpoints | Robert Schilling | 2017-08-28 | 1 | -0/+2 |
| | | |||||
| * | Update grape gemdz-update-grape | Dmitriy Zaporozhets | 2017-07-20 | 1 | -0/+1 |
| | | | | | | | | | New version of the gem returns 200 status code on delete with content instead of 204 so we explicitly set status code to keep existing behavior Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | ||||
| * | Fix edit button for deploy keys available from other projects | Alexander Randa | 2017-06-20 | 1 | -1/+1 |
| | | |||||
| * | Implement ability to update deploy keys | Alexander Randa | 2017-06-02 | 1 | -0/+21 |
| | | |||||
| * | Enable creation of deploy keys with write access via the API | Mark Fletcher | 2017-04-05 | 1 | -0/+1 |
| | | | | | * Documentation was incorrectly advertising the missing param | ||||
| * | Add `requirements: { id: %r{[^/]+} }` for all projects and groups namespaced ↵ | Rémy Coutable | 2017-03-16 | 1 | -1/+1 |
| | | | | | | | API routes Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | API: Remove `DELETE projects/:id/deploy_keys/:key_id/disable`api-remove-deploy-key-disable | Robert Schilling | 2017-02-20 | 1 | -19/+3 |
| | | |||||
| * | Paginate all endpoints that return an array | Robert Schilling | 2017-02-16 | 1 | -3/+11 |
| | | |||||
| * | Remove /projects/:id/keys/.. endpoints | Robert Schilling | 2017-02-07 | 1 | -89/+83 |
| | | |||||
| * | Merge branch 'grapify-deploy-keys' into 'master' | Rémy Coutable | 2017-01-24 | 1 | -9/+8 |
| |\ | | | | | | | | | Grapify all endpoints of the deploy keys API See merge request !8721 | ||||
| | * | Grapify all endpoints of the deploy keys APIgrapify-deploy-keys | Robert Schilling | 2017-01-23 | 1 | -9/+8 |
| | | | |||||
| * | | Merge branch 'fix-users-deleting-public-deployment-keys' into 'security' | Robert Speicher | 2017-01-23 | 1 | -3/+7 |
| |/ | | | | | Fix users being able to delete instance public deployment keys See merge request !2049 | ||||
| * | Use declared_params helper in APIgrapify-declared-params | Robert Schilling | 2016-11-14 | 1 | -1/+1 |
| | | |||||
| * | Fixes various errors when adding deploy keys caused by not exiting the ↵ | Joshua Welsh | 2016-10-26 | 1 | -2/+7 |
| | | | | | | | | | | | | | | control flow. When adding a deploy key that already exists in the project the existing key would not be returned, resulting in an attempt to create a new one, which in turn caused a 500 error due to an ActiveRecord exception. When adding a deploy key that exists within another project the key would be joined to the project, but would also attempt to create a new one, which resulted in a 400 error due to the key already existing. Fixes #22741 Fixes #21754 Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Namespace EnableDeployKeyService under Projects | Z.J. van de Weg | 2016-08-08 | 1 | -1/+2 |
| | | |||||
| * | Create service for enabling deploy keys | Z.J. van de Weg | 2016-08-05 | 1 | -3/+3 |
| | | |||||
| * | Move deploy_key tests to deploy_key_spec.rb | Z.J. van de Weg | 2016-08-04 | 1 | -5/+6 |
| | | | | | Also, fix the failing test in the process | ||||
| * | Use Grape DSL for deploy keys endpoints | Z.J. van de Weg | 2016-08-03 | 1 | -39/+34 |
| | | | | | Also a minor clean up of the post endpoint | ||||
| * | Endpoints to enable and disable deploy keys | Z.J. van de Weg | 2016-08-03 | 1 | -0/+31 |
| | | | | | Resolves #20123 | ||||
| * | Change `return`s for `next`s to please rubocop (behaviour is the same) | Alejandro Rodríguez | 2016-07-20 | 1 | -2/+2 |
| | | |||||
| * | Add /deploy_keys API to retrieve all deploy keys regardless of project ↵ | Alejandro Rodríguez | 2016-07-20 | 1 | -53/+66 |
| | | | | | | | | affiliation Also, in favour of consistency, deprecate `/projects/:id/keys/...` routes in favour of `/projects/:id/deploy_keys/...` | ||||
| * | Improve error reporting on users API | jubianchi | 2014-09-16 | 1 | -1/+1 |
| | | | | | | | | | * users (#6878, #3526, #4209): Validation error messages are now exposed through 400 responses, 409 response are sent in case of duplicate email or username * MRs (#5335): 409 responses are sent in case of duplicate merge request (source/target branches), 422 responses are sent when submiting MR fo/from unrelated forks * issues * labels * projects | ||||
| * | Remove deprecated finders | skv | 2014-01-19 | 1 | -2/+2 |
| | | |||||
| * | API: set gitlab-ci service for project | Dmitriy Zaporozhets | 2013-10-29 | 1 | -10/+0 |
| | | |||||
| * | API: Protect project deploy keys from unauthorized access | Dmitriy Zaporozhets | 2013-09-30 | 1 | -0/+1 |
| | | |||||
| * | Split Project api on several parts: deploy_keys, hooks, snippets etc | Dmitriy Zaporozhets | 2013-06-06 | 1 | -0/+84 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |