c70adf6702
* reorganizing security and access sections * updating delete doc * making vscode doc moore os agnostic * updating developing in a codespace * fixing broken links * fixing some broken links * fixing broken topic * fixing broken link * Managing users permissions for your organization and other stuff (#19231) * Add new 'Managing user permissions for your organization' article * Revise 'Managing access and security for Codespaces' and screenshot * Add codespaces to org repo permissions article * Apply suggestions from code review Co-authored-by: Amy Burns <timeyoutakeit@github.com> * fixing title to match slug * fixing broken link * updating personalization doc * updating troubleshooting guide * updating creating doc * adding information about when secrets are used * removing secrets stuff from this PR * Addig order of operations for codespaces * self review fixes * Apply suggestions from code review Co-authored-by: Allison Weins <3174849+2percentsilk@users.noreply.github.com> * renaming quickstart to correct pattern: * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * rewriting re. review comments * Codespaces landingpage (#19053) * adding new tables and linking to info on audit logs * editing some text: * adding new info on how to add image registry login * adding link and fixing table * formatting * formatting * Apply suggestions from code review Co-authored-by: Laura Coursen <lecoursen@github.com> * updaing private image registry secret info and other improvements * some minor fixes * fixing test errors * rewriting registry secret section * rewriting registry secret section * updating link to reflect title * Update content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md Co-authored-by: Laura Coursen <lecoursen@github.com> * updating bullet point * moving codespaces to top-level item * fixing duplicated redirect * Adding some organization for contributors * adding learning codespaces to index file * do not error out if category array is empty * Apply suggestions from code review Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com> * fixing broken link * testing what is possible for the landing page * adding first run of landing page * adding new video and intro text * add landing page scaffolding * Update codespaces_code_examples.yml * lint * fixing issues in branch * fixing nav * fixing broken directs * Creating guides sub-landing page * adding topics * removing unused toopic * removing instant * updating landing page and guides page * updating versioning * removing unused topic * removing other versions: * actually fixing broken links * fixing title * fixing intro to suit the landing page * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * adding video * adding video * adding correct link for video * removing duplicated guides Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * rewording and reorganizing code samples * fixing some feedback from engineering * Adding doc on Secrets in codespaces (#19248) * adding secrets docs * fixing some broken links * fixing some more broken redirects * copy edit and updating limits for secrets * adding limits for users * Apply suggestions from code review Co-authored-by: Felicity Chapman <felicitymay@github.com> * adding feedback Co-authored-by: Felicity Chapman <felicitymay@github.com> * updating beta banner * adding quickstarts to landing page * removing availability section from reusable Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Allison Weins <3174849+2percentsilk@users.noreply.github.com> Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com>
57 lines
3.4 KiB
Markdown
57 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**.
|