New translation batch for es (#23337)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-known-broken-translation-files.js * Check in es CSV report Co-authored-by: Francis <15894826+francisfuzz@users.noreply.github.com>
This commit is contained in:
docubot
@@ -133,11 +133,15 @@ runs:
|
||||
|
||||
For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)."
|
||||
|
||||
## `runs`
|
||||
|
||||
**Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
|
||||
|
||||
## `runs` for JavaScript actions
|
||||
|
||||
**Required** Configures the path to the action's code and the application used to execute the code.
|
||||
**Required** Configures the path to the action's code and the runtime used to execute the code.
|
||||
|
||||
### Example using Node.js
|
||||
### Example using Node.js v12
|
||||
|
||||
```yaml
|
||||
runs:
|
||||
@@ -147,15 +151,18 @@ runs:
|
||||
|
||||
### `runs.using`
|
||||
|
||||
**Required** The application used to execute the code specified in [`main`](#runsmain).
|
||||
**Required** The runtime used to execute the code specified in [`main`](#runsmain).
|
||||
|
||||
- Use `node12` for Node.js v12.
|
||||
- Use `node16` for Node.js v16.
|
||||
|
||||
### `runs.main`
|
||||
|
||||
**Required** The file that contains your action code. The application specified in [`using`](#runsusing) executes this file.
|
||||
**Required** The file that contains your action code. The runtime specified in [`using`](#runsusing) executes this file.
|
||||
|
||||
### `pre`
|
||||
|
||||
**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The application specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
|
||||
**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
|
||||
|
||||
In this example, the `pre:` action runs a script called `setup.js`:
|
||||
|
||||
@@ -181,7 +188,7 @@ In this example, `cleanup.js` only runs on Linux-based runners:
|
||||
|
||||
### `post`
|
||||
|
||||
**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The application specified with the [`using`](#runsusing) syntax will execute this file.
|
||||
**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The runtime specified with the [`using`](#runsusing) syntax will execute this file.
|
||||
|
||||
In this example, the `post:` action runs a script called `cleanup.js`:
|
||||
|
||||
@@ -207,11 +214,11 @@ For example, this `cleanup.js` will only run on Linux-based runners:
|
||||
|
||||
## `runs` for composite actions
|
||||
|
||||
**Required** Configures the path to the composite action, and the application used to execute the code.
|
||||
**Required** Configures the path to the composite action.
|
||||
|
||||
### `runs.using`
|
||||
|
||||
**Required** To use a composite action, set this to `"composite"`.
|
||||
**Required** You must set this value to `'composite'`.
|
||||
|
||||
### `runs.steps`
|
||||
|
||||
@@ -354,7 +361,7 @@ runs:
|
||||
|
||||
**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if).
|
||||
|
||||
The application specified with the [`using`](#runsusing) syntax will execute this file.
|
||||
The runtime specified with the [`using`](#runsusing) syntax will execute this file.
|
||||
|
||||
In this example, the `pre-entrypoint:` action runs a script called `setup.sh`:
|
||||
|
||||
|
||||
@@ -139,7 +139,8 @@ The `runner` context contains information about the runner that is executing the
|
||||
| Property name | Type | Description |
|
||||
|---------------|------|-------------|
|
||||
| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
|
||||
| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |
|
||||
| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
|
||||
| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
|
||||
| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
|
||||
| `runner.tool_cache` | `string` | {% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
|
||||
|
||||
|
||||
@@ -79,7 +79,8 @@ We strongly recommend that actions use environment variables to access the files
|
||||
| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
|
||||
| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
|
||||
| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %}
|
||||
| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}
|
||||
| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %}
|
||||
| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %}
|
||||
| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
|
||||
{% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %}
|
||||
|
||||
|
||||
@@ -54,6 +54,36 @@ It's not possible to add CPU or memory resources to an existing AWS/EC2 instance
|
||||
3. Start the instance.
|
||||
{% data reusables.enterprise_installation.configuration-recognized %}
|
||||
|
||||
## Adding CPU or memory resources on Microsoft Azure
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** To add CPU or memory resources in Microsoft Azure, you must be familiar with using either the Azure Portal, Azure CLI or Azure Powershell to manage VM instances. For background and details on using the Azure tools of your choice to perform the resize, please refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Resizing considerations
|
||||
|
||||
Before increasing CPU or memory resources for {% data variables.product.product_location %}, review the following recommendations.
|
||||
|
||||
- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %}
|
||||
- **Assign a static IP address to the instance**. If you haven't assigned a static IP to your instance, you might have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in IP address.
|
||||
|
||||
### Supported Microsoft Azure instance sizes
|
||||
|
||||
You need to determine the instance size you would like to upgrade to based on CPU/memory specifications.
|
||||
|
||||
{% data reusables.enterprise_installation.warning-on-scaling %}
|
||||
|
||||
{% data reusables.enterprise_installation.azure-instance-recommendation %}
|
||||
|
||||
### Resizing for Microsoft Azure
|
||||
|
||||
You can scale the VM up by changing the VM size. Changing its size will cause it to be restarted. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM.
|
||||
|
||||
1. Refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm) for the required steps.
|
||||
{% data reusables.enterprise_installation.configuration-recognized %}
|
||||
|
||||
## Adding CPU or memory resources for OpenStack KVM
|
||||
|
||||
It's not possible to add CPU or memory resources to an existing OpenStack KVM instance. Instead, you must:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Instalar el servidor de GitHub Enterprise en Azure
|
||||
intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Azure, debes implementar en una instancia de serie DS y usar almacenamiento Premium-LRS.'
|
||||
title: Installing GitHub Enterprise Server on Azure
|
||||
intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a DS-series instance and use Premium-LRS storage.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/guides/installation/installing-github-enterprise-on-azure/
|
||||
- /enterprise/admin/installation/installing-github-enterprise-server-on-azure
|
||||
@@ -13,63 +13,58 @@ topics:
|
||||
- Enterprise
|
||||
- Infrastructure
|
||||
- Set up
|
||||
shortTitle: Instalar en Azure
|
||||
shortTitle: Install on Azure
|
||||
---
|
||||
You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government.
|
||||
|
||||
Puedes implementar {% data variables.product.prodname_ghe_server %} en Azure mundial o Azure Government.
|
||||
|
||||
## Prerrequisitos
|
||||
## Prerequisites
|
||||
|
||||
- {% data reusables.enterprise_installation.software-license %}
|
||||
- Debes tener una cuenta Azure capaz de abastecer nuevas máquinas. Para obtener más información, consulta el [sitio web de Microsoft Azure](https://azure.microsoft.com).
|
||||
- La mayoría de las acciones necesarias para lanzar tu máquina virtual (VM) también se podrían realizar por medio del Portal Azure. Sin embargo, recomendamos instalar la interfaz de la línea de comando de Azure (CLI) para la configuración inicial. Abajo se incluyen ejemplos que utilizan Azure CLI 2.0. Para obtener más información, consulta la guía de Azure "[Instalar Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
|
||||
- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com).
|
||||
- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
|
||||
|
||||
## Consideraciones relativas al hardware
|
||||
## Hardware considerations
|
||||
|
||||
{% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
|
||||
|
||||
## Determinar el tipo de máquina virtual
|
||||
## Determining the virtual machine type
|
||||
|
||||
Antes de iniciar {% data variables.product.product_location %} en Azure, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. Para revisar los requisitos mínimos para {% data variables.product.product_name %}, consulta la sección "[Requisitos mínimos](#minimum-requirements)".
|
||||
Before launching {% data variables.product.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
|
||||
|
||||
{% data reusables.enterprise_installation.warning-on-scaling %}
|
||||
|
||||
El aparato {% data variables.product.prodname_ghe_server %} requiere un disco de datos de almacenamiento prémium, y es compatible con cualquier Azure VM que admita almacenamiento prémium. Los tipos de Azure VM con el sufijo `s`s son compatibles con el almacenamiento premium. Para obtener más información, consulta las secciones "[¿Qué tipos de disco están disponibles en Azure?](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd)" y "[Almacenamiento premium de Azure: diseño para la disponibilidad alta](https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance)" en la documentación de Azure.
|
||||
{% data reusables.enterprise_installation.azure-instance-recommendation %}
|
||||
|
||||
{% data variables.product.company_short %} recomienda una VM con memoria optimizada para {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Tamaños de máquina virtual con memoria optimizada](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory)" en la documentación de Azure.
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} admite cualquier región que sea compatible con tu tipo de VM. Para obtener más información sobre las regiones admitidas para cada VM, consulte los productos de Azure "[disponibles por región](https://azure.microsoft.com/regions/services/)."
|
||||
|
||||
## Crear la máquina virtual{% data variables.product.prodname_ghe_server %}
|
||||
## Creating the {% data variables.product.prodname_ghe_server %} virtual machine
|
||||
|
||||
{% data reusables.enterprise_installation.create-ghe-instance %}
|
||||
|
||||
1. Encuentra la imagen de aparato más reciente {% data variables.product.prodname_ghe_server %}. Para obtener más información sobre el comando `vm image list`, consulta "[lista de imagen vm de az](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" en la documentación de Microsoft.
|
||||
1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
|
||||
```shell
|
||||
$ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
|
||||
```
|
||||
|
||||
2. Crea una nueva VM utilizando la imagen de aparato que encontraste. Para obtener más información, consulta "[crear vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" en la documentación de Microsoft.
|
||||
2. Create a new VM using the appliance image you found. For more information, see "[az vm create](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
|
||||
|
||||
Aprueba opciones para el nombre de tu VM, el grupo de recurso, el tamaño de tu VM, el nombre de tu región Azure preferida, el nombre de la imagen de tu aparato VM que enumeraste en el paso anterior y el almacenamiento SKU para un almacenamiento prémium. Para obtener más información sobre grupos de recursos, consulta "[Grupos de recursos](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" en la documentación de Microsoft.
|
||||
Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation.
|
||||
|
||||
```shell
|
||||
$ az vm create -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --size <em>VM_SIZE</em> -l <em>REGION</em> --image <em>APPLIANCE_IMAGE_NAME</em> --storage-sku Premium_LRS
|
||||
```
|
||||
|
||||
3. Configura los parámetros de seguridad en tu VM para abrir los puertos requeridos. Para obtener más información, consulta "[abrir puerto de vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" en la documentación de Microsoft. Consulta la tabla de abajo para obtener una descripción de cada puerto para determinar qué puertos debes abrir.
|
||||
3. Configure the security settings on your VM to open up required ports. For more information, see "[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open.
|
||||
|
||||
```shell
|
||||
$ az vm open-port -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --port <em>PORT_NUMBER</em>
|
||||
```
|
||||
|
||||
Esta tabla identifica para qué se utiliza cada puerto.
|
||||
This table identifies what each port is used for.
|
||||
|
||||
{% data reusables.enterprise_installation.necessary_ports %}
|
||||
|
||||
4. Crea y adjunta a la VM un nuevo disco de datos descifrado y configura su tamaño con base en la cantidad de licencias que tengas. Para obtener más información, consulta "[adjuntar un disco de vm de az](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" en la documentación de Microsoft.
|
||||
4. Create and attach a new unencrypted data disk to the VM, and configure the size based on your user license count. For more information, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
|
||||
|
||||
Aprueba opciones para el nombre de tu VM (por ejemplo, `ghe-acme-corp`), el grupo de recurso, el almacenamiento prémium de SKU, el tamaño del disco (por ejemplo, `100`) y un nombre para el VHD resultante.
|
||||
Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `100`), and a name for the resulting VHD.
|
||||
|
||||
```shell
|
||||
$ az vm disk attach --vm-name <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --sku Premium_LRS --new -z <em>SIZE_IN_GB</em> --name ghe-data.vhd --caching ReadWrite
|
||||
@@ -77,33 +72,33 @@ El aparato {% data variables.product.prodname_ghe_server %} requiere un disco de
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** para instancias no productivas que tengan suficiente rendimiento de E/S, el tamaño mínimo recomendado es de 40 GiB con caché de lectura/escritura activado (`--caching ReadWrite`).
|
||||
**Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 40 GiB with read/write cache enabled (`--caching ReadWrite`).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Configurara la máquina virtual {% data variables.product.prodname_ghe_server %}
|
||||
## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine
|
||||
|
||||
1. Antes de configurar el VM, debes esperar que pase al estado ReadyRole. Controla el estado del VM con el comando `vm list`. Para obtener más información, consulta "[lista de vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" en la documentación de Microsoft.
|
||||
1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[az vm list](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
|
||||
```shell
|
||||
$ az vm list -d -g <em>RESOURCE_GROUP</em> -o table
|
||||
> Name ResourceGroup PowerState PublicIps Fqdns Location Zones
|
||||
> ------ --------------- ------------ ------------ ------- ---------- -------
|
||||
> VM_NAME RESOURCE_GROUP VM running 40.76.79.202 eastus
|
||||
|
||||
|
||||
```
|
||||
{% note %}
|
||||
|
||||
**Nota:** Azure no crea automáticamente una entrada FQDNS para el VM. Para obtener más información, consulta la guía de Azure sobre cómo "[Crear un nombre de dominio certificado completo en el portal de Azure para una VM de Linux](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
|
||||
|
||||
|
||||
**Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
|
||||
{% data reusables.enterprise_installation.upload-a-license-file %}
|
||||
{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
|
||||
{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
|
||||
{% data reusables.enterprise_installation.instance-will-restart-automatically %}
|
||||
{% data reusables.enterprise_installation.visit-your-instance %}
|
||||
|
||||
## Leer más
|
||||
|
||||
- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
|
||||
- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
|
||||
- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
|
||||
|
||||
@@ -14,6 +14,7 @@ children:
|
||||
- /changing-the-machine-type-for-your-codespace
|
||||
- /setting-your-default-editor-for-codespaces
|
||||
- /setting-your-default-region-for-codespaces
|
||||
- /setting-your-timeout-period-for-codespaces
|
||||
- /prebuilding-codespaces-for-your-project
|
||||
---
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ shortTitle: Personalize your codespaces
|
||||
When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
|
||||
|
||||
- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
|
||||
- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
|
||||
- [Dotfiles](#dotfiles) – You can use a `dotfiles` repository to specify scripts, shell preferences, and other configurations.
|
||||
|
||||
{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
|
||||
|
||||
@@ -33,7 +33,7 @@ Project maintainers can also define a default configuration that applies to ever
|
||||
|
||||
Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
|
||||
|
||||
To enable Settings Sync, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. From the dialog, select which settings you'd like to sync.
|
||||
To enable Settings Sync, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. In the dialog box, select the settings you'd like to sync.
|
||||
|
||||
|
||||
|
||||
@@ -41,13 +41,13 @@ For more information, see the [Settings Sync guide](https://code.visualstudio.co
|
||||
|
||||
## Dotfiles
|
||||
|
||||
Dotfiles are files and folders on Unix-like systems starting with `.` that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on {% data variables.product.prodname_dotcom %}. For advice and tutorials about what to include in your `dotfiles` repository, see [GitHub does dotfiles](https://dotfiles.github.io/).
|
||||
Dotfiles are files and folders on Unix-like systems starting with `.` that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on {% data variables.product.prodname_dotcom %}. For advice and tutorials about what to include in your dotfiles repository, see [GitHub does dotfiles](https://dotfiles.github.io/).
|
||||
|
||||
If your user account on {% data variables.product.prodname_dotcom %} owns a public repository named `dotfiles`, {% data variables.product.prodname_dotcom %} can automatically use this repository to personalize your codespace environment, once enabled from your [personal Codespaces settings](https://github.com/settings/codespaces). Private `dotfiles` repositories are not currently supported.
|
||||
Your dotfiles repository might include your shell aliases and preferences, any tools you want to install, or any other codespace personalization you want to make.
|
||||
|
||||
Your `dotfiles` repository might include your shell aliases and preferences, any tools you want to install, or any other codespace personalization you want to make.
|
||||
You can configure {% data variables.product.prodname_codespaces %} to use dotfiles from any repository you own by selecting that repository in your [personal {% data variables.product.prodname_codespaces %} settings](https://github.com/settings/codespaces).
|
||||
|
||||
When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your `dotfiles` repository to the codespace environment, and looks for one of the following files to set up the environment.
|
||||
When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your selected repository to the codespace environment, and looks for one of the following files to set up the environment.
|
||||
|
||||
* _install.sh_
|
||||
* _install_
|
||||
@@ -58,9 +58,9 @@ When you create a new codespace, {% data variables.product.prodname_dotcom %} cl
|
||||
* _setup_
|
||||
* _script/setup_
|
||||
|
||||
If none of these files are found, then any files or folders in `dotfiles` starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
|
||||
If none of these files are found, then any files or folders in your selected dotfiles repository starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
|
||||
|
||||
Any changes to your `dotfiles` repository will apply only to each new codespace, and do not affect any existing codespace.
|
||||
Any changes to your selected dotfiles repository will apply only to each new codespace, and do not affect any existing codespace.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -70,18 +70,20 @@ Any changes to your `dotfiles` repository will apply only to each new codespace,
|
||||
|
||||
### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %}
|
||||
|
||||
You can use your public `dotfiles` repository to personalize your {% data variables.product.prodname_codespaces %} environment. Once you set up that repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_codespaces %} settings page.
|
||||
You can use your selected dotfiles repository to personalize your {% data variables.product.prodname_codespaces %} environment. Once you choose your dotfiles repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_codespaces %} settings page.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Dotfiles have the ability to run arbitrary scripts, which may contain unexpected or malicious code. Before installing a dotfiles repo, we recommend checking scripts to ensure they don't perform any unexpected actions.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.codespaces-tab %}
|
||||
1. Under "Dotfiles", select "Automatically install dotfiles" so that {% data variables.product.prodname_codespaces %} automatically installs your dotfiles into every new codespace you create.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** This option is only available if you've created a public `dotfiles` repository for your user account.
|
||||
|
||||
{% endnote %}
|
||||
1. Under "Dotfiles", select **Automatically install dotfiles** so that {% data variables.product.prodname_codespaces %} automatically installs your dotfiles into every new codespace you create.
|
||||
|
||||
2. Choose the repository you want to install dotfiles from.
|
||||
|
||||
|
||||
You can add further script, preferences, configuration files to your dotfiles repository or edit existing files whenever you want. Changes to settings will only be picked up by new codespaces.
|
||||
|
||||
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Setting your timeout period for Codespaces
|
||||
intro: 'You can set your default timeout for {% data variables.product.prodname_codespaces %} in your personal settings page.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Set the timeout
|
||||
---
|
||||
|
||||
A codespace will stop running after a period of inactivity. You can specify the length of this timeout period. The updated setting will apply to any newly created codespace.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. For more information, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## Setting your default timeout
|
||||
|
||||
{% include tool-switcher %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.codespaces-tab %}
|
||||
1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To set the timeout period, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (5 hours).
|
||||
|
||||
```shell
|
||||
gh codespace create --idle-timeout 90m
|
||||
```
|
||||
|
||||
If you do not specify a timeout period when creating a codespace, then your default timeout period will be used. You cannot currently specify a default timeout period for all future codespaces through {% data variables.product.prodname_cli %}.
|
||||
|
||||
{% endcli %}
|
||||
@@ -33,7 +33,7 @@ If you have unsaved changes, your editor will prompt you to save them before exi
|
||||
|
||||
## Codespaces timeouts
|
||||
|
||||
If you leave your codespace running without interaction or if you exit your codespace without explicitly stopping it, the codespace will timeout after 30 minutes of inactivity and stop running. For more information, see "[Stopping a codespace](#stopping-a-codespace)."
|
||||
If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)."
|
||||
|
||||
When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
|
||||
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
#Reference: #5727
|
||||
#Documentation for new runner 'arch' environment variables set by the `runner` app.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.4'
|
||||
ghae: 'ghae-issue-5727'
|
||||
@@ -55,6 +55,9 @@ sections:
|
||||
- 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.'
|
||||
- "The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:\n\n* A self-hosted runner is registered or removed.\n* A self-hosted runner is added to a runner group, or removed from a runner group.\n* A runner group is created or removed.\n* A workflow run is created or completed.\n* A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner.\n\nFor more information, see \"[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events).\"\n"
|
||||
- 'Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job concurrency.'
|
||||
- heading: 'Cambios a los GitHub packages'
|
||||
notes:
|
||||
- 'When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.'
|
||||
- heading: 'Cambios al Dependabot y a la gráfica de Dependencias'
|
||||
notes:
|
||||
- 'Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."'
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
The architecture of the runner executing the job. Possible values are `X86`, `X64`, `ARM`, and `ARM64`.
|
||||
@@ -0,0 +1,5 @@
|
||||
El aparato {% data variables.product.prodname_ghe_server %} requiere un disco de datos de almacenamiento prémium, y es compatible con cualquier Azure VM que admita almacenamiento prémium. Los tipos de Azure VM con el sufijo `s`s son compatibles con el almacenamiento premium. Para obtener más información, consulta las secciones "[¿Qué tipos de disco están disponibles en Azure?](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd)" y "[Almacenamiento premium de Azure: diseño para la disponibilidad alta](https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance)" en la documentación de Azure.
|
||||
|
||||
{% data variables.product.company_short %} recomienda una VM con memoria optimizada para {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Tamaños de máquina virtual con memoria optimizada](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory)" en la documentación de Azure.
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} admite cualquier región que sea compatible con tu tipo de VM. Para obtener más información sobre las regiones admitidas para cada VM, consulte los productos de Azure "[disponibles por región](https://azure.microsoft.com/regions/services/)."
|
||||
@@ -191,6 +191,7 @@ translations/es-ES/content/admin/github-actions/using-github-actions-in-github-a
|
||||
translations/es-ES/content/admin/guides.md,Listed in localization-support#489
|
||||
translations/es-ES/content/admin/guides.md,rendering error
|
||||
translations/es-ES/content/admin/index.md,rendering error
|
||||
translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md,rendering error
|
||||
translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,Listed in localization-support#489
|
||||
translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,rendering error
|
||||
translations/es-ES/content/admin/overview/about-enterprise-accounts.md,Listed in localization-support#489
|
||||
@@ -369,6 +370,7 @@ translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-c
|
||||
translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md,rendering error
|
||||
translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,rendering error
|
||||
translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,rendering error
|
||||
translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error
|
||||
translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,Listed in localization-support#489
|
||||
translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error
|
||||
translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,Listed in localization-support#489
|
||||
|
||||
|
Reference in New Issue
Block a user