Currently, we do not cap amount of tests returned to frontend,
thus in some extreme cases we can see a MBs of data stored in Redis.

This adds an upper limit of 100 tests per-suite.

We will continue showing the total counters correctly,
but we will limit amount of tests that will be presented.

Add @pslaughter to CODEOWNERS

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

Step 2 of #62214: Includes logic to update namespaces storage statistics

Closes #62214

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

- Add two new ActiveRecord models:
  - RootNamespaceStoragestatistics will persist root namespace statistics
  - NamespaceAggregationSchedule will save information when a new update
to the namespace statistics needs to be scheduled
- Inject into UpdateProjectStatistics concern a new callback that will
call an async job to insert a new row onto NamespaceAggregationSchedule
table
- When a new row is inserted a new job is scheduled. This job will
update call an specific service to update the statistics and after that
it will delete thee aggregated scheduled row
- The RefresherServices makes heavy use of arel to build composable
queries to update Namespace::RootStorageStatistics attributes.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows

Squash old migrations

Closes #59177

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

Merge branch '45104-special-characters-in-project-name-path-prevent-users-from-using-the-container-registry' into 'master'

Resolve "Special characters in project name/path prevent users from using the container registry"

Closes #62770 and #45104

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

Includes changes to the Vue container registry component to support
the display of an empty message and error message when invalid
characters are found in the group, project or branch name.

repositories/index.html.haml has been changed to remove the content
and place into Vue component.

Feature/uninstall cluster ingress

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

- JupyterHub must not be available (installed or updated)

Disable juint reports tmp

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

Resolve "Cannot delete and upload file of the same name in the Web IDE"

Closes #60859

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

If an entry has been removed from the tree and later, during the same
session, a user is trying to add a new item with the same name/path we
should allow for that as long as the original entry is marked with
`deleted`.

Removes EE differences for app/views/admin/services/_form.html.haml

Closes gitlab-ee#12532

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

Add a memory cache local to the thread to reduce Redis load

Closes #63977

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

The junit reports are creating 90mb files inside of redis for
`gitlab-ce/ee` project. There is an ongoing production incident
https://gitlab.com/gitlab-com/gl-infra/production/issues/928 that is
because of high CPU uitlaization on the redis nodes. GitLab-ce/ee are
the highest consumers of memory becuase of these junit reports.

This is a bandage until we can scale redis properly.

Don't show image diff note on text file

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

Clarify 10k architecture resource per node

Closes #63424

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

Fix most bare URLs in project

Closes gitlab-com/gitlab-docs#287

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

Linting rule not enabled for now
because tooling produces false
positives.

Docs: update global nav document

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

On the assumption that a background migration whose specs need a schema
older than 2018 is obsoleted by this migration squash, we can remove
both specs and code for those that fail to run in CI as a result of the
schema at that date no longer existing.

This is true for all but the MigrateStageStatus background migration,
which is also used from the MigrateBuildStage background migration.

Since the migrations are gone, we don't need these specs either

Use the `squasher` gem to squash migrations older than the start of 2018

Memoizing root_ancestor in Namespace

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

The root_ancestor method is heavily used in EE for the group_saml
feature. Having this memoization implemented in CE would eliminate
the need of overriding the root_ancestor method in EE.

Tidy spec for API::ProjectClusters

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

QA: transfer project spec

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

Hid re-named entries in subfolders

Closes #63984

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

The introduction of the in-memory cache for application settings had a
side effect of making it harder to invalidate changes when the settings
occur. We now bypass the cache because it's possible the admin enabled
the usage ping, and we don't want to annoy the user again if they
already set the value.

To avoid causing significant load on the system, we add an extra check
to ensure the user is an admin. and we don't want to annoy the user
again if they already set the value. This is a bit of hack, but the
alternative would be to put in a more complex cache invalidation
step. Since this call only gets called in the uncommon situation where
the user is an admin and the only user in the instance, this shouldn't
cause too much load on the system.

Add ClusterRole step to external Knative docs

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

This reverts commit 092542d2fa5c036e4fc01ba3185f1dc0e9ddbebb.

Included a stray file

The /admin panel will now always return an uncached
application setting to ensure it always has the most
current info.