Codespace attached to fork repo while it should be attached to upstream

[tonyz1260]

Select Topic Area

Bug

Body

Hi,

So an issue I encountered with github codespace is quite weird as no settings are changed etc. So I forked a public repo couple months ago and I have been using a codespace on that repo for a long time. And the owner of the original repo invited me to become a collaborator and when we had the meeting, I tried to create a new codespace and then made a test push and it was successful. However, 2 days later when I was trying to change something and push again via that codespace, I found I can't do it (error says no permission) and somehow that codespace says it is attached to my fork repo. And I have to make a new codespace to push the changes and it became successful. And now I have to delete my fork repo to avoid this kind of issue, I wonder if this is the expected behaviour or no?

Thanks

[github-actions[bot]]

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