Skip to main content

Configuring automatic deletion of your codespaces

Unused codespaces are automatically deleted. You can choose how long your stopped codespaces are retained, up to a maximum of 30 days.

Acerca de GitHub Codespaces está disponible para las organizaciones que utilizan GitHub Team o Nube de GitHub Enterprise. Para obtener más información, consulta la sección "Productos de GitHub".

By default, Codespaces are automatically deleted after they have been stopped and have remained inactive for 30 days.

However, because Codespaces incur storage charges, you may prefer to reduce the retention period by changing your default period in your personal settings for Acerca de GitHub Codespaces. Para obtener más información sobre los cargos de almacenamiento, consulta la sección "Acerca de la facturación para Acerca de GitHub Codespaces".

Note: Whether or not you have set a personal codespace retention period, it's a good idea to get into the habit of deleting codespaces that you no longer need. Para obtener más información, consulta la sección "Borrar un codespace."

Automatic deletion happens irrespective of whether a codespace contains unpushed changes. To prevent automatic deletion of a codespace, just open the codespace again. The retention period is reset every time you connect to a codespace, and the retention countdown restarts when the codespace is stopped.

If a repository belongs to an organization, the organization admin may have set a retention period for the whole organization. If this period is less than the default retention period in your personal settings then the organization retention period will apply to codespaces you create for this repository. For more information, see "Restricting the retention period for codespaces."

Each codespace has its own retention period. You may, therefore, have codespaces with different rentention periods. For example, if:

  • You created a codespace, changed your default retention period, then created another codespace.
  • You created a codespace using CLI de GitHub and specified a different retention period.
  • You created a codespace from an organization-owned repository that has a retention period configured for the organization.

Note: The retention period is specified in days. A day represents a 24-hour period, beginning at the time of day when you stop a codespace.

Setting a default retention period for your codespaces

  1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en Configuración.

    Icono Settings (Parámetros) en la barra de usuario

  2. En la sección de "Código, planeación y automatización" de la barra lateral, haz clic en Codespaces.

  3. Under "Default retention period", enter the number of days for which you want your codespaces to be retained, by default, after they have been stopped.

    Selecting your retention period

    You can set your default retention period between 0 and 30 days.

    Warning: Setting the period to 0 will result in your codespaces being immediately deleted when you stop them, or when they timeout due to inactivity. For more information, see "Setting your timeout period for Acerca de GitHub Codespaces."

  4. Haz clic en Save (guardar).

When you create a codespace using CLI de GitHub you can override this default. If you create a codespace in an organization that specifies a shorter retention period, the organization-level value overrides your personal setting.

If you set a retention period of more than a day, you'll be sent an email notification one day prior to its deletion.

Checking the remaining time until autodeletion

You can check whether a codespace is due to be automatically deleted soon.

When an inactive codespace is approaching the end of its retention period, this is indicated in your list of codespaces on GitHub at https://github.com/codespaces.

The pre-deletion message in the codespaces list on GitHub

Setting a retention period for a codespace

To set the codespace retention period when you create a codespace, use the --retention-period flag with the codespace create subcommand. Specify the period in days. The period must be between 0 and 30 days.

gh codespace create --retention-period DAYS

If you don't specify a retention period when you create a codespace, then either your default retention period, or an organization retention period, will be used, depending on which is lower. For information about setting your default retention period, click the "Web browser" tab on this page.

Para aprender más sobre el CLI de GitHub, consulta la sección "Acerca del CLI de GitHub".

Setting the retention period

You can set your default retention period in your web browser, on GitHub.com. Alternatively, if you use CLI de GitHub to create a codespace you can set a retention period for that particular codespace. Para obtener más información, haz clic en la pestaña adecuada arriba.

Checking whether codespaces will be autodeleted soon

You can check, in the Visual Studio Code desktop application, whether a codespace is due to be automatically deleted soon.

  1. En VS Code, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. El icono de explorador remoto en Visual Studio Code

  2. Choose Acerca de GitHub Codespaces from the drop-down menu at the top right of the Remote Explorer, if it is not already selected.

  3. Under "GITHUB CODESPACES," position the mouse pointer over the codespace that you're interested in. A pop-up box is displayed showing you information about the codespace.

    If the codespace is nearing the end of its retention period, a line is included telling you when the codespace will be deleted.

    Codespace information showing the time until deletion