diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-09-15 15:13:49 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-09-15 15:13:49 +0000 |
| commit | 229395d3af51cd46a9179f2eba142c027d08b208 (patch) | |
| tree | 56efbeeb1bb9bf8e6f68174436cacd5c2d20fca4 /doc/development/feature_flags/controls.md | |
| parent | 3107fe7203685580829c7d6ca56161e13acb83eb (diff) | |
| download | gitlab-ce-229395d3af51cd46a9179f2eba142c027d08b208.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/feature_flags/controls.md')
| -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 b08e759a93a..63dad3070c7 100644 --- a/doc/development/feature_flags/controls.md +++ b/doc/development/feature_flags/controls.md @@ -339,7 +339,7 @@ take one of the following actions: To remove a feature flag, open **one merge request** to make the changes. In the MR: -1. Add the ~"feature flag" label so release managers are aware the changes are hidden behind a feature flag. +1. Add the ~"feature flag" label so release managers are aware of the removal. 1. If the merge request has to be picked into a stable branch, add the appropriate `~"Pick into X.Y"` label, for example `~"Pick into 13.0"`. See [the feature flag process](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release) |