Skip to content

Update feature flags that belong to group::code review

Patrick Bajao requested to merge pb-feature-flag-group-code-review-update into master

What does this MR do?

Since ~group::source code is being split into another group called ~group::code review, feature flags that belong to that group are updated accordingly.

Background

I grep'ed the project for feature flags that are tagged under groupsource code group. Found these:

config/feature_flags/development/approvals_commented_by.yml:group: group::source code
config/feature_flags/development/async_commit_diff_files.yml:group: group::source code
config/feature_flags/development/branch_list_keyset_pagination.yml:group: group::source code
config/feature_flags/development/cached_markdown_blob.yml:group: group::source code
config/feature_flags/development/default_merge_ref_for_diffs.yml:group: group::source code
config/feature_flags/development/display_merge_conflicts_in_diff.yml:group: group::source code
config/feature_flags/development/global_default_branch_name.yml:group: group::source code
config/feature_flags/development/grape_gitlab_json.yml:group: group::source code
config/feature_flags/development/hide_jump_to_next_unresolved_in_threads.yml:group: group::source code
config/feature_flags/development/highlight_current_diff_row.yml:group: group::source code
config/feature_flags/development/include_lfs_blobs_in_archive.yml:group: group::source code
config/feature_flags/development/increased_diff_limits.yml:group: group::source code
config/feature_flags/development/json_limited_encoder.yml:group: group::source code
config/feature_flags/development/merge_ref_auto_sync.yml:group: group::source code
config/feature_flags/development/merge_ref_auto_sync_lock.yml:group: group::source code
config/feature_flags/development/merge_request_cached_pipeline_serializer.yml:group: group::source code
config/feature_flags/development/merge_request_draft_filter.yml:group: group::source code
config/feature_flags/development/merge_request_reviewers.yml:group: group::source code
config/feature_flags/development/merge_request_widget_graphql.yml:group: group::source code
config/feature_flags/development/mr_commit_neighbor_nav.yml:group: group::source code
config/feature_flags/development/mrc_api_use_raw_diffs_from_gitaly.yml:group: group::source code
config/feature_flags/development/multiline_comments.yml:group: group::source code
config/feature_flags/development/paginated_notes.yml:group: group::source code
config/feature_flags/development/remove_resolve_note.yml:group: group::source code
config/feature_flags/development/repack_after_shard_migration.yml:group: group::source code
config/feature_flags/development/squash_options.yml:group: group::source code
config/feature_flags/development/unified_diff_components.yml:group: group::source code
config/feature_flags/development/unified_diff_lines.yml:group: group::source code
config/feature_flags/development/usage_data_i_source_code_code_intelligence.yml:group: group::source code
config/feature_flags/development/view_diffs_file_by_file.yml:group: group::source code
config/feature_flags/development/widget_visibility_polling.yml:group: group::source code
ee/config/feature_flags/development/create_approval_todos_on_mr_update.yml:group: group::source code
ee/config/feature_flags/development/pull_mirror_branch_prefix.yml:group: group::source code

Looked into each feature flag and the ones that belongs to groupcode review are updated in this MR.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • [-] Security reports checked/validated by a reviewer from the AppSec team

Merge request reports