Backfill GraphQL descriptions

See merge request gitlab-org/gitlab!22199

Remove unused attribute from ActivityService

See merge request gitlab-org/gitlab!22111

the `activity` attribute is not used anymore and
can be removed. This commit also adds a spec
for the happy path of git http info_refs to test
the new attributes on ActivityService

Fix GitLab plugins not working without hooks configured

Closes #194131

See merge request gitlab-org/gitlab!22409

Fix merge request license widget e2e spec flakiness

Closes #118654

See merge request gitlab-org/gitlab!22335

Productivity Analytics: Update URL date params properly

See merge request gitlab-org/gitlab!22419

Update tests to respect html() changes

Closes #191270

See merge request gitlab-org/gitlab!22299

Fix plurality and capitalization in the documentation

See merge request gitlab-org/gitlab!22393

Add documentation & helper text about securing a GitLab installation

See merge request gitlab-org/gitlab!18987

This change adds more prominent documentation
for sign up restrictions.

Add link to Mermaid Live Editor

See merge request gitlab-org/gitlab!22389

Fix typo 'displosal' in merge request doc

See merge request gitlab-org/gitlab!22429

Upgrade json-jwt to v1.11.0

Closes #39148

See merge request gitlab-org/gitlab!22440

Simplify static-analysis count for ignored warnings

See merge request gitlab-org/gitlab!22448

This adds a minor performance optimization to avoid allocation of an
array.

Fix static-analysis failure due to caniuse-lite dependency

Closes #194788

See merge request gitlab-org/gitlab!22447

As seen in https://gitlab.com/gitlab-org/gitlab/-/jobs/394057944,
static-analysis is failing with:

```
Browserslist: caniuse-lite is outdated. Please run next command
`yarn upgrade`
```

The problem may be occurring because browserslist is detecting that
caniuse-list is approximately 6 months old and outputs a warning using
console.warn.

To fix this, we change static-analysis to filter this warning message
when deciding to exit with error code 2. Older GitLab backports
shouldn't fail because we need to upgrade this dependency.

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

This fixes CVE-2019-18848 and brings in a number of minor fixes:
https://github.com/nov/json-jwt/compare/v1.9.4..v1.11.0

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

Update sharing and permissions section

See merge request gitlab-org/gitlab!21954

Include info under Settings > General for each repo

Specify milestone assignment on Security Release MR template

See merge request gitlab-org/gitlab!22430

Plugins documentation: Update examples link

See merge request gitlab-org/gitlab!22421

Loosen Danger requirements for security MRs

See merge request gitlab-org/gitlab!22396

Security MRs in the `gitlab-org/security` group don't require merge
request IDs for changelog entries, nor do they have strict target branch
requirements.

Specifies that a closed milestone can be assigned through a merge
request via quick actions.

Related to https://gitlab.com/gitlab-com/gl-infra/delivery/issues/610

Link merge requests for all non review app deploys

Closes #38000 and #38092

See merge request gitlab-org/gitlab!21254

Fix markdown table border colors

Closes #27884

See merge request gitlab-org/gitlab!22314

Use border color specified in Pajamas for markdown table borders

Fix bug when exposing non existing artifacts

See merge request gitlab-org/gitlab!22378

Fix a misspelling in sync-stable-branch script

See merge request gitlab-org/gitlab!22260

https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/31741, shipped
in GitLab 12.2, reduced Gitaly RPCs by generating commit data only if
hooks or services were actually active. However, GitLab plugins
(https://docs.gitlab.com/ee/administration/plugins.html), are executable
programs that get launched inside `SystemHooksService#execute_hooks`
regardless of whether any hooks are actually active. As a result of this
change, users have to configure a Webhook for plugins to fire.

We restore the previous behavior by checking whether plugins are
available and executing `SystemHooksService#execute_hooks` if any
plugins are available.

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

Gracefully handle CI lint errors in artifacts section

Closes #194069

See merge request gitlab-org/gitlab!22388

This changes how we link merge requests to deployments so that:

1. We link merge requests for any deployment that is not in the
   "created" state.
2. We do not link merge requests to review app deployments.

We want to link deployments regardless of their status so that we can
also show failed and running deploys in the merge request widget (and
perhaps in other places). We don't want to link review app deployments
since this is not useful, and may lead to deployments to different
review app environments showing up on a merge request page.

This builds on the refactoring of the deployment model introduced in
merge request https://gitlab.com/gitlab-org/gitlab/merge_requests/20474,
and moves the linking of merge requests to Deployments::FinishedWorker.
This worker is scheduled every time a deployment transitions to a
finished state.

As part of these changes we also change Deployment#link_merge_requests
so that it ignores any already linked merge requests. This way if a
deployment changes its status multiple times, we don't error with
duplicate key errors.

This fixes https://gitlab.com/gitlab-org/gitlab/issues/38092.

Add Index to help Hashed Storage migration on big instances

Closes #194066

See merge request gitlab-org/gitlab!22391

Use proper find targets in test

Closes #191269

See merge request gitlab-org/gitlab!22298

Wrap requests in an ApplicationContext

See merge request gitlab-org/gitlab!20791

Performance improvements on milestone burndown chart

See merge request gitlab-org/gitlab!22380

Prevent Gitaly N+1 queries in blob search

See merge request gitlab-org/gitlab!21996