https://gitlab.com/gitlab-org/gitlab/-/issues/217392

Add deploy keys to protected branches (DB and API)

See merge request gitlab-org/gitlab!34875

GraphQL docs - lowercase iteration's `include_ancestors` description

See merge request gitlab-org/gitlab!36870

Expose blob mode in GraphQL for repository files

See merge request gitlab-org/gitlab!36488

Add 'Code Owners' section to CODEOWNERS

See merge request gitlab-org/gitlab!36887

Add scanned_resources CSV path to Security Report Summary

See merge request gitlab-org/gitlab!36810

Merge branch '220573-frontend-modify-secure-configuration-page-to-provide-entry-point-to-sast-config-ui-page-2' into 'master'

Add button to Security Configuration to enable SAST scanning

See merge request gitlab-org/gitlab!36432

This adds a button to the Security Configuration page, allowing the user
to enable SAST scanning via a merge request with a simple click. This
button is only displayed when:

1. The sast_configuration_by_click feature flag is enabled.
1. The project does not have an existing .gitlab-ci.yml file.

Some other changes include (and are _not_ behind any feature flag):

 -  Add third status text string for when Auto DevOps is enabled.
 -  Add third column headed "Manage" to the Security Configuration
    table, which contains a link to that scanner's documentation. This
    is where the button appears in the SAST case when the
    sast_configuration_by_click feature flag is enabled.
 -  Extract thClass constant in app component.
 -  Do not guard the SASTConfigurationController#create action behind
    the sast_configuration_ui feature flag. This feature flag is
    intended for a future iteration when an actual configuration UI
    exists for SAST, which is what that controller is actually for. In
    this iteration, it's simply a placeholder for the temporary REST
    endpoint, which will be [replaced][gql] by a GraphQL mutation in
    another iteration.

This is an MVC for creating a [Configuration UI for SAST][1]. Some
technical debt has been incurred here:

1. The REST (POST) endpoint used to create the merge request will be
   replaced by a [GraphQL mutation][gql].
1. The `type` of each feature has been added to the security
   configuration features exposed to the fronted. This should be
   [replaced][type] by a field exposing the scanner's configuration UI
   path (or similar).
1. The CreateMergeRequestButton component will likely be removed in the
   next iteration of the SAST Configuration UI, particularly if the
   GraphQL mutation is ready by then.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/220573, part of
[Configuration UI for SAST][1].

[1]: https://gitlab.com/groups/gitlab-org/-/epics/3262
[gql]: https://gitlab.com/gitlab-org/gitlab/-/issues/227465
[type]: https://gitlab.com/gitlab-org/gitlab/-/issues/227575

Clarify changelog docs for feature flags

See merge request gitlab-org/gitlab!36276

Update $gray-900 to match gitlab-ui palette

Closes #228727

See merge request gitlab-org/gitlab!36778

Removing unused symbol folder

See merge request gitlab-org/gitlab!36858

Test report link fix

See merge request gitlab-org/gitlab!36220

Rename snippet_files to snippet_actions in snippet services

See merge request gitlab-org/gitlab!36841

Add confidential to graphQL for notes creation

See merge request gitlab-org/gitlab!36799

Add a rule to detect improper alert boxes

See merge request gitlab-org/gitlab!36788

Find and replace all note alert boxes and fix
the colon usage.

Create GitLab issues from PagerDuty webhook payload (Part 1)

See merge request gitlab-org/gitlab!36489

Replace append-right-10 class

See merge request gitlab-org/gitlab!36373

Remove an obsolete TODO comment

See merge request gitlab-org/gitlab!36696

Update to Grape v1.4.0

See merge request gitlab-org/gitlab!36628

Grape v1.4.0 fixes a memory leak that was present in v1.3.3
(https://github.com/ruby-grape/grape/pull/2084).

Full list of changes:

* https://github.com/ruby-grape/grape/blob/master/CHANGELOG.md
* https://github.com/ruby-grape/grape/compare/v1.3.3..v1.4.0

Geo - Make Registry tables as SSOT for Designs

Closes #212720

See merge request gitlab-org/gitlab!36587

Include Elasticsearch query params in Performance Bar

See merge request gitlab-org/gitlab!36899

Check whether PagerDuty setting is active when
creating incident issue

Extract
`Gitlab::IncidentManagement::PagerDuty::IncidentIssueDescription`
from
`IncidentManagement::PagerDuty::CreateIncidentIssueService`

Replace fa-play icon with GitLab SVG play

See merge request gitlab-org/gitlab!36379

- remove css on fa-play class
- replace two fa-play instances

Update metrics dashboard base path

See merge request gitlab-org/gitlab!36749

Replace loading state with an icon, show dashboard skeleton earlier

See merge request gitlab-org/gitlab!36399

Prevent 2nd Elasticsearch query for project searches

See merge request gitlab-org/gitlab!36672