Org admins need a way to avoid manually reviewing Copilot model availability every time GitHub adds new models. #202892
Replies: 2 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
My main gripe was addressed this week, which is great: https://docs.github.com/en/copilot/concepts/models/default-availability Closing this thread, although the recent changes don't handle automatically disabling obsolete models or just the general UX of the Copilot Models page. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Copilot in GitHub
Body
Problem
Today, orgs can remain on older AI models indefinitely unless an admin notices that new models were added and manually revisits settings. This creates operational overhead and inconsistent adoption across organizations.
Suggestions
All reactions