- 26 Aug, 2018 1 commit
-
-
Gabriel Mazetto authored
-
- 16 Aug, 2018 1 commit
-
-
Valery Sizov authored
-
- 16 Jul, 2018 1 commit
-
-
gfyoung authored
For directories application_settings --> labels. Partially addresses #47424.
-
- 08 Jan, 2018 1 commit
-
-
Yorick Peterse authored
This removes all usage of soft removals except for the "pending delete" system implemented for projects. This in turn simplifies all the query plans of the models that used soft removals. Since we don't really use soft removals for anything useful there's no point in keeping it around. This _does_ mean that hard removals of issues (which only admins can do if I'm not mistaken) can influence the "iid" values, but that code is broken to begin with. More on this (and how to fix it) can be found in https://gitlab.com/gitlab-org/gitlab-ce/issues/31114. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37447
-
- 22 Aug, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 28 Jul, 2017 1 commit
-
-
Z.J. van de Weg authored
When destroying a group, now an API call is made to the Mattermost server to request the deletion of the project. Actual team deletion on the Mattermost side happens async, so the runtime shouldn't increase by more than a second.
-
- 29 Jun, 2017 1 commit
-
-
Stan Hu authored
Group#destroy would actually hard-delete all associated projects even though the acts_as_paranoia gem is used, preventing Projects::DestroyService from doing any work. We first noticed this while trying to log all projects deletion to the Geo log.
-
- 28 Jun, 2017 1 commit
-
-
Tiago Botelho authored
-
- 27 Feb, 2017 1 commit
-
-
Stan Hu authored
-
- 16 Feb, 2017 1 commit
-
-
Stan Hu authored
There are two problems in the current implementation: 1. If a project is marked for deletion via the `pending_delete` flag and then the namespace was quickly deleted, it's possible that the namespace skips over that project and leaves that project in an orphaned state. 2. Before namespace deletion, the namespace attempts to clean up all the relevant storage paths. However, if all projects have been removed synchronously, then the namespace will not be able to clean anything. To prevent this, we should load the paths to be deleted before actually destroying projects. The specs were missing this second case due to a permission issue that caused project removal never to happen.
-
- 08 Feb, 2017 1 commit
-
-
dixpac authored
* Changed name of delete_user_service and worker to destroy * Move and change delete_group_service to Groups::DestroyService * Rename Notes::DeleteService to Notes::DestroyService
-