Repo CODEOWNERs do not show properly as reviewers

[TomAnthony]

Select Topic Area

Product Feedback

Body

If you have a CODEOWNER file which adds a designated user as a reviewer for PRs to a repo, when you first create a PR the interface doesn't properly show that user as a reviewer, which can lead to them inadvertently being removed as a reviewer.

An example - I open this PR:

We can see the owner is added as a reviewer (automatically). However, the reviewer menu in the sidebar does not show them as a reviewer:

If you click the menu their name is there with a tick but given they were not in the menu that is confusing as best, and certainly not clear:

If you click their name in this menu it removes them as a reviewer. If you then add them back manually then they show properly:

Fixing this would certainly make things clearer. Thanks!

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