I cannot export my changes to a branch from codespace

[cismuc]

Select Topic Area

Question

Body

Heyh, I can't export my current codespace changes (the uncommited changes) to my github.. I've an option for that but it's taking a while and stops. I can't access my codespace to export them manually sicne I'm out of the free credits. Is it a known bug?

[cismuc]

I tried before when I was running out of credits, but even then, it was the same. The export changes process took forever, but somehow, when I opened the codespace, a new branch had been created. So, the issue is that exporting changes does create a branch, but it doesn't commit and push the changes to the remote.

and I don't have a "Download changes" option. All i can do is prevent codespace from bring auto deleted after the period of inactivity

[Zaxerion]

how to download it, i didn't see a Download changes

[AphroDatalyst]

Yes, this is a known limitation—GitHub Codespaces doesn’t allow exporting uncommitted changes once free credits are exhausted, and the built-in “export” can hang. Your best bet is to commit locally in a Codespace before credit runs out.

[Rocky-Dewan]

This is a known limitation of GitHub Codespaces, not a typical bug.

The "Export changes to a branch" feature requires the Codespace's underlying virtual machine (VM) to be running or at least accessible to bundle your work. When you run out of free credits, the Codespace is effectively shut down or suspended, preventing the export process from completing.

Possible solution:
Method : Use GitHub CLI (Requires a local setup)
If you have the GitHub CLI installed locally, you may be able to force the export.

Check CLI Access (Local Machine): Open your local terminal/command prompt.

Authenticate (if needed): Ensure you are logged into GitHub CLI:

Bash command:

gh auth login
Identify Codespace: Find the exact name of your Codespace from your Codespaces list (https://github.com/codespaces).

Execute Export Command: Run the export command using the CLI:

Bash command:

gh codespace export -c
Replace with the name you found in the previous step.

Result: The CLI attempts to bypass the web UI's limitations and export the changes. If successful, it will give you a new branch name where the changes are committed.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[barqimfathi-xyz]

Hey @cismuc ,
Before troubleshooting your export issue:

Quiz: If you have uncommitted changes in a Codespace and switch branches, what happens to those changes? 🤔

Hint: Think about Git’s behavior with uncommitted work.
Once you answer this, we can proceed with a safe workflow to export changes.