From 3a40d0737cf8046b3d50687b4caa6e2ea5c55fee Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Mon, 21 Nov 2022 08:42:43 -0800 Subject: [PATCH] New translation batch for es (#32811) --- .../environment-variables.md | 8 +- .../about-billing-for-github-actions.md | 2 +- .../about-billing-for-github-codespaces.md | 8 +- .../syntax-for-githubs-form-schema.md | 151 +++++++++--------- ...-with-github-copilot-in-a-jetbrains-ide.md | 2 +- .../creating-ci-tests-with-the-checks-api.md | 4 +- .../rest/guides/traversing-with-pagination.md | 6 +- .../reusables/actions/ref_name-description.md | 2 +- translations/log/msft-es-resets.csv | 1 + 9 files changed, 96 insertions(+), 88 deletions(-) diff --git a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md index 60f517beb6..c28d08e7ee 100644 --- a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md +++ b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md @@ -163,13 +163,15 @@ We strongly recommend that actions use environment variables to access the files | `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. | | `GITHUB_WORKSPACE` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. For example, `/home/runner/work/my-repo-name/my-repo-name`. | {%- ifversion actions-runner-arch-envvars %} -| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %} -{%- endif %} | +| `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` | -{% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %} For example, `C:\hostedtoolcache\windows` |{% endif %} +{%- ifversion not ghae %} +| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %} For example, `C:\hostedtoolcache\windows` | +{%- endif %} {% note %} diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index 6e8acc6b4d..571de5c750 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -67,7 +67,7 @@ The storage used by a repository is the total storage used by {% data variables. ### Per-minute rates {% data reusables.billing.billing-standard-runners %} -{% ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{% endif %} +{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %} - The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. - {% data reusables.user-settings.context_switcher %} diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md index ce73aba9f4..d1ee841dbc 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md @@ -39,12 +39,14 @@ The following storage and core hours of usage are included, free of charge, for | Account plan | Storage per month | Core hours per month | | ------------ | ----------------- | -------------------- | -| {% data variables.product.prodname_dotcom %} Free for personal accounts | 15 GB | 120 | -| {% data variables.product.prodname_dotcom %} Pro | 20 GB | 180 | +| {% data variables.product.prodname_dotcom %} Free for personal accounts | 15 GB-month | 120 | +| {% data variables.product.prodname_dotcom %} Pro | 20 GB-month | 180 | {% note %} -**Note**: A "core hour" is a measure used for included compute usage. To calculate core hours, multiply the number of hours for which a codespace has been active by the multiplier in the pricing table below. For the basic machine types, the multiplier is the number of processor cores in the machine that hosts the codespace. For example, if you use a 2-core machine for your codespace and it's active for an hour, you have used 2 core hours. If you use an 8-core machine for an hour, you have used 8 core hours. If you use an 8-core machine for two hours, you have used 16 core hours. +**Notes**: +- The GB-month unit of storage is a time-based measurement, 1 GB-month being 1 GB of storage usage for one whole month. The disk space used by all of your codespaces and prebuilds is assessed once an hour and your current GB-month usage is recalculated. Therefore, while you have codespaces and prebuilds, your GB-month usage will increase throughout the month. For example, if the storage totals 15 GB, and remains unchanged throughout your monthly billing cycle, then you will have used 7.5 GB halfway through the month, and 15 GB at the end of the month. For more information, see "[Billing for storage usage](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)" below. +- A "core hour" is a measure used for included compute usage. To calculate core hours, multiply the number of hours for which a codespace has been active by the multiplier in the pricing table below. For the basic machine types, the multiplier is the number of processor cores in the machine that hosts the codespace. For example, if you use a 2-core machine for your codespace and it's active for an hour, you have used 2 core hours. If you use an 8-core machine for an hour, you have used 8 core hours. If you use an 8-core machine for two hours, you have used 16 core hours. {% endnote %} diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md index 1eb75a5d63..93a197c3eb 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md @@ -1,32 +1,27 @@ --- -title: Sintaxis para el modelado de formato de GitHub -intro: 'Puedes utilizar el modelado de formato de {% data variables.product.company_short %} para configurar los formatos para las características compatibles.' +title: Syntax for GitHub's form schema +intro: 'You can use {% data variables.product.company_short %}''s form schema to configure forms for supported features.' versions: fpt: '*' ghec: '*' miniTocMaxHeadingLevel: 3 topics: - Community -ms.openlocfilehash: 2a329c7c0a7f1943f7515059c3f376fa36ea29b1 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145117577' --- + {% note %} -**Nota:** El esquema de formato de {% data variables.product.company_short %} se encuentra actualmente en versión beta y está sujeto a cambios. +**Note:** {% data variables.product.company_short %}'s form schema is currently in beta and subject to change. {% endnote %} -## Acerca del modelado de formatos de {% data variables.product.company_short %} +## About {% data variables.product.company_short %}'s form schema -Puedes utilizar el modelado de formato de {% data variables.product.company_short %} para configurar los formatos para las características compatibles. Para más información, vea "[Configuración de plantillas de incidencia para el repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)". +You can use {% data variables.product.company_short %}'s form schema to configure forms for supported features. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)." -Un formato es un conjunto de elemotos para solicitar la aportación de un usuario. Puedes configurar un formato si creas una definición de formato YAML, la cual es un arreglo de elementos de formato. Cada elemento de formato es un conjunto de pares de valor-llave que determinan el tipo y las propiedades del elemento y las restricciones que quieres aplicarle. Para algunas claves, el valor es otro conjunto de pares de clave-valor. +A form is a set of elements for requesting user input. You can configure a form by creating a YAML form definition, which is an array of form elements. Each form element is a set of key-value pairs that determine the type of the element, the properties of the element, and the constraints you want to apply to the element. For some keys, the value is another set of key-value pairs. -Por ejemplo, la siguente definición de formato incluye cuatro elementos de formato: un área de texto para proporcionar el sistema operativo del usuario, un menú desplegable para elegir la versión de software que está ejecutando el usuario, una casilla de verificación para reconocer que se leyó y aceptó el código de conducta y el lenguaje de marcado que agradece al usuario por haber completado el formato. +For example, the following form definition includes four form elements: a text area for providing the user's operating system, a dropdown menu for choosing the software version the user is running, a checkbox to acknowledge the Code of Conduct, and Markdown that thanks the user for completing the form. ```yaml{:copy} - type: textarea @@ -60,48 +55,48 @@ Por ejemplo, la siguente definición de formato incluye cuatro elementos de form value: "Thanks for completing our form!" ``` -## Teclas +## Keys -Para cada elemento de formato, puedes configurar las siguientes claves. +For each form element, you can set the following keys. -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | -| `type` | El tipo de elemento que quieres definir. | Obligatorio | String | {% octicon "dash" aria-label="The dash icon" %} | | -| `id` | Identificador del elemento, excepto cuando `type` se establece en `markdown`. {% data reusables.form-schema.id-must-be-unique %} Si se proporciona, `id` es el identificador canónico para el campo en los valores previamente rellenados de parámetro de la consulta de URL. | Opcionales | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `attributes` | Un conjunto de pares clave-valor que definen las propiedades del elemento. | Obligatorio | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `validations` | Un conjunto de pares de clave-valor que configuran las restricciones en el elemento. | Opcionales | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `type` | The type of element that you want to define. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | | +| `id` | The identifier for the element, except when `type` is set to `markdown`. {% data reusables.form-schema.id-must-be-unique %} If provided, the `id` is the canonical identifier for the field in URL query parameter prefills. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `attributes` | A set of key-value pairs that define the properties of the element. | Required | Map | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `validations` | A set of key-value pairs that set constraints on the element. | Optional | Map | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -Puedes elegir desde los siguientes tipos de elementos de formato. Cada tipo tiene atributos y validaciones únicos. +You can choose from the following types of form elements. Each type has unique attributes and validations. -| Tipo | Descripción | +| Type | Description | | ---- | ----------- | -| [`markdown`](#markdown) | El texto de Markdown que se muestra en el formulario para proporcionar contexto adicional al usuario, pero que **no se envía**. | -| [`textarea`](#textarea) | Un campo de texto de línea múltiple. | -| [`input`](#input) | Un campo de texto de línea sencilla. | -| [`dropdown`](#dropdown) | Un menú desplegable. | -| [`checkboxes`](#checkboxes) | Un conjunto de casillas de verificación. | +| [`markdown`](#markdown) | Markdown text that is displayed in the form to provide extra context to the user, but is **not submitted**. | +| [`textarea`](#textarea) | A multi-line text field. | +| [`input`](#input) | A single-line text field. | +| [`dropdown`](#dropdown) | A dropdown menu. | +| [`checkboxes`](#checkboxes) | A set of checkboxes. | ### `markdown` -Puede usar un elemento `markdown` para mostrar Markdown en el formulario que proporcione contexto adicional al usuario, pero que no se envíe. +You can use a `markdown` element to display Markdown in your form that provides extra context to the user, but is not submitted. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | -| `value` | El texto se interpreta. El formateo en lenguaje de marcado es compatible. | Obligatorio | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | The text that is rendered. Markdown formatting is supported. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | {% tip %} -**Sugerencias:** el procesamiento de YAML tratará el símbolo hash como un comentario. Para insertar encabezados con lenguaje de marcado, pon tu texto entre comillas. +**Tips:** YAML processing will treat the hash symbol as a comment. To insert Markdown headers, wrap your text in quotes. -Para el texto de línea múltiple, puedes utilizar el operador de pipa. +For multi-line text, you can use the pipe operator. {% endtip %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -116,29 +111,29 @@ body: ### `textarea` -Puede usar un elemento `textarea` para agregar un campo de texto de varias líneas al formulario. Los colaboradores también pueden adjuntar archivos en campos `textarea`. +You can use a `textarea` element to add a multi-line text field to your form. Contributors can also attach files in `textarea` fields. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | Una descripción breve de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Obligatorio | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | Una descripción del área de texto para proporcionar contexto u orientación, la cual se muestra en el formato. | Opcionales | String | Cadena vacía | {% octicon "dash" aria-label="The dash icon" %} | -| `placeholder` | Un marcador de posición que interpreta en el área de texto cuando está vacía. | Opcionales | String | Cadena vacía | {% octicon "dash" aria-label="The dash icon" %} | -| `value` | El texto se pre-llena en el área de texto. | Opcionales | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `render` | Si se proporciona un valor, el texto emitido se formatea en un bloque de código. Cuando se proporciona esta llave, el áera de texto no se expandirá para los adjuntos de archivo o la edición de lenguaje de marcado. | Opcionales | String | {% octicon "dash" aria-label="The dash icon" %} | Los lenguajes que conoce {% data variables.product.prodname_dotcom %}. Para más información, vea [el archivo YAML de lenguajes](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). | +| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the text area to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `placeholder` | A semi-opaque placeholder that renders in the text area when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | Text that is pre-filled in the text area. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `render` | If a value is provided, submitted text will be formatted into a codeblock. When this key is provided, the text area will not expand for file attachments or Markdown editing. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | Languages known to {% data variables.product.prodname_dotcom %}. For more information, see [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). | -#### Validaciones +#### Validations {% data reusables.form-schema.validations-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -159,28 +154,28 @@ body: ### `input` -Puede usar un elemento `input` para agregar un campo de texto de una sola línea al formulario. +You can use an `input` element to add a single-line text field to your form. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | Una descripción breve de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Obligatorio | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | Una descripción del campo para proporcionar contexto u orientación, la cual se muestra en el formato. | Opcionales | String | Cadena vacía | {% octicon "dash" aria-label="The dash icon" %} | -| `placeholder` | Un marcador de posición semi-transparente que interpreta en el campo cuando está vacío. | Opcionales | String | Cadena vacía | {% octicon "dash" aria-label="The dash icon" %} | -| `value` | El texto se pre-llenó en el campo. | Opcionales | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the field to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `placeholder` | A semi-transparent placeholder that renders in the field when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | Text that is pre-filled in the field. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -#### Validaciones +#### Validations {% data reusables.form-schema.validations-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -196,28 +191,28 @@ body: ### `dropdown` -Puede usar un elemento `dropdown` para agregar un menú desplegable en el formulario. +You can use a `dropdown` element to add a dropdown menu in your form. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Obligatorio | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | Una descripción del menú desplegable para proporcionar contexto adicional u orientación, la cual se muestra en el formato. | Opcionales | String | Cadena vacía | {% octicon "dash" aria-label="The dash icon" %} | -| `multiple` | Determina si el usuario puede seleccionar más de una opción. | Opcionales | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} | -| `options` | Un arreglo de opciones que puede elegir el usuario. No puede estar vacío y todas las elecciones deben ser distintas. | Obligatorio | Matriz de cadena | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the dropdown to provide extra context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `multiple` | Determines if the user can select more than one option. | Optional | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} | +| `options` | An array of options the user can choose from. Cannot be empty and all choices must be distinct. | Required | String array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -#### Validaciones +#### Validations {% data reusables.form-schema.validations-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -236,21 +231,29 @@ body: ### `checkboxes` -Puede usar el elemento `checkboxes` para agregar un conjunto de casillas al formulario. +You can use the `checkboxes` element to add a set of checkboxes to your form. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Obligatorio | Tipo | Valor predeterminado | Valores válidos | +| Key | Description | Required | Type | Default | Valid values | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Obligatorio | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | Una descripción del conjunto de casillas de verificación, la cual se muestra en el formato. Es compatible con el formateo de lenguaje de marcado. | Opcionales | String | Cadena vacía | {% octicon "dash" aria-label="The dash icon" %} | -| `options` | Un arreglo de casillas de verificación que puede seleccionar el usuario. Para conocer la sintaxis, consulta a continuación. | Obligatorio | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the set of checkboxes, which is displayed in the form. Supports Markdown formatting. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `options` | An array of checkboxes that the user can select. For syntax, see below. | Required | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -{% data reusables.form-schema.options-syntax %} {% data reusables.form-schema.required-key %} +{% data reusables.form-schema.options-syntax %} -#### Ejemplo +#### Validations + +{% data reusables.form-schema.validations-intro %} + +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | +{% data reusables.form-schema.required-key %} + +#### Example ```YAML{:copy} body: @@ -265,6 +268,6 @@ body: - label: Linux ``` -## Información adicional +## Further reading - [YAML](https://yaml.org) diff --git a/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md b/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md index 784262db66..4030606035 100644 --- a/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md +++ b/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md @@ -19,7 +19,7 @@ If you use a JetBrains IDE, you can view and incorporate suggestions from {% dat {% data reusables.copilot.jetbrains-ides %} -## Installing the JetBrains extension +## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} extension. The following procedure will guide you through installation of the {% data variables.product.prodname_copilot %} plugin in IntelliJ IDEA. Steps to install the plugin in another supported IDE may differ. diff --git a/translations/es-ES/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md b/translations/es-ES/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md index d7a628b157..ed48c7bb97 100644 --- a/translations/es-ES/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md +++ b/translations/es-ES/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md @@ -154,7 +154,7 @@ def create_check_run end ``` -This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run). +This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://msp-greg.github.io/octokit/Octokit/Client/Checks.html#create_check_run-instance_method). To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [RuboCop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo RuboCop" is used here, but you can choose any name you'd like for the check run. @@ -236,7 +236,7 @@ def initiate_check_run end ``` -The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) to update the check run that you already created. +The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://msp-greg.github.io/octokit/Octokit/Client/Checks.html#update_check_run-instance_method) to update the check run that you already created. Here's what this code is doing. First, it updates the check run's status to `in_progress` and implicitly sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`. diff --git a/translations/es-ES/content/rest/guides/traversing-with-pagination.md b/translations/es-ES/content/rest/guides/traversing-with-pagination.md index f47cd8dbbf..008346f884 100644 --- a/translations/es-ES/content/rest/guides/traversing-with-pagination.md +++ b/translations/es-ES/content/rest/guides/traversing-with-pagination.md @@ -102,7 +102,7 @@ link: +after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before= ``` @@ -115,7 +115,7 @@ after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D% Using cursor based pagination requires you to use the terms `before` and `after`. To navigate using `before` and `after`, copy the link header generated above into your curl request: ```shell -$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=> +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before= ``` The above example will generate a page of results and new header information that you can use to make the next request. `rel="next"` provides the next page of results. `rel="prev"` provides the previous page of results. The important part of the output here is the link header needs to be generated rather than manually imputed. Copy the entire link from the following output. @@ -183,7 +183,7 @@ our results. You can also pass the `per_page` parameter for cursor-based pagination. ```shell -$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>&per_page=50 +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=&per_page=50 ``` ## Consuming the information diff --git a/translations/es-ES/data/reusables/actions/ref_name-description.md b/translations/es-ES/data/reusables/actions/ref_name-description.md index b57457d5cc..0efeaa0606 100644 --- a/translations/es-ES/data/reusables/actions/ref_name-description.md +++ b/translations/es-ES/data/reusables/actions/ref_name-description.md @@ -1 +1 @@ -The short ref name of the branch or tag that triggered the workflow run. This value matches the branch or tag name shown on {% data variables.product.prodname_dotcom %}. For example, `feature-branch-1`. +The short ref name of the branch or tag that triggered the workflow run. This value matches the branch or tag name shown on {% data variables.product.prodname_dotcom %}. For example, `feature-branch-1`. \ No newline at end of file diff --git a/translations/log/msft-es-resets.csv b/translations/log/msft-es-resets.csv index c6e9386997..22eee4d4e7 100644 --- a/translations/log/msft-es-resets.csv +++ b/translations/log/msft-es-resets.csv @@ -820,6 +820,7 @@ translations/es-ES/content/communities/documenting-your-project-with-wikis/editi translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md,broken liquid tags translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md,rendering error translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error +translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,broken liquid tags translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags