{% raw %}
@@ -533,7 +532,7 @@ jobs:
# Push image to GitHub Packages.
# See also https://docs.docker.com/docker-hub/builds/
push:
- runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+ runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
packages: write
contents: read{% endif %}
diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md
index 2118fbff99..7896aa0be5 100644
--- a/translations/es-ES/content/packages/quickstart.md
+++ b/translations/es-ES/content/packages/quickstart.md
@@ -1,37 +1,36 @@
---
-title: Guía de inciio rápido para GitHub Packages
-intro: 'Publica en el {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %}.'
+title: Quickstart for GitHub Packages
+intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
ghes: '*'
ghae: '*'
ghec: '*'
-shortTitle: Inicio Rápido
+shortTitle: Quickstart
---
{% data reusables.actions.enterprise-github-hosted-runners %}
-{% data reusables.actions.ae-beta %}
-## Introducción
+## Introduction
-En esta guía, crearás un flujo de trabajo de {% data variables.product.prodname_actions %} para probar tu código y luego lo publicarás en el {% data variables.product.prodname_registry %}.
+In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}.
-## Publicar tu paquete
+## Publishing your package
-1. Crea un repositorio nuevo en {% data variables.product.prodname_dotcom %}, agregando el `.gitignore` para Node. {% ifversion ghes < 3.1 %} Crea un repositorio privado si te gustaría borrar este paquete más adelante, los paquetes públicos no pueden borrarse.{% endif %} Para obtener más información, consulta la sección "[Crear un repositorio nuevo ](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)".
-2. Clona el repositorio en tu máquina local.
+1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. {% ifversion ghes < 3.1 %} Create a private repository if you’d like to delete this package later, public packages cannot be deleted.{% endif %} For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
+2. Clone the repository to your local machine.
```shell
$ git clone https://{% ifversion ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
$ cd YOUR-REPOSITORY
```
-3. Crea un archivo `index.js` y agrega una alerta básica que diga "Hello world!"
+3. Create an `index.js` file and add a basic alert to say "Hello world!"
{% raw %}
```javascript{:copy}
alert("Hello, World!");
```
{% endraw %}
-4. Inicializa un paquete de npm con `npm init`. En el asistente de inicialización de paquetes, ingresa tu paquete con el nombre: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, y configura el script de pruebas en `exit 0`. Esto generará un archivo `package.json` con información sobre tu paquete.
+4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package.
{% raw %}
```shell
$ npm init
@@ -42,15 +41,15 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam
...
```
{% endraw %}
-5. Ejecuta `npm install` para generar el archivo `package-lock.json` y luego confirma y sube tus cambios a {% data variables.product.prodname_dotcom %}.
+5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
```shell
$ npm install
$ git add index.js package.json package-lock.json
$ git commit -m "initialize npm package"
$ git push
```
-6. Crea un directorio de `.github/workflows`. En este directorio, crea un archivo que se llame `release-package.yml`.
-7. Copia el siguiente contenido de YAML en el archivo `release-package.yml`{% ifversion ghae %}, reemplazando a `YOUR-HOSTNAME` con el nombre de tu empresa{% endif %}.
+6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`.
+7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}.
```yaml{:copy}
name: Node.js Package
@@ -71,7 +70,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam
publish-gpr:
needs: build
- runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+ runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
packages: write
contents: read{% endif %}
@@ -86,14 +85,14 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam
env:
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
```
-8. Dile a NPM en qué alcance y registro publicar paquetes para utilizar uno de los siguientes métodos:
- - Agrega un archivo de configuración NPM para el repositorio creando un archivo `.npmrc` en el directorio raíz con el siguiente contenido:
+8. Tell NPM which scope and registry to publish packages to using one of the following methods:
+ - Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
{% raw %}
```shell
@YOUR-USERNAME:registry=https://npm.pkg.github.com
```
{% endraw %}
- - Edita el archivo `package.json` y especifica la clave `publishConfig`:
+ - Edit the `package.json` file and specify the `publishConfig` key:
{% raw %}
```shell
"publishConfig": {
@@ -101,7 +100,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam
}
```
{% endraw %}
-9. Confirma y sube tus cambios a {% data variables.product.prodname_dotcom %}.
+9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
```shell
$ git add .github/workflows/release-package.yml
# Also add the file you created or edited in the previous step.
@@ -109,29 +108,29 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam
$ git commit -m "workflow to publish package"
$ git push
```
-10. El flujo de trabajo que creaste se ejecutará cuando sea que se cree un lanzamiento nuevo en tu repositorio. Si las pruebas pasan, entonces el paquete se publicará en {% data variables.product.prodname_registry %}.
+10. The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}.
+
+ To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)."
- Para probar esto, navega a la pestaña de **Código** en tu repositorio y crea un lanzamiento nuevo. Para obtener más información, consulta la sección "[Gestionar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)".
+## Viewing your published package
-## Visualizar tu paquete publicado
-
-Puedes ver todos los paquetes que has publicado.
+You can view all of the packages you have published.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.package_registry.packages-from-code-tab %}
{% data reusables.package_registry.navigate-to-packages %}
-## Instalar un paquete publicado
+## Installing a published package
-Ahora que publicaste el paquete, querrás utilizarlo como una dependencia en tus proyectos. Para obtener más información, consulta la sección "[Trabajar con el registro de npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)".
+Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
-## Pasos siguientes
+## Next steps
-El flujo básico que acabas de agregar se ejecuta en cualquier momento que se cree un lanzamiento nuevo en tu repositorio. Pero esto es solo el inicio de lo que puedes hacer con el {% data variables.product.prodname_registry %}. Puedes publicar tu paquete en varios registros con un solo flujo de trabajo, activar el flujo de trabajo para que se ejecute en eventos diferentes tales como una solicitud de cambios fusionada, administrar contenedores, y más.
+The basic workflow you just added runs any time a new release is created in your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
-El combinar el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu proceso de desarrollo de aplicaciones. ¿Listo para comenzar? Aquí hay algunos recursos útiles para llevar a cabo los siguientes pasos con el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %}:
+Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}:
-- "[Aprende sobre el {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" para un tutorial más a fondo de GitHub Packages
-- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para un tutorial más a fondo de GitHub Actions
-- "[Trabajar con un registro de {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" para casos de uso y ejemplos específicos
+- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages
+- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions
+- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
index 0a76534207..36d4f570c7 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
@@ -13,14 +13,13 @@ redirect_from:
- /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
- /github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request
- /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
-
shortTitle: Merge PR automatically
---
## About auto-merge
If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.
-Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}
+Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %}
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
index a9effb3ad9..6dc332b6d9 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -72,7 +72,7 @@ Only the user who created the pull request can give you permission to push commi
{% tip %}
- **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository)."
+ **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)."
{% endtip %}
8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like.
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 8a89ae3bb8..8babad4362 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -30,7 +30,7 @@ You can review changes in a pull request one file at a time. While reviewing the
{% data reusables.repositories.sidebar-pr %}
{% data reusables.repositories.choose-pr-review %}
{% data reusables.repositories.changed-files %}
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-next %}
+{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
You can change the format of the diff view in this tab by clicking {% octicon "gear" aria-label="The Settings gear" %} and choosing the unified or split view. The choice you make will apply when you view the diff for other pull requests.
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 8d9cfd5548..586100d514 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -15,7 +15,7 @@ topics:
- Pull requests
---
-{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Syncing a fork from the web UI
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 371252c242..1b863c2771 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -17,7 +17,7 @@ shortTitle: Manage auto merge
---
## About auto-merge
-If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
## Managing auto-merge
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
index 9d1c5e6711..6f1a34c11c 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
@@ -16,8 +16,32 @@ shortTitle: Use merge queue
## About pull request merge queue
{% data reusables.pull_requests.merge-queue-overview %}
-{% data reusables.pull_requests.merge-queue-reject %}
+The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`.
+
+For example, with {% data variables.product.prodname_actions %}, adding the following trigger to a workflow will cause the workflow to run when any push is made to a merge queue preparatory branch that targets `main`.
+
+```
+on:
+ push:
+ branches:
+ - gh/readonly/queue/main/**
+```
+
+{% data reusables.pull_requests.merge-queue-merging-method %}
+
+For information about merge methods, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." For information about the "Require linear history" branch protection setting, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)."
+
+{% note %}
+
+**Note:** During the beta, there are some limitations when using the merge queue:
+
+* The merge queue cannot be enabled on branch protection rules using wildcards (`*`) in the name.
+* There is no support for squash merge commits. (Only merge commits and "rebase and merge" commits are supported.)
+
+{% endnote %}
+
+{% data reusables.pull_requests.merge-queue-reject %}
## Managing pull request merge queue
Repository administrators can configure merge queues for pull requests targeting selected branches of a repository. The requirement to use a merge queue is a branch protection setting called "Require merge queue" that can be enabled in branch protection rules.
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index c4be3a9f2a..2d760fe6f2 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -42,7 +42,7 @@ By default, the restrictions of a branch protection rule don't apply to people w
For each branch protection rule, you can choose to enable or disable the following settings.
- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging)
- [Require status checks before merging](#require-status-checks-before-merging)
-{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
- [Require conversation resolution before merging](#require-conversation-resolution-before-merging){% endif %}
- [Require signed commits](#require-signed-commits)
- [Require linear history](#require-linear-history)
@@ -99,7 +99,7 @@ You can set up required status checks to either be "loose" or "strict." The type
For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)."
-{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
### Require conversation resolution before merging
Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge.
@@ -138,6 +138,8 @@ Before you can require a linear commit history, your repository must allow squas
{% data reusables.pull_requests.merge-queue-beta %}
{% data reusables.pull_requests.merge-queue-overview %}
+
+{% data reusables.pull_requests.merge-queue-merging-method %}
{% data reusables.pull_requests.merge-queue-references %}
{% endif %}
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index 1ac3ee3211..fe9eb1dd68 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -80,7 +80,7 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
- Search for status checks, selecting the checks you want to require.
-{%- ifversion fpt or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghes > 3.1 or ghae %}
1. Optionally, select **Require conversation resolution before merging**.
{%- endif %}
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
index b6d8c53a63..d82c43712f 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
@@ -1,6 +1,6 @@
---
-title: Cambiar la rama predeterminada
-intro: 'Si tienes màs de una rama en tu repositorio, puedes configurar cualquiera de ellas como la predeterminada.'
+title: Changing the default branch
+intro: 'If you have more than one branch in your repository, you can configure any branch as the default branch.'
permissions: People with admin permissions to a repository can change the default branch for the repository.
versions:
fpt: '*'
@@ -14,40 +14,43 @@ redirect_from:
- /github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch
topics:
- Repositories
-shortTitle: Cambia la rama predeterminada
+shortTitle: Change the default branch
---
+## About changing the default branch
-## Acerca de cambiar la rama predeterminada
-
-Puedes elegir la rama predeterminada para un repositorio. Èsta es la rama base para las solicitudes de cambios y confirmaciones de còdigo. Para obtener màs informaciòn sobre la rama predeterminada, consulta la secciòn "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)".
+You can choose the default branch for a repository. The default branch is the base branch for pull requests and code commits. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
{% ifversion not ghae %}
{% note %}
-**Nota**: Si utilizas el puente de Git-Subversion, el cambiar la rama predeterminada afectarà al contenido de tu rama `trunk` y al `HEAD` que ves cuando listas las referencias para el repositorio remoto. Para obtener màs informaciòn, consulta la secciòn "[Soporte para los clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)" y a [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) en la documentaciòn de Git.
+**Note**: If you use the Git-Subversion bridge, changing the default branch will affect your `trunk` branch contents and the `HEAD` you see when you list references for the remote repository. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)" and [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) in the Git documentation.
{% endnote %}
{% endif %}
-{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-También puedes renombrar la rama predeterminada. Para obtener más información, consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)".
+You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
{% endif %}
{% data reusables.branches.set-default-branch %}
-## Prerrequisitos
+## Prerequisites
-Para cambiar la rama predeterminada, tu repositorio debe tener màs de una rama. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)".
+To change the default branch, your repository must have more than one branch. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)."
-## Cambiar la rama predeterminada
+## Changing the default branch
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.repository-branches %}
-1. Debajo de "Rama predeterminada", a la derecha del nombre de rama predeterminado, da clic en el {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. 
-1. Utiliza el menù desplegable y luego da clic en el nombre de una rama. 
-1. Da clic en **Actualizar**. 
-1. Lee la advertencia y luego da clic en **Entiendo, actualizar la rama predeterminada.** 
+1. Under "Default branch", to the right of the default branch name, click {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}.
+ 
+1. Use the drop-down, then click a branch name.
+ 
+1. Click **Update**.
+ 
+1. Read the warning, then click **I understand, update the default branch.**
+ 
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index e5683513b9..820352f6af 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -5,7 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i
versions:
fpt: '*'
ghes: '>=3.1'
- ghae: next
+ ghae: '*'
ghec: '*'
topics:
- Repositories
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index 970ef6ff72..a6ad2effcd 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -40,7 +40,7 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu
-{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
## Auto-generated table of contents for README files
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index cb0ef50a07..90bd18f498 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -90,7 +90,7 @@ You can configure this behavior for a repository using the procedure below. Modi
{% data reusables.repositories.settings-sidebar-actions %}
{% data reusables.github-actions.private-repository-forks-configure %}
-{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Setting the permissions of the `GITHUB_TOKEN` for your repository
{% data reusables.github-actions.workflow-permissions-intro %}
diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md
index 7e4246ba15..d0f6114565 100644
--- a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md
+++ b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -15,16 +15,34 @@ topics:
## About navigating code on {% data variables.product.prodname_dotcom %}
-Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). The following languages are supported:
-- C#
-- CodeQL
-- Go
-- Java
-- JavaScript
-- PHP
-- Python
-- Ruby
-- TypeScript
+Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition.
+
+
+
+Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported:
+
+| Language | search-based code navigation | precise code navigation |
+|:----------:|:----------------------------:|:-----------------------:|
+| C# | ✅ | |
+| CodeQL | ✅ | |
+| Go | ✅ | |
+| Java | ✅ | |
+| JavaScript | ✅ | |
+| PHP | ✅ | |
+| Python | ✅ | ✅ |
+| Ruby | ✅ | |
+| TypeScript | ✅ | |
+
+
+You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both.
+
+{% data variables.product.prodname_dotcom %} has developed two code navigation approaches based on the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) and [`stack-graphs`](https://github.com/github/stack-graphs) library:
+ - search-based - searches all definitions and references across a repository to find entities with a given name
+ - precise - resolves definitions and references based on the set of classes, functions, and imported definitions at a given point in your code
+
+To learn more about these approaches, see "[Precise and search-based navigation](#precise-and-search-based-navigation)."
+
+Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results.
## Jumping to the definition of a function or method
@@ -38,11 +56,21 @@ You can find all references for a function or method within the same repository
+## Precise and search-based navigation
+
+Certain languages supported by {% data variables.product.prodname_dotcom %} have access to *precise code navigation*, which uses an algorithm (based on the open source [`stack-graphs`](https://github.com/github/stack-graphs) library) that resolves definitions and references based on the set of classes, functions, and imported definitions that are visible at any given point in your code. Other languages use *search-based code navigation*, which searches all definitions and references across a repository to find entities with a given name. Both strategies are effective at finding results and both make sure to avoid inappropriate results such as comments, but precise code navigation can give more accurate results, especially when a repository contains multiple methods or functions with the same name.
+
+If you don't see the results you expect from a precise code navigation query, you can click on the "search-based" link in the displayed popover to perform search-based navigation.
+
+
+
+If your precise results appear inaccurate, you can file a support request.
+
## Troubleshooting code navigation
If code navigation is enabled for you but you don't see links to the definitions of functions and methods:
- Code navigation only works for active branches. Push to the branch and try again.
-- Code navigation only works for repositories with less than 100,000 files.
+- Code navigation only works for repositories with fewer than 100,000 files.
## Further reading
- "[Searching code](/github/searching-for-information-on-github/searching-code)"
diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md
index 74ab5b1968..86d5220126 100644
--- a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md
@@ -230,7 +230,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap
In the same way, we can [view repositories for the authenticated user][user repos api]:
```shell
-$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
+$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
{% data variables.product.api_url_pre %}/user/repos
```
@@ -274,7 +274,7 @@ Fetching information for existing repositories is a common use case, but the
we need to `POST` some JSON containing the details and configuration options.
```shell
-$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
+$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
-d '{ \
"name": "blog", \
"auto_init": true, \
@@ -320,7 +320,7 @@ Just like github.com, the API provides a few methods to view issues for the
authenticated user. To [see all your issues][get issues api], call `GET /issues`:
```shell
-$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
+$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
{% data variables.product.api_url_pre %}/issues
```
@@ -328,7 +328,7 @@ To get only the [issues under one of your {% data variables.product.product_name
/orgs//issues`:
```shell
-$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
+$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
{% data variables.product.api_url_pre %}/orgs/rails/issues
```
@@ -370,7 +370,7 @@ body to the `/issues` path underneath the repository in which we want to create
the issue:
```shell
-$ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \
+$ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \
$ -d '{ \
$ "title": "New logo", \
$ "body": "We should have one", \
diff --git a/translations/es-ES/content/rest/guides/traversing-with-pagination.md b/translations/es-ES/content/rest/guides/traversing-with-pagination.md
index bbf5c4c404..91595eb798 100644
--- a/translations/es-ES/content/rest/guides/traversing-with-pagination.md
+++ b/translations/es-ES/content/rest/guides/traversing-with-pagination.md
@@ -16,7 +16,7 @@ shortTitle: Traverse with pagination
The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
Most of the time, you might even find that you're asking for _too much_ information,
-and in order to keep our servers happy, the API will automatically [paginate the requested items][pagination].
+and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
In this guide, we'll make some calls to the Search API, and iterate over
the results using pagination. You can find the complete source code for this project
diff --git a/translations/es-ES/content/rest/index.md b/translations/es-ES/content/rest/index.md
index 22b8cc2c19..789e0c3023 100644
--- a/translations/es-ES/content/rest/index.md
+++ b/translations/es-ES/content/rest/index.md
@@ -1,7 +1,27 @@
---
-title: API de REST de GitHub
-shortTitle: API de REST
-intro: 'Puedes utilizar la API de REST de {% data variables.product.prodname_dotcom %} para crear llamadas y obtener los datos que necesitas para integrar con GitHub.'
+title: GitHub REST API
+shortTitle: REST API
+intro: 'To create integrations, retrieve data, and automate your workflows, build with the {% data variables.product.prodname_dotcom %} REST API.'
+introLinks:
+ quickstart: /rest/guides/getting-started-with-the-rest-api
+featuredLinks:
+ guides:
+ - /rest/guides/getting-started-with-the-rest-api
+ - /rest/guides/basics-of-authentication
+ - /rest/guides/best-practices-for-integrators
+ popular:
+ - /rest/overview/resources-in-the-rest-api
+ - /rest/overview/other-authentication-methods
+ - /rest/overview/troubleshooting
+ - /rest/overview/endpoints-available-for-github-apps
+ - /rest/overview/openapi-description
+ guideCards:
+ - /rest/guides/delivering-deployments
+ - /rest/guides/getting-started-with-the-checks-api
+ - /rest/guides/traversing-with-pagination
+changelog:
+ label: 'api, apis'
+layout: product-landing
redirect_from:
- /v3
versions:
diff --git a/translations/es-ES/content/rest/reference/actions.md b/translations/es-ES/content/rest/reference/actions.md
index d18e1d43d1..f00f66a23b 100644
--- a/translations/es-ES/content/rest/reference/actions.md
+++ b/translations/es-ES/content/rest/reference/actions.md
@@ -13,7 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.actions.ae-beta %}
The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)."
@@ -34,7 +33,7 @@ The Artifacts API allows you to download, delete, and retrieve information about
{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
## Permissions
-The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."
+The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API.
diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md
index d8512c1e8d..fbe657c8eb 100644
--- a/translations/es-ES/content/rest/reference/enterprise-admin.md
+++ b/translations/es-ES/content/rest/reference/enterprise-admin.md
@@ -34,6 +34,10 @@ REST API endpoints{% ifversion ghes %}—except [Management Console](#management
{% data variables.product.api_url_pre %}
```
+{% ifversion fpt or ghec %}
+When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`.
+{% endif %}
+
{% ifversion ghes %}
[Management Console](#management-console) API endpoints are only prefixed with a hostname:
@@ -85,7 +89,6 @@ You can also read the current version by calling the [meta endpoint](/rest/refer
## GitHub Actions
-{% data reusables.actions.ae-beta %}
{% for operation in currentRestOperations %}
{% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %}
diff --git a/translations/es-ES/content/rest/reference/packages.md b/translations/es-ES/content/rest/reference/packages.md
index 9c4a6e924b..72b91cab3b 100644
--- a/translations/es-ES/content/rest/reference/packages.md
+++ b/translations/es-ES/content/rest/reference/packages.md
@@ -1,6 +1,6 @@
---
-title: Paquetes
-intro: 'Con la API del {% data variables.product.prodname_registry %}, puedes administrar paquetes para tus repositorios y organizaciones de {% data variables.product.prodname_dotcom %}.'
+title: Packages
+intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
product: '{% data reusables.gated-features.packages %}'
versions:
fpt: '*'
@@ -10,16 +10,16 @@ topics:
miniTocMaxHeadingLevel: 3
---
-La API de {% data variables.product.prodname_registry %} te permite administrar paquetes utilizando la API de REST. Para aprender más sobre cómo restablecer o borrar paquetes, consulta la sección "[Restablecer y borrar paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package)".
+The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."
-Para utilizar esta API, primero tienes que autenticarte utilizando un token de acceso personal.
- - Para acceder a los metadatos del paquete, tu token debe incluir el alcance `read:packages`.
- - Para borrar los paquetes y las versiones de paquetes, tu token debe incluir los alcances `read:packages` y `delete:packages`.
- - Para restablecer los paquetes y sus versiones, tu token debe incluir los alcances de `read:packages` y `write:packages`.
+To use this API, you must authenticate using a personal access token.
+ - To access package metadata, your token must include the `read:packages` scope.
+ - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes.
+ - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes.
-Si tu `package_type` es `npm`, `maven`, `rubygems`, o `nuget`, entonces tu token también debe incluir el alcance `repo`, ya que este hereda los permisos de un repositorio de {% data variables.product.prodname_dotcom %}. Si tu paquete está en el {% data variables.product.prodname_container_registry %}, entonces tu `package_type` es `container` y tu token no necesita el alcance de `repo` para acceder o administrar este `package_type`. Los paquetes de `container` ofrecen permisos granulares separados de un repositorio. Para obtener más información, consulta la sección "[Acerca de los permisos para el {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)".
+If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
-Si quieres utilizar la API del {% data variables.product.prodname_registry %} para acceder a los recursos de una organización con el SSO habilitado, entonces debes habilitar el SSO para tu token de acceso personal. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizar con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)".
+If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."
{% for operation in currentRestOperations %}
{% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md
index ca85509c37..b740a1207d 100644
--- a/translations/es-ES/content/rest/reference/repos.md
+++ b/translations/es-ES/content/rest/reference/repos.md
@@ -170,7 +170,7 @@ You can communicate that a transient environment no longer exists by setting its
{% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %}
{% endfor %}
-{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Environments
The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
diff --git a/translations/es-ES/content/rest/reference/secret-scanning.md b/translations/es-ES/content/rest/reference/secret-scanning.md
index d3fd555101..2cb0e7cdf5 100644
--- a/translations/es-ES/content/rest/reference/secret-scanning.md
+++ b/translations/es-ES/content/rest/reference/secret-scanning.md
@@ -11,7 +11,7 @@ miniTocMaxHeadingLevel: 3
{% data reusables.secret-scanning.api-beta %}
-The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}:
+The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index cc87ced91a..f6f7e88e11 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -61,18 +61,18 @@ The {% data variables.search.advanced_url %} provides a visual interface for con
-{% ifversion fpt or ghes or ghae-next or ghec %}
+{% ifversion fpt or ghes or ghae or ghec %}
## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment
-If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following.
+If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following.
{% ifversion fpt or ghes or ghec %}
-- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %}
-- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation
-{% endif %}
-{% ifversion ghes or ghae-next %}
+- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}
+- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation
+
+{% ifversion ghes or ghae %}
To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`.
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
index 1ad80e1954..cf410536e1 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -1,7 +1,7 @@
---
-title: Habilitar la búsqueda en repositorios de GitHub.com desde tu ambiente empresarial privado
-shortTitle: Buscar en GitHub.com desde una empresa
-intro: 'Puedes conectar tus cuentas personales de {% data variables.product.prodname_dotcom_the_website %} y tu ambiente privado de {% data variables.product.prodname_enterprise %} para buscar contenido en repositorios específicos de {% data variables.product.prodname_dotcom_the_website %}{% ifversion fpt or ghec %} desde tu ambiente privado{% else %} desde {% data variables.product.product_name %}{% endif %}.'
+title: Enabling GitHub.com repository search from your private enterprise environment
+shortTitle: Search GitHub.com from enterprise
+intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt or ghec %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.'
redirect_from:
- /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/
- /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/
@@ -12,42 +12,41 @@ redirect_from:
versions:
fpt: '*'
ghes: '*'
- ghae: next
+ ghae: '*'
ghec: '*'
topics:
- GitHub search
---
-## Acerca de cómo buscar repositorios de {% data variables.product.prodname_dotcom_the_website %} desde {% ifversion fpt or ghec %}tu ambiente empresarial privado{% else %}{% data variables.product.product_name %}{% endif %}
+## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt or ghec %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %}
-Puedes buscar repositorios privados designados en {% data variables.product.prodname_ghe_cloud %} desde {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_location %}{% ifversion ghae %} en {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}Por ejemplo, si utilizas {% data variables.product.prodname_ghe_server %}, puedes buscar repositorios privados desde tu empresa en {% data variables.product.prodname_ghe_cloud %} en la interfaz web de {% data variables.product.prodname_ghe_server %}.{% endif %}
+You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %}
-## Prerrequisitos
+## Prerequisites
-- Un propietario de empresa de {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} debe habilitar {% data variables.product.prodname_github_connect %} y {% data variables.product.prodname_unified_search %}. Para obtener más información, consulta lo siguiente.{% ifversion fpt or ghes or ghec %}
- - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %}
- - "[Habilitar {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" en la documentación de {% data variables.product.prodname_ghe_managed %} documentation
+- An enterprise owner for {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes or ghec %}
+ - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
+ - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %}
{% endif %}
-- Ya debes tener acceso a los repositorios privados y conectar tu cuenta {% ifversion fpt or ghec %}en tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %} en {% data variables.product.product_name %}{% endif %} con tu cuenta en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre los repositorios en los que puedes buscar, consulta la sección "[Acerca de cómo buscar en GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)".
+- You must already have access to the private repositories and connect your account {% ifversion fpt or ghec %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)."
-## Habilitar la búsqueda de repositorios de GitHub.com desde {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %}
+## Enabling GitHub.com repository search from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %}
{% ifversion fpt or ghec %}
-Para obtener más información, consulta lo siguiente.
+For more information, see the following.
-| Tue ambiente empresarial | Más información |
-|:--------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| {% data variables.product.prodname_ghe_server %} | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %}
-|
-| {% data variables.product.prodname_ghe_managed %} | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)"
-{% endif %}
+| Your enterprise environment | More information |
+| :- | :- |
+| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
+| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" |
{% elsif ghes or ghae %}
-1. Inicia sesión en {% data variables.product.product_name %} y en {% data variables.product.prodname_dotcom_the_website %}.
-1. En {% data variables.product.product_name %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. 
+1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.
+1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
+
{% data reusables.github-connect.github-connect-tab-user-settings %}
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 53bb4c70c6..87b2785ed3 100644
--- a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -155,7 +155,7 @@ You can narrow your results by labels, using the `label` qualifier. Since issues
| ------------- | -------------
| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories.
| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority."
-| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}
+| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
## Search by milestone
diff --git a/translations/es-ES/data/glossaries/external.yml b/translations/es-ES/data/glossaries/external.yml
index 852e08b17e..5b8ada1c94 100644
--- a/translations/es-ES/data/glossaries/external.yml
+++ b/translations/es-ES/data/glossaries/external.yml
@@ -177,13 +177,13 @@
-
term: rama predeterminada
description: >-
- The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
+ La rama base para todas las solicitudes de cambio y confirmaciones de código en un repositorio. Cada repositorio tiene por lo menos una rama, la cual crea Git cuando lo inicializas. La rama principal a menudo se llama {% ifversion ghes < 3.2 %} 'master'{% else %}'main'{% endif %}, y habitualmente es la rama predeterminada.
-
- term: dependents graph
+ term: gráfica de dependientes
description: >-
Un gráfico del repositorio que muestra los paquetes, los proyectos y los repositorios que dependen de un repositorio público.
-
- term: dependency graph
+ term: gráfica de dependencias
description: >-
Un gráfico del repositorio que muestra los paquetes y los proyectos de los que depende el respositorio.
-
@@ -248,7 +248,7 @@
-
term: gist
description: >-
- A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
+ Un gist es un archivo que se puede compartir y que editas, clonas y bifurcas en GitHub. Puedes hacer que un gist sea {% ifversion ghae %}interno{% else %}público{% endif %} o secreto, aunque los gists secretos estarán disponibles para {% ifversion ghae %}cualquier miembro de la empresa{% else %}cualquiera{% endif %} que tenga la URL.
-
term: Git
description: >-
@@ -373,7 +373,7 @@
description: >-
Una cuenta personal a la que el usuario no puede acceder. Las cuentas se bloquean cuando los usuarios degradan su cuenta paga a una gratis o si su plan de pago se venció.
-
- term: management console
+ term: consola de administración
description: >-
Una sección dentro de la interfaz GitHub Enterprise que contiene funciones administrativas.
-
@@ -392,7 +392,7 @@
description: >-
La rama predeterminada en muchos de los repositorios de Git. Predeterminadamente, cuando creas un repositorio de Git nuevo en la línea de comandos, se creará una rama denominada 'master'. Hoy en día, muchas herramientas utilizan un nombre alterno para la rama predeterminada.{% ifversion fpt or ghes > 3.1 or ghae %} Por ejemplo, cuando creas un repositorio nuevo en GitHub, la rama predeterminada se llama 'main'.{% endif %}
-
- term: members graph
+ term: gráfica de miembros
description: Un gráfico del repositorio que muestra todas las bifurcaciones de un repositorio.
-
term: mención
@@ -418,7 +418,7 @@
description: >-
Un equipo hijo de un equipo padre. Puedes tener varios equipos hijo (o anidados).
-
- term: network graph
+ term: gráfica de red
description: >-
Un gráfico del repositorio que muestra el historial de la rama de toda la red del repositorio, incluidas las ramas del repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones de cambios únicas para la red.
-
@@ -539,10 +539,10 @@
description: >-
Los comentarios de los colaboradores en una solicitud de extracción que aprueban los cambios o solicitan otros cambios antes de fusionar la solicitud de extracción.
-
- term: pulse graph
+ term: gráfica de pulso
description: Un gráfico del repositorio que te brinda una descripción de la actividad de un repositorio.
-
- term: punch graph
+ term: gráfica de perforado
description: >-
Un gráfico del repositorio que muestra la frecuencia de las actualizaciones para un repositorio en función del día de la semana y la hora del día.
-
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml
new file mode 100644
index 0000000000..b2e5ff7237
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml
@@ -0,0 +1,20 @@
+date: '2021-12-07'
+sections:
+ security_fixes:
+ - 'Support bundles could include sensitive files if they met a specific set of conditions.'
+ bugs:
+ - 'Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.'
+ - 'A misconfiguration in the Management Console caused scheduling errors.'
+ - 'Docker would hold log files open after a log rotation.'
+ - 'GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments.'
+ changes:
+ - 'Clarifies explanation of Actions path-style in documentation.'
+ - 'Updates support contact URLs to use the current support site, support.github.com.'
+ known_issues:
+ - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
+ - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+ - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+ - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+ - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+ - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.'
+ - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml
index 6f3bbb15f3..8ad038ea19 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml
@@ -25,7 +25,7 @@ sections:
- "Puedes personalizar los tipos de notificaciones que quieres recibir de repositorios individuales. Para obtener más información, consulta la sección \"[Configurar las notificaciones](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)\".\n"
- heading: 'Filtrado de GitHub Mobile'
notes:
- - "El filtrado con [{% data variables.product.prodname_mobile %}](https://github.com/mobile) te permite buscar y encontrar propuestas, solicitudes de cambio y debates desde tu dispositivo. Los metadatos nuevos para los elementos de lista de las propuestas y solicitudes de cambio te permiten filtrar por asignados, estado de verificación, estados de revisión y conteo de comentarios.\n\n{% data variables.product.prodname_mobile %} beta está disponible para {% data variables.product.prodname_ghe_server %}. Inicia sesión con nuestras apps para [Android](https://play.google.com/store/apps/details?id=com.github.android) y [iOS](https://apps.apple.com/app/github/id1477376905) para clasificar las notificaciones y administrar las propuestas y solicitudes de cambio al momento. Los administradores pueden inhabilitar la compatibilidad móvil para sus empresas utilizando la consola de administración o ejecutando `ghe-config app.mobile.enabled false`. Para obtener más información, consulta la sección \"[GitHub para dispositivos móviles](/github/getting-started-with-github/using-github/github-for-mobile).\"\n"
+ - "El filtrado con [{% data variables.product.prodname_mobile %}](https://github.com/mobile) te permite buscar y encontrar propuestas, solicitudes de cambio y debates desde tu dispositivo. Los metadatos nuevos para los elementos de lista de las propuestas y solicitudes de cambio te permiten filtrar por asignados, estado de verificación, estados de revisión y conteo de comentarios.\n\n{% data variables.product.prodname_mobile %} beta está disponible para {% data variables.product.prodname_ghe_server %}. Inicia sesión con nuestras apps para [Android](https://play.google.com/store/apps/details?id=com.github.android) y [iOS](https://apps.apple.com/app/github/id1477376905) para clasificar las notificaciones y administrar las propuestas y solicitudes de cambio al momento. Los administradores pueden inhabilitar la compatibilidad móvil para sus empresas utilizando la consola de administración o ejecutando `ghe-config app.mobile.enabled false`. Para obtener más información, consulta la sección \"[GitHub móvil](/github/getting-started-with-github/using-github/github-mobile)\".\n"
changes:
- heading: 'Cambios en la administración'
notes:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml
new file mode 100644
index 0000000000..cec6929d55
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml
@@ -0,0 +1,21 @@
+date: '2021-12-07'
+sections:
+ security_fixes:
+ - 'Support bundles could include sensitive files if they met a specific set of conditions.'
+ bugs:
+ - 'Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.'
+ - 'A misconfiguration in the Management Console caused scheduling errors.'
+ - 'Docker would hold log files open after a log rotation.'
+ - 'GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments.'
+ changes:
+ - 'Clarifies explanation of Actions path-style in documentation.'
+ - 'Updates support contact URLs to use the current support site, support.github.com.'
+ known_issues:
+ - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
+ - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
+ - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+ - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+ - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+ - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+ - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontar un nodo de réplica con `ghe-repl-teardown` tendrá éxito, pero podría devolver un `ERROR:Running migrations`.'
+ - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml
index 747617a9bb..62d2d7a5ae 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml
@@ -1,127 +1,309 @@
date: '2021-09-09'
release_candidate: true
deprecated: true
-intro: 'Si {% data variables.product.product_location %} está ejecutando una compilación candidata a lanzamiento, no puedes mejorarla con un hotpatch. Te recomendamos que solo ejecutes candidatos a lanzamiento en ambientes de prueba.'
+intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
sections:
features:
- - heading: 'Patrones personalizados para el escaneo de secretos'
+ - heading: Custom patterns for secret scanning
notes:
- - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden especificar los patrones para el escaneo de secretos. Cuando se especifica un patrón nuevo, el escaneo de secretos busca dicho patrón en todo el historial de Git del repositorio, así como cualquier confirmación nueva.\n\nLos patrones definidos por los usuarios se encuentran en beta para {% data variables.product.prodname_ghe_server %} 3.2. Se pueden definir a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección \"[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)\".\n"
- - heading: 'Resumen de seguridad para la Seguridad Avanzada (beta)'
+ # https://github.com/github/releases/issues/1426
+ - |
+ {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits.
+
+ User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+ - heading: Security overview for Advanced Security (beta)
notes:
- - "Los clientes de la {% data variables.product.prodname_GH_advanced_security %} ahora tienen una vista de nivel de organización apra los riegos de seguridad de las aplicaciones que detecte el {% data variables.product.prodname_code_scanning %}, el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_secret_scanning %}. El resumen de seguridad muestra la habilitación de estado de las características de seguridad en cada repositorio, así como la cantidad de alertas que se detectan.\n\nAdicionalmente, el resumen de seguridad lista todas las alertas del {% data variables.product.prodname_secret_scanning %} a nivel organizacional. Tendremos vistas similares para el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_code_scanning %} en los lanzamientos futuros cercanos. Para obtener más información, consulta la sección \"[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)\".\n\n\n"
- - heading: 'Revisión de dependencias (beta)'
+ # https://github.com/github/releases/issues/1381
+ - |
+ {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected.
+
+ In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+ 
+
+ - heading: Dependency review (beta)
notes:
- - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden ver un diff enriquecido de las dependencias que cambiaron en una solicitud de cambios. La revisión de dependencias proporciona una vista fácil de entender de los cambios a las dependencias y de su impacto de seguridad en la pestaña de \"Archivos que cambiaron\" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron junto con la información de vulnerabilidades de estas dependencias. Para obtener más información, consulta la sección \"[Revisar los cambios de dependencias en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)\".\n"
- - heading: 'Ambientes de GitHub Actions'
+ # https://github.com/github/releases/issues/1364
+ - |
+ {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)."
+
+ - heading: GitHub Actions environments
notes:
- - "Los ambientes, las reglas de protección de ambiente y los secretos de ambiente ahora están disponibles en general para las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}. Para obtener más información, consulta la sección \"[Environments](/actions/reference/environments)\".\n"
- - heading: 'Autenticación por SSH con llaves seguras'
+ # https://github.com/github/releases/issues/1308
+ - |
+ Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)."
+
+ 
+
+ - heading: SSH authentication with security keys
notes:
- - "Ahora es compatible la autenticación por SSH utilizando una llave de seguridad FIDO2 cuando agregas una llave SSH de tipo `sk-ecdsa-sha2-nistp256@openssh.com` o `sk-ssh-ed25519@openssh.com` a tu cuenta. Las llaves de seguridad SSH almacenan material de llaves secretas en un dispositivo de hardware por separado, el cual requiere de verificación, tal como un tap, para operar. Para obtener más información, consulta la sección \"[Generar una clave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)\".\n"
- - heading: 'Temas oscuro y oscuro atenuado'
+ # https://github.com/github/releases/issues/1276
+ - |
+ SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+
+ - heading: 'Dark and dark dimmed themes'
notes:
- - "Ahora hay temas oscuro y opaco oscuro disponibles para la IU web. {% data variables.product.product_name %} empatará las preferencias de tu sistema si no has configurado las preferencias de tema en {% data variables.product.product_name %}. También puedes elegir qué temas estarán activos durante el día y la noche. Para obtener más información, consulta la sección \"[Administrar la configuración de tu tema](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n\n\n"
- - heading: 'Aprobar dominios no verificados para las notificaciones de correo electrónico'
+ # https://github.com/github/releases/issues/1260
+ - |
+ Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
+
+ 
+
+ - heading: 'Approving unverified domains for email notifications'
notes:
- - 'Los dominios que no se pueden verificar ahora pueden aprobarse para el enrutamiento de notificaciones por correo electrónico. Los propietarios de empresas y organizaciones podrán aprobar dominios y aumentar su política de restricción de notificaciones por correo electrónico automáticamente, lo cual permitirá que las notificaciones se envíen a los colaboradores, consultores, adquisiciones o a otros socios. para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" y "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."'
- - heading: 'Soporte para el almacenamiento de credenciales seguro del Administrador de Credenciales de Git (GCM) y autenticación multifactorial'
+ # https://github.com/github/releases/issues/1244
+ - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."
+
+ - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support'
notes:
- - "Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}.\n\nGCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository.\n"
+ # https://github.com/github/releases/issues/1406
+ - |
+ Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}.
+
+ GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository.
+
changes:
- - heading: 'Cambios en la administración'
+ - heading: Administration Changes
notes:
- - 'Se agregó un ajuste de "Política de Referente de Agente Usuario" a la configuración empresarial. Esto permite que un administrador configure una "Política de referente" más estricta para ocultar el nombre de host de una instalación de {% data variables.product.prodname_ghe_server %} de sitios externos. Este ajuste se encuentra inhabilitado predeterminadamente y los eventos de bitácoras de auditoría lo rastrean para los propietarios empresariales y el personal de las empresas cuando se habilita o inhabilita. Para obtener más información, consulta la sección "[Configurar la Política de Referente en tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".'
- - 'La revisión de salud de MySQL se cambió al uso de `mysqladmin ping` en vez de las verificaciones de TCP, lo cual elimina algo del ruido innecesario en la bitácora de errores de MySQL, las verificaciones de recuperación de fallos del orquestador se mejoraron para prevenir las recuperaciones de fallos de MySQL innecesarias al aplicar cambios de configuración del clúster.'
- - 'El servicio Resque, el cual da la compatibilidad con procesamiento de jobs en segundo plano, se reemplazó con Aqueduct Lite. este cambio hace que el sistema de jobs se pueda administrar más fácilmente y no debería afectar la experiencia del usuario. Para la administración y comandos de depuración nuevas de Aqueduct, consulta la sección "[Utilidades de la línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)".'
- - heading: 'Cambios de Token'
+ # https://github.com/github/releases/issues/1309
+ - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."
+
+ # https://github.com/github/releases/issues/1515
+ - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes.
+
+ # https://github.com/github/releases/issues/1287
+ - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."
+
+ - heading: Token Changes
notes:
- - "El formato de tokens de autenticación para {% data variables.product.product_name %} ha cambiado,. Dicho cambio afecta el formato de los tokens de acceso personal y de los tokens de acceso para las {% data variables.product.prodname_oauth_apps %}, así como de los tokens de usuario a servidor, de servidor a servidor y de actualización para {% data variables.product.prodname_github_apps %}.\n\nLos diferentes tipos de token ahora tienen prefijos identificables únicos, los cuales permiten que el escaneo de secretos detecten los tokens para que puedas mitigar el impacto de que alguien confirme un token accidentalmente en un repositorio. {% data variables.product.company_short %} recomienda actualizar los tokens existentes tan pronto como te sea posible. Para obtener más información, consulta las secciones \"[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)\" y \"[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)\".\n"
- - heading: 'Cambios de repositorios'
+ # https://github.com/github/releases/issues/1235
+ - |
+ The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}.
+
+ The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
+
+ - heading: 'Repositories changes'
notes:
- - 'Los repositorios en los perfiles de usuario y en los perfiles de organización ahora son compatibles con la clasificación por conteo de estrellas.'
- - 'Cuando veas el historial de confirmación de un archivo único, ahora puedes hacer clic en {% octicon "file-code" aria-label="The code icon" %} para ver dicho archivo en algún punto selecto del historial.'
- - 'Cuando un submódulo se define con una ruta relativa en {% data variables.product.product_location %}, el submódulo ahora se puede hacer clic en la interfaz web. Al hacer clic en el submódulo de la interfaz web le llevará al repositorio enlazado. Anteriormente, sólo los submódulos con URLs absolutas podían hacer clic. Esto es soportado para rutas relativas para los repositorios con el mismo propietario que siguen el patrón ..REPOSITORY o rutas relativas de repositorios con un propietario diferente que siga el patrón ../OWNER/REPOSITORY. Para obtener más información sobre cómo trabajar con submódulos, consulta la sección [Trabajar con submódulos](https://github.blog/2016-02-01-working-with-submodules/) en {% data variables.product.prodname_blog %}.'
- - 'La IU web ahora puede utilizarse para sincronizar una rama desactualizada de una bifurcación con la rama ascendente de dicha bifurcación. Si no hay conflictos de fusión entre las ramas, la rama se actualizará ya sea mediante un envío rápido o mediante la fusión desde la parte ascendente. Si hay conflictos, se te pedirá crear una solicitud de cambios para resolverlos. Para obtener más información, consulta la sección "[Sincronizar una bifurcación](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)".'
- - heading: 'Cambios en el Lenguaje de Marcado'
+ # https://github.com/github/releases/issues/1295
+ - Repositories on user profiles and organization profiles now support sorting by star count.
+
+ # https://github.com/github/releases/issues/1327
+ - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history.
+
+ # https://github.com/github/releases/issues/1254
+ - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}.
+
+ # https://github.com/github/releases/issues/1250
+ - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."
+
+ - heading: 'Markdown changes'
notes:
- - 'El editor de lenguaje de marcado que se utiliza al crear o editar un lanzamiento en un repositorio ahora tiene una barra de herramientas para edición de texto. Para obtener más información, consulta la sección "[Adminsitrar los lanzamientos en un repositorio](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)".'
- - '{% data variables.product.product_name %} ahora tiene compatibilidad para cargar archivos de video en donde sea que utilices lenguaje de marcado. Comparte demostraciones, pasos de reproducción y más en los comentarios de tus propuestas y solicitudes de cambio, así como en los archivos de lenguaje de marcado dentro de los repositorios, tales como los README. Para obtener más información, consulta la sección "[Adjuntar archivos](/github/writing-on-github/working-with-advanced-formatting/attaching-files)".'
- - 'Los archivos de lenguaje de marcado ahora generarán una tabla de contenido automáticamente en el encabezado cuando haya 2 o más encabezados. La tabla de contenido es interactiva y enlaza a la sección seleccionada. Los 6 niveles de encabezado del lenguaje de marcado son compatibles.'
- - 'Hay un atajo de teclado nuevo, `cmd+e` en macOS o `ctrl+e` en Windows, para insertar bloques de código en los archivos, propuestas, solicitudes de cambio y comentarios de Lenguaje de Marcado.'
- - 'El agregar `?plain=1` a la URL en cualquier archivo de lenguaje de marcado ahora mostrará al archivo sin procesar y con números de línea. La vista simple puede utilizarse para enlazar a otros usuarios a líneas específicas. Por ejemplo, el agregar `?plain=1#L52` resaltará la línea 52 del archivo de marcado en texto simple. Para obtener más información, consulta la sección "[Crear un enlace permanente a un fragmento de código](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)".'
- - heading: 'Cambios en propuestas y sollicitudes de cambio'
+ # https://github.com/github/releases/issues/1477
+ - The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."
+
+ # https://github.com/github/releases/issues/1169
+ - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
+
+ # https://github.com/github/releases/issues/1269
+ - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported.
+
+ # https://github.com/github/releases/issues/1294
+ - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.'
+
+ # https://github.com/github/releases/issues/1474
+ - Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."
+
+ - heading: 'Issues and pull requests changes'
notes:
- - 'Con la [versión más reciente de Octicons](https://github.com/primer/octicons/releases), los estados de las propuestas y solicitudes de cambios ahora son más fáciles de distinguir visualmente para que puedas escanear los estados de forma más sencilla. Para obtener más información consulta la sección [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).'
- - 'Ahora tenemos disponible una regla de protección de rama de "Requerir la resolución de la conversación antes de fusionar" y un menú de "Conversaciones". Descubre fácilmente tus comentarios de solicitudes de cambios desde la pestaña de "Archivos que cambiaron" y requiere qeu todas tus conversaciones en solicitudes de cambio se resuelvan antes de fusionarse. Para obtener más información, consulta las secciones "[Acerca de las revisiones de solicitudes de cambio](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" y "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)".'
- - 'Para prevenir la fusión de cambios inesperados después de habilitar la fusión automática para una solicitud de cambios, ahora se inhabilitó esta opción automáticamente cuando un usuario sin acceso de escritura al repositorio sube estos cambios. Los usuarios que no tengan permisos de escritura aún pueden actualizar la solicitud de cambios con aquellos de la rama base cuando se habilita la fusión automática. Para prevenir que un usuario malintencionado utilice un conflicto de fusión para introducir cambios inesperados a la solicitud de cambios, la fusión automática para la solicitud de cambios se encuentra inhabilitada si dicha actualización causa un conflicto de fusión. Para obtener más información sobre la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".'
- - 'Las personas con permisos de mantenimiento ahora pueden administrar el ajuste de "Permitir la fusión automática" a nivel de repositorio. Este ajuste, el cual a menudo se encuentra inhabilitado, controla si la fusión automática está disponible para las solicitudes de cambios en el repositorio., Anteriormente, solo las personas con permisos administrativos podían administrar este ajuste. Adicionalmente, este ajuste ahora puede controlarse utilizando las API de REST para "[Crear repositorio](/rest/reference/repos#create-an-organization-repository)" y "[Actualizar repositorio](/rest/reference/repos#update-a-repository)". Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio]](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)".'
- - 'La selección de propuestas y solicitudes de cambio de los asignados ahora es compatible con la búsqueda de escritura anticipada, así que puedes encontrar usuarios en tu organización más rápidamente. Adicionalmente, las clasificaciones de resultados de búsqueda se actualizaron para preferir las coincidencias al inicio del nombre de usuario de una persona o nombre de perfil.'
- - 'Cuando se solicita una revisión de un equipo de más de 100 personas, los desarrolladores ahora muestran una caja de diálogo de confirmación para poder prevenir las notificaciones innecesarias para los equipos grandes.'
- - 'Ahora hay compatibilidad con tener `code blocks` con comilla inversa en los títulos de las propuestas y en cualquier lugar en el que se referencien propuestas y solicitudes de cambios en {% data variables.product.prodname_ghe_server %}.'
- - 'Los eventos para las solicitudes de cambios y revisiones de solicitudes de cambios ahora se incluyen en la bitácora de auditoría tanto para [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) como para [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). estos eventos ayudan a que los administradores monitoreen mejor la actividad de las solicitudes de cambios y ayuden a garantizar que se cumplan los requisitos de seguridad y cumplimiento. Los eventos pueden verse desde la IU web, exportarse como CSV o JSON o acceder a ellos a través de la API de REST. También puedes buscar la bitácora de auditoría para los eventos de solicitudes de cambio específicos. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)".'
- - heading: 'Cambios a las ramas'
+ # https://github.com/github/releases/issues/1413
+ - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).
+
+ # https://github.com/github/releases/issues/1419
+ - A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."
+
+ # https://github.com/github/releases/issues/1279
+ - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+
+ # https://github.com/github/releases/issues/1550
+ - People with maintain permissions can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin permissions could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)."
+
+ # https://github.com/github/releases/issues/1201
+ - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name.
+
+ # https://github.com/github/releases/issues/1430
+ - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams.
+
+ # https://github.com/github/releases/issues/1293
+ - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}.
+
+ # https://github.com/github/releases/issues/1300
+ - Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."
+
+ - heading: 'Branches changes'
notes:
- - "El nombre de rama predeterminado para los repositorios nuevos ahora es `main`. Los repositorios existentes no se verán impactados por este cambio. Si los usuarios, propietarios de organizaciones o propietarios de empresas ya especificaron una rama predeterminada para repositorios nuevos anteriormente, tampoco se les impactará.\n\nSi quieres configurar un nombre de rama predeterminada diferente, puedes hacerlo en los ajustes de [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), o [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name).\n"
- - "Las ramas, incluyendo a la predeterminada, ahora pueden volver a nombrarse utilizando la IU web de {% data variables.product.product_name %}. Cuando una rama se vuelve a nombrar, cualquier solicitud de cambios abierta y lanzamiento de borrador que apunten a la rama que se volvió a nombrar se redirigirá automáticamente y las reglas de protección de rama que referencien explícitamente a la rama que se volvió a nombrar se actualizarán.\n\nSe requieren permisos administrativos para volver a nombrar la rama predeterminada, pero es suficiente contar con permisos de escritura para volver a nombrar otras ramas.\n\nPara ayudar a hacer el cambio con tanta continuidad como sea posible para los usuarios:\n\n* Se muestra un aviso a los contribuyentes, mantenedores y administradores de la página de inicio del repositorio, el cual contiene instrucciones para actualizar su repositorio local.\n*Las solicitudes web para la rama antigua se redireccionarán.\n* Se devolverá una respuesta HTTP de \"se movió permanentemente\" a todo llamado de la API de REST.\n* Se mostrará un mensaje informativo para los usuarios de la línea de comandos de Git que suban información a la rama antigua.\n\nPara obtener más información, consulta la sección \"[Volver a nombrar una rama](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)\".\n"
- - heading: 'Cambioas a las GitHub Actions'
+ # https://github.com/github/releases/issues/885
+ - |
+ The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted.
+
+ If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings.
+
+ # https://github.com/github/releases/issues/981
+ - |
+ Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated.
+
+ Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches.
+
+ To help make the change as seamless as possible for users:
+
+ * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository.
+ * Web requests to the old branch will be redirected.
+ * A "moved permanently" HTTP response will be returned to REST API calls.
+ * An informational message is displayed to Git command line users that push to the old branch.
+
+ For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)."
+
+ - heading: 'GitHub Actions changes'
notes:
- - 'Las {% data variables.product.prodname_actions %} ahora te permiten controlar los permisos que se otorgan al secreto del `GITHUB_TOKEN`. El `GITHUB_TOKEN` es un secreto que se genera automáticamente y te permite hacer llamados autenticados a la API de {% data variables.product.product_name %} en tus ejecuciones de flujo de trabajo. Las {% data variables.product.prodname_actions %} generan un token nuevo para cada job y hacen que el token venza cuando se completa el job. El token a menudo tiene permisos de `escritura` para varias [Terminales de la API](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), con excepción de los casos de las solicitudes de cambios de las bifurcaciones, los cuales siempre se marcan como de `lectura`. Estos ajustes nuevos te permiten seguir el principio de los menores privilegios necesarios en tus flujos de trabajo,. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".'
- - 'El {% data variables.product.prodname_cli %} 1.9 y posterior te permiten trabajar con las {% data variables.product.prodname_actions %} en tu terminal. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).'
- - 'La bitácora de auditoría ahora incluye eventos asociados con las ejecuciones de flujo de trabajo de {% data variables.product.prodname_actions %}. Estos datos proporcionan un conjunto de datos ampliamente expandidos para los administradores, así como auditorías de cumplimiento. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)".'
- - 'Se hicieron mejoras de rendimiento a {% data variables.product.prodname_actions %}, lo cual podría dar como resultado una capacidad de procesamiento de jobs máxima más alta. Para obtener más información sobre la capacidad de procesamiento de los jobs con configuraciones de CPU y memoria probadas internamente, consulta la sección "[Iniciar con {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".'
- - heading: 'Cambios a los GitHub packages'
+ # https://github.com/github/releases/issues/1227
+ - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."'
+
+ # https://github.com/github/releases/issues/1280
+ - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).'
+
+ # https://github.com/github/releases/issues/1157
+ - The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."
+
+ # https://github.com/github/releases/issues/1587
+ - Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job throughput. For more information on job throughput with internally-tested CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+
+ - heading: 'GitHub Packages changes'
notes:
- - 'Cualquier paquete o versión de paquete del {% data variables.product.prodname_registry %} ahora se puede borrar de la IU web de {% data variables.product.product_name %}. También puedes deshacer el borrado de cualquier paquete o versión de paquete dentro de los primeros 30 días. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".'
- - heading: 'Cambios al Dependabot y a la gráfica de Dependencias'
+ # https://github.com/github/releases/issues/1088
+ - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)".
+
+ - heading: 'Dependabot and Dependency graph changes'
notes:
- - 'La gráfica de dependencias ahora puede habilitarse utilizando la Consola de Administración en vez de necesitar la ejecución de un comando en el shell administrativo. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables de {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".'
- - 'Ahora, las notificaciones para {% data variables.product.prodname_dependabot_alerts %} múltiples se agrupan si se descubren al mismo tiempo. Esto reduce significativamente el volumen de notificaciones de alertas del {% data variables.product.prodname_dependabot %} que reciben los usuarios. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).'
- - 'Las gráficas de dependencias y {% data variables.product.prodname_dependabot_alerts %} ahora son compatibles con los módulos de Go. {% data variables.product.prodname_ghe_server %} analiza los archivos de `go.mod` de un repositorio para entender las dependencias del mismo. En conjunto con las asesorías de seguridad, la gráfica de dependencias proporciona la información necesaria para alertar a los desarrolladores sobre las dependencias vulnerables. Para obtener más información sobre cómo habilitar la gráfica de dependencias en los repositorios privados, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)".'
- - 'Los ajustes de notificación predeterminados para las alertas de seguridad han cambiado. Anteriormente, si tenías permiso para ver las alertas de seguridad en un repositorio, hubieras recibido las notificaciones de dicho repositorio mientras tu configuración permitiera las notificaciones de alertas de seguridad. Ahora debes decidir unirte a las notificaciones de alertas de seguridad observando el repositorio. Se te notificará si seleccionas `Toda la actividad` o si configuras `Personalizado` para incluir las `Alertas de seguridad`. Todos los repositorios existentes se migrarán automáticamente a estos ajustes nuevos y seguirás recibiendo notificaciones; sin embargo, cualquier repositorio nuevo requerirá que decidas unirte observando el repositorio. Para obtener más información, consulta las secciones "[Configurar notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" y "[Administrar las alertas del escaneo de secretos](/code-security/secret-security/managing-alerts-from-secret-scanning)".'
- - heading: 'Cambios al escaneo de código y de secretos'
+ # https://github.com/github/releases/issues/1537
+ - The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+
+ # https://github.com/github/releases/issues/1153
+ - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).
+
+ # https://github.com/github/releases/issues/1371
+ - Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository's `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."
+
+ # https://github.com/github/releases/issues/1538
+ - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. For more information see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+ - heading: 'Code scanning and secret scanning changes'
notes:
- - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql %} ahora genera información diagnóstica para todos los lenguajes compatibles. Esto ayuda a mantener el estado de la base de datos creada para entender el estado y calidad del análisis que se realizó. La información diagnóstica se encuentra disponible desde la [versión 2.5.6](https://github.com/github/codeql-cli-binaries/releases) del {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). Puedes ver esta información diagnóstica detallada en las bitácoras para {% data variables.product.prodname_codeql %} de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Visualizar las bitácoras de escaneo de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)".'
- - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql_cli %} ahora es compatible con el análisis de diversos lenguajes durante una compilación sencilla. Esto facilita el ejecutar análisis de código para utilizar sistemas de IC/DC diferentes a los de las {% data variables.product.prodname_actions %}. El modo nuevo del comando `codeql database create` se encuentra disponible desde la [versión 2.5.6] (https://github.com/github/codeql-cli-binaries/releases) del [{% data variables.product.prodname_codeql_cli %}] (https://codeql.github.com/docs/codeql-cli/). Para obtener más información sobre cómo configurar esto, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)".'
- - 'Las alertas de {% data variables.product.prodname_code_scanning_capc %} de todas las herramientas habilitadas ahora se muestran en una lista consolidada para que puedas priorizar fácilmente entre todas ellas. Puedes ver las alertas desde una herramienta específica utilizando le filtro de "Herramienta" y los de "Regla" y "Etiqueta" se actualizarán dinámicamente con base en tu selección de "Herramientas".'
- - 'El {% data variables.product.prodname_code_scanning_capc %} cib {% data variables.product.prodname_codeql %} ahora incluye soporte beta para analizar código de C++20. Esto solo está disponible cuando creas bases de código con GCC en Linux. Los módulos de C++20 aún no son compatibles.'
- - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró al agregar compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) y al incrementar la cobertura de nuestros modelos de marcos de trabajo y librerías para varios lenguajes ({C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), y [Java](https://github.com/github/codeql/tree/main/java)). Como resultado, el {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuarios no confiables, revisar los pasos a través de los cuales fluyen los datos e identificar hundimientos potencialmente peligrosos en los cuales podrían terminar estos datos,. Esto da como resultado una mejora general de la calidad de las alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección de [registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).'
- - "El {% data variables.product.prodname_code_scanning_capc %} ahora muestra niveles de `gravedad de seguridad` para las alertas del Code QL. Puedes configurar qué niveles de `gravedad de seguridad` ocasionarán un fallo de verificación para una solicitud de cambios. El nivel de gravedad de las alertas de seguridad puede ser `crítico`, `alto, `medio` o `bajo`. Predeterminadamente, cualquier alerta del {% data variables.product.prodname_code_scanning %} con un `nivel de gravedad` que sea `crítico` o `alto` ocasionará que una solicitud de cambios falle.\n\nAdicionalmetnte, ahora también puedes configurar qué niveles de gravedad ocasionarán que la verificación de solicitudes de cambio falle para las alertas que no sean de seguridad. Puedes configurar este comportamiento a nivel de repositorio y definir si las alertas con gravedad de `error`, `advertencia` o `nota` ocasionarán que una verificación de solicitud de cambio falle. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} que no sean de seguridad y tengan un nivel de gravedad de `error` ocasionarán que la verificación de una solicitud de cambios falle.\n\nPara obtener más información, consulta la sección \"[Definir qué alertas de niveles de gravedad ocasionan que falle la verificación de las solicitudes de cambio]](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)\".\n\n\n"
- - "Las mejoras al filtro de rama para las alertas del {% data variables.product.prodname_code_scanning %} dejan más claro qué alertas del {% data variables.product.prodname_code_scanning %} se están mostrando en la página de alertas. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} se filtran para mostrar únicamente las alertas de la rama predeterminada del repositorio. Puedes utilizar el filtro de rama para mostrar las alertas en cualquiera de las ramas no predeterminadas. Cualquier filtro de rama que se haya aplicado se mostrará en la barra de búsqueda.\n\nLa sintaxis de búsqueda también se simplificó como `branch:`. Esta sintaxis se puede utilizar varias veces en la barra de búsqueda para filtrar en ramas múltiples. La sintaxis previa `ref:refs/heads/`, aún es compatible, así que cualquier URL que se haya guardado seguirá funcionando.\n"
- - "Ahora está disponible la búsqueda de texto libre para las alertas de escaneo de código. Puedes buscar resultados del escaneo de código para encontrar alertas específicas rápidamente sin tener que conocer los términos de búsqueda exactos. La búsqueda se aplica a lo large del nombre, descripción y texto de ayuda de la alerta. La sintaxis es:\n\n- Una palabra única devuelve todas las coincidencias.\n- Las palabras de búsqueda múltiples devuelven coincidencias para cualquiera de las palabras.\n- Las palabras entre comillas dobles devuelven coincidencias exactas.\n- La palabra clave 'AND' devuelve coincidencias de palabras múltiples.\n"
- - '{% data variables.product.prodname_secret_scanning_caps %} agregó patrones para 23 proveedores de servicio nuevos. Para encontrar la lista actualizada de secretos compatibles, consulta la sección "[Acerca del escaneo de secretos](/code-security/secret-scanning/about-secret-scanning)".'
- - heading: 'Cambios a la API'
+ # https://github.com/github/releases/issues/1352
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."'
+
+ # https://github.com/github/releases/issues/1360
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."'
+
+ # https://github.com/github/releases/issues/1160
+ - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.'
+
+ # https://github.com/github/releases/issues/1454
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.'
+
+ # https://github.com/github/releases/issues/1375
+ - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).
+
+ # https://github.com/github/releases/issues/1335
+ # https://github.com/github/releases/issues/1314
+ - |
+ {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure.
+
+ Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure.
+
+ For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
+
+ 
+
+ # https://github.com/github/releases/issues/1324
+ - |
+ Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar.
+
+ The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work.
+
+ # https://github.com/github/releases/issues/1313
+ - |
+ Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is:
+
+ - A single word returns all matches.
+ - Multiple search words returns matches to either word.
+ - Words in double quotes returns exact matches.
+ - The keyword 'AND' returns matches to multiple words.
+
+ - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."'
+
+ - heading: API Changes
notes:
- - 'La compatibilidad con paginación se agregó a la terminar de "comparar dos confirmaciones" de la API de REST, la cual devuelve una lista de confirmaciones que se pueden alcanzar desde una confirmación o rama, pero no desde alguna otra. La API ahora también puede devolver los resultados para comparaciones de más de 250 confirmaciones. Para obtener más información, consulta la sección de "[Repositories](/rest/reference/repos#compare-two-commits)" de la API de REST y la sección de "[Navegar con paginación](/rest/guides/traversing-with-pagination)".'
- - 'La API de REST ahora puede utilizarse para reenviar mediante programación o verificar el estado de los webhooks. Para obtener más información, consulta las secciones "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," y "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.'
- - "Se han realizado mejoras al escaneo de código y a las API de la {% data variables.product.prodname_GH_advanced_security %}:\n\n- La API de escaneo de código ahora devuelve la versión de consulta de COdeQL que se utiliza para un análisis. Esto puede utilizarse para reproducir los resultados o confirmar un análisis que se utiliza como la consulta más reciente. Para obtener información, consulta la sección \"[Escaneo de código](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)\" en la documentación de la API de REST.\n-Los usuarios administrativos ahora pueden utilizar la API de REST para habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para repositorios utilizando el objeto `security_and_analysis` en `repos/{org}/{repo}`. Adicionalmente, los usuarios administrativos pueden verificar si la {% data variables.product.prodname_advanced_security %} se encuentra habilitada actualmente para un repositorio utilizando una solicitud de tipo `GET /repos/{owner}/{repo}`. Estos cambios de ayudan a administrar el acceso a los repositorios de {% data variables.product.prodname_advanced_security %} en escala. Para obtener más información, consulta la sección de \"[Repositories](/rest/reference/repos#update-a-repository)\" en la documentación de la API de REST.\n"
+ # https://github.com/github/releases/issues/1253
+ - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
+
+ # https://github.com/github/releases/issues/969
+ - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.
+
+ # https://github.com/github/releases/issues/1349
+ - |
+ Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs:
+
+ - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation.
+ - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
+
+ # No security/bug fixes for the RC release
+ # security_fixes:
+ # - PLACEHOLDER
+
+ # bugs:
+ # - PLACEHOLDER
+
known_issues:
- - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
- - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
- - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
- - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
- - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
- - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
- - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+
deprecations:
- - heading: 'Obsoletización de GitHub Enterprise Server 2.21'
+ - heading: Deprecation of GitHub Enterprise Server 2.21
notes:
- - '**{% data variables.product.prodname_ghe_server %} 2.21 se descontinuó el 6 de junio de 2021**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.'
- - heading: 'Obsoletización de GitHub Enterprise Server 2.22'
+ - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+ - heading: Deprecation of GitHub Enterprise Server 2.22
notes:
- - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuará el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.'
- - heading: 'Obsoletización del soporte para XenServer Hypervisor'
+ - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+ - heading: Deprecation of XenServer Hypervisor support
notes:
- - 'Desde la versión 3.1 de {% data variables.product.prodname_ghe_server %}, comenzaremos a descontinuar la compatibilidad con Xen Hypervisor. La obsoletización completa está programada para la versión 3.3 de {% data variables.product.prodname_ghe_server %}, siguiendo la ventana de obsoletización estándar de un año. Por favor, contacta al [Soporte de Github](https://support.github.com/contact) so tienes dudas o preguntas.'
- - heading: 'Eliminación de los servicios tradicionales de GitHub'
+ # https://github.com/github/docs-content/issues/4439
+ - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://support.github.com/contact) with questions or concerns.
+ - heading: Removal of Legacy GitHub Services
notes:
- - '{% data variables.product.prodname_ghe_server %} 3.2 elimina los registros de base de datos de GitHub Service sin utilizar. Hay más información disponible en la [publicación del anuncio de obsoletización](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).'
- - heading: 'Obsoletización de las terminales de la API de Aplicaciones OAuth y autenticación de la API a través de parámetros de consulta'
+ # https://github.com/github/releases/issues/1506
+ - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).'
+ - heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters
notes:
- - "Para prevenir el inicio de sesión o exposición accidental de los `access_tokens`, desalentamos el uso de las terminales de la API de las Aplicaciones OAuth y el uso de auth de API a través de parámetros de consultas. Visita las siguientes publicaciones para ver los reemplazos propuestos:\n\n*[Reemplazo para las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Reemplazo de auth a través de encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nSe pretende que estas terminales y rutas de auth se eliminen del {% data variables.product.prodname_ghe_server %} en la versión 3.4 de {% data variables.product.prodname_ghe_server %}.\n"
- - heading: 'Eliminación de los eventos de webhook y terminales tradicionales de las GitHub Apps'
+ # https://github.com/github/releases/issues/1316
+ - |
+ To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements:
+
+ * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)
+ * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)
+
+ These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.
+ - heading: Removal of legacy GitHub App webhook events and endpoints
notes:
- - "Se eliminaron dos eventos de webhook relacionados con las GitHub Apps tradicionales: `integration_installation` y `integration_installation_repositories`. En su lugar, deberías estar escuchando a los eventos de `installation` y `installation_repositories`.\n"
- - "La siguiente terminal de la API de REST se eliminó: `POST /installations/{installation_id}/access_tokens`. En su lugar, deberías etar utilizando aquella con designador de nombre: `POST /app/installations/{installation_id}/access_tokens`.\n"
+ # https://github.com/github/releases/issues/965
+ - |
+ Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events.
+ - |
+ The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`.
+
backups:
- - '{% data variables.product.prodname_ghe_server %} 3.2 requiere de por lo menos contar con [Las Utilidades de Respaldo 3.2.0 de GitHub Enterprise](https://github.com/github/backup-utils) para [Los Respaldos y Recuperación de Desastres](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).'
+ - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml
index 3ffe8ffef8..b5f39207ee 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml
@@ -1,126 +1,311 @@
date: '2021-09-28'
-intro: 'Para encontrar las instrucciones de mejora, consulta la sección "[Mejorar a {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".'
+intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
sections:
features:
- - heading: 'Patrones personalizados para el escaneo de secretos'
+ - heading: Custom patterns for secret scanning
notes:
- - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden especificar los patrones para el escaneo de secretos. Cuando se especifica un patrón nuevo, el escaneo de secretos busca dicho patrón en todo el historial de Git del repositorio, así como cualquier confirmación nueva.\n\nLos patrones definidos por los usuarios se encuentran en beta para {% data variables.product.prodname_ghe_server %} 3.2. Se pueden definir a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección \"[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)\".\n"
- - heading: 'Resumen de seguridad para la Seguridad Avanzada (beta)'
+ # https://github.com/github/releases/issues/1426
+ - |
+ {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits.
+
+ User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+ - heading: Security overview for Advanced Security (beta)
notes:
- - "Los clientes de la {% data variables.product.prodname_GH_advanced_security %} ahora tienen una vista de nivel de organización apra los riegos de seguridad de las aplicaciones que detecte el {% data variables.product.prodname_code_scanning %}, el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_secret_scanning %}. El resumen de seguridad muestra la habilitación de estado de las características de seguridad en cada repositorio, así como la cantidad de alertas que se detectan.\n\nAdicionalmente, el resumen de seguridad lista todas las alertas del {% data variables.product.prodname_secret_scanning %} a nivel organizacional. Tendremos vistas similares para el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_code_scanning %} en los lanzamientos futuros cercanos. Para obtener más información, consulta la sección \"[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)\".\n\n\n"
- - heading: 'Revisión de dependencias (beta)'
+ # https://github.com/github/releases/issues/1381
+ - |
+ {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected.
+
+ In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+ 
+
+ - heading: Dependency review (beta)
notes:
- - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden ver un diff enriquecido de las dependencias que cambiaron en una solicitud de cambios. La revisión de dependencias proporciona una vista fácil de entender de los cambios a las dependencias y de su impacto de seguridad en la pestaña de \"Archivos que cambiaron\" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron junto con la información de vulnerabilidades de estas dependencias. Para obtener más información, consulta la sección \"[Revisar los cambios de dependencias en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)\".\n"
- - heading: 'Ambientes de GitHub Actions'
+ # https://github.com/github/releases/issues/1364
+ - |
+ {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)."
+
+ - heading: GitHub Actions environments
notes:
- - "Los ambientes, las reglas de protección de ambiente y los secretos de ambiente ahora están disponibles en general para las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}. Para obtener más información, consulta la sección \"[Environments](/actions/reference/environments)\".\n"
- - heading: 'Autenticación por SSH con llaves seguras'
+ # https://github.com/github/releases/issues/1308
+ - |
+ Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)."
+
+ 
+
+ - heading: SSH authentication with security keys
notes:
- - "Ahora es compatible la autenticación por SSH utilizando una llave de seguridad FIDO2 cuando agregas una llave SSH de tipo `sk-ecdsa-sha2-nistp256@openssh.com` o `sk-ssh-ed25519@openssh.com` a tu cuenta. Las llaves de seguridad SSH almacenan material de llaves secretas en un dispositivo de hardware por separado, el cual requiere de verificación, tal como un tap, para operar. Para obtener más información, consulta la sección \"[Generar una clave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)\".\n"
- - heading: 'Temas oscuro y oscuro atenuado'
+ # https://github.com/github/releases/issues/1276
+ - |
+ SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+
+ - heading: 'Dark and dark dimmed themes'
notes:
- - "Ahora hay temas oscuro y opaco oscuro disponibles para la IU web. {% data variables.product.product_name %} empatará las preferencias de tu sistema si no has configurado las preferencias de tema en {% data variables.product.product_name %}. También puedes elegir qué temas estarán activos durante el día y la noche. Para obtener más información, consulta la sección \"[Administrar la configuración de tu tema](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n\n\n"
- - heading: 'Aprobar dominios no verificados para las notificaciones de correo electrónico'
+ # https://github.com/github/releases/issues/1260
+ - |
+ Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
+
+ 
+
+ - heading: 'Approving unverified domains for email notifications'
notes:
- - 'Los dominios que no se pueden verificar ahora pueden aprobarse para el enrutamiento de notificaciones por correo electrónico. Los propietarios de empresas y organizaciones podrán aprobar dominios y aumentar su política de restricción de notificaciones por correo electrónico automáticamente, lo cual permitirá que las notificaciones se envíen a los colaboradores, consultores, adquisiciones o a otros socios. para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" y "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."'
- - heading: 'Soporte para el almacenamiento de credenciales seguro del Administrador de Credenciales de Git (GCM) y autenticación multifactorial'
+ # https://github.com/github/releases/issues/1244
+ - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."
+
+ - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support'
notes:
- - "Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}.\n\nGCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository.\n"
+ # https://github.com/github/releases/issues/1406
+ - |
+ Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}.
+
+ GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository.
+
changes:
- - heading: 'Cambios en la administración'
+ - heading: Administration Changes
notes:
- - 'Se agregó un ajuste de "Política de Referente de Agente Usuario" a la configuración empresarial. Esto permite que un administrador configure una "Política de referente" más estricta para ocultar el nombre de host de una instalación de {% data variables.product.prodname_ghe_server %} de sitios externos. Este ajuste se encuentra inhabilitado predeterminadamente y los eventos de bitácoras de auditoría lo rastrean para los propietarios empresariales y el personal de las empresas cuando se habilita o inhabilita. Para obtener más información, consulta la sección "[Configurar la Política de Referente en tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".'
- - 'La revisión de salud de MySQL se cambió al uso de `mysqladmin ping` en vez de las verificaciones de TCP, lo cual elimina algo del ruido innecesario en la bitácora de errores de MySQL, las verificaciones de recuperación de fallos del orquestador se mejoraron para prevenir las recuperaciones de fallos de MySQL innecesarias al aplicar cambios de configuración del clúster.'
- - 'El servicio Resque, el cual da la compatibilidad con procesamiento de jobs en segundo plano, se reemplazó con Aqueduct Lite. este cambio hace que el sistema de jobs se pueda administrar más fácilmente y no debería afectar la experiencia del usuario. Para la administración y comandos de depuración nuevas de Aqueduct, consulta la sección "[Utilidades de la línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)".'
- - heading: 'Cambios de Token'
+ # https://github.com/github/releases/issues/1309
+ - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."
+
+ # https://github.com/github/releases/issues/1515
+ - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes.
+
+ # https://github.com/github/releases/issues/1287
+ - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."
+
+ - heading: Token Changes
notes:
- - "El formato de tokens de autenticación para {% data variables.product.product_name %} ha cambiado,. Dicho cambio afecta el formato de los tokens de acceso personal y de los tokens de acceso para las {% data variables.product.prodname_oauth_apps %}, así como de los tokens de usuario a servidor, de servidor a servidor y de actualización para {% data variables.product.prodname_github_apps %}.\n\nLos diferentes tipos de token ahora tienen prefijos identificables únicos, los cuales permiten que el escaneo de secretos detecten los tokens para que puedas mitigar el impacto de que alguien confirme un token accidentalmente en un repositorio. {% data variables.product.company_short %} recomienda actualizar los tokens existentes tan pronto como te sea posible. Para obtener más información, consulta las secciones \"[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)\" y \"[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)\".\n"
- - heading: 'Cambios de repositorios'
+ # https://github.com/github/releases/issues/1235
+ - |
+ The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}.
+
+ The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
+
+ - heading: 'Repositories changes'
notes:
- - 'Los repositorios en los perfiles de usuario y en los perfiles de organización ahora son compatibles con la clasificación por conteo de estrellas.'
- - 'Cuando veas el historial de confirmación de un archivo único, ahora puedes hacer clic en {% octicon "file-code" aria-label="The code icon" %} para ver dicho archivo en algún punto selecto del historial.'
- - 'Cuando un submódulo se define con una ruta relativa en {% data variables.product.product_location %}, el submódulo ahora se puede hacer clic en la interfaz web. Al hacer clic en el submódulo de la interfaz web le llevará al repositorio enlazado. Anteriormente, sólo los submódulos con URLs absolutas podían hacer clic. Esto es soportado para rutas relativas para los repositorios con el mismo propietario que siguen el patrón ..REPOSITORY o rutas relativas de repositorios con un propietario diferente que siga el patrón ../OWNER/REPOSITORY. Para obtener más información sobre cómo trabajar con submódulos, consulta la sección [Trabajar con submódulos](https://github.blog/2016-02-01-working-with-submodules/) en {% data variables.product.prodname_blog %}.'
- - 'La IU web ahora puede utilizarse para sincronizar una rama desactualizada de una bifurcación con la rama ascendente de dicha bifurcación. Si no hay conflictos de fusión entre las ramas, la rama se actualizará ya sea mediante un envío rápido o mediante la fusión desde la parte ascendente. Si hay conflictos, se te pedirá crear una solicitud de cambios para resolverlos. Para obtener más información, consulta la sección "[Sincronizar una bifurcación](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)".'
- - heading: 'Cambios en el Lenguaje de Marcado'
+ # https://github.com/github/releases/issues/1295
+ - Repositories on user profiles and organization profiles now support sorting by star count.
+
+ # https://github.com/github/releases/issues/1327
+ - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history.
+
+ # https://github.com/github/releases/issues/1254
+ - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}.
+
+ # https://github.com/github/releases/issues/1250
+ - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."
+
+ - heading: 'Markdown changes'
notes:
- - 'El editor de lenguaje de marcado que se utiliza al crear o editar un lanzamiento en un repositorio ahora tiene una barra de herramientas para edición de texto. Para obtener más información, consulta la sección "[Adminsitrar los lanzamientos en un repositorio](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)".'
- - '{% data variables.product.product_name %} ahora tiene compatibilidad para cargar archivos de video en donde sea que utilices lenguaje de marcado. Comparte demostraciones, pasos de reproducción y más en los comentarios de tus propuestas y solicitudes de cambio, así como en los archivos de lenguaje de marcado dentro de los repositorios, tales como los README. Para obtener más información, consulta la sección "[Adjuntar archivos](/github/writing-on-github/working-with-advanced-formatting/attaching-files)".'
- - 'Los archivos de lenguaje de marcado ahora generarán una tabla de contenido automáticamente en el encabezado cuando haya 2 o más encabezados. La tabla de contenido es interactiva y enlaza a la sección seleccionada. Los 6 niveles de encabezado del lenguaje de marcado son compatibles.'
- - 'Hay un atajo de teclado nuevo, `cmd+e` en macOS o `ctrl+e` en Windows, para insertar bloques de código en los archivos, propuestas, solicitudes de cambio y comentarios de Lenguaje de Marcado.'
- - 'El agregar `?plain=1` a la URL en cualquier archivo de lenguaje de marcado ahora mostrará al archivo sin procesar y con números de línea. La vista simple puede utilizarse para enlazar a otros usuarios a líneas específicas. Por ejemplo, el agregar `?plain=1#L52` resaltará la línea 52 del archivo de marcado en texto simple. Para obtener más información, consulta la sección "[Crear un enlace permanente a un fragmento de código](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)".'
- - heading: 'Cambios en propuestas y sollicitudes de cambio'
+ # https://github.com/github/releases/issues/1477
+ - The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."
+
+ # https://github.com/github/releases/issues/1169
+ - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
+
+ # https://github.com/github/releases/issues/1269
+ - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported.
+
+ # https://github.com/github/releases/issues/1294
+ - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.'
+
+ # https://github.com/github/releases/issues/1474
+ - Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."
+
+ - heading: 'Issues and pull requests changes'
notes:
- - 'Con la [versión más reciente de Octicons](https://github.com/primer/octicons/releases), los estados de las propuestas y solicitudes de cambios ahora son más fáciles de distinguir visualmente para que puedas escanear los estados de forma más sencilla. Para obtener más información consulta la sección [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).'
- - 'Ahora tenemos disponible una regla de protección de rama de "Requerir la resolución de la conversación antes de fusionar" y un menú de "Conversaciones". Descubre fácilmente tus comentarios de solicitudes de cambios desde la pestaña de "Archivos que cambiaron" y requiere qeu todas tus conversaciones en solicitudes de cambio se resuelvan antes de fusionarse. Para obtener más información, consulta las secciones "[Acerca de las revisiones de solicitudes de cambio](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" y "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)".'
- - 'Para prevenir la fusión de cambios inesperados después de habilitar la fusión automática para una solicitud de cambios, ahora se inhabilitó esta opción automáticamente cuando un usuario sin acceso de escritura al repositorio sube estos cambios. Los usuarios que no tengan permisos de escritura aún pueden actualizar la solicitud de cambios con aquellos de la rama base cuando se habilita la fusión automática. Para prevenir que un usuario malintencionado utilice un conflicto de fusión para introducir cambios inesperados a la solicitud de cambios, la fusión automática para la solicitud de cambios se encuentra inhabilitada si dicha actualización causa un conflicto de fusión. Para obtener más información sobre la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".'
- - 'Las personas con permisos de mantenimiento ahora pueden administrar el ajuste de "Permitir la fusión automática" a nivel de repositorio. Este ajuste, el cual a menudo se encuentra inhabilitado, controla si la fusión automática está disponible para las solicitudes de cambios en el repositorio., Anteriormente, solo las personas con permisos administrativos podían administrar este ajuste. Adicionalmente, este ajuste ahora puede controlarse utilizando las API de REST para "[Crear repositorio](/rest/reference/repos#create-an-organization-repository)" y "[Actualizar repositorio](/rest/reference/repos#update-a-repository)". Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio]](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)".'
- - 'La selección de propuestas y solicitudes de cambio de los asignados ahora es compatible con la búsqueda de escritura anticipada, así que puedes encontrar usuarios en tu organización más rápidamente. Adicionalmente, las clasificaciones de resultados de búsqueda se actualizaron para preferir las coincidencias al inicio del nombre de usuario de una persona o nombre de perfil.'
- - 'Cuando se solicita una revisión de un equipo de más de 100 personas, los desarrolladores ahora muestran una caja de diálogo de confirmación para poder prevenir las notificaciones innecesarias para los equipos grandes.'
- - 'Ahora hay compatibilidad con tener `code blocks` con comilla inversa en los títulos de las propuestas y en cualquier lugar en el que se referencien propuestas y solicitudes de cambios en {% data variables.product.prodname_ghe_server %}.'
- - 'Los eventos para las solicitudes de cambios y revisiones de solicitudes de cambios ahora se incluyen en la bitácora de auditoría tanto para [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) como para [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). estos eventos ayudan a que los administradores monitoreen mejor la actividad de las solicitudes de cambios y ayuden a garantizar que se cumplan los requisitos de seguridad y cumplimiento. Los eventos pueden verse desde la IU web, exportarse como CSV o JSON o acceder a ellos a través de la API de REST. También puedes buscar la bitácora de auditoría para los eventos de solicitudes de cambio específicos. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)".'
- - heading: 'Cambios a las ramas'
+ # https://github.com/github/releases/issues/1413
+ - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).
+
+ # https://github.com/github/releases/issues/1419
+ - A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."
+
+ # https://github.com/github/releases/issues/1279
+ - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+
+ # https://github.com/github/releases/issues/1550
+ - People with maintain permissions can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin permissions could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)."
+
+ # https://github.com/github/releases/issues/1201
+ - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name.
+
+ # https://github.com/github/releases/issues/1430
+ - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams.
+
+ # https://github.com/github/releases/issues/1293
+ - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}.
+
+ # https://github.com/github/releases/issues/1300
+ - Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."
+
+ - heading: 'Branches changes'
notes:
- - "El nombre de rama predeterminado para los repositorios nuevos ahora es `main`. Los repositorios existentes no se verán impactados por este cambio. Si los usuarios, propietarios de organizaciones o propietarios de empresas ya especificaron una rama predeterminada para repositorios nuevos anteriormente, tampoco se les impactará.\n\nSi quieres configurar un nombre de rama predeterminada diferente, puedes hacerlo en los ajustes de [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), o [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name).\n"
- - "Las ramas, incluyendo a la predeterminada, ahora pueden volver a nombrarse utilizando la IU web de {% data variables.product.product_name %}. Cuando una rama se vuelve a nombrar, cualquier solicitud de cambios abierta y lanzamiento de borrador que apunten a la rama que se volvió a nombrar se redirigirá automáticamente y las reglas de protección de rama que referencien explícitamente a la rama que se volvió a nombrar se actualizarán.\n\nSe requieren permisos administrativos para volver a nombrar la rama predeterminada, pero es suficiente contar con permisos de escritura para volver a nombrar otras ramas.\n\nPara ayudar a hacer el cambio con tanta continuidad como sea posible para los usuarios:\n\n* Se muestra un aviso a los contribuyentes, mantenedores y administradores de la página de inicio del repositorio, el cual contiene instrucciones para actualizar su repositorio local.\n*Las solicitudes web para la rama antigua se redireccionarán.\n* Se devolverá una respuesta HTTP de \"se movió permanentemente\" a todo llamado de la API de REST.\n* Se mostrará un mensaje informativo para los usuarios de la línea de comandos de Git que suban información a la rama antigua.\n\nPara obtener más información, consulta la sección \"[Volver a nombrar una rama](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)\".\n"
- - heading: 'Cambioas a las GitHub Actions'
+ # https://github.com/github/releases/issues/885
+ - |
+ The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted.
+
+ If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings.
+
+ # https://github.com/github/releases/issues/981
+ - |
+ Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated.
+
+ Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches.
+
+ To help make the change as seamless as possible for users:
+
+ * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository.
+ * Web requests to the old branch will be redirected.
+ * A "moved permanently" HTTP response will be returned to REST API calls.
+ * An informational message is displayed to Git command line users that push to the old branch.
+
+ For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)."
+
+ - heading: 'GitHub Actions changes'
notes:
- - 'Las {% data variables.product.prodname_actions %} ahora te permiten controlar los permisos que se otorgan al secreto del `GITHUB_TOKEN`. El `GITHUB_TOKEN` es un secreto que se genera automáticamente y te permite hacer llamados autenticados a la API de {% data variables.product.product_name %} en tus ejecuciones de flujo de trabajo. Las {% data variables.product.prodname_actions %} generan un token nuevo para cada job y hacen que el token venza cuando se completa el job. El token a menudo tiene permisos de `escritura` para varias [Terminales de la API](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), con excepción de los casos de las solicitudes de cambios de las bifurcaciones, los cuales siempre se marcan como de `lectura`. Estos ajustes nuevos te permiten seguir el principio de los menores privilegios necesarios en tus flujos de trabajo,. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".'
- - 'El {% data variables.product.prodname_cli %} 1.9 y posterior te permiten trabajar con las {% data variables.product.prodname_actions %} en tu terminal. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).'
- - 'La bitácora de auditoría ahora incluye eventos asociados con las ejecuciones de flujo de trabajo de {% data variables.product.prodname_actions %}. Estos datos proporcionan un conjunto de datos ampliamente expandidos para los administradores, así como auditorías de cumplimiento. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)".'
- - '{% data variables.product.prodname_ghe_server %} 3.2 contiene mejoras de rendimiento para la concurrencia de los jobs con {% data variables.product.prodname_actions %}. Para obtener más información sobre las metas de rendimiento nuevas de acuerdo con los rangos de configuraciones de CPU y memoria, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".'
- - 'The [{% data variables.product.prodname_actions %} Runner](https://github.com/actions/runner) application in {% data variables.product.prodname_ghe_server %} 3.2 has been updated to [v2.279.0](https://github.com/actions/runner/releases/tag/v2.279.0).'
- - heading: 'Cambios a los GitHub packages'
+ # https://github.com/github/releases/issues/1227
+ - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."'
+
+ # https://github.com/github/releases/issues/1280
+ - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).'
+
+ # https://github.com/github/releases/issues/1157
+ - The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."
+
+ # https://github.com/github/releases/issues/1587
+ - |
+ {% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+ * The "Maximum Concurrency" values were modified to reflect our most up to date performance testing. [Updated: 2021-12-07]
+
+ - The [{% data variables.product.prodname_actions %} Runner](https://github.com/actions/runner) application in {% data variables.product.prodname_ghe_server %} 3.2 has been updated to [v2.279.0](https://github.com/actions/runner/releases/tag/v2.279.0).
+
+ - heading: 'GitHub Packages changes'
notes:
- - 'Cualquier paquete o versión de paquete del {% data variables.product.prodname_registry %} ahora se puede borrar de la IU web de {% data variables.product.product_name %}. También puedes deshacer el borrado de cualquier paquete o versión de paquete dentro de los primeros 30 días. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".'
- - heading: 'Cambios al Dependabot y a la gráfica de Dependencias'
+ # https://github.com/github/releases/issues/1088
+ - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)".
+
+ - heading: 'Dependabot and Dependency graph changes'
notes:
- - 'La gráfica de dependencias ahora puede habilitarse utilizando la Consola de Administración en vez de necesitar la ejecución de un comando en el shell administrativo. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables de {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".'
- - 'Ahora, las notificaciones para {% data variables.product.prodname_dependabot_alerts %} múltiples se agrupan si se descubren al mismo tiempo. Esto reduce significativamente el volumen de notificaciones de alertas del {% data variables.product.prodname_dependabot %} que reciben los usuarios. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).'
- - 'Las gráficas de dependencias y {% data variables.product.prodname_dependabot_alerts %} ahora son compatibles con los módulos de Go. {% data variables.product.prodname_ghe_server %} analiza los archivos de `go.mod` de un repositorio para entender las dependencias del mismo. En conjunto con las asesorías de seguridad, la gráfica de dependencias proporciona la información necesaria para alertar a los desarrolladores sobre las dependencias vulnerables. Para obtener más información sobre cómo habilitar la gráfica de dependencias en los repositorios privados, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)".'
- - 'Los ajustes de notificación predeterminados para las alertas de seguridad han cambiado. Anteriormente, si tenías permiso para ver las alertas de seguridad en un repositorio, hubieras recibido las notificaciones de dicho repositorio mientras tu configuración permitiera las notificaciones de alertas de seguridad. Ahora debes decidir unirte a las notificaciones de alertas de seguridad observando el repositorio. Se te notificará si seleccionas `Toda la actividad` o si configuras `Personalizado` para incluir las `Alertas de seguridad`. Todos los repositorios existentes se migrarán automáticamente a estos ajustes nuevos y seguirás recibiendo notificaciones; sin embargo, cualquier repositorio nuevo requerirá que decidas unirte observando el repositorio. Para obtener más información, consulta las secciones "[Configurar notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" y "[Administrar las alertas del escaneo de secretos](/code-security/secret-security/managing-alerts-from-secret-scanning)".'
- - heading: 'Cambios al escaneo de código y de secretos'
+ # https://github.com/github/releases/issues/1537
+ - The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+
+ # https://github.com/github/releases/issues/1153
+ - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).
+
+ # https://github.com/github/releases/issues/1371
+ - Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository's `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."
+
+ # https://github.com/github/releases/issues/1538
+ - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. For more information see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+ - heading: 'Code scanning and secret scanning changes'
notes:
- - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql %} ahora genera información diagnóstica para todos los lenguajes compatibles. Esto ayuda a mantener el estado de la base de datos creada para entender el estado y calidad del análisis que se realizó. La información diagnóstica se encuentra disponible desde la [versión 2.5.6](https://github.com/github/codeql-cli-binaries/releases) del {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). Puedes ver esta información diagnóstica detallada en las bitácoras para {% data variables.product.prodname_codeql %} de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Visualizar las bitácoras de escaneo de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)".'
- - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql_cli %} ahora es compatible con el análisis de diversos lenguajes durante una compilación sencilla. Esto facilita el ejecutar análisis de código para utilizar sistemas de IC/DC diferentes a los de las {% data variables.product.prodname_actions %}. El modo nuevo del comando `codeql database create` se encuentra disponible desde la [versión 2.5.6] (https://github.com/github/codeql-cli-binaries/releases) del [{% data variables.product.prodname_codeql_cli %}] (https://codeql.github.com/docs/codeql-cli/). Para obtener más información sobre cómo configurar esto, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)".'
- - 'Las alertas de {% data variables.product.prodname_code_scanning_capc %} de todas las herramientas habilitadas ahora se muestran en una lista consolidada para que puedas priorizar fácilmente entre todas ellas. Puedes ver las alertas desde una herramienta específica utilizando le filtro de "Herramienta" y los de "Regla" y "Etiqueta" se actualizarán dinámicamente con base en tu selección de "Herramientas".'
- - 'El {% data variables.product.prodname_code_scanning_capc %} cib {% data variables.product.prodname_codeql %} ahora incluye soporte beta para analizar código de C++20. Esto solo está disponible cuando creas bases de código con GCC en Linux. Los módulos de C++20 aún no son compatibles.'
- - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró al agregar compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) y al incrementar la cobertura de nuestros modelos de marcos de trabajo y librerías para varios lenguajes ({C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), y [Java](https://github.com/github/codeql/tree/main/java)). Como resultado, el {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuarios no confiables, revisar los pasos a través de los cuales fluyen los datos e identificar hundimientos potencialmente peligrosos en los cuales podrían terminar estos datos,. Esto da como resultado una mejora general de la calidad de las alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección de [registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).'
- - "El {% data variables.product.prodname_code_scanning_capc %} ahora muestra niveles de `gravedad de seguridad` para las alertas del Code QL. Puedes configurar qué niveles de `gravedad de seguridad` ocasionarán un fallo de verificación para una solicitud de cambios. El nivel de gravedad de las alertas de seguridad puede ser `crítico`, `alto, `medio` o `bajo`. Predeterminadamente, cualquier alerta del {% data variables.product.prodname_code_scanning %} con un `nivel de gravedad` que sea `crítico` o `alto` ocasionará que una solicitud de cambios falle.\n\nAdicionalmetnte, ahora también puedes configurar qué niveles de gravedad ocasionarán que la verificación de solicitudes de cambio falle para las alertas que no sean de seguridad. Puedes configurar este comportamiento a nivel de repositorio y definir si las alertas con gravedad de `error`, `advertencia` o `nota` ocasionarán que una verificación de solicitud de cambio falle. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} que no sean de seguridad y tengan un nivel de gravedad de `error` ocasionarán que la verificación de una solicitud de cambios falle.\n\nPara obtener más información, consulta la sección \"[Definir qué alertas de niveles de gravedad ocasionan que falle la verificación de las solicitudes de cambio]](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)\".\n\n\n"
- - "Las mejoras al filtro de rama para las alertas del {% data variables.product.prodname_code_scanning %} dejan más claro qué alertas del {% data variables.product.prodname_code_scanning %} se están mostrando en la página de alertas. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} se filtran para mostrar únicamente las alertas de la rama predeterminada del repositorio. Puedes utilizar el filtro de rama para mostrar las alertas en cualquiera de las ramas no predeterminadas. Cualquier filtro de rama que se haya aplicado se mostrará en la barra de búsqueda.\n\nLa sintaxis de búsqueda también se simplificó como `branch:`. Esta sintaxis se puede utilizar varias veces en la barra de búsqueda para filtrar en ramas múltiples. La sintaxis previa `ref:refs/heads/`, aún es compatible, así que cualquier URL que se haya guardado seguirá funcionando.\n"
- - "Ahora está disponible la búsqueda de texto libre para las alertas de escaneo de código. Puedes buscar resultados del escaneo de código para encontrar alertas específicas rápidamente sin tener que conocer los términos de búsqueda exactos. La búsqueda se aplica a lo large del nombre, descripción y texto de ayuda de la alerta. La sintaxis es:\n\n- Una palabra única devuelve todas las coincidencias.\n- Las palabras de búsqueda múltiples devuelven coincidencias para cualquiera de las palabras.\n- Las palabras entre comillas dobles devuelven coincidencias exactas.\n- La palabra clave 'AND' devuelve coincidencias de palabras múltiples.\n"
- - '{% data variables.product.prodname_secret_scanning_caps %} agregó patrones para 23 proveedores de servicio nuevos. Para encontrar la lista actualizada de secretos compatibles, consulta la sección "[Acerca del escaneo de secretos](/code-security/secret-scanning/about-secret-scanning)".'
- - heading: 'Cambios a la API'
+ # https://github.com/github/releases/issues/1352
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."'
+
+ # https://github.com/github/releases/issues/1360
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."'
+
+ # https://github.com/github/releases/issues/1160
+ - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.'
+
+ # https://github.com/github/releases/issues/1454
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.'
+
+ # https://github.com/github/releases/issues/1375
+ - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).
+
+ # https://github.com/github/releases/issues/1335
+ # https://github.com/github/releases/issues/1314
+ - |
+ {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure.
+
+ Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure.
+
+ For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
+
+ 
+
+ # https://github.com/github/releases/issues/1324
+ - |
+ Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar.
+
+ The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work.
+
+ # https://github.com/github/releases/issues/1313
+ - |
+ Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is:
+
+ - A single word returns all matches.
+ - Multiple search words returns matches to either word.
+ - Words in double quotes returns exact matches.
+ - The keyword 'AND' returns matches to multiple words.
+
+ - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."'
+
+ - heading: API Changes
notes:
- - 'La compatibilidad con paginación se agregó a la terminar de "comparar dos confirmaciones" de la API de REST, la cual devuelve una lista de confirmaciones que se pueden alcanzar desde una confirmación o rama, pero no desde alguna otra. La API ahora también puede devolver los resultados para comparaciones de más de 250 confirmaciones. Para obtener más información, consulta la sección de "[Repositories](/rest/reference/repos#compare-two-commits)" de la API de REST y la sección de "[Navegar con paginación](/rest/guides/traversing-with-pagination)".'
- - 'La API de REST ahora puede utilizarse para reenviar mediante programación o verificar el estado de los webhooks. Para obtener más información, consulta las secciones "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," y "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.'
- - "Se han realizado mejoras al escaneo de código y a las API de la {% data variables.product.prodname_GH_advanced_security %}:\n\n- La API de escaneo de código ahora devuelve la versión de consulta de COdeQL que se utiliza para un análisis. Esto puede utilizarse para reproducir los resultados o confirmar un análisis que se utiliza como la consulta más reciente. Para obtener información, consulta la sección \"[Escaneo de código](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)\" en la documentación de la API de REST.\n-Los usuarios administrativos ahora pueden utilizar la API de REST para habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para repositorios utilizando el objeto `security_and_analysis` en `repos/{org}/{repo}`. Adicionalmente, los usuarios administrativos pueden verificar si la {% data variables.product.prodname_advanced_security %} se encuentra habilitada actualmente para un repositorio utilizando una solicitud de tipo `GET /repos/{owner}/{repo}`. Estos cambios de ayudan a administrar el acceso a los repositorios de {% data variables.product.prodname_advanced_security %} en escala. Para obtener más información, consulta la sección de \"[Repositories](/rest/reference/repos#update-a-repository)\" en la documentación de la API de REST.\n"
+ # https://github.com/github/releases/issues/1253
+ - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
+
+ # https://github.com/github/releases/issues/969
+ - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.
+
+ # https://github.com/github/releases/issues/1349
+ - |
+ Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs:
+
+ - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation.
+ - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
+
+ # No security/bug fixes for the RC release
+ # security_fixes:
+ # - PLACEHOLDER
+
+ # bugs:
+ # - PLACEHOLDER
+
known_issues:
- - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
- - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
- - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
- - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
- - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
- - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
- - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+
deprecations:
- - heading: 'Obsoletización de GitHub Enterprise Server 2.21'
+ - heading: Deprecation of GitHub Enterprise Server 2.21
notes:
- - '**{% data variables.product.prodname_ghe_server %} 2.21 se descontinuó el 6 de junio de 2021**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.'
- - heading: 'Obsoletización de GitHub Enterprise Server 2.22'
+ - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+ - heading: Deprecation of GitHub Enterprise Server 2.22
notes:
- - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuará el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.'
- - heading: 'Obsoletización del soporte para XenServer Hypervisor'
+ - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+ - heading: Deprecation of XenServer Hypervisor support
notes:
- - 'Desde la versión 3.1 de {% data variables.product.prodname_ghe_server %}, comenzaremos a descontinuar la compatibilidad con Xen Hypervisor. La obsoletización completa está programada para la versión 3.3 de {% data variables.product.prodname_ghe_server %}, siguiendo la ventana de obsoletización estándar de un año. Por favor, contacta al [Soporte de Github](https://support.github.com/contact) so tienes dudas o preguntas.'
- - heading: 'Eliminación de los servicios tradicionales de GitHub'
+ # https://github.com/github/docs-content/issues/4439
+ - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://support.github.com/contact) with questions or concerns.
+ - heading: Removal of Legacy GitHub Services
notes:
- - '{% data variables.product.prodname_ghe_server %} 3.2 elimina los registros de base de datos de GitHub Service sin utilizar. Hay más información disponible en la [publicación del anuncio de obsoletización](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).'
- - heading: 'Obsoletización de las terminales de la API de Aplicaciones OAuth y autenticación de la API a través de parámetros de consulta'
+ # https://github.com/github/releases/issues/1506
+ - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).'
+ - heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters
notes:
- - "Para prevenir el inicio de sesión o exposición accidental de los `access_tokens`, desalentamos el uso de las terminales de la API de las Aplicaciones OAuth y el uso de auth de API a través de parámetros de consultas. Visita las siguientes publicaciones para ver los reemplazos propuestos:\n\n*[Reemplazo para las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Reemplazo de auth a través de encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nSe pretende que estas terminales y rutas de auth se eliminen del {% data variables.product.prodname_ghe_server %} en la versión 3.4 de {% data variables.product.prodname_ghe_server %}.\n"
- - heading: 'Eliminación de los eventos de webhook y terminales tradicionales de las GitHub Apps'
+ # https://github.com/github/releases/issues/1316
+ - |
+ To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements:
+
+ * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)
+ * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)
+
+ These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.
+ - heading: Removal of legacy GitHub App webhook events and endpoints
notes:
- - "Se eliminaron dos eventos de webhook relacionados con las GitHub Apps tradicionales: `integration_installation` y `integration_installation_repositories`. En su lugar, deberías estar escuchando a los eventos de `installation` y `installation_repositories`.\n"
- - "La siguiente terminal de la API de REST se eliminó: `POST /installations/{installation_id}/access_tokens`. En su lugar, deberías etar utilizando aquella con designador de nombre: `POST /app/installations/{installation_id}/access_tokens`.\n"
+ # https://github.com/github/releases/issues/965
+ - |
+ Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events.
+ - |
+ The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`.
+
backups:
- - '{% data variables.product.prodname_ghe_server %} 3.2 requiere de por lo menos contar con [Las Utilidades de Respaldo 3.2.0 de GitHub Enterprise](https://github.com/github/backup-utils) para [Los Respaldos y Recuperación de Desastres](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).'
+ - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml
new file mode 100644
index 0000000000..2d761493fc
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml
@@ -0,0 +1,25 @@
+date: '2021-12-07'
+sections:
+ security_fixes:
+ - 'Support bundles could include sensitive files if they met a specific set of conditions.'
+ bugs:
+ - 'In some cases when Actions was not enabled, `ghe-support-bundle` reported an unexpected message `Unable to find MS SQL container.`'
+ - 'Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.'
+ - 'A misconfiguration in the Management Console caused scheduling errors.'
+ - 'Docker would hold log files open after a log rotation.'
+ - 'Migrations could get stuck due to incorrect handling of `blob_path` values that are not UTF-8 compatible.'
+ - 'GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments.'
+ - 'Pagination links on org audit logs would not persist query parameters.'
+ - 'During a hotpatch, it was possible for duplicate hashes if a transition ran more than once.'
+ changes:
+ - 'Clarifies explanation of Actions path-style in documentation.'
+ - 'Updates support contact URLs to use the current support site, support.github.com.'
+ - 'Additional troubleshooting provided when running `ghe-mssql-diagnostic`.'
+ known_issues:
+ - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
+ - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+ - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+ - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+ - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+ - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
+ - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml
index ab3c6a4e98..cf185c5c31 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml
@@ -1,6 +1,6 @@
date: '2021-11-09'
release_candidate: true
-deprecated: false
+deprecated: true
intro: "{% note %}\n\n**Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.\n\n{% endnote %}\n\nFor upgrade instructions, see \"[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server).\"\n"
sections:
features:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml
new file mode 100644
index 0000000000..99bf26343c
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml
@@ -0,0 +1,114 @@
+date: '2021-12-07'
+intro: 'For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command.'
+sections:
+ features:
+ - heading: 'Security Manager role'
+ notes:
+ - "Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The \"security manager\" role can be applied to any team and grants the team's members the following access:\n\n- Read access on all repositories in the organization.\n- Write access on all security alerts in the organization.\n- Access to the organization-level security tab.\n- Write access on security settings at the organization level.\n- Write access on security settings at the repository level.\n\nFor more information, see \"[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"\n"
+ - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling'
+ notes:
+ - "{% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.\n\nEphemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management.\n\nYou can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.\n\nFor more information, see \"[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)\" and \"[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job).\"\n"
+ - heading: 'Dark high contrast theme'
+ notes:
+ - "A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.\n\n\n\nFor more information about changing your theme, see \"[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings).\"\n"
+ changes:
+ - heading: 'Cambios en la administración'
+ notes:
+ - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
+ - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
+ - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
+ - 'A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.'
+ - heading: 'Cambios de Token'
+ notes:
+ - "An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original.\n\nWhen using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see \"[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).\"\n"
+ - heading: 'Notifications changes'
+ notes:
+ - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.'
+ - heading: 'Cambios de repositorios'
+ notes:
+ - 'Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code.'
+ - 'If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list.'
+ - 'When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request.'
+ - 'You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers.'
+ - 'When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."'
+ - 'A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).'
+ - 'You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)."'
+ - heading: 'Cambios en el Lenguaje de Marcado'
+ notes:
+ - "You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments.\n\n* To add quotes, use cmd shift . on Mac, or ctrl shift . on Windows and Linux.\n* To add an ordered list, use cmd shift 7 on Mac, or ctrl shift 7 on Windows and Linux.\n* To add an unordered list, use cmd shift 8 on Mac, or ctrl shift 8 on Windows and Linux.\n\nSee \"[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)\" for a full list of available shortcuts.\n"
+ - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."'
+ - 'When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.'
+ - 'You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."'
+ - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.'
+ - 'When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.'
+ - heading: 'Cambios en propuestas y sollicitudes de cambio'
+ notes:
+ - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."'
+ - "Improvements have been made to help teams manage code review assignments. You can now:\n\n- Limit assignment to only direct members of the team.\n- Continue with automatic assignment even if one or more members of the team are already requested.\n- Keep a team assigned to review even if one or more members is newly assigned.\n\nThe timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.\n\nFor more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).\n"
+ - 'You can now filter pull request searches to only include pull requests you are directly requested to review.'
+ - 'Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."'
+ - heading: 'Cambioas a las GitHub Actions'
+ notes:
+ - 'You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."'
+ - '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"
+ - '{% data variables.product.prodname_ghe_server %} 3.3 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."'
+ - 'To mitigate insider man in the middle attacks when using actions resolved through {% data variables.product.prodname_github_connect %} to {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.prodname_ghe_server %}, the actions namespace (`owner/name`) is retired on use. Retiring the namespace prevents that namespace from being created on your {% data variables.product.prodname_ghe_server %} instance, and ensures all workflows referencing the action will download it from {% data variables.product.prodname_dotcom_the_website %}.'
+ - 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)."'
+ - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.'
+ - heading: 'Cambios al escaneo de código y de secretos'
+ notes:
+ - 'The depth of {% data variables.product.prodname_codeql %}''s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.'
+ - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
+ - "Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request.\n\nSome other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).\n"
+ - 'You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).'
+ - 'User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository''s entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."'
+ - heading: 'API and webhook changes'
+ notes:
+ - 'Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)."'
+ - 'You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."'
+ - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Repositories](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.'
+ - 'Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."'
+ - 'You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.'
+ - 'GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository''s issues and pull requests, and to access a public repository''s comments and content.'
+ - 'When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn''t include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.'
+ - "A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call.\n\nCommits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).\n"
+ - 'When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.'
+ - heading: 'Performance Changes'
+ notes:
+ - 'Page loads and jobs are now significantly faster for repositories with many Git refs.'
+ known_issues:
+ - 'After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.'
+ - 'On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.'
+ - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+ - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+ - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+ - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+ - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
+ - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
+ deprecations:
+ - heading: 'Obsoletización de GitHub Enterprise Server 2.22'
+ notes:
+ - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuó el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.'
+ - heading: 'Deprecation of GitHub Enterprise Server 3.0'
+ notes:
+ - '**{% data variables.product.prodname_ghe_server %} 3.0 se descontinuará el 16 de febrero de 2022**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.'
+ - heading: 'Obsoletización del soporte para XenServer Hypervisor'
+ notes:
+ - 'Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.'
+ - heading: 'Deprecation of OAuth Application API endpoints and API authentication using query parameters'
+ notes:
+ - "To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements:\n\n* [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nThese endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.\n"
+ - heading: 'Deprecation of the CodeQL runner'
+ notes:
+ - 'The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).'
+ - heading: 'Deprecation of custom bit-cache extensions'
+ notes:
+ - "Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3.\n\nAny repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated.\n\nRepositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.\n\nTo start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the **Schedule** button.\n"
+ backups:
+ - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
diff --git a/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml b/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml
index 62827a6cf5..0931904dc8 100644
--- a/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml
+++ b/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml
@@ -9,11 +9,9 @@ sections:
heading: 'GitHub Actions beta'
notes:
- |
- [Las {% data variables.product.prodname_actions %}](https://github.com/features/actions)son una solución poderosa y flexible de IC/DC y automatización de flujos de trabajo. Para obtener más información, consulta la sección "[Introducción a las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)."
+ [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[Introduction to {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)."
- Las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %} utilizan un [{% data variables.actions.hosted_runner %}] nuevo (/actions/using-github-hosted-runners/about-ae-hosted-runners), el cual solo se encuentra disponible para {% data variables.product.product_name %} y que te permite personalizar el tamaño, imágenes y configuración de red de los ejecutores. Estos ejecutores son un ambiente de cómputo de IC con servicios finalizados y que cuentan con auto-escalamiento y administración y que {% data variables.product.company_short %} administra en su totalidad. Durante el beta, usar los {% data variables.actions.hosted_runner %}s es gratuito. Para obtener más información, consulta la sección "[Agregar {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)."
-
- Por favor, toma en cuenta que cuando se habiliten las {% data variables.product.prodname_actions %} durante esta mejora, se mostrarán dos organizaciones llamadas "GitHub Actions" (@**actions** y @**github**) en {% data variables.product.product_location %}. {% data variables.product.prodname_actions %} requiere estas organizaciones. los usuarios de nombre @**ghost** y @**actions** aparecerán como los actores para la creación de estas organizaciones en la bitácora de auditoría.
+ Please note that when {% data variables.product.prodname_actions %} is enabled during this upgrade, two organizations named "GitHub Actions" (@**actions** and @**github**) will appear in {% data variables.product.product_location %}. These organizations are required by {% data variables.product.prodname_actions %}. Users named @**ghost** and @**actions** appear as the actors for creation of these organizations in the audit log.
-
heading: 'GitHub Packages beta'
notes:
diff --git a/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml
new file mode 100644
index 0000000000..1b0a3fcaa6
--- /dev/null
+++ b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml
@@ -0,0 +1,136 @@
+date: '2021-12-06'
+friendlyDate: 'December 6, 2021'
+title: 'December 6, 2021'
+currentWeek: true
+sections:
+ features:
+ - heading: 'Administration'
+ notes:
+ - |
+ Customers with active or trial subscriptions for {% data variables.product.product_name %} can now provision {% data variables.product.product_name %} resources from the [Azure Portal](https://portal.azure.com/signin/index/). Your Azure subscription must be feature-flagged to access {% data variables.product.product_name %} resources in the portal. Contact your account manager or {% data variables.contact.contact_enterprise_sales %} to validate your Azure subscription's eligibility. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_managed %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae#deploying-github-ae-with-the-azure-portal)."
+ - heading: 'GitHub Actions'
+ notes:
+ - |
+ [GitHub Actions](https://github.com/features/actions) is now generally available for {% data variables.product.product_name %}. GitHub Actions is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+ - |
+ Self-hosted runners are the default type of runner system on {% data variables.product.product_name %}, and are now generally available for GitHub Actions. With self-hosted runners, you can manage your own machines or containers for the execution of GitHub Actions jobs. For more information, see "[About self-hosted runners](https://docs.github.com/en/github-ae@latest/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+ - |
+ Environments, environment protection rules, and environment secrets are now generally available for GitHub Actions on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)."
+ - |
+ GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can achieve the following.
+
+ - View and understand complex workflows.
+ - Track progress of workflows in real-time.
+ - Troubleshoot runs quickly by easily accessing logs and jobs metadata.
+ - Monitor progress of deployment jobs and easily access deployment targets.
+
+ For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
+ - |
+ GitHub Actions now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. GitHub Actions generates a new token for each job and expires the token when a job completes. The token has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token) except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."
+ - |
+ GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
+ - |
+ GitHub CLI 1.9 and later allows you to work with GitHub Actions in your terminal. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).
+
+ - heading: 'Code scanning'
+ notes:
+ - |
+ Code scanning is now in beta for {% data variables.product.product_name %}. For more information, see "[About code scanning](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)."
+ - heading: 'Secret scanning'
+ notes:
+ - |
+ You can now specify your own patterns for secret scanning with the beta of custom patterns on {% data variables.product.product_name %}. You can specify patterns for repositories, organizations, and your entire enterprise. When you specify a new pattern, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+ - heading: 'GitHub Connect'
+ notes:
+ - |
+ GitHub Connect is now available in beta for {% data variables.product.product_name %}. GitHub Connect brings the power of the world's largest open source community to {% data variables.product.product_location %}. You can allow users to view search results from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_name %}, show contribution counts from {% data variables.product.product_name %} on {% data variables.product.prodname_dotcom_the_website %}, and use GitHub Actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)."
+ - heading: 'GitHub Packages'
+ notes:
+ - |
+ You can now delete any package or package version for GitHub Packages from {% data variables.product.product_name %}'s web UI or REST API. You can also undo the deletion of any package or package version within 30 days.
+ - |
+ The npm registry for GitHub Packages and {% data variables.product.prodname_dotcom_the_website %} no longer returns a time value in metadata responses, providing substantial performance improvements. {% data variables.product.company_short %} will continue returning the time value in the future.
+ - heading: 'Audit logging'
+ notes:
+ - |
+ Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help administrators better monitor pull request activity and ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events.
+ - |
+ Additional events for GitHub Actions are now included in the audit log for both [enterprises](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization).
+
+ - A workflow is deleted or re-run.
+ - A self-hosted runner's version is updated.
+ - heading: 'Authentication'
+ notes:
+ - |
+ GitHub AE now officially supports Okta for SAML single sign-on (SSO) and user provisioning with SCIM. You can also map groups in Okta to teams on GitHub AE. For more information, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" and "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+ - |
+ The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for OAuth Apps, as well as user-to-server, server-to-server, and refresh tokens for GitHub Apps. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible to improve security and allow secret scanning to detect the tokens. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About secret scanning](/code-security/secret-security/about-secret-scanning)."
+ - |
+ You can now authenticate SSH connections to {% data variables.product.product_name %} using a FIDO2 security key by adding an `sk-ecdsa-sha2-nistp256@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. Storing the key on separate hardware and requiring physical interaction for your SSH key offers additional security. Since the key is stored on hardware and is non-extractable, the key can't be read or stolen by software running on the computer. The physical interaction prevents unauthorized use of the key since the security key will not operate until you physically interact with it. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+ - |
+ Git Credential Manager (GCM) Core versions 2.0.452 and later now provide secure credential storage and multi-factor authentication support for {% data variables.product.product_name %}. GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository.
+ - heading: 'Notifications'
+ notes:
+ - |
+ You can now configure which events you would like to be notified about on {% data variables.product.product_name %}. From any repository, select the {% octicon "file-code" aria-label="The code icon" %} **Watch** drop-down, then click **Custom**. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+ - heading: 'Issues and pull requests'
+ notes:
+ - |
+ With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).
+ - |
+ You can now see all pull request review comments in the **Files** tab for a pull request by selecting the **Conversations** drop-down. You can also require that all pull request review comments are resolved before anyone merges the pull request. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." For more information about management of branch protection settings with the API, see "[Repositories](/rest/reference/repos#get-branch-protection)" in the REST API documentation and "[Mutations](/graphql/reference/mutations#createbranchprotectionrule)" in the GraphQL API documentation.
+ - |
+ You can now upload video files everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, show reproduction steps, and more in issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
+ - |
+ {% data variables.product.product_name %} now shows a confirmation dialog when you request a review from a team with more than 100 members, allowing you to prevent unnecessary notifications for large teams.
+ - |
+ When an issue or pull request has fewer than 30 possible assignees, the assignees control will list all potential users rather than a limited set of suggestions. This behavior helps people in small organizations to quickly find the right user. For more information about assigning users to issues and pull requests, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users#assigning-an-individual-issue-or-pull-request)."
+ - |
+ You can now include multiple words after the `#` in a comment for an issue or pull request to further narrow your search. To dismiss the suggestions, press Esc.
+ - |
+ To prevent the merge of unexpected changes after you enable auto-merge for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, {% data variables.product.product_name %} will disable auto-merge for the pull request if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+ - |
+ People with maintain access can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin access could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)."
+ - |
+ The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name.
+
+ - heading: 'Repositories'
+ notes:
+ - |
+ When viewing the commit history for a file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view the file at the specified time in the repository's history.
+ - |
+ You can now use the web UI to synchronize an out-of-date branch for a fork with the fork's upstream branch. If there are no merge conflicts between the branches, {% data variables.product.product_name %} updates your branch either by fast-forwarding or by merging from upstream. If there are conflicts, {% data variables.product.product_name %} will prompt you to open pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."
+ - |
+ You can now sort the repositories on a user or organization profile by star count.
+ - |
+ The Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another, now supports pagination. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
+ - |
+ When you define a submodule in {% data variables.product.product_location %} with a relative path, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. Relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY are supported. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}.
+ - |
+ By precomputing checksums, the amount of time a repository is under lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
+ - heading: 'Releases'
+ notes:
+ - |
+ You can now react with emoji to all releases on {% data variables.product.product_name %}. For more information, see "[About releases](/github/administering-a-repository/releasing-projects-on-github/about-releases)."
+ - heading: 'Themes'
+ notes:
+ - |
+ Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also customize the themes that are active during day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
+ - heading: 'Markdown'
+ notes:
+ - |
+ Markdown files in your repositories now automatically generate a table of contents in the header the file has two or more headings. The table of contents is interactive and links to the corresponding section. All six Markdown heading levels are supported. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes#auto-generated-table-of-contents-for-readme-files)."
+ - |
+ `code` markup is now supported in titles for issues and pull requests. Text within backticks (`` ` ``) will appear rendered in a fixed-width font anywhere the issue or pull request title appears in the web UI for {% data variables.product.product_name %}.
+ - |
+ While editing Markdown in files, issues, pull requests, or comments, you can now use a keyboard shortcut to insert a code block. The keyboard shortcut is command + E on a Mac or Ctrl + E on other devices. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code)."
+ - |
+ You can append `?plain=1` to the URL for any Markdown file to display the file without rendering and with line numbers. You can use the plain view to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."
+ - heading: 'GitHub Apps'
+ notes:
+ - |
+ API requests to create an installation access token now respect IP allow lists for an enterprise or organization. Any API requests made with an installation access token for a GitHub App installed on your organization already respect IP allow lists. This feature does not currently consider any Azure network security group (NSG) rules that {% data variables.product.company_short %} Support has configured for {% data variables.product.product_location %}. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise#about-ip-allow-lists)," "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)," and "[Apps](https://docs.github.com/en/rest/reference/apps#create-an-installation-access-token-for-an-app)" in the REST API documentation.
+ - heading: 'Webhooks'
+ notes:
+ - |
+ You can now programmatically resend or check the status of webhooks through the REST API. For more information, see "[Repositories](https://docs.github.com/en/rest/reference/repos#webhooks)," "[Organizations](https://docs.github.com/en/rest/reference/orgs#webhooks)," and "[Apps](https://docs.github.com/en/rest/reference/apps#webhooks)" in the REST API documentation.
diff --git a/translations/es-ES/data/reusables/actions/about-secrets.md b/translations/es-ES/data/reusables/actions/about-secrets.md
index c2b646d0ae..6a1f925a0c 100644
--- a/translations/es-ES/data/reusables/actions/about-secrets.md
+++ b/translations/es-ES/data/reusables/actions/about-secrets.md
@@ -1 +1 @@
-Los secretos cifrados te permiten almacenar información sensible, tal como tokens de acceso, en tu repositorio{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, ambientes de repositorio,{% endif %} u organización.
+Los secretos cifrados te permiten almacenar información sensible, tal como tokens de acceso, en tu repositorio{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, ambientes de repositorio,{% endif %} u organización.
diff --git a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md
index a6086c3289..2006e4fe69 100644
--- a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md
+++ b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md
@@ -1,12 +1,12 @@
-| Acción | Descripción |
-| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
-| `cancel_workflow_run` | Se activa cuando se cancela una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Cancelar un flujo de trabajo](/actions/managing-workflow-runs/canceling-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
-| `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
-| `created_workflow_run` | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Crear un flujo de trabajo de ejemplo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
-| `delete_workflow_run` | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)". |
-| `disable_workflow` | Se activa cuando se inhabilita un flujo de trabajo. |
-| `enable_workflow` | Se activa cuando se habilita un flujo de trabajo después de que `disable_workflow` lo inhabilitó previamente. |
-| `rerun_workflow_run` | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
-| `prepared_workflow_job` | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. Para obtener más información, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
-| `approve_workflow_job` | Se activa cuando se aprueba el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". |
-| `reject_workflow_job` | Se activa cuando se rechaza el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)".{% endif %}
+| Acción | Descripción |
+| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `cancel_workflow_run` | Se activa cuando se cancela una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Cancelar un flujo de trabajo](/actions/managing-workflow-runs/canceling-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
+| `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
+| `created_workflow_run` | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Crear un flujo de trabajo de ejemplo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `delete_workflow_run` | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)". |
+| `disable_workflow` | Se activa cuando se inhabilita un flujo de trabajo. |
+| `enable_workflow` | Se activa cuando se habilita un flujo de trabajo después de que `disable_workflow` lo inhabilitó previamente. |
+| `rerun_workflow_run` | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
+| `prepared_workflow_job` | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. Para obtener más información, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `approve_workflow_job` | Se activa cuando se aprueba el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". |
+| `reject_workflow_job` | Se activa cuando se rechaza el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)".{% endif %}
diff --git a/translations/es-ES/data/reusables/actions/ae-beta.md b/translations/es-ES/data/reusables/actions/ae-beta.md
deleted file mode 100644
index 2bb67af1aa..0000000000
--- a/translations/es-ES/data/reusables/actions/ae-beta.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% ifversion ghae-next %}
-
-
-
-{% elsif ghae %}
-
-{% note %}
-
-**Nota:** El {% data variables.product.prodname_actions %} se encuentra actualmente en beta para {% data variables.product.prodname_ghe_managed %}.
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md b/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md
deleted file mode 100644
index 3abe4cf00b..0000000000
--- a/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% ifversion ghae %}
-{% note %}
-
-**Nota:** Los {% data variables.actions.hosted_runner %} se encuentran actualmente en beta y están sujetos a cambios.
-
-{% endnote %}
-{% endif %}
diff --git a/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md
index ee2da8757a..09b656c396 100644
--- a/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md
+++ b/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md
@@ -2,17 +2,7 @@
{% warning %}
-{% ifversion ghae-next %}
-
-**Advertencia:** Los ejecutores auto-hospedados se hablitan predeterminadamente para {% data variables.product.prodname_ghe_managed %}. Los ejecutores auto-hospedados son de larga duración y cualquier riesgo que sufra la máquina hospedadora podría filtrar secretos o credenciales, o habilitar otros ataques. Si te gustaría inhabilitar los ejecutores auto-hospedados en tu empresa, puedes contactar al soporte de {% data variables.product.prodname_dotcom %}. Para obtener más información sobre los riesgos de utilizar ejecutores auto-hospedados, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)".
-
-{% elsif ghae %}
-
-**Advertencia:** Los ejecutores auto-hospedados actualmente están inhabilitados para {% data variables.product.prodname_ghe_managed %}. Esto es porque {% data variables.product.prodname_ghe_managed %} ofrece garantías para los límites de seguridad, las cuales son incompatibles con la forma en que trabajan los ejecutores auto-hospedados. Sin embargo, en caso de que sí necesites utilizar ejecutores auto-hospedados con {% data variables.product.prodname_ghe_managed %} y entender las implicaciones de seguridad, puedes contactar al soporte de {% data variables.product.prodname_dotcom %} para que hagan una exepción de seguridad que los habilitará.
-
-Si no necesitas ejecutores auto-hospedados, entonces puedes utilizar {% data variables.actions.hosted_runner %} para que ejecuten tus flujos de trabajo. Para obtener más información, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)".
-
-{% endif %}
+**Warning:** Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. Para obtener más información sobre los riesgos de utilizar ejecutores auto-hospedados, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)". For more information about the management of access to {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}, see "[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
{% endwarning %}
diff --git a/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md b/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md
index 4cc9f1d2eb..77cf1f0458 100644
--- a/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md
+++ b/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md
@@ -2,7 +2,7 @@
{% note %}
-**Nota:** Las {% data variables.product.prodname_actions %} en {% data variables.product.product_location %} podrían tener acceso limitado a las acciones en {% data variables.product.prodname_dotcom_the_website %} o en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)."
+**Note:** {% data variables.product.prodname_actions %} on {% data variables.product.product_location %} may have limited access to actions on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator.
{% endnote %}
diff --git a/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md
index 9e5c719981..d7fd554d79 100644
--- a/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md
+++ b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md
@@ -1 +1 @@
-Las {% data variables.product.prodname_actions %} utilizan almacenamiento externo para almacenar artefactos de flujo de trabajo y bitácoras. Estos datos se almacenan en tu proveedor de almacenamiento externo, tal como Azure Blob Storage, Amazon S3 o MinIO. Como resultado, los respaldos de {% data variables.product.prodname_ghe_server %} y sus configuraciones de disponibilidad alta no proporcionan protección para los datos que se almacenan en este servicio externo y, en vez de esto, dependen de la protección de datos y replicación que proporciona el proveedor de almacenamiento externo, tal como Azure o AWS.
+{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS.
diff --git a/translations/es-ES/data/reusables/actions/self-hosted-runners-software.md b/translations/es-ES/data/reusables/actions/self-hosted-runners-software.md
new file mode 100644
index 0000000000..03bcfb0728
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/self-hosted-runners-software.md
@@ -0,0 +1 @@
+You must install the required software on your self-hosted runners. For more information about self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
diff --git a/translations/es-ES/data/reusables/advanced-security/license-overview.md b/translations/es-ES/data/reusables/advanced-security/license-overview.md
index 3e5a8c9db2..2812d4cc53 100644
--- a/translations/es-ES/data/reusables/advanced-security/license-overview.md
+++ b/translations/es-ES/data/reusables/advanced-security/license-overview.md
@@ -1 +1,12 @@
-Cada licencia de {% data variables.product.prodname_GH_advanced_security %} especifica una cantidad máxima de cuentas o de plazas que pueden utilizar estas características. Cada confirmante activo en por lo menos un repositorio con la característica habilitada utilizará una plaza. Un confirmante activo es alguien que crea por lo menos una confirmación que se haya subido al repositorio en los últimos 90 días.
+Cada licencia de {% data variables.product.prodname_GH_advanced_security %} especifica una cantidad máxima de cuentas o de plazas que pueden utilizar estas características. Cada confirmante activo en por lo menos un repositorio con la característica habilitada utilizará una plaza. A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored.
+
+{% note %}
+
+**Note:** Active committers are calculated using both the commit author information and the timestamp for when the code was pushed to {% data variables.product.product_name %}.
+
+- When a user pushes code to {% data variables.product.prodname_dotcom %}, every user who authored code in that push counts towards {% data variables.product.prodname_GH_advanced_security %} seats, even if the code is not new to {% data variables.product.prodname_dotcom %}.
+
+- Users should always create branches from a recent base, or rebase them before pushing. This will ensure that users who have not committed in the last 90 days do not take up {% data variables.product.prodname_GH_advanced_security %} seats.
+
+{% endnote %}
+
diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
index e4dd8be529..8669a6386e 100644
--- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
+++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
@@ -4,4 +4,4 @@
1. Proporciona una secuencia de pruebas de muestra para asegurarte de que tu configuración empate con los patrones que esperas.
-1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}.
+1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}.
diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
index 7859cac121..07bf614a03 100644
--- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
+++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
@@ -1 +1 @@
-1. Debajo de "{% data variables.product.prodname_secret_scanning_caps %}", debajo de "Patrones personalizados", haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}**Patrón nuevo**{% elsif ghes = 3.2 %}**Patrón personalizado nuevo**{% endif %}.
+1. Debajo de "{% data variables.product.prodname_secret_scanning_caps %}", debajo de "Patrones personalizados", haz clic en {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Patrón nuevo**{% elsif ghes = 3.2 %}**Patrón personalizado nuevo**{% endif %}.
diff --git a/translations/es-ES/data/reusables/classroom/classroom-admins-link.md b/translations/es-ES/data/reusables/classroom/classroom-admins-link.md
new file mode 100644
index 0000000000..238033da6d
--- /dev/null
+++ b/translations/es-ES/data/reusables/classroom/classroom-admins-link.md
@@ -0,0 +1 @@
+For more information on classroom admins, see "[About management of classrooms](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms#about-management-of-classrooms)."
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md b/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md
index 091f3e931e..8ee0fc92dc 100644
--- a/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md
+++ b/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md
@@ -1 +1 @@
-Puedes ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} dentro de {% data variables.product.product_name %} utilizando {% data variables.product.prodname_actions %}. Como alternativa, si utilizas un sistema de integración o despliegue/entrega contínua (IC/ID) de terceros, puedes ejecutar un análisis de {% data variables.product.prodname_codeql %} en tu sistema existente y cargar los resultados a {% data variables.product.product_location %}.
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using {% data variables.product.prodname_actions %}. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}.
diff --git a/translations/es-ES/data/reusables/code-scanning/edit-workflow.md b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md
index 16b6594082..98bd06f5cb 100644
--- a/translations/es-ES/data/reusables/code-scanning/edit-workflow.md
+++ b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md
@@ -1 +1 @@
-Habitualmente, no necesitas editar el flujo de trabajo predeterminado para {% data variables.product.prodname_code_scanning %}. Sin embargo, si lo requieres, puedes editar el flujo de trabajo para personalizar algunos de los ajustes. Por ejemplo, puedes editar el {% data variables.product.prodname_codeql_workflow %} de {% data variables.product.prodname_dotcom %} para especificar la frecuencia de los escaneos, los idiomas o los directorios a escanear, y qué debe buscar el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} en tu código. También podrías necesitar editar el {% data variables.product.prodname_codeql_workflow %} si utilizas un conjunto de comandos específicos para compilar tu código.
+Typically, you don't need to edit the default workflow for {% data variables.product.prodname_code_scanning %}. However, if required, you can edit the workflow to customize some of the settings. For example, you can edit {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql_workflow %} to specify the frequency of scans, the languages or directories to scan, and what {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} looks for in your code. You might also need to edit the {% data variables.product.prodname_codeql_workflow %} if you use a specific set of commands to compile your code.
diff --git a/translations/es-ES/data/reusables/code-scanning/enabling-options.md b/translations/es-ES/data/reusables/code-scanning/enabling-options.md
index 9fee080bae..ad4eded9d1 100644
--- a/translations/es-ES/data/reusables/code-scanning/enabling-options.md
+++ b/translations/es-ES/data/reusables/code-scanning/enabling-options.md
@@ -1,28 +1,8 @@
-
-
- |
- Tipo de análisis
- |
-
-
- Opciones para generar alertas
- |
-
-
-
- |
- |
-
-
- |
-
-
-{%- ifversion fpt or ghes > 3.0 or ghae-next %}
-|
-{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)").
+| Type of analysis | Options for generating alerts |
+|------------------|-------------------------------|
+{%- ifversion fpt or ghes > 3.0 or ghae %}
+| {% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)").
{%- else %}
-|
-{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)").
+| {% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)").
{%- endif %}
-| Terceros | Utilizando
-{% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)").|
+| Third‑party | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)").|
diff --git a/translations/es-ES/data/reusables/code-scanning/licensing-note.md b/translations/es-ES/data/reusables/code-scanning/licensing-note.md
index 4be164fb79..22e63b326f 100644
--- a/translations/es-ES/data/reusables/code-scanning/licensing-note.md
+++ b/translations/es-ES/data/reusables/code-scanning/licensing-note.md
@@ -1,7 +1,7 @@
{% note %}
-**Nota:** {% ifversion fpt or ghec %}
-El {% data variables.product.prodname_codeql_cli %} se puede usar gratuitamente en los repositorios públicos que se mantienen en {% data variables.product.prodname_dotcom_the_website %} y está disponible para utilizarse en los repositorios privados que pertenezcan a los clientes con una licencia de la {% data variables.product.prodname_advanced_security %}. Para obtener información, consulta la sección "[Términos y condiciones del {% data variables.product.prodname_codeql %} de {% data variables.product.product_name %}](https://securitylab.github.com/tools/codeql/license)" y [CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
-{%- else %}El {% data variables.product.prodname_codeql_cli %} se encuentra disponible para los clientes con una licencia de la {% data variables.product.prodname_advanced_security %}.
+**Note:** {% ifversion fpt or ghec %}
+The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
{% endif %}
{% endnote %}
diff --git a/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md
index 5b4083e896..e74bb3a820 100644
--- a/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md
+++ b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md
@@ -1,20 +1,18 @@
-Cuando utilizas {% data variables.product.prodname_codeql %} para escanear código, el motor de análisis de {% data variables.product.prodname_codeql %} genera una base de datos desde el código y ejecuta consultas en éste. El {% data variables.product.prodname_codeql %} utiliza un conjunto predeterminado de consultas, pero puedes especificar más consultas para que se ejecuten, adicionalmente a las predeterminadas.
+When you use {% data variables.product.prodname_codeql %} to scan code, the {% data variables.product.prodname_codeql %} analysis engine generates a database from the code and runs queries on it. {% data variables.product.prodname_codeql %} analysis uses a default set of queries, but you can specify more queries to run, in addition to the default queries.
{% if codeql-packs %}
-Puedes ejecutar consultas adicionales si son parte de un
-paquete de {% data variables.product.prodname_codeql %} (beta) publicado en el {% data variables.product.prodname_container_registry %} de {% data variables.product.company_short %} o de un paquete de {% data variables.product.prodname_ql %} en un repositorio. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)".
+You can run extra queries if they are part of a {% data variables.product.prodname_codeql %} pack (beta) published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} or a {% data variables.product.prodname_ql %} pack stored in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
-Las opciones disponibles para especificar las consultas adicionales que quieres ejecutar son:
+The options available to specify the additional queries you want to run are:
-- `packs` para instalar uno o más paquetes de consulta de {% data variables.product.prodname_codeql %} (beta) y ejecutar la suite de consultas predeterminada para estos paquetes.
-- `queries` para especificar un archivo sencilo de _.ql_, un directorio que contenga varios archivos de _.ql_, un archivo de definición de suite de consultas _.qls_ o cualquier combinación de estos. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)".
+- `packs` to install one or more {% data variables.product.prodname_codeql %} query packs (beta) and run the default query suite or queries for those packs.
+- `queries` to specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)."
-Puedes utilizar tanto `packs` como `queries` en el mismo flujo de trabajo.
+You can use both `packs` and `queries` in the same workflow.
{% else %}
-Cualquier consulta adicional que quieras ejecutar debe pertenecer a un
-paquete de {% data variables.product.prodname_ql %} en un repositorio. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)".
+Any additional queries you want to run must belong to a {% data variables.product.prodname_ql %} pack in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
-Puedes especificar un solo archivo _.ql_, un directorio que contenga varios archivos _.ql_, un archivo de definición de suite de consulta _.qls_, o cualquier combinación de éstos. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)".
+You can specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)."
{% endif %}
-{% ifversion fpt or ghec %}No te recomendamos referenciar las suites de consultas directamente desde el repositorio de `github/codeql`, como por ejemplo `github/codeql/cpp/ql/src@main`. Puede que dichas consultas no se compilen con la misma versión de {% data variables.product.prodname_codeql %} que se utiliza para tus otras consultas, lo cual puede llevar a que se cometan errores durante el análisis.{% endif %}
+{% ifversion fpt or ghec %}We don't recommend referencing query suites directly from the `github/codeql` repository, like `github/codeql/cpp/ql/src@main`. Such queries may not be compiled with the same version of {% data variables.product.prodname_codeql %} as used for your other queries, which could lead to errors during analysis.{% endif %}
diff --git a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md
index a65b4e97ab..7b5e1aabf8 100644
--- a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,7 +1,7 @@
{% note %}
**Notas:**
-- La carga de SARIF es compatible con un máximo de {% ifversion ghae-next or fpt or ghes > 3.0 or ghec %}5000{% else %}1000{% endif %} resultados por carga. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes.
+- La carga de SARIF es compatible con un máximo de {% ifversion ghae or fpt or ghes > 3.0 or ghec %}5000{% else %}1000{% endif %} resultados por carga. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes.
- Para cada carga, la carga de SARIF es compatible con un tamaño máximo de 10 MB para el archivo comprimido de `gzip`. Cualquier carga que esté sobre este límite, se rechazará. Si tu archivo SARIF es demasiado grande porque contiene demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes.
diff --git a/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md b/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md
index 74f1e7755b..aaf643f0db 100644
--- a/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md
+++ b/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
Si no es adecuado que utilices el {% data variables.product.prodname_codeql_cli %} para tu sistema de IC, como alternativa, está disponible el {% data variables.product.prodname_codeql_runner %}. Típicamente, esto se necesita si el sistema de IC necesitaría orquestrar invocaciones del compilador así como ejecutar un análisis de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)".
{% endif %}
diff --git a/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md
index 139214e8f0..d1c977333f 100644
--- a/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md
+++ b/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -1,3 +1,3 @@
-{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
El {% data variables.product.prodname_codeql_cli %} es un producto independiente que puedes utilizar para analizar código. Su propósito principal es generar una representación de base de datos de una base de código, una base de datos de {% data variables.product.prodname_codeql %}. Una vez que esté lista la base de datos, puedes consultarla interactivamente o ejecutar una suite de consultas para generar un conjunto de resultados en formato SARIF y cargarlos a {% data variables.product.product_location %}.
{% endif %}
diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-tos.md b/translations/es-ES/data/reusables/dependabot/dependabot-tos.md
index a358938079..c22b0988af 100644
--- a/translations/es-ES/data/reusables/dependabot/dependabot-tos.md
+++ b/translations/es-ES/data/reusables/dependabot/dependabot-tos.md
@@ -1,5 +1,5 @@
{% ifversion fpt %}
-En las [Condiciones de Servicio de {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/github/site-policy/github-terms-of-service) se incluyen al {% data variables.product.prodname_dependabot %} y a todas sus características relacionadas.
+{% data variables.product.prodname_dependabot %} and all related features are covered by [{% data variables.product.prodname_dotcom %}'s Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service).
{% elsif ghec %}
-Tu acuerdo de licencia cubre al {% data variables.product.prodname_dependabot %} y a todas las características relacionadas. Para obtener más información, consulta la sección "[Términos para clientes de {% data variables.product.company_short %} Enterprise](https://github.com/enterprise-legal)".
+{% data variables.product.prodname_dependabot %} and all related features are covered by your license agreement. For more information, see "[{% data variables.product.company_short %} Enterprise Customer Terms](https://github.com/enterprise-legal)."
{% endif %}
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md
index 36e8e9c64a..8d633a04a6 100644
--- a/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md
+++ b/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md
@@ -1 +1 @@
-1. Haz clic en la pestaña de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}**Ejecutores**{% else %}**Ejecutores auto-hospedados**{% endif %}.
+1. Haz clic en la pestaña de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}**Ejecutores**{% else %}**Ejecutores auto-hospedados**{% endif %}.
diff --git a/translations/es-ES/data/reusables/enterprise/navigate-to-log-streaming-tab.md b/translations/es-ES/data/reusables/enterprise/navigate-to-log-streaming-tab.md
new file mode 100644
index 0000000000..b4d6f85f4e
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise/navigate-to-log-streaming-tab.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+1. Haz clic en la pestaña de **Transmisión de bitácoras**.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md b/translations/es-ES/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
new file mode 100644
index 0000000000..37b1ab5120
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
@@ -0,0 +1 @@
+1. Verify the endpoint, then click **Save**.
diff --git a/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md b/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md
index 51c91b94b1..c06f308925 100644
--- a/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md
+++ b/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md
@@ -1 +1 @@
-1. Haz clic en **Get the latest release of {% data variables.product.prodname_ghe_server %}** (Obtener el último lanzamiento del {% data variables.product.prodname_ghe_server %}).
+1. Click **Get the latest release of {% data variables.product.prodname_ghe_server %}**.
diff --git a/translations/es-ES/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md b/translations/es-ES/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md
new file mode 100644
index 0000000000..690abb634f
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** {% data variables.product.prodname_ghe_server %} supports PROXY Protocol V1, which is incompatible with AWS Network Load Balancers. If you use AWS Network Load Balancers with {% data variables.product.prodname_ghe_server %}, do not enable PROXY support.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md b/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md
index 7ea6837515..0c74592a2b 100644
--- a/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md
+++ b/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md
@@ -1 +1 @@
-Un equipo que se encuentra [sincronizado a un grupo LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) se indica con una insignia de LDAP especial. La lista de miembros para un equipo de LDAP sincronizado únicamente se puede administrar desde el grupo LDAP al que está mapeado.
+A team that's [synced to an LDAP group](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) is indicated with a special LDAP badge. The member list for an LDAP synced team can only be managed from the LDAP group it's mapped to.
diff --git a/translations/es-ES/data/reusables/form-schema/options-syntax.md b/translations/es-ES/data/reusables/form-schema/options-syntax.md
index e87310212b..0837b76ba1 100644
--- a/translations/es-ES/data/reusables/form-schema/options-syntax.md
+++ b/translations/es-ES/data/reusables/form-schema/options-syntax.md
@@ -1,5 +1,5 @@
Para cada valor en el arreglo de `options`, puedes configurar las siguientes claves.
-| Clave | Descripción | Requerido | Type | Predeterminado | Opciones |
+| Clave | Descripción | Requerido | Tipo | Predeterminado | Opciones |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- |
| `etiqueta` | El identificador para la opción, el cual se muestra en el formato. Hay compatibilidad con lenguaje de marcado para formateo de texto en itálicas o negritas y para los hipervínculos. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
diff --git a/translations/es-ES/data/reusables/gated-features/ghas.md b/translations/es-ES/data/reusables/gated-features/ghas.md
index 0f74920694..060b70911a 100644
--- a/translations/es-ES/data/reusables/gated-features/ghas.md
+++ b/translations/es-ES/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 3.0 or higher.{% ifversion fpt or ghec %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %}
+La {% data variables.product.prodname_GH_advanced_security %} se encuentra disponible para las cuentas empresariales en {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %} 3.0 o superior.{% ifversion fpt or ghec %} La {% data variables.product.prodname_GH_advanced_security %} también se incluye en todos los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Acerca de los productos de GitHub](/github/getting-started-with-github/githubs-products)".{% else %} Para obtener más información sobre cómo mejorar tu instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" y refiérete al [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar la ruta de mejora desde tu versión de lanzamiento actual.{% endif %}
diff --git a/translations/es-ES/data/reusables/gated-features/packages.md b/translations/es-ES/data/reusables/gated-features/packages.md
index 797b9cc52e..be454eea75 100644
--- a/translations/es-ES/data/reusables/gated-features/packages.md
+++ b/translations/es-ES/data/reusables/gated-features/packages.md
@@ -1,4 +1,4 @@
-{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 3.0 or higher, and {% data variables.product.prodname_ghe_managed %}.{% ifversion ghes %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %}
+El {% data variables.product.prodname_registry %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 3.0 o superior y {% data variables.product.prodname_ghe_managed %}.{% ifversion ghes %} Para obtener más información sobre cómo mejorar tu instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" y refiérete al [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar la ruta de mejora desde tu versión de lanzamiento actual.{% endif %}
{% ifversion fpt or ghec %}
{% data variables.product.prodname_registry %} no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. Las cuentas que utilicen los planes tradicionales por repositorio tampoco podrán acceder al {% data variables.product.prodname_container_registry %} ya que estas cuentas se facturan por repositorio. {% data reusables.gated-features.more-info %}
diff --git a/translations/es-ES/data/reusables/gated-features/secret-scanning.md b/translations/es-ES/data/reusables/gated-features/secret-scanning.md
index 3a91933dfb..f910931949 100644
--- a/translations/es-ES/data/reusables/gated-features/secret-scanning.md
+++ b/translations/es-ES/data/reusables/gated-features/secret-scanning.md
@@ -1,5 +1,5 @@
{% ifversion fpt or ghec %}El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible para todos los repositorios públicos y para los privados que pertenecen a organizaciones en donde se habilitó la {% data variables.product.prodname_GH_advanced_security %}.
-{%- elsif ghes > 3.0 or ghae-next %}Las {% data variables.product.prodname_secret_scanning_caps %} están disponibles para los repositorios que pertenezcan a organizaciones en donde esté habilitada la {% data variables.product.prodname_GH_advanced_security %}.
+{%- elsif ghes > 3.0 or ghae %}Las {% data variables.product.prodname_secret_scanning_caps %} están disponibles para los repositorios que pertenezcan a organizaciones en donde esté habilitada la {% data variables.product.prodname_GH_advanced_security %}.
{%- elsif ghae %}
El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible como parte de la {% data variables.product.prodname_GH_advanced_security %}, la cual es gratuita durante el lanzamiento beta.
{%- else %}
diff --git a/translations/es-ES/data/reusables/getting-started/marketplace.md b/translations/es-ES/data/reusables/getting-started/marketplace.md
index 5283cdf6a7..31b86d2397 100644
--- a/translations/es-ES/data/reusables/getting-started/marketplace.md
+++ b/translations/es-ES/data/reusables/getting-started/marketplace.md
@@ -1 +1 @@
-{% data variables.product.prodname_marketplace %} contiene integraciones que agregan funcionalidad y mejoran tu flujo de trabajo. En [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), puedes descubrir, buscar e instalar herramientas gratuitas y de pago, incluyendo {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, y {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace)".
+{% data variables.product.prodname_marketplace %} contains integrations that add functionality and improve your workflow. You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). For more information, see "[About {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace)."
diff --git a/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md
index 320cd7d9fd..816927b973 100644
--- a/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md
+++ b/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md
@@ -1 +1 @@
-Predeterminadamente, {% data variables.product.product_name %} almacena bitácoras de compilación y artefactos durante 90 días y este periodo de retención puede personalizarse. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)".
+By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and this retention period can be customized.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/contacting-support.md b/translations/es-ES/data/reusables/github-actions/contacting-support.md
index 9ba6a3389e..d4bcb7c776 100644
--- a/translations/es-ES/data/reusables/github-actions/contacting-support.md
+++ b/translations/es-ES/data/reusables/github-actions/contacting-support.md
@@ -1,9 +1,9 @@
-Si necesitas ayuda con lo que sea relacionado con la configuración de flujo de trabajo, tal como la sintaxis, los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, o la creación de acciones, busca un tema existente o inicia uno nuevo en la [categoría de {% data variables.product.prodname_actions %} de {% data variables.product.prodname_gcf %}](https://github.community/c/code-to-cloud/github-actions/41).
+If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41).
-Si tienes algún tipo de retroalimentación o solicitudes de características para {% data variables.product.prodname_actions %}, compártelas en el {% data variables.contact.contact_feedback_actions %}.
+If you have feedback or feature requests for {% data variables.product.prodname_actions %}, share those in the {% data variables.contact.contact_feedback_actions %}.
-Contacta a {% data variables.contact.contact_support %} para cualquiera de los siguientes, que tu tipo de uso o el tipo de uso que pretendes tener caiga en las siguientes categorías de limitación:
+Contact {% data variables.contact.contact_support %} for any of the following, whether your use or intended use falls into the usage limit categories:
-* Si crees que tu cuenta se ha restringido de manera incorrecta
-* Si llegas un error inesperado cuando ejecutas una de tus acciones, por ejemplo: una ID única
-* Si llegas a una situación en donde el comportamiento existente contradice a aquél que se espera, pero no siempre se documenta
+* If you believe your account has been incorrectly restricted
+* If you encounter an unexpected error when executing one of your Actions, for example: a unique ID
+* If you encounter a situation where existing behavior contradicts expected, but not always documented, behavior
diff --git a/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md b/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md
index 3f5092e9ca..c5e42afc4f 100644
--- a/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md
+++ b/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md
@@ -1 +1 @@
-When you enable {% data variables.product.prodname_actions %}, workflows are able to run actions located within your repository and any other{% ifversion fpt %} public{% elsif ghec or ghes %} public or internal{% elsif ghae %} internal{% endif %} repository.
+Cuando habilitas las {% data variables.product.prodname_actions %}, los flujos de trabajo pueden ejecutar acciones que se ubiquen dentro de tu repositorio y en cualquier otro repositorio{% ifversion fpt %} público{% elsif ghec or ghes %} público o interno{% elsif ghae %} interno{% endif %}.
diff --git a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
index 101a1a3d0e..8c23fd1fdb 100644
--- a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
@@ -10,6 +10,7 @@ permissions:
issues: read|write|none
discussions: read|write|none
packages: read|write|none
+ pages: read|write|none
pull-requests: read|write|none
repository-projects: read|write|none
security-events: read|write|none
diff --git a/translations/es-ES/data/reusables/github-actions/github-token-permissions.md b/translations/es-ES/data/reusables/github-actions/github-token-permissions.md
index 5ffe1cbb78..a65beaf53a 100644
--- a/translations/es-ES/data/reusables/github-actions/github-token-permissions.md
+++ b/translations/es-ES/data/reusables/github-actions/github-token-permissions.md
@@ -1 +1 @@
-El secreto de `GITHUB_TOKEN` se configuro para un token de acceso para el repositorio cada vez que comienza un job en un flujo de trabajo. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}Debes configurar los permisos para este token de acceso en el archivo del flujo de trabajo para otorgar acceso de lectura para el alcance `contents` y acceso de escritura para el de `packages`. {% else %}Tiene permisos de lectura y escritura para los paquetes del repositorio en donde se ejecuta el flujo de trabajo. {% endif %}Para obtener más información, consulta la sección "[Autenticarte con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+El secreto de `GITHUB_TOKEN` se configuro para un token de acceso para el repositorio cada vez que comienza un job en un flujo de trabajo. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Debes configurar los permisos para este token de acceso en el archivo del flujo de trabajo para otorgar acceso de lectura para el alcance `contents` y acceso de escritura para el de `packages`. {% else %}Tiene permisos de lectura y escritura para los paquetes del repositorio en donde se ejecuta el flujo de trabajo. {% endif %}Para obtener más información, consulta la sección "[Autenticarte con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
diff --git a/translations/es-ES/data/reusables/github-actions/hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/hosted-runner-navigate-to-repo-org-enterprise.md
deleted file mode 100644
index c52cf043db..0000000000
--- a/translations/es-ES/data/reusables/github-actions/hosted-runner-navigate-to-repo-org-enterprise.md
+++ /dev/null
@@ -1,15 +0,0 @@
-1. Navega a donde está registrado tu {% data variables.actions.hosted_runner %}:
- * **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**.
- * **Si utilizas un ejecutor a nivel de empresa**:
-
- 1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}.
- 1. En la barra lateral izquierda, da clic en **Resumen empresarial**.
- 1. En la barra lateral de la cuenta de empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Policies** (Políticas).
-1. Navega a los ajustes de {% data variables.product.prodname_actions %}:
- * **En un repositorio de organización**: Haz clic en **Acciones** en la barra lateral izquierda.
-
- 
- * **Si utilizas un ejecutor a nivel de empresa**: Debajo de "Políticas {% octicon "law" aria-label="The law icon" %}", haz clic en **Acciones**.
-
- 
-
diff --git a/translations/es-ES/data/reusables/github-actions/ip-allow-list-hosted-runners.md b/translations/es-ES/data/reusables/github-actions/ip-allow-list-hosted-runners.md
deleted file mode 100644
index 48f22d58a8..0000000000
--- a/translations/es-ES/data/reusables/github-actions/ip-allow-list-hosted-runners.md
+++ /dev/null
@@ -1,3 +0,0 @@
-Para permitir que tus {% data variables.actions.hosted_runner %} se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus {% data variables.actions.hosted_runner %} a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)".
-
-Para obtener más información sobre los {% data variables.actions.hosted_runner %}, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/github-ae@latest/actions/using-github-hosted-runners/about-ae-hosted-runners)".
diff --git a/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
index 753300c299..ed15a5ea59 100644
--- a/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
+++ b/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
@@ -1,6 +1,6 @@
{% ifversion ghae %}
-Para permitir que tus
-{% data variables.actions.hosted_runner %} se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus {% data variables.actions.hosted_runner %} a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)".
+Para permitir que tus ejecutores auto-hospedados se comuniquen con
+{% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)".
{% else %}
{% warning %}
diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md
index 4ccf0b2a66..a3630e59cb 100644
--- a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md
+++ b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md
@@ -1,4 +1,4 @@
-Si dependes en el uso de bifurcaciones de tus repositorios privados, puedes configurar las políticas que controlan cómo los usuarios pueden ejecutar flujos de trabajo en los eventos de `pull_request`. Available to private {% ifversion ghec or ghes or ghae %}and internal{% endif %} repositories only, you can configure these policy settings for {% ifversion ghec %}enterprises, {% elsif ghes or ghae %}your enterprise, {% endif %}organizations, or repositories.{% ifversion ghec or ghes or ghae %} For enterprises, the policies are applied to all repositories in all organizations.{% endif %}
+Si dependes en el uso de bifurcaciones de tus repositorios privados, puedes configurar las políticas que controlan cómo los usuarios pueden ejecutar flujos de trabajo en los eventos de `pull_request`. Disponible únicamente para los repositorios privados {% ifversion ghec or ghes or ghae %}e internos{% endif %}, puedes configurar estos ajustes de política para {% ifversion ghec %}empresas, {% elsif ghes or ghae %}tu empresa, {% endif %}organizaciones, o repositorios.{% ifversion ghec or ghes or ghae %}Para empresas, las políticas se aplcan a todos los repositorios en todas las organizaciones.{% endif %}
- **Ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones** - permite a los usuarios ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones utilizando un `GITHUB_TOKEN` con permisos de solo lectura y sin acceso a los secretos.
- **Enviar tokens de escritura a los flujos de trabajo desde las solicitudes de extracción** - Permite a las solicitudes de extracción de las bifuraciones utilizar un `GITHUB_TOKEN` con permiso de escritura.
diff --git a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md
index 83faa1f3f9..c5cc918fbe 100644
--- a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}La clave de `permissions` especifica el acceso otorgado al `GITHUB_TOKEN`.{% endif %}
+Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso otorgado al `GITHUB_TOKEN`.{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index d2d8dbe1ee..78fd73c235 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -1,4 +1,4 @@
-1. En la sección de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"ejecutores"{% else %}"ejecutores auto-hospedados"{% endif %} de la página de ajustes, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecutores que te gustaría configurar y luego en **Editar el nombre y acceso a la [organización|repositorio]**. 
+1. En la sección de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"ejecutores"{% else %}"ejecutores auto-hospedados"{% endif %} de la página de ajustes, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecutores que te gustaría configurar y luego en **Editar el nombre y acceso a la [organización|repositorio]**. 
1. Modifica tus opciones de política o cambia el nombre del grupo ejecutor.
{% ifversion not ghae %}
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
index 2a714dd952..085ae92c05 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
@@ -6,7 +6,7 @@
{% elsif ghec or ghes or ghae %}
1. Navega a donde se ubiquen tus grupos de ejecutores auto-hospedados:
* **In an organization**: navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.{% ifversion ghec %}
- * **If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif ghes or ghae %}
+ * **If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}
* **Si utilizas un ejecutor a nivel de empresa**:
1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}.
2. En la barra lateral izquierda, da clic en **Resumen empresarial**.
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md
index d948b07bb5..24de0e04b3 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md
@@ -1,5 +1,5 @@
Para especificar un ejecutor auto-hospedado para tu trabajo, configura `runs-on` en tu archivo de flujo de trabajo con las etiquetas de dicho ejecutor.
-Todos los ejecutores auto-hospedados tienen la etiqueta `self-hosted`. El utilizar únicamente esta etiqueta seleccionará cualquier ejecutor auto-hospedado. To select runners that meet certain criteria, such as operating system or architecture, we recommend providing an array of labels that begins with `self-hosted` (this must be listed first) and then includes additional labels as needed. When you specify an array of labels, jobs will be queued on runners that have all the labels that you specify.
+Todos los ejecutores auto-hospedados tienen la etiqueta `self-hosted`. El utilizar únicamente esta etiqueta seleccionará cualquier ejecutor auto-hospedado. Para seleccionar los ejecutores que cumplen con ciertos criterios, tales como el sistema operativo o arquitectura, te recomendamos proporcionar un arreglo de etiquetas que comience con `self-hosted` (este se debe listar primero) y que luego incluya etiquetas adicionales conforme lo requieras. Cuando especifiques un arreglo de etiquetas, los jobs se pondrán en cola cuando se trate de ejecutores que tengan todas las etiquetas que especificas.
-Although the `self-hosted` label is not required, we strongly recommend specifying it when using self-hosted runners to ensure that your job does not unintentionally specify any current or future {% data variables.product.prodname_dotcom %}-hosted runners.
+Aunque la etiqueta de `self-hosted` no se requiere, te recomendamos ampliamente especificarla cuando utilices ejecutores auto-hospedados para garantizar que tu trabajo no especifique algún ejecutor hospedado en {% data variables.product.prodname_dotcom %} futuro o actual por accidente.
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md
index 7372ea0240..fbf869e5fd 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md
@@ -1 +1 @@
- 1. Ubica la lista de ejecutores debajo de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}.
+ 1. Ubica la lista de ejecutores debajo de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}.
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
index d8348476c5..65ded479f7 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
@@ -6,12 +6,12 @@
{% elsif ghec or ghes or ghae %}
1. Navega a donde está registrado tu ejecutor auto-hospedado:
* **En una organización**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**.
- * {% ifversion ghec %}**Si se utiliza una cuenta empresarial**: navega a tu cuenta visitando `https://github.com/enterprises/ENTERPRISE-NAME`, remplazando la parte de `ENTERPRISE-NAME` con tu nombre de cuenta empresarial.{% elsif ghes or ghae %}**Si utilizas un ejecutor a nivel empresarial**:
+ * {% ifversion ghec %}**If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}**If using an enterprise-level runner**:
1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}.
1. En la barra lateral izquierda, da clic en **Resumen empresarial**.
1. In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %}
1. Navega a los ajustes de {% data variables.product.prodname_actions %}:
- * **En una organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %} y luego en **Ejecutores**{% endif %}.
- * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}, y luego en la pestaña de **Ejecutores** {% endif %}.
+ * **En una organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghec or ghes > 3.1 or ghae %} y luego en **Ejecutores**{% endif %}.
+ * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt or ghec or ghes > 3.1 or ghae %}, y luego en la pestaña de **Ejecutores** {% endif %}.
{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
index 35412e38f8..c8f28605ee 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
@@ -6,12 +6,12 @@
{% elsif ghec or ghes or ghae %}
1. Navega a donde está registrado tu ejecutor auto-hospedado:
* **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. {% ifversion ghec %}
- * **If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif ghes or ghae %}
+ * **If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}
* **Si utilizas un ejecutor a nivel de empresa**:
1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}.
2. En la barra lateral izquierda, da clic en **Resumen empresarial**.
3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %}
2. Navega a los ajustes de {% data variables.product.prodname_actions %}:
- * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, then click **Runners**{% endif %}.{% ifversion ghec or ghae or ghes %}
- * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghes > 3.1 or ghae-next or ghec %}, then click the **Runners** tab{% endif %}.{% endif %}
+ * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, then click **Runners**{% endif %}.{% ifversion ghec or ghae or ghes %}
+ * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghes > 3.1 or ghae or ghec %}, then click the **Runners** tab{% endif %}.{% endif %}
{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md
index fe7dc99744..794a26ad6b 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md
@@ -1,4 +1,4 @@
-1. Debajo de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista.
+1. Debajo de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista.
1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al ejecutor que quieres eliminar, y luego da clic en **Eliminar**.
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md
index 54a6af6358..8591d0ffe6 100644
--- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md
+++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md
@@ -1,2 +1,2 @@
-1. En la barra lateral izquierda, haz clic en **Acciones**.{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+1. En la barra lateral izquierda, haz clic en **Acciones**.{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
1. En la barra lateral izquierda, debajo de "Acciones"; haz clic en **Grupos ejecutores**.{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md
index dcc2e80609..4abb0ab1cf 100644
--- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md
+++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md
@@ -1 +1 @@
-1. En la barra lateral izquierda, haz clic en **Acciones**{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} y luego haz clic en **Ejecutores**{% endif %}.
+1. En la barra lateral izquierda, haz clic en **Acciones**{% ifversion fpt or ghes > 3.1 or ghae or ghec %} y luego haz clic en **Ejecutores**{% endif %}.
diff --git a/translations/es-ES/data/reusables/github-ae/saml-idp-table.md b/translations/es-ES/data/reusables/github-ae/saml-idp-table.md
new file mode 100644
index 0000000000..db04f96ef7
--- /dev/null
+++ b/translations/es-ES/data/reusables/github-ae/saml-idp-table.md
@@ -0,0 +1,4 @@
+| IdP | SAML | Aprovisionamiento de usuarios | Team mapping |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| [Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label= "The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/github-connect/beta.md b/translations/es-ES/data/reusables/github-connect/beta.md
index 38de9506c0..7abe1798db 100644
--- a/translations/es-ES/data/reusables/github-connect/beta.md
+++ b/translations/es-ES/data/reusables/github-connect/beta.md
@@ -1,4 +1,4 @@
-{% ifversion ghae-next %}
+{% ifversion ghae %}
{% note %}
**Nota:** {% data variables.product.prodname_github_connect %} para {% data variables.product.product_name %} se encuentra actualmente en beta y está sujeto a cambios.
diff --git a/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md
index 18a044ccbb..4dd41c844b 100644
--- a/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md
+++ b/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md
@@ -1 +1,2 @@
-1. Debajo de "Contributions" (Contribuciones), selecciona **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}** (Enviar mi recuento de contribuciones a {% data variables.product.prodname_dotcom_the_website %}), luego haz clic en **Update contributions** (Actualizar contribuciones). 
+1. Under "Contributions", select **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}**, then click **Update contributions.**
+ 
diff --git a/translations/es-ES/data/reusables/github-connect/sync-frequency.md b/translations/es-ES/data/reusables/github-connect/sync-frequency.md
index 0057d0fdb2..0905f58853 100644
--- a/translations/es-ES/data/reusables/github-connect/sync-frequency.md
+++ b/translations/es-ES/data/reusables/github-connect/sync-frequency.md
@@ -1 +1 @@
-{% data variables.product.product_name %} envía actualizaciones cada hora.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% elsif ghes or ghae %}{% data variables.product.product_name %}{% endif %} sends updates hourly.
diff --git a/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md b/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md
index 18a4258c7a..2b6cb58ca4 100644
--- a/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md
+++ b/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md
@@ -1,4 +1,4 @@
-| Nombre | Type | Descripción |
+| Nombre | Tipo | Descripción |
| ------------------------ | ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
| `id` | `número` | El identificador único del evento. |
| `node_id` | `secuencia` | La [ID de Nodo Global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) del evento. |
diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md
index db56805fb3..da5e9656ae 100644
--- a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md
+++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md
@@ -5,7 +5,7 @@
- en la interface de usuario, se muestra una advertencia en tu archivo de repositorio y vistas de código si hay dependencias vulnerables (opción de **Alertas de la IU**).
- en la línea de comandos, las advertencias se muestran como rellamados cuando subes información a los repositorios con dependencias vulnerables (opción de **Línea de comandos**).
- en tu bandeja de entrada, como notificaciones web. Se enviará una notificación web cuando se habilite el {% data variables.product.prodname_dependabot %} en un repositorio cada que se confirme un archivo de manifiesto nuevo en dicho repositorio y cuando se encuentre una vulnerabilidad nueva con severidad crítica o alta (opción **Web**).{% ifversion not ghae %}
-- en {% data variables.product.prodname_mobile %}, como notificaciones web. Para obtener más información, consulta la sección [Habilitar las notificaciones de subida con GitHub para dispositivos móviles](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)".{% endif %}
+- en {% data variables.product.prodname_mobile %}, como notificaciones web. For more information, see "[Enabling push notifications with GitHub Mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."{% endif %}
{% note %}
diff --git a/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md b/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md
index 2921877ac6..e6a87294c4 100644
--- a/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md
+++ b/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md
@@ -1,5 +1,5 @@
{% note %}
-**Nota:** Cuando eliminas un usuario de la organización, sus datos de membresía se guardan durante tres meses. Si en el transcurso de ese tiempo invitas al usuario a que se vuelva a unir a la organización, puedes restaurar sus datos o cualquier bifurcación privada de tus repositorios de la organización que le haya pertenecido. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ page.version }}/user/articles/reinstating-a-former-member-of-your-organization)".
+**Note:** When you remove a user from your organization, their membership data is saved for three months. You can restore their data, or any private forks they owned of your organization's repositories, if you invite the user to rejoin the organization within that time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
{% endnote %}
diff --git a/translations/es-ES/data/reusables/organizations/organizations_include.md b/translations/es-ES/data/reusables/organizations/organizations_include.md
index 728f14f7d4..a2fd3eb92b 100644
--- a/translations/es-ES/data/reusables/organizations/organizations_include.md
+++ b/translations/es-ES/data/reusables/organizations/organizations_include.md
@@ -3,7 +3,8 @@ Las organizaciones incluyen:
- La capacidad de otorgarles a los miembros [un rango de permisos de acceso a los repositorios de la organización](/articles/repository-permission-levels-for-an-organization)
- [Los elementos anidados que reflejan la estructura de tu grupo o compañía](/articles/about-teams) con permisos de acceso y menciones en cascada{% ifversion not ghae %}
- La posibilidad de que los propietarios de la organización vean el [estado de autenticación de dos factores(2FA)](/articles/about-two-factor-authentication) de los miembros
-- La opción de [requerir que todos los miembros de la organización utilicen autenticación bifactorial](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}
+- The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}{% ifversion fpt%}
+- The ability to [create and administer classrooms with GitHub Classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms){% endif %}
{% ifversion fpt or ghec %}
Puedes utilizar las organizaciones de forma gratuita con
diff --git a/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md b/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md
index 3d980144e1..c40d3a47ca 100644
--- a/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md
+++ b/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md
@@ -1,5 +1,5 @@
{%- ifversion ghae %}
-1. In the `plugins` element of the *pom.xml* file, add the [checksum-maven-plugin](https://search.maven.org/artifact/net.nicoulaj.maven.plugins/checksum-maven-plugin) plugin, and configure the plugin to send at least SHA-256 checksums.
+1. En el elemento `plugins` del archivo *pom.xml*, agrega el plugin [checksum-maven-plugin](https://search.maven.org/artifact/net.nicoulaj.maven.plugins/checksum-maven-plugin) y configúralo para enviar por lo menos comprobaciones SHA-256.
```xml
diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md
new file mode 100644
index 0000000000..9c09c5248f
--- /dev/null
+++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md
@@ -0,0 +1,2 @@
+Once CI checks pass, {% data variables.product.product_name %} merges the pull request by fast-forwarding the default branch. The merge queue will use merge commits if the "Require linear history" branch protection setting is turned off, and the "Rebase and merge" method otherwise.
+
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md
index 9363401492..6e2a7cdd0f 100644
--- a/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md
+++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md
@@ -1,3 +1,5 @@
Merge queues for pull requests can increase the rate at which pull requests are merged into a busy default branch, whilst ensuring that CI checks pass.
-Once a pull request has passed any required checks and approvals, a contributor can add the pull request to the merge queue. The queue then creates a temporary branch with that pull request and any pull requests ahead of it in the queue, and triggers any required continuous integration (CI) checks. Once CI checks pass, {% data variables.product.product_name %} merges the pull request by fast-forwarding the default branch.
+Merge queues use {% data variables.product.prodname_actions %}. For more information about actions, see "[{% data variables.product.prodname_actions %}](/actions/)."
+
+Once a pull request has passed any required checks and approvals, a contributor with write access can add the pull request to the merge queue. The queue then creates a temporary branch with that pull request and any pull requests ahead of it in the queue, and triggers any required continuous integration (CI) checks.
diff --git a/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
index 4ca6162bed..43fe7d3734 100644
--- a/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
+++ b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
@@ -1,11 +1,11 @@
{% warning %}
-**Advertencia:**
+**Warning:**
-- Si eliminas el acceso de una persona a un repositorio privado, todas sus bifurcaciones de ese repositorio privado se eliminarán. Los clones locales del repositorio privado se conservarán. Si se revoca el acceso de un equipo a un repositorio privado o se elimina un equipo con acceso a un repositorio privado, y los miembros del equipo no tienen acceso al repositorio a través de otro equipo, las bifurcaciones privadas del repositorio se eliminarán.{% ifversion ghes %}
-- Cuando [LDAP Sync esté habilitado](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync), si eliminas a una persona de un repositorio, perderá acceso, pero sus bifurcaciones no se eliminarán. Si la persona se agrega a un equipo con acceso al repositorio original de la organización dentro de los tres meses, su acceso a las bifurcaciones se restaurarán de manera automática la próxima vez que ocurra una sincronización.{% endif %}
-- Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual.
+- If you remove a person’s access to a private repository, any of their forks of that private repository are deleted. Local clones of the private repository are retained. If a team's access to a private repository is revoked or a team with access to a private repository is deleted, and team members do not have access to the repository through another team, private forks of the repository will be deleted.{% ifversion ghes %}
+- When [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync), if you remove a person from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync.{% endif %}
+- You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
-- Las personas con permisos administrativos en un repositorio privado{% ifversion ghes or ghae or ghec %} o interno{% endif %} pueden dejar de permitir la bifurcación del mismo, y los propietarios de la organización pueden dejar de permitir la bifurcación de cualquier repositorio privado {% ifversion ghes or ghae or ghec %} o interno {% endif %} en una organización. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" y "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)".
+- People with admin permissions to a private{% ifversion ghes or ghae or ghec %} or internal{% endif %} repository can disallow forking of that repository, and organization owners can disallow forking of any private{% ifversion ghes or ghae or ghec %} or internal{% endif %} repository in an organization. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
{% endwarning %}
diff --git a/translations/es-ES/data/reusables/repositories/security-guidelines.md b/translations/es-ES/data/reusables/repositories/security-guidelines.md
index 36c886960a..7aac715200 100644
--- a/translations/es-ES/data/reusables/repositories/security-guidelines.md
+++ b/translations/es-ES/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
Puedes crear una política de seguridad para dar instrucciones a las personas para reportar las vulnerabilidades de seguridad en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)".
{% endif %}
diff --git a/translations/es-ES/data/reusables/repositories/sidebar-issues.md b/translations/es-ES/data/reusables/repositories/sidebar-issues.md
index 71e63b75b1..e17726b150 100644
--- a/translations/es-ES/data/reusables/repositories/sidebar-issues.md
+++ b/translations/es-ES/data/reusables/repositories/sidebar-issues.md
@@ -1,5 +1,5 @@
2. Debajo del nombre de tu repositorio, da clic en
{% octicon "issue-opened" aria-label="The issues icon" %} **Propuestas**.
- {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
+ {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
{% else %}
{% endif %}
diff --git a/translations/es-ES/data/reusables/repositories/sidebar-pr.md b/translations/es-ES/data/reusables/repositories/sidebar-pr.md
index bb96953c5c..ec55c20498 100644
--- a/translations/es-ES/data/reusables/repositories/sidebar-pr.md
+++ b/translations/es-ES/data/reusables/repositories/sidebar-pr.md
@@ -2,6 +2,6 @@
{% octicon "git-pull-request" aria-label="The pull request icon" %} **Solicitudes de cambios**.
{% ifversion fpt or ghec %}
- {% elsif ghes > 3.1 or ghae-next %}
+ {% elsif ghes > 3.1 or ghae %}
{% else %}
{% endif %}
diff --git a/translations/es-ES/data/reusables/saml/external-group-audit-events.md b/translations/es-ES/data/reusables/saml/external-group-audit-events.md
new file mode 100644
index 0000000000..0d8ec42f8d
--- /dev/null
+++ b/translations/es-ES/data/reusables/saml/external-group-audit-events.md
@@ -0,0 +1,7 @@
+| Acción | Descripción |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `external_group.delete` | Triggered when your Okta group is deleted. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
+| `external_group.link` | Triggered when your Okta group is mapped to your {% data variables.product.prodname_ghe_managed %} team. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
+| `external_group.provision` | Triggered when an Okta group is mapped to your team on {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
+| `external_group.unlink` | Triggered when your Okta group is unmapped from your {% data variables.product.prodname_ghe_managed %} team. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
+| `external_group.update` | Triggered when your Okta group's settings are updated. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/saml/external-identity-audit-events.md b/translations/es-ES/data/reusables/saml/external-identity-audit-events.md
new file mode 100644
index 0000000000..74a3811926
--- /dev/null
+++ b/translations/es-ES/data/reusables/saml/external-identity-audit-events.md
@@ -0,0 +1,5 @@
+| Acción | Descripción |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `external_identity.deprovision` | Triggered when a user is removed from your Okta group and is subsequently deprovisioned from {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
+| `external_identity.provision` | Triggered when an Okta user is added to your Okta group and is subsequently provisioned to the mapped team on {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
+| `external_identity.update` | Triggered when an Okta user's settings are updated. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/saml/okta-ae-applications-menu.md b/translations/es-ES/data/reusables/saml/okta-ae-applications-menu.md
new file mode 100644
index 0000000000..e20691a67e
--- /dev/null
+++ b/translations/es-ES/data/reusables/saml/okta-ae-applications-menu.md
@@ -0,0 +1,3 @@
+1. In the Okta Dashboard, expand the **Applications** menu, then click **Applications**.
+
+ 
diff --git a/translations/es-ES/data/reusables/saml/okta-ae-configure-app.md b/translations/es-ES/data/reusables/saml/okta-ae-configure-app.md
new file mode 100644
index 0000000000..ba304314fb
--- /dev/null
+++ b/translations/es-ES/data/reusables/saml/okta-ae-configure-app.md
@@ -0,0 +1,3 @@
+1. Click on the {% data variables.product.prodname_ghe_managed %} app.
+
+ 
diff --git a/translations/es-ES/data/reusables/saml/okta-ae-provisioning-tab.md b/translations/es-ES/data/reusables/saml/okta-ae-provisioning-tab.md
new file mode 100644
index 0000000000..2a9267415a
--- /dev/null
+++ b/translations/es-ES/data/reusables/saml/okta-ae-provisioning-tab.md
@@ -0,0 +1,3 @@
+1. Da clic en **Aprovisionamiento**.
+
+ 
diff --git a/translations/es-ES/data/reusables/saml/okta-ae-sso-beta.md b/translations/es-ES/data/reusables/saml/okta-ae-sso-beta.md
new file mode 100644
index 0000000000..599020093b
--- /dev/null
+++ b/translations/es-ES/data/reusables/saml/okta-ae-sso-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** {% data variables.product.prodname_ghe_managed %} single sign-on (SSO) support for Okta is currently in beta.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/saml/saml-supported-idps.md b/translations/es-ES/data/reusables/saml/saml-supported-idps.md
index 26402d8793..6263ae9071 100644
--- a/translations/es-ES/data/reusables/saml/saml-supported-idps.md
+++ b/translations/es-ES/data/reusables/saml/saml-supported-idps.md
@@ -11,4 +11,5 @@
- Shibboleth
{% elsif ghae %}
- Azure Active Directory (Azure AD)
+- Okta (beta)
{% endif %}
diff --git a/translations/es-ES/data/reusables/scim/supported-idps.md b/translations/es-ES/data/reusables/scim/supported-idps.md
index 0d38f43b12..87ae59bdf0 100644
--- a/translations/es-ES/data/reusables/scim/supported-idps.md
+++ b/translations/es-ES/data/reusables/scim/supported-idps.md
@@ -2,4 +2,5 @@ Los siguientes IdP pueden aprovisionar o desaprovisionar las cuentas de usuario
{% ifversion ghae %}
- Azure AD
+- Okta (currently in beta)
{% endif %}
diff --git a/translations/es-ES/data/reusables/secret-scanning/api-beta.md b/translations/es-ES/data/reusables/secret-scanning/api-beta.md
index 5d810c67a5..5da9aeb454 100644
--- a/translations/es-ES/data/reusables/secret-scanning/api-beta.md
+++ b/translations/es-ES/data/reusables/secret-scanning/api-beta.md
@@ -1,4 +1,4 @@
-{% ifversion ghes > 3.0 or ghae-next %}
+{% ifversion ghes > 3.0 or ghae %}
{% note %}
diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 2302ab0642..bee4e10bce 100644
--- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,31 +1,31 @@
| Proveedor | Secreto compatible | Slug de la API |
| ----------- | ----------------------- | ----------------- |
| Adafruit IO | Clave de IO de Adafruit | adafruit_io_key |
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Adobe | Token de Dispositivo de Adobe | adobe_device_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Adobe | Token de Servicio de Adobe | adobe_service_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Adobe | Token de Acceso de Duración Corta de Adobe | adobe_short_lived_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Adobe | Token Web JSON de Adobe | adobe_jwt{% endif %} Alibaba Cloud | ID de Llave de Acceso a Alibaba Cloud | alibaba_cloud_access_key_id Alibaba Cloud | Llave Secreta de Acceso a Alibaba Cloud | alibaba_cloud_access_key_secret Amazon Web Services (AWS) | ID de Llave de Acceso de Amazon AWS | aws_access_key_id Amazon Web Services (AWS) | Llave de Acceso Secreta de Amazon AWS | aws_secret_access_key
{%- ifversion fpt or ghec or ghes > 3.2 %}
Amazon Web Services (AWS) | Token de Sesión de Amazon AWS | aws_session_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
Amazon Web Services (AWS) | ID de Llave de Acceso Temporal de Amazon AWS | aws_temporary_access_key_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Asana | Token de Acceso Personal de Asana | asana_personal_access_token{% endif %} Atlassian | Token de la API de Atlassian | atlassian_api_token Atlassian | Token Web JSON de Atlassian | atlassian_jwt
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Atlassian | Token de Acceso Personal al Servidor de Bitbucket | bitbucket_server_personal_access_token{% endif %} Azure | Token de Acceso Personal a Azure DevOps | azure_devops_personal_access_token Azure | Token SAS de Azure | azure_sas_token Azure | Certificado de Administración de Servicios de Azure | azure_management_certificate
{%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %}
Azure | Secuencia de Conexión SQL de Azure | azure_sql_connection_string{% endif %} Azure | Llave de Cuenta de Almacenamiento de Azure | azure_storage_account_key
{%- ifversion fpt or ghec or ghes > 3.2 %}
Beamer | Llave de la API de Beamer | beamer_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Checkout.com | Llave de Secreto de Producción de Checkout.com | checkout_production_secret_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Checkout.com | Llave Secreta de Pruebas de Checkout.com | checkout_test_secret_key{% endif %} Clojars | Token de Despliegue de Clojars | clojars_deploy_token
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
CloudBees CodeShip | Credencial de CodeShip de CloudBees | codeship_credential{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
Contentful | Token de Acceso Personal a Contentful | contentful_personal_access_token{% endif %} Databricks | Token de Acceso a Databricks | databricks_access_token Discord | Token de Bot de Discord | discord_bot_token
@@ -37,33 +37,33 @@ Doppler | Token de Servicio de Doppler | doppler_service_token{% endif %}
Doppler | Token del CLI de Doppler | doppler_cli_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.0 or ghae %}
Doppler | Token de SCIM de Doppler | doppler_scim_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Doppler | Token de Auditoría de Doppler | doppler_audit_token{% endif %} Dropbox | Token de Acceso a Dropbox | dropbox_access_token Dropbox | Token de Acceso de Vida Corta a Dropbox | dropbox_short_lived_access_token
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Duffel | Token de Acceso en Vivo de Duffel | duffel_live_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Duffel | Token de Acceso de Prueba de Duffel | duffel_test_access_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.0 or ghae %}
Dynatrace | Token de Acceso a Dynatrace | dynatrace_access_token{% endif %} Dynatrace | Token Interno de Dynatrace | dynatrace_internal_token
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
EasyPost | Llave de la API de Producción de EasyPost | easypost_production_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
EasyPost | Llave de la API de Pruebas de EasyPost | easypost_test_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Fastly | Token de la API de Fastly | fastly_api_token{% endif %} Finicity | Llave de la App de Finicity | finicity_app_key
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Flutterwave | Llave de Secreto de la API en Vivo de Flutterwave | flutterwave_live_api_secret_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Flutterwave | Ññave Secreta de la API de Pruebas de Flutterwave | flutterwave_test_api_secret_key{% endif %} Frame.io | Token Web JSON de Frame.io | frameio_jwt Frame.io| Token de Desarrollador de Frame.io | frameio_developer_token
{%- ifversion fpt or ghec or ghes > 3.2 %}
FullStory | Llave de la API de FullStory | fullstory_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
GitHub | Token de Acceso Personal de GitHub | github_personal_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
GitHub | Token de Acceso de OAuth de GitHub | github_oauth_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
GitHub | Token de Actualización de GitHub | github_refresh_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} GitHub | GitHub SSH Private Key | github_ssh_private_key
{%- ifversion fpt or ghec or ghes > 3.3 %}
GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
@@ -83,31 +83,31 @@ Google | ID de Cliente OAuth de Google | google_oauth_client_id{% endif %}
Google | Secreto de Cliente OAuth de Google | google_oauth_client_secret{% endif %}
{%- ifversion fpt or ghec or ghes > 3.3 %}
Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Grafana | Llave de la API de Grafana | grafana_api_key{% endif %} Hashicorp Terraform | API del Token de Terraform Cloud / Enterprise | terraform_api_token Hubspot | Llave de la API de Hubspot | hubspot_api_key
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Intercom | Token de Acceso a Intercom | intercom_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Ionic | Token de Acceso Personal de Ionic | ionic_personal_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Ionic | Token de Actualización de Ionic | ionic_refresh_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
JFrog | Llave de la API de la Plataforma de JFrog | jfrog_platform_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Linear | Llave de la API de Linear | linear_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Linear | Token de Acceso Oauth de Linear | linear_oauth_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Lob | Llave de la API en Vivo de Lob | lob_live_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Lob | Llave de la API de Pruebas de Lob | lob_test_api_key{% endif %} Mailchimp | Llave de la API de Mailchimp | mailchimp_api_key Mailgun | Llave de la API de Mailgun | mailgun_api_key
{%- ifversion fpt or ghec or ghes > 3.3 %}
Mapbox | Token de Acceso Secreto a Mapbox | mapbox_secret_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
MessageBird | Llave de la API de MessageBird | messagebird_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Meta | Token de Acceso a Facebook | facebook_access_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
New Relic | Llave Personal de la API de New Relic | new_relic_personal_api_key{% endif %}
@@ -121,11 +121,11 @@ New Relic | Llave de Licencia de New Relic | new_relic_license_key{% endif %}
Notion | Notion Integration Token | notion_integration_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.3 %}
Notion | Notion OAuth Client Secret | notion_oauth_client_secret{% endif %} npm | npm Access Token | npm_access_token NuGet | NuGet API Key | nuget_api_key
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Onfido | Token de la API de Onfido Live | onfido_live_api_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Onfido | Token de la API de Onfido Sandbox | onfido_sandbox_api_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
OpenAI | Llave de la API de OpenAI | openai_api_key{% endif %} Palantir | Token Web JSON de Palantir | palantir_jwt
{%- ifversion fpt or ghec or ghes > 3.2 %}
PlanetScale | Contraseña de la Base de Datos de PlanetScale | planetscale_database_password{% endif %}
@@ -137,19 +137,19 @@ PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token{% end
Plivo | ID de Auth de Plivo | plivo_auth_id{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
Plivo | Token de Autenticación a Plivo | plivo_auth_token{% endif %} Postman | Llave de la API de Postman | postman_api_key Proctorio | Llave de Consumidor de Proctorio | proctorio_consumer_key Proctorio | Llave de Vinculación de Proctorio | proctorio_linkage_key Proctorio | Llave de Registro de Proctorio | proctorio_registration_key Proctorio | Llave de Secreto de Proctorio | proctorio_secret_key Pulumi | Toekn de Acceso a Pulumi | pulumi_access_token
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
PyPI | Token de la API de PyPI | pypi_api_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
RubyGems | Llave de la API de RubyGems | rubygems_api_key{% endif %} Samsara | Token de la API de Samsara | samsara_api_token Samsara | Token de Acceso OAuth a Samsara | samsara_oauth_access_token
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
SendGrid | Llave de la API de SendGrid | sendgrid_api_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
Sendinblue | Llave de la API de Sendinblue | sendinblue_api_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.2 %}
Sendinblue | Llave de SMTP de Sendinblue | sendinblue_smtp_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Shippo | Token de la API de Shippo Live | shippo_live_api_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Shippo | Token de la API de Pruebas de Shippo | shippo_test_api_token{% endif %} Shopify | Secreto Compartido de la App de Shopify | shopify_app_shared_secret Shopify | Token de Acceso a Shopify | shopify_access_token Shopify | Token de Acceso a la App Personalizada de Shopify | shopify_custom_app_access_token Shopify | Contraseña de la App Privada de Shopify | shopify_private_app_password Slack | Token de la API de Slack | slack_api_token Slack | URL del Webhook Entrante de Slack | slack_incoming_webhook_url Slack | URL del Webhook del Flujo de Trabajo de Slack | slack_workflow_webhook_url
{%- ifversion fpt or ghec or ghes > 3.3 %}
Square | Square Access Token | square_access_token{% endif %}
@@ -165,12 +165,12 @@ Stripe | Llave Secreta de la API de Prueba de Stripe | stripe_test_secret_key{%
Stripe | Llave Restringida de la API en Vivo de Stripe | stripe_live_restricted_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.0 or ghae %}
Stripe | Llave Restringida de la API de Prueba de Stripe | stripe_test_restricted_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Stripe | Secreto de Firmado de Webhook de Stripe | stripe_webhook_signing_secret{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
{%- ifversion fpt or ghec or ghes > 3.3 %}
Supabase | Supabase Service Key | supabase_service_key{% endif %} Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
Telegram | Token del Bot de Telegram | telegram_bot_token{% endif %} Tencent Cloud | ID Secreta de Tencent Cloud | tencent_cloud_secret_id
{%- ifversion fpt or ghec or ghes > 3.3 %}
Twilio | Token de Acceso a Twilio | twilio_access_token{% endif %} Twilio | Identificador de Secuencia de Cuenta de Twilio | twilio_account_sid Twilio | Llave de la API de Twilio | twilio_api_key
diff --git a/translations/es-ES/data/reusables/stars/stars-page-navigation.md b/translations/es-ES/data/reusables/stars/stars-page-navigation.md
new file mode 100644
index 0000000000..ce25909848
--- /dev/null
+++ b/translations/es-ES/data/reusables/stars/stars-page-navigation.md
@@ -0,0 +1 @@
+1. In the upper-right corner of any page, click your profile photo, then click ** Your stars**. 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md
index f0a72851b4..78729722f4 100644
--- a/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md
+++ b/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md
@@ -1,5 +1,5 @@
-{% data variables.contact.enterprise_support %} podría considerar a un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, {% ifversion ghae %}o {% endif %} instrucciones de solución alternativa{% ifversion ghes %}, o recomendándote un lanzamiento disponible que trate el problema{% endif %}.
+{% data variables.contact.enterprise_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, {% ifversion ghae %}or {% endif %} workaround instructions{% ifversion ghes %}, or by advising you of an available release that addresses the issue{% endif %}.
-Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.enterprise_support %} puede pedirte que elimines complementos, módulos o códigos no compatibles al intentar resolver el problema. Si el problema se arregla cuando el plug-in, módulo, o código personalizado no compatibles se eliminan, {% data variables.contact.enterprise_support %} podría considerar el ticket como resuelto.
+If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.enterprise_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.enterprise_support %} may consider the ticket solved.
-{% data variables.contact.enterprise_support %} podría cerrar un ticket si éste está fuera de su alcance o si han habido varios intentos para contactarte sin éxito. Si {% data variables.contact.enterprise_support %} cierra un ticket por falta de respuesta, puedes solicitar que lo vuelva a abrir.
+{% data variables.contact.enterprise_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.enterprise_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.enterprise_support %} reopen the ticket.
diff --git a/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md b/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md
index bda2be6cf1..01055b4e78 100644
--- a/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md
+++ b/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md
@@ -1,5 +1,5 @@
-{% data variables.contact.premium_support %} podría considerar un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, instrucciones de solución alternativa, o recomendándote un lanzamiento disponible que trata el problema.
+{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available release that addresses the issue.
-Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.premium_support %} puede pedirte que elimines el complemento, el módulo o el código no compatible mientras intentas resolver el problema. {% data variables.contact.premium_support %} puede considerar el ticket como resuelto si el problema se soluciona cuando se elimina el plug-in, módulo, o código personalizado no compatible.
+If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.premium_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.premium_support %} may consider the ticket solved.
-{% data variables.contact.premium_support %} podría cerrar un ticket si éste está fuera de su alcance o si han habido varios intentos para contactarte sin éxito. Si {% data variables.contact.premium_support %} cierra un ticket por no haber recibido respuesta, puedes solicitar que lo reabra.
+{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.premium_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.premium_support %} reopen the ticket.
diff --git a/translations/es-ES/data/reusables/supported-languages/python.md b/translations/es-ES/data/reusables/supported-languages/python.md
index 1427723cc8..2bf98383ae 100644
--- a/translations/es-ES/data/reusables/supported-languages/python.md
+++ b/translations/es-ES/data/reusables/supported-languages/python.md
@@ -1 +1 @@
-| Python |{% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
pip{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
+| Python |{% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %}
precise| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
pip{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
diff --git a/translations/es-ES/data/reusables/webhooks/check_run_properties.md b/translations/es-ES/data/reusables/webhooks/check_run_properties.md
index 71988ac64e..12015b12b4 100644
--- a/translations/es-ES/data/reusables/webhooks/check_run_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/check_run_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes: - `created` - Se creó una ejecución de verificación.
- `completed` - El `status` de la ejecución de verificación es `completed`.
- `rerequested` - Alguien volvió a solicitar que se volviera a ejecutar tu ejecución de verificación desde la IU de la solicitud de extracción. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub. Cuando recibes una acción de tipo `rerequested`, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó volver a ejecutar la verificación recibirá la carga útil de `rerequested`.
- `requested_action` - Alguien volvió a solicitar que se tome una acción que proporciona tu app. Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó llevar a cabo una acción recibirá la carga útil de `requested_action`. Para aprender más sobre las ejecuciones de verificación y las acciones solicitadas, consulta la sección "[Ejecuciones de ferificación y acciones solicitadas](/rest/reference/checks#check-runs-and-requested-actions)."
|
| `check_run` | `objeto` | La [check_run](/rest/reference/checks#get-a-check-run). |
diff --git a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md
index 300c2d99e0..7224ad2b90 100644
--- a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ---------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción realizada. Puede ser:- `completed` - Todas las ejecuciones de verificación en una suite de verificación se completaron.
- `requested` - Ocurre cuando se carga código nuevo al repositorio de la app. Cuando recibes un evento de acción de tipo `requested`, necesitarás [Crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run).
- `rerequested` - Ocurre cuando alguien solicita volver a ejecutar toda la suite de verificaciones desde la IU de la solicitud de extracción. Cuando recibes los eventos de una acción de tipo `rerequested, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub.
|
| `check_suite` | `objeto` | La [check_suite](/rest/reference/checks#suites). |
diff --git a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md
index 1e3bdf23c5..e39bbc74d2 100644
--- a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Este puede ser uno de entre `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, o `reopened`. |
| `alerta` | `objeto` | La alerta de escaneo de código involucrada en el evento. |
diff --git a/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md
index 5a09adfbf2..9fb6e5f95a 100644
--- a/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ------------ | ----------- | ------------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción realizada. Puede ser `created`. |
| `comentario` | `objeto` | El recurso de [comentario de la confirmación](/rest/reference/repos#get-a-commit-comment). |
diff --git a/translations/es-ES/data/reusables/webhooks/create_properties.md b/translations/es-ES/data/reusables/webhooks/create_properties.md
index e64b3ca05e..f0c5ada8a5 100644
--- a/translations/es-ES/data/reusables/webhooks/create_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/create_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `ref` | `secuencia` | El recurso de la [`git ref`](/rest/reference/git#get-a-reference). |
| `ref_type` | `secuencia` | El tipo de objeto de Git ref que se creó en el repositorio. Puede ser `branch` o `tag`. |
diff --git a/translations/es-ES/data/reusables/webhooks/delete_properties.md b/translations/es-ES/data/reusables/webhooks/delete_properties.md
index 727ad32af7..6e92c7eed9 100644
--- a/translations/es-ES/data/reusables/webhooks/delete_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/delete_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ---------- | ----------- | ---------------------------------------------------------------------------------------- |
| `ref` | `secuencia` | El recurso de la [`git ref`](/rest/reference/git#get-a-reference). |
| `ref_type` | `secuencia` | El tipo de objeto de Git ref que se borró en el repositorio. Puede ser `branch` o `tag`. |
diff --git a/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md
index d1e29d86b4..01db75f554 100644
--- a/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción realizada. Puede ser tanto `created` como `deleted`. |
| `clave` | `objeto` | El recurso [`deploy key`](/rest/reference/repos#get-a-deploy-key). |
diff --git a/translations/es-ES/data/reusables/webhooks/fork_properties.md b/translations/es-ES/data/reusables/webhooks/fork_properties.md
index a00605b049..731ec88d0c 100644
--- a/translations/es-ES/data/reusables/webhooks/fork_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/fork_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | -------- | --------------------------------------------------------------------------------- |
| `forkee` | `objeto` | El recurso de [`repository`](/rest/reference/repos#get-a-repository) que se creó. |
diff --git a/translations/es-ES/data/reusables/webhooks/gollum_properties.md b/translations/es-ES/data/reusables/webhooks/gollum_properties.md
index 98ca0e4bf3..39a7756aae 100644
--- a/translations/es-ES/data/reusables/webhooks/gollum_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/gollum_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------------------- | ----------- | ---------------------------------------------------------------------- |
| `páginas` | `arreglo` | Las páginas que se actualizaron. |
| `pages[][page_name]` | `secuencia` | El nombre de la página. |
diff --git a/translations/es-ES/data/reusables/webhooks/installation_properties.md b/translations/es-ES/data/reusables/webhooks/installation_properties.md
index 913f410ce2..2746802fde 100644
--- a/translations/es-ES/data/reusables/webhooks/installation_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/installation_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------------- | ----------- | ----------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:- `created` - Alguien instala una {% data variables.product.prodname_github_app %}.
- `deleted` - Alguien desinstala una {% data variables.product.prodname_github_app %}
{% ifversion fpt or ghes or ghae or ghec %}- `suspend` - alguien suspende la instalación de una {% data variables.product.prodname_github_app %}.
- `unsuspend` - Alguien deja de suspender una instalación de {% data variables.product.prodname_github_app %}.
{% endif %}- `new_permissions_accepted` - Alguien acepta permisos nuevos para una instalación de {% data variables.product.prodname_github_app %}. Cuando un propietario de una {% data variables.product.prodname_github_app %} solcita permisos nuevos, la persona que instaló dicha {% data variables.product.prodname_github_app %} debe aceptar la solicitud de estos permisos nuevos.
|
| `repositories` | `arreglo` | Un areglo de objetos de repositorio al que puede acceder la instalación. |
diff --git a/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md b/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md
index ecbe522cdb..7adfdfa19f 100644
--- a/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser tanto `added` como `removed`. |
| `repository_selection` | `secuencia` | La elección de repositorios en los cuales se encuentra la instalación. Puede ser tanto `selected` como `all`. |
diff --git a/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md
index 517915c39f..4f1f637743 100644
--- a/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | -------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. |
diff --git a/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md
index 42e5ad095f..f912fa2c38 100644
--- a/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, o `unlabeled`. |
diff --git a/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md
index 0b69e0fa29..0d42edcd07 100644
--- a/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `opened`, `edited`, `deleted`, `pinned`, `unpinned`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, `unlabeled`, `locked`, `unlocked`, `transferred`, `milestoned`, o `demilestoned`. |
diff --git a/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md
index 46d749a875..90cbcc889b 100644
--- a/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ---------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `added` para indicar que un usuario aceptó una invitación al repositorio. |
diff --git a/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md
index ff479a4024..5936ddb985 100644
--- a/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ----------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:- `added` - Un usuario acepta una invitación a un repositorio.
- `removed` - Se elimina a un usuario como colaborador de un repositorio.
- `edited` - Han cambiado los permisos de colaborador de un usuario.
|
diff --git a/translations/es-ES/data/reusables/webhooks/membership_properties.md b/translations/es-ES/data/reusables/webhooks/membership_properties.md
index eb5e6b565c..5284292644 100644
--- a/translations/es-ES/data/reusables/webhooks/membership_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/membership_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------- | ----------- | --------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser `added` o `removed`. |
| `alcance` | `secuencia` | El alcance de la membrecía. Acutalmente, solo puede ser `team`. |
diff --git a/translations/es-ES/data/reusables/webhooks/milestone_properties.md b/translations/es-ES/data/reusables/webhooks/milestone_properties.md
index e875f5bc69..292021c0ec 100644
--- a/translations/es-ES/data/reusables/webhooks/milestone_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/milestone_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ---------------------------- | ----------- | ------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre: `created`, `closed`, `opened`, `edited`, o `deleted`. |
| `hito` | `objeto` | El hito mismo. |
diff --git a/translations/es-ES/data/reusables/webhooks/package_properties.md b/translations/es-ES/data/reusables/webhooks/package_properties.md
index 0ed44ec297..3cd2722195 100644
--- a/translations/es-ES/data/reusables/webhooks/package_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/package_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------- | ----------- | ------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser `published` o `updated`. |
| `paquete` | `objeto` | La información sobre el paquete. |
diff --git a/translations/es-ES/data/reusables/webhooks/project_card_properties.md b/translations/es-ES/data/reusables/webhooks/project_card_properties.md
index d094490cdb..47dcc76361 100644
--- a/translations/es-ES/data/reusables/webhooks/project_card_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/project_card_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción llevada a cabo en la tarjeta del proyecto. Puede ser `created`, `edited`, `moved`, `converted`, o `deleted`. |
| `changes` | `objeto` | Los cambios a la tarjeta del proyecto si la acción se puso como `edited` o `converted`. |
diff --git a/translations/es-ES/data/reusables/webhooks/project_column_properties.md b/translations/es-ES/data/reusables/webhooks/project_column_properties.md
index fba0041ffb..b21c652122 100644
--- a/translations/es-ES/data/reusables/webhooks/project_column_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/project_column_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó en la columna de proyecto. Puede ser una de entre `created`, `edited`, `moved` o `deleted`. |
| `changes` | `objeto` | Los cambios a la columna del proyecto si la acción se puso como `edited`. |
diff --git a/translations/es-ES/data/reusables/webhooks/project_properties.md b/translations/es-ES/data/reusables/webhooks/project_properties.md
index 41f15ed400..d6132e30b3 100644
--- a/translations/es-ES/data/reusables/webhooks/project_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/project_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción que se realizó en el proyecto. Puede ser uno de entre: `created`, `edited`, `closed`, `reopened`, o `deleted`. |
| `changes` | `objeto` | Los cambios al proyecto si la acción se puso como `edited`. |
diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md
index 03fe366d0b..21e7eb30eb 100644
--- a/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, y `synchronize`. |
diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
index 108cda8365..193c77ca4a 100644
--- a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | --------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`. |
diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
index 517915c39f..4f1f637743 100644
--- a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | -------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. |
diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md
index 8505fcdce2..bbd73c9214 100644
--- a/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ---------------------- | ----------- | ------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:- `submitted` - Se emitió una solicitud de extracción en un estado no pendiente.
- `edited` - el cuerpo de una revisión se editó.
- `dismissed` - Se descartó una revisión.
|
| `solicitud_extracción` | `objeto` | La [solicitud de extracción](/rest/reference/pulls) a la cual pertenece la revisión. |
diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md
index 5a1ed8c18f..8d62c7db5b 100644
--- a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ----------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:- `assigned`
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}- `auto_merge_disabled`
- `auto_merge_enabled`
{% endif %}- `closed`: Si la acción se muestra como `closed` y la clave `merged` está como `false`, la solicitud de cambios se cerró con confimraciones sin fusionar. Si la acción está `closed` y la clave que está como `merged` está en `true`, la solicitud de cambios se fusionó.
- `converted_to_draft`
- `edited`
- `labeled`
- `locked`
- `opened`
- `ready_for_review`
- `reopened`
- `review_request_removed`
- `review_requested`
- `synchronize`: Se activa cuando se actualiza la rama de encabezado de una solicitud 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.
- `unassigned`
- `unlabeled`
- `unlocked`
|
diff --git a/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md
index 32e6fa2985..9c534eafd7 100644
--- a/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | --------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `published`. |
diff --git a/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md
index fff2412103..a66281e74b 100644
--- a/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:- `published`: se publica un lanzamiento, pre-lanzamiento, o borrador de un lanzamiento
- `unpublished`: se borra un lanzamiento o pre-lanzamiento
- `created`: se guarda un borrador, o se publica un lanzamiento o pre-lanzamiento sin que se haya guardado previamente como un borrador
- `edited`: se edita un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
- `deleted`: se borra un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
- `prereleased`: se crea un pre-lanzamiento
- `released`: se publica un lanzamiento o borrador de un lanzamiento, o se cambia un prelanzamiento a lanzamiento
|
diff --git a/translations/es-ES/data/reusables/webhooks/repository_import_properties.md b/translations/es-ES/data/reusables/webhooks/repository_import_properties.md
index b695be300b..0eadefb117 100644
--- a/translations/es-ES/data/reusables/webhooks/repository_import_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/repository_import_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------------------------------------------- |
| `estado` | `secuencia` | El estado final de la importación. Este puede ser alguno de entre: `success`, `cancelled`, o `failure`. |
diff --git a/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md
index 62f800c9ca..206f353fb0 100644
--- a/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Este puede ser alguno de entre: `create`, `dismiss`, o `resolve`. |
| `alerta` | `objeto` | La alerta de seguridad de la dependencia vulnerable. |
diff --git a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md
index 8c9ab1fa16..f05b41ec01 100644
--- a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser ya sea `created`, `resolved`, o `reopened`. |
| `alerta` | `objeto` | La alerta del escaneo de secretos involucrada en el evento. |
diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md
index 178dc2e34d..28458c3853 100644
--- a/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ---------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`. |
diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md
index 7b747286ea..cbdd521f07 100644
--- a/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser una de entre: `created`, `cancelled`, `edited`, `tier_changed`, `pending_cancellation`, o `pending_tier_change`. Nota: La acción `created` solo se activa después de que se procesa un pago. |
diff --git a/translations/es-ES/data/reusables/webhooks/star_properties.md b/translations/es-ES/data/reusables/webhooks/star_properties.md
index 634104251a..a80dd2a379 100644
--- a/translations/es-ES/data/reusables/webhooks/star_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/star_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| ------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción realizada. Puede ser `created` o `deleted`. |
| `starred_at` | `secuencia` | La hora en la cual se creó un marcado con estrella. {% data reusables.shortdesc.iso_8601 %} Será `null` para las acciones que estén como `deleted`. |
diff --git a/translations/es-ES/data/reusables/webhooks/watch_properties.md b/translations/es-ES/data/reusables/webhooks/watch_properties.md
index 21b3643e64..b3930bbc65 100644
--- a/translations/es-ES/data/reusables/webhooks/watch_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/watch_properties.md
@@ -1,3 +1,3 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------- | ----------- | ---------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Acutalmente, solo puede ser `started`. |
diff --git a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md
index 1a54bff9f7..3d9ee845ac 100644
--- a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| --------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes: - `queued` - Se creó un job nuevo.
- `in_progress` - El job se comenzó a procesar en el ejecutor.
- `completed` - el `status` del job es `completed`.
|
| `workflow_job` | `objeto` | El job de flujo de trabajo. Muchas claves de `workflow_job`, tales como `head_sha`, `conclusion`, y `started_at` son las mismas que aquellas en un objeto [`check_run`](#check_run). |
diff --git a/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md b/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md
index 39bec3188e..52f531e154 100644
--- a/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md
@@ -1,4 +1,4 @@
-| Clave | Type | Descripción |
+| Clave | Tipo | Descripción |
| -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `requested` o `completed`. |
| `workflow_run` | `objeto` | La ejecución del flujo de trabajo. Muchas claves de `workflow_run`, tales como `head_branch`, `conclusion`, y `pull_requests` son las mismas que aquellas en un objeto [`check_suite`](#check_suite). |
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index e33e7fe7f2..fdb24cf77b 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -14,8 +14,7 @@ header:
ghes_release_notes_upgrade_release_only: '📣 Este no es el lanzamiento más reciente de Enterprise Server.'
ghes_release_notes_upgrade_patch_and_release: '📣 Este no es el lanzamiento de parche más reciente de esta serie de lanzamientos, y no es elúltimo lanzamiento de Enterprise Server.'
release_notes:
- banner_text_current: Estos cam bios se implementarán en la siguiente semana.
- banner_text_past: Estos cambios se implementarán en las empresas durante la semana de
+ banner_text: GitHub comenzó a implementar estos cambios en empresas en
search:
need_help: '¿Necesitas ayuda?'
placeholder: Busca temas, productos...
@@ -70,7 +69,7 @@ products:
fields: Campos
arguments: Argumentos
name: Nombre
- type: Type
+ type: Tipo
description: Descripción
input_fields: Campos de entrada
return_fields: Campos de retorno
@@ -161,7 +160,7 @@ product_guides:
all_guides: 'Todas las guías de {{ productMap[currentProduct].name }}'
filter_instructions: Filtra la lista de guías utilizando estos controles
filters:
- type: Type
+ type: Tipo
topic: Tema
all: Todas
guides_found:
diff --git a/translations/es-ES/data/variables/actions.yml b/translations/es-ES/data/variables/actions.yml
index 86968e6229..4fa0661763 100644
--- a/translations/es-ES/data/variables/actions.yml
+++ b/translations/es-ES/data/variables/actions.yml
@@ -1,3 +1,2 @@
---
-hosted_runner: 'Ejecutor hospedado en AE'
azure_portal: 'Portal de Azure'
diff --git a/translations/es-ES/data/variables/enterprise.yml b/translations/es-ES/data/variables/enterprise.yml
index 2757a36221..f48e897988 100644
--- a/translations/es-ES/data/variables/enterprise.yml
+++ b/translations/es-ES/data/variables/enterprise.yml
@@ -1,4 +1,4 @@
---
management_console: 'Consola de administración'
#https://support.github.com/enterprise/server-upgrade
-upgrade_assistant: 'Upgrade assistant'
+upgrade_assistant: 'Asistente de mejora'
diff --git a/translations/es-ES/data/variables/gists.yml b/translations/es-ES/data/variables/gists.yml
index 2973c08309..ad196f4396 100644
--- a/translations/es-ES/data/variables/gists.yml
+++ b/translations/es-ES/data/variables/gists.yml
@@ -1,7 +1,7 @@
---
gist_homepage: >-
- {% ifversion fpt or ghec %}[gist home page](https://gist.github.com/){% elsif ghae %}gist home page, `http(s)://gist.[hostname]`{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %}
+ {% ifversion fpt or ghec %}[página de inicio de gist](https://gist.github.com/){% elsif ghae %}página de inicio de gist, `http(s)://gist.[hostname]`{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` si se habilitaron los subdominios{% endif %}
gist_search_url: >-
- {% ifversion fpt or ghec %}[Gist Search](https://gist.github.com/search){% elsif ghae %}Gist Search, `http(s)://gist.[hostname]/search`{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %}
+ {% ifversion fpt or ghec %}[Búsqueda de Gists](https://gist.github.com/search){% elsif ghae %}Búsqueda de Gists, `http(s)://gist.[hostname]/search`,{% else %}Búsqueda de Gists, `http(s)://[hostname]/gist/search` o `http(s)://gist.[hostname]/search` si se habilitaron los subdominios{% endif %}
discover_url: >-
- {% ifversion fpt or ghec %}[Discover](https://gist.github.com/discover){% elsif ghae %}Discover, `http(s)://gist.[hostname]/discover`{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %}
+ {% ifversion fpt or ghec %}[Discover](https://gist.github.com/discover){% elsif ghae %}Descubre, `http(s)://gist.[hostname]/discover`,{% else %}Descubre, `http(s)://[hostname]/gist/discover` o `http(s)://gist.[hostname]/discover` si se habilitaron los subdominios{% endif %}
diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml
index 1749ca6ab8..8f5edae6a8 100644
--- a/translations/es-ES/data/variables/product.yml
+++ b/translations/es-ES/data/variables/product.yml
@@ -46,8 +46,8 @@ prodname_cli: 'CLI de GitHub'
#GitHub Desktop
prodname_desktop: 'GitHub Desktop'
desktop_link: 'https://desktop.github.com/'
-#GitHub for Mobile
-prodname_mobile: 'GitHub para móviles'
+#GitHub Mobile
+prodname_mobile: 'GitHub Mobile'
prodname_ios: 'GitHub para iOS'
prodname_android: 'GitHub para Android'
#GitHub Pages
diff --git a/translations/es-ES/data/variables/release_candidate.yml b/translations/es-ES/data/variables/release_candidate.yml
index 361ba6ba63..ec65ef6f94 100644
--- a/translations/es-ES/data/variables/release_candidate.yml
+++ b/translations/es-ES/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
---
-version: enterprise-server@3.3
+version: ''
diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv
index dc53402601..c017a692dd 100644
--- a/translations/log/es-resets.csv
+++ b/translations/log/es-resets.csv
@@ -1,22 +1,37 @@
file,reason
+translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error
+translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
+translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,rendering error
+translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
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/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error
translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,Listed in localization-support#489
translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.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/about-your-profile.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,Listed in localization-support#489
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/pinning-items-to-your-profile.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/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-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/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-github-user-account/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-github-user-account/managing-email-preferences/index.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,Listed in localization-support#489
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,Listed in localization-support#489
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,Listed in localization-support#489
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,rendering error
@@ -29,27 +44,54 @@ 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-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,Listed in localization-support#489
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error
+translations/es-ES/content/actions/advanced-guides/index.md,rendering error
translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,Listed in localization-support#489
translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error
+translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md,rendering error
translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md,rendering error
translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md,rendering error
translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,Listed in localization-support#489
translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,rendering error
translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md,Listed in localization-support#489
translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/index.md,rendering error
+translations/es-ES/content/actions/creating-actions/about-custom-actions.md,rendering error
+translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md,rendering error
translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,Listed in localization-support#489
translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
+translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md,rendering error
+translations/es-ES/content/actions/creating-actions/index.md,rendering error
translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
translations/es-ES/content/actions/creating-actions/releasing-and-maintaining-actions.md,rendering error
+translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md,rendering error
translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
+translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md,rendering error
translations/es-ES/content/actions/deployment/about-deployments/index.md,Listed in localization-support#489
translations/es-ES/content/actions/deployment/about-deployments/index.md,rendering error
+translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error
+translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service.md,rendering error
+translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md,Listed in localization-support#489
translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md,rendering error
+translations/es-ES/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error
+translations/es-ES/content/actions/deployment/index.md,rendering error
translations/es-ES/content/actions/deployment/managing-your-deployments/index.md,Listed in localization-support#489
translations/es-ES/content/actions/deployment/managing-your-deployments/index.md,rendering error
+translations/es-ES/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error
translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,Listed in localization-support#489
translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,rendering error
translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md,Listed in localization-support#489
@@ -69,11 +111,15 @@ translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-r
translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,Listed in localization-support#489
translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
+translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,rendering error
+translations/es-ES/content/actions/hosting-your-own-runners/index.md,rendering error
translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error
translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489
translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error
translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error
translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md,rendering error
+translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error
+translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,rendering error
translations/es-ES/content/actions/index.md,Listed in localization-support#489
translations/es-ES/content/actions/index.md,rendering error
translations/es-ES/content/actions/learn-github-actions/contexts.md,Listed in localization-support#489
@@ -81,38 +127,79 @@ translations/es-ES/content/actions/learn-github-actions/contexts.md,rendering er
translations/es-ES/content/actions/learn-github-actions/creating-workflow-templates.md,rendering error
translations/es-ES/content/actions/learn-github-actions/environment-variables.md,Listed in localization-support#489
translations/es-ES/content/actions/learn-github-actions/environment-variables.md,rendering error
+translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md,rendering error
translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md,Listed in localization-support#489
translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md,rendering error
translations/es-ES/content/actions/learn-github-actions/expressions.md,rendering error
translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md,rendering error
+translations/es-ES/content/actions/learn-github-actions/index.md,rendering error
+translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md,rendering error
translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md,rendering error
+translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error
translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
+translations/es-ES/content/actions/learn-github-actions/using-workflow-templates.md,rendering error
translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,Listed in localization-support#489
translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,rendering error
translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,Listed in localization-support#489
translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md,rendering error
+translations/es-ES/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md,rendering error
translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,rendering error
+translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md,rendering error
+translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md,rendering error
+translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md,rendering error
+translations/es-ES/content/actions/managing-workflow-runs/index.md,rendering error
translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,Listed in localization-support#489
translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
+translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error
+translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md,rendering error
translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md,rendering error
+translations/es-ES/content/actions/migrating-to-github-actions/index.md,rendering error
+translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md,rendering error
+translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md,rendering error
+translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md,rendering error
+translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md,rendering error
+translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md,rendering error
translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md,rendering error
translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md,rendering error
+translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md,rendering error
+translations/es-ES/content/actions/publishing-packages/index.md,rendering error
translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md,rendering error
translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md,rendering error
+translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md,rendering error
translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error
translations/es-ES/content/actions/quickstart.md,Listed in localization-support#489
translations/es-ES/content/actions/quickstart.md,rendering error
translations/es-ES/content/actions/security-guides/automatic-token-authentication.md,Listed in localization-support#489
translations/es-ES/content/actions/security-guides/automatic-token-authentication.md,rendering error
+translations/es-ES/content/actions/security-guides/encrypted-secrets.md,rendering error
+translations/es-ES/content/actions/security-guides/index.md,rendering error
translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
-translations/es-ES/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md,rendering error
+translations/es-ES/content/actions/using-containerized-services/about-service-containers.md,rendering error
+translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md,rendering error
+translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md,rendering error
+translations/es-ES/content/actions/using-containerized-services/index.md,rendering error
translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,Listed in localization-support#489
translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,Listed in localization-support#489
translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,rendering error
+translations/es-ES/content/actions/using-github-hosted-runners/index.md,rendering error
translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error
translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,rendering error
translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md,Listed in localization-support#489
@@ -121,19 +208,29 @@ translations/es-ES/content/admin/advanced-security/enabling-github-advanced-secu
translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md,rendering error
translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error
+translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md,rendering error
translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,Listed in localization-support#489
translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error
translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error
+translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,rendering error
+translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,rendering error
+translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md,rendering error
translations/es-ES/content/admin/authentication/index.md,rendering error
+translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md,rendering error
+translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,rendering error
+translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,rendering error
translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md,rendering error
translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,rendering error
@@ -141,12 +238,14 @@ translations/es-ES/content/admin/configuration/managing-connections-between-your
translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,rendering error
translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,rendering error
translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,rendering error
+translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,rendering error
translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,Listed in localization-support#489
translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,Listed in localization-support#489
translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,Listed in localization-support#489
translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,rendering error
+translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,rendering error
translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md,rendering error
translations/es-ES/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md,rendering error
translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,Listed in localization-support#489
@@ -159,6 +258,7 @@ translations/es-ES/content/admin/enterprise-management/configuring-high-availabi
translations/es-ES/content/admin/enterprise-management/index.md,Listed in localization-support#489
translations/es-ES/content/admin/enterprise-management/index.md,rendering error
translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
+translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,rendering error
translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,Listed in localization-support#489
translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
@@ -186,11 +286,14 @@ translations/es-ES/content/admin/github-actions/index.md,rendering error
translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,Listed in localization-support#489
translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,rendering error
+translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md,rendering error
translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,Listed in localization-support#489
translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,rendering error
+translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,rendering error
translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,Listed in localization-support#489
translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,rendering error
translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md,rendering error
+translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md,rendering error
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
@@ -208,6 +311,7 @@ translations/es-ES/content/admin/overview/system-overview.md,rendering error
translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,Listed in localization-support#489
translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
+translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,rendering error
translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
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-project-board-policies-in-your-enterprise.md,rendering error
@@ -217,6 +321,10 @@ translations/es-ES/content/admin/user-management/managing-organizations-in-your-
translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,rendering error
translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,Listed in localization-support#489
translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md,rendering error
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md,rendering error
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md,rendering error
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md,rendering error
translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md,rendering error
translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,Listed in localization-support#489
translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,rendering error
@@ -244,6 +352,7 @@ translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a
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,Listed in localization-support#489
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
+translations/es-ES/content/authentication/index.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,Listed in localization-support#489
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,Listed in localization-support#489
@@ -252,6 +361,10 @@ translations/es-ES/content/authentication/keeping-your-account-and-data-secure/a
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
@@ -262,10 +375,15 @@ translations/es-ES/content/authentication/managing-commit-signature-verification
translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
translations/es-ES/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error
+translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error
translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
+translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
+translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
+translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md,Listed in localization-support#489
translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md,rendering error
+translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error
translations/es-ES/content/billing/index.md,rendering error
translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,Listed in localization-support#489
translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error
@@ -287,6 +405,7 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,Listed in localization-support#489
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,Listed in localization-support#489
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,Listed in localization-support#489
@@ -294,6 +413,7 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,Listed in localization-support#489
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md,rendering error
translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,rendering error
@@ -302,8 +422,10 @@ translations/es-ES/content/code-security/code-scanning/using-codeql-code-scannin
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,rendering error
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,rendering error
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
+translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error
translations/es-ES/content/code-security/getting-started/github-security-features.md,Listed in localization-support#489
translations/es-ES/content/code-security/getting-started/github-security-features.md,rendering error
translations/es-ES/content/code-security/getting-started/securing-your-organization.md,Listed in localization-support#489
@@ -316,6 +438,7 @@ translations/es-ES/content/code-security/index.md,Listed in localization-support
translations/es-ES/content/code-security/index.md,rendering error
translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md,Listed in localization-support#489
translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
+translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,Listed in localization-support#489
translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error
@@ -378,6 +501,7 @@ translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-de
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/connecting-to-a-private-network.md,rendering error
translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,Listed in localization-support#489
translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error
translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,Listed in localization-support#489
@@ -420,13 +544,14 @@ translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md,renderi
translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,Listed in localization-support#489
translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,rendering error
translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,Listed in localization-support#489
-translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
+translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,parsing error
translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error
translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md,rendering error
translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error
translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md,Listed in localization-support#489
translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md,rendering error
+translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,rendering error
translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md,Listed in localization-support#489
translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md,rendering error
translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md,Listed in localization-support#489
@@ -434,14 +559,22 @@ translations/es-ES/content/desktop/contributing-and-collaborating-using-github-d
translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,Listed in localization-support#489
translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,rendering error
translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
+translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md,rendering error
translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
translations/es-ES/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
+translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
+translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error
translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
translations/es-ES/content/developers/apps/guides/using-content-attachments.md,rendering error
+translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
+translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
+translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
+translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error
translations/es-ES/content/developers/overview/managing-deploy-keys.md,rendering error
+translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md,rendering error
translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md,Listed in localization-support#489
translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md,rendering error
translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
@@ -454,20 +587,35 @@ translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learni
translations/es-ES/content/education/guides.md,Listed in localization-support#489
translations/es-ES/content/education/guides.md,rendering error
translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,rendering error
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,Listed in localization-support#489
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,rendering error
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,Listed in localization-support#489
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,rendering error
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,Listed in localization-support#489
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md,Listed in localization-support#489
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md,rendering error
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error
+translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
+translations/es-ES/content/get-started/exploring-projects-on-github/index.md,rendering error
+translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error
+translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
+translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error
translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
+translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error
+translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md,rendering error
+translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md,rendering error
+translations/es-ES/content/get-started/getting-started-with-git/index.md,rendering error
translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
+translations/es-ES/content/get-started/index.md,rendering error
translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
+translations/es-ES/content/get-started/learning-about-github/index.md,rendering error
translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,Listed in localization-support#489
@@ -477,6 +625,7 @@ translations/es-ES/content/get-started/onboarding/getting-started-with-github-te
translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
translations/es-ES/content/get-started/quickstart/be-social.md,Listed in localization-support#489
translations/es-ES/content/get-started/quickstart/be-social.md,rendering error
+translations/es-ES/content/get-started/quickstart/communicating-on-github.md,rendering error
translations/es-ES/content/get-started/quickstart/create-a-repo.md,rendering error
translations/es-ES/content/get-started/quickstart/fork-a-repo.md,Listed in localization-support#489
translations/es-ES/content/get-started/quickstart/fork-a-repo.md,rendering error
@@ -484,23 +633,33 @@ translations/es-ES/content/get-started/quickstart/git-and-github-learning-resour
translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md,rendering error
translations/es-ES/content/get-started/quickstart/github-flow.md,Listed in localization-support#489
translations/es-ES/content/get-started/quickstart/github-flow.md,rendering error
+translations/es-ES/content/get-started/quickstart/index.md,rendering error
+translations/es-ES/content/get-started/quickstart/set-up-git.md,rendering error
+translations/es-ES/content/get-started/signing-up-for-github/index.md,rendering error
+translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error
translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error
+translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
translations/es-ES/content/get-started/using-git/about-git-rebase.md,Listed in localization-support#489
translations/es-ES/content/get-started/using-git/about-git-rebase.md,rendering error
+translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md,rendering error
translations/es-ES/content/get-started/using-git/about-git.md,rendering error
translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md,Listed in localization-support#489
translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error
+translations/es-ES/content/get-started/using-git/index.md,rendering error
translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,Listed in localization-support#489
translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error
translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md,Listed in localization-support#489
translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md,rendering error
translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
+translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error
translations/es-ES/content/get-started/using-github/github-command-palette.md,Listed in localization-support#489
translations/es-ES/content/get-started/using-github/github-command-palette.md,rendering error
-translations/es-ES/content/get-started/using-github/github-for-mobile.md,rendering error
+translations/es-ES/content/get-started/using-github/github-mobile.md,rendering error
+translations/es-ES/content/get-started/using-github/index.md,rendering error
translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,Listed in localization-support#489
translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,rendering error
+translations/es-ES/content/get-started/using-github/supported-browsers.md,rendering error
translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error
translations/es-ES/content/github-cli/github-cli/github-cli-reference.md,Listed in localization-support#489
translations/es-ES/content/github-cli/github-cli/github-cli-reference.md,rendering error
@@ -508,6 +667,7 @@ translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md,rend
translations/es-ES/content/github/copilot/index.md,Listed in localization-support#489
translations/es-ES/content/github/copilot/index.md,rendering error
translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,rendering error
+translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
translations/es-ES/content/github/extending-github/about-webhooks.md,rendering error
translations/es-ES/content/github/extending-github/getting-started-with-the-api.md,rendering error
translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error
@@ -521,6 +681,7 @@ translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-sa
translations/es-ES/content/github/site-policy/github-data-protection-agreement.md,rendering error
translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md,Listed in localization-support#489
translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error
+translations/es-ES/content/github/site-policy/github-terms-of-service.md,rendering error
translations/es-ES/content/github/site-policy/index.md,Listed in localization-support#489
translations/es-ES/content/github/site-policy/index.md,rendering error
translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,rendering error
@@ -533,10 +694,13 @@ translations/es-ES/content/github/working-with-github-support/submitting-a-ticke
translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md,rendering error
translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,Listed in localization-support#489
translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
+translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md,rendering error
translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md,rendering error
translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md,rendering error
translations/es-ES/content/graphql/guides/index.md,rendering error
+translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md,rendering error
translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md,rendering error
+translations/es-ES/content/graphql/index.md,rendering error
translations/es-ES/content/graphql/overview/breaking-changes.md,Listed in localization-support#489
translations/es-ES/content/graphql/overview/breaking-changes.md,rendering error
translations/es-ES/content/index.md,Listed in localization-support#489
@@ -638,6 +802,7 @@ translations/es-ES/content/packages/learn-github-packages/installing-a-package.m
translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
translations/es-ES/content/packages/learn-github-packages/publishing-a-package.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/quickstart.md,rendering error
translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,rendering error
translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,rendering error
@@ -805,6 +970,7 @@ translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md,rendering error
+translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,Listed in localization-support#489
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md,rendering error
@@ -858,6 +1024,7 @@ translations/es-ES/content/rest/guides/index.md,rendering error
translations/es-ES/content/rest/guides/rendering-data-as-graphs.md,rendering error
translations/es-ES/content/rest/guides/traversing-with-pagination.md,rendering error
translations/es-ES/content/rest/guides/working-with-comments.md,rendering error
+translations/es-ES/content/rest/index.md,rendering error
translations/es-ES/content/rest/overview/api-previews.md,rendering error
translations/es-ES/content/rest/overview/libraries.md,rendering error
translations/es-ES/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489
@@ -878,6 +1045,7 @@ translations/es-ES/content/rest/reference/enterprise-admin.md,rendering error
translations/es-ES/content/rest/reference/gitignore.md,rendering error
translations/es-ES/content/rest/reference/licenses.md,rendering error
translations/es-ES/content/rest/reference/migrations.md,rendering error
+translations/es-ES/content/rest/reference/packages.md,rendering error
translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md,rendering error
translations/es-ES/content/rest/reference/pulls.md,Listed in localization-support#489
translations/es-ES/content/rest/reference/pulls.md,rendering error
@@ -888,6 +1056,7 @@ translations/es-ES/content/rest/reference/search.md,rendering error
translations/es-ES/content/rest/reference/secret-scanning.md,rendering error
translations/es-ES/content/rest/reference/teams.md,rendering error
translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error
+translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error
translations/es-ES/content/search-github/searching-on-github/searching-code.md,Listed in localization-support#489
translations/es-ES/content/search-github/searching-on-github/searching-code.md,rendering error
@@ -905,4 +1074,25 @@ translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponso
translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,rendering error
translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md,rendering error
translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md,rendering error
+translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags
+translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags
+translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken liquid tags
+translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
+translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags
+translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
+translations/es-ES/data/reusables/code-scanning/edit-workflow.md,broken liquid tags
+translations/es-ES/data/reusables/code-scanning/enabling-options.md,broken liquid tags
+translations/es-ES/data/reusables/code-scanning/licensing-note.md,broken liquid tags
+translations/es-ES/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
+translations/es-ES/data/reusables/dependabot/dependabot-tos.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_installation/download-appliance.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
+translations/es-ES/data/reusables/getting-started/marketplace.md,broken liquid tags
+translations/es-ES/data/reusables/github-actions/contacting-support.md,broken liquid tags
+translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md,broken liquid tags
+translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md,broken liquid tags
translations/es-ES/data/reusables/package_registry/authenticate-packages.md,Listed in localization-support#489
+translations/es-ES/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
+translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags
+translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md,broken liquid tags
+translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md,broken liquid tags
|