Automatically create a backup branch of unpushed and uncommited changes before automatically deleting codespace

[NCC1701M]

Select Topic Area

Product Feedback

Body

You send e-mails to inform about the automatic deletion of codespaces only with 7 days lead time. That is far too short notice. What if the user is unavailable for a longer period of time, e.g. because they are on vacation or sick? Then they cannot respond and cannot prevent the deletion. And if there are still changes in the branch that could not be pushed because, for example, the illness suddenly occurs, which is not uncommon with illnesses, then these changes are lost.

You already have the function to export the unpushed changes to a separate branch without having to open the codespace. Why don't you also do this automatically before the automatic deletion? You know that there are changes in a codespace.

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