- 29 Nov, 2018 1 commit
-
-
Toon Claes authored
-
- 27 Nov, 2018 1 commit
-
-
Tiago Botelho authored
Clears the import related columns and code from the Project model over to the ProjectImportState model
-
- 19 Nov, 2018 1 commit
-
-
Nick Thomas authored
-
- 17 Nov, 2018 1 commit
-
-
Stan Hu authored
Admins would be prevented from adding a project deploy key since the accessible keys would be restricted to the user's keys. Also backports a spec for DeployKeysController from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8432.
-
- 01 Nov, 2018 1 commit
-
-
George Tsiolis authored
-
- 22 Oct, 2018 1 commit
-
-
Yorick Peterse authored
This moves the logic of Project#rename_repo and all methods _only_ used by this method into a new service class: Projects::AfterRenameService. By moving this code into a separate service class we can more easily refactor it, and we also get rid of some RuboCop "disable" statements automatically. During the refactoring of this code, I removed most of the explicit logging using Gitlab::AppLogger. The data that was logged would not be useful when debugging renaming issues, as it does not add any value on top of data provided by users. I also removed a variety of comments that either mentioned something the code does in literal form, or contained various grammatical errors. Instead we now resort to more clearly named methods, removing the need for code comments. This method was chosen based on analysis in https://gitlab.com/gitlab-org/release/framework/issues/28. In this issue we determined this method has seen a total of 293 lines being changed in it. We also noticed that RuboCop determined the ABC size (https://www.softwarerenovation.com/ABCMetric.pdf) was too great.
-
- 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.
-
- 05 Oct, 2018 2 commits
-
-
Tuomo Ala-Vannesluoma authored
-
Fabian Schneider authored
-
- 03 Oct, 2018 1 commit
-
-
Chantal Rollison authored
-
- 21 Sep, 2018 1 commit
-
-
Douglas Barbosa Alexandre authored
We should not synchronize the source repository with the target root ref while updating a push mirror.
-
- 19 Sep, 2018 2 commits
-
-
Stan Hu authored
-
Stan Hu authored
When there are many tags in a container repository, deleting them can exceed the default 60 second idle-in-transaction timeout in Sidekiq. We now explicitly delete them in the DestroyService before destroying the model. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/51380
-
- 11 Sep, 2018 1 commit
-
-
Yorick Peterse authored
This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
-
- 10 Sep, 2018 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 08 Sep, 2018 1 commit
-
-
Stan Hu authored
-
- 07 Sep, 2018 1 commit
-
-
Stan Hu authored
When a container registry has many tags, it's easy for the DELETE call to take more than 60 seconds and fail. This can also leave the registry in a bad state with null bytes since some of the images have been deleted with tags still pointing to them. In addition, we have to prevent users from accidentally initiating the delete multiple times or this could leave the registry with orphaned tags. This commit also adds a flash message to notify the user the registry is scheduled for deletion. Closes #49926, #51063
-
- 06 Sep, 2018 1 commit
-
-
Mayra Cabrera authored
-
- 30 Aug, 2018 1 commit
-
-
James Lopez authored
-
- 29 Aug, 2018 1 commit
-
-
James Lopez authored
-
- 23 Aug, 2018 1 commit
-
-
Stan Hu authored
Remote mirrors only get created when the URL changes, However, during the GCP migration, the remote mirror did not get created automatically. Plus, there's no guarantee someone restoring a repository from backup would have this remote. We now add the remote each time we attempt to fetch from the repository. This works because Gitaly doesn't throw up an exception or error if the remote already exists: https://gitlab.com/gitlab-org/gitaly/issues/1317 In the future, we should attempt to add if the remote doesn't exist: https://gitlab.com/gitlab-org/gitaly/issues/1316 Closes #50562
-
- 20 Aug, 2018 1 commit
-
-
Toon Claes authored
A forked project stores its LFS objects in the `forked_from_project`. So the LFS objects become inaccessible, and therefore delete them from the database so they'll get cleaned up. To be refactored when implementing https://gitlab.com/gitlab-org/gitlab-ce/issues/39769
-
- 17 Aug, 2018 1 commit
-
-
Valery Sizov authored
-
- 16 Aug, 2018 2 commits
-
-
Yorick Peterse authored
This whitelists all existing places where we use "destroy_all".
-
Dylan Griffith authored
-
- 12 Aug, 2018 1 commit
-
-
gfyoung authored
Partially addresses #47424.
-
- 10 Aug, 2018 3 commits
-
-
Peter Leitzen authored
-
Peter Leitzen authored
-
Peter Leitzen authored
-
- 03 Aug, 2018 1 commit
-
-
Valery Sizov authored
Resolve "Hashed storage: extend "Enable hashed storage for all new projects" to "for all new and renamed projects""
-
- 02 Aug, 2018 2 commits
-
-
Zeger-Jan van de Weg authored
Rails 5 didn't like the arel usage, see: https://gitlab.com/gitlab-org/gitlab-ce/issues/49873#note_92040225 This change makes that right, but also makes the query nicer. I'm not sure anymore why it didn't work before, however there were issues with it that have been resolved.
-
James Lopez authored
- Refactor uploads manager - Refactor importer, update import spec - Add more object storage specs
-
- 01 Aug, 2018 1 commit
-
-
Zeger-Jan van de Weg authored
Our friends at GitHub show the programming languages for a long time, and inspired by that this commit means to create about the same functionality. Language detection is done through Linguist, as before, where the difference is that we cache the result in the database. Also, Gitaly can incrementaly scan a repository. This is done through a shell out, which creates overhead of about 3s each run. For now this won't be improved. Scans are triggered by pushed to the default branch, usually `master`. However, one exception to this rule the charts page. If we're requesting this expensive data anyway, we just cache it in the database. Edge cases where there is no repository, or its empty are caught in the Repository model. This makes use of Redis caching, which is probably already loaded. The added model is called RepositoryLanguage, which will make it harder if/when GitLab supports multiple repositories per project. However, for now I think this shouldn't be a concern. Also, Language could be confused with the i18n languages and felt like the current name was suiteable too. Design of the Project#Show page is done with help from @dimitrieh. This change is not visible to the end user unless detections are done.
-
- 31 Jul, 2018 1 commit
-
-
Jarka Kadlecová authored
-
- 30 Jul, 2018 1 commit
-
-
Jarka Kadlecová authored
-
- 25 Jul, 2018 2 commits
-
-
Yorick Peterse authored
This adds a database migration that creates routes for any projects and namespaces that don't already have one. We also remove the runtime code for dynamically creating routes, as this is no longer necessary.
-
Francisco Javier López authored
-
- 20 Jul, 2018 1 commit
-
-
Francisco Javier López authored
-
- 19 Jul, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 17 Jul, 2018 1 commit
-
-
Stan Hu authored
-