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

You're not missing anything. Introspecting the live schema confirms it:

• Team exposes only reviewRequestDelegationEnabled, reviewRequestDelegationAlgorithm, reviewRequestDelegationMemberCount and reviewRequestDelegationNotifyTeam.
• UpdateTeamReviewAssignmentInput additionally accepts removeTeamRequest, includeChildTeamMembers, countMembersAlreadyRequested and excludedTeamMemberIds, with no matching read fields.
• The REST API has no team review-assignment endpoints or fields at all.

So those four settings are write-only in the public APIs today.

For the Terraform provider, the practical options are:

1. Model them like secrets: write-only attributes (Terraform 1.11+ write_only, or plain attributes stored from config) that are applied on create/update but never compared against the API, so there's no drift detection for them.
2. Leave them out until GitHub adds read fields.

Option 1 is how the provider already handles values it can't read back, such as secrets. Either way, document that changes made in the UI to those four settings won't be detected.