Need a way to differentiate between manually triggering pipeline and Merge request events
Coming from here: https://forum.gitlab.com/t/need-a-way-to-differentiate-between-manually-triggering-pipeline-and-merge-request-events/50263
To summarize: I'd like to differentiate between all manual triggers and automatic triggers.
However, the "Run Pipeline"-Button in the Pipelines section behaves differently to the button in the merge requests. As the button there seems to use the Merge Request API (mentioned here: #216012 (closed)) using the button sets the source of the pipeline to be merge_request_event
. This is the same event that is automatically sent by creating/updating a merge request and therefore I cannot disable the creation of a pipeline due to a new merge request and a push for an open merge request while also enabling developers to use the "Run Pipeline"-Button in the merge request.
In my opinion it would make more sense to also set the source for a pipeline like this to web
as with the other button, but of course I have no idea how feasible that is.
If there are workarounds to achieve this, that would also work for me. I already outputted all available environment variables in both use cases and found no difference.
Thank you for your help!