debian-mirror-gitlab/doc/user/feature_flags.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

37 lines
1.8 KiB
Markdown
Raw Normal View History

2020-11-24 15:15:51 +05:30
---
stage: none
group: Development
2022-11-25 23:54:43 +05:30
info: "See the Technical Writers assigned to Development Guidelines: https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines"
2020-11-24 15:15:51 +05:30
description: "Understand what 'GitLab features deployed behind flags' means."
2021-06-08 01:23:25 +05:30
layout: 'feature_flags'
2020-11-24 15:15:51 +05:30
---
# GitLab functionality may be limited by feature flags
> Feature flag documentation warnings were [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227806) in GitLab 13.4.
GitLab releases some features in a disabled state using [feature flags](../development/feature_flags/index.md),
allowing them to be tested by specific groups of users and strategically
rolled out until they become enabled for everyone.
As a GitLab user, this means that some features included in a GitLab release
may be unavailable to you.
In this case, you'll see a warning like this in the feature documentation:
2021-04-29 21:17:54 +05:30
This in-development feature might not be available for your use. There can be
2021-10-27 15:23:28 +05:30
[risks when enabling features still in development](../administration/feature_flags.md#risks-when-enabling-features-still-in-development).
2021-04-29 21:17:54 +05:30
Refer to this feature's version history for more details.
2020-11-24 15:15:51 +05:30
In the version history note, you'll find information on the state of the
feature flag, including whether the feature is on ("enabled by default") or
off ("disabled by default") for self-managed GitLab instances and for users of
2021-10-27 15:23:28 +05:30
GitLab.com.
2020-11-24 15:15:51 +05:30
If you're a user of a GitLab self-managed instance and you want to try to use a
disabled feature, you can ask a [GitLab administrator to enable it](../administration/feature_flags.md),
although changing a feature's default state isn't recommended.
If you're a GitLab.com user and the feature is disabled, be aware that GitLab may
be working on the feature for potential release in the future.