<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=24885) </details> <!--IssueSummary end--> ### Problem to solve Spotted in gitlab-ce!22292 : - [ ] @nick.thomas started a [discussion](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22292#note_110696642): (+3 comments) > Should we add this to the graphql api at the same time to avoid having it fall further behind? ### Further details The `merge_pipeline` is not in the API. We do give out the `merge_commit_sha`, so I think it would be useful to add this attribute too. ### Proposal We should add it to both graphql and rest APIs at the same time. ### What does success look like, and how can we measure that? Able to get the merge pipeline for a merge request from the API ### Links / references /cc @nolith