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 Introducción a los contenedores dev.

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.

Para empezar a trabajar con GitHub Codespaces, consulta Quickstart for GitHub Codespaces. Para más información sobre cómo crear un codespace, consulta Creación de un codespace para un repositorio o Creación de un codespace a partir de una plantilla. Si quieres volver a un codespace que ya has creado, consulta Apertura de un codespace existente. Para más información sobre cómo funciona GitHub Codespaces, consulta 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.

Para seguir usando GitHub Codespaces más allá del almacenamiento y del uso de proceso mensuales incluidos, proporciona la información de pago y establece un límite de gasto. Consulta Acerca de la facturación de 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 Selección de quién posee y paga los codespaces de una organización. You can set a spending limit for use of GitHub Codespaces on your organization or enterprise account. See Administración del límite de gasto para GitHub Codespaces.

If use of a codespace will be billed to an organization or enterprise, this is shown when the codespace is created. See Creación de un codespace para un repositorio. 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 Borrar un codespace.

La capacidad de crear codespaces a partir de repositorios que posea la organización depende de varios factores, como la visibilidad del repositorio y la configuración de la organización o su empresa principal. Para más información, consulta Solucionar problemas de creación y borrado de 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 Introducción a los contenedores dev.

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 Personalizar tu codespace.

Billing for Codespaces

For information on pricing, storage, and usage for GitHub Codespaces, see Acerca de la facturación de GitHub Codespaces.

De forma predeterminada, todas las cuentas tienen un límite de gasto de GitHub Codespaces de 0 USD. Esto impide que se creen codespaces o que se abran codespaces existentes, si esto supone que se incurra en un costo facturable para la cuenta personal, de organización o de empresa. En el caso de las cuentas personales, si tiene acceso para crear un codespace, puede hacerlo siempre que la cuenta no haya alcanzado el límite de su uso mensual incluido. En el caso de las organizaciones y las empresas, el límite de gasto predeterminado significa que, para que los usuarios puedan crear codespaces que se facturan a la organización, o a su empresa matriz, el límite debe cambiarse a un valor superior a 0 USD.

Los costes de GitHub Codespaces siempre se facturan mensualmente, incluso si la cuenta se factura anualmente. For information on how organizations owners and billing managers can manage the spending limit for GitHub Codespaces for an organization, see Administración del límite de gasto para GitHub Codespaces.