jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-25 02:17:36 -05:00
Code Issues Projects Releases Wiki Activity

Codespaces: correct the details of permanent codespace names (#48853)

Browse Source 
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com>
This commit is contained in:
hubwriter
2024-01-30 15:44:23 +00:00
committed by GitHub
parent e0dcb8e63a
commit 4f4c4cba5f
8 changed files with 28 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
View File

@@ -36,6 +36,6 @@ The following steps describe how to export your changes to a branch or fork. For
![Screenshot of a list of codespaces with the dropdown menu for one of them displayed, showing the "Export changes to a branch" option.](/assets/images/help/codespaces/export-changes-to-a-branch.png)
1. From the popover or dialog box, select **Create branch** or **Create fork**.
1. In the dialog box, click **Create branch** or **Create fork**.
The name of the new branch will be the permanent name of your codespace prefixed by the string `codespace-`, for example `codespace-monalisa-ideal-space-engine-vj59xj67jg42xx7`.
The name of the new branch will be the permanent name of your codespace prefixed by the string `codespace-`, for example `codespace-ideal-space-engine-w5vg5ww5p793g7g9`.