Hi,

I was just going to give the same feedback. We have a lot different checks that target different scenarios. We're deveolping Ansible Collections and most checks are only useful when the targeted code has been changed. But before finally merging into main we want to run a check for the whole collection to see if all moving parts still work together. These checks can require significant ressources so we don't want to run them on every single push, only when we think the PR is ready for merge. So it looks like we also need a check that's only triggered when the PR is added to a queue. It should be neccessary before leaving the queue but not to enter the queue.

Maybe this helps to give an extra point of view.

I'd also like separate required checks for pull requests and merge queues.

Use case 1: Publishing documentation to readthedocs.org

I've configured Read the Docs to also build documentation for pull requests to ensure that nothing is broken. That's also why I would like to make this check required for pull requests. However, inside the merge queue, I don't even know how I could tell Read the Docs to build the documentation again.

Use case 2: Format checks

I want to verify that PR titles follow the Conventional Commit spec, so tools like semantic-release work. This check should also be required for pull requests. But inside the merge queue, the commit message is not going to change, so it's pointless to run the check again.

Conclusion

I want to specify a set of conditions that must be true before a pull request is allowed to enter the merge queue. Additionally, I want to specify another set of conditions that gets verified and enforced when the pull request reaches the front of the merge queue.

Same for us, using Drone CI.

Unfortunately, Drone server doesn't yet accept the enqueued action from the payload, thus it waits the merge queue build to be treated as a pull_request event with an opened or a synchronized action, which is not the case.

We are able to bypass this issue by triggering builds to run on gh-readonly-queue/** triggered on push events, but that's not working because it expects the pull_request event to run, because it's specified in the branch rules.

What we would like is to be able to set merge queues checks separately from the pull requests checks, so the merge queues are agnostic to the CI tool everyone uses.

Up. Same issue.

Bump. My specific scenario is that I would like a long-running verification to always run against the PR, but only be required to get past the MQ.