summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcia Ramos <marcia@gitlab.com>2019-06-03 16:04:08 +0000
committerMarcia Ramos <marcia@gitlab.com>2019-06-03 16:04:08 +0000
commit658c98191a8604fa52d668d639eca308a76477fe (patch)
treefc495671611cf5b1a79c888f117340846bd52000
parenta41585628990eb48b81ca7a9cf79a51a070ddb24 (diff)
parent2474023bde33eaf22fb9f802f64598829e5213fd (diff)
downloadgitlab-ce-658c98191a8604fa52d668d639eca308a76477fe.tar.gz
Merge branch 'fp-update-invalid-anchor-link' into 'master'
Update invalid anchor link See merge request gitlab-org/gitlab-ce!28822
-rw-r--r--doc/development/rolling_out_changes_using_feature_flags.md7
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/development/rolling_out_changes_using_feature_flags.md b/doc/development/rolling_out_changes_using_feature_flags.md
index 1b4c89ba2a8..84028b1b342 100644
--- a/doc/development/rolling_out_changes_using_feature_flags.md
+++ b/doc/development/rolling_out_changes_using_feature_flags.md
@@ -200,10 +200,9 @@ isn't gated by a License or Plan.
### Undefined feature flags default to "on"
-An important side-effect of the [implicit feature
-flags][#implicit-feature-flags] mentioned above is that unless the feature is
-explicitly disabled or limited to a percentage of users, the feature flag check
-will default to `true`.
+An important side-effect of the [implicit feature flags](#implicit-feature-flags)
+mentioned above is that unless the feature is explicitly disabled or limited to a
+percentage of users, the feature flag check will default to `true`.
As an example, if you were to ship the backend half of a feature behind a flag,
you'd want to explicitly disable that flag until the frontend half is also ready