Replace all '9koXpg98eAheJpvBs5tK' occurrences with
'<your_access_token>' in API docs.

Create shared gl-modal-vuex component and module

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

Resolve "Add "Submit feedback" in-product feedback link"

Closes #43623

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

Make RBAC enabled by default for new clusters

Closes #53696

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

Made user_popovers_spec more stable

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

Bring back reverted Gold Trial MR (CE backport)

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

Use cheap operation for `Ci::Pipeline#all_merge_requests`

Closes #54907

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

Add a comment on `Ci::Pipeline#git_ref` about merge request ref

Closes #54908

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

Many changes were also made to tests that expected this to default to
false.

Only validate project visibility when it has changed

Closes #55881

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

Merge branch '49056-configure-auto-devops-deployed-applications-with-secrets-that-aren-t-committed-to-the-repo' into 'master'

Configure Auto DevOps deployed applications with secrets from prefixed CI variables

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

Installation/Update guides for 11.7

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

Remove redundant counts in snippets search

Closes #44353

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

Support new issue creation by email without subaddressing

Closes #29951

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

[CE] Don't run checks for changed refs when specific changes are unknown

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

On GitLab.com, there are hundreds of projects that have visibility
levels that are inconsistent with the fork or group settings. Most
likely, this happened during a GitLab project import because the
validation was bypassed.  Attempting to migrate these projects to hashed
storage fails even though the migration doesn't touch the visibility
settings. Skipping the visibility validation allows the migration to go
through.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55881

Documentation: Make correction to URL, from https://about.gitab.com/handbook/documentation/...

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

**Why?**
It is significantly easier to manage the visibility of the modal in
Vuex. The module contains the state and mutations to manage this.
The component wraps GlModal and syncs the visibility with the module.

Make correction to URL, from https://about.gitab.com/handbook/documentation/ to https://about.gitlab.com/handbook/documentation/ (I searched to see if this is a duplicate of an existing fix, didn't find one)

Update `include` parameter usage description

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

Fix clone URL not showing if protocol is HTTPS

Closes #55896

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

Resolve "Add markdown editing buttons to the file editor"

Closes #27861

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

Add Knative metrics to Prometheus

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

GitLab 11.6.2 fixed the case for HTTP. However, HTTPS still did
not work because the protocol returned to `http_enabled?`
was the actual protocol in use (e.g. `https` instead of `http`).

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55896

We assert that a K8S_SECRET_* variable is ingestible by our Rack
application

Re-use project and cluster resources in Auto DevOps QA

Add hint about adding variables for Auto DevOps application variables
and link to More information

- DRY up setting deploy name

- DRY up application_secret_name

Use --from-env-file with bash process substitution

We still need bash as process substition (`<()`) is not available in sh

ie. fix below quoting issue:

```
kubectl create secret -n project-with-autodevops-900057eb1ce34399-77 \
  generic production-secret \
  '--from-literal=OPTIONAL_MESSAGE=You' can see this secret \
  -o yaml --dry-run
```

With fix, it should be generating:

```
kubectl create secret -n project-with-autodevops-900057eb1ce34399-77 \
  generic production-secret \
  --from-literal 'OPTIONAL_MESSAGE=You can see this secret' \
  -o yaml --dry-run
```

Call via bash -c, instead of assuming bash

The shell is /bin/sh, so we cannot asssume bash. Hence we use `bash -c`

bash is installed for deploy jobs in a prior step

Find any CI variables from `env` which has a prefix. If there are any
such CI variables, strip prefix from variable name then create a generic
Kubernetes secret containing all these CI variables as key-value pairs.

Also, Pass in secretname to application container

The secretname may be present, if nil, the chart does nothing. If
present, the chart will load the key-value pairs from the secret into
the application container. See
https://gitlab.com/charts/auto-deploy-app/blob/master/README.md#configuration

Added Comment to user avatar Image, Changed Fixtures to created ones, added shadow color

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

including verifying the project_slug

We now use `-issue` in order to support catch all email addresses