Switching to ruleset (even in eval mode) prevents merge queue bypass

[wyardley]

🏷️ Discussion Type

Bug

Body

We have a repo with traditional branch protection that I've been working on cutting over to new rulesets.
This mostly looks fine, but even in evaluate mode, I'm noticing that turning on "merge queue" in the ruleset makes the bypass option

With only traditional branch protection:

But with these rulesets in place (whether in "evaluate" or "active"), that bypass option doesn't show up in the UI, even if one is in the group in the "bypass" list. I've also tried toggling "restrict updates" or "restrict creations" on or off - same behavior either way.
Is there a setting I'm missing?

I've also tried making a second, separate ruleset, putting the merge queue rules in that one, and explicitly giving the same groups bypass permissions, but I still don't see the option to bypass merge queue. I've also looked at the "push" and "update"

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[wyardley]

So, not sure if this is just an evaluate mode issue or what, but I am able to do this successfully now without issue (i.e., bypass still works as expected).

However, similar to https://github.com/orgs/community/discussions/61107#discussioncomment-6569780, I haven't found a great way to accomplish "restrict who can push to matching branches". Doing a separate rule with only "update" checked, and checking specific teams that can override "always" or "on pull requests", doesn't seem to do it.