What are GitHub Codespaces?

Introduction

A codespace is a development environment that's hosted in the cloud. You can customize your project for GitHub Codespaces by committing configuration files to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. See 개발 컨테이너 소개.

Each codespace you create is hosted by GitHub in a Docker container, running on a virtual machine. You can choose from a selection of virtual machine types, from 2 cores, 8 GB RAM, and 32 GB storage, up to 32 cores, 64 GB RAM, and 128 GB storage.

By default, the codespace development environment is created from an Ubuntu Linux image that includes a selection of popular languages and tools, but you can use an image based on a Linux distribution of your choice and configure it for your particular requirements. Regardless of your local operating system, your codespace will run in a Linux environment. Windows and macOS are not supported operating systems for the remote development container.

You can connect to your codespaces from your browser, from Visual Studio Code, or by using GitHub CLI. When you connect, you are placed within the Docker container. You have limited access to the outer Linux virtual machine host.

Using GitHub Codespaces

To begin developing using cloud-based compute resources, you can create a codespace from a template or from any branch or commit in a repository. When you create a codespace from a template, you can start from a blank template or choose a template suitable for the work you're doing.

GitHub Codespaces을(를) 시작하려면 Quickstart for GitHub Codespaces을(를) 참조합니다. codespace를 만드는 방법에 대한 자세한 내용은 리포지토리에 대한 codespace 만들기 또는 템플릿에서 codespace 만들기을(를) 참조하세요. 이미 만든 codespace로 반환하려면 기존 Codespace 열기을(를) 참조하세요. GitHub Codespaces 작업 방법에 대해 자세히 알아보려면 Deep dive into GitHub Codespaces을(를) 참조하세요.

Using codespaces owned by your personal account

All personal GitHub accounts have a monthly quota of free use of GitHub Codespaces included in the Free or Pro plan. You can get started using GitHub Codespaces on your personal account without changing any settings or providing payment details.

If you create a codespace from an organization-owned repository, use of the codespace will either be charged to the organization (if the organization is configured for this), or to your personal account.

결제 세부 정보를 제공하고 지출 한도를 설정하여 GitHub Codespaces을(를) 월별 포함된 스토리지 및 컴퓨팅 사용량 이상으로 계속 사용할 수 있습니다. GitHub Codespaces 청구 관련 정보을(를) 참조하세요.

Using organization-owned codespaces

Owners of organizations on GitHub Team and GitHub Enterprise plans can pay for their members' and collaborators' use of GitHub Codespaces. This applies to codespaces created from repositories owned by the organization. See 조직에서 codespace를 소유하고 비용을 지불하는 사람 선택. You can set a spending limit for use of GitHub Codespaces on your organization or enterprise account. See GitHub Codespaces의 지출 한도 관리.

If use of a codespace will be billed to an organization or enterprise, this is shown when the codespace is created. See 리포지토리에 대한 codespace 만들기. Codespaces that are billed to an organization, or its parent enterprise, are owned by the organization and can be deleted by an organization owner. See Codespace 삭제.

조직 소유 리포지토리에서 codespace를 만드는 기능은 리포지토리의 가시성과 조직 또는 상위 기업의 설정을 비롯한 여러 요인에 따라 달라집니다. 자세한 내용은 Codespaces 만들기 및 삭제 문제 해결을(를) 참조하세요.

Customizing GitHub Codespaces

To customize the runtimes and tools in your codespace, you can create one or more dev container configurations for your repository. Adding dev container configurations to your repository allows you to define a choice of different development environments that are appropriate for the work people will do in your repository.

If you create a codespace from a repository without any dev container configurations, GitHub Codespaces will clone your repository into an environment with the default dev container image that includes many tools, languages, and runtime environments. If you create a codespace from a template, you might start with some initial configuration on top of the default image. See 개발 컨테이너 소개.

You can personalize aspects of your codespace environment by using a public dotfiles repository. You can use dotfiles to set shell aliases and preferences, or to install your personal preference of the tools you like to use. If you use GitHub Codespaces in the browser, or in Visual Studio Code, you can use Settings Sync to give your codespace editor the same settings, keyboard shortcuts, snippets, and extensions that you have set up in your local installation of Visual Studio Code.

See codespace 사용자 지정.

Billing for Codespaces

For information on pricing, storage, and usage for GitHub Codespaces, see GitHub Codespaces 청구 관련 정보.

기본적으로 모든 계정의 GitHub Codespaces 지출 한도는 $0 USD입니다. 이렇게 하면 개인, 조직 또는 기업 계정에 청구 가능한 비용이 발생할 경우 새 codespace가 만들어지거나 기존 codespace가 열리는 것을 방지할 수 있습니다 개인 계정의 경우 codespace를 만들 수 있는 액세스 권한이 있으면 계정이 월별 포함된 사용량 한도에 도달하지 않는 한 만들 수 있습니다. 조직 및 엔터프라이즈의 경우 기본 지출 한도는 사람들이 조직 또는 해당 부모 엔터프라이즈에 청구되는 codespace를 만들 수 있도록 허용하려면 한도를 $0 USD 이상의 값으로 변경해야 한다는 것을 의미합니다.

계정에 연간 요금이 청구되더라도 GitHub Codespaces에 대한 비용은 항상 매월 청구됩니다. For information on how organizations owners and billing managers can manage the spending limit for GitHub Codespaces for an organization, see GitHub Codespaces의 지출 한도 관리.