Trigger based on code insights in custom merge checks

[Martin Kovacik]

This is such a cool feature released before Christmas. I've spend already some time migrating our merge check logic to forge.

In our pipeline we run checks using source code analysis tools and uploading them via code insights. I'm trying to build logic, that would prevent merge in case there is a failed report. 

I realised that when a report is uploaded, the merge check is not re-evaluated. Similar situation is with associated build. When the build is re-run I can't find a way to re-evaluate the merge check automatically. 

Is there a way to intercept these events and trigger merge check code?

[Jeroen De Raedt]

Hi @Martin Kovacik, 

great to hear that you are already enjoying the new Checks feature! 

As it is still in beta, the feature set is still somewhat limited. This is why currently Checks are only triggered through an `on-code-pushed` or `on-merge` trigger.
From the sounds of it, you would want a type of trigger that would fire when reports are uploaded through code-insights? 

As a work around, you could declare your check to listen to the `on-merge` trigger. This Check could then query the uploaded reports and perform your validation upon them. This Check would then only be invoked during the PR merge process. Maybe this could be a valid work around until we build a more appropriate trigger type? 

[Diogo Borges]

A more appropriate option would be to allow any kind of `event` as a trigger for

bitbucket:mergeCheck.

i.e. this: https://developer.atlassian.com/platform/forge/events-reference/bitbucket/#pull-request-events