With Whisperfish, we're using merge trains and merged result tests. Instead of running the commit of a merge request on its own, Gitlab makes a merge commit with the target branch, then runs the CI on that.
This results in job events that cannot be correlated to the commits, and as such the very cool reaction bubbles don't appear for merge requests. They still appear for master branch commits.
If I can give you any information to help, I'd gladly supply it. Feel free to come say hi in #whisperfish:rubdos.be . That channel uses the t2bot.io instance and the unfiltered Gitlab group runner on https://gitlab.com/whisperfish (mainly the whisperfish repo)
Log:
[2022-04-09 19:11:02,073] [TRACE@maubot.instance.gitlab] Accepted processing of Merge Request Hook
[2022-04-09 19:11:02,073] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,904] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,905] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,906] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,914] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,914] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,915] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,926] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,927] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,928] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,931] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,931] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.0s"
[2022-04-09 19:11:03,932] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,939] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,939] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.0s"
[2022-04-09 19:11:03,940] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,942] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,943] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,944] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,946] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,947] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.0s"
[2022-04-09 19:11:03,947] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,950] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,950] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,951] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,952] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,952] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,954] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,956] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,957] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.002s"
[2022-04-09 19:11:03,958] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
[2022-04-09 19:11:03,961] [TRACE@maubot.instance.gitlab] Accepted processing of Job Hook
[2022-04-09 19:11:03,961] [INFO@aiohttp.access] 127.0.0.1 "POST /_matrix/maubot/plugin/gitlab/webhooks 202 199 in 0.001s"
[2022-04-09 19:11:03,963] [DEBUG@maubot.instance.gitlab] No message found to react to push push-13453292-1d7ac8a7fe32ec10a77a072cc8e6576a5466034b-refs/merge-requests/246/merge
With Whisperfish, we're using merge trains and merged result tests. Instead of running the commit of a merge request on its own, Gitlab makes a merge commit with the target branch, then runs the CI on that.
This results in job events that cannot be correlated to the commits, and as such the very cool reaction bubbles don't appear for merge requests. They still appear for master branch commits.
If I can give you any information to help, I'd gladly supply it. Feel free to come say hi in #whisperfish:rubdos.be . That channel uses the t2bot.io instance and the unfiltered Gitlab group runner on https://gitlab.com/whisperfish (mainly the whisperfish repo)
Log: