Rule “Automatically request Copilot code review” should support PRs authored by users that aren't assigned to the Copilot Premium account

[jml6m]

Select Topic Area

Product Feedback

Body

Summary
The ruleset option “Automatically request Copilot code review” currently only triggers when the pull request author has Copilot code review access and available premium quota. This prevents the feature from working for repositories where PRs are commonly authored by other users/collaborators. The ruleset automation doesn’t request Copilot code review when the collaborator account doesn’t have Copilot access/quota like the account owner. As a result, the “automatic” setting effectively becomes a no-op for some automation-driven workflows (manual requesting works in this case, but defeats the purpose of “automatic”).

Desired behavior
When enabled, the ruleset should be able to request Copilot code review for new PRs in the repository even if the PR author does not directly have Copilot code review access (perhaps they can be allowed to utilize the account owner's quota).

Why this matters
A lot of modern repos rely on automation to create PRs (dependency updates, codegen, agentic tools, etc.). These PRs are often the ones that would most benefit from fast automated review, but they’re also the most likely to be authored by non-human identities that won’t have Copilot entitlements.

Proposed solution (one or more of the below)

1. Add a ruleset mode like:
   “Automatically request Copilot code review for new pull requests (charged to repo owner / org billing / configured reviewer)”
   so it’s not tied to the PR author’s quota.

2. Allow selecting the “requester identity” for the automation, e.g.:

   • repository owner
   • a designated maintainer team/user
   • the actor who merged/approved installation of the app
     (Whoever is expected to have Copilot seats/quota.)

Thanks for considering—this would make the ruleset option much more useful in real-world workflows where automation opens PRs.

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