(Newbie) Where does Codespaces store my source code and environment? And will I lose my data if I don't use it for a long time? #180564
-
Select Topic AreaQuestion Body#Gemini Storage: Codespaces are stored in GitHub Storage (built on Azure). Your source code (repo-based) and your custom environment are stored as a virtual machine (VM) in the cloud. Data loss: You don't lose your source code because it's synchronized with the repository branch. However, if that Codespace is idle for a long time (usually 7 days by default), GitHub can automatically delete the entire environment and your uncommitted changes (retention policy) to save on storage costs. Tip: Always commit and push important changes before leaving a Codespace idle for many days. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
GitHub Codespaces stores your source code and development environment in the cloud, specifically on GitHub Storage built on Azure. Your repository-based code and your custom environment live inside a virtual machine (VM). Regarding data loss: any code you’ve committed and pushed to your GitHub repository is safe. However, if your Codespace is idle for a long period (typically around 7 days by default), GitHub may automatically delete the Codespace and any uncommitted changes to free up storage. Tip: Always commit and push important changes before leaving a Codespace idle for many days to avoid losing work. |
Beta Was this translation helpful? Give feedback.
GitHub Codespaces stores your source code and development environment in the cloud, specifically on GitHub Storage built on Azure. Your repository-based code and your custom environment live inside a virtual machine (VM).
Regarding data loss: any code you’ve committed and pushed to your GitHub repository is safe. However, if your Codespace is idle for a long period (typically around 7 days by default), GitHub may automatically delete the Codespace and any uncommitted changes to free up storage.
Tip: Always commit and push important changes before leaving a Codespace idle for many days to avoid losing work.