diff options
| author | Małgorzata Ksionek <meksionek@gmail.com> | 2019-04-11 08:43:43 +0200 |
|---|---|---|
| committer | Małgorzata Ksionek <meksionek@gmail.com> | 2019-04-11 09:00:51 +0200 |
| commit | 0bda1516d4fab1da5c73e5b056a6ebd6062c300e (patch) | |
| tree | bf80b5dbec375c2a28af2268207dac735c8af5d0 | |
| parent | ae255a1b53b39c4b87c7eb13750cf756f92da979 (diff) | |
| download | gitlab-ce-add-to-docs-info-about-moving-migrations.tar.gz | |
Add review remarks and claryfications to migration guideadd-to-docs-info-about-moving-migrations
| -rw-r--r-- | doc/development/migration_style_guide.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/migration_style_guide.md b/doc/development/migration_style_guide.md index 91c3a238c48..0c326eeb851 100644 --- a/doc/development/migration_style_guide.md +++ b/doc/development/migration_style_guide.md @@ -426,6 +426,6 @@ by an integer. For example: `users` would turn into `users0` ### Moving migrations from EE to CE -In the situation when some migrations need to be moved from Enterprise Edition to Community Edition, -a migration file should be moved from `ee/db/{post_,}migrate` directory to `db/{post_,}migrate` directory. This way -the schema number remains intact, there is no need to modify old migrations, but proper columns, tables or data are added in the Community Edition. +When migrations need to be moved from GitLab Enterprise Edition to GitLab Community Edition, +a migration file should be moved from `ee/db/{post_,}migrate` directory in the `gitlab-ee` project to `db/{post_,}migrate` directory in the `gitlab-ce` project. This way +the schema number remains intact, there is no need to modify old migrations, and proper columns, tables or data are added in the Community Edition. |