Copilot app: "Couldn't add this repository" for personal, private, renamed repo #207966
Replies: 2 comments 2 replies
|
💬 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. ⭐ |
|
Because another private repository on the same personal account can be added, this is not a general sign-in or plan failure. The recent rename makes a stale repository identity in the Copilot repository-access selection the strongest testable explanation. Try this sequence:
Do not rename the repository back merely to test this. If the current repository does not appear in the repository picker, or reselecting it still produces the old-account wording, capture the old name, new name, repository ID, rename time, and error time for Support. That would indicate the Copilot app's authorization record has not followed the rename, which only GitHub can repair. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Apps
Body
When trying to add a private repo, I get the error:
The account is the only GitHub account, has no organization, and the repo was renamed recently (few days).
I was able to add a different private repo on my account.
All reactions