PR closes automatically instead of base change

[mialbu]

Select Topic Area

Bug

Body

Problem

I sometimes have multiple PRs open that use branches that depend on each other. For example, I have a PR (pr1) that will merge branch f1 into dev. Then, I have another PR (pr2) that will merge branch f2 into f1. In order to keep pr1 clean, pr1 should be merged first. Once it is, I delete the branch f1. Normally (on the web app), the pr2 will change its base branch automatically from f1 to dev now. However, if I merge pr1 and delete the branch f1 in the GitHub mobile app, this is not the case. Instead the pr2 gets automatically closed (with no option to reopen).

Expected Behavior

The pr2 should change its base automatically to the dev branch, just like it would when using the GitHub web application.

System

• iOS
• version 1.183.1 (the problem already occurred with previous versions)

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

[peachmontt]

Provide Feedback: Since this appears to be a bug or an inconsistency with expected functionality, you can provide feedback directly within the app. Most apps have a feedback or support option that allows you to report issues.

Use the Web App: As a workaround, you may want to manage your pull requests and branches primarily through the web app until the mobile app's functionality aligns more closely with your expectations.

Check for Updates: Make sure your mobile app is updated to the latest version. Sometimes, issues like these are addressed in subsequent updates.

Reach Out to GitHub Support: If the issue persists, consider contacting GitHub Support to report this bug and seek further assistance.

[mialbu]

Provide Feedback: Since this appears to be a bug or an inconsistency with expected functionality, you can provide feedback directly within the app. Most apps have a feedback or support option that allows you to report issues.

The GitHub iOS app has a provide feedback option in the app and there's an App Support option in the App Store. Both lead me here to this GitHub org's discussions section. Please tell me where exactly bugs should be reported if not here.