Feature Request: Improve Email Notification Recipient Logic for Pull Request Act

[chuyich]

🏷️ Discussion Type

Product Feedback

Body

GHES version (3.19)
Description:
Currently, email notifications for pull request activities are sent to all users listed in the reviewers team, regardless of their actual participation. Note. The team involved via CODEOWNERS. This means:

• Users who have not actively participated in the pull request (e.g., did not review or comment) receive notifications in the same way as those who have.
• The email does not distinguish whether the recipient is being notified for their direct involvement or simply as a member of a reviewers team.

Example:
There is a PR created. TeamA was added to the PR in the reviewers list of that PR. All the members of teamA got the email in the format: To:ORG/REPO Cc:team_member; Review requested

One of the teamA member did the code review on that PR.
The teamA got removed from the reviewers list of that PR.
But any of the comments and code reviews were sent in the same format: To:ORG/REPO Cc:team_member; Review requested
It's hard for the team member who is not really involved on this PR to filter out the emails.

Feature Request
If a user actively participates in the pull request review (e.g., reviews, comments, or is directly requested), put their email address in the "To" field to indicate the notification requires their attention.
If a user is only part of a reviewers team and has not participated, put their email address in the "CC" field to indicate the notification is for reference only.
If there is no action required from the individual user, on the email, put the involved teams in Cc should be better.

This change will help users quickly identify whether the notification requires their attention or is just informational.

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