Fetch project capacity and usage items for all types of storage

See merge request gitlab-org/gitlab!68741

Click on 1st button in cluster health dashboard spec

See merge request gitlab-org/gitlab!68722

Fix old occurrences of QA::Support::Api

See merge request gitlab-org/gitlab!68992

Enable `assumeImmutableResults` in project merge options

See merge request gitlab-org/gitlab!69066

Update CI/CD index and get started pages

See merge request gitlab-org/gitlab!69046

Use Gitlab::Ci::Lint in /ci/lint API endpoint

See merge request gitlab-org/gitlab!68860

Update Gitaly version

See merge request gitlab-org/gitlab!69074

Remove scannerType argument from Mutations::Vulnerabilities::Create

See merge request gitlab-org/gitlab!68951

Refactor push rules to allow for bulk checks

See merge request gitlab-org/gitlab!68836

Update network policy request

See merge request gitlab-org/gitlab!68990

Move "Allow users to request access" setting to a new subsection "Membership"

See merge request gitlab-org/gitlab!68544

Enable the FF ci_idempotent_pipeline_process_worker by default

See merge request gitlab-org/gitlab!69068

Translate "by <AVATAR LINK>" in Environments

See merge request gitlab-org/gitlab!69009

Update Gitaly version

See merge request gitlab-org/gitlab!69070

Update GitLab Shell to v13.21.0

See merge request gitlab-org/gitlab!68985

The FileSizeCheck push rule loads all new blobs for a given change and
checks whether any of these blobs is bigger than a certain threshold.
This push rule is quite expensive: loading new blobs requires a revwalk
of all preexisting references and thus scales with the number of refs in
a repository. This may easily take a few dozen seconds to compute, and
repeating this computation for each change doesn't help either.

Refactor the FileSizeCheck to be implemented atop the BaseBulkChecker
such that we can fix this shortcoming in the future: instead of loading
blobs for each change, we may load them once for all changes. While this
would already amortize the costs because we have to perform the walk of
negative refs once only, we can eventually tweak this even further and
use the quarantine directory to enumerate all pushed objects directly
without doing a revwalk at all. This optimization will bring down the
time to load blobs from dozens of seconds to a few milliseconds.

Note that this commit doesn't yet change behaviour, but instead only
prepares the infrastructure to allow for batch loading. Batch loading
will require some additional changes to our infrastructure first, which
will be done in a separate patch series.

Deny access for repository coverage info for guests

See merge request gitlab-org/gitlab!68947

It's already enabled on GitLabcom

This commit solves https://gitlab.com/gitlab-org/gitlab/-/issues/338568
It enables `assumeImmutableResults` in the project merge options.

Add personalization questions to New Group page

See merge request gitlab-org/gitlab!67249

Repository coverage information should be accessible
for Reporter+ role only

Changelog: security
EE: true

Update db:migrate-from-previous-major-version

See merge request gitlab-org/gitlab!68754

Migrate browser_spec to Jest

See merge request gitlab-org/gitlab!69011

Fix linked pipelines downstream counter badge link [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!68962

Add a cleanup job for docs review apps

See merge request gitlab-org/gitlab!68718

Update the broken merge-request-types link on Dangerfile

See merge request gitlab-org/gitlab!69057

The PushRuleChecks are implemented as BaseSingleChecker, where they
always operate on a single change only. This is inefficient for a subset
of push rules, most namely for the file size rules: we could load all
blobs via a single RPC call and inspect their sizes instead of doing an
RPC call per change.

Prepare for this change by converting the PushRules to be implemented as
BaseBulkChecker. For now, nothing really changes: we just deconstruct
the bulk changes into SingleChangeAccesses and then pass those into our
subrules. But with this change in place, we can easily convert subsets
of our push rules to use batching.

There is only a single callsite right now which extracts changes from a
ChangesAccess and converts them into SingleChangeAccesses, which is
inside the ChangesAccess class itself. We're about to convert push rules
such that they can both drive single and bulk push rules, and there
we'll need the same functionality.

Extract the code into a standalone `#single_change_accesses()` function
which can be used to do the conversion.

Use dynamic mapping in trigger to sync `integrations.type_new`

See merge request gitlab-org/gitlab!68558

Database work to support inherited templates on service desk

See merge request gitlab-org/gitlab!67546

Push rules are only available in the Enterprise Edition and are thus
mixed into the BaseSingleChecker via a separate EE module which extends
the base class. This only makes push rules available for this single
checks: bulk checks ain't got any access to them, and until now they
haven't needed any either. We're about to refactor push rules to allow
batching of access checks though, so we need access to push rules in
both classes.

Move the push rule implementation into the BaseChecker class. This is
the parent class of both BaseSingleChecker and BaseBulkChecker, so it
will make the function available to both.

Log backtrace when SAVEPOINT is discovered

See merge request gitlab-org/gitlab!69023

Add missing slash to CODEOWNERS to catch directory

See merge request gitlab-org/gitlab!69050