The following discussion from !119637 should be addressed: - [ ] @OmarQunsulGitlab started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119637#note_1388847172): > (not-blocking) As we tend usually to query the database objects using finders, have you considered reusing the [`MergeRequestFinder`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/finders/merge_requests_finder.rb) instead? > You can maybe add a parameter to the finder to use the newly introduced scope `by_sorted_source_branches`, to make it available for other callers. > > I don't want this to block you - [ ] Or https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119637#note_1390938916 > This isn't a blocker, and not quite a nit, but I wonder if this logic would live on `MergeRequests::BaseService` comfortably? We're already doing some [semi-related searches](https://gitlab.com/gitlab-org/gitlab/-/blob/7079db66a73f73a64317460458ce910988ef3c84/app/services/merge_requests/base_service.rb#L227-233) there.. :thinking: ### Proposal Update the code to use `MergeRequestFinder` instead of requesting the list of merge requests from the controller.