I might have figured out at least some workaround that will allow to get the MR tested from a new unverified contributor:
-
Setup “pipelines for merge requests”
-
Add the new contributor as a “Developer” to the parent project. This allows “piplines for merge requests” to run (they run in the parent project).
-
Ensure a specific runner (on our own hardware) is registered at the parent project and is up and running.
When this is done, the pipelines will run. Conclusions: you have to give the new contributor merge rights in order to run the pipeline. Unfortunate, but that seems to be the only option right now.
Suggestion: Allow to run the pipeline for merge requests manually from the parent project, even for unverified contributors, without giving the new contributor merge rights (yet).