diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-10-27 15:09:41 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-10-27 15:09:41 +0300 |
commit | 0a559c913e4d333f339fcc03b89bfeade9ca0b93 (patch) | |
tree | 12175c0e0b5b97a72250acb8261d1c2512ef6bae /doc/architecture | |
parent | ef96d56ed3c723ac913ea4d8ab6504043f849555 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/architecture')
-rw-r--r-- | doc/architecture/blueprints/feature_flags_development/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/architecture/blueprints/feature_flags_development/index.md b/doc/architecture/blueprints/feature_flags_development/index.md index a5e46d25921..94d52ea3474 100644 --- a/doc/architecture/blueprints/feature_flags_development/index.md +++ b/doc/architecture/blueprints/feature_flags_development/index.md @@ -29,7 +29,7 @@ The extensive usage of feature flags poses a few challenges We sometimes forget how our feature flags are configured or why we haven't yet removed the feature flag. - The usage of feature flags can also be confusing to people outside of - development that might not fully understand dependence of ~feature or ~bug + development that might not fully understand dependence of ~"type::feature" or ~"type::bug" fix on feature flag and how this feature flag is configured. Or if the feature should be announced as part of release post. - Maintaining feature flags poses additional challenge of having to manage |