When the merge pipeline's source is not push, merge pipeline doesn't show on the merge request page

Summary

When a merge pipeline has source as external or not push, then the merge pipeline doesn't show on the merge request page.

Steps to reproduce

  1. Create a project and create a new branch
  2. Make some changes in the branch and create a merge request
  3. Merge into target branch.
  4. Call the commit status API to create a pipeline, update the status to running and successful
  5. When you check the merge request via https://gitlab.example.com/api/v4/projects/:project_id/merge_requests/:mr_id, you will see that pipeline.source is external.
  6. On the Merge Request overview page, merge pipeline doesn't show.

Example Project

What is the current bug behavior?

When the merge pipeline source is anything other than push, merge pipeline doesn't display on MR overview page.

What is the expected correct behavior?

Merge pipeline should show just above the Activity section like this:

Screenshot_2025-08-26_at_15.11.23

Relevant logs and/or screenshots

Merge pipeline does not show:

Screenshot_2025-08-26_at_15.13.35

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

My colleague @j.castillo found that this is due to the filter added in the merge request's merge_pipeline method, introduced in this merge request.

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖