Why can't the 15GB upper limit of CodeSpace directly prevent users from exceeding it ?

[saysth7]

🏷️ Discussion Type

Product Feedback

Body

For example, by limiting the disk size, it is entirely feasible to ensure that the total size of multiple codespaces does not exceed the limit.
The current design makes it difficult for users to notice if they have exceeded the limit.
Once the limit is exceeded, the user cannot turn on the codespace, let alone clear the disk space.
Moreover, after directly deleting CodeSpace, it is impossible to continue using CodeSpace before the current month.

I really don't understand why we don't do it this way.

Moreover, after deleting a codespace, if there is still disk space remaining, one should be able to continue creating new codespaces for use.

last, why not use auto-translation? it's so easy nowadays.

orgiin: #211854

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

[XY-code1]

The 15 GB allowance is monthly metered storage, not a fixed disk capacity. GitHub measures usage over time, including storage for stopped codespaces; deleting one stops future accrual but does not refund usage already recorded. That explains why freeing disk space does not necessarily let you create another codespace this month. Your feedback still identifies a real gap: show projected quota exhaustion before lockout, and provide an export or cleanup path that does not require starting the machine. Codespaces billing.