- Mar 17, 2020
-
-
GitLab Bot authored
-
- Mar 16, 2020
-
-
GitLab Bot authored
-
- Mar 03, 2020
-
-
GitLab Bot authored
-
- Jan 30, 2020
-
-
GitLab Bot authored
-
- Dec 10, 2019
-
-
GitLab Bot authored
-
- Oct 11, 2019
-
-
GitLab Bot authored
-
- Oct 04, 2019
-
-
GitLab Bot authored
-
- Sep 27, 2019
-
-
GitLab Bot authored
-
- Sep 18, 2019
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Jul 24, 2019
-
-
A project can have the same `LfsObject` linked with up to three `LfsObjectsProject` records. Each of these records would be for a different repository, recorded in the `repository_type` property. The different repositories at time of writing are "project", "wiki", and "design". See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894 This change exports the list of `repository_type`s as a JSON mapping of oid => repository_types, which are imported to recreate the correct `LfsObjectsProject` records. https://gitlab.com/gitlab-org/gitlab-ee/issues/11090
-
- Jul 19, 2019
-
-
Ensure that all numbered lists use only 1. and no other numbers. Also ensure that numbered lists use proper spacing.
-
- Jun 17, 2019
-
-
Yorick Peterse authored
This backports all EE schema changes to CE, including EE migrations, ensuring both use the same schema. == Updated tests A spec related to ghost and support bot users had to be modified to make it pass. The spec in question assumes that the "support_bot" column exists when defining the spec. In the single codebase setup this is not the case, as the column is backported in a later migration. Any attempt to use a different schema version or use of "around" blocks to conditionally disable specs won't help, as reverting the backport migration would also drop the "support_bot" column. Removing the "support_bot" tests entirely appears to be the only solution. We also need to update some foreign key tests now that we have backported the EE columns. Fortunately, these changes are very minor. == Backporting migrations This commit moves EE specific migrations (except those for the Geo tracking database) and related files to CE, and also removes any traces of the ee/db directory. Some migrations had to be modified or removed, as they no longer work with the schema being backported. These migrations were all quite old, so we opted for removing them where modifying them would take too much time and effort. Some old migrations were modified in EE, while also existing in CE. In these cases we took the EE code, and in one case removed them entirely. It's not worth spending time trying to merge these changes somehow as we plan to remove old migrations around the release of 12.0, see https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
-
- May 27, 2019
-
-
Achilleas Pipinellis authored
This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
-
- Feb 25, 2019
-
-
Takuya Noguchi authored
Signed-off-by:
Takuya Noguchi <takninnovationresearch@gmail.com>
-
- Feb 18, 2019
-
-
For the sake of consistency, removes any extraneous consecutive blank lines from the doc suite.
-
- Jan 14, 2019
-
-
James Lopez authored
-