Docs: add "GitLabbers" to Vale substitutions list

See merge request gitlab-org/gitlab!49540

Added more field types for merge request widget

See merge request gitlab-org/gitlab!48773

Add a cop that enforces no capitalization on expectations

See merge request gitlab-org/gitlab!49513

Remove FF ci_root_ancestor_for_pipeline_family

See merge request gitlab-org/gitlab!49240

Eliminate N+1 performance issues in MergeRequest.pipelines

See merge request gitlab-org/gitlab!47784

Expose normalizedTargetUrl on DastSiteValidation

See merge request gitlab-org/gitlab!49541

Fix future tense issues

See merge request gitlab-org/gitlab!49566

Clarify adding SSH key to local GitLab instance

See merge request gitlab-org/gitlab!49595

Prepare GraphQL resolvers for authorization framework changes

See merge request gitlab-org/gitlab!48993

Fix avatar size in profile activity

See merge request gitlab-org/gitlab!49047

Remove the `pull_mirror_branch_prefix` feature flag

See merge request gitlab-org/gitlab!49340

Put new call behind feature flag

See merge request gitlab-org/gitlab!49585

User Timing API documentation

See merge request gitlab-org/gitlab!47777

- Change future tense to present
- Use "for example" instead of "e.g." and "and so on" instead of "etc"
- Keep sentences at 25 words or shorter
- Fix list indentation

SSH does not work with personal access tokens

See merge request gitlab-org/gitlab!49363

The SSH mode of access purely relies on the key material being exchanged
during the SSH protocol, and does not perform lookups of passwords or
personal access tokens

The doc page is correct in that the tokens can be used in place of
passwords for basic HTTP(S) authentication, but they cannot be used as
passwords during SSH operations performed through Git

Fix cURL examples that need double quotes

See merge request gitlab-org/gitlab!49545

Remove ignore statement for namespace_storage_size_limit

See merge request gitlab-org/gitlab!47385

Move GitOps page into development docs

See merge request gitlab-org/gitlab!49262

Move the first half of the GitOps page from an external repository
to the development documentation. The second half of the page
discusses an architectural implementation that doesn't yet exist,
so I didn't add it.

Add resolver types to registry resolvers

See merge request gitlab-org/gitlab!47584

Docs: Deploy boards are now in Core

See merge request gitlab-org/gitlab!31956

Fix N+1 queries loading milestones when exporting CSVs

See merge request gitlab-org/gitlab!49429

Use a separate commit for formatting changes

See merge request gitlab-org/gitlab!49052

Use test detection based on crystalball mapping in rspec jobs (take 3)

See merge request gitlab-org/gitlab!49446

Update Gitaly version

See merge request gitlab-org/gitlab!49552

Merge branch '280589-set-vulnerabilities-as-dismissed-when-they-have-dismissed-feedback' into 'master'

Set vulnerability as dismissed when there is dismissal feedback

See merge request gitlab-org/gitlab!48795

This change adds background migration to fix problem with
vulnerabilities that are not dismissed, when they have dismissal
feedback created for associated findings.

Replace fa-tag with label SVG

See merge request gitlab-org/gitlab!49573

Add iteration_id column to lists

See merge request gitlab-org/gitlab!48103

Remove references to cross_project_pipeline source

See merge request gitlab-org/gitlab!49579

Add artifacts dropdown to security MR widget

See merge request gitlab-org/gitlab!48769

This implements the report artifacts download dropdown on the Core
security MR widget, for
https://gitlab.com/gitlab-org/gitlab/-/issues/249544.

This is implemented behind the `core_security_mr_widget_downloads`
feature flag, whose rollout is tracked by
https://gitlab.com/gitlab-org/gitlab/-/issues/273418.

When the Static Site Editor generates markdown from
the WYSIWYG editor, it does it following formatting
preferences that may be different from the original
preferences in the edited file

As a result, when the user creates a merge request
with the Static Site Editor, the merge request contains
many changes that result from generating markdown
with different formatting preferences. For example
the file may use a different syntax to set text as
bold from the one used in the editor

This change moves those formatting changes to a
separate commit