27 lines
2.1 KiB
Markdown
27 lines
2.1 KiB
Markdown
If you're working in a codespace, you can publish it from the {% data variables.product.prodname_vscode_shortname %} web client or desktop application.
|
|
|
|
{% data reusables.codespaces.source-control-display-dark %}
|
|
1. To stage your changes, click **+** next to the file you've added or changed, or next to **Changes** if you've changed multiple files and you want to stage them all.
|
|
|
|
|
|
|
|
{% note %}
|
|
|
|
**Note:** If you start from {% data variables.product.company_short %}'s blank template, you will not see a list of changes unless you have already initialized your directory as a Git repository. To publish codespaces created from the blank template, click **Publish to {% data variables.product.company_short %}** in the Source Control view, then skip to step 5.
|
|
|
|
{% endnote %}
|
|
2. To commit your staged changes, type a commit message describing the change you've made, then click **Commit**.
|
|
|
|
|
|
3. Click **Publish Branch**.
|
|
|
|
|
|
4. In the "Repository Name" dropdown, type a name for your new repository, then select **Publish to {% data variables.product.company_short %} private repository** or **Publish to {% data variables.product.company_short %} public repository**.
|
|
|
|
|
|
|
|
The owner of the new repository will be the {% data variables.product.prodname_dotcom %} account with which you created the codespace.
|
|
5. Optionally, in the pop-up that appears in the lower right corner of the editor, click **Open on {% data variables.product.company_short %}** to view the new repository on {% data variables.product.prodname_dotcom_the_website %}.
|
|
|
|
|