1
0
mirror of synced 2025-12-22 03:16:52 -05:00
Files
docs/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
Amy Burns c863678e73 New organization for codespaces docs (#18910)
* 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

* Document choosing machine type for a codespace in the GitHub UI (#19055)

* Document choosing machine type in the GitHub UI

* Replace link placeholder with actual path

* Update content/codespaces/changing-the-machine-type-for-your-codespace.md

Co-authored-by: Amy Burns <timeyoutakeit@github.com>

Co-authored-by: Amy Burns <timeyoutakeit@github.com>

* reoganizing based on CD

* putting machine type doc in correct location

* fixing broken redirects

* removing quickstart example from index page

* updating main index file

* Fixing broken links

* adding intros

* adding js quickstart (#18960)

* adding js quickstart

* clarify walkthrough

* adding more images and last few sections

* fixing broken links

* fixing broken links and formatting

* formatting fixes

* Apply suggestions from code review

Co-authored-by: hubwriter <hubwriter@github.com>

* adding index file for learn folder

* adding some feedback changes

* adding some review comments

* fixing broken links

Co-authored-by: hubwriter <hubwriter@github.com>

* doing some additional re-org

* fixing topics

* adding Codespaces as a topic

* fixing so title matches slug

* Update data/reusables/codespaces/codespaces-machine-types.md

Co-authored-by: Meg Bird <megbird@github.com>

* expanding intro

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: hubwriter <hubwriter@github.com>
Co-authored-by: Meg Bird <megbird@github.com>
2021-05-03 17:06:49 +00:00

1.7 KiB

title, intro, product, permissions, redirect_from, versions, topics
title intro product permissions redirect_from versions 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. {% data reusables.gated-features.codespaces %} 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
*
Codespaces

About development with {% data variables.product.prodname_codespaces %}

{% data reusables.codespaces.release-stage %}

{% data reusables.codespaces.use-visual-studio-features %}

{% data reusables.codespaces.about-port-forwarding %} For more information, see "Forwarding ports in your codespace."

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

{% data reusables.codespaces.use-chrome %} For more information, see "Troubleshooting your codespace."

{% data reusables.codespaces.connect-to-codespace-from-vscode %}

Navigating to your codespace

{% data reusables.codespaces.navigate-to-codespaces %} 2. Click the name of the codespace you want to develop in. Name of codespace