885da5b3d3
* New Crowdin translations by Github Action * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Ran script/fix-translation-errors.js * Reverted translated files with parsing and rendering errors * fix malformed liquid * add next directory to exclude list * currentversion -> currentVersion * fix liquid errors * fix liquid errors * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on * Reset known broken translation files LAST * Run script/i18n/homogenize-frontmatter.js Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
56 lines
3.4 KiB
Markdown
56 lines
3.4 KiB
Markdown
---
|
|
title: Developing in a codespace
|
|
intro: 'You can open a codespace on {% data variables.product.product_name %}, then develop using {% data variables.product.prodname_vscode %}''s features.'
|
|
permissions: Anyone can develop in a codespace owned by their user account.
|
|
redirect_from:
|
|
- /github/developing-online-with-github-codespaces/developing-in-a-codespace
|
|
- /github/developing-online-with-codespaces/developing-in-a-codespace
|
|
versions:
|
|
free-pro-team: '*'
|
|
type: how_to
|
|
topics:
|
|
- Codespaces
|
|
- Fundamentals
|
|
- Developer
|
|
---
|
|
|
|
{% data reusables.codespaces.release-stage %}
|
|
|
|
### About development with {% data variables.product.prodname_codespaces %}
|
|
|
|
{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
|
|
|
|
|
|
|
|
1. Side Bar - By default, this area shows your project files in the Explorer.
|
|
2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them.
|
|
3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it.
|
|
4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal.
|
|
5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more.
|
|
|
|
For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation.
|
|
|
|
{% data reusables.codespaces.connect-to-codespace-from-vscode %}
|
|
|
|
{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)."
|
|
|
|
#### Personalizing your codespace
|
|
|
|
{% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)."
|
|
|
|
{% data reusables.codespaces.apply-devcontainer-changes %} For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)."
|
|
|
|
#### Running your app from a codespace
|
|
{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)."
|
|
|
|
#### Committing your changes
|
|
|
|
{% data reusables.codespaces.committing-link-to-procedure %}
|
|
|
|
### Navigating to an existing codespace
|
|
|
|
1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
|
|
2. Click the name of the codespace you want to develop in. 
|
|
|
|
Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
|