How can we make CircleCI play well with Github merge queue merge groups?

Build Environment
1

I feel like I probably know what the answer is, given what I know about how merge groups work in Github’s merge queue.

Essentially, with the merge queue, we can enable merging in batches - this allows us to avoid a 2x growth in the number of CI jobs run. However, this is implemented by Github sending only one push event for a merge batch rather than every commit in the batch, so while we can reduce the number of GHAs, we can’t reduce the number of CCI jobs, since those still trigger on every commit to master.

Is there a way for CCI to hook into this and provide a way to allow CCI to run just once per batch as well? I’d prefer to avoid creating a GHA that then triggers a CCI run.

1 Like
2

Hey @purajit were you able to make any progress on this? We have been looking at setting up Github merge queue with CircleCI and so far running into the same thing you are describing. I can get the merge queue to work, but it triggers a separate build for every single commit in the queue, rather than batching them according to the batching rules we define in the Github settings.