diff options
author | Sean McGivern <sean@mcgivern.me.uk> | 2018-09-06 11:22:19 +0300 |
---|---|---|
committer | Sean McGivern <sean@mcgivern.me.uk> | 2018-09-06 11:22:19 +0300 |
commit | 26de39fc64e927378e839ec1037f655bf87e3e73 (patch) | |
tree | 152ce52b29cfe475cab3c1692289b4dd67fa693e /doc | |
parent | 3ff54a959d631740f9ad31727048cb175f700c8b (diff) | |
parent | e57d99947a8837ef3bfe20022f4c5b3ad735ec8f (diff) |
Merge branch 'bw-commonmark-for-files' into 'master'
Enable CommonMark for files and wikis
See merge request gitlab-org/gitlab-ce!21228
Diffstat (limited to 'doc')
-rw-r--r-- | doc/development/feature_flags.md | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/doc/development/feature_flags.md b/doc/development/feature_flags.md index 702caacc74f..6f757f1ce7b 100644 --- a/doc/development/feature_flags.md +++ b/doc/development/feature_flags.md @@ -58,13 +58,20 @@ Features that are developed and are intended to be merged behind a feature flag should not include a changelog entry. The entry should be added in the merge request removing the feature flags. +In the rare case that you need the feature flag to be on automatically, use +`default_enabled: true` when checking: + +```ruby +Feature.enabled?(:feature_flag, project, default_enabled: true) +``` + ### Specs In the test environment `Feature.enabled?` is stubbed to always respond to `true`, so we make sure behavior under feature flag doesn't go untested in some non-specific contexts. - -If you need to test the feature flag in a different state, you need to stub it with: + +If you need to test the feature flag in a different state, you need to stub it with: ```ruby stub_feature_flags(my_feature_flag: false) |