The PR interface is not very intuitive for describing the source branch and the target branch. #157482
Replies: 2 comments
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
I also support this request. It would be very nice to be able to control in settings how this can be displayed across different repos. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
Currently, on the open PR screen, the summary that outlines the source branch and the target branch can cause confusion. At least in Western contexts, we tend to think first about: where it comes from; and second: where it's going to. However, the current interface does the opposite, first: where it's going to; and second: where it comes from.
I believe that this change would make understanding a "pull request" more explicit and transparent for code reviewers, reducing potential misunderstandings in this process.
Reference to the interface mentioned here in this post.

Beta Was this translation helpful? Give feedback.
All reactions