- 01 Dec, 2017 18 commits
-
-
Michael Kozono authored
So the path on source installs cannot be too long for our column. And fix the column length test since Route.path is limited to 255 chars, it doesn’t matter how many nested groups there are.
-
Michael Kozono authored
-
Michael Kozono authored
Since duplicate inserts are now ignored.
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
by copy-pasting in the whole `Upload` class. Also, fix `Namespace` `model_type` (it should not be `Group`).
-
Michael Kozono authored
-
Michael Kozono authored
To process the unhashed_upload_files table.
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
To create the table, and schedule the background migration that begins the work.
-
Rémy Coutable authored
Ensure `Namespace`'s is namespaced in `Gitlab::Kubernetes::Helm#initialize` and fix a transient failing spec due to that Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Stan Hu authored
This was failing regularly with an Error 500 when the API branches endpoint was used. Closes #40615
-
- 30 Nov, 2017 3 commits
-
-
Zeger-Jan van de Weg authored
This endpoint still has to be migrated, and this comment makes sure everyone knows we are aware of this one. [ci skip]
-
haseeb authored
-
Lin Jen-Shin authored
-
- 29 Nov, 2017 4 commits
-
-
haseeb authored
-
Bob Van Landuyt authored
That way we can join forks-of-forks into the same network even if their original source was deleted. Consider the following: `awesome-oss/badger` is forked to `coolstuff/badger`, which is forked to `user-a/badger` which in turn is forked to `user-b/badger`. When `awesome-oss/badger` is deleted, we will now create a fork network with `coolstuff/badger` as the root. The `user-a/badger` and `user-b/badger` projects will be added to the network.
-
Andrew Newdigate authored
-
Kim "BKC" Carlbäcker authored
- Better gitaly-handling in /api/internal/allowed specs
-
- 28 Nov, 2017 4 commits
-
-
Sean McGivern authored
If a merge request was created with a branch name that also matched a tag name, we'd generate a comparison to or from the tag respectively, rather than the branch. Merging would still use the branch, of course. To avoid this, ensure that when we get the branch heads, we prepend the reference prefix for branches, which will ensure that we generate the correct comparison.
-
Sean McGivern authored
The st_commits and st_diffs columns on merge_request_diffs historically held the YAML-serialised data for a merge request diff, in a variety of formats. Since 9.5, these have been migrated in the background to two new tables: merge_request_diff_commits and merge_request_diff_files. That has the advantage that we can actually query the data (for instance, to find out how many commits we've stored), and that it can't be in a variety of formats, but must match the new schema. This is the final step of that journey, where we drop those columns and remove all references to them. This is a breaking change to the importer, because we can no longer import diffs created in the old format, and we cannot guarantee the export will be in the new format unless it was generated after this commit.
-
Zeger-Jan van de Weg authored
At this time we had good metrics on what number or requests each GRPC received, but were in the dark what controller#action combination was responsable. Or if Sidekiq was responsable. Now added are call counts per service and rpc matched with controller#action combinations.
-
Shinya Maeda authored
-
- 27 Nov, 2017 7 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 25 Nov, 2017 3 commits
-
-
George Andrinopoulos authored
-
digitalMoksha authored
-
digitalMoksha authored
-
- 24 Nov, 2017 1 commit
-
-
digitalMoksha authored
-