Symlinked hooks aren't executed

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

Ensure we create the secrets at the right time

Closes #53621

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

Add revert to commits API

Closes gitlab-org/release/framework#48

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

Improve Debugging Capabilities For Helm Application Installs

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

User can create a group level cluster and install applications

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

Add e2e test of push via HTTP via Git protocol v2

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

Remove created_at from WikiPage

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

Improve the Review Apps documentation a bit

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

In `deploy`, if the previous deployment failed, we delete/cleanup all
the objects related to the release, including secrets. The problem is
that if we create the root password before that, it will be then
recreated during the deploy with a random value!

By creatigng the secret just before actually deplying a new release, we
ensure that it won't be overriden.
Signed-off-by: Rémy Coutable <remy@rymai.me>

backport: Always proxy reports downloads

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

This recently changed on the Gitaly side, but now spotted this in the
docs for the next release. Updated to be more precise, and to signal
users should not want control over this specific hook location.

Revert "Extract code into IssueBoardEntity"

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

Parameter per_page added

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

Typo fix stoping -> stopping in the CI README.md

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

This reverts commit 8c126525.

Adds a new end-to-end test to check that Git protocol v2 can be used to
push over HTTP

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

Allow to override the gitlab-qa ref for the downstream trigger

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

Previously the string was spanning multiple lines and included a
needless `\n` character in the resulting error message.

This change also reduces duplication by assigning two variables.

Fix broken link

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

Remove duplicate primary button in dashboard snippets

Closes #53706

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

Replaces tooltip directive with gl-tooltip directive

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

Stop multiple discussion requests

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

Limit parallel to 50

Closes #53711

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

Resolve "Follow-up from "Resolve "Redesign activity feed"""

Closes #53640

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

Update license list

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

Update GitLab-Workhorse to 7.1.0

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

Run rake gitlab:update_templates

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

Regenerate Gitaly's config.toml each rspec run

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

This prevents some of the abusive behaviors, of someone putting 100000 and creating out of memory condition easily

However, we only need to raise for project_type clusters to maintain
previous behaviour.

In all probablity this requirement to have actual_namespace came from
KubernetesService and will no longer be required soon.

With multiple discussion requests we loose the reactivity of the
previously stored discussions state.
This means that certain features, toggling line discussions for example,
are no longer reactive.

Use presenters instead otherwise we will have x2 overides in EE