I would love to be able to set different sets of checks that need to pass to add a PR to a merge group, and to the merge group itself to be merged, so we can better manage speed and cost.
In a GitHub Action, this is was very easy:
on:
pull_request:
merge_group:
jobs:
build:
name: Whatever...
if: github.event_name == 'merge_group'
The docs say there's a separate event for merge_group which I assume means you can configure different checks.
https://docs.github.com/en/repositories/configuring-branches...
Actually getting to that point can be quite hard. But it's definitely possible. But also, if there's any change then you want to re-run anything that depends on the change. Limiting the rebuild to only things that have changed also take effort. But it's really worth it for the benefits you reap, both in CI and in development -- if your edit-compile-test cycle is long enough that an extra CI run is annoying, it's long enough to be detrimental in every day development.