Feature flags requiring attention for group::ide - 2025-10-01
This is a group level feature flag report containing feature flags that should be evaluated or need action.
Feature flag trends can be found in this dashboard.
A feature flag is considered end-of-life when it has existed in the codebase for longer than the prescribed lifespan based on feature flag type.
Feature flags needing action
These flags are approaching end-of-life in the next milestone.
| Feature flag | Milestone added | End of life milestone | Enabled by default? | Rollout issue |
|---|
Please take action on these feature flags by performing one of the following options:
- Enable the feature flag by default and remove it.
- Convert it to an instance, group, or project setting.
- Revert the changes if it's still disabled and not needed anymore.
Feature flags overdue
These flags have reached their maximum lifespan.
| Feature flag | Milestone added | End of life milestone | Enabled by default? | Rollout issue |
|---|---|---|---|---|
build_service_proxy development | Introduced by | No feature issue | GitLab.com state changes |
%11.11 | %12.5 | ||
reject_unsigned_commits_by_gitlab development | Introduced by | No feature issue | GitLab.com state changes |
%13.11 | %14.5 | [Feature flag] Remove `reject_unsigned_commits_... (gitlab-org/gitlab#326775) • Unassigned • Next 1-3 releases |
Please review these feature flags to determine if they are able to be removed entirely.
This report is generated from feature-flag-alert project by https://gitlab.com/gitlab-org/quality/toolbox/-/jobs/11559330452.