Merge branch 'main' into openapi-update-de74b35d04927e8cfa61a450650d952528b0f905c2e0b860f3444f7b82dc45fe

translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md

@@ -66,7 +66,7 @@ El README de tu perfil se eliminará de tu perfil de {% data variables.product.p
 - El repositorio es privado.
 - El nombre del repositorio no empata con tu nombre de usuario.
 
-The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
+The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. Para encontrar los pasos de cómo hacer tu repositorio privado, consulta la sección "[Cambiar la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)".
 
 ## Leer más
 

translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md

@@ -35,7 +35,7 @@ Puede que quieras utilizar un tema oscuro para reducir el consumo de energía en
       {%- ifversion ghes = 3.5 %}
       {% note %}
 
-      **Note**: The light high contrast theme is unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme will be available in an upcoming patch release. For more information about upgrades, contact your site administrator.
+      **Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
 
       For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of  {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
       {% endnote %}

translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md

@@ -433,7 +433,7 @@ runs:
 
 Para obtener más información acerca de cómo se ejecuta el `entrypoint`, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)".
 
-### `post-entrypoint`
+### `runs.post-entrypoint`
 
 **Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `post-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes anular esto utilizando [`runs.post-if`](#runspost-if).
 
@@ -475,7 +475,7 @@ runs:
 
 ## `branding`
 
-Puedes usar un color y un icono de [Pluma](https://feathericons.com/) para crear una insignia que personalice y diferencie tu acción. Los distintivos se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+**Opcional** puedes utilizar un color e icono de [Pluma](https://feathericons.com/) para crear una insignia para personalizar y distinguir tu acción. Los distintivos se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
 ### Ejemplo: Configurar la personalización de una acción
 

translations/es-ES/content/actions/learn-github-actions/contexts.md

@@ -470,6 +470,8 @@ The `runner` context contains information about the runner that is executing the
 | `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
 | `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
 | `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
+| `runner.debug` | `string` | {% data reusables.actions.runner-debug-description %} |
+
 {%- comment %}
 The `runner.workspace` property is purposefully not documented. It is an early Actions property that now isn't relevant for users, compared to `github.workspace`. It is kept around for compatibility.
 | `runner.workspace` | `string` | |

translations/es-ES/content/actions/learn-github-actions/environment-variables.md

@@ -165,6 +165,7 @@ We strongly recommend that actions use environment variables to access the files
 {%- ifversion actions-runner-arch-envvars %}
 | `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}
 {%- endif %} |
+| `RUNNER_DEBUG` | {% data reusables.actions.runner-debug-description %} |
 | `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} For example, `Hosted Agent` |
 | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} For example, `Windows` |
 | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} For example, `D:\a\_temp` |

translations/es-ES/content/actions/learn-github-actions/expressions.md

@@ -125,45 +125,53 @@ env:
 
 Arroja `true` si `search` contiene `item`. Si `search` es una matriz, esta función arroja `true` si el `item` es un elemento de la matriz. Si `search` es una cadena, esta función arroja `true` si el `item` es una subcadena de `search`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
 
-#### Ejemplo usando una matriz
-
-`contains(github.event.issue.labels.*.name, 'bug')` devuelve la información de si la propuesta que está relacionada al evento tiene una etiqueta de "bug" o no.
-
 #### Ejemplo usando una cadena
 
-`contains('Hello world', 'llo')` devuelve `verdadero`.
+`contains('Hello world', 'llo')` arroja `true`.
+
+#### Example using an object filter
+
+`contains(github.event.issue.labels.*.name, 'bug')` returns `true` if the issue related to the event has a label "bug".
+
+For more information, see "[Object filters](#object-filters)."
+
+#### Example matching an array of strings
+
+Instead of writing `github.event_name == "push" || github.event_name == "pull_request"`, you can use `contains()` with `fromJson()` to check if an array of strings contains an `item`.
+
+For example, `contains(fromJson('["push", "pull_request"]'), github.event_name)` returns `true` if `github.event_name` is "push" or "pull_request".
 
 ### startsWith
 
 `startsWith( searchString, searchValue )`
 
-Arroja `true` cuando `searchString` empieza con `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
+Devuelve `verdadero` cuando `searchString` contiene `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
 
 #### Ejemplo
 
-`startsWith('Hello world', 'He')` regresa a `verdadero`.
+`startsWith('Hello world', 'He')` arroja `true`.
 
 ### endsWith
 
 `endsWith( searchString, searchValue )`
 
-Arroja `true` si `searchString` termina con `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
+Devuelve `verdadero` si `searchString` contiene `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
 
 #### Ejemplo
 
-`endsWith('Hello world', 'He')` devuelve `verdadero`.
+`endsWith('Hello world', 'ld')` arroja `true`.
 
 ### format
 
 `format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
 
-Reemplaza valores en la `string`, con la variable `replaceValueN`. Las variables en la `string` se especifican con la sintaxis `{N}`, donde `N` es un entero. Debes especificar al menos un `replaceValue` y una `string`. No existe un máximo para el número de variables (`replaceValueN`) que puedes usar. Escapar las llaves utilizando llaves dobles.
+Reemplaza valores en la `cadena`, con la variable `replaceValueN`. Las variables en la `cadena` se especifican con la sintaxis `{N}`, donde `N` es un entero. Debes especificar al menos un `replaceValue` y una `cadena`. No existe un máximo para el número de variables (`replaceValueN`) que puedes usar. Escapar las llaves utilizando llaves dobles.
 
 #### Ejemplo
 
 `format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')`
 
-Devuelve 'Hello Mona the Octocat'.
+Arroja 'Hello Mona the Octocat'.
 
 #### Ejemplo de evasión de llaves
 
@@ -221,7 +229,7 @@ jobs:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
-      matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
+      matrix: ${{ fromJSON(needs.job1.outputs.matrix) }}
     steps:
       - run: build
 ```
@@ -235,7 +243,7 @@ Este flujo de trabajo utiliza `fromJSON` para convertir las variables de ambient
 ```yaml
 name: print
 on: push
-env: 
+env:
   continue: true
   time: 3
 jobs:
@@ -272,10 +280,10 @@ Crea un hash para cualquier archivo de `package-lock.json` y de `Gemfile.lock` e
 {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 ## Funciones de verificación del estado
 
-Puedes usar las siguientes funciones de verificación de estado como expresiones en condicionales `if` (si). Se aplicará una verificación de estado predeterminado de `success()` a menos de que incluyas una de estas funciones. Para obtener más información sobre los condicionales `if`, consulta la sección "[Sintaxis de flujo de trabajo para las GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" y "[Sintaxis de metadatos para las Acciones Compuestas de GitHub](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
+Puedes usar las siguientes funciones de verificación de estado como expresiones en condicionales `if`. Se aplicará una verificación de estado predeterminado de `success()` a menos de que incluyas una de estas funciones. Para obtener más información sobre los condicionales `if`, consulta la sección "[Sintaxis de flujo de trabajo para las GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" y "[Sintaxis de metadatos para las Acciones Compuestas de GitHub](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
 {% else %}
 ## Funciones de verificación
-Puedes usar las siguientes funciones de verificación de estado como expresiones en condicionales `if` (si). Se aplicará una verificación de estado predeterminado de `success()` a menos de que incluyas una de estas funciones. Para obtener más información sobre los condicionales `if`, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
+Puedes usar las siguientes funciones de verificación de estado como expresiones en condicionales `if`. Se aplicará una verificación de estado predeterminado de `success()` a menos de que incluyas una de estas funciones. Para obtener más información sobre los condicionales `if`, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
 {% endif %}
 
 ### success
@@ -303,7 +311,7 @@ if: {% raw %}${{ always() }}{% endraw %}
 
 ### cancelled
 
-Devuelve `verdadero` si se canceló el flujo de trabajo.
+Arroja `true` si se canceló el flujo de trabajo.
 
 #### Ejemplo
 
@@ -354,7 +362,7 @@ Por ejemplo, considera una matriz de objetos llamada `fruits`.
 ]
 ```
 
-El filtro `fruits.*.name` devuelve la matriz `[ "apple", "orange", "pear" ]`.
+El filtro `fruits.*.name` arroja la matriz `[ "apple", "orange", "pear" ]`.
 
 También puedes utilizar la sintaxis `*` en un objeto. Por ejemplo, supón que tienes un objeto que se llama `vegetables`.
 

translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md

@@ -121,7 +121,7 @@ jobs:
             {% raw %}${{ runner.os }}-build-{% endraw %}
             {% raw %}${{ runner.os }}-{% endraw %}
 
-      - if: {% raw %}${{ steps.cache-npm.outputs.cache-hit == 'false' }}{% endraw %}
+      - if: {% raw %}${{ steps.cache-npm.outputs.cache-hit != 'true' }}{% endraw %}
         name: List the state of node modules
         continue-on-error: true
         run: npm list
@@ -172,12 +172,12 @@ npm-d5ea0750
 
 ### Utilizar la salida de la acción `cache`
 
-Puedes utilizar la salida de la acción `cache` para hacer algo con base en si se suscita una ocurrencia u omisión en caché. Si se suscita una omisión en caché (no se encontró una coincidencia exacta para un caché en la `key` especificada), la salida `cache-hit` se configura en `false`.
+Puedes utilizar la salida de la acción `cache` para hacer algo con base en si se suscita una ocurrencia u omisión en caché. When an exact match is found for a cache for the specified `key`, the `cache-hit` output is set to `true`.
 
 En el flujo de trabajo del ejemplo anterior, hay un paso que lista el estado de los módulos de nodo si se suscitó una omisión de caché:
 
 ```yaml
-- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit == 'false' }}{% endraw %}
+- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit != 'true' }}{% endraw %}
   name: List the state of node modules
   continue-on-error: true
   run: npm list

translations/es-ES/content/admin/configuration/configuring-your-enterprise/deploying-github-ae.md

@@ -20,9 +20,7 @@ After you purchase or start a trial of {% data variables.product.product_name %}
 
 ## Prerequisites
 
-- Before you can deploy {% data variables.product.product_name %}, you must request access from your {% data variables.product.company_short %} account team. {% data variables.product.company_short %} will enable deployment of {% data variables.product.product_name %} for your Azure subscription. If you haven't already purchased {% data variables.product.product_name %}, you can contact {% data variables.contact.contact_enterprise_sales %} to check your eligibility for a trial.
-
-- You must have permission to perform the `/register/action` operation for the resource provider in Azure. The permission is included in the `Contributor` and `Owner` roles. For more information, see [Azure resource providers and types](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in the Microsoft documentation.
+You must have permission to perform the `/register/action` operation for the resource provider in Azure. The permission is included in the `Contributor` and `Owner` roles. For more information, see [Azure resource providers and types](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in the Microsoft documentation.
 
 ## Deploying {% data variables.product.product_name %} with the {% data variables.actions.azure_portal %}
 

translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md

@@ -173,19 +173,28 @@ Si programas mucho trabajo para actualizar una dependencias o decides que una al
 
 ## Ver y actualziar las alertas cerradas
 
-{% tip %}
-
-**Tip:** Solo puedes volver a abrir alertas que se hayan descartado previamente. Las alertas cerradas que ya se hayan corregido no se pueden volver a abrir.
-{% endtip %}
+You can view all open alerts, and you can reopen alerts that have been previously dismissed. Las alertas cerradas que ya se hayan corregido no se pueden volver a abrir.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
-1. Para solo ver las alertas cerradas, haz clic en **Cerrada**.{% ifversion dependabot-bulk-alerts %} ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed-checkbox.png){% else %}
-![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed.png){% endif %}
-1. Haz clic en la alerta que te gustaría ver o actualizar.{% ifversion dependabot-bulk-alerts %} ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png){% else %}
-![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert.png){% endif %}
-2. Opcionalmente, si se descartó la alerta y quieres volver a abrirla, haz clic en **Reabrir**. Las alertas que ya se hayan corregido no pueden volverse a abrir. ![Captura de pantalla que muestra el botón "Reabrir"](/assets/images/help/repository/reopen-dismissed-alert.png)
+1. To just view closed alerts, click **Closed**.
+
+   {%- ifversion dependabot-bulk-alerts %}
+   ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed-checkbox.png)
+   {%- else %}
+   ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed.png)
+   {%- endif %}
+1. Click the alert that you would like to view or update.
+
+   {%- ifversion dependabot-bulk-alerts %}
+   ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png)
+   {%- else %}
+   ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert.png)   {%- endif %}
+2. Opcionalmente, si se descartó la alerta y quieres volver a abrirla, haz clic en **Reabrir**. Las alertas que ya se hayan corregido no pueden volverse a abrir.
+
+   {% indented_data_reference reusables.enterprise.3-5-missing-feature spaces=3 %}
+   ![Captura de pantalla que muestra el botón "Reabrir"](/assets/images/help/repository/reopen-dismissed-alert.png)
 
 {% endif %}
 

translations/es-ES/content/codespaces/developing-in-codespaces/index.md

@@ -13,6 +13,7 @@ children:
   - /developing-in-a-codespace
   - /using-source-control-in-your-codespace
   - /using-github-codespaces-for-pull-requests
+  - /renaming-a-codespace
   - /deleting-a-codespace
   - /forwarding-ports-in-your-codespace
   - /default-environment-variables-for-your-codespace

translations/es-ES/content/codespaces/developing-in-codespaces/renaming-a-codespace.md

@@ -0,0 +1,54 @@
+---
+title: Renaming a codespace
+intro: 'You can use the {% data variables.product.prodname_cli %} to change the codespace display name to one of your choice.'
+product: '{% data reusables.gated-features.codespaces %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Rename a codespace
+---
+
+## About renaming a codespace
+
+Each codespace is assigned an auto-generated display name. If you have multiple codespaces, the display name helps you to differentiate between codespaces. For example: `literate space parakeet`. You can change the display name for your codespace.
+
+To find the display name of a codespace:
+
+- On {% data variables.product.product_name %}, view your list of codespaces at https://github.com/codespaces.
+
+  ![Screenshot of the list of codespaces in GitHub](/assets/images/help/codespaces/codespaces-list-display-name.png)
+
+- In the {% data variables.product.prodname_vscode %} desktop application, or the {% data variables.product.prodname_vscode_shortname %} web client, click the Remote Explorer. The display name is shown below the repository name. For example: `symmetrical space telegram` in the screenshot below.
+
+  ![Screenshot of the Remote Explorer in VS Code](/assets/images/help/codespaces/codespaces-remote-explorer.png)
+
+- In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`.
+### Permanent codespace names
+
+In addition to the display name, when you create a codespace, a permanent name is also assigned to the codespace. The name is a combination of your {% data variables.product.company_short %} handle, the repository name, and some random characters. Por ejemplo: `octocat-myrepo-gmc7`. You can't change this name.
+
+To find the permanent name of a codespace:
+
+* On {% data variables.product.product_name %}, the permanent name is shown in a pop-up when you hover over the **Open in browser** option on https://github.com/codespaces.
+
+   ![Screenshot of the codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png)
+
+* In a codespace, use this command in the terminal: `echo $CODESPACE_NAME`.
+* In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`.
+
+## Renaming a codespace
+
+Changing the display name of a codespace can be useful if you have multiple codespaces that you will be using for an extended period. An appropriate name helps you identify a codespace that you use for a particular purpose. You can change the display name for your codespace by using the {% data variables.product.prodname_cli %}.
+
+To rename a codespace, use the `gh codespace edit` subcommand:
+
+```shell
+gh codespace edit -c <em>permanent name of the codespace</em> -d <em>new display name</em>
+```
+
+In this example, replace `permanent name of the codespace` with the permanent name of the codespace. Replace `new display name` with the desired display name.

translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md

@@ -26,7 +26,7 @@ topics:
 Puedes crear enlaces en wikis usando el markup estándar admitido por tu página, o usando la sintaxis MediaWiki. Por ejemplo:
 
 - Si tus páginas se presentan con Markdown, la sintaxis del enlace es `[Link Text](full-URL-of-wiki-page)`.
-- With MediaWiki syntax, the link syntax is `[[nameofwikipage|Link Text]]`.
+- Con sintaxis de MediaWiki, la sintaxis del enlace es `[[nameofwikipage|Link Text]]`.
 
 ## Agregar imágenes
 

translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts.md

@@ -12,4 +12,4 @@ versions:
 
 Aprende habilidades comunicativas en público, escritura técnica, liderazgo comunitario y habilidades de desarrollo de software como un Experto en campus de {% data variables.product.prodname_dotcom %}.
 
-To learn more about training programs for student leaders, see "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)."
+Para aprender más sobre los programas de capacitación para los alumnos líderes, consulta la sección de "[Expertos del campus de {% data variables.product.prodname_dotcom %}](https://education.github.com/students/experts)".

translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md

@@ -17,7 +17,7 @@ El {% data variables.product.prodname_campus_program %} es un paquete de acceso
 
 - Acceso sin costo a {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} para todos tus departamentos técnicos y académicos
 - 50,000 minutos de {% data variables.product.prodname_actions %} y 50 GB de almacenamiento de {% data variables.product.prodname_registry %}
-- Teacher training to master Git and {% data variables.product.prodname_dotcom %}
+- Capacitación para docentes para dominar Git y {% data variables.product.prodname_dotcom %}
 - Acceso exclusivo a las características nuevas, swag específico de la Educación de GitHub y herramientas de desarrollo gratuitas de los socios de {% data variables.product.prodname_dotcom %}
 - Acceso automatizado a las funciones premium de {% data variables.product.prodname_education %}, como {% data variables.product.prodname_student_pack %}
 

translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md

@@ -100,5 +100,5 @@ La tarea inicial de Git & {% data variables.product.company_short %} solo se enc
 
 ## Leer más
 
-- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
+- "[{% data variables.product.prodname_global_campus %} para docentes](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
 - "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"

translations/es-ES/content/education/quickstart.md

@@ -15,7 +15,7 @@ En esta guía, iniciarás con {% data variables.product.product_name %}, regíst
 
 {% tip %}
 
-**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Apply to {% data variables.product.prodname_global_campus %} as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)."
+**Tip**: Si eres un alumno y te gustaría sacar provecho de un descuento académico, consulta cómo "[Aplicar para ingresar al {% data variables.product.prodname_global_campus %} como alumno](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)".
 
 {% endtip %}
 
@@ -35,9 +35,9 @@ Después de crear tu cuenta personal, crea una cuenta gratuita de organización.
 
 Para obtener más información, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)".
 
-## Applying for teacher benefits
+## Aplicar para obtener beneficios de docente
 
-Next, you'll sign up for teacher benefits and resources from {% data variables.product.company_short %} by applying to {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits all in one place.  {% data reusables.education.educator-requirements %}
+Luego, deberás registrarte para obtener los beneficios de docente y los recursos de {% data variables.product.company_short %} enviando la solicitud para ingresar en el {% data variables.product.prodname_global_campus %}, un portal que te permite acceder a tus beneficios educativos, todo en un solo lugar.  {% data reusables.education.educator-requirements %}
 
 {% tip %}
 
@@ -53,7 +53,7 @@ Next, you'll sign up for teacher benefits and resources from {% data variables.p
 {% data reusables.education.plan-to-use-github %}
 {% data reusables.education.submit-application %}
 
-Once you are a verified {% data variables.product.prodname_global_campus %} educator, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com).
+Una vez que seas un docente verificado del {% data variables.product.prodname_global_campus %}, podrás acceder en cualquier momento al {% data variables.product.prodname_global_campus %} si te diriges al [sitio web de {% data variables.product.prodname_education %}](https://education.github.com).
 
 ## Configura {% data variables.product.prodname_classroom %}
 

translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md

@@ -31,6 +31,8 @@ Tipos de tableros de proyecto:
 
 Para crear un {% data variables.projects.projects_v1_board %} de organización, debes ser miembro de ella. Los propietarios de las organizaciones y las personas con permisos administrativos de {% data variables.projects.projects_v1_board %} pueden personalizar el acceso al {% data variables.projects.projects_v1_board %}.
 
+{% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %}
+
 Si un {% data variables.projects.projects_v1_board %} perteneciente a una organización incluye propuestas o solicitudes de cambio de un repositorio en el cual no tienes permisos de visualización, la tarjeta se redactará.  Para obtener más información, consulta la sección "[Permisos de los {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)".
 
 La vista de actividad muestra el historial reciente del {% data variables.projects.projects_v1_board %}, tal como las tarjetas que haya creado alguien o movido entre columnas. Para acceder a la vista actividad, haz clic en **Menú** y desplázate hacia abajo.

translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md

@@ -17,11 +17,14 @@ allowTitleToDifferFromFilename: true
 
 {% data reusables.project-management.project-board-visibility %}
 
-{% tip %}
+{% note %}
 
-**Tip:** Cuando hagas a tu {% data variables.projects.projects_v1_board %} {% ifversion ghae %}interno{% else %}público{% endif %}, los miembros de la organización obtendrán acceso de lectura predeterminadamente. Puedes otorgar permisos de escritura o administración a miembros específicos de la organización si les das acceso a los equipos en los que se encuentran, agregándolos al {% data variables.projects.projects_v1_board %} como colaborador. Para obtener más información, consulta la sección "[Permisos de los {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)".
+**{% ifversion classic-project-visibility-permissions %}Notes{% else %}Note{% endif %}:** {% ifversion classic-project-visibility-permissions %}
 
-{% endtip %}
+* {% data reusables.projects.owners-can-limit-visibility-permissions %}
+* {% endif %}When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. Puedes otorgar permisos de escritura o administración a miembros específicos de la organización si les das acceso a los equipos en los que se encuentran, agregándolos al {% data variables.projects.projects_v1_board %} como colaborador. Para obtener más información, consulta la sección "[Permisos de los {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)".
+
+{% endnote %}
 
 1. Navega al tablero del proyecto que quieres hacer {% ifversion ghae %}interno{% else %}público{% endif %} o privado.
 {% data reusables.project-management.click-menu %}

translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md

@@ -57,6 +57,14 @@ También puedes configurar automatizaciones de flujo de trabajo para mantener si
 
 {% data reusables.projects.classic-project-creation %}
 
+{% ifversion classic-project-visibility-permissions %}
+{% note %}
+
+**Nota:** {% data reusables.projects.owners-can-limit-visibility-permissions %}
+
+{% endnote %}
+{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}

translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md

@@ -39,6 +39,8 @@ Por ejemplo, si un propietario de organización ha otorgado a permisos de lectur
 
 ## Visibilidad de {% data variables.projects.projects_v1_board_caps %}
 
+{% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %}
+
 {% data reusables.project-management.project-board-visibility %} Puedes cambiar la visibilidad del {% data variables.projects.projects_v1_board %} de privado a {% ifversion ghae %}interno{% else %}público{% endif %} y de vuelta. Para obtener más información, consulta la sección "[Cambiar la visibilidad de un {% data variables.product.prodname_project_v1 %}](/articles/changing-project-board-visibility)".
 
 ## Leer más

translations/es-ES/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md

@@ -1,19 +1,19 @@
 ---
 title: Permitir los cambios de visibilidad de proyecto en tu organización
-intro: Organization owners can allow members with admin permissions to adjust the visibility of projects in their organization.
+intro: 'Organization owners can allow members with admin permissions to adjust the visibility of {% data variables.projects.projects_v2_and_v1 %} in their organization.'
 versions:
-  feature: projects-v2
+  feature: classic-project-visibility-permissions-or-projects-v2
 topics:
   - Organizations
   - Projects
 shortTitle: Project visibility permissions
 allowTitleToDifferFromFilename: true
-permissions: Organization owners can allow project visibility changes for an organization.
+permissions: 'Organization owners can allow {% data variables.projects.project_v2_and_v1 %} visibility changes for an organization.'
 ---
 
-You can restrict who has the ability to change the visibility of projects in your organization, such as restricting members from changing a project from private to public.
+You can restrict who has the ability to change the visibility of {% data variables.projects.projects_v2_and_v1 %} in your organization, such as restricting members from changing {% data variables.projects.projects_v2_and_v1 %} from private to public.
 
-You can limit the ability to change project visibility to just organization owners, or you can allow anyone with admin permissions on a project to change the visibility.
+You can limit the ability to change {% data variables.projects.project_v2_and_v1 %} visibility to just organization owners, or you can allow anyone granted admin permissions to change the visibility.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -23,4 +23,8 @@ You can limit the ability to change project visibility to just organization owne
 
 ## Leer más
 
-- "[Managing visibility of your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)"
+{% ifversion projects-v2 %}
+- "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)"
+{%- endif %}{%- ifversion projects-v1 %}
+- "[Cambiar la visibilidad de un {% data variables.product.prodname_project_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)"
+{% endif %}

translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md

@@ -232,6 +232,8 @@ Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not s
 
 If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
 
+If you're using a `GITHUB_TOKEN` to authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, the token cannot access private repository-based packages in a different repository other than where the workflow is running in. To access packages associated with other repositories, instead generate a PAT with the `read:packages` scope and pass this token in as a secret.
+ 
 ## Further reading
 
 - "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"

translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md

@@ -15,22 +15,36 @@ versions:
 topics:
   - Pull requests
 ---
+## Merge your commits
+
 {% data reusables.pull_requests.default_merge_option %}
 
-## Squash and merge your pull request commits
+## Squash and merge your commits
 
 {% data reusables.pull_requests.squash_and_merge_summary %}
 
 ### Merge message for a squash merge
 
+{% ifversion default-merge-squash-commit-message %}
+When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. Depending on how the repository is configured and the number of commits in the pull request, not including merge commits, this message may include the pull request title, pull request description, or information about the commits.
+{% else %}
 When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits.
 
+Number of commits | Summary | Description |
+----------------- | ------- | ----------- |	
+One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
+More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order
+{% endif %}
+
 Number of commits | Summary | Description |
 ----------------- | ------- | ----------- |
 One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
 More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order
 
-{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}
+{% ifversion default-merge-squash-commit-message %}
+People with maintainer or admin access to a repository can configure their repository's default merge message for all squashed commits to use the pull request title, the pull request title and commit details, or the pull request title and description. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".{% endif %}
+
+{% ifversion ghes = 3.6 %}
 People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".
 {% endif %}
 
@@ -42,7 +56,7 @@ When you create a pull request, {% data variables.product.prodname_dotcom %} ide
 
 Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly.
 
-## Rebase and merge your pull request commits
+## Rebase and merge your commits
 
 {% data reusables.pull_requests.rebase_and_merge_summary %}
 

translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md

@@ -0,0 +1,30 @@
+---
+title: Configuring commit merging for pull requests
+intro: 'You can enforce, allow, or disable merging with a merge commit for all pull request merges on {% data variables.product.product_location %} in your repository.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Configure commit merging
+---
+
+{% data reusables.pull_requests.configure_pull_request_merges_intro %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.{% ifversion default-merge-squash-commit-message %} ![Screenshot of Pull Request settings with allow merge commits checkbox emphasized](/assets/images/help/repository/allow-merge-commits.png){% endif %}{% ifversion ghes = 3.6 %} ![Screenshot of Pull Request settings with allow merge commits checkbox emphasized](/assets/images/help/repository/allow-merge-commits-no-dropdown.png){% endif %}
+{% ifversion ghes < 3.6  %}
+ ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png){% endif %}
+{% ifversion default-merge-squash-commit-message %}
+1. Optionally, under **Allow merge commits**, use the dropdown to choose the format of the commit message presented to contributors when merging. The default message includes the pull request number and title. For example, `Merge pull request #123 from patch-1`. You can also choose to use just the pull request title, or the pull request title and description. ![Screenshot of emphasized default commit message dropdown](/assets/images/help/repository/default-commit-message-dropdown.png)
+{% endif %}
+
+Si seleccionas más de un método de fusión, los colaboradores pueden elegir qué tipo de confirmación de fusión utilizar cuando fusionan una solicitud de cambios. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
+
+## Leer más
+
+- "[Acerca de las fusiones de solicitudes de extracción](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- "[Fusionar una solicitud de extracción](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)"

translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md

@@ -19,4 +19,10 @@ shortTitle: Configurar el rebase de confirmaciones
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Debajo de {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Solicitudes de cambios"{% else %}"Botón de fusión"{% endif %}, selecciona **Permitir la fusión por rebase**. Esto permite que los colaboradores fusionen una solicitud de extracción al rebasar sus confirmaciones individuales en la rama base. Si también seleccionas otro método de fusión, los colaboradores podrán elegir el tipo de confirmación de fusión al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones de rebase de solicitudes de extracción](/assets/images/help/repository/pr-merge-rebase.png)
+3. Debajo de {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6069 %}"Solicitudes de cambios"{% else %}"Botón de fusión"{% endif %}, selecciona **Permitir la fusión por rebase**. Esto permite que los colaboradores fusionen una solicitud de extracción al rebasar sus confirmaciones individuales en la rama base.
+{% ifversion default-merge-squash-commit-message %}
+ ![Screenshot of Pull Request settings with allow rebase merging checkbox emphasized](/assets/images/help/repository/allow-rebase-merging.png){% endif %}{% ifversion ghes = 3.6  %} ![Screenshot of Pull Request settings with allow rebase merging checkbox emphasized](/assets/images/help/repository/allow-rebase-merging-no-dropdown.png){% endif %}
+ {% ifversion ghes < 3.6  %}
+ ![Confirmaciones de rebase de solicitudes de extracción](/assets/images/help/repository/pr-merge-rebase.png){% endif %}
+
+Si también seleccionas otro método de fusión, los colaboradores podrán elegir el tipo de confirmación de fusión al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}

translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md

@@ -20,13 +20,17 @@ shortTitle: Configure commit squashing
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, optionally select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.
-![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The squash message automatically defaults to the title of the pull request if it contains more than one commit. {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}If you want to use the title of the pull request as the default merge message for all squashed commits, regardless of the number of commits in the pull request, select **Default to PR title for squash merge commits**. 
-![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png){% else %}
-![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %}
+1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The default commit message presented to contributors when merging is the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. {% ifversion ghes = 3.6 %} To always use the title of the pull request regardless of the number of commits in the pull request select **Default to PR title for squash merge commits**.{% endif %}{% ifversion default-merge-squash-commit-message %} 
+ ![Pull request squashed commits](/assets/images/help/repository/allow-squash-merging.png){% endif %}{% ifversion ghes = 3.6 %}
+ ![Screenshot of Pull Request settings with allow merge commits checkbox emphasized](/assets/images/help/repository/allow-squash-merging-no-dropdown.png){% endif %}
+{% ifversion ghes < 3.6  %}
+ ![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %}
+{% ifversion default-merge-squash-commit-message %}
+1. Optionally, under **Allow squash merging**, use the dropdown to choose the format of the default squash commit message presented to contributors when merging. The default message uses the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. You can also choose to use just the pull request title, the pull request title and commit details, or the pull request title and description.
+![Screenshot of emphasized default squash message dropdown](/assets/images/help/repository/default-squash-message-dropdown.png)
+{% endif %}
 
-If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
+If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
 
 ## Further reading
 

translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md

@@ -13,6 +13,7 @@ topics:
   - Repositories
 children:
   - /about-merge-methods-on-github
+  - /configuring-commit-merging-for-pull-requests
   - /configuring-commit-squashing-for-pull-requests
   - /configuring-commit-rebasing-for-pull-requests
   - /managing-a-merge-queue

translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md

@@ -22,7 +22,7 @@ shortTitle: Agregar un archivo
 
 ## Agregar un archivo a un repositorio en {% data variables.product.product_name %}
 
-Los archivos que agregues a un repositorio mediante un navegador están limitados a {% data variables.large_files.max_github_browser_size %} por archivo. Puedes agregar archivos más grandes, de hasta {% data variables.large_files.max_github_size %} cada uno, mediante la línea de comando. Para obtener más información, consulta "[Agregar un archivo a un repositorio mediante la línea de comando](#adding-a-file-to-a-repository-using-the-command-line)". To add files larger than {% data variables.large_files.max_github_size %}, you must use {% data variables.large_files.product_name_long %}. For more information, see "[About large files on {% data variables.product.product_name %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github)."
+Los archivos que agregues a un repositorio mediante un navegador están limitados a {% data variables.large_files.max_github_browser_size %} por archivo. Puedes agregar archivos más grandes, de hasta {% data variables.large_files.max_github_size %} cada uno, mediante la línea de comando. Para obtener más información, consulta "[Agregar un archivo a un repositorio mediante la línea de comando](#adding-a-file-to-a-repository-using-the-command-line)". Para agregar archivos mayores a {% data variables.large_files.max_github_size %}, debes utilizar {% data variables.large_files.product_name_long %}. Para obtener más información, consulta la sección "[Acerca de los archivos grandes en {% data variables.product.product_name %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github)".
 
 {% tip %}
 

translations/es-ES/data/features/classic-project-visibility-permissions-or-projects-v2.yml

@@ -0,0 +1,7 @@
+#Issue 7720
+#Organization owners can restrict public classic projects /OR/ Projects V2
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7720'

translations/es-ES/data/features/classic-project-visibility-permissions.yml

@@ -0,0 +1,7 @@
+#Issue 7720
+#Organization owners can restrict public classic projects.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7720'

translations/es-ES/data/features/default-merge-squash-commit-message.yml

@@ -0,0 +1,7 @@
+#Reference: issue #7597
+#Admin can control default PR merge/ squash commit messages
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7597'

translations/es-ES/data/release-notes/enterprise-server/3-2/17.yml

@@ -0,0 +1,9 @@
+date: '2022-08-11'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+    - |
+      **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).
+  bugs:
+    - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."

translations/es-ES/data/release-notes/enterprise-server/3-3/12.yml

@@ -0,0 +1,11 @@
+date: '2022-08-11'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+    - |
+      **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).
+  bugs:
+    - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+  changes:
+    - 'The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."'

translations/es-ES/data/release-notes/enterprise-server/3-4/7.yml

@@ -0,0 +1,14 @@
+date: '2022-08-11'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+    - |
+      **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).
+  bugs:
+    - In some cases, GitHub Enterprise Server instances on AWS that used the `r4.4xlarge` instance type would fail to boot.
+    - 'When calculating committers for GitHub Advanced Security, it was not possible to specify individual repositories. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."'
+    - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+  changes:
+    - '`pre_receive_hook.rejected_push` events were not displayed in the enterprise audit log.'
+    - Both migration archives for repositories and archive exports for user accounts include release reactions.

translations/es-ES/data/release-notes/enterprise-server/3-5/0.yml

@@ -117,7 +117,7 @@ sections:
       notes:
         - |
           The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
-            - **Note**: This feature is unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature will be available in an upcoming patch release. [Updated: 2022-08-16]
+            - **Note**: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. [Updated: 2022-08-16]
     - 
       heading: El resumen de seguridad para empresas está en beta público
       notes:
@@ -202,7 +202,7 @@ sections:
       notes:
         - |
           You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
-            - **Note**: This feature is unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature will be available in an upcoming patch release. [Updated: 2022-08-16]
+            - **Note**: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. [Updated: 2022-08-16]
     - 
       heading: La compatibilidad de Pub para las actualizaciones de versión del Dependabot se encuentra en beta público
       notes:
@@ -267,7 +267,7 @@ sections:
           - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
 
           - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)."
-            - **Note**: This feature is unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature will be available in an upcoming patch release. [Updated: 2022-08-16]
+            - **Note**: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. [Updated: 2022-08-16]
     - 
       heading: Configurar los encabezados personalizados de HTTP para los sitios de GitHub Pages
       notes:
@@ -283,7 +283,7 @@ sections:
       notes:
         - |
           A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
-            - **Note**: This feature is unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature will be available in an upcoming patch release. [Updated: 2022-08-16]
+            - **Note**: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. [Updated: 2022-08-16]
     - 
       heading: Reglas de protección de etiquetas
       notes:
@@ -352,7 +352,7 @@ sections:
     - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. This issue is resolved in the 3.5.1 patch release. [Updated: 2022-06-10]'
     - 'La consola de administración podría haberse mostrado atascada en la pantalla de _Starting_ después de mejorar una instancia subaprovisionada para GitHub Enterprise Server 3.5. [Actualizado: 2022-06-20]'
     - |
-      The following features are unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features will be available in an upcoming patch release. [Updated: 2022-08-16]
+      The following features were unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features are available in 3.5.4 and later. [Updated: 2022-08-16]
 
       - Detection of GitHub Actions workflow files for the dependency graph
       - Reopening of dismissed Dependabot alerts

translations/es-ES/data/release-notes/enterprise-server/3-5/1.yml

@@ -32,7 +32,7 @@ sections:
     - 'Los repositorios borrados no se purgarán del disco automáticamente después de que finalice el periodo de retención de 90 días. Esta propuesta se resolvió en el lanzamiento 3.5.1. [Actualizado: 2022-06-10]'
     - 'La consola de administración podría haberse mostrado atascada en la pantalla de _Starting_ después de mejorar una instancia subaprovisionada para GitHub Enterprise Server 3.5. [Actualizado: 2022-06-20]'
     - |
-      The following features are unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features will be available in an upcoming patch release. [Updated: 2022-08-16]
+      The following features were unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features are available in 3.5.4 and later. [Updated: 2022-08-16]
 
       - Detection of GitHub Actions workflow files for the dependency graph
       - Reopening of dismissed Dependabot alerts

translations/es-ES/data/release-notes/enterprise-server/3-5/2.yml

@@ -33,7 +33,7 @@ sections:
     - 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.
     - Los servicios de las acciones necesitan reiniciarse después de restablecer un aplicativo de un respaldo que se llevó a un host diferente.
     - |
-      The following features are unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features will be available in an upcoming patch release. [Updated: 2022-08-16]
+      The following features were unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features are available in 3.5.4 and later. [Updated: 2022-08-16]
 
       - Detection of GitHub Actions workflow files for the dependency graph
       - Reopening of dismissed Dependabot alerts

translations/es-ES/data/release-notes/enterprise-server/3-5/3.yml

@@ -30,5 +30,5 @@ sections:
     - '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.'
     - 'Los servicios de las acciones necesitan reiniciarse después de restablecer un aplicativo de un respaldo que se llevó a un host diferente.'
-    - "The following features are unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features will be available in an upcoming patch release. [Updated: 2022-08-16]\n\n- Detection of GitHub Actions workflow files for the dependency graph\n- Reopening of dismissed Dependabot alerts\n- Enabling the **Update branch** button for all pull requests in a repository\n- Light high contrast theme\n"
+    - "The following features were unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features are available in 3.5.4 and later. [Updated: 2022-08-16]\n\n- Detection of GitHub Actions workflow files for the dependency graph\n- Reopening of dismissed Dependabot alerts\n- Enabling the **Update branch** button for all pull requests in a repository\n- Light high contrast theme\n"
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'

translations/es-ES/data/release-notes/enterprise-server/3-5/4.yml

@@ -0,0 +1,20 @@
+date: '2022-08-11'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+    - |
+      **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).
+  bugs:
+    - In some cases, GitHub Enterprise Server instances on AWS that used the `r4.4xlarge` instance type would fail to boot.
+    - In some cases, UI elements within a pull request's **Files changed** tab could overlap.
+    - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+    - 'When calculating committers for GitHub Advanced Security, it was not possible to specify individual repositories. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."'
+    - In some cases, Elasticsearch's post-upgrade `es:upgrade` process could crash before completion.
+    - The script for migration to internal repositories failed to convert the visibility for public repositories to internal or private. For more information about the migration, see "[Migrating to internal repositories](/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories)."
+    - 'Detection of GitHub Actions workflow files for the dependency graph was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#supported-package-ecosystems)."'
+    - 'The ability to reopen dismissed Dependabot alerts was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)."'
+    - The ability to always suggest updates from the base branch to a pull request's HEAD was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)."
+    - The light high contrast theme was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)."
+  changes:
+    - '`pre_receive_hook.rejected_push` events were not displayed in the enterprise audit log.'

translations/es-ES/data/reusables/actions/runner-debug-description.md

@@ -0,0 +1 @@
+This is set only if [debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging) is enabled, and always has the value of `1`. It can be useful as an indicator to enable additional debugging or verbose logging in your own job steps.

translations/es-ES/data/reusables/education/about-github-education-link.md

@@ -1,3 +1,3 @@
-As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} es un portal que permite que la Comunidad de GitHub Education acceda a sus beneficios educativos; ¡todo en un solo lugar! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, [{% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange), {% data variables.product.prodname_student_pack %}, and other exclusive features to help students and teachers shape the next generation of software development.
+Como alumno o miembro de una facultad en una institución educativa acreditada, puedes aplicar para {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} es un portal que permite que la Comunidad de GitHub Education acceda a sus beneficios educativos; ¡todo en un solo lugar! El portal de {% data variables.product.prodname_global_campus %} incluye acceso a {% data variables.product.prodname_education_community_with_url %}, herramientas de la industria que utilizan los desarrolladores profesionales, eventos, contenido de la [TV del Campus](https://www.twitch.tv/githubeducation), {% data variables.product.prodname_classroom_with_url %}, [{% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange), el {% data variables.product.prodname_student_pack %} y otras características exclusivas para ayudar a los alumnos y docentes a formar la siguiente generación de desarrollo de software.
 
 Antes de solicitar un descuento individual, comprueba si tu comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_campus_program %}. Para obtener más información, consulta la sección "[Acerca de la {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)".

translations/es-ES/data/reusables/education/educator-requirements.md

@@ -1,4 +1,4 @@
-To apply for teacher benefits and {% data variables.product.prodname_global_campus %} access, you must meet the following requirements.
+Para solicitar los beneficios de docente y el acceso al {% data variables.product.prodname_global_campus %}, primero debes cumplir con los siguientes requisitos.
 
 - Ser educador, miembro de una factultad, o investigador.
 - Tener una dirección de correo electrónico verificable que haya emitido una institución educativa.

translations/es-ES/data/reusables/enterprise/3-5-missing-feature.md

@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note**: This feature is unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature will be available in an upcoming patch release. For more information about upgrades, contact your site administrator.
+**Note**: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
 
 For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of  {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
 

translations/es-ES/data/reusables/gated-features/codespaces.md

@@ -1 +1 @@
-{% data variables.product.prodname_github_codespaces %} está disponible para las organizaciones que utilizan {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %}
+{% data variables.product.prodname_github_codespaces %} está disponible para las organizaciones que utilizan {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_codespaces %} is also available as a limited beta release for individual users on {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_pro %} plans. {% data reusables.gated-features.more-info-org-products %}

translations/es-ES/data/reusables/gpg/paste-gpg-key-id.md

@@ -1,4 +1,9 @@
-1. Para configurar tu llave de firma GPG en Git, pega el siguiente texto en sustitución de la ID de la llave GPG que quieras utilizar. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`:
-  ```shell
-$ git config --global user.signingkey <em>3AA5C34371567BD2</em>
-```
+1. To set your primary GPG signing key in Git, paste the text below, substituting in the GPG primary key ID you'd like to use. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`:
+   ```shell
+   $ git config --global user.signingkey <em>3AA5C34371567BD2</em>
+   ```
+
+   Alternatively, when setting a subkey include the `!` suffix. In this example, the GPG subkey ID is `4BB6D45482678BE3`:
+   ```shell
+   $ git config --global user.signingkey <em>4BB6D45482678BE3</em>!
+   ```

translations/es-ES/data/reusables/projects/owners-can-limit-visibility-permissions.md

@@ -0,0 +1 @@
+Organization owners can control the ability of organization members to create public {% data variables.projects.projects_v2_and_v1 %}, or change the visibility of existing {% data variables.projects.projects_v2_and_v1 %} to public. For more information, see "[Allowing project visibility changes in your organization](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)."

translations/es-ES/data/ui.yml

@@ -5,7 +5,7 @@ header:
   github_docs: GitHub Docs
   contact: Contacto
   notices:
-    ghae_silent_launch: GitHub AE está actualmente en un lanzamiento limitado. Por favor, <a href="https://enterprise.github.com/contact">contacta a nuestro equipo de ventas</a> para conocer más sobre esto.
+    ghae_silent_launch: GitHub AE está actualmente en lanzamiento limitado.
     release_candidate: '# El nombre de la versión se interpreta antes del texto siguiente a través de '' includes/header-notification.html '' se encuentra disponible actualmente como un candidato de lanzamiento. Para obtener más información, consulta la sección "<a href="/admin/overview/about-upgrades-to-new-releases">Acerca de las mejoras para los lanzamientos nuevos</a>".'
     localization_complete: Publicamos actualizaciones frecuentes a nuestra documentación y la traducción de esta página podría aún estar en curso. Para encontrar la mayoría de la información actual, visita la <a id="to-english-doc" href="/en">documentación en inglés</a>.
     early_access: '📣 Por favor, <b>no compartas</b> esta URL públicamente. Esta página tiene contenido sobre una característica de acceso temprano.'

translations/es-ES/data/variables/projects.yml

@@ -11,3 +11,6 @@ projects_v1_boards: >-
 projects_v1_boards_caps: >-
   {% ifversion ghes or ghae %}Project boards{% else %}Classic projects{% endif %}
 command-palette-shortcut: '<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)'
+#Use feature flags to return which projects versions are available.
+projects_v2_and_v1: '{% ifversion projects-v2 %}{% data variables.projects.projects_v2 %}{% ifversion projects-v1 %} and {% data variables.projects.projects_v1_boards %}{% endif %}{% else %}{% data variables.projects.projects_v1_boards %}{% endif %}'
+project_v2_and_v1: '{% ifversion projects-v2 %}{% data variables.projects.project_v2 %}{% ifversion projects-v1 %} and {% data variables.projects.projects_v1_board %}{% endif %}{% else %}{% data variables.projects.projects_v1_board %}{% endif %}'