Illogical behaviour in building merge request

This is a dupe of https://github.com/gitlabhq/gitlabhq/issues/9013. I couldn't find a corresponding issue here on gitlab.com.

Original Issue

Summary: Merging forked repository retrieves build result for fork Steps to reproduce:

  1. Create repository A
  2. Fork repository A into B
  3. Add CI services to A and B
  4. Add some commits to B
  5. Create merge request from B to A

Expected behavior: build status in merge request should relate to CI service binded to A

Observed behavior: build status in merge request relates to CI service binded to B

Last commit SHA1 of my Gitlab: gitlab-ce@bc57ff0ef023db3d07f1adfa6a309fb4a24ed203

Possible fixes: I have some ideas about how to fix it but I want to know if it seems illogical only for me or not.

Edited Jun 23, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading