diff options
| author | Fabio Pitino <fpitino@gitlab.com> | 2019-05-30 17:12:48 +0100 |
|---|---|---|
| committer | Fabio Pitino <fpitino@gitlab.com> | 2019-05-30 17:13:14 +0100 |
| commit | 1d9d80ca30a5496cd919c8af61fe4233c49b1d5a (patch) | |
| tree | a8f45692fb2b589ddf2b970e162e93fa3134aeb1 | |
| parent | 55cdf399d696bd5ed7d6c33b1fc2975f4c2a8b76 (diff) | |
| download | gitlab-ce-fp-update-invalid-anchor-link.tar.gz | |
Remove line ending inside the link definitionfp-update-invalid-anchor-link
| -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 06c79384577..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 |