Allow per‑repo exception for public repos when blocking public‑code filter

[e1em3ntoDX]

Select Topic Area

Product Feedback

Copilot Feature Area

Copilot Enterprise

Body

Hi there,

Is there a way to add an exception to our organization’s public repositories when the “suggestions matching public code” filter is disabled in GitHub Copilot?

We need to disable this option organization-wide, but since we also have our own public repositories, it would be beneficial for our employees to allow Copilot to use code from a few of our own public repositories. I believe this would also be helpful for enterprises that disable the filter but use third-party APIs/libraries to refer to the their official code/API usage examples published on GitHub.

If there’s no way to do this right now, is it on the roadmap?

Thanks in advance!

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