Use PARENT_PIPELINE_MERGE_REQUEST_REF_PATH to clone projects to accommodate MRs created from fork (!98) · Merge requests · GitLab.org / Developer Experience / Component Performance Testing

This MR uses PARENT_PIPELINE_MERGE_REQUEST_REF_PATH which is essentially CI_MERGE_REQUEST_REF_PATH that is passed from parent pipeline upstream.

This is used for MRs as when the MR is created from a community fork or renovate fork, using the branch throws errors. e.g. https://gitlab.com/gitlab-org/quality/component-performance-testing/-/jobs/11598297424#L1047

Using CI_MERGE_REQUEST_REF_PATH will fix this and also work for normal MRs which are from the same repository.

Corresponding MR in GitLab repo : gitlab-org/gitlab!208708 (merged) which needs to be merged first before this is merged.

Related to #108

Edited Oct 16, 2025 by Vishal Patel

Use PARENT_PIPELINE_MERGE_REQUEST_REF_PATH to clone projects to accommodate MRs created from fork