While 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.
- If you created the codespace from a repository to which you have write access, you can export your changes to a new branch of the repository.
- If you created the codespace from a repository to which you only have read access, you can export your changes to a fork of the repository. GitHub Codespaces will create a new fork for you, or link your codespace to an existing fork if you already have one for the repository, and export your changes to a new branch of the fork. For more information, see "Using source control in your codespace."
- If you created the codespace from a template, and have not yet published it, you can publish the codespace to a new repository.
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."
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 "Creating a codespace from a template."
Navigate 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.
From the popover or dialog box, select 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