Skip to content

Commit baa85fd

Browse files
committed
docs: add instructions for renaming codespace display name after creation
1 parent e69c7ed commit baa85fd

File tree

2 files changed

+18
-0
lines changed

2 files changed

+18
-0
lines changed

docs/assets/rdev3_5.png

172 KB
Loading

docs/container_setup/github_codespace/creating_codespace.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,3 +19,21 @@ GitHub Codespaces' button and then click the green 'Create Codespace' button.
1919

2020
3. You will be taken to a VSCode editor within your browser.
2121
![codespace](../../assets/rdev3.png)
22+
23+
4. Rename your codespace for easier identification:
24+
25+
By default, your codespace will have a randomly generated name. Renaming it to something descriptive — such as referencing the issue or feature you’re working on makes it much easier to find and manage your codespaces, especially if you use several.
26+
27+
To rename your codespace:**
28+
29+
- Open your [GitHub Codespaces dashboard](https://github.com/codespaces) in your browser.
30+
- Find the codespace you just created (it will show the repository name and the current random display name).
31+
- Click the ellipsis (**...**) next to your codespace to open the options menu.
32+
- Select **Rename** from the dropdown.
33+
- Enter a descriptive new display name (e.g., `r-dev-env-issue-229` or `r-dev-env-patch-naming`) and confirm.
34+
35+
![rename codespace](../../assets/rdev3_5.png)
36+
37+
> **Tip:**
38+
> You can rename your codespace at any time. The display name is for your convenience and does not affect your code or environment.
39+

0 commit comments

Comments
 (0)