Apparently disabling it by checking for a variable doesn't actually
disable it.

[ci skip]

Fix list that doesn't render properly

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

Setup Jest test environment

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

fix: update the link to the new address.

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

Merge request pipelines

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

Don't request changelog for MR with 'meta' label

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

Extract code into IssueBoardEntity / serializer (follow up)

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

Add example email on push notification to docs

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

Namely the `ci-build` and `meta` labels.
Signed-off-by: Rémy Coutable <remy@rymai.me>

Adjust divider margin to comply with design specs

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

Use a 32-byte version of db_key_base for web hooks

Closes #53659

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

This reverts commit b53ebd93

Update K8s project namespace and ServiceAccount if exist

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

This reverts commit ac5c20bd

Allow review app smoke test to fail for now

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

Make KUBECONFIG nil if KUBE_TOKEN is nil

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

Fixed diff files not expanding

Closes #54868

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

This reverts commit 22954f22

Geo: Backport of EE MR Geo: Fix push to secondary over SSH for LFS

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

For CE, #lfs_http_url_to_repo calls #http_url_to_repo where as for EE we
examine for a Geo setup so we can support push to secondary for LFS.

Added specs for #deploy_key_pushable?() and #type()

LfsToken::HMACToken#token_valid?() will be examined and if false, look
in redis via LfsToken::LegacyRedisDeviseToken#token_valid?().

Docs - Fix repository submodule API example

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

Upgrade GitLab Workhorse to v7.4.0

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

AES-256-GCM cipher mode requires a key that is exactly 32 bytes long.
We already handle the case when the key is too long, by truncating, but
the key can also be too short in some installations. Switching to a key
that is always exactly the right length (by virtue of right-padding
ASCII 0 characters) allows encryption to proceed, without breaking
backward compatibility.

When the key is too short, encryption fails with an `ArgumentError`,
causing the web hooks functionality to be unusable. As a result, zero
rows can exist with values encrypted with the too-short key.

When the key is too long, it is silently truncated. In this case, the
key is unchanged, so values encrypted with the new too-long key will
still be successfully decrypted.

Forward gitlab-svg

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

[QA] Add a log-out step and expectation to `qa/qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb`

Closes #52700

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

This reflects how we now create or update

Fixed typo in bitbucket import

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

[CE] Backport GroupSAML unlink changes

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

Remove pronunciation tip for knative

Closes #54724

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