Allow bulk "Mark as Draft" action for Pull Requests

[EwoutH]

Select Topic Area

Product Feedback

Body

GitHub currently lets you mark individual PRs as draft, but there's no way to do this in bulk. The "Mark as" dropdown on the PR list view only offers "Open" and "Closed" as batch actions. If you need to convert several PRs to draft status — for example, after a priority shift, during a large refactor, or when onboarding a new branching strategy — you're forced to open each PR individually and click "Convert to draft" one at a time. For repositories with dozens of active PRs, this is tedious and error-prone.

Proposed solution
Add "Draft" as an option in the bulk "Mark as" dropdown on the Pull Requests list page, alongside the existing "Open" and "Closed" actions. The flow would work identically to the current bulk actions: select PRs via checkboxes, click "Mark as," and choose "Draft." Optionally, a corresponding "Ready for review" bulk action would complete the round-trip.

Use cases
A team decides to pause review on a batch of PRs while a blocking architecture decision is made. A maintainer wants to signal that several contributed PRs need rework before review. A release manager wants to pull back a set of PRs from the review queue without closing them.

Alternatives considered
You can script this through the GraphQL API using the convertPullRequestToDraft mutation, but that requires API access and scripting knowledge that not all team members have. A native UI option would make this accessible to everyone.

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