Adding PR to Merge Queue Requires Target Branch Status Checks

[wjwatkinson]

Select Topic Area

Bug

Body

Adding A PR to a merge queue requires all of the same checks as if that PR were being merged directly to the target branch. However that PR is not being merged to the target branch, it is added to a Merge Queue branch and then merged if the checks succeed.

Required checks should only be required in the Merge Queue, which ensures the branch is up to date with the target branch including other inbound changes.

This way users do not have to wait for CI to run twice before merging their code. If they want they can add the PR to the merge queue before the checks on the PR all finish.

This would also enable deploying before merge with merge queues because the deploy step could be a required check.

[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. ⭐