jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-02 03:04:13 -05:00
Code Issues Projects Releases Wiki Activity

Changes from JetBrains PR

Browse Source 
These are the changes in the pre-review version of PR:
https://github.com/github/docs-internal/pull/29794

This version of the Codespaces docs forms the base for
the Universe megabranch.
This commit is contained in:
hubwriter
2022-10-06 12:48:44 +01:00
parent 7e3bc9ec8f
commit dfab0d1601
106 changed files with 1051 additions and 312 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
View File

@@ -41,7 +41,7 @@ When a codespace times out, your data is preserved from the last time your chang
## Rebuilding a codespace
You can rebuild your codespace to restore a clean state as if you had created a new codespace. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. You are most likely to rebuild a codespace to implement changes to your dev container. When you rebuild a codespace, any Docker containers, images, volumes, and caches are cleaned, then the codespace is rebuilt.
You can rebuild your codespace to restore a clean state as if you had created a new codespace. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. You are most likely to rebuild a codespace to implement changes to your dev container configuration. When you rebuild a codespace, any Docker containers, images, volumes, and caches are cleaned, then the codespace is rebuilt.
If you need any of this data to persist over a rebuild, you can create, at the desired location in the container, a symbolic link (symlink) to the persistent directory. For example, in your `.devcontainer` directory, you can create a `config` directory that will be preserved across a rebuild. You can then symlink the `config` directory and its contents as a `postCreateCommand` in your `devcontainer.json` file.