New translation batch for es (#25727)

* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check parsing * run script/i18n/reset-files-with-broken-liquid-tags.js --language=es * run script/i18n/reset-known-broken-translation-files.js * Check in es CSV report Co-authored-by: Peter Bengtsson <[email protected]>
github · Octomerger · Mar 2, 2022 · Mar 1, 2022 · Mar 1, 2022 · Mar 1, 2022
commit c03e00afd6e4598391ed9a05c5220262bab039ca
diff --git a/...ntent/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/...ntent/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -78,9 +78,9 @@ Este flujo de trabajo realiza los siguientes pasos:
 
 Los flujos de trabajo iniciales predeterminados son un punto de partida excelente para crear tu flujo de trabajo de prueba y de compilación y puedes personalizarlos de acuerdo con las necesidades de tu proyecto.
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
 
 ## Construir y probar tu código
 

diff --git a/...nt/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/...nt/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -83,9 +83,9 @@ Este flujo de trabajo realiza los siguientes pasos:
 
 Los flujos de trabajo iniciales predeterminados son un punto de partida excelente para crear tu flujo de trabajo de prueba y de compilación y puedes personalizarlos de acuerdo con las necesidades de tu proyecto.
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
 
 ## Construir y probar tu código
 

diff --git a/...ent/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/...ent/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -78,9 +78,9 @@ Este flujo de trabajo realiza los siguientes pasos:
 
 Los flujos de trabajo iniciales predeterminados son un punto de partida excelente para crear tu flujo de trabajo de prueba y de compilación y puedes personalizarlos de acuerdo con las necesidades de tu proyecto.
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
 
 ## Construir y probar tu código
 

diff --git a/...s-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/...s-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -73,7 +73,7 @@ jobs:
 ```
 {% endraw %}
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
 ## Especificar la versión de Node.js
 
@@ -204,7 +204,7 @@ steps:
 
 ### Ejemplo de uso de un registro privado y la creación del archivo .npmrc
 
-{% data reusables.github-actions.setup-node-intro %}
+{% data reusables.actions.setup-node-intro %}
 
 Para autenticar tu registro privado, necesitarás almacenar tu token de autenticación de npm como un secreto. Por ejemplo, crea un repositorio secreto que se llame `NPM_TOKEN`. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 

diff --git a/...ctions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/...ctions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -31,7 +31,7 @@ Para encontrar una lista completa de versiones disponibles de Xamarin SDK en los
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
 
-{% data reusables.github-actions.macos-runner-preview %}
+{% data reusables.actions.macos-runner-preview %}
 
 ## Prerrequisitos
 

diff --git a/translations/es-ES/content/actions/creating-actions/about-custom-actions.md b/translations/es-ES/content/actions/creating-actions/about-custom-actions.md
@@ -47,13 +47,13 @@ Los contenedores Docker empaquetan el entorno con el código de las {% data vari
 
 Un contenedor Docker te permite usar versiones específicas de un sistema operativo, dependencias, herramientas y código. Para las acciones que se deben ejecutar en una configuración de entorno específica, Docker es una opción ideal porque puedes personalizar el sistema operativo y las herramientas. Debido a la latencia para crear y recuperar el contenedor, las acciones del contenedor Docker son más lentas que las acciones de JavaScript.
 
-Las acciones de contenedor de Docker solo pueden ejecutarse en ejecutores con un sistema operativo Linux. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+Las acciones de contenedor de Docker solo pueden ejecutarse en ejecutores con un sistema operativo Linux. {% data reusables.actions.self-hosted-runner-reqs-docker %}
 
 ### Acciones de JavaScript
 
 Las acciones de JavaScript pueden ejecutarse directamente en una máquina del ejecutor y separar el código de acción del entorno utilizado para ejecutar el código. El uso de una acción de JavaScript simplifica el código de acción y se ejecuta más rápido que una acción de contenedor Docker.
 
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
 
 Si estás desarrollando un proyecto Node.js, el conjunto de herramientas de las {% data variables.product.prodname_actions %} te ofrece paquetes que puedes usar en tu proyecto para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit).
 

diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
@@ -23,7 +23,7 @@ En esta guía, aprenderás acerca de los componentes básicos necesarios para cr
 
 Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción compuesta y probarla en un flujo de trabajo.
 
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
 
 ## Prerrequisitos
 

diff --git a/...ns/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md b/...ns/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -27,9 +27,9 @@ In this guide, you'll learn about the basic components needed to create and use
 
 Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
 
-{% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+{% data reusables.actions.self-hosted-runner-reqs-docker %}
 
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
 
 ## Prerequisites
 

diff --git a/...slations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md b/...slations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
@@ -29,9 +29,9 @@ Esta guía usa el módulo Node.js del kit de herramientas {% data variables.prod
 
 Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de JavaScript y probarla en un flujo de trabajo.
 
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
 
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
 
 ## Prerrequisitos
 

diff --git a/...es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/...es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -105,7 +105,7 @@ Si defines el `args` en el archivo de metadatos de la acción, `args` invalidar
 
 Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos:
 
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
 
 ## Capacidades de Linux compatibles
 

diff --git a/...ns/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/...ns/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -272,7 +272,7 @@ Para obtener más información, consulta la sección "[``](/actions/reference/co
 
 **Opcional** Puedes utilizar el condicional `if` para prevenir que un paso se ejecute a menos de que se cumpla con una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional.
 
-{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
 
 **Ejemplo: Utilizando contextos**
 
@@ -441,7 +441,7 @@ runs:
 
 Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia:
 
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
 
 Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta ejecute un shell de comandos para realizar la sustitución de variables. Por ejemplo, si se configura tu atributo `entrypoint` como `"sh -c"`, entoces `args` se ejecutará en un shell de comandos. Como alternativa, si tu `Dockerfile` utiliza un `ENTRYPOINT` para ejecutar el mismo comando (`"sh -c"`), entonces `args` se ejecutará en un shell de comandos.
 

diff --git a/...eployment/targeting-different-environments/using-environments-for-deployment.md b/...eployment/targeting-different-environments/using-environments-for-deployment.md
@@ -69,13 +69,13 @@ Los secretos que se almacenan en un ambiente sólo se encuentran disponibles par
 
 ## Crear un ambiente
 
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
-{% data reusables.github-actions.new-environment %}
-{% data reusables.github-actions.name-environment %}
+{% data reusables.actions.sidebar-environment %}
+{% data reusables.actions.new-environment %}
+{% data reusables.actions.name-environment %}
 1. Opcionalmente, personas o equipos específicos deben aprobar los jobs de flujo de trabajo que utilicen este ambiente.
    1. Selecciona **Revisores requeridos**.
    1. Ingresa hasta 6 personas o equipos. Solo uno de los revisores requeridos necesita aprobar el job para que éste pueda proceder.
@@ -107,13 +107,13 @@ Cuando un flujo de trabajo referencia un ambiente, éste aparecerá en los despl
 
 ## Borrar un ambiente
 
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
 
 El borrar un ambiente borrará todos los secretos y reglas de protección asociadas con éste. Cualquier job que esté actualmente en espera porque depende de las reglas de protección del ambiente que se borró, fallará automáticamente.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
 1. Junto al ambiente que quieres borrar, haz clic en {% octicon "trash" aria-label="The trash icon" %}.
 2. Da clic en **Entiendo, borra este ambiente**.
 

diff --git a/...ons/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/...ons/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -18,25 +18,25 @@ type: overview
 
 ## About self-hosted runners
 
-{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
+{% data reusables.actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
 
 You can add self-hosted runners at various levels in the management hierarchy:
 - Repository-level runners are dedicated to a single repository.
 - Organization-level runners can process jobs for multiple repositories in an organization.
 - Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
 
-Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
 
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
 
 For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
 
-## {% ifversion fpt or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
+## {% ifversion fpt or ghec or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
 
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
 {% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted{% elsif ghae %}Self-hosted{% endif %} runners are a highly configurable way to run workflows in your own custom environment. {% ifversion ghae %}Self-hosted runners:{% endif %}
 
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
 **{% data variables.product.prodname_dotcom %}-hosted runners:**
 - Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application.
 - Are managed and maintained by {% data variables.product.prodname_dotcom %}.
@@ -70,15 +70,15 @@ You can automatically increase or decrease the number of self-hosted runners in
 
 There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
 
-{% data reusables.github-actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-workflow-run-time %}
 - **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
-{% data reusables.github-actions.usage-api-requests %}
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+{% data reusables.actions.usage-api-requests %}
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
 
 ## Workflow continuity for self-hosted runners
 
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
 
 ## Supported architectures and operating systems for self-hosted runners
 
@@ -224,7 +224,7 @@ codeload.github.com
 
 {% ifversion fpt or ghec %}
 
-{% data reusables.github-actions.self-hosted-runner-security %}
+{% data reusables.actions.self-hosted-runner-security %}
 
 {% endif %}
 

diff --git a/...ns/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/...ns/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -26,7 +26,7 @@ For information on supported operating systems for self-hosted runners, or using
 {% ifversion not ghae %}
 {% warning %}
 
-**Warning:** {% data reusables.github-actions.self-hosted-runner-security %}
+**Warning:** {% data reusables.actions.self-hosted-runner-security %}
 
 For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
@@ -40,18 +40,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
 1. Click **New self-hosted runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
 1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
 
 ## Adding a self-hosted runner to an organization
 
@@ -60,21 +60,21 @@ You can add self-hosted runners at the organization level, where they can be use
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
 1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
 1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% endif %}
 
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
 
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
 
 ## Adding a self-hosted runner to an enterprise
 
@@ -92,19 +92,19 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% elsif ghae or ghes < 3.4 %}
 To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 1. Click **Add new**, then click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
 
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
 
 ### Making enterprise runners available to repositories