Skip to content

[Version-unspecific] .gitlab-ci.yml "thorchain/thornode" -> $CI_MERGE_REQUEST_PROJECT_PATH

Multipartite requested to merge Multi/fork-job-own-repo-check into develop

[Version-unspecific]

I noticed that when the fork job runs instead of a pipeline it checks the MR project's ID for passed pipelines,
but when it's deciding whether to run the fork job it doesn't check whether the source branch is in the MR project,
but rather checks whether the source branch is in the hardcoded "thorchain/thornode".

Though not directly relevant to the main THORNode repository,
this difference means that anything with a merge request format in a forked repository
needs to have a pipeline manually run every time the merge request's branch is updated,
to check whether it passes.

$CI_MERGE_REQUEST_PROJECT_PATH and $CI_MERGE_REQUEST_SOURCE_PROJECT_PATH are both described here:
https://docs.gitlab.com/ee/ci/variables/predefined_variables.html#predefined-variables-for-merge-request-pipelines

My thanks to @AsmundTHORSec for having checked that this works as intended. 🙏
I add in a separate commit the same update for the build-events job.

Merge request reports