diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-03 09:07:54 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-03 09:07:54 +0000 |
| commit | 87ef501eacd66d7166183d20d84e33de022f7002 (patch) | |
| tree | fa4e0f41e00a4b6aeb035530be4b5473f51b7a3d /doc/development/feature_flags | |
| parent | f321e51f46bcb628c3e96a44b5ebf3bb1c4033ab (diff) | |
| download | gitlab-ce-87ef501eacd66d7166183d20d84e33de022f7002.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/feature_flags')
| -rw-r--r-- | doc/development/feature_flags/controls.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/feature_flags/controls.md b/doc/development/feature_flags/controls.md index 922995cb915..a9a75791db7 100644 --- a/doc/development/feature_flags/controls.md +++ b/doc/development/feature_flags/controls.md @@ -147,7 +147,7 @@ is always on or off to the users. ## Cleaning up Once the change is deemed stable, submit a new merge request to remove the -feature flag. This ensures the change is available to all users and self-hosted +feature flag. This ensures the change is available to all users and self-managed instances. Make sure to add the ~"feature flag" label to this merge request so release managers are aware the changes are hidden behind a feature flag. If the merge request has to be picked into a stable branch, make sure to also add the |