- 23 Oct, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 17 Sep, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 03 Sep, 2019 1 commit
-
-
Igor authored
It performs an expensive operation, but isn't required in most of tests
-
- 19 Aug, 2019 1 commit
-
-
Nick Thomas authored
This functionality is available in the /autocomplete users pseudo-API. We're attempting to replace that with the canonical API, so it needs support for this parameter too.
-
- 07 Aug, 2019 3 commits
-
-
Camil Staps authored
-
Camil Staps authored
-
Camil Staps authored
-
- 25 Jul, 2019 1 commit
-
-
Heinrich Lee Yu authored
These are not required because MySQL is not supported anymore
-
- 17 Jul, 2019 1 commit
-
-
- 03 Jul, 2019 4 commits
-
-
Mathieu Parent authored
The auto_devops object sometimes doesn't exists. We may need to create it.
-
Mathieu Parent authored
We map the boolean to the string 'fetch' or 'clone', to be more explicit.
-
Mathieu Parent authored
- issues_access_level - repository_access_level - merge_requests_access_level - builds_access_level - wiki_access_level - snippets_access_level
-
Stan Hu authored
Previously the Housekeeping button and API would use the counter of last pushes to determine whether to do a full garbage collection, or whether to do one of the less comprehensive tasks: a full repack, incremental pack, or ref pack. This was confusing behavior, since a project owner might have to click the button dozens of times before a full GC would be initiated. This commit forces a full GC each time this is initiated. Note that the `ExclusiveLease` in `HousekeepingService` prevents users from clicking on the button more than once a day. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63349
-
- 12 Jun, 2019 1 commit
-
-
Fabio Pitino authored
Enable Get and Update of ci_default_git_depth for Project API. Renaming Project#default_git_depth to :ci_default_git_depth to give more context through the API usage. Add API documentation
-
- 30 May, 2019 1 commit
-
-
Imre Farkas authored
-
- 07 May, 2019 1 commit
-
-
Francisco Javier López authored
Removed the conditions added to Project.with_feature_available_for_user, and moved to the IssuableFinder. Now, we ensure that, in the projects retrieved in the Finder, the user has enough access for the feature.
-
- 19 Apr, 2019 1 commit
-
-
Mayra Cabrera authored
- Namespace now return avatar_url and web_url - NamespaceBasic entity was modified to include avatar_url and web_url, information is fetched differently depending if the Namespace is a user or a group Includes documentation changes Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/39858
-
- 09 Apr, 2019 1 commit
-
-
Imre Farkas authored
Move Contribution Analytics related spec in spec/features/groups/group_page_with_external_authorization_service_spec to EE
-
- 05 Apr, 2019 2 commits
-
-
Andreas Brandl authored
This reverts merge request !26823
-
Imre Farkas authored
Move Contribution Analytics related spec in spec/features/groups/group_page_with_external_authorization_service_spec to EE
-
- 23 Mar, 2019 1 commit
-
-
Peter Marko authored
-
- 20 Mar, 2019 1 commit
-
-
Igor Drozdov authored
-
- 26 Feb, 2019 1 commit
-
-
Nermin Vehabovic authored
Added: Specs for the API action
-
- 25 Feb, 2019 1 commit
-
-
Zeger-Jan van de Weg authored
The repository charts page used to detect the repository language for each request that was made to the page. Given the detection is an expensive operation and the same data is stored in the database the database is now serving the request. The same goes for an API endpoint that serves the languages. When a repository is empty or non-existent the languages will always be empty. And the language detection RPC isn't requested. Closes: https://gitlab.com/gitlab-org/gitlab-ce/issues/47390
-
- 20 Feb, 2019 1 commit
-
-
Małgorzata Ksionek authored
-
- 19 Feb, 2019 1 commit
-
-
Balasankar "Balu" C authored
-
- 17 Feb, 2019 1 commit
-
-
Luke Duncalfe authored
default_branch, statistics and config_ci_path are now only exposed if the user has permissions to the repository.
-
- 04 Feb, 2019 1 commit
-
-
Dylan MacKenzie authored
-
- 16 Jan, 2019 1 commit
-
-
Alejandro Rodríguez authored
Currently if a project is inside a nested group and a user doesn't have specific permissions for that group but does have permissions on a parent group the `GET /projects/:id` API call will return the following permissions: ```json permissions: { project_access: null, group_access: null } ``` It could also happen that the group specific permissions are of lower level than the ones the user has in parent groups. This patch makes it so that the permission returned for `group_access` is the highest from amongst the hierarchy, which is (ostensibly) the information that the API user is interested in for that field.
-
- 15 Jan, 2019 2 commits
-
-
Mathieu Parent authored
-
Robert Schilling authored
-
- 18 Dec, 2018 1 commit
-
-
blackst0ne authored
Updates specs to use new rails5 format. The old format: `get :show, { some: params }, { some: headers }` The new format: `get :show, params: { some: params }, headers: { some: headers }`
-
- 06 Dec, 2018 1 commit
-
-
James Lopez authored
Resolve "Can add an existing group member into a group project with new permissions but permissions are not overridden"
-
- 26 Oct, 2018 1 commit
-
-
J.D. Bean authored
-
- 19 Oct, 2018 1 commit
-
-
Bob Van Landuyt authored
This removes the `ForkedProjectLink` model that has been replaced by the `ForkNetworkMember` and `ForkNetwork` combination. All existing relations have been adjusted to use these new models. The `forked_project_link` table has been dropped. The "Forks" count on the admin dashboard has been updated to count all `ForkNetworkMember` rows and deduct the number of `ForkNetwork` rows. This is because now the "root-project" of a fork network also has a `ForkNetworkMember` row. This count could become inaccurate when the root of a fork network is deleted.
-
- 12 Sep, 2018 2 commits
-
-
🙈 jacopo beschi 🙉 authored
-
Steve authored
-
- 21 Aug, 2018 1 commit
-
-
Robert Schilling authored
-