1
0
mirror of synced 2026-01-05 03:06:35 -05:00
Files
docs/translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
James M. Greene 885da5b3d3 Local run of Translations patching process over batch (#19360)
* 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>
2021-05-18 15:07:05 +00:00

3.4 KiB

title, intro, permissions, redirect_from, versions, type, topics
title intro permissions redirect_from versions type topics
Developing in a codespace You can open a codespace on {% data variables.product.product_name %}, then develop using {% data variables.product.prodname_vscode %}'s features. Anyone can develop in a codespace owned by their user account.
/github/developing-online-with-github-codespaces/developing-in-a-codespace
/github/developing-online-with-codespaces/developing-in-a-codespace
free-pro-team
*
how_to
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 %}

Codespace overview with annotations

  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 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."

Personalizing your codespace

{% data reusables.codespaces.about-personalization %} For more information, see "Personalizing {% data variables.product.prodname_codespaces %} for your account."

{% data reusables.codespaces.apply-devcontainer-changes %} For more information, see "Configuring {% data variables.product.prodname_codespaces %} for your project."

Running your app from a codespace

{% data reusables.codespaces.about-port-forwarding %} For more information, see "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. Name of codespace

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.