This article provides steps for exporting your codespace changes to a branch.
About exporting changesWhile using GitHub Codespaces, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a spending limit or have a general issue accessing your codespace.
You can export your changes in one of several ways, depending on how you created the codespace. In every case, only the Git branch that is currently checked out in the codespace is exported. Work contained in other branches is not exported.
Note
GitHub blocks pushes containing files larger than 100 MiB. If your codespace contains large files you will not be able to export your changes to a branch or fork. For more information, see About large files on GitHub.
Exporting changes to a branchThe 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 Creating a codespace from a template.
In the top-left corner of GitHub, select , then click Codespaces to take you to the "Your codespaces" page at github.com/codespaces. Or, for an individual repository, click the Code menu.
Click the ellipsis (...) to the right of the codespace you want to export from.
Select Export changes to a branch or Export changes to a fork.
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-ideal-space-engine-w5vg5ww5p793g7g9
.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4