gitlab-org--gitlab-foss/app/views/shared/_merge_requests.html.haml

- if @merge_requests.to_a.any?
  %ul.content-list.mr-list.issuable-list
    = render partial: 'projects/merge_requests/merge_request', collection: @merge_requests

  = paginate @merge_requests, theme: "gitlab"

- else
  = render 'shared/empty_states/merge_requests'
Save a query on issue and MR lists `any?` on an AR relation performs a `SELECT COUNT`, which we don't need. 1. We are very likely to have issues or MRs, so the `SELECT COUNT` is often unnecessary. 2. Even where there are no items returned, the overhead of the `SELECT *` instead of `SELECT COUNT` is relatively small. Calling `to_a` on the relation lets us use `Enumerable#any?`, which will return immediately if there are objects returned. 2016-11-25 08:41:13 -05:00			`- if @merge_requests.to_a.any?`
Add latest changes from gitlab-org/gitlab@master 2020-11-30 07:09:21 -05:00			`%ul.content-list.mr-list.issuable-list`
			`= render partial: 'projects/merge_requests/merge_request', collection: @merge_requests`
Add "New X" link to dashboard/group milestone project-specific issue/MR panels 2015-12-02 08:00:54 -05:00
Dont set @project variable in list. Remove a bit of duplication in dash and group 2013-01-14 03:09:01 -05:00			`= paginate @merge_requests, theme: "gitlab"`

			`- else`
MR empty state 2017-04-05 08:43:03 -04:00			`= render 'shared/empty_states/merge_requests'`