The section was included on security/raw_limits and on the admin area
settings.

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/48717

Adjust headers in /university

See merge request gitlab-org/gitlab-ce!31702

Update docs style for code blocks

Closes #65373

See merge request gitlab-org/gitlab-ce!31297

Clarify rules for code blocks, including spaces
above and below, and to use tilde when code blocks
contain triple backticks

Fix quarantined spec by waiting for requests

Closes #65329

See merge request gitlab-org/gitlab-ce!31862

Resolve "Web IDE uncommitted files use wrong icon in tree"

Closes #61335

See merge request gitlab-org/gitlab-ce!31560

- Uses vue-test-utils
- More complete coverage with parameterized tests

Document cleanup of feature flag after deploy

See merge request gitlab-org/gitlab-ce!31893

Enable DAG support by default

Closes #65457

See merge request gitlab-org/gitlab-ce!31814

Don't use go mod vendor

See merge request gitlab-org/gitlab-ce!31721

[Backport] Add feature specs for multiple issue boards for groups

See merge request gitlab-org/gitlab-ce!31481

Add feature specs for multiple issue boards for groups

Add key unbinds to DiscussionKeyboardNavigator

See merge request gitlab-org/gitlab-ce!31857

Add a note about the lack of arm64 support

See merge request gitlab-org/gitlab-ce!31887

Document option to set Security Dashboard as default view for groups

See merge request gitlab-org/gitlab-ce!31795

Revert adding productivity analytics docs

See merge request gitlab-org/gitlab-ce!31848

Remove indentation from list

See merge request gitlab-org/gitlab-ce!31885

Docs for DAG based on `needs:`

See merge request gitlab-org/gitlab-ce!31337

This reverts commit d1eddaa98a83400d043678a2239adc4d781b4549

Resolve "Multi selection for delete on registry page"

Closes #24705

See merge request gitlab-org/gitlab-ce!30837

Add nonce to globalEval in shortcuts.js

See merge request gitlab-org/gitlab-ce!31837

Support metrics dashboard query parameters in GFM metrics filter

See merge request gitlab-org/gitlab-ce!31304

https://gitlab.com/gitlab-org/gitlab-ce/issues/62971

Adds support for embedding specific charts from the
metrics dashboard. Expected parameters are dashboard,
title, group, and y_label.

Fix for role span being too 'ballooned'

Closes #65927

See merge request gitlab-org/gitlab-ce!31706

Update dependency @gitlab/svgs to ^1.68.0

See merge request gitlab-org/gitlab-ce!31729

Squash project templates on update

See merge request gitlab-org/gitlab-ce!31592

As per https://gitlab.com/gitlab-org/gitlab-ce/issues/46043, project
templates should be squashed before updating, so that repositories
created from these templates don't include the full history of the
backing repository.

Fix failing N+1 spec in spec/requests/api/discussions_spec.rb

See merge request gitlab-org/gitlab-ce!31865

Migrations for Cycle Analytics backend

See merge request gitlab-org/gitlab-ce!31621

This change lays the foundation for customizable cycle analytics stages.
The main reason for the change is to extract the event definitions to
separate objects (start_event, end_event) so that it could be easily
customized later on.

This test was failing in EE because the API helper `get()` creates a
personal access token each time it's run. We can avoid that by
pre-creating a personal access token and passing it each time.

Only read rebase status from the model

See merge request gitlab-org/gitlab-ce!31847

Prior to 12.1, rebase status was looked up directly from Gitaly. In
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14417 , a DB
column was added to track the status instead. However, we couldn't stop
looking at the gitaly status immediately, since some rebases may been
running across the upgrade.

Now that we're in 12.3, it is safe to remove the direct-to-gitaly
lookup. This also happens to fix a 500 error that is seen when viewing
an MR for a fork where the source project has been removed.

We still look at the Gitaly status in the service, just in case Gitaly
and Sidekiq get out of sync - I assume this is possible, and it's a
relatively cheap check.

Since we atomically check and set `merge_requests.rebase_jid`, we
should never enqueue two `RebaseWorker` jobs in parallel.

Removes db/fixtures from database files

See merge request gitlab-org/gitlab-ce!31635