Hello!

It seems that actors who can bypass other required branch protection rules (e.g. PR approval) can no longer bypass them if merge queue is required. In other words, there's no way to force adding a PR to the merge queue, even when one has bypass rights for all repository rulesets.

It might come from what's mentioned in the doc:

Once a pull request has passed all required branch protection checks, a user with write access to the repository can add the pull request to the queue.

The current behavior feels like an overly strict interpretation of this, which tightly couples these required checks to the ability to use the merge queue without taking into account one's bypasser status.

(FYI, it feels like there is a possible link to this discussion around bypasser mergability status, though I haven't checked if this particular "required merge queue" issue also applies to the equivalent classic branch protection.)

Our use case concerns a bot/app that we want to automatically generate and merge update PRs via the merge queue without human interaction. Our request is essentially the same as the one mentioned in this comment: we want to allow some PRs to be added to the merge queue while bypassing other requirements. We could of course use our bypasser status to push the protected branch directly without a PR, but the goal is to open the PR and add it directly to the merge queue in order to avoid logical conflicts in our highly active repo.

Is a solution to this issue on your radar?

Thanks!

Retiring this post as it is over 6 months old. If you have any questions, consider starting a new post.