These actions/endpoints are not under code review feature category.

They're are under the following categories:
- `code_testing`
- `usability_testing`
- `continuous_integration`

Add new project sidebar panel

See merge request gitlab-org/gitlab!58854

Make blobs directly accessible through the graphql repository

See merge request gitlab-org/gitlab!58677

Expose timelogs against issues and merge requests in graphql

See merge request gitlab-org/gitlab!57321

Remove mock data from DAST Site Profiles

See merge request gitlab-org/gitlab!58735

Fix RSpec/EmptyLineAfterFinalLetItBe for ee/spec/services/merge_trains

See merge request gitlab-org/gitlab!58333

Fix EmptyLineAfterFinalLetItBe offenses in spec/lib/gitlab/hook_data

See merge request gitlab-org/gitlab!58262

Fix N+1 queries to find or initialize services

See merge request gitlab-org/gitlab!58879

Fix EmptyLineAfterFinalLetItBe offenses in spec/services/ide

See merge request gitlab-org/gitlab!58424

Fix timeout error when loading pipelines by commit SHA for GraphQL

See merge request gitlab-org/gitlab!59110

Use object quarantine directory to enumerate new LFS pointers [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!58634

Fix EmptyLineAfterFinalLetItBe offenses in spec/services/merge_requests

See merge request gitlab-org/gitlab!58429

Include context in spec time tracking

See merge request gitlab-org/gitlab!58980

Fix cop offenses for Style/HashTransformation in spec directory

See merge request gitlab-org/gitlab!56586

Fix cop offenses for Style/HashTransformation in ee directory

See merge request gitlab-org/gitlab!56581

Add Billable Memberships API

See merge request gitlab-org/gitlab!58506

Set version when externally installed

See merge request gitlab-org/gitlab!58852

It was loading all the pipelines for a given project and tried to match
them from with the requested one from Ruby. This was causing database
statement timeouts for projects with lots of pipelines.

Fix RSpec/EmptyLineAfterFinalLetItBe for ee/spec/features/admin

See merge request gitlab-org/gitlab!58403

Add instructions about running pipeline schedules through rails console

See merge request gitlab-org/gitlab!58978

When accepting pushes, we will check whether pushes contain any new LFS
pointers and, if so, verify that we've got the corresponding LFS object
for each of the poniters in order to ensure consistency. Determining new
LFS pointers is expensive though: we need to perform a complete graph
walk in order to determine which blobs are new and which aren't. The
integrity check's runtime thus scales with repository size and is
frequently seen to take multiple seconds or even time out after 30
seconds. Results are that the push seems to be hanging for quite some
time doing nothing, or that the push is refused altogether in the case
of a timeout.

We can do better though: instead of doing a graph walk, we can just
inspect all pushed objects directly by enumerating all pushed objects.
This is quite trivial to do: when git-receive-pack(1) receives a push,
all pushed objects will be put into a quarantine directory which is then
made available to git hooks via the GIT_OBJECT_DIRECTORY variable, where
the real repository is stored in GIT_ALTERNATIVE_OBJECT_DIRECTORIES.
Instead of doing the graph walk, we can just use git-cat-file(1) with
the `--batch-all-objects` flag and the alternate object directories
unset. The result is a direct enumeration of all pushed objects, which
scales linearly with push size and not with repository size. Doing some
benchmarks for gitlab-org/gitlab showed that these computations are
around 100-200x faster than doing the graph walk, reducing the time from
around 200ms to 2-4ms.

This functionality has recently been implemented in Gitaly via the new
`ListAllLFSPointers()` RPC: given a repository, it will simply list all
reachable or unreachable objects. We can now use above semantics when a
pre-receive hook environment is active and strip the repository's
alternative object directory, which will as a result only list newly
pushed objects.

Move to btn-confirm from btn-success in push_rules directory

See merge request gitlab-org/gitlab!58033

Gitaly has recently introduced two new RPCs `ListLFSPointers` and
`ListAllLFSPointers` which are slated to replace the current RPCs
`GetLFSPointers`, `GetNewLFSPointers` and `GetAllLFSPointers`.

As a preparatory step to make use of the replacements, this commit
updates the Gitaly Gem to v13.11.0.pre.rc1.

Update Gitaly version

See merge request gitlab-org/gitlab!59103

Clean up manual variables form spec

See merge request gitlab-org/gitlab!58493

Add an E2E test of PostReceive idempotency

See merge request gitlab-org/gitlab!57927

In this commit we start the refactor of the project sidebar.

Instead of the current approach with all the logic in views and helpers,
we're moving to a model based structure where each menu model contains
its logic, visibility access levels, and all the necessary info.

Nevertheless, the migration is tricky because we cannot just replace
the whole sidebar (that would be a 130 files MR). In order to
make it incremental we still render the old views. Then, when we
add a new menu to the new structure we'll remove that menu
from the menu, until we migrate all menus and we can remove the view
entirely.

Resolve N+1 query issue for scanners in StoreSecurityReportsWorker [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!57426