Feature request: allow atomically reopening PRs with dead branches, provided a valid replacement branch is supplied

[dead-claudia]

Select Topic Area

Product Feedback

Body

This command result took me a bit by surprise:

$ gh api --method PATCH -H 'Accept: application/vnd.github+json' -H 'X-GitHub-Api-Version: 2022-11-28' /repos/MithrilJS/mithril.js/pulls/2824 -f state=open -f base=main
{
  "message": "Validation Failed",
  "errors": [
    {
      "message": "Cannot change the base branch of a closed pull request.",
      "resource": "PullRequest",
      "field": "base",
      "code": "invalid"
    }
  ],
  "documentation_url": "https://docs.github.com/rest/pulls/pulls#update-a-pull-request",
  "status": "422"
}
gh: Validation Failed (HTTP 422)

I deleted the next branch that PR (MithrilJS/mithril.js#2862) was targeting in favor of main. Unfortunately, I couldn't just use automated default branch migration, since I needed to also be careful to not accidently cut a new release with our automation. It would've been very helpful to have so I could resurrect the auto-closed PRs that died due to that migration:

• #2025 array of querystring without number MithrilJS/mithril.js#2053
• [WIP] Kick bundler - use esbuild for building MithrilJS/mithril.js#2753
• WiP: Inline scope components MithrilJS/mithril.js#2791
• stringifying xhr error response MithrilJS/mithril.js#2804
• Cleaning up code by making vnode.attrs always non-null MithrilJS/mithril.js#2819
• Global error management MithrilJS/mithril.js#2824
• feat: Redraw once promise returned from event handler is settled MithrilJS/mithril.js#2862

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