- 31 5月, 2018 1 次提交
-
-
由 Kamil Trzciński 提交于
-
- 05 5月, 2018 1 次提交
-
-
由 Mario de la Ossa 提交于
-
- 02 5月, 2018 1 次提交
-
-
由 Dylan Griffith 提交于
-
- 09 4月, 2018 1 次提交
-
-
由 Dylan Griffith 提交于
-
- 06 4月, 2018 1 次提交
-
-
由 Francisco Javier López 提交于
-
- 06 3月, 2018 1 次提交
-
-
由 Felipe Artur 提交于
-
- 03 3月, 2018 1 次提交
-
-
由 Felipe Artur 提交于
-
- 07 2月, 2018 3 次提交
-
-
由 Dylan Griffith 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 06 2月, 2018 1 次提交
-
-
由 Mayra Cabrera 提交于
-
- 05 2月, 2018 1 次提交
-
-
由 Nick Thomas 提交于
-
- 03 2月, 2018 1 次提交
-
-
由 Mario de la Ossa 提交于
-
- 09 1月, 2018 1 次提交
-
-
由 Yorick Peterse 提交于
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
-
- 04 1月, 2018 3 次提交
-
-
- 09 12月, 2017 1 次提交
-
-
由 Mayra Cabrera 提交于
-
- 05 12月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
On the `show` of a project that is part of a fork network. We check if the user already created a fork of this project in their personal namespace. We do this in several places, so caching the result of this query in the request store prevents us from repeating it.
-
- 27 11月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 25 11月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 06 11月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 10 10月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 07 10月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 15 9月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
Prior to this commit running Namespace#force_share_with_group_lock_on_descendants would result in updating _all_ namespaces in the namespaces table, not just the descendants. This is the result of ActiveRecord::Relation#update_all not taking into account the CTE. To work around this we use the CTE query as a sub-query instead of directly calling #update_all. To prevent this from happening the relations returned by Gitlab::GroupHierarchy are now marked as read-only, resulting in an error being raised when methods such as #update_all are used. Fortunately on GitLab.com our statement timeouts appear to have prevented this query from actually doing any damage other than causing a very large amount of dead tuples. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37916
-
- 07 9月, 2017 2 次提交
-
-
由 Michael Kozono 提交于
-
由 Michael Kozono 提交于
…when needed
-
- 31 8月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
In this instance its subgroups, and given we can't deploy it, we shouldn't allow it to be shown. Fixes gitlab-org/gitlab-ce#34864
-
- 14 8月, 2017 1 次提交
-
-
由 Nick Thomas 提交于
-
- 01 8月, 2017 2 次提交
-
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
- 17 7月, 2017 1 次提交
-
-
由 Nick Thomas 提交于
In EE, we make use of `namespace#public?` in projects. When the project is in a personal namespace, this breaks as the `public?` helper isn't present.
-
- 06 7月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
-
- 30 6月, 2017 1 次提交
-
-
由 Stan Hu 提交于
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.
-
- 29 6月, 2017 2 次提交
-
-
由 Tiago Botelho 提交于
-
由 Tiago Botelho 提交于
-
- 21 6月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 03 6月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 18 5月, 2017 2 次提交
-
-
由 Douwe Maan 提交于
-
由 Yorick Peterse 提交于
This hides/disables some UI elements and API parameters related to nested groups when MySQL is used, since nested groups are not supported for MySQL.
-