- 04 Nov, 2016 1 commit
-
-
Nick Thomas authored
-
- 02 Nov, 2016 2 commits
-
-
Z.J. van de Weg authored
[ci skip]
-
Zeger-Jan van de Weg authored
-
- 01 Nov, 2016 5 commits
-
-
Felipe Artur authored
-
Valery Sizov authored
-
Sean McGivern authored
-
Gauvain Pocentek authored
The UI allows to define a token to validate payload on the target URL, this patch adds the feature to the API.
-
Kamil Trzcinski authored
Due to different way of handling owners of a project, they were not allowed to fetch CI sources for project.
-
- 31 Oct, 2016 3 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
- 27 Oct, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 26 Oct, 2016 2 commits
-
-
Joshua Welsh authored
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>
-
Kamil Trzcinski authored
-
- 24 Oct, 2016 7 commits
-
-
Airat Shigapov authored
Make events order spec deterministic, create only 3 record instead of 5, explicitely check for events order
-
Airat Shigapov authored
-
Airat Shigapov authored
-
Robert Schilling authored
-
Luis HGO authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
barthc authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Timothy Andrew authored
1. Previously, we were not removing existing access levels before creating new ones. This is not a problem for EE, but _is_ for CE, since we restrict the number of access levels in CE to 1. 2. The correct approach is: CE -> delete all access levels before updating a protected branch EE -> delete developer access levels if "developers_can_{merge,push}" is switched off 3. The dispatch is performed by checking if a "length: 1" validation is present on the access levels or not. 4. Another source of problems was that we didn't put multiple queries in a transaction. If the `destroy_all` passes, but the `update` fails, we should have a rollback. 5. Modifying the API to provide users direct access to CRUD access levels will make things a lot simpler. 6. Create `create/update` services separately for this API, which perform the necessary data translation, before calling the regular `create/update` services. The translation code was getting too large for the API endpoint itself, so this move makes sense.
-
- 21 Oct, 2016 2 commits
-
-
Airat Shigapov authored
-
Valery Sizov authored
-
- 20 Oct, 2016 1 commit
-
-
Douwe Maan authored
-
- 19 Oct, 2016 3 commits
-
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Robert Schilling authored
-
- 17 Oct, 2016 1 commit
-
-
Nick Thomas authored
The amount of precision times have in databases is variable, so we need tolerances when comparing in specs. It's better to have the tolerance defined in one place than several.
-
- 14 Oct, 2016 2 commits
-
-
Dmitriy Zaporozhets authored
This reverts commit 68ab7047.
-
Robert Schilling authored
-
- 12 Oct, 2016 2 commits
-
-
Robert Schilling authored
-
Thomas Balthazar authored
The /licenses, /gitignores and /gitlab_ci_ymls endpoints are now also available under a new /templates namespace. Old endpoints will be deprecated when GitLab 9.0.0 is released.
-
- 11 Oct, 2016 4 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
API: Share projects only with groups current_user can access Aims to address the issues here: https://gitlab.com/gitlab-org/gitlab-ce/issues/23004 * Projects can be shared with non-existent groups * Projects can be shared with groups that the current user does not have access to read Concerns: The new implementation of the API endpoint allows projects to be shared with a larger range of groups than can be done via the web UI. The form for sharing a project with a group uses the following API endpoint to index the available groups: https://gitlab.com/gitlab-org/gitlab-ce/blob/494269fc92f61098ee6bd635a0426129ce2c5456/lib/api/groups.rb#L17. The groups indexed in the web form will only be those groups that the user is currently a member of. The new implementation allows projects to be shared with any group that the authenticated user has access to view. This widens the range of groups to those that are public and internal. See merge request !2005 Signed-off-by: Rémy Coutable <remy@rymai.me>
-
tiagonbotelho authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 10 Oct, 2016 4 commits
-
-
Rémy Coutable authored
From 8.15s to 4.55s by grouping expectations Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-