Feature flags requiring attention for group::gitaly - 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:

1. Enable the feature flag by default and remove it.
2. Convert it to an instance, group, or project setting.
3. 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
gitaly_upload_pack_gitaly_hooks undefined | Introduced by ? | No feature issue | GitLab.com state changes	%13.9	%13.11	❌	https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/807+s
gitaly_user_merge_branch_access_error undefined | Introduced by | No feature issue | GitLab.com state changes	%14.3	%14.5	❌	[Feature flag] Enable use of structured errors ... (gitlab-org/gitaly#3757 - closed) • Patrick Steinhardt • 14.9
pipeline_cleanup_ref_worker_async development | Introduced by | No feature issue | GitLab.com state changes	%16.1	%16.7	❌	[Feature flag] Enable pipeline_cleanup_ref_work... (gitlab-org/gitlab#421696) • Unassigned • Backlog
disable_keep_around_refs ops | Introduced by | No feature issue | GitLab.com state changes	%16.1	%17.1	❌
merge_request_cleanup_ref_worker_async development | Introduced by | No feature issue | GitLab.com state changes	%16.2	%16.8	❌	[Feature flag] Enable merge_request_cleanup_ref... (gitlab-org/gitlab#421695) • Unassigned • Backlog
merge_request_delete_gitaly_refs_in_batches development | Introduced by | No feature issue | GitLab.com state changes	%16.3	%16.9	❌	Rollout feature flag pipeline_delete_gitaly_ref... (gitlab-org/gitlab#416969) • James Liu • 18.6
pipeline_delete_gitaly_refs_in_batches development | Introduced by | No feature issue | GitLab.com state changes	%16.3	%16.9	❌	Rollout feature flag pipeline_delete_gitaly_ref... (gitlab-org/gitlab#416969) • James Liu • 18.6
collect_all_diff_paths development | Introduced by | No feature issue | GitLab.com state changes	%16.4	%16.10	❌	[Feature Flag] Enable `collect_all_diff_paths` (gitlab-org/gitlab#421460) • Unassigned
remove_file_commit_history_following ops | Introduced by | Feature issue | GitLab.com state changes	%16.10	%17.10	❌	[Feature flag] Rollout of `remove_file_commit_h... (gitlab-org/gitlab#441312 - closed) • Unassigned
project_repositories_health gitlab_com_derisk | Introduced by | Feature issue | GitLab.com state changes	%17.10	%18.0	❌	[Feature flag] Enable project_repositories_health (gitlab-org/gitlab#521115) • James Liu

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.