* 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>
4.4 KiB
title, intro, allowTitleToDifferFromFilename, versions, type, topics, redirect_from
| title | intro | allowTitleToDifferFromFilename | versions | type | topics | redirect_from | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| Quickstart for GitHub Codespaces | Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less. | true |
|
quick_start |
|
|
{% data reusables.codespaces.release-stage %}
Introduction
In this guide, you'll create a codespace from the sample repository and explore some of the essential features available to you within the codespace.
The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
Creating your codespace
-
Navigate to the main page of the sample repository.
-
Under the repository name, use the {% octicon "download" aria-label="The download icon" %} Code drop-down menu, and select Open with Codespaces.
- To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} New codespace.
Run the application
With your project open in a codespace, you can now run the application and launch it in a browser.
-
Start the application by entering
npm run devin the terminal. This command executes thedevscript in the package.json file and starts up the web application defined in the sample repository. -
When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
- Click Open in Browser to view your running application in a new tab.
Personalize with a theme extension
Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
-
In the left sidebar, click the Extensions icon.
-
In the search bar, enter
fairyflossand install the fairyfloss extension.
- Select the
fairyflosstheme by selecting it from the list.
- Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via Settings Sync.
Personalize with dotfiles
If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
This example guides you through creating a dotfiles repository for your codespaces.
-
Navigate to the sample dotfiles repository.
-
Fork the repository to your account and ensure it's public.
Verify the repository created under your account is named dotfiles, for example
yourname/dotfiles. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization. -
Create a new codespace from the sample application repository as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
Next Steps
You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_codespaces %}.
- "Getting Started guides" for using {% data variables.product.prodname_codespaces %} with specific languages
- Create a custom configuration to configure {% data variables.product.prodname_codespaces %} for your project.






