Sort flags by milestone and display results in table
Problem
When analyzing a FF report such as gitlab-org/quality/triage-reports#8579 (closed) it's difficult to visually see the milestone and look first at flags introduced in older milestones.
What does this MR do?
This MR sorts the feature flags by milestone (ascending order) and displays the results in a markdown table for better readability.
Before
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 the Sisense dashboard.
Feature flags needing action
These flags have been enabled in the codebase for 6 or more releases.
-
auto_devops_banner_disabled- %10.0 gitlab#350882 -
ci_enable_live_trace- %10.8 gitlab#350883 -
ci_enforce_throttle_pipelines_creation- %15.1 gitlab#362513 (closed) -
ci_enforce_throttle_pipelines_creation_override- %15.1 gitlab#362513 (closed) -
ci_job_artifacts_backlog_large_loop_limit- %14.10 gitlab#347151 (closed) -
ci_job_artifacts_backlog_work- %14.10 gitlab#347144 (closed) -
ci_new_query_for_running_stuck_jobs- %14.4 gitlab#339264 -
ci_parent_pipeline_cancels_children- %15.3 gitlab#354528 (closed) -
ci_pipeline_triggers_settings_vue_ui- %13.5 gitlab#247486 (closed) -
ci_skip_persistent_ref_existence_check- %13.1 gitlab#350885 -
configure_sentry_in_application_settings- %14.5 gitlab#344832 (closed) -
disable_unsafe_regexp- %14.9 *Missing rollout issue -
enable_new_sentry_integration- %14.9 gitlab#344832 (closed) -
enable_old_sentry_integration- %14.9 gitlab#344832 (closed) -
git_push_create_all_pipelines- %11.10 gitlab#350886 -
gitlab_ci_archived_trace_consistent_reads- %13.9 gitlab#350887 -
gitlab_ci_builds_queuing_metrics- %13.10 gitlab#350888 (closed) -
job_log_search- %15.2 gitlab#366455 (closed) -
legacy_merge_request_state_check_for_merged_result_pipelines- %15.2 gitlab#367019 (closed) -
project_overwrite_service_tracking- %14.1 gitlab#350889 -
rebase_without_ci_ui- %14.7 gitlab#350262 (closed)
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 been enabled in the codebase for 2 or more 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
After
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 the Sisense dashboard.
Feature flags needing action
These flags have been enabled in the codebase for 6 or more releases.
| Feature flag | Milestone | Link |
|---|---|---|
flag_one |
%11.7 | http://issue.com |
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 been enabled in the codebase for 2 or more releases.
| Feature flag | Milestone | Link |
|---|---|---|
flag_two |
%12.0 | Missing rollout issue |
flag_three |
%12.3 | http://nope.com |
Please review these feature flags to determine if they are able to be removed entirely.
This report is generated from feature-flag-alert project