These log messages often pollute structured log streams and do not
provide useful information. We tweak the log level to FATAL to suppress
all output.

https://github.com/snowplow/snowplow-ruby-tracker/pull/109
would make it possible to configure this logger directly.

Closes https://gitlab.com/gitlab-org/gitlab/issues/204755

Remove addMultipleIssues function logic from list model

See merge request gitlab-org/gitlab!21404

Move some board tests to jest

See merge request gitlab-org/gitlab!24365

Resolve "Abstract common fragments to GraphQL shared folder"

Closes #202228

See merge request gitlab-org/gitlab!24580

Record audit event when user is deleted

See merge request gitlab-org/gitlab!24257

Merge branch '197369-group-and-instance-security-dashboards-hit-the-vulnerabilities-summary-endpoint-without' into 'master'

Skip summary endpoint for Group and Instance Security Dashboard

See merge request gitlab-org/gitlab!23757

The Group and Instance Security Dashboards hit the vulnerability
summary endpoint, even though they're not using the data from it

Frontend: Remove confidence from security reports

See merge request gitlab-org/gitlab!24033

Application limit for ES indexed field length

See merge request gitlab-org/gitlab!24345

There is an edge case when the parent `execute` fails and returns a user
with errors. This should be excluded from audit event logging.

When user is the sole owner of the group no explicit delete
options are enabled, the method is expected to return the
attempted delete user with error messages attached.

The test is to ensure we honour this interface and does not
cause unexpected failures from the callers.

Add version badge for Service Desk feature

See merge request gitlab-org/gitlab!24753

Using the plan_limit table we can down store a limit for the maximum
size of any fields being indexed in Elasticsearch. This is for
https://gitlab.com/gitlab-org/gitlab/issues/201826 . Any strings above
the length limit will be truncated down to the limit.

We default to 0 which means unlimited so this has no affect for
self-managed customers. On GitLab.com we will likely want to set this to
around 20k as a sensible upper limit on what we should store.

Add grammar linting tests for Latin phrases in docs

Closes #199110

See merge request gitlab-org/gitlab!23798

Refactor specs for FeatureFlagsController

See merge request gitlab-org/gitlab!24446

Fix cache:key:prefix section documentation format.

See merge request gitlab-org/gitlab!24677

Add intro and link to dev docs for GraphQL

See merge request gitlab-org/gitlab!24750

Remove `destroyed?` check to handle cases where
destroy operation fail and returns `false` instead of
the user object.

Add test to ensure the return interface is honoured.

This method is called to record audit event for entities
other than `User`. There is more refactor effort required
to rectify those usages.

Integration test is also added to extend coverage for both soft
delete (delete user, not contributions) and hard delete (delete
user only).

Add tests to cover all available user actions

Update links to MRs in various projects

See merge request gitlab-org/gitlab!24733

Add context to the ExpiringWorker

See merge request gitlab-org/gitlab!24686

Update dependency @sourcegraph/code-host-integration to v0.0.30

See merge request gitlab-org/gitlab!24683

Inline reconfigure instruction in Praefect docs

See merge request gitlab-org/gitlab!24712

Separate note entities into own class files

See merge request gitlab-org/gitlab!24732

Set timeout for Kubeclient

See merge request gitlab-org/gitlab!23970

Fix hour-dependent spec in error_tracking_shared_context.rb

See merge request gitlab-org/gitlab!24734

The test was failing because the expected format included the leading 0
in "08:01:29 AM UTC" instead of omitting it in "8:01:29 AM UTC".  As
https://ruby-doc.org/stdlib-2.6.5/libdoc/date/rdoc/DateTime.html
mentions, we can omit the leading value by using `%-l` in `strftime`.

Added how pipeline quotas is assigned to projects

See merge request gitlab-org/gitlab!20688