Handle cases when authorized_keys doesn't exist

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

Add documentation reference for chatops feature flag commands

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

Add issue template for database reviewer

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

Update merge request widget pipeline block to accommodate post-merge pipelines

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

This commit updates the pipeline block that appears on the merge request
page to include information that will be exposed by the API as part of
the post-merge pipeline feature.

Externalize strings in admin controllers

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

docs: Adds information and links to clarify how to create feature flags

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

Merge branch '59189-long-names-in-project-path-namespace-dropdown-breaks-past-container' into 'master'

Resolve "Long names in project path namespace dropdown breaks past container"

Closes #59189

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

Allow users to create protected branches via CLI

Closes #59289

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

Resolve "Inconsistent hover behavior on navbar items"

Closes #59117

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

Adds A short summary of the steps to create and use feature flags
in development for frontend developers who might be unfamiliar
with `rails` and or `flipper`. Adds links to further reading
in the development guide.

- Update PO file

Resolve "Android template is missing .gitlab-ci.yml"

Closes #59293

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

This is for fixing a regression introduced by:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24969

This fix will allow users who are allowed to push to protected
branches to create protected branches via CLI as well, just
like before. The checks for protected branch creation won't
need to run.

Revert "Enrich commits with full data in CommitCollection"

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

Use the default git clone depth for the review-build-cng job

Closes #59288

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

Update job detail view sidebar to accommodate post-merge pipelines

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

Revert "Merge branch '58805-allow-incomplete-commit-data-to-be-fetched-from-collection' into 'master'"

This reverts merge request !26144

Upgrade Gitaly to v1.29.0

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

Prepare multi-line suggestions for rendering in Markdown

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

Update pipeline list view to accommodate post-merge request pipelines

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

Signed-off-by: Rémy Coutable <remy@rymai.me>

Handle nil name in Gitlab::Auth::LDAP::Person#name

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

Enrich commits with full data in CommitCollection

Closes #58805

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

Update dashboards to additionally use new environment selector

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

Deploy boards now will check for app.gitlab.com/env and
app.gitlab.com/app

Create project-specific Kubernetes resources just-in-time

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

Add option to whitelist _html fields from attributes on CacheMarkdownField

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

Bump httparty to version 1.16.4

Closes #44342

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

Resolve "Use vendored files for CI config"

Closes #57598

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

A project is needed in order to fetch data from gitaly. Projects can be
absent from commits in certain rare situations (like when viewing a MR
of a deleted fork). In these cases, assume that the enriched data is not
needed.

See this comment:

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26144#note_152191106

"It's led to a dilemma about where to "fix" this in code. I'm going
to fix it by allowing CommitCollection#enrich! to just return unenriched
commits when a project is missing, essentially "silently failing". I
hope this is the right decision. It's going with the assumption that
calls in these situations in the future are not needing the full data.
The alternative would be to allow CommitCollection#enrich! to still
error, but handle it in the methods that call #enrich!, however that
might lead to brittleness in future when working with project-less MRs."

* dev/master:
  Update CHANGELOG.md for 11.8.3
  Update CHANGELOG.md for 11.7.7
  Only return `commands_changes` used in frontend

Fix project serialization in quick actions response

Closes #2826

See merge request gitlab/gitlabhq!3001