diff options
| author | Fabio Pitino <fpitino@gitlab.com> | 2019-06-03 19:04:07 +0300 |
|---|---|---|
| committer | Marcia Ramos <marcia@gitlab.com> | 2019-06-03 19:04:07 +0300 |
| commit | 2474023bde33eaf22fb9f802f64598829e5213fd (patch) | |
| tree | fc495671611cf5b1a79c888f117340846bd52000 /doc/development/rolling_out_changes_using_feature_flags.md | |
| parent | a41585628990eb48b81ca7a9cf79a51a070ddb24 (diff) | |
Update invalid anchor link
Diffstat (limited to 'doc/development/rolling_out_changes_using_feature_flags.md')
| -rw-r--r-- | doc/development/rolling_out_changes_using_feature_flags.md | 7 |
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 |