New translation batch for es (#31684)
This commit is contained in:
docubot
@@ -169,6 +169,8 @@ Sets an action's output parameter.
|
||||
|
||||
Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."
|
||||
|
||||
You can escape multiline strings for setting an output parameter by creating an environment variable and using it in a workflow command. For more information, see "[Setting an environment variable](#setting-an-environment-variable)."
|
||||
|
||||
### Example: Setting an output parameter
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Configurar copias de seguridad en tu aparato
|
||||
title: Configuring backups on your appliance
|
||||
shortTitle: Configuring backups
|
||||
redirect_from:
|
||||
- /enterprise/admin/categories/backups-and-restores
|
||||
@@ -14,7 +14,7 @@ redirect_from:
|
||||
- /enterprise/admin/installation/configuring-backups-on-your-appliance
|
||||
- /enterprise/admin/configuration/configuring-backups-on-your-appliance
|
||||
- /admin/configuration/configuring-backups-on-your-appliance
|
||||
intro: 'Como parte de un plan de recuperación ante desastres, puedes proteger los datos de producción en {% data variables.product.product_location %} configurando copias de seguridad automáticas.'
|
||||
intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
@@ -23,162 +23,158 @@ topics:
|
||||
- Enterprise
|
||||
- Fundamentals
|
||||
- Infrastructure
|
||||
ms.openlocfilehash: 4403ec24aa3da63f6700ae4bfcd2392ec0cfd194
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147861656'
|
||||
---
|
||||
## Acerca de {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
## About {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} es un sistema de copias de seguridad que se instala en un host independiente, el cual realiza instantáneas de copias de seguridad de {% data variables.product.product_location %} en intervalos regulares a través de una conexión de red SSH segura. Puedes utilizar una instantánea para restablecer una instancia existente del {% data variables.product.prodname_ghe_server %} a su estado previo desde el host de copias de seguridad.
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.product.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host.
|
||||
|
||||
Solo se transferirán por la red y ocuparán espacio de almacenamiento físico adicional los datos que se hayan agregado después de esa última instantánea. Para minimizar el impacto en el rendimiento, las copias de seguridad se realizan en línea con la prioridad CPU/IO más baja. No necesitas programar una ventana de mantenimiento para realizar una copia de seguridad.
|
||||
Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup.
|
||||
|
||||
Las versiones principales y los números de versión de {% data variables.product.prodname_enterprise_backup_utilities %} se alinean con las versiones de actualización de características de {% data variables.product.product_name %}. Se admiten las cuatro versiones más recientes de ambos productos. Para obtener más información, consulta "[Versiones de {% data variables.product.product_name %}](/admin/all-releases)".
|
||||
Major releases and version numbers for {% data variables.product.prodname_enterprise_backup_utilities %} align with feature releases of {% data variables.product.product_name %}. We support the four most recent versions of both products. For more information, see "[{% data variables.product.product_name %} releases](/admin/all-releases)."
|
||||
|
||||
Para obtener información más detallada sobre las características, los requisitos y el uso avanzado, consulta el archivo [README de {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme) en la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
For more detailed information on features, requirements, and advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## Prerrequisitos
|
||||
## Prerequisites
|
||||
|
||||
Para utilizar {% data variables.product.prodname_enterprise_backup_utilities %}, debe tener un sistema de host Linux o Unix independiente de {% data variables.product.product_location %}.
|
||||
To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.product.product_location %}.
|
||||
|
||||
También puedes incorporar {% data variables.product.prodname_enterprise_backup_utilities %} en un entorno existente para almacenar los datos críticos de manera permanente y a largo plazo.
|
||||
You can also integrate {% data variables.product.prodname_enterprise_backup_utilities %} into an existing environment for long-term permanent storage of critical data.
|
||||
|
||||
Recomendamos que exista una distancia geográfica entre el host de copias de seguridad y {% data variables.product.product_location %}. Esto asegura que las copias de seguridad estén disponibles para su recuperación en el caso de que ocurra un desastre significativo o una interrupción de red en el sitio principal.
|
||||
We recommend that the backup host and {% data variables.product.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site.
|
||||
|
||||
Los requisitos de almacenamiento físico variarán en función del uso del disco del repositorio de Git y de los patrones de crecimiento esperados:
|
||||
Physical storage requirements will vary based on Git repository disk usage and expected growth patterns:
|
||||
|
||||
| Hardware | Recomendación |
|
||||
| Hardware | Recommendation |
|
||||
| -------- | --------- |
|
||||
| **vCPU** | 2 |
|
||||
| **Memoria** | 2 GB |
|
||||
| **Storage** | Cinco veces el almacenamiento asignado de la instancia principal |
|
||||
| **vCPUs** | 2 |
|
||||
| **Memory** | 2 GB |
|
||||
| **Storage** | Five times the primary instance's allocated storage |
|
||||
|
||||
Es posible que se requieran más recursos según su uso, como la actividad del usuario y las integraciones seleccionadas.
|
||||
More resources may be required depending on your usage, such as user activity and selected integrations.
|
||||
|
||||
Para obtener más información, consulta [los requisitos de {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils/blob/master/docs/requirements.md) en la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %} requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## Instalar {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
## Installing {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
|
||||
Para instalar {% data variables.product.prodname_enterprise_backup_utilities %} en el host de copia de seguridad, se recomienda clonar el repositorio Git del proyecto. Este enfoque permite capturar nuevas versiones directamente mediante Git y el archivo de configuración de copia de seguridad existente, `backup.config`, se conservará al instalar una nueva versión.
|
||||
To install {% data variables.product.prodname_enterprise_backup_utilities %} on your backup host, we recommend cloning the project's Git repository. This approach allows you to fetch new releases directly using Git, and your existing backup configuration file, `backup.config`, will be preserved when installing a new version.
|
||||
|
||||
Como alternativa, si el equipo host no puede acceder a Internet, puedes descargar cada versión de {% data variables.product.prodname_enterprise_backup_utilities %} como archivo comprimido y, después, extraer e instalar el contenido. Para obtener más información, consulta [Introducción](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) de la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
Alternatively, if the host machine can't access the internet, you can download each {% data variables.product.prodname_enterprise_backup_utilities %} release as a compressed archive, then extract and install the contents. For more information, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
Las instantáneas de copia de seguridad se escriben en la ruta de acceso del disco establecida por la variable de directorio de datos `GHE_DATA_DIR` del archivo `backup.config`. Las instantáneas deben almacenarse en un sistema de archivos que admita vínculos simbólicos y físicos.
|
||||
Backup snapshots are written to the disk path set by the `GHE_DATA_DIR` data directory variable in your `backup.config` file. Snapshots need to be stored on a filesystem which supports symbolic and hard links.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Se recomienda asegurarse de que las instantáneas no se mantienen en un subdirectorio del directorio de instalación de {% data variables.product.prodname_enterprise_backup_utilities %} para evitar sobrescribir accidentalmente el directorio de datos al actualizar las versiones de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
**Note:** We recommend ensuring your snapshots are not kept in a subdirectory of the {% data variables.product.prodname_enterprise_backup_utilities %} installation directory, to avoid inadvertently overwriting your data directory when upgrading {% data variables.product.prodname_enterprise_backup_utilities %} versions.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Ejecuta el siguiente comando para clonar el [repositorio del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils/) en un directorio local del host de copia de seguridad.
|
||||
1. To clone the [{% data variables.product.prodname_enterprise_backup_utilities %} project repository](https://github.com/github/backup-utils/) to a local directory on your backup host, run the following command.
|
||||
|
||||
```
|
||||
$ git clone https://github.com/github/backup-utils.git /path/to/target/directory/backup-utils
|
||||
```
|
||||
1. Ejecuta el siguiente comando para cambiar al directorio del repositorio local.
|
||||
1. To change into the local repository directory, run the following command.
|
||||
|
||||
```
|
||||
cd backup-utils
|
||||
```
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
|
||||
1. Ejecuta el siguiente comando para copiar el archivo `backup.config-example` incluido en `backup.config`.
|
||||
1. To copy the included `backup.config-example` file to `backup.config`, run the following command.
|
||||
|
||||
```shell
|
||||
cp backup.config-example backup.config
|
||||
```
|
||||
1. Para personalizar la configuración, edita `backup.config` en un editor de texto.
|
||||
1. Establezca el valor `GHE_HOSTNAME` en la dirección IP o el nombre del host de su instancia principal de {% data variables.product.prodname_ghe_server %}.
|
||||
1. To customize your configuration, edit `backup.config` in a text editor.
|
||||
1. Set the `GHE_HOSTNAME` value to your primary {% data variables.product.prodname_ghe_server %} instance's hostname or IP address.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Si {% data variables.product.product_location %} se implementa como un clúster o en una configuración de alta disponibilidad utilizando un equilibrador de carga, el `GHE_HOSTNAME` puede ser el nombre de host del equilibrador de carga siempre y cuando permita acceso por SSH a {% data variables.product.product_location %} (por el puerto 122).
|
||||
**Note:** If {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}.
|
||||
|
||||
Para garantizar que un dispositivo recuperado esté disponible de inmediato, realiza copias de seguridad centradas en la instancia principal, incluso en una configuración de replicación geográfica.
|
||||
To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a geo-replication configuration.
|
||||
|
||||
{% endnote %}
|
||||
1. Establezca el valor `GHE_DATA_DIR` para la ubicación del sistema de archivos en la que quiera almacenar las instantáneas de copias de seguridad. Se recomienda elegir una ubicación en el mismo sistema de archivos que el host de copia de seguridad, pero fuera de donde se clonó el repositorio Git en el paso 1.
|
||||
1. Para conceder acceso al host de copia de seguridad a la instancia, abre la página de configuración de la instancia principal en `http(s)://HOSTNAME/setup/settings` y agrega la clave SSH del host de copia de seguridad a la lista de claves SSH autorizadas. Para obtener más información, consulte"[Acceso al shell administrativo (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)".
|
||||
1. En el host de copia de seguridad, comprueba la conectividad SSH con {% data variables.product.product_location %} con el comando `ghe-host-check`.
|
||||
1. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots. We recommend choosing a location on the same filesystem as your backup host, but outside of where you cloned the Git repository in step 1.
|
||||
1. To grant your backup host access to your instance, open your primary instance's settings page at `http(s)://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)."
|
||||
1. On your backup host, verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command.
|
||||
|
||||
```shell
|
||||
./bin/ghe-host-check
|
||||
```
|
||||
1. Ejecuta el siguiente comando para crear una copia de seguridad completa inicial.
|
||||
```
|
||||
1. To create an initial full backup, run the following command.
|
||||
|
||||
```shell
|
||||
./bin/ghe-backup
|
||||
```
|
||||
|
||||
Para obtener más información sobre el uso avanzado, consulta el archivo [README de {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme) en la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
For more information on advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## Actualizar {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
## Upgrading {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
|
||||
Al actualizar {% data variables.product.prodname_enterprise_backup_utilities %}, debes elegir una versión que funcione con la versión actual de {% data variables.product.product_name %}. La versión instalada de {% data variables.product.prodname_enterprise_backup_utilities %} debe ser, al menos, la misma que la de {% data variables.product.product_location %} y no puede ser más de dos versiones posteriores. Para obtener más información, consulta [los requisitos de la versión de {% data variables.product.prodname_ghe_server %}](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) en la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
Puedes actualizar {% data variables.product.prodname_enterprise_backup_utilities %} en un repositorio Git mediante la captura y extracción del repositorio de los cambios más recientes.
|
||||
When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.product.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
You can upgrade {% data variables.product.prodname_enterprise_backup_utilities %} in a Git repository by fetching and checking out the latest changes.
|
||||
|
||||
Como alternativa, si no usas un repositorio Git para la instalación, puedes extraer un nuevo archivo o cambiar el enfoque para usar un repositorio Git en su lugar.
|
||||
Alternatively, if you don't use a Git repository for your installation, you can extract a new archive into place, or you can change your approach to use a Git repository instead.
|
||||
|
||||
### Comprobación del tipo de instalación
|
||||
### Verifying the installation type
|
||||
|
||||
Puedes comprobar el método de instalación de {% data variables.product.prodname_enterprise_backup_utilities %} y determinar la mejor manera de actualizar la versión instalada.
|
||||
You can verify the installation method for {% data variables.product.prodname_enterprise_backup_utilities %} and determine the best way to upgrade your installation.
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
|
||||
1. Ejecuta el siguiente comando para comprobar si existe un directorio de trabajo válido dentro de un repositorio Git.
|
||||
1. To check if a valid working directory exists inside a Git repository, run the following command.
|
||||
|
||||
```
|
||||
git rev-parse --is-inside-work-tree
|
||||
```
|
||||
|
||||
Si la salida es `true`, {% data variables.product.prodname_enterprise_backup_utilities %} se instaló mediante la clonación del repositorio Git del proyecto. Si la salida incluye `fatal: not a git repository (or any of the parent directories)`, es probable que {% data variables.product.prodname_enterprise_backup_utilities %} se instalase extrayendo un archivo de archivo comprimido.
|
||||
Si la instalación está en un repositorio Git, puedes instalar la versión más reciente mediante Git. Si la instalación procede de un archivo comprimido, puedes descargar y extraer la versión más reciente, o bien puedes volver a instalar {% data variables.product.prodname_enterprise_backup_utilities %} mediante Git para simplificar las actualizaciones futuras.
|
||||
If the output is `true`, {% data variables.product.prodname_enterprise_backup_utilities %} was installed by cloning the project's Git repository. If the output includes `fatal: not a git repository (or any of the parent directories)`, {% data variables.product.prodname_enterprise_backup_utilities %} was likely installed by extracting a compressed archive file.
|
||||
If your installation is in a Git repository, you can install the latest version using Git. If the installation is from a compressed archive file, you can either download and extract the latest version, or you can reinstall {% data variables.product.prodname_enterprise_backup_utilities %} using Git to simplify future upgrades.
|
||||
|
||||
- [Actualización de una instalación en un repositorio Git](#upgrading-an-installation-in-a-git-repository)
|
||||
- [Uso de Git en lugar de archivos comprimidos para actualizaciones](#using-git-instead-of-compressed-archives-for-upgrades)
|
||||
- [Upgrading an installation in a Git repository](#upgrading-an-installation-in-a-git-repository)
|
||||
- [Using Git instead of compressed archives for upgrades](#using-git-instead-of-compressed-archives-for-upgrades)
|
||||
|
||||
### Actualización de una instalación en un repositorio Git
|
||||
### Upgrading an installation in a Git repository
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %} {% note %}
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
|
||||
{% note %}
|
||||
|
||||
**Nota:** Se recomienda crear una copia del archivo `backup.config` existente en una ubicación temporal, como `$HOME/backup.config`, antes de actualizar {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
**Note:** We recommend creating a copy of your existing `backup.config` file in a temporary location, like `$HOME/backup.config`, before upgrading {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Descarga las actualizaciones más recientes del proyecto mediante la ejecución del comando `git fetch`.
|
||||
1. Download the latest project updates by running the `git fetch` command.
|
||||
|
||||
```shell
|
||||
git fetch
|
||||
```
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %} {% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
|
||||
|
||||
### Uso de Git en lugar de archivos comprimidos para actualizaciones
|
||||
### Using Git instead of compressed archives for upgrades
|
||||
|
||||
Si el host de copia de seguridad tiene conectividad a Internet y se usó previamente un archivo comprimido (`.tar.gz`) para instalar o actualizar {% data variables.product.prodname_enterprise_backup_utilities %}, se recomienda usar un repositorio Git para la instalación en su lugar. La actualización mediante Git requiere menos trabajo y conserva la configuración de copia de seguridad.
|
||||
If your backup host has internet connectivity and you previously used a compressed archive (`.tar.gz`) to install or upgrade {% data variables.product.prodname_enterprise_backup_utilities %}, we recommend using a Git repository for your installation instead. Upgrading using Git requires less work and preserves your backup configuration.
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
|
||||
1. Para realizar una copia de seguridad de la configuración de {% data variables.product.prodname_enterprise_backup_utilities %} existente, copia el archivo `backup.config` actual en una ubicación segura, como el directorio principal.
|
||||
1. To back up your existing {% data variables.product.prodname_enterprise_backup_utilities %} configuration, copy your current `backup.config` file to a safe location, such as your home directory.
|
||||
|
||||
```
|
||||
$ cp backup.config $HOME/backup.config.saved-$(date +%Y%m%d-%H%M%S)
|
||||
```
|
||||
|
||||
1. Cambia al directorio local del host de copia de seguridad donde deseas instalar el repositorio Git {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
1. Ejecuta el siguiente comando para clonar el [repositorio del proyecto](https://github.com/github/backup-utils/) en el directorio del host de copia de seguridad.
|
||||
1. Change to the local directory on your backup host where you want to install the {% data variables.product.prodname_enterprise_backup_utilities %} Git repository.
|
||||
1. To clone the [project repository](https://github.com/github/backup-utils/) to the directory on your backup host, run the following command.
|
||||
|
||||
```
|
||||
git clone https://github.com/github/backup-utils.git
|
||||
```
|
||||
1. Ejecuta el siguiente comando para cambiar al repositorio clonado.
|
||||
1. To change into the cloned repository, run the following command.
|
||||
|
||||
```
|
||||
cd backup-utils
|
||||
```
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
|
||||
1. Para restaurar la configuración de copia de seguridad anterior, copia el archivo de configuración de copia de seguridad existente en el directorio del repositorio local. Reemplaza la ruta de acceso del comando por la ubicación del archivo guardado en el paso 2.
|
||||
1. To restore your backup configuration from earlier, copy your existing backup configuration file to the local repository directory. Replace the path in the command with the location of the file saved in step 2.
|
||||
|
||||
```
|
||||
$ cp PATH/TO/BACKUP/FROM/STEP/2 backup.config
|
||||
@@ -186,44 +182,44 @@ Si el host de copia de seguridad tiene conectividad a Internet y se usó previam
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Puedes elegir dónde restaurar el archivo de configuración de copia de seguridad después de la clonación. Para obtener más información sobre dónde se pueden encontrar los archivos de configuración, consulta [Introducción](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) en la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
**Note:** You can choose where to restore your backup configuration file to after cloning. For more information about where configuration files can be located, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Revisa el archivo en un editor de texto para confirmar que las rutas de acceso a directorios o scripts del archivo de configuración de copia de seguridad son correctas.
|
||||
1. To confirm that the paths to directories or scripts in your backup configuration file are correct, review the file in a text editor.
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
|
||||
1. Elimina el antiguo directorio de GitHub Enterprise Server Backup Utilities del paso 1 (donde se encuentra la instalación del archivo comprimido).
|
||||
1. Delete your old GitHub Enterprise Server Backup Utilities directory from step 1 (where the compressed archive installation was located).
|
||||
|
||||
## Programar una copia de seguridad
|
||||
## Scheduling a backup
|
||||
|
||||
Puede programar copias de seguridad con una determinada frecuencia en el host de copia de seguridad utilizando el comando `cron(8)` o un servicio de programación mediante comando similar. La frecuencia de copias de seguridad configurada dictará el peor caso de Punto Objetivo de Recuperación (RPO) de tu plan de recuperación. Por ejemplo, si has programado que la copia de seguridad se ejecute todos los días a la medianoche, podrías perder hasta 24 horas de datos en un escenario de desastre. Recomendamos comenzar con un cronograma de copias de seguridad por hora, que garantice un peor caso máximo de una hora de pérdida de datos, si los datos del sitio principal se destruyen.
|
||||
You can schedule regular backups on the backup host using the `cron(8)` command or a similar command scheduling service. The configured backup frequency will dictate the worst case recovery point objective (RPO) in your recovery plan. For example, if you have scheduled the backup to run every day at midnight, you could lose up to 24 hours of data in a disaster scenario. We recommend starting with an hourly backup schedule, guaranteeing a worst case maximum of one hour of data loss if the primary site data is destroyed.
|
||||
|
||||
Si los intentos de copias de seguridad se superponen, el comando `ghe-backup` se detendrá con un mensaje de error que indicará la existencia de una copia de seguridad simultánea. Si esto ocurre, recomendamos que disminuyas la frecuencia de tus copias de seguridad programadas. Para obtener más información, consulta la sección sobre programar copias de seguridad del archivo [README de {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#scheduling-backups) en la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
If backup attempts overlap, the `ghe-backup` command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## Restauración de una copia de seguridad
|
||||
## Restoring a backup
|
||||
|
||||
En el caso de una interrupción de red prolongada o de un evento catastrófico en el sitio principal, puede restablecer {% data variables.product.product_location %} proporcionando otro dispositivo para {% data variables.product.prodname_enterprise %} y realizando un restablecimiento desde el host de copias de seguridad. Debes agregar la clave SSH del host de copias de seguridad en el aparato objetivo {% data variables.product.prodname_enterprise %} como una clave SSH autorizada antes de restablecer un aparato.
|
||||
In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Cuando realice restauraciones de copias de seguridad en {% data variables.product.product_location %}, se aplicarán las mismas reglas de compatibilidad de versión. Solo puedes restablecer datos de por lo mucho dos lanzamientos de características anteriores.
|
||||
**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind.
|
||||
|
||||
Por ejemplo, si haces una copia de seguridad de {% data variables.product.product_name %} 3.0.x, puedes restaurar la copia de seguridad en una instancia de {% data variables.product.product_name %} 3.2.x. No se pueden restaurar datos desde una copia de seguridad de {% data variables.product.product_name %} 2.22.x a una instancia que ejecute 3.2.x, ya que serían tres saltos entre versiones (de 2.22 a 3.0, a 3.1 y finalmente a 3.2). Primero necesitarías restablecer a una instancia que ejecute 3.1.x y luego actualizar a 3.2.x.
|
||||
For example, if you take a backup from {% data variables.product.product_name %} 3.0.x, you can restore the backup to a {% data variables.product.product_name %} 3.2.x instance. You cannot restore data from a backup of {% data variables.product.product_name %} 2.22.x to an instance running 3.2.x, because that would be three jumps between versions (2.22 to 3.0 to 3.1 to 3.2). You would first need to restore to an instance running 3.1.x, and then upgrade to 3.2.x.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Para restaurar {% data variables.product.product_location %} desde la última instantánea correcta, use el comando `ghe-restore`.
|
||||
To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Antes de restaurar una copia de seguridad, asegúrate de que:
|
||||
- El modo de mantenimiento está habilitado en la instancia principal y se han completado todos los procesos activos. Para más información, vea "[Habilitación del modo de mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)".
|
||||
- La replicación se ha detenido en todas las réplicas en configuraciones de alta disponibilidad. Para obtener más información, consulta el comando `ghe-repl-stop` en "[Acerca de la configuración de alta disponibilidad](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)".
|
||||
- Si {% data variables.product.product_location %} tiene habilitadas las {% data variables.product.prodname_actions %}, primero deberás configurar el proveedor de almacenamiento externo de {% data variables.product.prodname_actions %} en el dispositivo de repuesto. Para obtener más información, consulte "[Copia de seguridad y restauración de {% data variables.product.prodname_ghe_server %} con {% data variables.product.prodname_actions %} habilitado](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)".
|
||||
**Note:** Prior to restoring a backup, ensure:
|
||||
- Maintenance mode is enabled on the primary instance and all active processes have completed. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
|
||||
- Replication is stopped on all replicas in high availability configurations. For more information, see the `ghe-repl-stop` command in "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)."
|
||||
- If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Al ejecutar el comando `ghe-restore`, deberías ver un resultado similar al siguiente:
|
||||
When running the `ghe-restore` command, you should see output similar to this:
|
||||
|
||||
```shell
|
||||
$ ghe-restore -c 169.154.1.1
|
||||
@@ -242,15 +238,20 @@ $ ghe-restore -c 169.154.1.1
|
||||
> Visit https://169.154.1.1/setup/settings to review appliance configuration.
|
||||
```
|
||||
|
||||
{% ifversion ip-exception-list %} Opcionalmente, para validar la restauración, configura una lista de excepciones IP para permitir el acceso a una lista específica de direcciones IP. Para obtener más información, consulta "[Validación de cambios en el modo de mantenimiento mediante la lista de excepciones de IP](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)".
|
||||
{% ifversion ip-exception-list %}
|
||||
Optionally, to validate the restore, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)."
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** La configuración de red se excluye de la instantánea de copia de seguridad. Debes configurar manualmente la red en el aparato objetivo para el {% data variables.product.prodname_ghe_server %} como obligatoria para tu entorno.
|
||||
**Note:**
|
||||
|
||||
- The network settings are excluded from the backup snapshot. You must manually configure the network on the target {% data variables.product.prodname_ghe_server %} appliance as required for your environment.
|
||||
|
||||
- When restoring to new disks on an existing or empty {% data variables.product.prodname_ghe_server %} instance, stale UUIDs may be present, resulting in Git and/or Alambic replication reporting as out of sync. Stale server entry IDs can be the result of a retired node in a high availability configuration still being present in the application database, but not in the restored replication configuration. To remediate, stale UUIDs can be torn down using `ghe-repl-teardown` once the restore has completed and prior to starting replication. In this scenario, contact {% data variables.contact.contact_ent_support %} for further assistance.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Puede usar estas opciones adicionales con el comando `ghe-restore`:
|
||||
- La marca `-c` sobrescribe los ajustes, el certificado y los datos de licencia en el host objetivo, incluso si este ya está configurado. Omite esta marca si estás configurando una instancia de preparación con fines de prueba y si quieres conservar la configuración existente en el objetivo. Para obtener más información, consulta la sección sobre el uso de comandos de copia de seguridad y restauración del archivo [README de {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#using-the-backup-and-restore-commands) en la documentación del proyecto de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
- La marca `-s` le permite seleccionar una instantánea de copia de seguridad diferente.
|
||||
You can use these additional options with `ghe-restore` command:
|
||||
- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
- The `-s` flag allows you to select a different backup snapshot.
|
||||
|
||||
@@ -93,7 +93,7 @@ Optionally, if you use {% data variables.product.prodname_registry %} on your pr
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance.
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_registry %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -128,7 +128,7 @@ Optionally, if you use {% data variables.product.prodname_registry %} on your pr
|
||||
|
||||
Use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
|
||||
If the staging instance is already configured and you're about to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation.
|
||||
If the staging instance is already configured and you want to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation.
|
||||
|
||||
### 6. Review the instance's configuration
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ Jobs that run on Windows and macOS runners that {% data variables.product.prodna
|
||||
|
||||
The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
|
||||
|
||||
If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes each job uses up to the nearest minute.
|
||||
If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -3,6 +3,7 @@ title: About billing for GitHub Codespaces
|
||||
shortTitle: About billing
|
||||
intro: 'View pricing and see how to manage {% data variables.product.prodname_github_codespaces %} billing for your organization.'
|
||||
permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -13,40 +14,105 @@ topics:
|
||||
- Billing
|
||||
redirect_from:
|
||||
- /billing/managing-billing-for-github-codespaces/about-billing-for-codespaces
|
||||
- /github/developing-online-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/understanding-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md
|
||||
---
|
||||
|
||||
## {% data variables.product.prodname_github_codespaces %} pricing
|
||||
|
||||
Charges are incurred for the use of {% data variables.product.prodname_github_codespaces %} for repositories owned by organization and enterprise accounts on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %}. These accounts do not include any free minutes or storage for {% data variables.product.prodname_github_codespaces %}. Repositories in personal accounts are not currently billed for {% data variables.product.prodname_github_codespaces %} usage.
|
||||
Charges are incurred for the use of {% data variables.product.prodname_github_codespaces %} for repositories owned by organization and enterprise accounts on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %}. These accounts do not include any free minutes or storage for {% data variables.product.prodname_github_codespaces %}. Personal accounts are not currently billed for {% data variables.product.prodname_github_codespaces %} usage.
|
||||
|
||||
A {% data variables.product.prodname_github_codespaces %} instance (a "codespace") incurs charges for compute time, while it is active, and for the amount of storage it uses on disk.
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} usage is billed according to the units of measure in the following table:
|
||||
|
||||
| Product | SKU | Unit of measure | Price |
|
||||
| ------------------- | -------- | --------------- | ----- |
|
||||
| Codespaces Compute | 2 core | 1 hour | $0.18 |
|
||||
| | 4 core | 1 hour | $0.36 |
|
||||
| | 8 core | 1 hour | $0.72 |
|
||||
| | 16 core | 1 hour | $1.44 |
|
||||
| | 32 core | 1 hour | $2.88 |
|
||||
| Codespaces Storage | Storage | 1 GB-month | $0.07 |
|
||||
| Component | Machine type | Unit of measure | Price |
|
||||
| ------------------- | ------------ | --------------- | ----- |
|
||||
| Codespaces compute | 2 core | 1 hour | $0.18 |
|
||||
| | 4 core | 1 hour | $0.36 |
|
||||
| | 8 core | 1 hour | $0.72 |
|
||||
| | 16 core | 1 hour | $1.44 |
|
||||
| | 32 core | 1 hour | $2.88 |
|
||||
| Codespaces storage | Storage | 1 GB-month<sup>*</sup> | $0.07 |
|
||||
|
||||
<sup>*</sup> See "[Billing for storage usage](#billing-for-storage-usage)" below for details of the GB-month unit of measure.
|
||||
|
||||
If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[Billing for {% data variables.product.prodname_codespaces %} prebuilds](#billing-for-codespaces-prebuilds)."
|
||||
|
||||
## About billing for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-billing %}
|
||||
{% data variables.product.prodname_github_codespaces %} is billed in US dollars (USD) according to their compute and storage usage. {% data reusables.codespaces.codespaces-monthly-billing %} xxx
|
||||
|
||||
Your {% data variables.product.prodname_github_codespaces %} usage shares your organization or enterprise account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
|
||||
Your {% data variables.product.prodname_github_codespaces %} usage shares your organization or enterprise account's existing payment method, and receipt. For more information, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_codespaces %}
|
||||
### Billing for compute usage
|
||||
The compute usage of a codespace is the number of minutes for which that codespace is active. Total compute usage is calculated by summing the number of minutes used by all codespaces that are billable to the organization or enterprise. These totals are reported to the billing service every hour, and are billed monthly.
|
||||
|
||||
As an example, if a codespace is active for 1 hour and 15 minutes, then the compute cost will be the hourly cost of the codespace, as determined by its machine type, multiplied by 1.25.
|
||||
|
||||
You can restrict compute usage by stopping your codespaces. For information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)." Codespaces are stopped automatically after a configurable period of inactivity. The timeout period can be configured by the user, or at the organization level. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
|
||||
### Billing for storage usage
|
||||
For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all storage used by all codespaces and prebuilds in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. Storage is billed for all of your existing codespaces, regardless of whether they are active or stopped. The storage billing for a codespace ends when it is deleted.
|
||||
|
||||
Codespace storage is reported in GB-months. Your billing month runs from a fixed day in one month until the same day in the next month. In most cases the day of the month is determined by the day you started on your current {% data variables.product.prodname_dotcom %} plan. Your GB-month storage, is calculated as follows. Once every hour, the storage used by all of your currently active and stopped codespaces is assessed. This figure is then divided by the number of hours in the current billing month: `total storage size / hours this month`. The result is added to the running total for codespace storage for the month.
|
||||
|
||||
For example, if you have one codespace that uses 100 GB of storage and has existed for one hour you will have used `100 / (24 * 30) = 0.1388` GB-months of storage in a 30-day month. If your use of GitHub Codespaces during a 30-day month consists of two 100 GB codespaces that both existed for three full days then there will be `24 * 3` hourly reports for the storage of these codespaces, giving a total of: `(24 * 3) * 200 / (24 * 30) = 20` GB-months.
|
||||
|
||||
For each hourly report, the storage usage for the previous hour is calculated in seconds. As a result, you won't be charged for a full hour of storage if a codespace did not exist for the full 60 minutes. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB.
|
||||
|
||||
As an organization owner, you can:
|
||||
- List the currently active and stopped codespaces for your organization. For more information, see "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)." In addition to the cost of these codespaces, the cost of {% data variables.product.prodname_github_codespaces %} for the current month may include costs for codespaces that existed earlier in the current month but have since been deleted.
|
||||
- See the total {% data variables.product.prodname_github_codespaces %} compute and storage usage for your organization for the current month to date. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
- Configure your organization settings to manage the cost of {% data variables.product.prodname_github_codespaces %}. For more information, see "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)."
|
||||
|
||||
To estimate the costs for metered services, you can use the {% data variables.product.prodname_dotcom %} [pricing calculator](https://github.com/pricing/calculator?feature=codespaces).
|
||||
|
||||
### Billing for {% data variables.product.prodname_codespaces %} prebuilds
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-default %}
|
||||
{% data reusables.codespaces.prebuilds-definition %} For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-reducing %}
|
||||
#### {% data variables.product.prodname_actions %} costs for prebuilds
|
||||
|
||||
Prebuilds are created and updated by running a {% data variables.product.prodname_actions %} workflow on a {% data variables.product.prodname_dotcom %}-hosted runner. By default, prebuilds are updated every time you modify the prebuild configuration, or push changes to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." There is no associated {% data variables.product.prodname_codespaces %} compute cost for creating or updating prebuilds.
|
||||
|
||||
To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of previous versions of each prebuild that are retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
If you are an organization or enterprise owner, you can track usage of prebuild workflows and storage by downloading a usage report for your organization or enterprise. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create {% data variables.product.prodname_github_codespaces %} Prebuilds." For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)."
|
||||
|
||||
#### Storage costs for prebuilds
|
||||
|
||||
In addition to {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuilds associated with each prebuild configuration for a given repository and region. Storage of prebuilds is billed at the same rate as storage of codespaces.
|
||||
|
||||
The storage cost for a prebuild in a single region will be similar to the storage cost that will be incurred for storing a single codespace created from that prebuild. The storage cost for the generated codespace may be more than the cost for the prebuild if, for example, the `updateContentCommand` and `postCreateCommand` commands are used during codespace creation to download more files to the dev container.
|
||||
|
||||
The total storage costs associated with a prebuild template will depend on:
|
||||
|
||||
* The price of storage per GB. See the table above.
|
||||
* The size of the generated prebuild in GB.
|
||||
* The number of regions in which the prebuild is available (because a copy of the prebuild is stored in each region).
|
||||
* The number of older versions of the prebuild that are retained.
|
||||
|
||||
The storage cost for a prebuild is therefore calculated as: `price per GB * size (GB) * regions * versions`.
|
||||
|
||||
To limit the storage costs associated with prebuilds, you can choose to create prebuilds only in selected regions, and you can specify the number of older versions of prebuilds that will be retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Prebuilds may be updated several times during a billing month. Newer versions of a prebuild may be larger or smaller than the previous versions. This will affect the storage charges. For details of how storage is calculated during a billing month, see "[Billing for storage usage](#billing-for-storage-usage)" above.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
#### Cost of codespaces created from prebuilds
|
||||
|
||||
Use of codespaces created using prebuilds is charged at the same rate as regular codespaces.
|
||||
|
||||
## Setting a spending limit
|
||||
|
||||
@@ -72,7 +138,7 @@ For example, a user in an organization can fork a repository within that organiz
|
||||
|
||||
## How billing is handled when a repository is transferred
|
||||
|
||||
Usage is billed and reported on every hour. As such, you pay for any usage when a repository is within your organization. When a repository is transferred out of your organization, any codespaces in that repository are removed as part of the transfer process.
|
||||
Usage is calculated every hour. An organization pays for usage of codespaces created from any repository owned by the organization, where the organization settings permit the organization to be billed. For more information, see "[Enabling GitHub Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)." When a repository is transferred out of your organization, ownership and billing responsibility for any codespaces associated with that repository will change accordingly.
|
||||
|
||||
## What happens when users are removed
|
||||
|
||||
|
||||
@@ -11,4 +11,3 @@ children:
|
||||
- /viewing-your-github-codespaces-usage
|
||||
- /managing-spending-limits-for-github-codespaces
|
||||
---
|
||||
|
||||
|
||||
@@ -21,6 +21,8 @@ redirect_from:
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-monthly-billing %}
|
||||
|
||||
Once you've reached your spending limit, your organization or repository will no longer be able to create new codespaces, and won't be able to start existing codespaces. Any existing codespaces that are still running will not be shutdown; if you don't change the spending limit, you will not be charged for the amount that exceeds the limit.
|
||||
|
||||
For more information about pricing for {% data variables.product.prodname_github_codespaces %} usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
@@ -67,4 +69,4 @@ You can disable these notifications anytime by navigating to the bottom of the *
|
||||
## Further reading
|
||||
|
||||
- "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
|
||||
@@ -21,8 +21,21 @@ Organization owners and billing managers can view {% data variables.product.prod
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Under "{% data variables.product.prodname_codespaces %}", view the details of the compute hours and storage used so far this month.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also see and update your current spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
* The costs shown here are the cumulative costs within the current monthly billing period. The metered costs for {% data variables.product.prodname_github_codespaces %} shown on this page are reset to zero at the start of each monthly billing period. Outstanding costs from previous months are not shown.
|
||||
* The figures on this page are updated every hour.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
|
||||
The data used for this report is updated daily.
|
||||
1. Filter the report to show only rows that mention "Codespaces" in the `Product` field.
|
||||
|
||||
|
||||
@@ -38,3 +51,7 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
|
||||
1. Under "{% data variables.product.prodname_codespaces %} monthly usage", view the usage details of each organization in your enterprise account.
|
||||
{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %}
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
|
||||
@@ -14,23 +14,23 @@ shortTitle: Private image registry
|
||||
|
||||
A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more images. There are many examples of registries, such as {% data variables.product.prodname_container_registry %}, {% data variables.product.prodname_npm_registry %}, Azure Container Registry, or DockerHub.
|
||||
|
||||
{% data variables.product.prodname_ghcr_and_npm_registry %} can be configured to allow container images to be pulled seamlessly into {% data variables.product.prodname_github_codespaces %} during codespace creation, without having to provide any authentication credentials. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_github_codespaces %} to access images stored in that registry.
|
||||
{% data variables.packages.prodname_ghcr_and_npm_registry %} can be configured to allow container images to be pulled seamlessly into {% data variables.product.prodname_github_codespaces %} during codespace creation, without having to provide any authentication credentials. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_github_codespaces %} to access images stored in that registry.
|
||||
|
||||
## Accessing images stored in {% data variables.product.prodname_ghcr_and_npm_registry %}
|
||||
## Accessing images stored in {% data variables.packages.prodname_ghcr_and_npm_registry %}
|
||||
|
||||
{% data variables.product.prodname_ghcr_and_npm_registry %} provide the easiest way for {% data variables.product.prodname_github_codespaces %} to consume dev container images.
|
||||
{% data variables.packages.prodname_ghcr_and_npm_registry %} provide the easiest way for {% data variables.product.prodname_github_codespaces %} to consume dev container images.
|
||||
|
||||
For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)".
|
||||
|
||||
### Accessing an image published to the same repository as the codespace
|
||||
|
||||
If you publish a container image to {% data variables.product.prodname_ghcr_or_npm_registry %} in the same repository that the codespace is being launched in, you will automatically be able to fetch that image on codespace creation. You won't have to provide any additional credentials, unless the **Inherit access from repo** option was unselected when the container image was published.
|
||||
If you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %} in the same repository that the codespace is being launched in, you will automatically be able to fetch that image on codespace creation. You won't have to provide any additional credentials, unless the **Inherit access from repo** option was unselected when the container image was published.
|
||||
|
||||
#### Inheriting access from the repository from which an image was published
|
||||
|
||||
By default, when you publish a container image to {% data variables.product.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
|
||||
By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
|
||||
|
||||
This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.product.prodname_ghcr_or_npm_registry %} using a Personal Access Token (PAT).
|
||||
This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a Personal Access Token (PAT).
|
||||
|
||||
If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
|
||||
|
||||
@@ -46,13 +46,13 @@ If you want to allow a subset of an organization's repositories to access a cont
|
||||
|
||||
### Publishing a container image from a codespace
|
||||
|
||||
Seamless access from a codespace to {% data variables.product.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope.
|
||||
Seamless access from a codespace to {% data variables.packages.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope.
|
||||
|
||||
We recommend publishing images via {% data variables.product.prodname_actions %}. For more information, see "[Publishing Docker images](/actions/publishing-packages/publishing-docker-images)" and "[Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages)."
|
||||
|
||||
## Accessing images stored in other container registries
|
||||
|
||||
If you are accessing a container image from a registry that isn't {% data variables.product.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace.
|
||||
If you are accessing a container image from a registry that isn't {% data variables.packages.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace.
|
||||
|
||||
- `<*>_CONTAINER_REGISTRY_SERVER`
|
||||
- `<*>_CONTAINER_REGISTRY_USER`
|
||||
|
||||
@@ -6,7 +6,6 @@ versions:
|
||||
ghec: '*'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
children:
|
||||
- /understanding-billing-for-github-codespaces
|
||||
- /allowing-your-codespace-to-access-a-private-image-registry
|
||||
- /using-github-copilot-in-github-codespaces
|
||||
- /using-the-vs-code-command-palette-in-codespaces
|
||||
|
||||
@@ -1,63 +0,0 @@
|
||||
---
|
||||
title: Understanding billing for GitHub Codespaces
|
||||
intro: 'Learn how your {% data variables.product.prodname_github_codespaces %} usage is billed.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/understanding-billing-for-codespaces
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
- Billing
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
shortTitle: Understanding billing
|
||||
---
|
||||
|
||||
This article explains how billing works for your codespaces, and explains how your organization's billing manager can help.
|
||||
|
||||
## Getting access to {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
Your organization's administrator might limit {% data variables.product.prodname_github_codespaces %} usage to only specific personal accounts. To get access, you will need to contact your billing manager. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
|
||||
|
||||
## How much it costs to use {% data variables.product.prodname_codespaces %}
|
||||
|
||||
To see the pricing for {% data variables.product.prodname_github_codespaces %} usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
|
||||
|
||||
## How your codespace usage is billed
|
||||
|
||||
Your codespace is billed for its compute minutes and for the amount of storage it uses on disk.
|
||||
|
||||
If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)."
|
||||
|
||||
### Understanding what compute minutes are
|
||||
Your codespace is billed for the number of minutes that it's active. If your codespaces window is left idle for 30 minutes, it will automatically shutdown, and compute billing for the codespace will end until you start the codespace again.
|
||||
|
||||
### Understanding how codespace storage is billed
|
||||
For {% data variables.product.prodname_github_codespaces %}, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces.
|
||||
|
||||
## How spending limits work
|
||||
|
||||
Before your organization can use {% data variables.product.prodname_github_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
## Exporting changes when you have reached your spending limit
|
||||
|
||||
{% data reusables.codespaces.exporting-changes %}
|
||||
|
||||
## Checking your current usage and limits
|
||||
If you need to check your current usage or spending limit, contact your organization's billing manager. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
## Codespaces can be automatically deleted
|
||||
|
||||
Your codespace will be automatically deleted when you are removed from an organization or repository.
|
||||
|
||||
## Deleting your unused codespaces
|
||||
|
||||
You can manually delete your codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, you can manually delete files using the terminal or from within {% data variables.product.prodname_vscode %}.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
@@ -71,7 +71,7 @@ If you try to delete a codespace with unpushed git commits, your editor will not
|
||||
|
||||
Codespaces that have been stopped and remain inactive for a specified period of time will be deleted automatically. By default, inactive codespaces are deleted after 30 days, but you can customize your codespace retention period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
|
||||
You will be charged for the storage of all your codespaces. When you delete a codespace, you will no longer be charged.
|
||||
If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)." Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
|
||||
|
||||
@@ -11,12 +11,12 @@ children:
|
||||
- /codespaces-lifecycle
|
||||
- /developing-in-a-codespace
|
||||
- /creating-a-codespace
|
||||
- /deleting-a-codespace
|
||||
- /opening-an-existing-codespace
|
||||
- /using-source-control-in-your-codespace
|
||||
- /using-github-codespaces-for-pull-requests
|
||||
- /stopping-and-starting-a-codespace
|
||||
- /renaming-a-codespace
|
||||
- /deleting-a-codespace
|
||||
- /forwarding-ports-in-your-codespace
|
||||
- /default-environment-variables-for-your-codespace
|
||||
- /connecting-to-a-private-network
|
||||
|
||||
@@ -117,6 +117,6 @@ If you already use {% data variables.product.prodname_vscode_shortname %}, you c
|
||||
## Further reading
|
||||
|
||||
- "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)"
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
- "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)"
|
||||
- "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)"
|
||||
|
||||
@@ -111,4 +111,4 @@ You've successfully created, personalized, and run your first application within
|
||||
## Further reading
|
||||
|
||||
- "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)"
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
|
||||
@@ -19,7 +19,7 @@ topics:
|
||||
|
||||
## About enabling {% data variables.product.prodname_github_codespaces %} for your organization
|
||||
|
||||
Organization owners can control which users in your organization can create and use codespaces at the organization's expense.
|
||||
Organization owners can control which users in your organization can create and use codespaces at the organization's expense. For information about pricing, see "[About billing for GitHub Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
Only people who can clone a repository can create a codespace for that repository. To allow people to create codespaces for repositories owned by your organization, you must:
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ topics:
|
||||
children:
|
||||
- /enabling-github-codespaces-for-your-organization
|
||||
- /listing-the-codespaces-in-your-organization
|
||||
- /managing-billing-for-github-codespaces-in-your-organization
|
||||
- /managing-the-cost-of-github-codespaces-in-your-organization
|
||||
- /managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces
|
||||
- /managing-repository-access-for-your-organizations-codespaces
|
||||
- /reviewing-your-organizations-audit-logs-for-github-codespaces
|
||||
|
||||
@@ -1,62 +0,0 @@
|
||||
---
|
||||
title: Managing billing for GitHub Codespaces in your organization
|
||||
shortTitle: Manage billing
|
||||
intro: 'You can check your {% data variables.product.prodname_github_codespaces %} usage and set usage limits.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
- Billing
|
||||
redirect_from:
|
||||
- /codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
To learn about pricing for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-billing %}
|
||||
|
||||
- As an organization owner or a billing manager, you can manage {% data variables.product.prodname_github_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)
|
||||
- As an organization owner, you can list the currently active and stopped codespaces for your organization. In addition to these codespaces, costs for the current month may include costs for codespaces that existed earlier in the current month but have since been deleted.
|
||||
- For users, there is a guide that explains how billing works: ["Understanding billing for {% data variables.product.prodname_github_codespaces %}"](/codespaces/codespaces-reference/understanding-billing-for-github-codespaces)
|
||||
|
||||
## Usage limits
|
||||
|
||||
You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_github_codespaces %}:
|
||||
|
||||
- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_github_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_github_codespaces %} usage in your organization. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
- **Storage usage:** For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes resources such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_github_codespaces %}, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage"](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
## Disabling or limiting {% data variables.product.prodname_codespaces %}
|
||||
|
||||
You can disable all use of {% data variables.product.prodname_github_codespaces %} that would be billed to your organization. Alternatively, you can specify which organization members or collaborators can use {% data variables.product.prodname_codespaces %} at your organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-disabling-org-billing %}
|
||||
|
||||
You can configure which repositories can be accessed from codespaces created for a particular repository. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
|
||||
|
||||
You can limit the choice of types of machine that are available for codespaces created from repositories owned by your organization. This allows you to prevent people using overly resourced machines for their codespaces, and incurring unnecessary charges. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
|
||||
|
||||
You can also restrict how long a codespace can remain unused before it is automatically deleted. This can help to reduce storage costs for {% data variables.product.prodname_codespaces %}. For more information, see "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)."
|
||||
|
||||
## Deleting unused codespaces
|
||||
|
||||
Your users can delete their own codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
As an organization owner, you can delete any codespace in your organization. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Codespaces are automatically deleted after they have been stopped and have remained inactive for a defined number of days. For more information, see "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)." A codespace can only be manually deleted by the person who created the codespace.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
|
||||
@@ -40,6 +40,8 @@ You can also personalize aspects of your codespace environment by using a public
|
||||
|
||||
For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
|
||||
@@ -14,7 +14,9 @@ redirect_from:
|
||||
|
||||
## Overview
|
||||
|
||||
Prebuilding your codespaces allows you to be more productive and access your codespace faster, particularly if your repository is large or complex and new codespaces currently take more than 2 minutes to start. This is because any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace for your project. Think of a prebuild as a "ready-to-go" template for a codespace.
|
||||
{% data reusables.codespaces.prebuilds-definition %}
|
||||
|
||||
If it currently takes more than 2 minutes to create a codespace for a repository, you are likely to benefit from using prebuilds. This is because, with a prebuild, any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace.
|
||||
|
||||
By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds.
|
||||
|
||||
@@ -28,16 +30,10 @@ To create a prebuild you set up a prebuild configuration. When you save the conf
|
||||
|
||||
When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored.
|
||||
|
||||
As with other Actions workflows, running a prebuild configuration workflow will either consume some of the Actions minutes included with your account, if you have any, or it will incur charges for Actions minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
|
||||
|
||||
When you create a codespace from a prebuild, {% data variables.product.prodname_dotcom %} downloads the existing container snapshot from storage and deploys it on a fresh virtual machine, completing the remaining commands specified in the dev container configuration. Since many operations have already been performed, such as cloning the repository, creating a codespace from a prebuild can be substantially quicker than creating one without a prebuild. This is true where the repository is large and/or `onCreateCommand` commands take a long time to run.
|
||||
|
||||
## About billing for {% data variables.product.prodname_codespaces %} prebuilds
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-default %} For details of {% data variables.product.prodname_github_codespaces %} storage pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-reducing %}
|
||||
|
||||
Use of codespaces created using prebuilds is charged at the same rate as regular codespaces.
|
||||
|
||||
## About pushing changes to prebuild-enabled branches
|
||||
|
||||
By default, each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed Actions workflow run to update the prebuild. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes.
|
||||
|
||||
@@ -61,7 +61,7 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
* The prebuild for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)."
|
||||
* The prebuild for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
|
||||
* Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Referencias y direcciones URL autovinculadas
|
||||
intro: 'Las referencias a las direcciones URL, propuestas, solicitudes de extracción y confirmaciones se acortan automáticamente y se convierten en vínculos.'
|
||||
title: Autolinked references and URLs
|
||||
intro: 'References to URLs, issues, pull requests, and commits are automatically shortened and converted into links.'
|
||||
redirect_from:
|
||||
- /articles/autolinked-references-and-urls
|
||||
- /github/writing-on-github/autolinked-references-and-urls
|
||||
@@ -11,68 +11,68 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Auto linked references
|
||||
ms.openlocfilehash: 6f6548dbe931a7a6adb809aa4e5616db4358c242
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147419693'
|
||||
---
|
||||
## URLs
|
||||
|
||||
{% data variables.product.product_name %} automáticamente crea vínculos desde las direcciones URL estándar.
|
||||
{% data variables.product.product_name %} automatically creates links from standard URLs.
|
||||
|
||||
`Visit https://github.com`
|
||||
|
||||
|
||||
|
||||
|
||||
Para obtener más información sobre la creación de vínculos, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax/#links)".
|
||||
For more information on creating links, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax/#links)."
|
||||
|
||||
## Propuestas y solicitudes de extracción
|
||||
## Issues and pull requests
|
||||
|
||||
Dentro de las conversaciones en {% data variables.product.product_name %}, las referencias a las propuestas y solicitudes de extracción se convierten automáticamente en vínculos acortados.
|
||||
Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Las referencias vinculadas automáticamente no se crean en wikis ni archivos en un repositorio.
|
||||
**Note:** Autolinked references are not created in wikis or files in a repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
| Tipo de referencia | Referencia sin formato | Vínculo corto |
|
||||
| Reference type | Raw reference | Short link |
|
||||
| --- | --- | --- |
|
||||
| Dirección URL de la solicitud de incorporación de cambios o el problema | https://github.com/jlord/sheetsee.js/issues/26 | [#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `#` y número de la solicitud de incorporación de cambios o el problema | #26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `GH-` y número de la solicitud de incorporación de cambios o el problema | GH-26 | [GH-26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `Username/Repository#` y número de la solicitud de incorporación de cambios o el problema | jlord/sheetsee.js#26 | [jlord/sheetsee.js#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `Organization_name/Repository#` y número de la solicitud de incorporación de cambios o el problema | github/linguist#4039 | [github/linguist#4039](https://github.com/github/linguist/pull/4039)
|
||||
| Issue or pull request URL | https://github.com/jlord/sheetsee.js/issues/26 | [#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `#` and issue or pull request number | #26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `GH-` and issue or pull request number | GH-26 | [GH-26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `Username/Repository#` and issue or pull request number | jlord/sheetsee.js#26 | [jlord/sheetsee.js#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `Organization_name/Repository#` and issue or pull request number | github/linguist#4039 | [github/linguist#4039](https://github.com/github/linguist/pull/4039)
|
||||
|
||||
{% ifversion fpt or ghec %} Si referencias una propuesta, una solicitud de cambios o un debate en una lista, la referencia se desplegará para mostrar el título y el estado en su lugar. Para obtener más información sobre las listas de tareas, consulta "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)".
|
||||
{% ifversion fpt or ghec %}
|
||||
If you reference an issue, pull request, or discussion in a list, the reference will unfurl to show the title and state instead. For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
{% endif %}
|
||||
|
||||
## Etiquetas
|
||||
Al hacer referencia a la URL de una etiqueta en Markdown, la etiqueta se representa automáticamente. Solo se representan las etiquetas del mismo repositorio, las direcciones URL que apuntan a una etiqueta de otro repositorio se representan como cualquier [dirección URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls).
|
||||
## Labels
|
||||
When referencing the URL of a label in Markdown, the label is automatically rendered. Only labels of the same repository are rendered, URLs pointing to a label from a different repository are rendered as any [URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls).
|
||||
|
||||
Para encontrar la dirección URL de una etiqueta, navega a la página Etiquetas y haz clic en una etiqueta. Por ejemplo, la dirección URL de la etiqueta "mejora" en nuestro [repositorio de documentación](https://github.com/github/docs/) público es
|
||||
The URL of a label can be found by navigating to the labels page and clicking on a label. For example, the URL of the label "enhancement" in our public [docs repository](https://github.com/github/docs/) is
|
||||
|
||||
```md
|
||||
https://github.com/github/docs/labels/enhancement
|
||||
```
|
||||
{% note %}
|
||||
|
||||
## Confirmar SHA
|
||||
**Note:** If the label name contains a period (`.`), the label will not automatically render from the label URL.
|
||||
|
||||
Las referencias a un hash SHA de confirmación se convertirán automáticamente en enlaces acortados para la confirmación en {% data variables.product.product_name %}.
|
||||
{% endnote %}
|
||||
|
||||
| Tipo de referencia | Referencia sin formato | Vínculo corto |
|
||||
## Commit SHAs
|
||||
|
||||
References to a commit's SHA hash are automatically converted into shortened links to the commit on {% data variables.product.product_name %}.
|
||||
|
||||
| Reference type | Raw reference | Short link |
|
||||
| --- | --- | --- |
|
||||
| Dirección URL de confirmación | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| Commit URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e)
|
||||
| `Username/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
|
||||
## Personalizar enlaces automáticos a recursos externos
|
||||
## Custom autolinks to external resources
|
||||
|
||||
{% data reusables.repositories.autolink-references %}
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)"
|
||||
- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
|
||||
|
||||
@@ -26,14 +26,14 @@ The {% data variables.product.prodname_registry %} registries below **only** use
|
||||
- Apache Maven registry
|
||||
- NuGet registry
|
||||
|
||||
{% ifversion packages-npm-v2 %}For {% data variables.product.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
|
||||
{% ifversion packages-npm-v2 %}For {% data variables.packages.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Granular permissions for user/organization-scoped packages
|
||||
|
||||
Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
|
||||
|
||||
Currently, the {% data variables.product.prodname_ghcr_and_npm_registry %} offer granular permissions for your container image packages.
|
||||
Currently, the {% data variables.packages.prodname_ghcr_and_npm_registry %} offer granular permissions for your container image packages.
|
||||
|
||||
## Visibility and access permissions for container images
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ shortTitle: Access control & visibility
|
||||
|
||||
Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
|
||||
|
||||
Currently, you can only use granular permissions with the {% data variables.product.prodname_ghcr_and_npm_registry %}. Granular permissions are not supported in our other package registries, such as the RubyGems registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
|
||||
Currently, you can only use granular permissions with the {% data variables.packages.prodname_ghcr_and_npm_registry %}. Granular permissions are not supported in our other package registries, such as the RubyGems registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
|
||||
|
||||
For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
|
||||
|
||||
@@ -105,7 +105,7 @@ To further customize access to your container image, see "[Configuring access to
|
||||
{% ifversion fpt or ghec %}
|
||||
## Ensuring {% data variables.product.prodname_github_codespaces %} access to your package
|
||||
|
||||
By default, a codespace can seamlessly access certain packages in the {% data variables.product.prodname_ghcr_and_npm_registry %}, such as those published in the same repository with the **Inherit access** option selected. For more information on which access is automatically configured, see "[Allowing your codespace to access a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-container-registry-and-npm-registry)."
|
||||
By default, a codespace can seamlessly access certain packages in the {% data variables.packages.prodname_ghcr_and_npm_registry %}, such as those published in the same repository with the **Inherit access** option selected. For more information on which access is automatically configured, see "[Allowing your codespace to access a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-container-registry-and-npm-registry)."
|
||||
|
||||
Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Borrar y restablecer un paquete
|
||||
intro: Aprende cómo borrar o restablecer un paquete.
|
||||
title: Deleting and restoring a package
|
||||
intro: Learn how to delete or restore a package.
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
- /github/managing-packages-with-github-packages/deleting-a-package
|
||||
@@ -13,90 +13,88 @@ versions:
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
shortTitle: Delete & restore a package
|
||||
ms.openlocfilehash: 4491e7cd25fbec2a19abb06c552ba0e0d3ac7b24
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147704991'
|
||||
---
|
||||
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %}
|
||||
|
||||
## Soporte para borrado y restablecimiento de paquetes en {% data variables.product.prodname_dotcom %}
|
||||
## Package deletion and restoration support on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
En {% data variables.product.prodname_dotcom %}, si tienes el acceso necesario, puedes borrar:
|
||||
- todo un paquete privado
|
||||
- todo un paquete público, si es que no hay más de 5000 descargas de ninguna versión de este
|
||||
- una versión específica de un paquete privado
|
||||
- una versión específica de un paquete público, si la versión del paquete no tiene más de 5000 descargas
|
||||
On {% data variables.product.prodname_dotcom %} if you have the required access, you can delete:
|
||||
- an entire private package
|
||||
- an entire public package, if there's not more than 5000 downloads of any version of the package
|
||||
- a specific version of a private package
|
||||
- a specific version of a public package, if the package version doesn't have more than 5,000 downloads
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:**
|
||||
- No puedes eliminar un paquete público específico si alguna versión del paquete tiene más de 5000 descargas. Ante este escenario, ponte en contacto con el equipo de [soporte técnico de GitHub](https://support.github.com/contact?tags=docs-packages) para obtener más ayuda.
|
||||
- Cuando borres paquetes públicos, toma en cuenta que podrías dañar proyetos que dependen de ellos.
|
||||
**Note:**
|
||||
- You cannot delete a public package if any version of the package has more than 5,000 downloads. In this scenario, contact [GitHub support](https://support.github.com/contact?tags=docs-packages) for further assistance.
|
||||
- When deleting public packages, be aware that you may break projects that depend on your package.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
En {% data variables.product.prodname_dotcom %}, también puedes restablecer un paquete completo o una versión de paquete si:
|
||||
- Restableces el paquete dentro de los primeros 30 días después de que se borró.
|
||||
- El espacio de nombre del paquete aún se encuentra disponible y no se ha utilizado en un paquete nuevo.
|
||||
On {% data variables.product.prodname_dotcom %}, you can also restore an entire package or package version, if:
|
||||
- You restore the package within 30 days of its deletion.
|
||||
- The same package namespace is still available and not used for a new package.
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
## Soporte de la API de paquetes
|
||||
## Packages API support
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
Puedes utiliza la API de REST para administrar tus paquetes. Para obtener más información, consulta "[API {% data variables.product.prodname_registry %}](/rest/reference/packages)".
|
||||
You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
En el caso de los paquetes que heredan sus permisos y acceso desde repositorios, puedes usar GraphQL para eliminar una versión específica de paquete.{% data reusables.package_registry.no-graphql-to-delete-packages %} Para obtener más información sobre la compatibilidad con GraphQL, consulta «[Eliminación de una versión de un paquete con ámbito de repositorio con GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)».
|
||||
For packages that inherit their permissions and access from repositories, you can use GraphQL to delete a specific package version.{% data reusables.package_registry.no-graphql-to-delete-packages %} For more information about GraphQL support, see "[Deleting a version of a repository-scoped package with GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Permisos necesarios para borrar o restablecer un paquete
|
||||
## Required permissions to delete or restore a package
|
||||
|
||||
En el caso de los paquetes que heredan sus permisos de acceso de los repositorios, puedes borrar un paquete si tienes permisos administrativos en el repositorio.
|
||||
For packages that inherit their access permissions from repositories, you can delete a package if you have admin permissions to the repository.
|
||||
|
||||
Los registros {% data variables.product.prodname_registry %} que se mencionan a continuación **solo** utilizan permisos con ámbito de repositorio:
|
||||
The {% data variables.product.prodname_registry %} registries below **only** use repository-scoped permissions:
|
||||
|
||||
{% ifversion not fpt or ghec %}: Imágenes de Docker en `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %} {% ifversion packages-npm-v2 %}{% else %}: npm{% endif %}
|
||||
- Registro de RubyGems
|
||||
- Registro de Apache maven
|
||||
- Registro de NuGet
|
||||
{% ifversion not fpt or ghec %}- Docker images at `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
|
||||
{% ifversion packages-npm-v2 %}{% else %}- npm{% endif %}
|
||||
- RubyGems registry
|
||||
- Apache Maven registry
|
||||
- NuGet registry
|
||||
|
||||
{% ifversion packages-npm-v2 %}Para {% data variables.product.prodname_ghcr_and_npm_registry %}, puedes optar por permitir que los paquetes estén en el ámbito de un usuario o una organización, o vinculados a un repositorio.{% endif %}
|
||||
{% ifversion packages-npm-v2 %}For {% data variables.packages.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
Para eliminar un paquete que tenga permisos pormenorizados separados de un repositorio, tales como imágenes de contenedor que se almacenan en `https://ghcr.io/OWNER/PACKAGE-NAME` o `https://npm.pkg.github.com/OWNER/PACKAGE-NAME`, debes tener acceso de administrador al paquete. Para más información, vea "[Acerca de los permisos para {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)".
|
||||
To delete a package that has granular permissions separate from a repository, such as container images stored at `https://ghcr.io/OWNER/PACKAGE-NAME` or `https://npm.pkg.github.com/OWNER/PACKAGE-NAME`, you must have admin access to the package. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Borrar la versión de un paquete
|
||||
## Deleting a package version
|
||||
|
||||
### Borrar la versión de un paquete con alcance de repositorio en {% data variables.product.prodname_dotcom %}
|
||||
### Deleting a version of a repository-scoped package on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
Para borrar una versión de un paquete con alcance de repositorio debes tener permisos de administrador en el repositorio al que pertenezca dicho paquete. Para obtener más información, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
To delete a version of a repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.package-settings-option %}
|
||||
5. A la izquierda, haz clic en **Administrar versiones**.
|
||||
5. A la derecha de la versión que quieres eliminar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Eliminar versión**.
|
||||
|
||||
6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **Entiendo las consecuencias y quiero eliminar esta versión**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.package_registry.packages-from-code-tab %}
|
||||
{% data reusables.package_registry.package-settings-option %}
|
||||
5. On the left, click **Manage versions**.
|
||||
5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
|
||||
|
||||
6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
### Borrar una versión de un paquete con alcance de repositorio con GraphQL
|
||||
### Deleting a version of a repository-scoped package with GraphQL
|
||||
|
||||
En el caso de los paquetes que heredan sus permisos y acceso de los repositorios, puedes utilizar a GraphQL para borrar las versiones específicas de estos.
|
||||
For packages that inherit their permissions and access from repositories, you can use the GraphQL to delete a specific package version.
|
||||
|
||||
{% data reusables.package_registry.no-graphql-to-delete-packages %}{% ifversion fpt or ghec %} Sin embargo, puedes usar la API de REST. Para obtener más información, consulta «[API de {% data variables.product.prodname_registry %}](/rest/reference/packages)».{% endif %}
|
||||
{% data reusables.package_registry.no-graphql-to-delete-packages %}{% ifversion fpt or ghec %} You can however use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."{% endif %}
|
||||
|
||||
Usa la mutación `deletePackageVersion` en GraphQL API. Debes usar un token con los ámbitos `read:packages`, `delete:packages` y `repo`. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
|
||||
Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
|
||||
|
||||
En el ejemplo siguiente se muestra cómo eliminar una versión de paquete mediante un elemento `packageVersionId` de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
|
||||
The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
|
||||
|
||||
```shell
|
||||
curl -X POST \
|
||||
@@ -106,136 +104,148 @@ curl -X POST \
|
||||
HOSTNAME/graphql
|
||||
```
|
||||
|
||||
Para encontrar todos los paquetes privados que has publicado en {% data variables.product.prodname_registry %}, junto con los identificadores de versión de los paquetes, puedes usar la conexión `packages` mediante el objeto `repository`. Necesitarás un token con los ámbitos `read:packages` y `repo`. Para obtener más información, consulta la conexión [`packages`](/graphql/reference/objects#repository) o la interfaz [`PackageOwner`](/graphql/reference/interfaces#packageowner).
|
||||
To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface.
|
||||
|
||||
Para obtener más información sobre la mutación `deletePackageVersion`, consulta "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)".
|
||||
For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)."
|
||||
|
||||
No puedes borrar directamente todo un paquete utilizando GraphQL, pero si borras cada versión de un paquete, este ya no se mostrará en {% data variables.product.product_name %}.
|
||||
You cannot directly delete an entire package using GraphQL, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Borrar una versión de un paquete con alcance de usuario en {% data variables.product.prodname_dotcom %}
|
||||
### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
Para eliminar una versión específica de un paquete con ámbito de usuario en {% data variables.product.prodname_dotcom %}, como una imagen de Docker en `ghcr.io`, sigue estos pasos. Para eliminar un paquete completo, consulta "[Eliminación de un paquete de ámbito de usuario completo en {% data variables.product.prodname_dotcom %}](#deleting-an-entire-user-scoped-package-on-github)."
|
||||
To delete a specific version of a user-scoped package on {% data variables.product.prodname_dotcom %}, such as for a Docker image at `ghcr.io`, use these steps. To delete an entire package, see "[Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-user-scoped-package-on-github)."
|
||||
|
||||
Para revisar quién puede eliminar una versión del paquete, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
To review who can delete a package version, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-user-level %} {% data reusables.package_registry.package-settings-option %}
|
||||
5. A la izquierda, haz clic en **Administrar versiones**.
|
||||
5. A la derecha de la versión que quieres eliminar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Eliminar versión**.
|
||||
|
||||
6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **Entiendo las consecuencias y quiero eliminar esta versión**.
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-user-level %}
|
||||
{% data reusables.package_registry.package-settings-option %}
|
||||
5. On the left, click **Manage versions**.
|
||||
5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
|
||||
|
||||
6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
|
||||
|
||||
|
||||
### Borrar una versión de un paquete con alcance de organización en {% data variables.product.prodname_dotcom %}
|
||||
### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
Para eliminar una versión específica de un paquete con ámbito de organización en {% data variables.product.prodname_dotcom %}, como una imagen de Docker en `ghcr.io`, sigue estos pasos.
|
||||
Para eliminar un paquete completo, consulta "[Eliminación de un paquete de ámbito de organización completo en {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)."
|
||||
To delete a specific version of an organization-scoped package on {% data variables.product.prodname_dotcom %}, such as for a Docker image at `ghcr.io`, use these steps.
|
||||
To delete an entire package, see "[Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)."
|
||||
|
||||
Para revisar quién puede elimninar una versión de paquete, consulta "[Permisos necesarios para eliminar o restaurar un paquete](#required-permissions-to-delete-or-restore-a-package)."
|
||||
To review who can delete a package version, see "[Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-org-level %} {% data reusables.package_registry.package-settings-option %}
|
||||
5. A la izquierda, haz clic en **Administrar versiones**.
|
||||
5. A la derecha de la versión que quieres eliminar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Eliminar versión**.
|
||||
|
||||
6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **Entiendo las consecuencias y quiero eliminar esta versión**.
|
||||
 {% endif %}
|
||||
|
||||
## Borrar un paquete completo
|
||||
|
||||
### Borrar un paquete completo con alcance de repositorio en {% data variables.product.prodname_dotcom %}
|
||||
|
||||
Para borrar un paquete completo con alcance de repositorio, debes tener permisos administrativos en el repositorio al que pertenezca dicho paquete. Para obtener más información, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.package-settings-option %}
|
||||
4. En "Zona de peligro", haz clic en **Eliminar este paquete**.
|
||||
5. Para confirmarlo, revisa el mensaje de confirmación, escribe el nombre de tu paquete y haz clic en **Lo entiendo y quiero eliminar este paquete.**
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Borrar un paquete completo con alcance de usuario en {% data variables.product.prodname_dotcom %}
|
||||
|
||||
Para revisar quién puede eliminar un paquete, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-user-level %} {% data reusables.package_registry.package-settings-option %}
|
||||
5. A la izquierda, haz clic en **Opciones**.
|
||||
|
||||
6. En "Zona de peligro", haz clic en **Eliminar este paquete**.
|
||||
|
||||
6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **Entiendo las consecuencias y quiero eliminar este paquete**.
|
||||
|
||||
|
||||
### Borrar un paquete completo con alcance de organización en {% data variables.product.prodname_dotcom %}
|
||||
|
||||
Para revisar quién puede eliminar un paquete, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-org-level %} {% data reusables.package_registry.package-settings-option %}
|
||||
5. A la izquierda, haz clic en **Opciones**.
|
||||
|
||||
6. En "Zona de peligro", haz clic en **Eliminar este paquete**.
|
||||
|
||||
6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **Entiendo las consecuencias y quiero eliminar este paquete**.
|
||||
 {% endif %}
|
||||
|
||||
## Restablecer paquetes
|
||||
|
||||
Puedes restablecer un paquete o versión que hayas borrado si:
|
||||
- Restableces el paquete dentro de los primeros 30 días después de que se borró.
|
||||
- El mismo designador de nombre del paquete y su versión se encuentran disponibles y no se han reutilizado para un paquete nuevo.
|
||||
|
||||
Por ejemplo, si tienes un paquete RubyGems eliminado denominado `octo-package` que tenía como ámbito el repositorio `octo-repo-owner/octo-repo`, solo puedes restaurar el paquete si el espacio de nombres `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` del paquete todavía está disponible y aún no han transcurrido 30 días.
|
||||
|
||||
{% ifversion fpt or ghec %} Para restaurar un paquete eliminado, también debes cumplir uno de estos requisitos de permisos:
|
||||
- Para los paquetes con ámbito de repositorio: tienes permisos de administrador para el repositorio que posee el paquete eliminado.{% ifversion fpt or ghec %}
|
||||
- Para los paquetes con ámbito de cuenta de usuario: el paquete eliminado pertenece a tu cuenta de usuario.
|
||||
- Para los paquetes con ámbito de organización: tienes permisos de administrador para el paquete eliminado en la organización que posee el paquete.{% endif %} {% endif %}
|
||||
|
||||
{% ifversion ghae or ghes %} Para eliminar un paquete, también debes tener permisos de administrador en el repositorio que posee el paquete eliminado.
|
||||
{% data reusables.package_registry.package-settings-from-org-level %}
|
||||
{% data reusables.package_registry.package-settings-option %}
|
||||
5. On the left, click **Manage versions**.
|
||||
5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
|
||||
|
||||
6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
Para obtener más información, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
## Deleting an entire package
|
||||
|
||||
Una vez que se restablezca el paquete, este utilizará el designador de nombre que ya tenía. Si ya no está disponible el mismo designador de nombre del paquete, no podrás restablecerlo. En este caso, para restablecer el paquete que se borró, primero deberás borrar el paquete nuevo que utiliza el designador de nombre del paquete que se borró.
|
||||
### Deleting an entire repository-scoped package on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
### Restablecer un paquete en una organización
|
||||
To delete an entire repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
Puedes restablecer un paquete borrado a través de los ajustes de cuenta de tu organización, siempre y cuando el paquete estuviera en el repositorio que pertenece a esta{% ifversion fpt or ghec %} o tuviera permisos granulares y se le hubiera configurado un alcance para tu cuenta de organización{% endif %}.
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.package_registry.packages-from-code-tab %}
|
||||
{% data reusables.package_registry.package-settings-option %}
|
||||
4. Under "Danger Zone", click **Delete this package**.
|
||||
5. To confirm, review the confirmation message, enter your package name, and click **I understand, delete this package.**
|
||||
|
||||
|
||||
Para revisar quién puede restaurar un paquete en una organización, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
{% ifversion fpt or ghec %}
|
||||
### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %}
|
||||
3. En la izquierda, haga clic en **Packages**.
|
||||
4. En "Paquetes eliminados", junto al paquete que quieres restaurar, haz clic en **Restaurar**.
|
||||
|
||||
5. Para confirmar, escribe el nombre del paquete y haz clic en **Entiendo las consecuencias y quiero restaurar este paquete**.
|
||||
|
||||
To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-user-level %}
|
||||
{% data reusables.package_registry.package-settings-option %}
|
||||
5. On the left, click **Options**.
|
||||
|
||||
6. Under "Danger zone", click **Delete this package**.
|
||||
|
||||
6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
|
||||
|
||||
|
||||
### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-org-level %}
|
||||
{% data reusables.package_registry.package-settings-option %}
|
||||
5. On the left, click **Options**.
|
||||
|
||||
6. Under "Danger zone", click **Delete this package**.
|
||||
|
||||
6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Restoring packages
|
||||
|
||||
You can restore a deleted package or version if:
|
||||
- You restore the package within 30 days of its deletion.
|
||||
- The same package namespace and version is still available and not reused for a new package.
|
||||
|
||||
For example, if you have a deleted RubyGems package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
To restore a deleted package, you must also meet one of these permission requirements:
|
||||
- For repository-scoped packages: You have admin permissions to the repository that owns the deleted package.{% ifversion fpt or ghec %}
|
||||
- For user-account scoped packages: Your personal account owns the deleted package.
|
||||
- For organization-scoped packages: You have admin permissions to the deleted package in the organization that owns the package.{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae or ghes %}
|
||||
To delete a package, you must also have admin permissions to the repository that owns the deleted package.
|
||||
{% endif %}
|
||||
|
||||
For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
Once the package is restored, the package will use the same namespace it did before. If the same package namespace is not available, you will not be able to restore your package. In this scenario, to restore the deleted package, you must delete the new package that uses the deleted package's namespace first.
|
||||
|
||||
### Restoring a package in an organization
|
||||
|
||||
You can restore a deleted package through your organization account settings, as long as the package was in a repository owned by the organizaton{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}.
|
||||
|
||||
To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
3. On the left, click **Packages**.
|
||||
4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
|
||||
|
||||
5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
### Restablecer un paquete con alcance de cuenta de usuario
|
||||
### Restoring a user-account scoped package
|
||||
|
||||
Puedes restaurar un paquete que se haya eliminado mediante la configuración de tu cuenta de usuario, siempre y cuando haya estado en uno de tus repositorios o haya tenido como ámbito tu cuenta de usuario. Para obtener más información, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
You can restore a deleted package through your personal account settings, if the package was in one of your repositories or scoped to your personal account. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. En la izquierda, haga clic en **Packages**.
|
||||
4. En "Paquetes eliminados", junto al paquete que quieres restaurar, haz clic en **Restaurar**.
|
||||
|
||||
5. Para confirmar, escribe el nombre del paquete y haz clic en **Entiendo las consecuencias y quiero restaurar este paquete**.
|
||||
|
||||
2. On the left, click **Packages**.
|
||||
4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
|
||||
|
||||
5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Restablecer la versión de un paquete
|
||||
### Restoring a package version
|
||||
|
||||
Puedes restablecer una versión de paquete desde la página de llegada del mismo. Para revisar quién puede restaurar un paquete, consulta "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)".
|
||||
You can restore a package version from your package's landing page. To review who can restore a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
|
||||
|
||||
1. Navega a la página de llegada de tu paquete.
|
||||
2. A la derecha, haz clic en **Configuración del paquete**.
|
||||
2. A la izquierda, haz clic en **Administrar versiones**.
|
||||
3. A la derecha, usa el menú desplegable "Versiones" y selecciona **Eliminado**.
|
||||
|
||||
4. Junto a la versión del paquete eliminado que quieres restaurar, haz clic en **Restaurar**.
|
||||
|
||||
5. Para confirmarlo, haz clic en **Entiendo las consecuencias y quiero restaurar esta versión.**
|
||||
|
||||
1. Navigate to your package's landing page.
|
||||
2. On the right, click **Package settings**.
|
||||
2. On the left, click **Manage versions**.
|
||||
3. On the top right, use the "Versions" drop-down menu and select **Deleted**.
|
||||
|
||||
4. Next to the deleted package version you want to restore, click **Restore**.
|
||||
|
||||
5. To confirm, click **I understand the consequences, restore this version.**
|
||||
|
||||
|
||||
@@ -51,7 +51,7 @@ For more information about the configuration of {% data variables.product.prodna
|
||||
|
||||
| | |
|
||||
|--------------------|--------------------|
|
||||
| Permissions | {% ifversion fpt or ghec %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_ghcr_and_npm_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |
|
||||
| Permissions | {% ifversion fpt or ghec %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.packages.prodname_ghcr_and_npm_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |
|
||||
| Visibility | {% data reusables.package_registry.public-or-private-packages %} |
|
||||
|
||||
For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
|
||||
|
||||
@@ -31,7 +31,7 @@ Repository-scoped packages inherit their permissions and visibility from the rep
|
||||
- NuGet registry
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
The {% data variables.product.prodname_ghcr_and_npm_registry %} offer you the option of granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account. You can choose to use granular permissions or connect the package to a repository and inherit it's permissions. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
|
||||
The {% data variables.packages.prodname_ghcr_and_npm_registry %} offer you the option of granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account. You can choose to use granular permissions or connect the package to a repository and inherit it's permissions. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
|
||||
{% endif %}
|
||||
|
||||
For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages){% ifversion fpt or ghec %}" and "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility){% endif %}."
|
||||
|
||||
@@ -24,7 +24,7 @@ shortTitle: Publish & install with Actions
|
||||
You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Authenticating to the {% data variables.product.prodname_ghcr_and_npm_registry %}
|
||||
### Authenticating to the {% data variables.packages.prodname_ghcr_and_npm_registry %}
|
||||
|
||||
{% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
|
||||
|
||||
@@ -40,7 +40,7 @@ You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Some registries, such as RubyGems, {% ifversion packages-npm-v2 %}{% else %}npm, {% endif %}Apache Maven, NuGet, {% ifversion fpt or ghec %}and Gradle{% else %}Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`{% endif %}, only allow repository-owned packages. With {% data variables.product.prodname_ghcr_and_npm_registry_full %} you can choose to allow packages to be owned by a user, an organization, or linked to a repository.
|
||||
**Note:** Some registries, such as RubyGems, {% ifversion packages-npm-v2 %}{% else %}npm, {% endif %}Apache Maven, NuGet, {% ifversion fpt or ghec %}and Gradle{% else %}Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`{% endif %}, only allow repository-owned packages. With {% data variables.packages.prodname_ghcr_and_npm_registry_full %} you can choose to allow packages to be owned by a user, an organization, or linked to a repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -49,11 +49,11 @@ When you enable GitHub Actions, GitHub installs a GitHub App on your repository.
|
||||
{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## About permissions and package access for {% data variables.product.prodname_ghcr_and_npm_registry %}
|
||||
## About permissions and package access for {% data variables.packages.prodname_ghcr_and_npm_registry %}
|
||||
|
||||
The {% data variables.product.prodname_ghcr_and_npm_registry_full %} allows users to create and administer packages as free-standing resources at the organization level. Packages can be owned by an organization or personal account and you can customize access to each of your packages separately from repository permissions.
|
||||
The {% data variables.packages.prodname_ghcr_and_npm_registry_full %} allows users to create and administer packages as free-standing resources at the organization level. Packages can be owned by an organization or personal account and you can customize access to each of your packages separately from repository permissions.
|
||||
|
||||
All workflows accessing the {% data variables.product.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
|
||||
All workflows accessing the {% data variables.packages.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
|
||||
|
||||
## Default permissions and access settings for containers modified through workflows
|
||||
|
||||
@@ -486,7 +486,7 @@ Installing packages hosted by {% data variables.product.prodname_registry %} thr
|
||||
{% ifversion fpt or ghec %}
|
||||
## Upgrading a workflow that accesses a registry using a PAT
|
||||
|
||||
The {% data variables.product.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
|
||||
The {% data variables.packages.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
|
||||
|
||||
For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -8,7 +8,6 @@ topics:
|
||||
children:
|
||||
- /github-privacy-statement
|
||||
- /global-privacy-practices
|
||||
- /github-data-protection-agreement
|
||||
- /github-subprocessors-and-cookies
|
||||
- /github-codespaces-privacy-statement
|
||||
- /github-candidate-privacy-policy
|
||||
|
||||
@@ -1,11 +1 @@
|
||||
---
|
||||
ms.openlocfilehash: 39b050df26b1192db1f0d539b2bd789f90c022d1
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: "147764120"
|
||||
---
|
||||
Se recomienda usar solo {% data variables.actions.hosted_runner %} con repositorios privados:
|
||||
- Las bifurcaciones de tu repositorio pueden ejecutar código potencialmente peligroso en tu {% data variables.actions.hosted_runner %} creando una solicitud de extracción que ejecute el código en un flujo de trabajo.
|
||||
- Podría incurrir en costos inesperados si permites que los repositorios bifurcados ejecuten trabajos en {% data variables.actions.hosted_runner %}.
|
||||
If you are using a Fixed IP range, we recommend that you only use {% data variables.actions.hosted_runner %}s with private repositories. Forks of your repository can potentially run dangerous code on your {% data variables.actions.hosted_runner %} by creating a pull request that executes the code in a workflow.
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 0036dd5cf979531479a7ddf523c7475391b29c0a
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147548012"
|
||||
---
|
||||
De forma predeterminada, un flujo de trabajo de {% data variables.product.prodname_actions %} se desencadena cada vez que crea o actualiza una precompilación, o hace una inserción en una rama habilitada para la precompilación. Como sucede con otros flujos de trabajo, mientras se ejecutan los de precompilación, consumirán algunos de los minutos de acciones incluidos en la cuenta, si tiene alguno, o incurrirán en cargos por los minutos de acciones. Para más información sobre los precios de los minutos de acciones, vea "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
|
||||
|
||||
Junto con los minutos de {% data variables.product.prodname_actions %}, también se le facturarán por el almacenamiento de precompilaciones asociadas a cada configuración de precompilación para un repositorio y una región determinados. El almacenamiento de precompilaciones se factura a la misma velocidad que el almacenamiento de los codespaces.
|
||||
@@ -1,3 +0,0 @@
|
||||
To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of template versions to be retained for your prebuild configurations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
If you are an organization or enterprise owner, you can track usage of prebuild workflows and storage by downloading a {% data variables.product.prodname_actions %} usage report for your organization or enterprise. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create {% data variables.product.prodname_github_codespaces %} Prebuilds." For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)."
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 845c770a8a03c57a4c10a84d28fd4d3d78282042
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147111126"
|
||||
---
|
||||
Los {% data variables.product.prodname_codespaces %} se cobran en dólares estadounidenses (USD) de acuerdo con su uso de almacenamiento y cálculo.
|
||||
|
||||
### Calcular el uso de cómputo
|
||||
El uso de proceso se define como la cantidad total de minutos de tiempo de actividad durante los cuáles se encuentra activa una instancia de {% data variables.product.prodname_github_codespaces %}. El uso de cómputo se calcula sumando la cantidad real de minutos que utilizan todos los codespaces. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente.
|
||||
|
||||
El tiempo de actividad se controla deteniendo tu codespace, lo cual se puede hacer manual o automáticamente después de que un desarrollador especifique un periodo de inactividad. Para obtener más información, consulta "[Cerrar o detener el codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
|
||||
|
||||
### Calcular el uso de almacenamiento
|
||||
En la facturación de {% data variables.product.prodname_github_codespaces %}, se incluye todo el almacenamiento que utilizan todos los codespaces de tu cuenta. Esto incluye cualquier archivo que utilicen los codespaces, tales como los repositorios clonados, archivos de configuración y extensiones, entre otros. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano.
|
||||
@@ -5,5 +5,3 @@
|
||||
{% endnote %}
|
||||
|
||||
By default, your organization or enterprise will have a {% data variables.product.prodname_github_codespaces %} spending limit of $0. This prevents new codespaces from being created, or existing codespaces from being opened, if this would incur a billable cost to your organization or enterprise. To allow your users to create codespaces in your organization, set the limit to a value higher than $0.
|
||||
|
||||
{% data reusables.billing.overages-billed-monthly %}
|
||||
|
||||
@@ -1,11 +1,5 @@
|
||||
After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Currently, {% data variables.product.prodname_vscode_shortname %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}.
|
||||
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 86ebb6e0ab13cf7daf5fb580792bf8f4606eb054
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "147881920"
|
||||
---
|
||||
Para estimar los costos por servicios de consumo, puede usar la [calculadora de precios](https://github.com/pricing/calculator?feature=codespaces) de {% data variables.product.prodname_dotcom %}.
|
||||
@@ -78,6 +78,7 @@ translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-s
|
||||
translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,file deleted because it no longer exists in main
|
||||
@@ -88,6 +89,7 @@ translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-
|
||||
translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md,file deleted because it no longer exists in main
|
||||
@@ -174,6 +176,7 @@ translations/es-ES/content/rest/reference/secret-scanning.md,file deleted becaus
|
||||
translations/es-ES/content/rest/reference/teams.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/rest/reference/users.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/rest/reference/webhooks.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/site-policy/privacy-policies/github-data-protection-agreement.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/glossaries/internal.yml,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
|
||||
@@ -186,7 +189,10 @@ translations/es-ES/data/reusables/billing/per-user-pricing-reference.md,file del
|
||||
translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/availability.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/billing-for-prebuilds-default.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/billing-for-prebuilds-reducing.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/billing-for-prebuilds.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/codespaces-billing.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
|
||||
@@ -194,6 +200,7 @@ translations/es-ES/data/reusables/codespaces/unsupported-repos.md,file deleted b
|
||||
translations/es-ES/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/education/upgrade-organization.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
|
||||
translations/es-ES/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
|
||||
@@ -256,7 +263,7 @@ translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifi
|
||||
translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
|
||||
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
|
||||
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
|
||||
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,broken liquid tags
|
||||
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
|
||||
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags
|
||||
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
|
||||
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
|
||||
@@ -306,6 +313,7 @@ translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-
|
||||
translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
|
||||
translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,rendering error
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
|
||||
translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
|
||||
translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags
|
||||
@@ -391,7 +399,6 @@ translations/es-ES/content/code-security/supply-chain-security/understanding-you
|
||||
translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags
|
||||
@@ -411,7 +418,6 @@ translations/es-ES/content/codespaces/developing-in-codespaces/using-github-code
|
||||
translations/es-ES/content/codespaces/getting-started/deep-dive.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/getting-started/quickstart.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,broken liquid tags
|
||||
@@ -473,6 +479,7 @@ translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,render
|
||||
translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
|
||||
translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
|
||||
translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags
|
||||
translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags
|
||||
translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error
|
||||
translations/es-ES/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
|
||||
translations/es-ES/content/graphql/overview/about-the-graphql-api.md,rendering error
|
||||
@@ -481,7 +488,7 @@ translations/es-ES/content/issues/planning-and-tracking-with-projects/managing-y
|
||||
translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
|
||||
translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags
|
||||
translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,broken liquid tags
|
||||
translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
|
||||
translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
|
||||
translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error
|
||||
translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error
|
||||
@@ -501,6 +508,7 @@ translations/es-ES/content/organizations/restricting-access-to-your-organization
|
||||
translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,broken liquid tags
|
||||
translations/es-ES/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error
|
||||
translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
|
||||
translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,broken liquid tags
|
||||
translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
|
||||
translations/es-ES/content/packages/learn-github-packages/viewing-packages.md,rendering error
|
||||
translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
|
||||
@@ -597,6 +605,7 @@ translations/es-ES/data/reusables/actions/changing-the-name-of-a-runner-group.md
|
||||
translations/es-ES/data/reusables/actions/create-runner-group.md,rendering error
|
||||
translations/es-ES/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
|
||||
translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/actions/hosted-runner-security.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
|
||||
translations/es-ES/data/reusables/actions/ref_name-description.md,broken liquid tags
|
||||
@@ -624,7 +633,6 @@ translations/es-ES/data/reusables/code-scanning/autobuild-add-build-steps.md,bro
|
||||
translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
|
||||
translations/es-ES/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
|
||||
translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/codespaces/billing-for-prebuilds-reducing.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/codespaces/codespaces-api-beta-note.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md,broken liquid tags
|
||||
|
||||
|
Reference in New Issue
Block a user