jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-08 12:01:53 -05:00
Code Issues Projects Releases Wiki Activity

New translation batch for es (#31344)

Browse Source
This commit is contained in:
docubot
2022-10-01 10:23:59 -07:00
committed by GitHub
parent 31aba8a75b
commit b091bfe355
7 changed files with 116 additions and 115 deletions
Download Patch File Download Diff File Expand all files Collapse all files

55
translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
View File

@@ -44,14 +44,14 @@ If you are a site administrator for {% data variables.product.product_location %
{%- ifversion ghae %}
<!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
```shell
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
```
{%- else %}
```shell
$ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
```
{% note %}
**Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
```shell
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
@@ -67,27 +67,27 @@ If you are a site administrator for {% data variables.product.product_location %
3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
{% mac %}
```shell
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
```
{% endmac %}
{% windows %}
```shell
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
```
{% endwindows %}
{% linux %}
```shell
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
```
{% endlinux %}
4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
@@ -119,7 +119,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
$ touch ~/.ssh/config
```
* Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
* Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
```
Host *
@@ -131,9 +131,9 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
{% note %}
**Notes:**
- If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
- If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section.
```
@@ -144,15 +144,16 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
```shell
$ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
```
{% note %}
$ ssh-add --apple-use-keychain ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
```
{% note %}
**Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option.
**Note:** The `--apple-use-keychain` option stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `--apple-use-keychain` option.
The `--apple-use-keychain` option is in Apple's standard version of `ssh-add`. In MacOS versions prior to Monterey (12.0), the `--apple-use-keychain` and `--apple-load-keychain` flags used the syntax `-K` and `-A`, respectively.
If you don't have Apple's standard version of `ssh-add` installed, you may receive an error. For more information, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively.
{% endnote %}
@@ -199,7 +200,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
```shell
$ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
```
{%- ifversion not ghae %}
{% note %}
@@ -207,34 +208,34 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
```shell
$ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
```
{% endnote %}
{%- endif %}
4. When you are prompted, touch the button on your hardware security key.
5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
{% mac %}
```shell
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
```
{% endmac %}
{% windows %}
```shell
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
```
{% endwindows %}
{% linux %}
```shell
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
```
{% endlinux %}
6. When you are prompted to type a passphrase, press **Enter**.

4
translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
View File

@@ -1065,6 +1065,10 @@ Key | Type | Description
{% data reusables.webhooks.pull_request_short_desc %}
{% ifversion fpt or ghec %}
{% data reusables.pull_requests.merge-queue-beta %}
{% endif %}
### Availability
- Repository webhooks

116
translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
View File

@@ -1,6 +1,6 @@
---
title: Configurar un dominio personalizado para tu sitio de Páginas de GitHub
intro: 'Puedes configurar o actualizar determinados registros DNS y las configuraciones de tu repositorio para que apunten el dominio predeterminado de tu sitio de {% data variables.product.prodname_pages %} a un dominio personalizado.'
title: Managing a custom domain for your GitHub Pages site
intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.'
redirect_from:
- /articles/quick-start-setting-up-a-custom-domain
- /articles/setting-up-an-apex-domain
@@ -18,42 +18,49 @@ versions:
topics:
- Pages
shortTitle: Manage a custom domain
ms.openlocfilehash: ad96d0be88614e8294e29de74fd7112cfed1bc46
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 09/09/2022
ms.locfileid: '147710327'
---
Las personas con permisos de administración para un repositorio pueden configurar un dominio personalizado para un sitio de {% data variables.product.prodname_pages %}.
## Acerca de la configuración de dominios personalizados
People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site.
Asegúrate de agregar tu dominio personalizado al sitio de {% data variables.product.prodname_pages %} antes de configurar el dominio personalizado con tu proveedor DNS. Configurar tu dominio personalizado con tu proveedor DNS sin agregar tu dominio personalizado a {% data variables.product.product_name %} podría dar como resultado que alguien aloje un sitio en uno de tus subdominios.
## About custom domain configuration
Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains.
{% windows %}
El comando `dig`, que se puede usar para verificar la correcta configuración de los registros DNS, no está incluido en Windows. Para comprobar que los registros DNS se han configurado correctamente, debes instalar [BIND](https://www.isc.org/bind/).
The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/).
{% endwindows %}
{% note %}
**Nota:** Los cambios de DNS pueden tardar hasta 24 horas en propagarse.
**Note:** DNS changes can take up to 24 hours to propagate.
{% endnote %}
## Configurar un subdominio
## Configuring a subdomain
Para configurar un `www` o subdominio personalizado, como `www.example.com` o `blog.example.com`, debes agregar el dominio en la configuración del repositorio. Después de esto, configura un registro de CNAME con tu proveedor de DNS.
To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings. After that, configure a CNAME record with your DNS provider.
{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
4. En "Dominio personalizado", escribe el nombre de tu dominio personalizado y, a continuación, haz clic en **Guardar**. Si publicas el sitio desde una rama, se creará una confirmación que agrega un archivo `CNAME` a la raíz de la rama de origen. Si publicas el sitio con un flujo de trabajo de {% data variables.product.prodname_actions %} personalizado, no se crea ningún archivo `CNAME`. Para más información sobre la fuente de publicación, consulta "[Configuración de una fuente de publicación para el sitio de GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-subdomain.png)
5. Desplázate hasta tu proveedor DNS y crea un registro `CNAME` que apunte tu subdominio al dominio predeterminado de tu sitio. Por ejemplo, si quieres usar el subdominio `www.example.com` para el sitio de usuario, crea un registro `CNAME` que dirija `www.example.com` a `<user>.github.io`. Si quieres usar el subdominio `another.example.com` para el sitio de la organización, crea un registro `CNAME` que dirija `another.example.com` a `<organization>.github.io`. El registro `CNAME` siempre debe apuntar a `<user>.github.io` o `<organization>.github.io`, excepto el nombre del repositorio. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
{% data reusables.pages.navigate-site-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.pages.sidebar-pages %}
4. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow , no `CNAME` file is created. For more information about your publishing source, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png)
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %}
6. Para confirmar que el registro DNS se ha configurado correctamente, usa el comando `dig` y reemplaza _WWW.EXAMPLE.COM_ por el subdominio.
{% note %}
**Note:** If your custom domain is an internationalized domain name, you must enter the Punycode encoded version.
For more information on Punycodes, see [Internationalized domain name](https://en.wikipedia.org/wiki/Internationalized_domain_name).
{% endnote %}
5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `<user>.github.io`. If you want to use the subdomain `another.example.com` for your organization site, create a `CNAME` record that points `another.example.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
{% data reusables.command_line.open_the_multi_os_terminal %}
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
```shell
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
> ;<em>WWW.EXAMPLE.COM.</em> IN A
@@ -61,27 +68,30 @@ Para configurar un `www` o subdominio personalizado, como `www.example.com` o `b
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
```
{% data reusables.pages.build-locally-download-cname %} {% data reusables.pages.enforce-https-custom-domain %}
{% data reusables.pages.build-locally-download-cname %}
{% data reusables.pages.enforce-https-custom-domain %}
## Configurar un dominio apex
## Configuring an apex domain
Para configurar un dominio apex, como `example.com`, debes configurar un dominio personalizado en la configuración del repositorio y al menos un registro `ALIAS`, `ANAME` o `A` con el proveedor de DNS.
To set up an apex domain, such as `example.com`, you must configure a custom domain in your repository settings and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
{% data reusables.pages.www-and-apex-domain-recommendation %} Para obtener más información, consulta "[Configuración de un subdominio](#configuring-a-subdomain)".
{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)."
{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
4. En "Dominio personalizado", escribe el nombre de tu dominio personalizado y, a continuación, haz clic en **Guardar**. Si publicas el sitio desde una rama, se creará una confirmación que agrega un archivo `CNAME` a la raíz de la rama de origen. Si publicas el sitio con un flujo de trabajo de {% data variables.product.prodname_actions %} personalizado, no se crea ningún archivo `CNAME`. Para más información sobre la fuente de publicación, consulta "[Configuración de una fuente de publicación para el sitio de GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-apex-domain.png)
5. Desplázate hasta el proveedor DNS y crea un registro `ALIAS`, `ANAME` o `A`. También puedes crear registros `AAAA` para la compatibilidad con IPv6. {% data reusables.pages.contact-dns-provider %}
- Para crear un registro `ALIAS` o `ANAME`, apunta el dominio apex al dominio predeterminado del sitio. {% data reusables.pages.default-domain-information %}
- Para crear registros `A`, apunta el dominio apex a las direcciones IP de {% data variables.product.prodname_pages %}.
{% data reusables.pages.navigate-site-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.pages.sidebar-pages %}
4. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow , no `CNAME` file is created. For more information about your publishing source, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
![Save custom domain button](/assets/images/help/pages/save-custom-apex-domain.png)
5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
- To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
- To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
```shell
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153
```
- Para crear registros `AAAA`, apunta el dominio apex a las direcciones IP de {% data variables.product.prodname_pages %}.
- To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
```shell
2606:50c0:8000::153
2606:50c0:8001::153
@@ -89,9 +99,10 @@ Para configurar un dominio apex, como `example.com`, debes configurar un dominio
2606:50c0:8003::153
```
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %}
6. Para confirmar que el registro DNS se ha configurado correctamente, usa el comando `dig`, reemplazando _EXAMPLE.COM_ por tu dominio apex. Confirma que los resultados coincidan con las direcciones IP de las {% data variables.product.prodname_pages %} que aparecen arriba.
- Para registros `A`.
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
{% data reusables.command_line.open_the_multi_os_terminal %}
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
- For `A` records.
```shell
$ dig <em>EXAMPLE.COM</em> +noall +answer -t A
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.108.153
@@ -99,7 +110,7 @@ Para configurar un dominio apex, como `example.com`, debes configurar un dominio
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.110.153
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.111.153
```
- Para registros `AAAA`.
- For `AAAA` records.
```shell
$ dig <em>EXAMPLE.COM</em> +noall +answer -t AAAA
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8000::153
@@ -107,18 +118,19 @@ Para configurar un dominio apex, como `example.com`, debes configurar un dominio
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8002::153
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8003::153
```
{% data reusables.pages.build-locally-download-cname %} {% data reusables.pages.enforce-https-custom-domain %}
{% data reusables.pages.build-locally-download-cname %}
{% data reusables.pages.enforce-https-custom-domain %}
## Configuración de un dominio apex y la variante de subdominio `www`
## Configuring an apex domain and the `www` subdomain variant
Cuando utilizas un dominio apex, te recomendamos configurar tu sitio de {% data variables.product.prodname_pages %} para hospedar contenido tanto en el dominio de apex como en la variante de subdominio `www`.
When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant.
Para configurar un subdominio `www` junto con el dominio apex, primero debes configurar un dominio apex mediante la creación de un registro `ALIAS`, `ANAME` o `A` con el proveedor DNS. Para obtener más información, consulta "[Configuración de un dominio apex](#configuring-an-apex-domain)".
To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain by creating an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)."
Después de configurar el domnio apex, debes configurar un registro de CNAME con tu proveedor de DNS.
After you configure the apex domain, you must configure a CNAME record with your DNS provider.
1. Desplázate hasta tu proveedor DNS y crea un registro `CNAME` que apunte `www.example.com` al dominio predeterminado de tu sitio: `<user>.github.io` o `<organization>.github.io`. No incluyas el nombre de repositorio. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
2. Para confirmar que el registro DNS se ha configurado correctamente, usa el comando `dig` y reemplaza _WWW.EXAMPLE.COM_ por la variante de subdominio `www`.
1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
```shell
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
> ;<em>WWW.EXAMPLE.COM.</em> IN A
@@ -126,16 +138,18 @@ Después de configurar el domnio apex, debes configurar un registro de CNAME con
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
```
## Eliminar un dominio personalizado
## Removing a custom domain
{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
4. En "Dominio personalizado", haz clic en **Quitar**.
![Botón de guardar dominio personalizado](/assets/images/help/pages/remove-custom-domain.png)
{% data reusables.pages.navigate-site-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.pages.sidebar-pages %}
4. Under "Custom domain," click **Remove**.
![Save custom domain button](/assets/images/help/pages/remove-custom-domain.png)
## Asegurar tu dominio personalizado
## Securing your custom domain
{% data reusables.pages.secure-your-domain %} Para obtener más información, consulta "[Comprobación de un dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)".
{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
## Información adicional
## Further reading
- "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)".
- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"

13
translations/es-ES/data/reusables/pull_requests/merge-queue-beta.md
View File

@@ -1,14 +1,7 @@
---
ms.openlocfilehash: 2aec9cd701a3503386b9d751c1da74f64940c431
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 09/05/2022
ms.locfileid: "147496440"
---
{% ifversion fpt %} {% note %}
{% ifversion fpt or ghec %}
{% note %}
**Nota:** La característica de cola de fusión mediante combinación de solicitudes de incorporación de cambios se encuentra actualmente en versión beta pública y está sujeta a cambios.
**Note:** The pull request merge queue feature is currently in limited public beta and subject to change.
{% endnote %}

19
translations/es-ES/data/reusables/webhooks/pull_request_properties.md
View File

@@ -1,13 +1,6 @@
---
ms.openlocfilehash: e2c781f830b789fbb8fdaaa9403fe4c7a37c63b5
ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 09/09/2022
ms.locfileid: "147878524"
---
`number`|`integer` | Número de la solicitud de incorporación de cambios.
`changes`|`object` | Cambios en el comentario si la acción ha sido `edited`.
`changes[title][from]`|`string` | Versión previa del título si la acción ha sido `edited`.
`changes[body][from]`|`string` | Versión previa del cuerpo si la acción ha sido `edited`.
`pull_request`|`object` | La propia [solicitud de incorporación de cambios](/rest/reference/pulls).
`number`|`integer` | The pull request number.
`changes`|`object`| The changes to the comment if the action was `edited`.
`changes[title][from]`|`string` | The previous version of the title if the action was `edited`.
`changes[body][from]`|`string` | The previous version of the body if the action was `edited`.
`pull_request`|`object` | The [pull request](/rest/reference/pulls) itself.{% ifversion fpt or ghec %}
`reason`|`string` | The reason the pull request was removed from a merge queue if the action was `dequeued`.{% endif %}

12
translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md
View File

@@ -1,11 +1,3 @@
---
ms.openlocfilehash: b7fde4d22f9d5e5e8b7a3d8f55b3ab19dee1185a
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 09/10/2022
ms.locfileid: "145091462"
---
Clave | Tipo | Descripción
Key | Type | Description
----|------|-------------
`action`|`string` | La acción que se ha realizado. Puede ser una de las siguientes:<ul><li>`assigned`</li><li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li><li>`closed`: si la acción es `closed` y la clave `merged` es `false`, la solicitud de incorporación de cambios se ha cerrado con confirmaciones no combinadas. Si la acción es `closed` y la clave `merged` es `true`, la solicitud de incorporación de cambios se ha combinado.</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: se desencadena cuando se actualiza la rama principal de una solicitud de incorporación de cambios. Por ejemplo, cuando se actualiza la rama de encabezado desde la rama base, cuando las confirmaciones nuevas se suben a la rama de encabezado o cuando se cambia la rama de encabezado.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul>
`action`|`string` | The action that was performed. Can be one of:<ul><li>`assigned`</li><li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li><li>`closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.</li><li>`converted_to_draft`</li>{% ifversion fpt or ghec %}<li>`dequeued`: Triggered when a pull request is removed from a merge queue</li>{% endif %}<li>`edited`</li>{% ifversion fpt or ghec %}<li>`enqueued`: Triggered when a pull request is added to a merge queue</li>{% endif %}<li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Triggered when a pull request's head branch is updated. For example, when the head branch is updated from the base branch, when new commits are pushed to the head branch, or when the base branch is changed.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul>

12
translations/log/msft-es-resets.csv
View File

@@ -256,7 +256,7 @@ translations/es-ES/content/account-and-profile/setting-up-and-managing-your-gith
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
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,broken liquid tags
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
@@ -311,7 +311,7 @@ translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-
translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags
translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
@@ -355,7 +355,7 @@ translations/es-ES/content/code-security/dependabot/dependabot-version-updates/a
translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md,rendering error
translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error
translations/es-ES/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error
translations/es-ES/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,broken liquid tags
translations/es-ES/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error
translations/es-ES/content/code-security/getting-started/github-security-features.md,rendering error
translations/es-ES/content/code-security/getting-started/securing-your-repository.md,rendering error
translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,rendering error
@@ -392,7 +392,7 @@ translations/es-ES/content/codespaces/getting-started/deep-dive.md,broken liquid
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,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
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,broken liquid tags
@@ -471,6 +471,7 @@ translations/es-ES/content/packages/learn-github-packages/introduction-to-github
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
translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,broken liquid tags
translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
@@ -618,6 +619,7 @@ translations/es-ES/data/reusables/organizations/verified-domains.md,rendering er
translations/es-ES/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
translations/es-ES/data/reusables/pages/sidebar-pages.md,rendering error
translations/es-ES/data/reusables/policies/abuse.md,rendering error
translations/es-ES/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags
translations/es-ES/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
translations/es-ES/data/reusables/repositories/changed-files.md,broken liquid tags
translations/es-ES/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error
@@ -640,3 +642,5 @@ translations/es-ES/data/reusables/user-settings/saved_replies.md,rendering error
translations/es-ES/data/reusables/user-settings/security-analysis.md,rendering error
translations/es-ES/data/reusables/user-settings/security.md,rendering error
translations/es-ES/data/reusables/user-settings/ssh.md,rendering error
translations/es-ES/data/reusables/webhooks/pull_request_properties.md,broken liquid tags
translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags
1 file reason
256 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
257 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md rendering error
258 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md rendering error
259 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md broken liquid tags rendering error
260 translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md rendering error
261 translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md rendering error
262 translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md rendering error
311 translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md broken liquid tags
312 translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md rendering error
313 translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md broken liquid tags
314 translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md broken liquid tags rendering error
315 translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md broken liquid tags
316 translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md rendering error
317 translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md rendering error
355 translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md rendering error
356 translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md rendering error
357 translations/es-ES/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md rendering error
358 translations/es-ES/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md broken liquid tags rendering error
359 translations/es-ES/content/code-security/getting-started/github-security-features.md rendering error
360 translations/es-ES/content/code-security/getting-started/securing-your-repository.md rendering error
361 translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md rendering error
392 translations/es-ES/content/codespaces/getting-started/quickstart.md broken liquid tags
393 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md broken liquid tags
394 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md broken liquid tags
395 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md broken liquid tags rendering error
396 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md broken liquid tags
397 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md broken liquid tags
398 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md broken liquid tags
471 translations/es-ES/content/packages/learn-github-packages/viewing-packages.md rendering error
472 translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md rendering error
473 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md rendering error
474 translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md broken liquid tags
475 translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md rendering error
476 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md broken liquid tags
477 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md rendering error
619 translations/es-ES/data/reusables/package_registry/authenticate-packages.md broken liquid tags
620 translations/es-ES/data/reusables/pages/sidebar-pages.md rendering error
621 translations/es-ES/data/reusables/policies/abuse.md rendering error
622 translations/es-ES/data/reusables/pull_requests/merge-queue-beta.md broken liquid tags
623 translations/es-ES/data/reusables/pull_requests/resolving-conversations.md broken liquid tags
624 translations/es-ES/data/reusables/repositories/changed-files.md broken liquid tags
625 translations/es-ES/data/reusables/repositories/navigate-to-code-security-and-analysis.md rendering error
642 translations/es-ES/data/reusables/user-settings/security-analysis.md rendering error
643 translations/es-ES/data/reusables/user-settings/security.md rendering error
644 translations/es-ES/data/reusables/user-settings/ssh.md rendering error
645 translations/es-ES/data/reusables/webhooks/pull_request_properties.md broken liquid tags
646 translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md broken liquid tags