diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-29 06:08:38 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-29 06:08:38 +0300 |
| commit | 4c9d60c166ff44abb3a354925e8a15d31b08e15c (patch) | |
| tree | 53013062606064c935a236c1a0860518420caeb8 /doc/development/background_migrations.md | |
| parent | 79216161b305b8d23b34226d45aa92dbae316cfe (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/background_migrations.md')
| -rw-r--r-- | doc/development/background_migrations.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/development/background_migrations.md b/doc/development/background_migrations.md index 746618be50f..02d31976481 100644 --- a/doc/development/background_migrations.md +++ b/doc/development/background_migrations.md @@ -59,8 +59,7 @@ integrity is guaranteed. ## Background migrations for EE-only features All the background migration classes for EE-only features should be present in GitLab CE. -For this purpose, an empty class can be created for GitLab CE and for GitLab EE it can be extended -For this purpose, an empty class can be created for GitLab CE, and it can be extended for GitLab EE +For this purpose, an empty class can be created for GitLab CE, and it can be extended for GitLab EE as explained in the [guidelines for implementing Enterprise Edition features](ee_features.md#code-in-libgitlabbackground_migration). ## How It Works |