diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-15 21:06:24 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-15 21:06:24 +0300 |
| commit | eca3cd3a9e7d9ea680086cad8150050ec8cdef3f (patch) | |
| tree | c3d262e0d8e721fc138c2d617f501fb09876f1b6 /doc/development/feature_flags | |
| parent | 6e81d7f6283fae1b22f66b9d9b133243921cbd9e (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/feature_flags')
| -rw-r--r-- | doc/development/feature_flags/development.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/feature_flags/development.md b/doc/development/feature_flags/development.md index 1ce9525d74e..c410c7eae41 100644 --- a/doc/development/feature_flags/development.md +++ b/doc/development/feature_flags/development.md @@ -61,7 +61,7 @@ you'd want to explicitly disable that flag until the frontend half is also ready to be shipped. To make sure this feature is disabled for both GitLab.com and self-managed instances you'd need to explicitly call `Feature.enabled?` method before the `feature_available` method. This ensures the feature_flag is defaulting -to `true`. +to `false`. ## Feature groups |