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

The Problem

Right now, configuring the Copilot code review firewall (enabling/disabling the firewall, toggling the recommended allowlist, or managing custom allowlists) can only be done manually through the web UI.

For Copilot cloud agents, we can manage configuration through repository environment variables, but that option isn't available for code review firewall settings. When managing a large number of repositories or organizations, updating these toggles manually across the UI is tedious, error-prone, and impossible to track cleanly via Git or Terraform.

What We Need

We’d love to see programmatic support for managing these settings as code:

1. REST API Endpoints

• Ability to read and update firewall status, recommended allowlists, and custom IP/domain rules at both the Organization (/orgs/{org}/...) and Repository (/repos/{owner}/{repo}/...) levels.

2. Environment Variable or File-Based Config

• Support for configuring allowlists and firewall behaviors via repository environment variables (similar to Copilot cloud agents) or a config file in .github/.

Why This Matters

• Scalability: Managing network boundaries manually across dozens or hundreds of repos isn't practical for enterprise teams.
• Security & Auditing: Having API access allows us to enforce, audit, and automate network security policies consistently across all codebases.
• Terraform Support: Exposing API endpoints will allow us (and the GitHub Terraform provider) to manage firewall settings alongside the rest of our GitHub infrastructure.