An error occurred fetching the project authors.
- 26 Jun, 2018 1 commit
-
-
Lin Jen-Shin authored
-
- 05 Jun, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 04 May, 2018 1 commit
-
-
Mario de la Ossa authored
-
- 25 Apr, 2018 1 commit
-
-
Zeger-Jan van de Weg authored
Direct disk access is done through Gitaly now, so the legacy path was deprecated. This path was used in Gitlab::Shell however. This required the refactoring in this commit. Added is the removal of direct path access on the project model, as that lookup wasn't needed anymore is most cases. Closes https://gitlab.com/gitlab-org/gitaly/issues/1111
-
- 21 Mar, 2018 1 commit
-
-
Jacob Vosmaer authored
-
- 14 Mar, 2018 1 commit
-
-
Michael Kozono authored
-
- 13 Mar, 2018 3 commits
-
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
- 28 Feb, 2018 2 commits
-
-
Kamil Trzciński authored
This reverts commit 54a575f1, reversing changes made to c63af942.
-
Sean McGivern authored
Move uploads to object storage Closes #4163 See merge request gitlab-org/gitlab-ee!3867
-
- 07 Feb, 2018 1 commit
-
-
Nick Thomas authored
-
- 06 Feb, 2018 2 commits
-
-
Douwe Maan authored
-
Mayra Cabrera authored
-
- 05 Feb, 2018 1 commit
-
-
Nick Thomas authored
-
- 01 Feb, 2018 1 commit
-
-
Micaël Bergeron authored
-
- 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
-
- 05 Jan, 2018 1 commit
-
-
Jacob Vosmaer authored
-
- 03 Jan, 2018 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
- 08 Dec, 2017 1 commit
-
-
Mayra Cabrera authored
-
- 04 Dec, 2017 1 commit
-
-
Bob Van Landuyt authored
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.
-
- 17 Oct, 2017 1 commit
-
-
Jen-Shin Lin authored
Security fixes for 10.1 RC See merge request gitlab/gitlabhq!2209
-
- 10 Oct, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 07 Oct, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 05 Oct, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 07 Sep, 2017 1 commit
-
-
Tiago Botelho authored
-
- 06 Sep, 2017 4 commits
-
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
…when needed
-
- 14 Aug, 2017 1 commit
-
-
Nick Thomas authored
-
- 02 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 27 Jul, 2017 2 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Remove superfluous lib: true, type: redis, service: true, models: true, services: true, no_db: true, api: true Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 18 Jul, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 17 Jul, 2017 1 commit
-
-
Nick Thomas authored
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.
-
- 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
-
-
Oswaldo Ferreira authored
-
- 21 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-