Add API support for “Never assign certain team members” in Team Code Review settings #173567
-
Select Topic AreaQuestion BodyHi GitHub team, This makes it hard to manage teams with automation tools (Terraform, Python scripts, etc.), since we can’t exclude specific people programmatically. Feature request: REST: add a never_assign_members field under team code review settings. GraphQL: add a field in TeamCodeReviewSettings. This would let orgs keep reviewer rules consistent, avoid assigning admins/leads, and manage policies as code. Thanks for considering! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hi! 👋 You’re correct—currently, the “Never assign certain team members” setting in GitHub’s UI is not exposed via REST or GraphQL APIs, so it can’t be managed programmatically. Your feature request makes sense: exposing this in the API would let organizations automate reviewer rules and manage policies as code. The best next step is to submit it to GitHub’s feedback forum or feature request tracker so the team can prioritize it. For now, manual configuration in the UI is required. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Hi! 👋
You’re correct—currently, the “Never assign certain team members” setting in GitHub’s UI is not exposed via REST or GraphQL APIs, so it can’t be managed programmatically.
Your feature request makes sense: exposing this in the API would let organizations automate reviewer rules and manage policies as code. The best next step is to submit it to GitHub’s feedback forum or feature request tracker so the team can prioritize it.
For now, manual configuration in the UI is required.