This change removes the add_policy_approvers_to_rules
feature flag which was default enabled in 16.8.

Changelog: other

rspec-profiling recently added new columns to the CSV collector, but
the PSQL collector doesn't support this. We should exclude columns
until we actually want them.

* https://gitlab.com/gitlab-org/quality/engineering-productivity/master-broken-incidents/-/issues/5763
* https://gitlab.com/gitlab-org/quality/engineering-productivity/master-broken-incidents/-/issues/5898

Previously consolidated object storage settings were disabled if any
section-specific connection were specified. For example, in Omnibus if
`gitlab_rails['artifacts_object_store_connection']` were specified
with some value, this would be a signal to use storage-specific
configurations.

However, this restriction became a problem when
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/131819 promoted
`ci_secure_files` to be specified as a consolidated storage
type. Because `gitlab_rails['ci_secure_files_object_store_connection']`
may be specified, this would effectively disable object storage
for all the other types.

Let's relax this constraint by comparing the section-specific config
with the consolidated object config. If the connection settings are
the same, we can still use consolidated settings.

This makes it possible to "promote" `ci_secure_files` from
a storage-specific type to a consolidated storage supported type.

Changelog: changed

This reverts merge request !131819

This MR places the API endpoint introduced in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147904
behind a beta flag to give us the opportunity to release it in a more
controlled way.

Changelog: changed

Before:

For a single suggestion:

- The author of the suggestion note is set as the author
- The user who applies the suggestion is the committer

For batch suggestions:

- The user who applies the suggestion is the author and committer

Now:

For signle and batch suggestions:

- The user who applies the suggestion is the author and committer

In a separate commit/MR an option to provide co-authors will be
introduced.

When commit signing is enabled, the committer will be GitLab

Remove CH analytics related feature flags

Changelog: removed
EE: true

Changelog: changed

Enables the approval rules drawer feature flag by default

Changelog: changed

Add the front-end updates needed to alter and utilize the
show_diff_preview_in_email column.

This should be used to hide the diff content found in the _note_email
templates.  Replace it with a string text informing the user that the
GitLab instance should be visited to see the line in question.

Changelog: added

Changelog: added
EE: true

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/146153

Move /-/profile/keys to /-/user_settings/ssh_keys and
redirect end_point to new endpoint till next major release (17.0)

Changelog: changed
EE: true

This primarily affects MailDeliveryJob enqueues by ActionMailer.

Changelog: other

Adds the ability to specify the context in which `rules:exists` searches
for the given file paths. The subkeys `paths`, `project`, and `ref` can
be specified.  If `project` is specified but not `ref`, the default
`ref` is the project's HEAD. If `project` is not specified, the defaults
are as follows:

For `job:rules:exists`, the default context is the project/ref in
which the pipeline is running.

For `include:rules:exists`, the default context is the project/ref
of the file in which the `include` is declared.

These changes are made behind a Feature flag:
`ci_support_rules_exists_paths_and_project`

When an issue is moved into another project
(copied and closed on source project), we will do the
same for tasks that might have been associated to the
issue

Changelog: changed

Move /-/profile/gpg_keys to /-/user_settings/gpg_keys and
redirect end_point to new endpoint till next major release (17.0)

Changelog: changed

Organization switching won't be available until Cells 1.5

This reverts merge request
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148356

Changelog: other

As we want to display all visible groups on the organization groups
dashboard on /-/organizations/<organization path>/groups_and_projects.

Changelog: other

The callout is shown to attract more attention to the global
Duo Chat button. The callout is shown only unless user explicitly
closed it, or clicks the Duo Chat button.

Changelog: other
EE: true

This extends the tailwind_all_the_way.mjs to accept an --only-used
flag.

Also remove the `content` option override from the all_the_way config.

I don't think we need this anymore, we can rely on the conversion script
to decide whether or not we want to parse all the utils.

Adds the ability to specify the context in which `rules:exists` searches
for the given file paths. The subkeys `paths`, `project`, and `ref` can
be specified.  If `project` is specified but not `ref`, the default
`ref` is the project's HEAD. If `project` is not specified, the defaults
are as follows:

For `job:rules:exists`, the default context is the project/ref in
which the pipeline is running.

For `include:rules:exists`, the default context is the project/ref
of the file in which the `include` is declared.

These changes are made behind a Feature flag:
`ci_support_rules_exists_paths_and_project`

Instead of loading `icons.json` and `file_icons/file_icons.json` from
`node_modules/@gitlab/svgs/dist`, we can also make them assets and
consume them from the asset pipeline. This means that if assets are
pre-compiled inside of `compile-test-assets`, they will be included in
the asset bundle and our rspec tests can pass _without_ relying on the
`node_modules` folder.

This removes the flags `merge_trains_create_ref_service` and
`fast_forward_merge_trains_support`, which controlled the rollout of
fast-forward and semi-linear merge trains. Both flags have been enabled
everywhere since 16.5.

The compatibility code paths should be removed at some point, but we
leave them in for now to ensure a smooth upgrade from any 16.x to 17.x.

Changelog: other

Add a new graphql field which will return delimited UTF codes instead of
removing invalid UTF characters.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/139090

This feature is set to true in production for sufficient amount of time
and can be removed

Changelog: removed

Fixed the spec issue

Adds a Ci::Pipeline::Chain step 'ComponentUsage' that
tracks the usage of CI Catalog components in the pipeline.
For each usage event, an Internal Event is sent and  a record
is inserted into `p_catalog_resource_component_usages` if not
already recorded for the given date.

Removes feature flag `ci_track_catalog_component_usage`

Changelog: added

This renames the feature flag from `epic_creation_with_synced_work_item`
to `sync_epic_to_work_item`. This has the following reasons:

1. We not only create work items when an epic gets created, but sync
   updates as well.
2. We want to sync the other way around in the future (work item to
   epic) where we will create the opposite feature flag and want to have
   a consistent naming.

This feature flag has already been enabled by default in 16.10.

Changelog: other

Remove default_to_import_tab experiment and tracking

Changelog: removed

auto_fix.

Changelog: removed

This change updates the design of the pipeline graph
by enabling the `new_pipeline_graph` feature flag.

This redesign of the pipeline uses GlCard to simplify
the view and add some mobile layout improvements.

Changelog: changed