Improve Pull Request Usability

[asjerbereket]

🏷️ Discussion Type

Product Feedback

Body

Hi!

While working on a pull request, I noticed that when there’s a lot of discussion—both from Copilot and team members—the page can get pretty long. Once the PR is approved, I often have to scroll quite far to find the “Merge pull request” button.

Would it be possible to make the merge button sticky? That way, you could keep scrolling through comments while still having quick access to merge, without needing to scroll all the way down.

I was also wondering if it might be possible to add an option to sort or filter conversations so newer comments appear at the top. That would make it easier to catch up on recent feedback without scrolling through everything.

Thanks for considering this!

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

[michitheonlyone]

The same here the "approved" message and the checkmark are irritating and to less visible nor prominent enough. Also in the overview list of all PR's it should be more visible/ more prominent

[mohamedxelturkey-cpu]

The same here the "approved" message and the checkmark are irritating and to less visible nor prominent enough. Also in the overview list of all PR's it should be more visible/ more prominent

[mohamedxelturkey-cpu]

The same here the "approved" message and the checkmark are irritating and to less visible nor prominent enough. Also in the overview list of all PR's it should be more visible/ more prominent