jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 21:07:12 -05:00
Code Issues Projects Releases Wiki Activity

Add aria-labels to octicons (#55740)

Browse Source
This commit is contained in:
Kevin Heis
2025-05-20 16:45:25 -07:00
committed by GitHub
parent e9730d4590
commit 39beae4778
494 changed files with 758 additions and 758 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

@@ -27,9 +27,9 @@ You can export your changes in one of several ways, depending on how you created
The following steps describe how to export your changes to a branch or fork. For information on exporting an unpublished codespace to a new repository, see [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template#publishing-from-githubcom).
{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-hidden="true" %} Code** menu.
{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** menu.
1. Click the ellipsis (**...**) to the right of the codespace you want to export from.
1. Select **{% octicon "git-branch" aria-hidden="true" %} Export changes to a branch** or **{% octicon "git-branch" aria-hidden="true" %} Export changes to a fork**.
1. Select **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Export changes to a branch** or **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Export changes to a fork**.
![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)