**Why?**

Previously it managed this as an internal data property, but there
was extra complexity involved because the component doesn't have
all the information it needs (i.e. the `mouseOver` prop).

This is a good opportunity to colocate the data prop with the component
that has the information to change it (i.e. `file_row`) and let
`new_dropdown/index` receive this value as a prop.

**What?**

A Vue warning that `ide_status_bar` sent a `Boolean` to a `String`
property (`img-src).

**What was the fix?**

Previously, `latestPipeline` could be one of the following values:

|          |        |
|----------|--------|
| `null`   | The pipeline hasn't loaded yet |
| `false`  | The pipeline has loaded, but nothing was returned. |
| `Object` | The piepline has loaded. |

Giving a semantic meaning to different falsey values hurts
maintainability. This commit fixes the above problem by removing the
`false` value and introducing a `hasLoadedPipeline` state property.

Consider array params on rendering MR list on dashboard

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

This fixes the bug, when approver filter is provided,
but dashboard asks to enter any filter

Fix an order-dependent spec failure in spec/migrations/schedule_sync_issuables_state_id_spec.rb

Closes #60029

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

Change the way it is checked if the user is last group owner

Closes #38564

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

Chnage method used in model to make it
more efficient database-wise
Add additional spec

Revert "Merge branch 'fix/missing-border' into 'master'"

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

Monitor GraphQL with Prometheus (try 2)

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

Extends graphql's platform tracing class to observe duration
of graphql methods.

In graphql 1.8.11 is added prometheus class but it's not very useful
for us because it uses prometheus_exporter to export results.

Exempt release automation MRs from Danger rules

Closes gitlab-org/release/framework#269

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

Support multi-line suggestions

Closes #53310

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

- added suggestions to mock data
- fixed props to be not required

Backport: Ignore merge if the status of the merge request pipeline is stale

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

Fix webpack dev-server crash caused by 1.5gb limit

Closes #59075

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

Speed up avatar URLs with object storage

Closes #43065

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

Add v2 to reserved top level routes

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

GraphQL Type authorization

Closes #54417

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

Add testing to feature proposal template

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

Filters branch and path labels for metrics

Closes #48090

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

With object storage enabled, calling `#filename` on an upload does this:

1. Call the `#filename` method on the CarrierWave object.
2. Generate the URL for that object.
3. If the uploader isn't public, do so by generating an authenticated
   URL, including signing that request.

That's all correct behaviour, but for the case where we use `#filename`,
it's typically to generate a GitLab URL. That URL doesn't need to be
signed because we do our own auth.

Signing the URLs can be very expensive, especially in batch (say, we
need to get the avatar URLs for 150 users in one request). It's all
unnecessary work. If we used the `RecordsUploads` concern, we have
already recorded a `path` in the database. That `path` is actually
generated from CarrierWave's `#filename` at upload time, so we don't
need to recompute it - we can just use it and strip off the prefix if
it's available.

On a sample users autocomplete URL, at least 10% of the time before this
change went to signing URLs. After this change, we spend no time in URL
signing, and still get the correct results.

Move tag quick action spec to shared example

Closes #59570

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

Extract merge quick action to a shared example

Closes #59570

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

Work around lack of HTML list support in topic

Closes #59338

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

Download a folder from repository

Closes #24704

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

Merge branch '59979-update-documentation-about-only-allow-merge-requests-to-be-merged-if-the-pipeline-succeeds-to-take-into-account-the-settings-page-reorganization' into 'master'

Update "Pipelines must succeed" documentation

Closes #59979

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

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Backport: Use merge request MERGE ref for attached merge request pipelines

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

Add pipeline bridge presenter

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

Prevent premailer from replacing HTML entities

Closes #55964

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

Backport some changes from gitlab-ee!9815

Closes #3314

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

Show backtrace when logging to kubernetes.log

Closes #56768

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

Expose pipeline in the related merge requests

Closes #57662

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

Expose head pipeline for the MR in the api when requesting
related merge requests for an issue and show a detailed
status for the pipeline, which would include:
details_path, favicon, group, icon, label, text, tooltip.

https://gitlab.com/gitlab-org/gitlab-ce/issues/57662#note_152023412