Suggestion: Global User Policy to Opt Out of Third-Party Copilot Review Billing

[alennartz]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Code Review

Body

Problem: With the introduction of token-based usage billing, repository branch policies requiring automated Copilot Code Reviews pull AI credits directly from the PR author. This creates an unfair dynamic where open-source maintainers can dictate policies that actively deplete an external contributor's personal wallets or enterprise credit pools.

Proposed Solution: Implement a user-level billing setting:

"Allow my AI credits to be used for automated code reviews on repositories I do not own."

If a user toggles this to "No", any automated code review triggered by an external repository should instantly fail or skip gracefully (acting exactly as if the user were out of credits), allowing the PR process to continue without penalizing the contributor financially.

The obvious risk for maintainers is that everyone will turn it off and they will have to pay for the reviews of all the slop that contributors generated. If this is a concern I would suggest that repo maintainers can have a way of auto refusing any PR for which the contributor cant or won't pay for the AI review of their contribution.

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