Fix error when creating labels in a new issue in the boards page

Closes #54311

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

Resolve "Extended user centric tooltips: Add missing cases"

Closes #54981

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

Increase consistency of documentation suite with more guidance

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

ActiveRecord::Migration -> ActiveRecord::Migration[5.0] for AddIndexesToCiBuildsAndPipelines

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

Fix Bitbucket Server import only including first 25 pull requests

Closes #55914

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

Remove app/views/shared/issuable/_filter.html.haml

Closes #55670

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

Exit `wait_for_job_to_be_done` as error if the job fails

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

Merge branch '54142-pages-in-project-s-permission-should-be-named-pages-access-control' into 'master'

Resolve "Pages in project's permissions settings should be named Pages access control"

Closes #54142

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

Allow to include another project files

Closes #53903

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

Update common CSS for MR approvals

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

Create shared user-avatar-list component

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

Fixes diff sugestions removing dashes from diff

Closes #55634

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

Fixes if case to render author info in releases

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

This adds `project:, file:, ref:` specification support.

Add help icon next to private email

Closes #29951

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

Support CURD operation for individual asset links in Release API

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

The change to paginate repos in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22825 caused the
paginator to stop after 25 pull requests because the limit was set to 25
if none was defined. To fix this, we should only stop if the limit has
actually been set and use the limit parameter to determine the maximum
number of items to process per page.

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

Add tests for the API and add a couple of tests

Add

revert

revert

Authorize against release not project

Also:

- Slight restructure.
- Some Markdown improvements.

Also fixes spelling, and makes the Markdown style more consistent.

Clarify needed app files for Auto Build to work

Closes #45279

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

Do not use tokens that look like tokens in docs

Closes #38064

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

Remove unnecessary TOC from file

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

Move Settings Operations controller to CE

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

This commit prepares the structure for the upcoming feature error
tracking.

Use BuildMetadata to store build configuration in JSONB form

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

Hide Auto DevOps banner for projects with CI file or CI disabled

Closes #52446

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

Fix multipart attachments not uploading

Closes gitlab-ee#9035

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

Add API Support for Kubernetes integration

Closes #40473

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

Require Knative to be installed only on an RBAC kubernetes cluster

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

Mixing and matching the use of Rack::Request and ActionDispatch::Request
in Rails 5 is bad, particularly if you have middleware that
manipulates or accesses environment variables.

`Gitlab::Middleware::Multipart` attempts to rewrite request parameters
to the proper values (e.g. replacing `data_file` with
`UploadedFile`). It does this by calling `Rack::Request#update_params`,
which essentially updates `env['rack.request.form_hash']`.

By changing to `ActionDispatch::Request`, the Go middleware was causing
the request parameters to be stored inside
`env['action_dispatch.request.request_parameters']`. Later calls to
`Rack::Request#update_params` would not have any effect because it would
attempt to update `env['rack.request.form_has']` instead of
`env['action_dispatch.request.request_parameters']`. As a result, the
controller still saw the old parameters.

Since the Go middleware appears to be using `ActionDispatch::Request`
for authorization methods, we can switch the multipart middleware to
use it too.

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/9035