Excessive number of pipelines in SELECT statement while loading a merge request

In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28436, I see this giant SELECT:

image

image

This merge request merged a few thousand commits from master, which is probably why there's so many commit SHAs in that SELECT statement. Still seems unnecessary.

Edited Sep 25, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading