URGENT: Copilot disabled by GitHub System after org migration to Enterprise #192638
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. β |
Beta Was this translation helpful? Give feedback.
-
|
Hi @pennz1, Thank you for your patience. The community is unable to assist with nor escalate your ticket, but we can assure you it is in the right place. It will be answered in the order it was received based on our team's resources and the amount of tickets ahead of yours. We appreciate your understanding! As no other Community Discussions team members will be able to provide additional help with account related questions I am going to close this discussion. Thank you! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
π·οΈ Discussion Type
Bug
Body
Hi GitHub team,
We have an urgent production issue affecting 8 developers for 24+ hours. Support ticket submitted with no response.
Enterprise: yswlingyu
Organization: yswsf
Issue:

After migrating org "yswsf" into enterprise "yswlingyu", GitHub System automatically disabled Copilot seat management
TWICE (confirmed in Audit Log, actor: GitHub System).
Errors:
When i allow this in organization settingsοΌ

"There was an error when trying to allow this organization to assign seats"
Status:
The Audit Log clearly shows
copilot.cfb_seat_management_changedtriggered by GitHub System, not by any user action.Can someone from GitHub escalate this to the support team? Or advise how to manually re-enable from the backend?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions