From 2474023bde33eaf22fb9f802f64598829e5213fd Mon Sep 17 00:00:00 2001 From: Fabio Pitino Date: Mon, 3 Jun 2019 16:04:07 +0000 Subject: [PATCH] Update invalid anchor link --- doc/development/rolling_out_changes_using_feature_flags.md | 7 +++---- 1 file 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 -- GitLab