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

It somehow orphans the PR in the process of renaming + retargeting

This looks like the PR metadata is still pointing to the original branch reference even after the branch rename operation completed successfully.

From what I can tell:

• The branch itself was renamed correctly
• GitHub displays the rename event properly
• But the pull request head reference was not updated accordingly
• As a result, subsequent pushes to the renamed branch are no longer associated with the existing PR

So the PR appears to remain attached to the stale branch ref internally.

This is especially problematic for automation workflows like release-please where branch names may be regenerated or renamed dynamically.

A few things that may help narrow this down:

• Does this reproduce consistently for renamed branches created by bots/apps?
• Does manually pushing to the renamed branch create a new detached PR state?
• Is the issue specific to branch names containing nested path segments (release-please--branches--...)?

It may also be worth checking whether the PR stores the branch by immutable ref ID vs branch name string, since this behavior suggests the linkage is name-based and not being reconciled after rename events.

I overcame this by updating the ref instead of renaming and deleting the branch, but there shouldn't be dangling PRs like the above one I guess. Seems weird, it should probably error out instead of being stuck at the loading screen I guess.