Split workflow.md into a new feature workflow page vs other improvement
workflow page because the original page was too long and using 4 heading
levels. Left it in place as an index so we have a single workflow
landing page.

Prevent admins from attempting hashed storage migration on read only DB

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

CE: Document the "Abuse reports" feature

Closes #45552

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

Update yaml/README.md to clarify allow_failure interaction with stages

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

Add FakeApplicationSettings#commit_email_hostname

Closes #54953

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

Refactor BroadcastMessage to use Gitlab::JsonCache

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

Make Projects::DeployKeysController EE-ready

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

Kudos to @eread for feedback!

Make LfsRequest EE-compatible

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

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

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

ActiveRecord::Migration -> ActiveRecord::Migration[5.0] for ImportCommonMetricsNginxVts

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

Update danger for documentation

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

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

Leave object pools when destroying projects

Closes gitaly#1415

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

This action doesn't lean on reduplication, so a short call can me made
to the Gitaly server to have the object pool remove its remote to the
project pending deletion.
https://gitlab.com/gitlab-org/gitaly/blob/f6cd55357/internal/git/objectpool/link.go#L58

When an object pool doesn't have members, this would invalidate the need
for a pool. So when a project leaves the pool, the pool will be
destroyed on the background.

Fixes: https://gitlab.com/gitlab-org/gitaly/issues/1415