- Add protected branches to Projet Migration
    when using Group Migration tool in order to
    be able to migrate projects' protected
    branches configurations

Move "Add Namespace" button to GlEmptyState

See merge request gitlab-org/gitlab!73714

Link handbook from deprecation template

See merge request gitlab-org/gitlab!74185

Edit custom issue tracker docs

See merge request gitlab-org/gitlab!74191

File mode changes are not always visible in the merge request diff view

See merge request gitlab-org/gitlab!72937

Add section for permanent experiment implementation concerns

See merge request gitlab-org/gitlab!74106

Clean up vale warnings in yaml ref

See merge request gitlab-org/gitlab!74184

Enable signup before test start

See merge request gitlab-org/gitlab!72234

Add support for NPM package metadata

See merge request gitlab-org/gitlab!73639

Remove deprecated WIP from GraphQL

See merge request gitlab-org/gitlab!73349

Create ProjectNamespace when a Project is created

See merge request gitlab-org/gitlab!70972

Add gl-form-input class for fields in github import page

See merge request gitlab-org/gitlab!58307

Remove startup JS call for issue notes

See merge request gitlab-org/gitlab!74146

Reject multiple PGP signatures for commits

See merge request gitlab-org/gitlab!74095

Add cron for prometheus integration health check

See merge request gitlab-org/gitlab!73884

Enable linear GroupPlanPreloader ancestors queries

See merge request gitlab-org/gitlab!72594

Move database partitioning code from initializers to module for reusing

See merge request gitlab-org/gitlab!74107

Fix inconsistent addresses gmail

See merge request gitlab-org/gitlab!74093

Add Push Rule to Project Migration

See merge request gitlab-org/gitlab!73554

Prepare for CreateRepository starting to fail with existing repos

See merge request gitlab-org/gitlab!72491

Use Pipeline Editor to add new CI file from Suggest Pipeline banner

See merge request gitlab-org/gitlab!73514

Take the user to the Pipeline Editor instead of the File Editor when
they click on the CTA button of the Pipeline Suggest banner.

Changelog: changed

Fix rollout issue url

See merge request gitlab-org/gitlab!74089

Update Gitaly version

See merge request gitlab-org/gitlab!74188

Rename duplicate GQL type name Environment to LocalEnvironment

See merge request gitlab-org/gitlab!74174

Fixes multiple new line suggestions not escaping correctly

See merge request gitlab-org/gitlab!74090

Revise very wordy expiry messages

See merge request gitlab-org/gitlab!73999

E2E: Bump allure report publisher version

See merge request gitlab-org/gitlab!74173

Resolve "SaaS Service Ping Metrics Failures causing null UMAU value"

See merge request gitlab-org/gitlab!73670

Fix CodeReuse/ActiveRecord offenses in workers

See merge request gitlab-org/gitlab!74150

The `#create_if_not_exists` function is supposed to create a repository
if it doesn't exist yet. It may happen though that the existence-cache
may pretend a repo doesn't exist yet even though it does, and in that
case we'd call the CreateRepository RPC. This worked alright until now
given that this RPC call is idempotent and simply reinitializes the repo
in case it exists already. But Gitaly is going to change semantics of
the RPC such that it raises an error if the repo exists already, where
it then won't touch the preexisting repo at all.

Prepare for this change by introducing a new `RepositoryExists` error
which gets raised when `#create_repository` returns an AlreadyExists
error. This error is rescued from in `#create_if_not_exists` such that
semantics of this RPC call remain the same.

When synchronizing repositories, then depending on a retry counter we
may either fetch into the real repository, or recreate the repo by first
creating a temporary staging repository, populating that repository and
then moving it into place. Our tests stub out this logic though such
that we always end up fetching into the real repository: this both keeps
us from exercising whether we fetch into the expected repo, and this
logic will break when Gitaly changes semantics of the CreateRepository
RPC to raise an error if the repository exists already.

Fix this issue by not stubbing out the temporary repository. Instead, we
now assert that function calls end up using the correct repository.

In order to set up snippet repositories in some of our tests, we first
copy over a template repository into the target location and then call
Gitaly's `CreateRepository()`. While this call wouldn't do anything if
used with Gitaly only given that the RPC is idempotent, it would create
a database record when Gitaly is proxied by Praefect.

Gitaly is about to drop idempotentcy of `CreateRepository()`, where it
will instead raise an error. Prepare for this by reversing calls such
that we first create the repository in Gitaly, and then copy over
contents of our seed repository.