- 04 1月, 2019 4 次提交
-
-
由 Shinya Maeda 提交于
Fix coding style Improve coding style Decouple UPDATE and DELETE operations of asset links Rename links_attributes to assets:links Rename exposed param and updated spec
-
由 Shinya Maeda 提交于
- Add Releases::Links model - Expose it in release API - Add integration tests
-
由 Dylan Griffith 提交于
Many changes were also made to tests that expected this to default to false.
-
由 Andreas Brandl 提交于
This is useful to distinguish any other indexes on the same columns but with different conditions and/or sorting.
-
- 03 1月, 2019 2 次提交
-
-
由 Andreas Brandl 提交于
This adds specific indexes to speed up the query mentioned in https://gitlab.com/gitlab-org/gitlab-ce/issues/50763 and to avoid statement timeouts. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/50763.
-
由 Jasper Maes 提交于
-
- 26 12月, 2018 2 次提交
-
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
- 21 12月, 2018 1 次提交
-
-
由 George Tsiolis 提交于
-
- 19 12月, 2018 2 次提交
-
-
Adds a background migration that will ensure all projects that are on legacy storage have a row in `project_repositories`.
-
由 Jasper Maes 提交于
-
- 18 12月, 2018 3 次提交
-
-
由 Joshua Lambert 提交于
-
由 Gabriel Mazetto 提交于
-
由 Jasper Maes 提交于
-
- 16 12月, 2018 1 次提交
-
-
由 Jasper Maes 提交于
-
- 14 12月, 2018 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 13 12月, 2018 1 次提交
-
-
由 Alessio Caiazza 提交于
This commit adds a name to each release, defaulting it to tag name, keeps track of the SHA when a new release is created and tracks the current user as release author.
-
- 12 12月, 2018 1 次提交
-
-
由 Yorick Peterse 提交于
Extending from ActiveRecord::Migration is deprecated, but was still used in a bunch of places.
-
- 08 12月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
When a project is forked, the new repository used to be a deep copy of everything stored on disk by leveraging `git clone`. This works well, and makes isolation between repository easy. However, the clone is at the start 100% the same as the origin repository. And in the case of the objects in the object directory, this is almost always going to be a lot of duplication. Object Pools are a way to create a third repository that essentially only exists for its 'objects' subdirectory. This third repository's object directory will be set as alternate location for objects. This means that in the case an object is missing in the local repository, git will look in another location. This other location is the object pool repository. When Git performs garbage collection, it's smart enough to check the alternate location. When objects are duplicated, it will allow git to throw one copy away. This copy is on the local repository, where to pool remains as is. These pools have an origin location, which for now will always be a repository that itself is not a fork. When the root of a fork network is forked by a user, the fork still clones the full repository. Async, the pool repository will be created. Either one of these processes can be done earlier than the other. To handle this race condition, the Join ObjectPool operation is idempotent. Given its idempotent, we can schedule it twice, with the same effect. To accommodate the holding of state two migrations have been added. 1. Added a state column to the pool_repositories column. This column is managed by the state machine, allowing for hooks on transitions. 2. pool_repositories now has a source_project_id. This column in convenient to have for multiple reasons: it has a unique index allowing the database to handle race conditions when creating a new record. Also, it's nice to know who the host is. As that's a short link to the fork networks root. Object pools are only available for public project, which use hashed storage and when forking from the root of the fork network. (That is, the project being forked from itself isn't a fork) In this commit message I use both ObjectPool and Pool repositories, which are alike, but different from each other. ObjectPool refers to whatever is on the disk stored and managed by Gitaly. PoolRepository is the record in the database.
-
- 07 12月, 2018 7 次提交
-
-
由 Kamil Trzciński 提交于
Brings back 1e8f1de0 reverted in !23644 Closes #52342 See merge request gitlab-org/gitlab-ce!23436
-
由 Shinya Maeda 提交于
-
-
由 Robert Speicher 提交于
This reverts commit 1e8f1de0, reversing changes made to 62d97112.
-
由 Oswaldo Ferreira 提交于
-
由 Toon Claes 提交于
This adds a background migration that will ensure all projects that are on hashed storage have a row in `project_repositories`. Related issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/48527
-
由 Nick Thomas 提交于
-
- 06 12月, 2018 5 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Forks influence the working of GitLab, and now getting in a fork is a situation that's harder than it needs to be.
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Stan Hu 提交于
Determined by running the script: ``` included = `git grep --name-only ShellAdapter`.chomp.split("\n") used = `git grep --name-only gitlab_shell`.chomp.split("\n") included - used ```
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
- 05 12月, 2018 6 次提交
-
-
由 Francisco Javier López 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Shinya Maeda 提交于
-
由 Yorick Peterse 提交于
This reverts commit d7291c64
-
由 🤖 GitLab Bot 🤖 提交于
This reverts commit c3d0f129
-
- 04 12月, 2018 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 03 12月, 2018 2 次提交
-
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
-