-
Notifications
You must be signed in to change notification settings - Fork 15
Docs: Add instructions for renaming and managing codespaces (closes #229) #257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: devel
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
@@ -20,3 +20,28 @@ GitHub Codespaces' button and then click the green 'Create Codespace' button. | |||||||||
|
||||||||||
3. You will be taken to a VS Code editor within your browser. | ||||||||||
 | ||||||||||
|
||||||||||
4. Rename your codespace for easier identification: | ||||||||||
|
||||||||||
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: | ||||||||||
|
||||||||||
**To Rename your codespace:** | ||||||||||
Comment on lines
+28
to
+30
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As previously suggested (do not need line 30 here as it duplicates what is on line 24)
Suggested change
|
||||||||||
|
||||||||||
- Open your [GitHub Codespaces dashboard](https://github.com/codespaces) in | ||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it's useful for people to know the url - I often get people to type it in directly.
Suggested change
|
||||||||||
your browser. | ||||||||||
- Find the codespace you just created (it will show the repository name and | ||||||||||
the current random display name). | ||||||||||
- Click the ellipsis (**...**) next to your codespace to open the options menu. | ||||||||||
- Select **Rename** from the dropdown. | ||||||||||
- Enter a descriptive new display name, e.g., | ||||||||||
`Bug 7084 - text() recycling problems` or | ||||||||||
`Ignore deprecated/defunct fns in checkS3methods`, and confirm. | ||||||||||
|
||||||||||
 | ||||||||||
|
||||||||||
!!! Tip | ||||||||||
|
||||||||||
You can rename your codespace at any time. The display name is | ||||||||||
for your convenience and **does not** affect your code or environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the screenshot, it is a bit hard to work out what's going on. I think it would help to highlight the ellipsis, mark that as "A" or "1", then highlight "Rename" as you have done, but mark that "B" or "2", to show the sequence of events.