기존 codespace 열기

Note: Using GitHub Codespaces with JetBrains IDEs is currently in public beta and is subject to change.

You can reopen any of your active or stopped codespaces on GitHub.com, in a JetBrains IDE, in Visual Studio Code, or by using GitHub CLI. You can't reopen a codespace that has been deleted. For more information, see "The codespace lifecycle."

You can view all your codespaces on the "Your codespaces" page at github.com/codespaces. From this page, you can:

Open, stop, or delete your codespaces.
See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. For more information, see "About billing for GitHub Codespaces."
See the machine type, size, and status of your codespaces.
Create a new codespace, either by choosing one of GitHub's templates or by clicking New codespace. For more information, see "Creating a codespace from a template" and "Creating a codespace for a repository."
Prevent automatic deletion of a codespace. For more information, see "Configuring automatic deletion of your codespaces."

Reopening a codespace

Navigate to the "Your codespaces" page at github.com/codespaces.
To open a codespace in your default editor, click the name of the codespace. You can set your default editor for Codespaces in your personal settings page. For more information, see "Setting your default editor for GitHub Codespaces."

To open the codespace in an editor other than your default:
1. Click the ellipsis (...) to the right of the codespace you want to open.
2. Click Open in.
3. Click Open in APPLICATION.
You can open the codespace in:
- Your browser
- Visual Studio Code
- JetBrains Gateway
- JupyterLab
If you choose Visual Studio Code or JetBrains Gateway, you must make sure you have installed the selected application on your local machine.

If you choose JupyterLab, the JupyterLab application must be installed in the codespace. The default container image includes JupyterLab, so codespaces created from the default image will always have JupyterLab installed. For more information about the default image, see "Introduction to dev containers" and the devcontainers/images repository. If you're not using the default image in your dev container configuration, you can install JupyterLab by adding the ghcr.io/devcontainers/features/python feature to your devcontainer.json file. You should include the option "installJupyterlab": true. For more information, see the README for the python feature, in the devcontainers/features repository.

Note: To use GitHub Codespaces in VS Code, you need to install the Codespaces extension. For more information, see "Using GitHub Codespaces in Visual Studio Code."

In the VS Code desktop application, open the Command Palette with Command+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux).
Type "Codespaces" and select one of the following commands.
- To open a codespace in a new window of VS Code, select Codespaces: Open Codespace in New Window
- To open a codespace in the web editor, select Codespaces: Open in Browser
Click the codespace that you want to open.

You can also access the commands listed above by navigating to the Remote Explorer view in VS Code and right-clicking the codespace that you want to open.

Screenshot of a codespace selected in the Remote Explorer, with "Open in Browser" highlighted in the right-click menu.

Note: If the Remote Explorer is not displayed in the Activity Bar:

Access the Command Palette. For example, by pressing Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux).
Type: details.
Click Codespaces: Details.

In a terminal, enter one of the following GitHub CLI commands.
- To open a codespace in VS Code, enter:
  Shell
```
gh codespace code
```
  Note: You must have VS Code installed on your local machine. For more information, see "Setting up Visual Studio Code" in the VS Code documentation.
- To open a codespace in the browser, enter:
  Shell
```
gh codespace code --web
```
- To open a codespace in JupyterLab, enter:
  Shell
```
gh codespace jupyter
```
  Note: The JupyterLab application must be installed in the codespace you are opening. The default container image includes JupyterLab, so codespaces created from the default image will always have JupyterLab installed. For more information about the default image, see "Introduction to dev containers" and the devcontainers/images repository. If you're not using the default image in your dev container configuration, you can install JupyterLab by adding the ghcr.io/devcontainers/features/python feature to your devcontainer.json file. You should include the option "installJupyterlab": true. For more information, see the README for the python feature, in the devcontainers/features repository.
- To access a codespace from the command line, over SSH, enter:
  Shell
```
gh codespace ssh
```
Using the arrow keys, navigate to the codespace that you want to open.
To open the codespace, press Enter.

For more information, see gh codespace code in the GitHub CLI manual.

If you have set the JetBrains Gateway as your default editor, then the Gateway will launch automatically when you open a codespace from GitHub.com.

If the JetBrains Gateway is not your default editor, you can still open a codespace in JetBrains by going to the "Your codespaces" page at github.com/codespaces and clicking the ellipsis (...) to the right of the codespace you want to open. For more information, see "Opening an existing codespace."

Alternatively, you can also open the JetBrains Gateway and select an existing codespace, as described in the following procedure.

Open the JetBrains Gateway application.
Click Connect to Codespaces.
In the "Your Codespaces" list, click the codespace you want to work in.
In the "Available IDEs" list, click the JetBrains IDE you want to use. The Gateway will remember your choice the next time you connect to a codespace.
Click Connect.
Notes:
- If you chose Rider as your JetBrains IDE and the repository contains multiple solution files, the "Set Solution Path" dialog is displayed prompting you to choose which solution you want to work in. Choose a solution file from the dropdown menu and click OK.
  
  If the repository doesn't have a solution file, Rider opens in a basic project directory view and will have limited capabilities. For instance, you won't get .NET-specific code navigation. If there is just a single solution file in the repository it will be used automatically, without the prompt being displayed. For more information, see "Create and open projects and solutions" in the JetBrains documentation.
- If you are running a firewall, then the first time you connect to a remote resource you may be prompted to allow the JetBrains Gateway to communicate across your network.