14 days after a merge request gets closed/merged, its merge ref
will be deleted and moved as a keep-around ref (if not yet added).

This is to ensure that the commit won't be deleted when GC runs
and still being able to reduce the number of advertised refs on
git push/pull.

Before deletion, it'll be cached to `merge_ref_sha` column of
`merge_requests` table so we can still display the merge ref diff.

Fix dasboard to dashboard

See merge request gitlab-org/gitlab!41440

Fix user registration e2e spec

Closes #247743

See merge request gitlab-org/gitlab!42060

Clean up stale merge request HEAD ref

See merge request gitlab-org/gitlab!41555

Add confidential parameter to epic link creation API

Closes #229839

See merge request gitlab-org/gitlab!37882

- set to copy the confidentiality status from the parent epic
- replicate this behavior on the frontend

Fixes https://gitlab.com/gitlab-org/gitlab/-/issues/229839

Default Enable Read-Only Legacy Feature Flags

See merge request gitlab-org/gitlab!40320

Update documentation for legacy flags

Add graphQL mutation for destroying issue boards

See merge request gitlab-org/gitlab!40930

Add tokens to agents graphql endpoint

See merge request gitlab-org/gitlab!40779

Guard type selector via permissions

Closes #247464

See merge request gitlab-org/gitlab!42007

Milestone Dashboard: Move Gray Type Badge Next to the Milestone Title

See merge request gitlab-org/gitlab!39617

Fix todos hover style in dark mode

Closes #241970

See merge request gitlab-org/gitlab!41122

Our page specific CSS don't have a dark mode variant. Rather than
compiling a page specific CSS file for each theme, we make use of CSS
variables in order to define the correct colors. There is prior art with
the IDE Themes and eventually we can move to _only_ use these variables.

In case one variable is undefined, we will fallback on the light theme
value for it. Thus we just need to define the variables in the dark
theme, since the fallback _is_ the light theme.

This approach will allow us to create other themes, e.g. for
accessibility (color blindness, high contrast) in the future.

Show additional columns on group/instance sec dash

See merge request gitlab-org/gitlab!41829

- show identifier column
- show scanner column
- update tests
- update docs

Update cache to be immutable

See merge request gitlab-org/gitlab!42015

Follow up api bridge endpoint

See merge request gitlab-org/gitlab!36622

Remove issue note from vulnerability details

See merge request gitlab-org/gitlab!40686

Enable advanced search by default for global search scope

See merge request gitlab-org/gitlab!41041

This reverts commit 5c234b63.

Let Gitlab/RailsLogger check only log methods

See merge request gitlab-org/gitlab!41987

Check CSRF token in UsageData API - RUN AS-IF-FOSS

Closes #247454

See merge request gitlab-org/gitlab!41984

Use applogger in some files of auth/ldap dir

See merge request gitlab-org/gitlab!41061

This MR adds AppLogger in auth/ldap files
and adds changelog for
the changes

Change type in changelog

Resolve "Create class for generating user data export file"

See merge request gitlab-org/gitlab!41595

Surface incident Severity in the Incident List

See merge request gitlab-org/gitlab!40112

Fix registry list item vertical spacing

See merge request gitlab-org/gitlab!41780

- source
- snapshots

Refactor code in profiles/emails_controller_spec.rb

See merge request gitlab-org/gitlab!41959

Replace bootstrap alerts with utility classes

Closes #233683

See merge request gitlab-org/gitlab!41974

Expose iteration burnup chart time series through GraphQL

See merge request gitlab-org/gitlab!41666

Add clarify about deploy_boards_kubernetes_label.png screenshot

See merge request gitlab-org/gitlab!41962

The use of e.g. `Rails.logger.level` is fine for historical reasons.

Avoid programmatic checks because they are slower as well.