New translation batch for es (#24880)
* 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
This commit is contained in:
docubot
@@ -38,8 +38,8 @@ Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %},
|
||||
1. Solicita el nombre de usuario de la persona a la que estás invitando como colaborador.{% ifversion fpt or ghec %} Si aún no tiene un nombre de usuario, puede registrarse para {% data variables.product.prodname_dotcom %} Para obtener más información, consulta "[Registrar una cuenta {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account)".{% endif %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
1. Da clic en **Invitar un colaborador**. 
|
||||
2. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. 
|
||||
3. Da clic en **Añadir NOMBRE a REPOSITORIO**. 
|
||||
|
||||
@@ -30,8 +30,8 @@ Aunque se borren las bifurcaciones de los repositorios privados cuando se elimin
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
4. Da clic en {% octicon "trash" aria-label="The trash icon" %} a la derecha del colaborador que quieres eliminar. 
|
||||
{% else %}
|
||||
3. En la barra lateral izquierda, haz clic en **Collaborators & teams** (Colaboradores y equipos). 
|
||||
|
||||
@@ -26,8 +26,7 @@ Puedes configurar recordatorios programados para solicitudes de revisión a nive
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
3. Da clic en **Editar** a un costado de la organización para la cual quieres programar un recordatorio. 
|
||||
1. Da clic en **Editar** a un costado de la organización para la cual quieres programar un recordatorio. 
|
||||
{% data reusables.reminders.add-reminder %}
|
||||
{% data reusables.reminders.authorize-slack %}
|
||||
{% data reusables.reminders.days-dropdown %}
|
||||
@@ -41,16 +40,14 @@ Puedes configurar recordatorios programados para solicitudes de revisión a nive
|
||||
## Administrar recordatorios programados para tu cuenta de usuario
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
3. Da clic en **Editar** a un costado de la organización para la cual quieres editar los recordatorios programados. 
|
||||
1. Da clic en **Editar** a un costado de la organización para la cual quieres editar los recordatorios programados. 
|
||||
{% data reusables.reminders.edit-page %}
|
||||
{% data reusables.reminders.update-buttons %}
|
||||
|
||||
## Borrar recordatorios programados para tu cuenta de usuario
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
3. Da clic en **Editar** a un costado de la organización para la cual quieres borrar un recordatorio. 
|
||||
1. Da clic en **Editar** a un costado de la organización para la cual quieres borrar un recordatorio. 
|
||||
{% data reusables.reminders.delete %}
|
||||
|
||||
## Leer más
|
||||
|
||||
@@ -84,7 +84,9 @@ Antes de comenzar, deberás crear un repositorio en {% ifversion ghae %}{% data
|
||||
- id: random-number-generator
|
||||
run: echo "::set-output name=random-id::$(echo $RANDOM)"
|
||||
shell: bash
|
||||
- run: ${{ github.action_path }}/goodbye.sh
|
||||
- run: echo "${{ github.action_path }}" >> $GITHUB_PATH
|
||||
shell: bash
|
||||
- run: goodbye.sh
|
||||
shell: bash
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -47,6 +47,8 @@ Si defines el `entrypoint` en un archivo de metadatos de una acción, este inval
|
||||
|
||||
La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. Para obtener más información acerca de las formas _exec_ y _shell_, consulta la sección [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) en la documentación de Docker.
|
||||
|
||||
You should not use `WORKDIR` to specify your entrypoint in your Dockerfile. Instead, you should use an absolute path. For more information, see [WORKDIR](#workdir).
|
||||
|
||||
Si configuras tu contenedor para que utilice la forma _exec_ de la instrucción `ENTRYPOINT`, entonces el `args` configurado en el archivo de metadatos de la acción no se ejecutará en un shell de comandos. Si el `args` de la accion contiene una variable de ambiente, ésta no se sustituirá. Por ejemplo, utilizar el siguiente formato _exec_ no imprimirá los valores almacenados en `$GITHUB_SHA`, si no que imprimirá `"$GITHUB_SHA"`.
|
||||
|
||||
```dockerfile
|
||||
@@ -99,7 +101,7 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s
|
||||
|
||||
### CMD
|
||||
|
||||
Si defines el `args` en el archivo de metadatos de la acción, `args` invalidará la instrucción `CMD` especificada en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
|
||||
If you define `args` in the action's metadata file, `args` will override the `CMD` instruction specified in the `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
|
||||
|
||||
Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos:
|
||||
|
||||
|
||||
@@ -13,6 +13,7 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
miniTocMaxHeadingLevel: 4
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
@@ -40,7 +41,7 @@ Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAM
|
||||
|
||||
**Opcional** Los parámetros de entrada te permiten especificar datos que la acción espera para usar durante el tiempo de ejecución. {% data variables.product.prodname_dotcom %} almacena parámetros de entrada como variables de entorno. Las Id de entrada con letras mayúsculas se convierten a minúsculas durante el tiempo de ejecución. Recomendamos usar Id de entrada en minúsculas.
|
||||
|
||||
### Ejemplo
|
||||
### Example: Specifying inputs
|
||||
|
||||
Este ejemplo configura dos entradas: numOctocats y octocatEyeColor. La entrada numOctocats no se requiere y se predeterminará a un valor de '1'. Se requiere la entrada octocatEyeColor y no tiene un valor predeterminado. Los archivos de flujo de trabajo que usan esta acción deben usar la palabra clave `with` (con) para establecer un valor de entrada para octocatEyeColor. Para obtener información sobre la sintaxis `with` (con), consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)".
|
||||
|
||||
@@ -83,13 +84,13 @@ Por ejemplo, si un flujo de trabajo definió las entradas de `numOctocats` y `oc
|
||||
|
||||
**Opcional** Si se utiliza el parámetro de entrada, esta `string` se registrará como un mensaje de advertencia. Puedes utilizar esta advertencia para notificar a los usuarios que la entrada es obsoleta y mencionar cualquier alternativa.
|
||||
|
||||
## `outputs (salidas)`
|
||||
## `outputs` for Docker container and JavaScript actions
|
||||
|
||||
**Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior. Por ejemplo, si tuviste una acción que realizó la adición de dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada.
|
||||
|
||||
Si no declaras una salida en tu archivo de metadatos de acción, todavía puedes configurar las salidas y utilizarlas en un flujo de trabajo. Para obtener más información acerca de la configuración de salidas en una acción, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)".
|
||||
|
||||
### Ejemplo
|
||||
### Example: Declaring outputs for Docker container and JavaScript actions
|
||||
|
||||
```yaml
|
||||
outputs:
|
||||
@@ -107,9 +108,9 @@ outputs:
|
||||
|
||||
## `outputs` para las acciones compuestas
|
||||
|
||||
Los `outputs` **Opcionales** utilizan los mismos parámetros que los `outputs.<output_id>` and los `outputs.<output_id>.description` (consulta la sección "[`outputs` para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), pero también incluyen el token de `value`.
|
||||
**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
|
||||
|
||||
### Ejemplo
|
||||
### Example: Declaring outputs for composite actions
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
@@ -134,13 +135,13 @@ Para obtener más información sobre cómo utilizar la sintaxis de contexto, con
|
||||
|
||||
## `runs`
|
||||
|
||||
**Requerido** Especifica si esta es una acción de JavaScript, una acción compuesta o una acción de Docker y cómo se ejecuta dicha acción.
|
||||
**Required** Specifies whether this is a JavaScript action, a composite action, or a Docker container action and how the action is executed.
|
||||
|
||||
## `runs` para acciones de JavaScript
|
||||
|
||||
**Requerido** Configura la ruta al código de la acción y el tiempo de ejecución que se utiliza para ejecutarlo.
|
||||
|
||||
### Ejemplo de uso con Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
|
||||
### Example: Using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
|
||||
|
||||
```yaml
|
||||
runs:
|
||||
@@ -159,9 +160,9 @@ runs:
|
||||
|
||||
**Requerido** El archivo que contiene tu código de acción. El tiempo de ejecución que se especifica en [`using`](#runsusing) ejecuta este archivo.
|
||||
|
||||
### `pre`
|
||||
### `runs.pre`
|
||||
|
||||
**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. La acción `pre:` siempre se ejecuta predeterminadamente pero puedes invalidarla utilizando [`pre-if`](#pre-if).
|
||||
**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
|
||||
|
||||
En este ejemplo, la acción `pre:` ejecuta un script llamado `setup.js`:
|
||||
|
||||
@@ -173,7 +174,7 @@ runs:
|
||||
post: 'cleanup.js'
|
||||
```
|
||||
|
||||
### `pre-if`
|
||||
### `runs.pre-if`
|
||||
|
||||
**Opcional** Te permite definir las condiciones para la ejecución de la acción `pre:`. La acción `pre:` únicamente se ejecutará si se cumplen las condiciones en `pre-if`. Si no se configura, `pre-if` se configurará predefinidamente como `always()`. En `pre-if`, las funciones de verificación de estado evalúan contra el estado del job y no contra el estado de la propia acción.
|
||||
|
||||
@@ -186,7 +187,7 @@ En este ejemplo, `cleanup.js` se ejecuta únicamente en los ejecutores basados e
|
||||
pre-if: runner.os == 'linux'
|
||||
```
|
||||
|
||||
### `publicación`
|
||||
### `runs.post`
|
||||
|
||||
**Opcional** Te permite ejecutar un script al final de un job, una vez que se haya completado la acción `main:`. Por ejemplo, puedes utilizar `post:` para finalizar algunos procesos o eliminar los archivos innecesarios. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo.
|
||||
|
||||
@@ -201,7 +202,7 @@ runs:
|
||||
|
||||
La acción `post:` siempre se ejecuta predeterminadamente, pero la puedes invalidar utilizando `post-if`.
|
||||
|
||||
### `post-if`
|
||||
### `runs.post-if`
|
||||
|
||||
**Opcional** Te permite definir condiciones para la ejecución de la acción `post:`. La acción `post` únicamente se ejecutará si se cumplen las condiciones en `post-if`. Si no se configura, `pre-if` se configurará predeterminadamente como `always()`. En `post-if`, las funciones de verificación de estado evalúan contra el estado del job y no contra el estado de la propia acción.
|
||||
|
||||
@@ -364,11 +365,11 @@ runs:
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
## `runs` para acciones de Docker
|
||||
## `runs` for Docker container actions
|
||||
|
||||
**Requerido** Configura la imagen que se utiliza para la acción de Docker.
|
||||
**Required** Configures the image used for the Docker container action.
|
||||
|
||||
### Ejemplo utilizando un Dockerfile en tu repositorio
|
||||
### Example: Using a Dockerfile in your repository
|
||||
|
||||
```yaml
|
||||
runs:
|
||||
@@ -376,7 +377,7 @@ runs:
|
||||
image: 'Dockerfile'
|
||||
```
|
||||
|
||||
### Ejemplo usando un contenedor de registro Docker público
|
||||
### Example: Using public Docker registry container
|
||||
|
||||
```yaml
|
||||
runs:
|
||||
@@ -388,9 +389,9 @@ runs:
|
||||
|
||||
**Requerido** Debes configurar este valor como `'docker'`.
|
||||
|
||||
### `pre-entrypoint`
|
||||
### `runs.pre-entrypoint`
|
||||
|
||||
**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `pre-entrypoint:` siempre se ejecuta predeterminadamente pero la puedes invalidar utilizando [`pre-if`](#pre-if).
|
||||
**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
|
||||
|
||||
El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo.
|
||||
|
||||
@@ -422,7 +423,7 @@ Para obtener más información acerca de cómo se ejecuta el `entrypoint`, consu
|
||||
|
||||
### `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 invalidarla utilizando [`post-if`](#post-if).
|
||||
**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_`. The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if).
|
||||
|
||||
```yaml
|
||||
runs:
|
||||
@@ -446,7 +447,7 @@ Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta eje
|
||||
|
||||
Para obtener más información sobre el uso de la instrucción `CMD` con {% data variables.product.prodname_actions %}, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)".
|
||||
|
||||
#### Ejemplo
|
||||
#### Example: Defining arguments for the Docker container
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
@@ -464,7 +465,7 @@ runs:
|
||||
|
||||
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).
|
||||
|
||||
### Ejemplo
|
||||
### Example: Configuring branding for an action
|
||||
|
||||
```yaml
|
||||
branding:
|
||||
@@ -478,7 +479,12 @@ El color de fondo de la insignia. Puede ser: `blanco`, `amarillow`, `azul`, `ver
|
||||
|
||||
### `branding.icon`
|
||||
|
||||
El nombre del icono de [Pluma](https://feathericons.com/) que se debe usar.
|
||||
El nombre del icono de [Pluma](https://feathericons.com/) que se debe usar. <!--
|
||||
This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
|
||||
This table does not match the latest version the feather library.
|
||||
(Brand icons are omitted, and our supported list is not necessarily up-to-date with the latest version of the feather icon library.)
|
||||
To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo.
|
||||
-->
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
|
||||
@@ -29,7 +29,7 @@ By updating your workflows to use OIDC tokens, you can adopt the following good
|
||||
|
||||
- **No cloud secrets**: You won't need to duplicate your cloud credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC.
|
||||
- **Authentication and authorization management**: You have more granular control over how workflows can use credentials, using your cloud provider's authentication (authN) and authorization (authZ) tools to control access to cloud resources.
|
||||
- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single workflow run, and then automatically expires.
|
||||
- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single job, and then automatically expires.
|
||||
|
||||
### Getting started with OIDC
|
||||
|
||||
@@ -38,7 +38,7 @@ The following diagram gives an overview of how {% data variables.product.prodnam
|
||||
|
||||
|
||||
1. In your cloud provider, create an OIDC trust between your cloud role and your {% data variables.product.prodname_dotcom %} workflow(s) that need access to the cloud.
|
||||
2. Every time your {% data variables.product.prodname_actions %} workflow job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate.
|
||||
2. Every time your job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate.
|
||||
3. You could include a step or action in your job to request this token from {% data variables.product.prodname_dotcom %}'s OIDC provider, and present it to the cloud provider.
|
||||
4. Once the cloud provider successfully validates the claims presented in the token, it then provides a short-lived cloud access token that is available only for the duration of the job.
|
||||
|
||||
@@ -51,7 +51,7 @@ When you configure your cloud to trust {% data variables.product.prodname_dotcom
|
||||
|
||||
### Understanding the OIDC token
|
||||
|
||||
Each workflow run requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. During a workflow run, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition.
|
||||
Each job requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. When the job runs, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition.
|
||||
|
||||
The following example OIDC token uses a subject (`sub`) that references a job environment named `prod` in the `octo-org/octo-repo` repository.
|
||||
|
||||
@@ -148,7 +148,7 @@ In addition, your cloud provider could allow you to assign a role to the access
|
||||
|
||||
### Examples
|
||||
|
||||
The following examples demonstrate how to use "Subject" as a condition. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the workflow run's [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use.
|
||||
The following examples demonstrate how to use "Subject" as a condition. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use.
|
||||
|
||||
#### Filtering for a specific environment
|
||||
|
||||
|
||||
@@ -93,7 +93,7 @@ jobs:
|
||||
- name: Git clone the repository
|
||||
uses: actions/checkout@v2
|
||||
- name: configure aws credentials
|
||||
uses: aws-actions/configure-aws-credentials@master
|
||||
uses: aws-actions/configure-aws-credentials@v1
|
||||
with:
|
||||
role-to-assume: arn:aws:iam::1234567890:role/example-role
|
||||
role-session-name: samplerolesession
|
||||
|
||||
@@ -44,7 +44,7 @@ For more information about installing and using self-hosted runners, see "[Addin
|
||||
- Use free minutes on your {% data variables.product.prodname_dotcom %} plan, with per-minute rates applied after surpassing the free minutes.
|
||||
|
||||
**Self-hosted runners:**{% endif %}
|
||||
- Receive automatic updates for the self-hosted runner application only. You are responsible for updating the operating system and all other software.
|
||||
- Receive automatic updates for the self-hosted runner application only{% ifversion fpt or ghec or ghes > 3.2 %}, though you may disable automatic updates of the runner. For more information about controlling runner software updates on self-hosted runners, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners#controlling-runner-software-updates-on-self-hosted-runners)."{% else %}.{% endif %} You are responsible for updating the operating system and all other software.
|
||||
- Can use cloud services or local machines that you already pay for.
|
||||
- Are customizable to your hardware, operating system, software, and security requirements.
|
||||
- Don't need to have a clean instance for every job execution.
|
||||
|
||||
@@ -32,7 +32,7 @@ Each solution has certain specifics that may be important to consider:
|
||||
| Runtime | Kubernetes | Linux and Windows VMs |
|
||||
| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services |
|
||||
| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
|
||||
| Pull-based autoscaling support | Yes | No |
|
||||
| How runners can be scaled | Webhook events, Scheduled, Pull-based | Webhook events, Scheduled (org-level runners only) |
|
||||
|
||||
## Using ephemeral runners for autoscaling
|
||||
|
||||
@@ -42,8 +42,8 @@ This approach allows you to manage your runners as ephemeral systems, since you
|
||||
|
||||
To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. For example:
|
||||
|
||||
```
|
||||
$ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral
|
||||
```shell
|
||||
./config.sh --url https://github.com/octo-org --token example-token --ephemeral
|
||||
```
|
||||
|
||||
The {% data variables.product.prodname_actions %} service will then automatically de-register the runner after it has processed one job. You can then create your own automation that wipes the runner after it has been de-registered.
|
||||
@@ -54,6 +54,28 @@ The {% data variables.product.prodname_actions %} service will then automaticall
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Controlling runner software updates on self-hosted runners
|
||||
|
||||
By default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available. If you use ephemeral runners in containers then this can lead to repeated software updates when a new runner version is released. Turning off automatic updates allows you to update the runner version on the container image directly on your own schedule.
|
||||
|
||||
If you want to turn off automatic software updates and install software updates yourself, you can specify the `--disableupdate` parameter when starting the runner. For example:
|
||||
|
||||
```shell
|
||||
./run.sh --disableupdate
|
||||
```
|
||||
|
||||
If you disable automatic updates, you must still update your runner version regularly. New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software. The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
|
||||
|
||||
If you disable automatic updates, you will be required to update your runner version within 30 days of a new version being made available. You may want to subscribe to notifications for releases in the [`actions/runner` repository](https://github.com/actions/runner/releases). For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#about-custom-notifications)."
|
||||
|
||||
For instructions on how to install the latest runner version, see the installation instructions for [the latest release](https://github.com/actions/runner/releases).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you do not perform a software update within 30 days, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner. In addition, if a critical security update is required, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner until it has been updated.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Using webhooks for autoscaling
|
||||
|
||||
You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads.
|
||||
|
||||
@@ -410,7 +410,7 @@ The `steps` context contains information about the steps in the current job that
|
||||
| Property name | Type | Description |
|
||||
|---------------|------|-------------|
|
||||
| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. This object contains all the properties listed below. |
|
||||
| `steps.<step_id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." |
|
||||
| `steps.<step_id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)." |
|
||||
| `steps.<step_id>.conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
|
||||
| `steps.<step_id>.outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
|
||||
| `steps.<step_id>.outputs.<output_name>` | `string` | The value of a specific output. |
|
||||
|
||||
@@ -47,6 +47,8 @@ Puedes buscar acciones manualmente o por coincidencia exacta directamente en el
|
||||
|
||||
Puedes agregar una acción a tu flujo de trabajo si la referencias en tu archivo de flujo de trabajo.
|
||||
|
||||
You can view the actions referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
|
||||
|
||||
### Agregar una acción desde {% data variables.product.prodname_marketplace %}
|
||||
|
||||
La página de descripción de una acción incluye la versión de la acción y la sintaxis de flujo de trabajo que se necesita para usar la acción. Para mantener estable a tu flujo de trabajo, aún cuando se hagan actualizaciones en una acción, puedes referenciar la versión de la acción a utilizar si especificas el número de etiqueta de Git o de Docker en tu archivo de flujo de trabajo.
|
||||
|
||||
@@ -255,3 +255,8 @@ Para entender cómo funciona la facturación de las {% data variables.product.pr
|
||||
## Contactar con soporte técnico
|
||||
|
||||
{% data reusables.github-actions.contacting-support %}
|
||||
|
||||
## Leer más
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"{% endif %}
|
||||
|
||||
@@ -63,7 +63,7 @@ Jenkins utiliza directivas para administrar los _Mapas Declarativos_. Estas dire
|
||||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
|
||||
| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
|
||||
| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) |
|
||||
| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions) |
|
||||
| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore) <br> [<code>on.<pull_request\>.<branches\></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) |
|
||||
| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) |
|
||||
| [Sintaxis de Jenkins cron](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax) | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule) |
|
||||
|
||||
@@ -1187,7 +1187,7 @@ on:
|
||||
| ------------------------------------------ | ------------------ | ------------------------------------------ | ------------------------------------------ |
|
||||
| El mismo que el flujo de trabajo que llama | n/a | El mismo que el flujo de trabajo que llama | El mismo que el flujo de trabajo que llama |
|
||||
|
||||
`workflow_call` se utiliza para indicar que un flujo de trabajo puede llamar a otro. Cuando se activa un flujo de trabajo con el evento `workflow_call`, la carga útil del evento en el flujo de trabajo llamado es la misma del flujo de trabajo llamante. Para obtener más información, consulta la sección "[Reutilizar los flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".
|
||||
`workflow_call` se utiliza para indicar que un flujo de trabajo puede llamar a otro. When a workflow is triggered with the `workflow_call` event, the event payload in the called workflow is the same event payload from the calling workflow. Para obtener más información, consulta la sección "[Reutilizar los flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".
|
||||
|
||||
El siguiente ejemplo solo ejecuta el flujo de trabajo cuando se le llama desde otro flujo de trabajo:
|
||||
|
||||
|
||||
@@ -34,6 +34,8 @@ Si utilizas un flujo de trabajo desde un repositorio diferente, cualquier acció
|
||||
|
||||
Cuando un flujo de trabajo llamante activa uno reutilizable, el contexto `github` siempre se asocia con el flujo llamante. Se otorga acceso automáticamente al flujo de trabajo llamado para `github.token` y `secrets.GITHUB_TOKEN`. Para obtener más información sobre el contexto `github`, consulta la sección "[Sintaxis de contexto y expresión para GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
|
||||
|
||||
You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
|
||||
|
||||
### Flujos de trabajo reutilizables e iniciales
|
||||
|
||||
Los flujos de trabajo iniciales permiten que toda persona en tu organización que tenga permiso para crear flujos de trabajo lo haga de forma más fácil y rápida. Cuando las personas crean un flujo de trabajo nuevo, pueden elegir un flujo de trabajo inicial y parte o todo el trabajo de escribir dicho flujo de trabajo se hará automáticamente. Dentro de un flujo de trabajo inicial, también puedes referenciar los flujos de trabajo reutilizables para hacer más fácil que las personas se beneficien de reutilizar el código de flujo de trabajo que se administra centralmente. Si utilizas un nombre de rama o etiqueta cuando referencias el flujo de trabajo reutilizable, puedes garantizar que todo aquél que reutilice ese flujo de trabajo siempre estará utilizando el mismo código de YAML. Sin embargo, si referencias un flujo de trabajo reutilizable mediante una etiqueta o rama, asegúrate de que puedas confiar en esa versión del flujo de trabajo. Para obtener más información, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)".
|
||||
|
||||
@@ -92,7 +92,7 @@ La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles
|
||||
|
||||
Establece un parámetro de salida de la acción.
|
||||
|
||||
Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)".
|
||||
Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."
|
||||
|
||||
### Ejemplo
|
||||
|
||||
@@ -292,7 +292,7 @@ El paso anterior imprime las siguientes líneas en la bitácora:
|
||||
|
||||
Puedes utilizar el comando `save-state` para crear variables de ambiente para compartir con tus acciones `pre:` o `post:` de flujo de trabajo. Por ejemplo, puedes crear un archivo con la acción `pre:`, pasar la ubicación del archivo a la acción `main:`, y después, utilizar la acción `post:` para borrar el archivo. Como alternativa, puedes crear un archivo con la acción `main:`, pasar la ubicación del archivo a la acción `post:`, y también utilizar la acción `post:` para borrar el archivo.
|
||||
|
||||
Si tienes varias acciones `pre:` o `post:`, solo podrás acceder al valor que se guardó en la acción donde se utilizó `save-state`. Para obtener más información sobre la acción `post:`, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)".
|
||||
Si tienes varias acciones `pre:` o `post:`, solo podrás acceder al valor que se guardó en la acción donde se utilizó `save-state`. Para obtener más información sobre la acción `post:`, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runspost)".
|
||||
|
||||
El comando `save-state` solo puede ejecutarse dentro de una acción y no está disponible para archivos YAML. El valor guardado se almacena en un valor de ambiente con el prefijo `STATE_`.
|
||||
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: About GitHub Actions for enterprises
|
||||
shortTitle: Acerca de Acciones de GitHub
|
||||
intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Actions
|
||||
- Enterprise
|
||||
---
|
||||
|
||||
With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow.
|
||||
|
||||
| Tarea | Más información |
|
||||
| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Automatically test and build your application | "[Acerca de la integración continua](/actions/automating-builds-and-tests/about-continuous-integration)" |
|
||||
| Deploy your application | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)" |
|
||||
| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" |
|
||||
| Automate your project management tasks | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
|
||||
|
||||
{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
|
||||
|
||||
{% data variables.product.prodname_actions %} also provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. This will allow you to stop storing credentials as long-lived secrets and provide other security benefits. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
|
||||
|
||||
{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
|
||||
|
||||
You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. Para obtener más información, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions)".
|
||||
|
||||
{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
|
||||
{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. Para obtener más información, consulta la sección "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
|
||||
|
||||
|
||||
To learn more about how you can successfully adopt {% data variables.product.prodname_actions %} for your enterprise, follow the "[Adopt {% data variables.product.prodname_actions %} for your enterprise](/admin/guides#adopt-github-actions-for-your-enterprise)" learning path.
|
||||
|
||||
## Leer más
|
||||
|
||||
- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
|
||||
- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
|
||||
@@ -9,6 +9,7 @@ topics:
|
||||
- Enterprise
|
||||
- Actions
|
||||
children:
|
||||
- /about-github-actions-for-enterprises
|
||||
- /introducing-github-actions-to-your-enterprise
|
||||
- /migrating-your-enterprise-to-github-actions
|
||||
- /getting-started-with-github-actions-for-github-enterprise-cloud
|
||||
|
||||
@@ -14,7 +14,7 @@ topics:
|
||||
|
||||
## About {% data variables.product.prodname_actions %} for enterprises
|
||||
|
||||
{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
|
||||
{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -178,7 +178,7 @@ Puedes ver la lista completa de usuarios LDAP que tienen acceso a tu instancia y
|
||||
{% data reusables.enterprise_site_admin_settings.sign-in %}
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
3. En la barra lateral izquierda, haz clic en **LDAP users** (Usuarios LDAP). 
|
||||
4. Para buscar un usuario, escribe un nombre de usuario completo o parcial y haz clic en **Search** (Buscar). Se mostrarán los usuarios existentes en los resultados de búsqueda. Si un usuario no existe, haz clic en **Create** (Crear) para aprovisionar la nueva cuenta de usuario. 
|
||||
4. Para buscar un usuario, escribe un nombre de usuario completo o parcial y haz clic en **Search** (Buscar). Se mostrarán los usuarios existentes en los resultados de búsqueda. Si un usuario no existe, haz clic en **Create** (Crear) para aprovisionar la nueva cuenta de usuario. 
|
||||
|
||||
## Actualizar cuentas LDAP
|
||||
|
||||
|
||||
@@ -47,6 +47,7 @@ Probamos y damos compatibilidad oficial de los siguientes IdP. Para el SSO de SA
|
||||
| -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
|
||||
| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | |
|
||||
| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}
|
||||
| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}
|
||||
| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
|
||||
| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
|
||||
| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
|
||||
|
||||
@@ -22,12 +22,10 @@ shortTitle: Registro de seguridad
|
||||
La bitácora de seguridad lista todas las acciones que se llevaron a cabo en los últimos 90 días.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
2. En la barra lateral de la configuración de usuario, da clic en **Registro de Seguridad**. 
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
|
||||
{% else %}
|
||||
{% data reusables.user_settings.security %}
|
||||
3. En "Security history" (Historial de seguridad) se muestra tu registro. 
|
||||
4. Haz clic en la entrada para ver más información acerca del evento. 
|
||||
1. En la barra lateral de la configuración de usuario, da clic en **Registro de Seguridad**. 
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
|
||||
@@ -37,6 +37,10 @@ Si quieres ver un resumen de tu uso y suscripción de {% data variables.product.
|
||||
|
||||
## Ver la suscripción y el uso de tu cuenta de empresa
|
||||
|
||||
You can view the subscription and usage for your enterprise and download a file with license details.
|
||||
|
||||
{% data reusables.billing.license-statuses %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.license-tab %}
|
||||
|
||||
@@ -36,7 +36,7 @@ Si eres un propietario de empresa y organización, puedes cambiar entre los ajus
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
1. En la parte superior de la lágina, a la derecha de tu nombre de usuario, haz clic en **Cambiar a otra cuenta**. 
|
||||
1. Comienza a teclear el nombre de la cuenta a la que quieres cambiar y luego haz clic en su nombre. 
|
||||
1. En la barra lateral izquierda, haz clic en **Facturación & planes**. 
|
||||
1. In the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
|
||||
## Leer más
|
||||
|
||||
|
||||
@@ -30,6 +30,10 @@ Puedes ver el uso de licencia de {% data variables.product.prodname_ghe_server %
|
||||
|
||||
## Ver el uso de licencia en {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}
|
||||
|
||||
You can view the license usage for your enterprise and download a file with license details.
|
||||
|
||||
{% data reusables.billing.license-statuses %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
|
||||
|
||||
@@ -166,7 +166,7 @@ codeql database analyze <database> --format=<format> \
|
||||
| Option | Required | Usage |
|
||||
|--------|:--------:|-----|
|
||||
| `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. |
|
||||
| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
|
||||
| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/qlpacks/codeql/<language>-queries/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
|
||||
| <nobr>`--format`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae or ghec %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
|
||||
| <nobr>`--output`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| <nobr>`--sarif-category`<nobr> | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
|
||||
|
||||
@@ -42,7 +42,7 @@ El equipo de seguridad de aplicaciones en tu compañía puede utilizar el resume
|
||||
|
||||
En el resumen de seguridad, puedes ver, clasificar y filtrar las alertas para entender los riesgos de seguridad en tu organización y en los repositorios específicos. El resumen de seguridad es altamente interactivo, lo cual te permite investigar las categorías de información específicas con base en los calificadores como nivel de riesgo de alerta, tipo de alerta y habilitación de características. También puedes aplicar filtros múltiples para enfocarte en áreas de interés más específicas. Por ejemplo, puedes identificar repositorios privados que tengan una gran cantidad de {% data variables.product.prodname_dependabot_alerts %} o repositorios que no tengan alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Filtrar las alertas en el resumen de seguridad](/code-security/security-overview/filtering-alerts-in-the-security-overview)".
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 %}
|
||||
{% if security-overview-views %}
|
||||
|
||||
En el resumen de seguridad, tanto a nivel de repositorio como de organización, hay vistas dedicadas para las características de seguridad específicas, tales como alertas de escaneo de secretos y de escaneo de código. Puedes utilizar estas vistas para limitar tu análisis a un conjunto de alertas específico y reducirlos aún más con un rango de filtros específico para cada vista. Por ejemplo, en la vista de alertas del escaneo de secretos, puedes utilizar el filtro `Secret type` para ver solo las alertas de escaneo de secretos para un secreto específico, como un Token de Acceso Personal de GitHub. A nivel de repositorio, puedes utilizar el resumen de seguridad para valorar el estado de seguridad actual del repositorio específico y configurar cualquier característica de seguridad adicional que no esté utilizando el repositorio.
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@ permissions: Organization owners and security managers can access the security o
|
||||
product: '{% data reusables.gated-features.security-center %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: issue-4554
|
||||
ghes: '>3.1'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
@@ -99,7 +100,7 @@ Disponible en el resumen a nivel organizacional.
|
||||
| ------------------------- | ------------------------------------------------------------ |
|
||||
| <code>topic:<em>TOPIC-NAME</em></code> | Muestra los repositorios que se clasifican con *TOPIC-NAME*. |
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 %}
|
||||
{% if security-overview-views %}
|
||||
|
||||
## Filter by severity
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@ permissions: Organization owners and security managers can access the security o
|
||||
product: '{% data reusables.gated-features.security-center %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: issue-5503
|
||||
ghes: '>3.1'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
@@ -25,7 +26,7 @@ shortTitle: View the security overview
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. Para ver la información agregada sobre los tipos de alerta, haz clic en **Mostrar más**. 
|
||||
{% data reusables.organizations.filter-security-overview %}
|
||||
{% ifversion ghec or ghes > 3.4 %}
|
||||
{% if security-overview-views %}
|
||||
1. Alternatively and optionally, use the sidebar on the left to filter information per security feature. On each page, you can use filters that are specific to each feature to fine-tune your search. 
|
||||
|
||||
## Viewing alerts across your organization
|
||||
|
||||
@@ -27,7 +27,9 @@ shortTitle: Configuration options
|
||||
|
||||
The {% data variables.product.prodname_dependabot %} configuration file, *dependabot.yml*, uses YAML syntax. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
|
||||
|
||||
You must store this file in the `.github` directory of your repository. When you add or update the *dependabot.yml* file, this triggers an immediate check for version updates. Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
|
||||
You must store this file in the `.github` directory of your repository. When you add or update the *dependabot.yml* file, this triggers an immediate check for version updates. For more information and an example, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)."
|
||||
|
||||
Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
|
||||
|
||||
The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key. The file must start with `version: 2`.
|
||||
|
||||
@@ -490,9 +492,9 @@ updates:
|
||||
|
||||
### `registries`
|
||||
|
||||
To allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you must include a `registries` setting within the relevant `updates` configuration. You can allow all of the defined registries to be used by setting `registries` to `"*"`. Alternatively, you can list the registries that the update can use. To do this, use the name of the registry as defined in the top-level `registries` section of the _dependabot.yml_ file.
|
||||
To allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you must include a `registries` setting within the relevant `updates` configuration. You can allow all of the defined registries to be used by setting `registries` to `"*"`. Alternatively, you can list the registries that the update can use. To do this, use the name of the registry as defined in the top-level `registries` section of the _dependabot.yml_ file. For more information, see "[Configuration options for private registries](#configuration-options-for-private-registries)" below.
|
||||
|
||||
To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution).
|
||||
To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above.
|
||||
|
||||
```yaml
|
||||
# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries
|
||||
|
||||
@@ -38,7 +38,7 @@ Dependency review is available when dependency graph is enabled for {% data vari
|
||||
|
||||
Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities.
|
||||
|
||||
By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)."
|
||||
By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix problems at a later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
|
||||
@@ -77,6 +77,9 @@ The recommended formats explicitly define which versions are used for all direct
|
||||
| --- | --- | --- | ---|
|
||||
| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` |
|
||||
| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
|
||||
{%- if github-actions-in-dependency-graph %}
|
||||
| {% data variables.product.prodname_actions %} workflows<sup>[1]</sup> | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` |
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghes > 3.2 or ghae %}
|
||||
| Go modules | Go | `go.sum` | `go.mod`, `go.sum` |
|
||||
{%- elsif ghes = 3.2 %}
|
||||
@@ -84,18 +87,28 @@ The recommended formats explicitly define which versions are used for all direct
|
||||
{%- endif %}
|
||||
| Maven | Java, Scala | `pom.xml` | `pom.xml` |
|
||||
| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`|
|
||||
| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* |
|
||||
| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
|
||||
{%- ifversion fpt or ghes > 3.3 %}
|
||||
| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
|
||||
| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
|
||||
| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
|
||||
|
||||
{% if github-actions-in-dependency-graph %}
|
||||
[1] Please note that {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions)."
|
||||
|
||||
[2] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
|
||||
|
||||
{% else %}
|
||||
[1] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
|
||||
{% endif %}
|
||||
|
||||
{% if github-actions-in-dependency-graph %}
|
||||
{% note %}
|
||||
|
||||
**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
|
||||
**Note:** {% data variables.product.prodname_actions %} workflow dependencies are displayed in the dependency graph for informational purposes. Dependabot alerts are not currently supported for {% data variables.product.prodname_actions %} workflows.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
## Further reading
|
||||
|
||||
- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
|
||||
|
||||
@@ -12,7 +12,7 @@ shortTitle: Registro de imagen privado
|
||||
|
||||
## Acerca de los registros de imagen y {% data variables.product.prodname_codespaces %} privados
|
||||
|
||||
Un registro es un espacio seguro para almacenar, administrar y recuperar imágenes de contenedor privadas. Puedes utilizar uno de ellos para almacenar uno o más devcontainers. Hay muchos ejemplos de registros, tales como el Registro de Contenedores de {% data variables.product.prodname_dotcom %}, Registro de Contenedores de Azure o DockerHub.
|
||||
Un registro es un espacio seguro para almacenar, administrar y recuperar imágenes de contenedor privadas. You may use one to store one or more images. Hay muchos ejemplos de registros, tales como el Registro de Contenedores de {% data variables.product.prodname_dotcom %}, Registro de Contenedores de Azure o DockerHub.
|
||||
|
||||
El Registro de Contenedores de {% data variables.product.prodname_dotcom %} puede configurarse para extraer imágenes de contenedor sin problemas, sin tener que proporcionar credenciales de autenticación a {% data variables.product.prodname_codespaces %}. Para otros registros de imágenes, debes crear secretos en {% data variables.product.prodname_dotcom %} para almacenar los detalles de acceso, los cuales permitirán que los {% data variables.product.prodname_codespaces %} accedan a las imágenes almacenadas en dicho registro.
|
||||
|
||||
@@ -87,7 +87,7 @@ Para acceder a AWS Elastic Container Registry (ECR), puedes proporcionar una ID
|
||||
```
|
||||
*_CONTAINER_REGISTRY_SERVER = <ECR_URL>
|
||||
*_CONTAINER_REGISTRY_USER = <AWS_ACCESS_KEY_ID>
|
||||
*_container_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
|
||||
*_CONTAINER_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
|
||||
```
|
||||
|
||||
Debes de asegurarte de que tengas los permisos adecuados de AWS IAM para realizar el cambio de credenciales (por ejemplo: `sts:GetServiceBearerToken`), así como la operación de lectura de ECR (ya sea `AmazonEC2ContainerRegistryFullAccess` o `ReadOnlyAccess`).
|
||||
@@ -97,7 +97,7 @@ Como alternativa, si no quieres que GitHub realice el cambio de credenciales en
|
||||
```
|
||||
*_CONTAINER_REGISTRY_SERVER = <ECR_URL>
|
||||
*_CONTAINER_REGISTRY_USER = AWS
|
||||
*_container_REGISTRY_PASSWORD = <TOKEN>
|
||||
*_CONTAINER_REGISTRY_PASSWORD = <TOKEN>
|
||||
```
|
||||
|
||||
Ya que estos tokens tienen una vida corta y necesitan actualizarse constantemente, te recomendamos proporcionar una ID de llave de acceso y secreto.
|
||||
|
||||
@@ -41,12 +41,11 @@ Para crear secretos para un repositorio de la organización, debes tener acceso
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.github-actions.sidebar-secret %}
|
||||
1. Navega hacia la parte inferior de la página y, debajo de **Secretos**, selecciona **Codespaces**. 
|
||||
1. En la parte superior de la página, haz clci en **Secreto de repositorio nuevo**.
|
||||
1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
|
||||
1. Ingresa el valor de tu secreto.
|
||||
1. Haz clic en **Agregar secreto** (Agregar secreto).
|
||||
1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
|
||||
2. En la parte superior de la página, haz clci en **Secreto de repositorio nuevo**.
|
||||
3. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
|
||||
4. Ingresa el valor de tu secreto.
|
||||
5. Haz clic en **Agregar secreto** (Agregar secreto).
|
||||
|
||||
## Agregar secretos para una organización
|
||||
|
||||
@@ -56,13 +55,12 @@ Cuando creas un secreto en una organización, puedes utilizar una política para
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.github-actions.sidebar-secret %}
|
||||
1. Navega hacia la parte inferior de la página y, debajo de **Secretos**, selecciona **Codespaces**. 
|
||||
1. En la parte superior de la página, haz clic en **Nuego secreto de organización**.
|
||||
1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
|
||||
1. Ingresa el **Valor** para tu secreto.
|
||||
1. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. 
|
||||
1. Haz clic en **Agregar secreto** (Agregar secreto).
|
||||
1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
|
||||
2. En la parte superior de la página, haz clic en **Nuego secreto de organización**.
|
||||
3. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
|
||||
4. Ingresa el **Valor** para tu secreto.
|
||||
5. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. 
|
||||
6. Haz clic en **Agregar secreto** (Agregar secreto).
|
||||
|
||||
## Revisar el acceso a los secretos de nivel organizacional
|
||||
|
||||
|
||||
@@ -47,38 +47,34 @@ If you add an organization-wide policy, you should set it to the largest choice
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.click-codespaces %}
|
||||
1. Under "Codespaces", click **Policy**.
|
||||
|
||||
|
||||
|
||||
1. On the "Codespace policies" page, click **Create Policy**.
|
||||
1. Enter a name for your new policy.
|
||||
1. Click **Add constraint** and choose **Machine types**.
|
||||
1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policy**.
|
||||
2. On the "Codespace policies" page, click **Create Policy**.
|
||||
3. Enter a name for your new policy.
|
||||
4. Click **Add constraint** and choose **Machine types**.
|
||||
|
||||
|
||||
|
||||
1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
|
||||
5. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
|
||||
|
||||
|
||||
|
||||
1. In the "Change policy target" area, click the dropdown button.
|
||||
1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
|
||||
1. Si eliges **Repositorios seleccionados**:
|
||||
6. In the "Change policy target" area, click the dropdown button.
|
||||
7. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
|
||||
8. Si eliges **Repositorios seleccionados**:
|
||||
1. Da clic en {% octicon "gear" aria-label="The settings icon" %}.
|
||||
|
||||
|
||||
|
||||
1. Select the repositories you want this policy to apply to.
|
||||
1. At the bottom of the repository list, click **Select repositories**.
|
||||
2. Select the repositories you want this policy to apply to.
|
||||
3. At the bottom of the repository list, click **Select repositories**.
|
||||
|
||||
|
||||
|
||||
1. Haz clic en **Save ** (guardar).
|
||||
9. Haz clic en **Save ** (guardar).
|
||||
|
||||
## Editing a policy
|
||||
|
||||
1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
|
||||
1. Muestra la página de "Políticas del Codespace". Para obtener más información, consulta la sección "[Agregar una política para limitar los tipos de máquina disponibles](#adding-a-policy-to-limit-the-available-machine-types)".
|
||||
1. Click the name of the policy you want to edit.
|
||||
1. Make the required changes then click **Save**.
|
||||
|
||||
|
||||
@@ -33,7 +33,7 @@ Si seleccionaste una cantidad de tiempo específica para bloquear al usuario, se
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.moderation-settings %}
|
||||
{% data reusables.organizations.moderation-settings %}, then click **Blocked users**.
|
||||
5. En "Blocked users" (Usuarios bloqueados), al lado del usuario que quieres desbloquear, haz clic en **Unblock** (Desbloquear). 
|
||||
|
||||
## Leer más
|
||||
|
||||
@@ -33,8 +33,7 @@ Los propietarios de la organización también pueden bloquear a los usuarios por
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. Enla barra lateral de configuración de la organización, da clic en **Configuración de moderación**. 
|
||||
1. Debajo de "Configuración de moderación", da clic en **Límites de interacción**. 
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**.
|
||||
{% data reusables.community.set-interaction-limit %}
|
||||
|
||||
|
||||
|
||||
@@ -28,8 +28,7 @@ También puedes habilitar los límites de actividad en todos los repositorios qu
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. En la barra lateral izquierda, da clic en **Configuración de moderación**. 
|
||||
1. Debajo de "Configuración de moderación", da clic en **Límites de interacción**. 
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**.
|
||||
{% data reusables.community.set-interaction-limit %}
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,641 @@
|
||||
---
|
||||
title: Common validation errors when creating issue forms
|
||||
intro: 'You may see some of these common validation errors when creating, saving, or viewing issue forms.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Community
|
||||
---
|
||||
|
||||
<!--UI-LINK: We link to individual anchors within this file from the issue template editor when the given YAML error is thrown. Links to and anchors within this file should be preserved or should be updated in github/github if they are changed -->
|
||||
{% data reusables.community.issue-forms-beta %}
|
||||
|
||||
## Required top level key `name` is missing
|
||||
|
||||
The template does not contain a `name` field, which means it is not clear what to call your issue template when giving users a list of options.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
description: "Thank you for reporting a bug!"
|
||||
...
|
||||
```
|
||||
|
||||
The error can be fixed by adding `name` as a key.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
description: "Thank you for reporting a bug!"
|
||||
...
|
||||
```
|
||||
|
||||
## `key` must be a string
|
||||
|
||||
This error message means that a permitted key has been provided, but its value cannot be parsed as the data type is not supported.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
The `description` below is being parsed as a Boolean, but it should be a string.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
description: true
|
||||
...
|
||||
```
|
||||
|
||||
The error can be fixed by providing a string as the value. Strings may need to be wrapped in double quotes to be successfully parsed. For example, strings that contain `'` must be wrapped in double quotes.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
description: "true"
|
||||
...
|
||||
```
|
||||
|
||||
Empty strings, or strings consisting of only whitespaces, are also not permissible when the field expects a string.
|
||||
|
||||
```yaml
|
||||
name: ""
|
||||
description: "File a bug report"
|
||||
assignees: " "
|
||||
...
|
||||
```
|
||||
|
||||
The error can be fixed by correcting the value to be a non-empty string. If the field is not required, you should delete the key-value pair.
|
||||
|
||||
```yaml
|
||||
name: "Bug Report"
|
||||
description: "File a bug report"
|
||||
...
|
||||
```
|
||||
|
||||
## `input` is not a permitted key
|
||||
|
||||
An unexpected key was supplied at the top level of the template. For more information about which top-level keys are supported, see "[Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax)."
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
hello: world
|
||||
...
|
||||
```
|
||||
|
||||
The error can be fixed by removing the unexpected keys.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
...
|
||||
```
|
||||
|
||||
## Forbidden keys
|
||||
|
||||
YAML parses certain strings as `Boolean` values. To avoid this, we have explicitly forbidden the usage of the following keys:
|
||||
|
||||
`y`, `Y`, `yes`, `Yes`, `YES`, `n`, `N`, `no`, `No`, `NO`, `true`, `True`, `TRUE`, `false`, `False`, `FALSE`, `on`, `On`, `ON`, `off`, `Off`, `OFF`
|
||||
|
||||
The error can be fixed by removing the forbidden keys.
|
||||
|
||||
## Body must contain at least one non-markdown field
|
||||
|
||||
Issue forms must accept user input, which means that at least one of its fields must contain a user input field. A `markdown` element is static text, so a `body` array cannot contain only `markdown` elements.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Bugs are the worst!"
|
||||
```
|
||||
|
||||
The error can be fixed by adding non-markdown elements that accept user input.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Bugs are the worst!"
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: "What's wrong?"
|
||||
```
|
||||
|
||||
## Body must have unique ids
|
||||
|
||||
If using `id` attributes to distinguish multiple elements, each `id` attribute must be unique.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: input
|
||||
id: name
|
||||
attributes:
|
||||
label: First name
|
||||
- type: input
|
||||
id: name
|
||||
attributes:
|
||||
label: Last name
|
||||
```
|
||||
|
||||
The error can be fixed by changing the `id` for one of these inputs, so that every `input` field has a unique `id` attribute.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: input
|
||||
id: name
|
||||
attributes:
|
||||
label: First name
|
||||
- type: input
|
||||
id: surname
|
||||
attributes:
|
||||
label: Last name
|
||||
```
|
||||
|
||||
## Body must have unique labels
|
||||
|
||||
When there are multiple `body` elements that accept user input, the `label` attribute for each user input field must be unique.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Name
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Name
|
||||
```
|
||||
|
||||
The error can be fixed by changing the `label` attribute for one of the input fields to ensure that each `label` is unique.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Name
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Operating System
|
||||
```
|
||||
|
||||
Input fields can also be differentiated by their `id` attribute. If duplicate `label` attributes are required, you can supply at least one `id` to differentiate two elements with identical labels.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: textarea
|
||||
id: name_1
|
||||
attributes:
|
||||
label: Name
|
||||
- type: textarea
|
||||
id: name_2
|
||||
attributes:
|
||||
label: Name
|
||||
```
|
||||
|
||||
`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
|
||||
|
||||
|
||||
## Labels are too similar
|
||||
|
||||
Similar labels may be processed into identical references. If an `id` attribute is not provided for an `input`, the `label` attribute is used to generate a reference to the `input` field. To do this, we process the `label` by leveraging the Rails [parameterize](https://apidock.com/rails/ActiveSupport/Inflector/parameterize) method. In some cases, two labels that are distinct can be processed into the same parameterized string.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: input
|
||||
attributes:
|
||||
label: Name?
|
||||
- type: input
|
||||
id: name
|
||||
attributes:
|
||||
label: Name???????
|
||||
```
|
||||
|
||||
The error can be fixed by adding at least one differentiating alphanumeric character, `-`, or `_` to one of the clashing labels.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: input
|
||||
attributes:
|
||||
label: Name?
|
||||
- type: input
|
||||
attributes:
|
||||
label: Your name
|
||||
```
|
||||
|
||||
The error can also be fixed by giving one of the clashing labels a unique `id`.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: input
|
||||
attributes:
|
||||
label: Name?
|
||||
- type: input
|
||||
id: your-name
|
||||
attributes:
|
||||
label: Name???????
|
||||
```
|
||||
|
||||
## Checkboxes must have unique labels
|
||||
|
||||
When a `checkboxes` element is present, each of its nested labels must be unique among its peers, as well as among other input types.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Name
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
options:
|
||||
- label: Name
|
||||
```
|
||||
|
||||
The error can be fixed by changing the `label` attribute for one of these inputs.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Name
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
options:
|
||||
- label: Your name
|
||||
```
|
||||
|
||||
Alternatively, you can supply an `id` to any clashing top-level elements. Nested checkbox elements do not support the `id` attribute.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: textarea
|
||||
id: name_1
|
||||
attributes:
|
||||
label: Name
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
options:
|
||||
- label: Name
|
||||
```
|
||||
|
||||
`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
|
||||
|
||||
## Body[i]: required key type is missing
|
||||
|
||||
Each body block must contain the key `type`.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the zero-indexed index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
preview_only: false
|
||||
```
|
||||
|
||||
The error can be fixed by adding the key `type` with a valid input type as the value. Para los tipos de entrada de `body` disponibles y sus sintaxis, consulta la sección "[Sintaxis para el modelo de formato de {% data variables.product.prodname_dotcom %}](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys)".
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
preview_only: false
|
||||
```
|
||||
|
||||
## Body[i]: `x` is not a valid input type
|
||||
|
||||
One of the body blocks contains a type value that is not one of the [permitted types](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys).
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: x
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
preview_only: false
|
||||
```
|
||||
|
||||
The error can be fixed by changing `x` to one of the valid types.
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
preview_only: false
|
||||
```
|
||||
|
||||
## Body[i]: required attribute key `value` is missing
|
||||
|
||||
One of the required `value` attributes has not been provided. The error occurs when a block does not have an `attributes` key or does not have a `value` key under the `attributes` key.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
preview_only: false
|
||||
- type: markdown
|
||||
```
|
||||
|
||||
The error in this example can be fixed by adding `value` as a key under `attributes` in the second list element of `body`.
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
preview_only: false
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "This is working now!"
|
||||
```
|
||||
|
||||
## Body[i]: label must be a string
|
||||
|
||||
Within its `attributes` block, a value has the wrong data type.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
The `label` below is being parsed as a Boolean, but it should be a string.
|
||||
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Bug Description
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: true
|
||||
```
|
||||
|
||||
The error can be fixed by supplying a string value for `label`. If you want to use a `label` value that may be parsed as a Boolean, integer, or decimal, you should wrap the value in quotes. For example, `"true"` or `"1.3"` instead of `true` or `1.3`.
|
||||
|
||||
```yaml
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Bug Description
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Environment Details
|
||||
```
|
||||
|
||||
Empty strings, or strings consisting of only whitespaces, are not permissible when an attribute expects a string. For example, `""` or `" "` are not allowed.
|
||||
|
||||
If the attribute is required, the value must be a non-empty string. If the field is not required, you should delete the key-value pair.
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: input
|
||||
attributes:
|
||||
label: "Name"
|
||||
```
|
||||
|
||||
## Body[i]: `id` can only contain numbers, letters, -, _
|
||||
|
||||
`id` attributes can only contain alphanumeric characters, `-`, and `_`. Your template may include non-permitted characters, such as whitespace, in an `id`.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: input
|
||||
id: first name
|
||||
attributes:
|
||||
label: First name
|
||||
```
|
||||
|
||||
The error can be fixed by ensuring that whitespaces and other non-permitted characters are removed from `id` values.
|
||||
|
||||
```yaml
|
||||
name: "Bug report"
|
||||
body:
|
||||
- type: input
|
||||
id: first-name
|
||||
attributes:
|
||||
label: First name
|
||||
```
|
||||
|
||||
## Body[i]: `x` is not a permitted key
|
||||
|
||||
An unexpected key, `x`, was provided at the same indentation level as `type` and `attributes`.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
x: woof
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
```
|
||||
|
||||
The error can be fixed by removing extra keys and only using `type`, `attributes`, and `id`.
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
|
||||
```
|
||||
|
||||
## Body[i]: `label` contains forbidden word
|
||||
|
||||
To minimize the risk of private information and credentials being posted publicly in GitHub Issues, some words commonly used by attackers are not permitted in the `label` of input or textarea elements.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: Hello world!
|
||||
- type: input
|
||||
attributes:
|
||||
label: Password
|
||||
```
|
||||
|
||||
The error can be fixed by removing terms like "password" from any `label` fields.
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: Hello world!
|
||||
- type: input
|
||||
attributes:
|
||||
label: Username
|
||||
```
|
||||
|
||||
## Body[i]: `x` is not a permitted attribute
|
||||
|
||||
An invalid key has been supplied in an `attributes` block.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
x: "a random key!"
|
||||
value: "Thanks for taking the time to fill out this bug!"
|
||||
```
|
||||
|
||||
The error can be fixed by removing extra keys and only using permitted attributes.
|
||||
|
||||
```yaml
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: "Thanks for taking the time to fill out this bug!"
|
||||
```
|
||||
|
||||
## Body[i]: `options` must be unique
|
||||
|
||||
For checkboxes and dropdown input types, the choices defined in the `options` array must be unique.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```
|
||||
body:
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: Favorite dessert
|
||||
options:
|
||||
- ice cream
|
||||
- ice cream
|
||||
- pie
|
||||
```
|
||||
|
||||
The error can be fixed by ensuring that no duplicate choices exist in the `options` array.
|
||||
|
||||
```
|
||||
body:
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: Favorite dessert
|
||||
options:
|
||||
- ice cream
|
||||
- pie
|
||||
```
|
||||
|
||||
## Body[i]: `options` must not include the reserved word, none
|
||||
|
||||
"None" is a reserved word in an `options` set because it is used to indicate non-choice when a `dropdown` is not required.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```
|
||||
body:
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: What types of pie do you like?
|
||||
options:
|
||||
- Steak & Ale
|
||||
- Chicken & Leek
|
||||
- None
|
||||
validations:
|
||||
required: true
|
||||
```
|
||||
|
||||
The error can be fixed by removing "None" as an option. If you want a contributor to be able to indicate that they like none of those types of pies, you can additionally remove the `required` validation.
|
||||
|
||||
```
|
||||
body:
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: What types of pie do you like?
|
||||
options:
|
||||
- Steak & Ale
|
||||
- Chicken & Leek
|
||||
```
|
||||
|
||||
In this example, "None" will be auto-populated as a selectable option.
|
||||
|
||||
## Body[i]: `options` must not include booleans. Please wrap values such as 'yes', and 'true' in quotes
|
||||
|
||||
There are a number of English words that become processed into Boolean values by the YAML parser unless they are wrapped in quotes. For dropdown `options`, all items must be strings rather than Booleans.
|
||||
|
||||
Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
|
||||
|
||||
### Ejemplo
|
||||
|
||||
```
|
||||
body:
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: Do you like pie?
|
||||
options:
|
||||
- Yes
|
||||
- No
|
||||
- Maybe
|
||||
```
|
||||
|
||||
The error can be fixed by wrapping each offending option in quotes, to prevent them from being processed as Boolean values.
|
||||
|
||||
```
|
||||
body:
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: Do you like pie?
|
||||
options:
|
||||
- "Yes"
|
||||
- "No"
|
||||
- Maybe
|
||||
```
|
||||
|
||||
## Leer más
|
||||
|
||||
- [YAML](https://yaml.org/)
|
||||
- [Sintaxis para formatos de propuesta](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)
|
||||
@@ -21,5 +21,6 @@ children:
|
||||
- /syntax-for-githubs-form-schema
|
||||
- /creating-a-pull-request-template-for-your-repository
|
||||
- /manually-creating-a-single-issue-template-for-your-repository
|
||||
- /common-validation-errors-when-creating-issue-forms
|
||||
---
|
||||
|
||||
|
||||
@@ -241,7 +241,7 @@ Puedes utilizar el elemento de `checkboxes` para agregar un conjunto de casillas
|
||||
|
||||
| Clave | Descripción | Requerido | Tipo | Predeterminado | Valores válidos |
|
||||
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- |
|
||||
| `etiqueta` | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
|
||||
| `etiqueta` | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
|
||||
| `descripción` | 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. | Opcional | Secuencia | Secuencia 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. | Requerido | Arreglo | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
|
||||
|
||||
|
||||
@@ -165,3 +165,4 @@ body:
|
||||
## Further reading
|
||||
|
||||
- [YAML](https://yaml.org/)
|
||||
- [Common validation errors when creating issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms)
|
||||
|
||||
@@ -53,7 +53,7 @@ La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Ha
|
||||
|
||||
1. Agregar una URL remota nueva que apunte a un proyecto por separado en el que estemos interesados.
|
||||
```shell
|
||||
$ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
|
||||
$ git remote add -f spoon-knife https://github.com/octocat/Spoon-Knife.git
|
||||
> Updating spoon-knife
|
||||
> warning: no common commits
|
||||
> remote: Counting objects: 1732, done.
|
||||
@@ -61,7 +61,7 @@ La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Ha
|
||||
> remote: Total 1732 (delta 1086), reused 1558 (delta 967)
|
||||
> Receiving objects: 100% (1732/1732), 528.19 KiB | 621 KiB/s, done.
|
||||
> Resolving deltas: 100% (1086/1086), done.
|
||||
> From git://github.com/octocat/Spoon-Knife
|
||||
> From https://github.com/octocat/Spoon-Knife
|
||||
> * [new branch] main -> Spoon-Knife/main
|
||||
```
|
||||
2. Fusionar el proyecto `Spoon-Knife` en el proyecto de Git local. Esto no modifica ninguno de tus archivos localmente, pero prepara Git para el siguiente paso.
|
||||
|
||||
@@ -29,45 +29,45 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>s</kbd> or <kbd>/</kbd> | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
|
||||
|<kbd>g</kbd> <kbd>n</kbd> | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
|
||||
|<kbd>esc</kbd> | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in
|
||||
{% if command-palette %}|<kbd>control</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
|
||||
|<kbd>S</kbd> or <kbd>/</kbd> | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
|
||||
|<kbd>G</kbd> <kbd>N</kbd> | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
|
||||
|<kbd>Esc</kbd> | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in
|
||||
{% if command-palette %}|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
|
||||
|
||||
## Repositories
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>g</kbd> <kbd>c</kbd> | Go to the **Code** tab
|
||||
|<kbd>g</kbd> <kbd>i</kbd> | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)."
|
||||
|<kbd>g</kbd> <kbd>p</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
|
||||
|<kbd>g</kbd> <kbd>a</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
|
||||
|<kbd>g</kbd> <kbd>b</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."
|
||||
|<kbd>g</kbd> <kbd>w</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
|
||||
|<kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
|
||||
|<kbd>G</kbd> <kbd>C</kbd> | Go to the **Code** tab
|
||||
|<kbd>G</kbd> <kbd>I</kbd> | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)."
|
||||
|<kbd>G</kbd> <kbd>P</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
|
||||
|<kbd>G</kbd> <kbd>A</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
|
||||
|<kbd>G</kbd> <kbd>B</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."
|
||||
|<kbd>G</kbd> <kbd>W</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
|
||||
|<kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
|
||||
|
||||
## Source code editing
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------{% ifversion fpt or ghec %}
|
||||
|<kbd>.</kbd>| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|
||||
| <kbd>control b</kbd> or <kbd>command b</kbd> | Inserts Markdown formatting for bolding text
|
||||
| <kbd>control i</kbd> or <kbd>command i</kbd> | Inserts Markdown formatting for italicizing text
|
||||
| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
|
||||
| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
|
||||
| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list
|
||||
| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}
|
||||
|<kbd>e</kbd> | Open source code file in the **Edit file** tab
|
||||
|<kbd>control f</kbd> or <kbd>command f</kbd> | Start searching in file editor
|
||||
|<kbd>control g</kbd> or <kbd>command g</kbd> | Find next
|
||||
|<kbd>control shift g</kbd> or <kbd>command shift g</kbd> | Find previous
|
||||
|<kbd>control shift f</kbd> or <kbd>command option f</kbd> | Replace
|
||||
|<kbd>control shift r</kbd> or <kbd>command shift option f</kbd> | Replace all
|
||||
|<kbd>alt g</kbd> | Jump to line
|
||||
|<kbd>control z</kbd> or <kbd>command z</kbd> | Undo
|
||||
|<kbd>control y</kbd> or <kbd>command y</kbd> | Redo
|
||||
|<kbd>command shift p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
|
||||
|<kbd>control s</kbd> or <kbd>command s</kbd> | Write a commit message
|
||||
|<kbd>.</kbd> | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|
||||
|<kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | Inserts Markdown formatting for bolding text
|
||||
|<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text
|
||||
|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}
|
||||
|<kbd>E</kbd> | Open source code file in the **Edit file** tab
|
||||
|<kbd>Command</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>F</kbd> (Windows/Linux) | Start searching in file editor
|
||||
|<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Find next
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Windows/Linux) | Find previous
|
||||
|<kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F</kbd> (Windows/Linux) | Replace
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>R</kbd> (Windows/Linux) | Replace all
|
||||
|<kbd>Alt</kbd>+<kbd>G</kbd> | Jump to line
|
||||
|<kbd>Command</kbd>+<kbd>Z</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Z</kbd> (Windows/Linux) | Undo
|
||||
|<kbd>Command</kbd>+<kbd>Y</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Y</kbd> (Windows/Linux) | Redo
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
|
||||
|<kbd>Command</kbd>+<kbd>S</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>S</kbd> (Windows/Linux) | Write a commit message
|
||||
|
||||
For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
|
||||
|
||||
@@ -75,67 +75,67 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>t</kbd> | Activates the file finder
|
||||
|<kbd>l</kbd> | Jump to a line in your code
|
||||
|<kbd>w</kbd> | Switch to a new branch or tag
|
||||
|<kbd>y</kbd> | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)."
|
||||
|<kbd>i</kbd> | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)."
|
||||
|<kbd>a</kbd> | Show or hide annotations on diffs
|
||||
|<kbd>b</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
|
||||
|<kbd>T</kbd> | Activates the file finder
|
||||
|<kbd>L</kbd> | Jump to a line in your code
|
||||
|<kbd>W</kbd> | Switch to a new branch or tag
|
||||
|<kbd>Y</kbd> | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)."
|
||||
|<kbd>I</kbd> | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)."
|
||||
|<kbd>A</kbd> | Show or hide annotations on diffs
|
||||
|<kbd>B</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
|
||||
|
||||
## Comments
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
| <kbd>control b</kbd> or <kbd>command b</kbd> | Inserts Markdown formatting for bolding text
|
||||
| <kbd>control i</kbd> or <kbd>command i</kbd> | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
| <kbd>control e</kbd> or <kbd>command e</kbd> | Inserts Markdown formatting for code or a command within a line{% endif %}
|
||||
| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link
|
||||
| <kbd>control shift p</kbd> or <kbd>command shift p</kbd>| Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
|
||||
| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list{% endif %}
|
||||
| <kbd>control enter</kbd> or <kbd>command enter</kbd> | Submits a comment
|
||||
| <kbd>control .</kbd> and then <kbd>control [saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
|
||||
|<kbd>control g</kbd> or <kbd>command g</kbd> | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
|
||||
| <kbd>r</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
|
||||
|<kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | Inserts Markdown formatting for bolding text
|
||||
|<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
|<kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% endif %}
|
||||
|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %}
|
||||
|<kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submits a comment
|
||||
|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
|
||||
|<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
|
||||
|<kbd>R</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
|
||||
|
||||
## Issue and pull request lists
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>c</kbd> | Create an issue
|
||||
| <kbd>control /</kbd> or <kbd>command /</kbd> | Focus your cursor on the issues or pull requests search bar. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."||
|
||||
|<kbd>u</kbd> | Filter by author
|
||||
|<kbd>l</kbd> | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
|
||||
| <kbd>alt</kbd> and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
|
||||
|<kbd>m</kbd> | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)."
|
||||
|<kbd>a</kbd> | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)."
|
||||
|<kbd>o</kbd> or <kbd>enter</kbd> | Open issue
|
||||
|<kbd>C</kbd> | Create an issue
|
||||
|<kbd>Command</kbd>+<kbd>/</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>/</kbd> (Windows/Linux) | Focus your cursor on the issues or pull requests search bar. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."||
|
||||
|<kbd>U</kbd> | Filter by author
|
||||
|<kbd>L</kbd> | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
|
||||
|<kbd>Alt</kbd> and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
|
||||
|<kbd>M</kbd> | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)."
|
||||
|<kbd>A</kbd> | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)."
|
||||
|<kbd>O</kbd> or <kbd>Enter</kbd> | Open issue
|
||||
|
||||
## Issues and pull requests
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>q</kbd> | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)."
|
||||
|<kbd>m</kbd> | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)."
|
||||
|<kbd>l</kbd> | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)."
|
||||
|<kbd>a</kbd> | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)."
|
||||
|<kbd>cmd + shift + p</kbd> or <kbd>control + shift + p</kbd> | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %}
|
||||
|<kbd>alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
|<kbd>shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
|<kbd>command</kbd> or <kbd>control + shift</kbd> and click | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>command</kbd> or <kbd>control + shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
|
||||
|<kbd>Q</kbd> | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)."
|
||||
|<kbd>M</kbd> | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)."
|
||||
|<kbd>L</kbd> | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)."
|
||||
|<kbd>A</kbd> | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)."
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %}
|
||||
|<kbd>Alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>Alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
|<kbd>Shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
|<kbd>Command</kbd> and click (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and click (Windows/Linux) | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>Command</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
|
||||
|
||||
## Changes in pull requests
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>c</kbd> | Open the list of commits in the pull request
|
||||
|<kbd>t</kbd> | Open the list of changed files in the pull request
|
||||
|<kbd>j</kbd> | Move selection down in the list
|
||||
|<kbd>k</kbd> | Move selection up in the list
|
||||
| <kbd>cmd + shift + enter </kbd> | Add a single comment on a pull request diff |
|
||||
| <kbd>alt</kbd> and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| Click, then <kbd>shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>shift</kbd>, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %}
|
||||
|<kbd>C</kbd> | Open the list of commits in the pull request
|
||||
|<kbd>T</kbd> | Open the list of changed files in the pull request
|
||||
|<kbd>J</kbd> | Move selection down in the list
|
||||
|<kbd>K</kbd> | Move selection up in the list
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> | Add a single comment on a pull request diff |
|
||||
|<kbd>Alt</kbd> and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %}
|
||||
|Click, then <kbd>Shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %}
|
||||
|
||||
## Project boards
|
||||
|
||||
@@ -143,50 +143,50 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>enter</kbd> or <kbd>space</kbd> | Start moving the focused column
|
||||
|<kbd>escape</kbd> | Cancel the move in progress
|
||||
|<kbd>enter</kbd> | Complete the move in progress
|
||||
|<kbd>←</kbd> or <kbd>h</kbd> | Move column to the left
|
||||
|<kbd>command + ←</kbd> or <kbd>command + h</kbd> or <kbd>control + ←</kbd> or <kbd>control + h</kbd> | Move column to the leftmost position
|
||||
|<kbd>→</kbd> or <kbd>l</kbd> | Move column to the right
|
||||
|<kbd>command + →</kbd> or <kbd>command + l</kbd> or <kbd>control + →</kbd> or <kbd>control + l</kbd> | Move column to the rightmost position
|
||||
|<kbd>Enter</kbd> or <kbd>Space</kbd> | Start moving the focused column
|
||||
|<kbd>Esc</kbd> | Cancel the move in progress
|
||||
|<kbd>Enter</kbd> | Complete the move in progress
|
||||
|<kbd>←</kbd> or <kbd>H</kbd> | Move column to the left
|
||||
|<kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux) | Move column to the leftmost position
|
||||
|<kbd>→</kbd> or <kbd>L</kbd> | Move column to the right
|
||||
|<kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux) | Move column to the rightmost position
|
||||
|
||||
### Moving a card
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>enter</kbd> or <kbd>space</kbd> | Start moving the focused card
|
||||
|<kbd>escape</kbd> | Cancel the move in progress
|
||||
|<kbd>enter</kbd> | Complete the move in progress
|
||||
|<kbd>↓</kbd> or <kbd>j</kbd> | Move card down
|
||||
|<kbd>command + ↓</kbd> or <kbd>command + j</kbd> or <kbd>control + ↓</kbd> or <kbd>control + j</kbd> | Move card to the bottom of the column
|
||||
|<kbd>↑</kbd> or <kbd>k</kbd> | Move card up
|
||||
|<kbd>command + ↑</kbd> or <kbd>command + k</kbd> or <kbd>control + ↑</kbd> or <kbd>control + k</kbd> | Move card to the top of the column
|
||||
|<kbd>←</kbd> or <kbd>h</kbd> | Move card to the bottom of the column on the left
|
||||
|<kbd>shift + ←</kbd> or <kbd>shift + h</kbd> | Move card to the top of the column on the left
|
||||
|<kbd>command + ←</kbd> or <kbd>command + h</kbd> or <kbd>control + ←</kbd> or <kbd>control + h</kbd> | Move card to the bottom of the leftmost column
|
||||
|<kbd>command + shift + ←</kbd> or <kbd>command + shift + h</kbd> or <kbd>control + shift + ←</kbd> or <kbd>control + shift + h</kbd> | Move card to the top of the leftmost column
|
||||
|<kbd>Enter</kbd> or <kbd>Space</kbd> | Start moving the focused card
|
||||
|<kbd>Esc</kbd> | Cancel the move in progress
|
||||
|<kbd>Enter</kbd> | Complete the move in progress
|
||||
|<kbd>↓</kbd> or <kbd>J</kbd> | Move card down
|
||||
|<kbd>Command</kbd>+<kbd>↓</kbd> or <kbd>Command</kbd>+<kbd>J</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↓</kbd> or <kbd>Ctrl</kbd>+<kbd>J</kbd> (Windows/Linux) | Move card to the bottom of the column
|
||||
|<kbd>↑</kbd> or <kbd>K</kbd> | Move card up
|
||||
|<kbd>Command</kbd>+<kbd>↑</kbd> or <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↑</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Move card to the top of the column
|
||||
|<kbd>←</kbd> or <kbd>H</kbd> | Move card to the bottom of the column on the left
|
||||
|<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Shift</kbd>+<kbd>H</kbd> | Move card to the top of the column on the left
|
||||
|<kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux) | Move card to the bottom of the leftmost column
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | Move card to the top of the leftmost column
|
||||
|<kbd>→</kbd> | Move card to the bottom of the column on the right
|
||||
|<kbd>shift + →</kbd> or <kbd>shift + l</kbd> | Move card to the top of the column on the right
|
||||
|<kbd>command + →</kbd> or <kbd>command + l</kbd> or <kbd>control + →</kbd> or <kbd>control + l</kbd> | Move card to the bottom of the rightmost column
|
||||
|<kbd>command + shift + →</kbd> or <kbd>command + shift + l</kbd> or <kbd>control + shift + →</kbd> or <kbd>control + shift + l</kbd> | Move card to the bottom of the rightmost column
|
||||
|<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Shift</kbd>+<kbd>L</kbd> | Move card to the top of the column on the right
|
||||
|<kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux) | Move card to the bottom of the rightmost column
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | Move card to the bottom of the rightmost column
|
||||
|
||||
### Previewing a card
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>esc</kbd> | Close the card preview pane
|
||||
|<kbd>Esc</kbd> | Close the card preview pane
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## {% data variables.product.prodname_actions %}
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>command + space </kbd> or <kbd>control + space</kbd> | In the workflow editor, get suggestions for your workflow file.
|
||||
|<kbd>g</kbd> <kbd>f</kbd> | Go to the workflow file
|
||||
|<kbd>shift + t</kbd> or <kbd>T</kbd> | Toggle timestamps in logs
|
||||
|<kbd>shift + f</kbd> or <kbd>F</kbd> | Toggle full-screen logs
|
||||
|<kbd>esc</kbd> | Exit full-screen logs
|
||||
|<kbd>Command</kbd>+<kbd>Space </kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Space</kbd> (Windows/Linux) | In the workflow editor, get suggestions for your workflow file.
|
||||
|<kbd>G</kbd> <kbd>F</kbd> | Go to the workflow file
|
||||
|<kbd>Shift</kbd>+<kbd>T</kbd> or <kbd>T</kbd> | Toggle timestamps in logs
|
||||
|<kbd>Shift</kbd>+<kbd>F</kbd> or <kbd>F</kbd> | Toggle full-screen logs
|
||||
|<kbd>Esc</kbd> | Exit full-screen logs
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -195,28 +195,28 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>e</kbd> | Mark as done
|
||||
| <kbd>shift + u</kbd>| Mark as unread
|
||||
| <kbd>shift + i</kbd>| Mark as read
|
||||
| <kbd>shift + m</kbd> | Unsubscribe
|
||||
|<kbd>E</kbd> | Mark as done
|
||||
|<kbd>Shift</kbd>+<kbd>U</kbd>| Mark as unread
|
||||
|<kbd>Shift</kbd>+<kbd>I</kbd>| Mark as read
|
||||
|<kbd>Shift</kbd>+<kbd>M</kbd> | Unsubscribe
|
||||
|
||||
{% else %}
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>e</kbd> or <kbd>I</kbd> or <kbd>y</kbd> | Mark as read
|
||||
|<kbd>shift + m</kbd> | Mute thread
|
||||
|<kbd>E</kbd> or <kbd>I</kbd> or <kbd>Y</kbd> | Mark as read
|
||||
|<kbd>Shift</kbd>+<kbd>M</kbd> | Mute thread
|
||||
{% endif %}
|
||||
|
||||
## Network graph
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>←</kbd> or <kbd>h</kbd> | Scroll left
|
||||
|<kbd>→</kbd> or <kbd>l</kbd> | Scroll right
|
||||
|<kbd>↑</kbd> or <kbd>k</kbd> | Scroll up
|
||||
|<kbd>↓</kbd> or <kbd>j</kbd> | Scroll down
|
||||
|<kbd>shift + ←</kbd> or <kbd>shift + h</kbd> | Scroll all the way left
|
||||
|<kbd>shift + →</kbd> or <kbd>shift + l</kbd> | Scroll all the way right
|
||||
|<kbd>shift + ↑</kbd> or <kbd>shift + k</kbd> | Scroll all the way up
|
||||
|<kbd>shift + ↓</kbd> or <kbd>shift + j</kbd> | Scroll all the way down
|
||||
|<kbd>←</kbd> or <kbd>H</kbd> | Scroll left
|
||||
|<kbd>→</kbd> or <kbd>L</kbd> | Scroll right
|
||||
|<kbd>↑</kbd> or <kbd>K</kbd> | Scroll up
|
||||
|<kbd>↓</kbd> or <kbd>J</kbd> | Scroll down
|
||||
|<kbd>Shift</kbd>+<kbd>←</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | Scroll all the way left
|
||||
|<kbd>Shift</kbd>+<kbd>→</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | Scroll all the way right
|
||||
|<kbd>Shift</kbd>+<kbd>↑</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>K</kbd> (Windows/Linux) | Scroll all the way up
|
||||
|<kbd>Shift</kbd>+<kbd>↓</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>J</kbd> (Windows/Linux) | Scroll all the way down
|
||||
|
||||
@@ -30,5 +30,8 @@ Nos preocupa la censura de Internet y creemos que la transparencia a un nivel es
|
||||
## ¿Qué significa que publiquemos una notificación en nuestro repositorio de retiro del gobierno?
|
||||
Significa que recibimos la notificación en la fecha indicada. *No* significa que el contenido es ilegal o sea incorrecto. *No* significa que el usuario identificado en la notificación haya hecho algo incorrecto. No hacemos ni implicamos ningún juicio sobre el mérito de las reclamaciones que hacen. Publicamos estas notificaciones y solicitudes sólo para propósitos informativos.
|
||||
|
||||
## Government takedowns based on violations of GitHub's Terms of Service
|
||||
In some cases, GitHub receives reports from government officials of violations of GitHub's Terms of Service. We process those violations as we would process a Terms-of-Service violation reported by anyone else. However, we notify the affected users that the report came from a government and, as with any other case, allow them the opportunity to appeal.
|
||||
|
||||
## Reportes de transparencia
|
||||
Además de publicar notificaciones de retiro del gobierno en nuestro repositorio de retiros del gobierno, las informamos en nuestro reporte de transparencia. También rastreamos e informamos en nuestro reporte de transparencia sobre los retiros del gobierno con base en violaciones de los Términos de Servicio de GitHub. Procesamos dichas violaciones como procesaríamos una violación de los Términos de Servicio denunciada por cualquier otro.
|
||||
In addition to posting government takedown notices in our `github/gov-takedowns` repository, we report on them in our transparency report. También rastreamos e informamos en nuestro reporte de transparencia sobre los retiros del gobierno con base en violaciones de los Términos de Servicio de GitHub.
|
||||
|
||||
@@ -18,8 +18,12 @@ shortTitle: Revisar las integraciones instaladas
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %} Instaladas**. 
|
||||
5. Al lado de la {% data variables.product.prodname_github_app %} que quieras revisar, haz clic en **Configure** (Configurar). 
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %} Instaladas**. 
|
||||
{% endif %}
|
||||
2. Al lado de la {% data variables.product.prodname_github_app %} que quieras revisar, haz clic en **Configure** (Configurar). 
|
||||
6. Revisa el acceso al repositorio y los permisos de {% data variables.product.prodname_github_app %}. 
|
||||
- Para darle acceso a la {% data variables.product.prodname_github_app %} a todos los repositorios de tu organización, selecciona **All repositories** (Todos los repositorios).
|
||||
- Para elegir repositorios específicos para darle acceso a la aplicación, selecciona **Only select repositories** (Solo repositorios seleccionados), luego escribe el nombre de un repositorio.
|
||||
|
||||
@@ -40,8 +40,8 @@ To further support your team's collaboration abilities, you can upgrade to {% da
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
{% data reusables.organizations.invite-teams-or-people %}
|
||||
5. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
|
||||
|
||||
|
||||
@@ -28,9 +28,13 @@ Cuando eliminas a un colaborador de un repositorio en tu organización, el colab
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% endif %}
|
||||
{% data reusables.organizations.invite-teams-or-people %}
|
||||
5. En el campo de búsqueda, comienza a teclear el nombre de la persona que desees invitar y luego haz clic en un nombre de la lista de coincidencias. 
|
||||
1. En el campo de búsqueda, comienza a teclear el nombre de la persona que desees invitar y luego haz clic en un nombre de la lista de coincidencias. 
|
||||
6. Debajo de "Elige un rol", selecciona el rol de repositorio que quieres asignar a la persona y luego haz clic en **Agregar NOMBRE a REPOSITORIO**. 
|
||||
|
||||
## Administrar el acceso de una persona a un repositorio de una organización
|
||||
|
||||
@@ -24,10 +24,13 @@ Cuando inhabilitas los tableros de proyecto, ya no ves la información de los ta
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. Decide si deseas inhabilitar los tableros de proyecto que se usan en toda la organización, los tableros de proyecto de los repositorios de la organización, o ambos. Luego, en "Proyectos":
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
|
||||
{% endif %}
|
||||
1. Decide si deseas inhabilitar los tableros de proyecto que se usan en toda la organización, los tableros de proyecto de los repositorios de la organización, o ambos. Luego, en "Proyectos":
|
||||
- Para inhabilitar los tableros de proyecto que se usan en toda la organización, quita la marca de selección de **Habilitar proyectos para la organización**.
|
||||
- Para inhabilitar los tableros de proyecto de los repositorios en la organización, quita la marca de selección de **Habilitar proyectos para todos los repositorios**. 
|
||||
5. Haz clic en **Save ** (guardar).
|
||||
1. Haz clic en **Save ** (guardar).
|
||||
|
||||
{% data reusables.organizations.disable_project_board_results %}
|
||||
|
||||
|
||||
@@ -10,14 +10,21 @@ versions:
|
||||
shortTitle: Integrar Jira
|
||||
---
|
||||
|
||||
{% ifversion ghes > 3.3 or ghae-issue-5658 %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**. 
|
||||
1. Da clic en **Nueva App de OAuth**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. En la barra lateral izquierda en **Organization settings** (Configuraciones de la organización), haz clic en el nombre de tu organización. 
|
||||
3. En la barra lateral de **Developer settings** (Configuraciones del programador), haz clic en **OAuth applications** (Aplicaciones OAuth). 
|
||||
4. Haz clic en **Register a new application** (Registrar una aplicación nueva).
|
||||
5. En **Application name** (Nombre de la aplicación), escribe "Jira".
|
||||
6. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira.
|
||||
7. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira.
|
||||
8. Haz clic en **Register application** (Registrar aplicación). 
|
||||
1. En la barra lateral izquierda en **Organization settings** (Configuraciones de la organización), haz clic en el nombre de tu organización. 
|
||||
1. En la barra lateral de **Developer settings** (Configuraciones del programador), haz clic en **OAuth applications** (Aplicaciones OAuth). 
|
||||
1. Haz clic en **Register a new application** (Registrar una aplicación nueva).
|
||||
{% endif %}
|
||||
1. En **Application name** (Nombre de la aplicación), escribe "Jira".
|
||||
2. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira.
|
||||
3. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira.
|
||||
4. Haz clic en **Register application** (Registrar aplicación). 
|
||||
9. En **Organization owned applications** (Aplicaciones propiedad de la organización), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). 
|
||||
{% data reusables.user_settings.jira_help_docs %}
|
||||
|
||||
|
||||
@@ -24,14 +24,13 @@ Los propietarios de la organización pueden programar un recordatorio para uno m
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.add-reminder %}
|
||||
{% data reusables.reminders.authorize-slack %}
|
||||
{% data reusables.reminders.slack-channel %}
|
||||
{% data reusables.reminders.days-dropdown %}
|
||||
{% data reusables.reminders.times-dropdowns %}
|
||||
{% data reusables.reminders.tracked-repos %}
|
||||
11. Da clic en el menú desplegable de **Añadir equipo** debajo de "Filtrar por equipo asignado para revisar el código", y elige uno o más equipos. Puedes agregar hasta 100 equipos. Si el equipo que seleccionas carece de acceso a los "Repositorios rastreados" seleccionados anteriormente, no podrás crear el recordatorio programado. 
|
||||
1. Da clic en el menú desplegable de **Añadir equipo** debajo de "Filtrar por equipo asignado para revisar el código", y elige uno o más equipos. Puedes agregar hasta 100 equipos. Si el equipo que seleccionas carece de acceso a los "Repositorios rastreados" seleccionados anteriormente, no podrás crear el recordatorio programado. 
|
||||
{% data reusables.reminders.ignore-drafts %}
|
||||
{% data reusables.reminders.no-review-requests %}
|
||||
{% data reusables.reminders.author-reviews %}
|
||||
@@ -47,7 +46,6 @@ Los propietarios de la organización pueden programar un recordatorio para uno m
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.edit-existing %}
|
||||
{% data reusables.reminders.edit-page %}
|
||||
{% data reusables.reminders.update-buttons %}
|
||||
@@ -56,7 +54,6 @@ Los propietarios de la organización pueden programar un recordatorio para uno m
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.delete %}
|
||||
|
||||
## Leer más
|
||||
|
||||
@@ -63,3 +63,7 @@ La persona invitada recibirá una invitación por correo electrónico solicitán
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Debajo de "Administración de la facturación", junto a "Gerentes de facturación", haz clic en **Agregar**. 
|
||||
6. Escribe el nombre de usuario o la dirección de correo electrónico de la persona a la que deseas agregar y haz clic en **Send invitation** (Enviar invitación). 
|
||||
|
||||
## Leer más
|
||||
|
||||
- "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
|
||||
|
||||
@@ -57,8 +57,12 @@ Any team members that have set their status to "Busy" will not be selected for r
|
||||
{% data reusables.user_settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
|
||||
{% else %}
|
||||
1. In the left sidebar, click **Code review**
|
||||
|
||||
{% endif %}
|
||||
1. Select **Only notify requested team members.**
|
||||
|
||||
1. Click **Save changes**.
|
||||
@@ -69,8 +73,12 @@ Any team members that have set their status to "Busy" will not be selected for r
|
||||
{% data reusables.user_settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
|
||||
{% else %}
|
||||
1. In the left sidebar, click **Code review**
|
||||
|
||||
{% endif %}
|
||||
1. Select **Enable auto assignment**.
|
||||
|
||||
1. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request.
|
||||
|
||||
@@ -27,7 +27,6 @@ Los mantenedores de equipo y propietarios de organización pueden configurar rec
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.add-reminder %}
|
||||
{% data reusables.reminders.authorize-slack %}
|
||||
{% data reusables.reminders.slack-channel %}
|
||||
@@ -51,7 +50,6 @@ Los mantenedores de equipo y propietarios de organización pueden configurar rec
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.edit-existing %}
|
||||
{% data reusables.reminders.edit-page %}
|
||||
{% data reusables.reminders.update-buttons %}
|
||||
@@ -62,7 +60,6 @@ Los mantenedores de equipo y propietarios de organización pueden configurar rec
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.delete %}
|
||||
|
||||
## Leer más
|
||||
|
||||
@@ -25,12 +25,12 @@ This guide will lead you through creating a user site at `username.github.io`.
|
||||
{% data reusables.repositories.create_new %}
|
||||
1. Enter `username.github.io` as the repository name. Replace `username` with your {% data variables.product.prodname_dotcom %} username. For example, if your username is `octocat`, the repository name should be `octocat.github.io`. 
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. En la barra lateral izquierda, da clic en **Páginas**. 
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
1. Click **Choose a theme**. 
|
||||
1. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now. 
|
||||
1. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
|
||||
1. When you are done editing the file, click **Commit changes**.
|
||||
1. Visit `username.github.io` to view your new website. **Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}.
|
||||
2. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now. 
|
||||
3. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
|
||||
4. When you are done editing the file, click **Commit changes**.
|
||||
5. Visit `username.github.io` to view your new website. **Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}.
|
||||
|
||||
## Changing the title and description
|
||||
|
||||
@@ -38,7 +38,7 @@ By default, the title of your site is `username.github.io`. You can change the t
|
||||
|
||||
1. Click the **Code** tab of your repository.
|
||||
1. In the file list, click `_config.yml` to open the file.
|
||||
1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
|
||||
1. Haz clic en {% octicon "pencil" aria-label="The edit icon" %} para editar el archivo.
|
||||
1. The `_config.yml` file already contains a line that specifies the theme for your site. Add a new line with `title:` followed by the title you want. Add a new line with `description:` followed by the description you want. Por ejemplo:
|
||||
|
||||
```yaml
|
||||
|
||||
@@ -22,8 +22,12 @@ Si usas Zendesk para hacer el seguimiento de los tickets informados por el usuar
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. En la barra lateral izquierda, haz clic en **Autolink references** (Referencias de enlace automático). 
|
||||
4. Haz clic en **Add autolink reference** (Agregar referencia de enlace automático). 
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-label="The cross-reference icon" %} Autolink references**.
|
||||
{% else %}
|
||||
1. En la barra lateral izquierda, haz clic en **Autolink references** (Referencias de enlace automático). 
|
||||
{% endif %}
|
||||
1. Haz clic en **Add autolink reference** (Agregar referencia de enlace automático). 
|
||||
5. Debajo de "Reference prefix" (Prefijo de referencia), escribe un prefijo corto y significativo que quieras que los colaboradores utilicen para generar enlaces automáticos para el recurso externo. 
|
||||
6. Debajo de "Target URL" (URL de destino), escribe el enlace al sistema externo al que te quieras vinculr. Asegúrate de conservar `<num>` como variable para el número de referencia. 
|
||||
7. Haz clic en **Add autolink reference** (Agregar referencia de enlace automático). 
|
||||
|
||||
@@ -28,7 +28,7 @@ Para obtener más información acerca de los roles de los repositorios, consulta
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
4. Debajo de "Administrar acceso" en el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres encontrar. 
|
||||
|
||||
## Cambiar permisos para un equipo o persona
|
||||
@@ -42,7 +42,7 @@ Para obtener más información acerca de los roles de los repositorios, consulta
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
{% data reusables.organizations.invite-teams-or-people %}
|
||||
5. En el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres invitar y da clic en el mismo dentro de la lista de coincidencias. 
|
||||
6. Debajo de "Elige un rol", selecciona el rol del repositorio que quieras otorgar al equipo o persona y luego haz clic en **Add NAME to REPOSITORY**. 
|
||||
@@ -51,7 +51,7 @@ Para obtener más información acerca de los roles de los repositorios, consulta
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
4. Debajo de "Administrar acceso", encuentra al equipo o persona de quien quieras eliminar el acceso y da clic{% octicon "trash" aria-label="The trash icon" %}. 
|
||||
|
||||
## Leer más
|
||||
|
||||
@@ -8,7 +8,7 @@ versions:
|
||||
ghec: '*'
|
||||
children:
|
||||
- /navigating-code-on-github
|
||||
- /tracking-changes-in-a-file
|
||||
- /viewing-a-file
|
||||
- /getting-permanent-links-to-files
|
||||
- /working-with-non-code-files
|
||||
---
|
||||
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: Viewing a file
|
||||
intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
|
||||
redirect_from:
|
||||
- /articles/using-git-blame-to-trace-changes-in-a-file
|
||||
- /articles/tracing-changes-in-a-file
|
||||
- /articles/tracking-changes-in-a-file
|
||||
- /github/managing-files-in-a-repository/tracking-changes-in-a-file
|
||||
- /github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file
|
||||
- /repositories/working-with-files/using-files/tracking-changes-in-a-file
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: View files and track file changes
|
||||
---
|
||||
|
||||
## Viewing or copying the raw file content
|
||||
|
||||
With the raw view, you can view or copy the raw content of a file without any styling.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Click the file that you want to view.
|
||||
2. In the upper-right corner of the file view, click **Raw**. 
|
||||
3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
|
||||
|
||||
## Viewing the line-by-line revision history for a file
|
||||
|
||||
Con la vista de último responsable, puedes ver el historial de revisión línea por línea para todo un archivo o ver el historial de revisión de una única línea dentro de un archivo haciendo clic en {% octicon "versions" aria-label="The prior blame icon" %}. Cada vez que hagas clic en {% octicon "versions" aria-label="The prior blame icon" %}, verás la información de revisión anterior para esa línea, incluido quién y cuándo confirmó el cambio.
|
||||
|
||||
|
||||
|
||||
En un archivo o solicitud de extracción, también puedes utilizar el menú {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} para ver el último responsable de Git para una línea o rango de líneas seleccionado.
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Sugerencia:** En la línea de comando, también puedes utilizar `git blame` para ver el historial de revisión de líneas dentro de un archivo. Para obtener más información, consulta la documentación de [ `git blame`](https://git-scm.com/docs/git-blame) de Git.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. Haz clic para abrir el archivo cuyo historial de líneas quieres ver.
|
||||
3. En la esquina superior derecha de la vista del archivo, haz clic en **Blame** (Último responsable) para abrir la vista del último responsable. 
|
||||
4. Para ver versiones anteriores de una línea específica, o el siguiente último responsable, haz clic en {% octicon "versions" aria-label="The prior blame icon" %} hasta que hayas encontrado los cambios que quieres ver. 
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
#Reference: #5813.
|
||||
#Documentation for GitHub Actions workflow dependencies appearing in the dependency graph
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: 'issue-5813'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
#Reference: #5503.
|
||||
#Documentation for the security overview individual views
|
||||
versions:
|
||||
ghes: '> 3.4'
|
||||
ghae: 'issue-5503'
|
||||
ghec: '*'
|
||||
@@ -41,6 +41,7 @@ adopting_github_actions_for_your_enterprise:
|
||||
title: 'Adoptar GitHub Actions para tu empresa'
|
||||
description: 'Aprende cómo planear y hacer una implementación de {% data variables.product.prodname_actions %} en tu empresa.'
|
||||
guides:
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
|
||||
- /actions/learn-github-actions/understanding-github-actions
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
|
||||
|
||||
@@ -40,6 +40,7 @@ adopting_github_actions_for_your_enterprise:
|
||||
title: 'Adoptar GitHub Actions para tu empresa'
|
||||
description: 'Aprende cómo planear y hacer una implementación de {% data variables.product.prodname_actions %} en tu empresa.'
|
||||
guides:
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
|
||||
- /actions/learn-github-actions/understanding-github-actions
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
date: '2020-08-11'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**CRÍTICA:** Se identificó una vulnerabilidad de ejecución en GitHub Pages que podría permitir que un atacante ejecute comandos como parte de la construcción de un sitio de GitHub Pages. Este problema se da debido a una dependencia vulnerable desactualizada que se utiliza en el proceso de creación de Pages. para explotar esta vulnerabilidad, el atacante necesita permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afecta a todas las versiones de GitHub Enterprise Server. Para mitigarla, Kramdown se actualizó para dirigirse a CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}'
|
||||
- '**ALTA:** Un atacante pudo inyectar un argumento malicioso en un sub-comando de Git cuando se ejecutó en GitHub Enterprise Server. Esto pudo permitir que el atacante sobreescribiera archivos arbitrarios con un contenido parcialmente controlado por el usuario y que ejecutara potencialmente comandos arbitrarios en la instancia de GitHub Enterprise Server. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para acceder a los repositorios dentro de la instancia de GitHub Enterprise Server. Sin embargo, debido a que existen otros tipos de protección, no pudimos identificar una forma de explotar activamente esta vulnerabilidad. Dicha vulnerabilidad se reportó a través del programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}'
|
||||
- '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}'
|
||||
- '**High:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}'
|
||||
- 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}'
|
||||
bugs:
|
||||
- 'Un error de configuración de Consul previnió que algunos jobs en segundo plano se procesaran en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}'
|
||||
|
||||
@@ -3,7 +3,7 @@ date: '2020-08-26'
|
||||
sections:
|
||||
security_fixes:
|
||||
- >-
|
||||
**CRÍTICO:** Se identificó una vulnerabilidad de ejecución remota de código en GitHub Pages, la cual podría aprovecharse al crear un sitio de GitHub Pages. La configuración controlada por el usuario de los analizadores sintácticos subyacentes que utiliza GitHub Pages no se restringió lo suficiente e hizo posible que se ejecutaran comandos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, cualquier atacante necesitaría permiso de crear y compilar un sitio de GitHub Pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server. Los problemas subyacentes contribuyeron a que esta vulnerabilidad se identificara tanto internamente como a través del programa de Recompensas por Errores de Seguridad de GitHub. Emitimos el código CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %}
|
||||
{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %}
|
||||
- '**MEDIA:** Una vulnerabilidad de control de acceso inadecuado se identificó, la cual permitía a los usuarios autenticados de la instancia determinar los nombres de repositorios privados no autorizados de acuerdo con sus ID numéricas. Dicha vulnerabilidad no permitió el acceso no autorizado a ningún tipo de contenido de los repositorios mas que su nombre. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anteriores a la 2.22 y se le asignó el [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). La vulnerabilidad se reportó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}'
|
||||
- 'Se actualizaron los paquetes a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}'
|
||||
bugs:
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
date: '2020-08-11'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**CRÍTICA:** Se identificó una vulnerabilidad de ejecución en GitHub Pages que podría permitir que un atacante ejecute comandos como parte de la construcción de un sitio de GitHub Pages. Este problema se da debido a una dependencia vulnerable desactualizada que se utiliza en el proceso de creación de Pages. para explotar esta vulnerabilidad, el atacante necesita permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afecta a todas las versiones de GitHub Enterprise Server. Para mitigarla, Kramdown se actualizó para dirigirse a CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}'
|
||||
- '**ALTA:** Un atacante pudo inyectar un argumento malicioso en un sub-comando de Git cuando se ejecutó en GitHub Enterprise Server. Esto pudo permitir que el atacante sobreescribiera archivos arbitrarios con un contenido parcialmente controlado por el usuario y que ejecutara potencialmente comandos arbitrarios en la instancia de GitHub Enterprise Server. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para acceder a los repositorios dentro de la instancia de GHES. Sin embargo, debido a que existen otros tipos de protección, no pudimos identificar una forma de explotar activamente esta vulnerabilidad. Dicha vulnerabilidad se reportó a través del programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}'
|
||||
- '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}'
|
||||
- '**High:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}'
|
||||
- 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}'
|
||||
bugs:
|
||||
- 'Un error de configuración de Consul previnió que algunos jobs en segundo plano se procesaran en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}'
|
||||
|
||||
@@ -3,8 +3,8 @@ date: '2020-08-26'
|
||||
sections:
|
||||
security_fixes:
|
||||
- >-
|
||||
**CRÍTICO:** Se identificó una vulnerabilidad de ejecución remota de código en GitHub Pages, la cual podría aprovecharse al crear un sitio de GitHub Pages. La configuración controlada por el usuario de los analizadores sintácticos subyacentes que utiliza GitHub Pages no se restringió lo suficiente e hizo posible que se ejecutaran comandos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, cualquier atacante necesitaría permiso de crear y compilar un sitio de GitHub Pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server. Los problemas subyacentes contribuyeron a que esta vulnerabilidad se identificara tanto internamente como a través del programa de Recompensas por Errores de Seguridad de GitHub. Emitimos el código CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %}
|
||||
- '**MEDIA:** Una vulnerabilidad de control de acceso inadecuado se identificó, la cual permitía a los usuarios autenticados de la instancia determinar los nombres de repositorios privados no autorizados de acuerdo con sus ID numéricas. Dicha vulnerabilidad no permitió el acceso no autorizado a ningún tipo de contenido de los repositorios mas que su nombre. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anteriores a la 2.22 y se le asignó el [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). La vulnerabilidad se reportó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}'
|
||||
{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %}
|
||||
- '**Medium:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}'
|
||||
- 'Se actualizaron los paquetes a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}'
|
||||
bugs:
|
||||
- 'No se registró un mensaje cuando el proceso ghe-config-apply terminó de ejecutar ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}'
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
date: '2021-12-13'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
|
||||
- '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
|
||||
- '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
|
||||
known_issues:
|
||||
- En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
date: '2021-12-13'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
|
||||
- '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
|
||||
- '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
|
||||
known_issues:
|
||||
- El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
date: '2021-12-13'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
|
||||
- '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
|
||||
- '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
|
||||
known_issues:
|
||||
- En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
date: '2021-12-13'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
|
||||
- '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
|
||||
- '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
|
||||
known_issues:
|
||||
- Después de haber actualizado a {% data variables.product.prodname_ghe_server %} 3.3, podría que las {% data variables.product.prodname_actions %} no inicien automáticamente. Para resolver este problema, conéctate al aplicativo a través de SSH y ejecuta el comando `ghe-actions-start`.
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
|
||||
{% else %}
|
||||
1. En la barra lateral de Parámetros, haz clic en **Audit Log (Registro de auditoría)**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
3. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
|
||||
{% else %}
|
||||
3. En la barra lateral izquierda, haz clic en **Audit Log (Registro de auditoría)**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -0,0 +1,6 @@
|
||||
{% ifversion ghec %}
|
||||
If your license includes {% data variables.product.prodname_vss_ghe %}, you can identify whether a user account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following.
|
||||
- "Matched": The user account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
|
||||
- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation.
|
||||
- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the user account on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% endif %}
|
||||
@@ -1,2 +1,5 @@
|
||||
1. En la barra lateral, haz clic en **{% data variables.product.prodname_dependabot %}**.{% ifversion fpt or ghec %} {% else %}
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**.
|
||||
{% elsif ghes > 3.2%}
|
||||
1. En la barra lateral, haz clic en **{% data variables.product.prodname_dependabot %}**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
Si necesitas restablecer la contraseña de tu usuario de configuración, utiliza una ventana privada o de modo incógnito para solicitar una contraseña nueva. Cuando recibas el correo electrónico con el enlace para restablecer tu contraseña, cópialo en tu buscador. Para obtener más información sobre cómo restablecer tu contraseña, consulta la sección "[Solicitar una contraseña nueva](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)".
|
||||
If you need to reset the password for your setup user, contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}.
|
||||
|
||||
@@ -14,3 +14,6 @@
|
||||
- Ejecutar el script `config` para configurar la aplicación del ejecutor auto-hospedado y registrarlo con {% data variables.product.prodname_actions %}. El script `config` requiere la URL destino y un token de tiempo limitado generado automáticamente para autenticar la solicitud.
|
||||
- En Windows, el script `config` también te pregunta si deseas instalar la aplicación del ejecutor autoalojado como un servicio. Para Linux y macOS, puedes instalar un servicio después de que termines de agregar el ejecutor. Para obtener más información, consulta "[Configurar la aplicación del ejecutor autoalojado como un servicio](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)."
|
||||
- Ejecutar la aplicación del ejecutor autoalojado para conectar la máquina a las {% data variables.product.prodname_actions %}.
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
- If you are setting up a cluster of runners, you can install another tool to automatically scale your runners. Para obtener más información, consulta la sección "[Autoescalar con ejecutores auto-hospedados](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)".
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En la barra lateral izquierda, haz clic en **Secrets** (Secretos).
|
||||
{% endif %}
|
||||
|
||||
@@ -83,6 +83,12 @@ macOS Catalina 10.15
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** The `-latest` virtual environments are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
<b>Nota:</b> Las imágenes beta y obsoletizadas se proporcionan "tal cual", "con todos sus fallos" y "conforme estén disponibles" y se les excluye del acuerdo de nivel de servicio y de la garantía. El soporte al cliente podría no cubrir las imágenes beta.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. En la barra lateral, haz clic en **Organizaciones**. 
|
||||
2. In the settings sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. Si eres un propietario de organización, en la barra lateral izquierda, haz clic en **Facturación & planes**. 
|
||||
1. If you're an organization owner, in the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En la barra lateral de configuración de tu organización, haz clic en **Planes & facturación**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. En la barra lateral de Configuración de tu organización, da clic en **Usuarios bloqueados**. 
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. En la barra lateral izquierda, da clic en **Codespaces**. 
|
||||
1. In the left sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %}**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
4. En la barra lateral izquierda, da clic en **Privilegios de los miembros**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. En la barra lateral izquierda, da clic en **Configuración de moderación**. 
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**
|
||||
|
||||
@@ -1 +1 @@
|
||||
4. En la barra lateral izquierda, da clic en **Roles del repositorio**. 
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-label="The ID badge icon" %} Repository roles**.
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-label="The repo icon" %} Repository**, then click **Repository defaults**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En la barra lateral izquierda da clic en **Predeterminados del repositorio**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. En la barra lateral izquierda, da clic en **Etiquetas de repositorio**. 
|
||||
1. En la barra lateral izquierda, da clic en **Etiquetas de repositorio**.
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Authentication security**.
|
||||
{% else %}
|
||||
1. En la barra lateral izquierda, da clic en **Seguridad de la organización**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En la barra lateral izquierda, haz clic en **Dominios verificados & aprobados**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
{% ifversion fpt or ghes > 3.1 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %}
|
||||
1. In the "Code & operations" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
|
||||
{% else %}
|
||||
1. En la barra lateral izquierda, da clic en **Páginas**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. En la barra lateral izquierda, da clic en **Recordatorios programados**.
|
||||
1. In the "Integrations" section of the sidebar, click **{% octicon "clock" aria-label="The clock icon" %} Scheduled reminders**.
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Collaborators & teams**.
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
|
||||
1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**.
|
||||
{% elsif ghes < 3.4 or ghae %}
|
||||
1. En el menú izquierdo, da clic en **Ramas**. 
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. En la barra lateral izquierda, da clic en **Contenido reportado**. 
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Reported content**.
|
||||
|
||||
@@ -38,6 +38,7 @@ toc:
|
||||
guides: Guías
|
||||
whats_new: Qué hay de nuevo
|
||||
videos: Vídeos
|
||||
all_changelogs: All changelog posts
|
||||
pages:
|
||||
article_version: 'Versión del artículo'
|
||||
miniToc: En este artículo
|
||||
@@ -160,7 +161,10 @@ product_landing:
|
||||
release_notes_for: Notas de lanzamiento para
|
||||
upgrade_from: Mejorar desde
|
||||
browse_all_docs: Buscar todos los documentos
|
||||
browse_all: Browse all
|
||||
docs: documentación
|
||||
explore_release_notes: Explorar las notas de lanzamiento
|
||||
view: Ver todos
|
||||
product_guides:
|
||||
start_path: Start learning path
|
||||
learning_paths: 'Rutas de aprendizaje de {{ productMap[currentProduct].name }}'
|
||||
|
||||
Reference in New Issue
Block a user