Understanding SCM Sensor in GitLab Merge Request (Pull Request)

[MichaelGissing]

Thanks @ganncamp for clarifying!

Regarding the GitLab CI MR pipelines, I found this post by your colleague in the meantime:

Pull Request Analysis in GitLab without using detached pipeline ("only: merge_requests")

Hi, SonarQube reads a bunch of “only: merge_requests” specific environment variables: CI_MERGE_REQUEST_IID (Mandatory to trigger a MR decoration) CI_MERGE_REQUEST_SOURCE_BRANCH_NAME (Mandatory to trigger a MR decoration) CI_MERGE_REQUEST_TARGET_BRANCH_NAME (Optional, will use the main branch as default) CI_MERGE_REQUEST_PROJECT_URL (Required to have the link to the MR from SQ PR view) (+ others environment variable not specific to only: merge_requests) Keep in mind that its internal implemen…

So I guess it does an auto-detection based on the environment and is not irritated by the detached head.

So all should be fine for us, thanks for your assistance.