New translation batch for es (#29008)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=es * run script/i18n/reset-known-broken-translation-files.js * Check in es CSV report Co-authored-by: Hector Alfaro <hectorsector@github.com>
This commit is contained in:
docubot
@@ -129,9 +129,9 @@ Email notifications from {% data variables.product.product_location %} contain t
|
||||
| --- | --- |
|
||||
| `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
|
||||
| `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} |
|
||||
| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li>{% ifversion fpt or ghes or ghae or ghec %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li>{% endif %}<li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
|
||||
| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %}
|
||||
| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li><li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li><li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
|
||||
| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |
|
||||
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |
|
||||
|
||||
## Choosing your notification settings
|
||||
|
||||
@@ -139,8 +139,8 @@ Email notifications from {% data variables.product.product_location %} contain t
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
3. On the notifications settings page, choose how you receive notifications when:
|
||||
- There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)."
|
||||
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %}
|
||||
- There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %}
|
||||
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."
|
||||
- There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% ifversion fpt or ghec %}
|
||||
- There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %}
|
||||
- There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %}
|
||||
|
||||
@@ -194,7 +194,6 @@ If you are a member of more than one organization, you can configure each one to
|
||||
5. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## {% data variables.product.prodname_dependabot_alerts %} notification options
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-enable %}
|
||||
@@ -202,7 +201,6 @@ If you are a member of more than one organization, you can configure each one to
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-options %}
|
||||
|
||||
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
## {% data variables.product.prodname_actions %} notification options
|
||||
|
||||
@@ -112,15 +112,13 @@ To filter notifications for specific activity on {% data variables.product.produ
|
||||
- `is:gist`
|
||||
- `is:issue-or-pull-request`
|
||||
- `is:release`
|
||||
- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %}
|
||||
- `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %}
|
||||
- `is:repository-invitation`
|
||||
- `is:repository-vulnerability-alert`{% ifversion fpt or ghec %}
|
||||
- `is:repository-advisory`{% endif %}
|
||||
- `is:team-discussion`{% ifversion fpt or ghec %}
|
||||
- `is:discussion`{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
{% endif %}
|
||||
|
||||
You can also use the `is:` query to describe how the notification was triaged.
|
||||
|
||||
@@ -142,8 +140,8 @@ To filter notifications by why you've received an update, you can use the `reaso
|
||||
| `reason:invitation` | When you're invited to a team, organization, or repository.
|
||||
| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to.
|
||||
| `reason:mention` | You were directly @mentioned.
|
||||
| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| `reason:security-alert` | When a security alert is issued for a repository.{% endif %}
|
||||
| `reason:review-requested` | You or a team you're on have been requested to review a pull request.
|
||||
| `reason:security-alert` | When a security alert is issued for a repository.
|
||||
| `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged.
|
||||
| `reason:team-mention` | When a team you're a member of is @mentioned.
|
||||
| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status.
|
||||
@@ -161,7 +159,6 @@ For example, to see notifications from the octo-org organization, use `org:octo-
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## {% data variables.product.prodname_dependabot %} custom filters
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
@@ -182,4 +179,3 @@ If you use {% data variables.product.prodname_dependabot %} to tell you about in
|
||||
For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -20,7 +20,7 @@ Opcionalmente, puedes elegir agregar una descripción, ubicación, sitio web y d
|
||||
|
||||
{% ifversion fpt %}
|
||||
Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} pueden confirmar la identidad de la organización y mostrar una insignia de "Verificado" en la página de perfil de la misma si verifican los dominios de la organización con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" en la documentación de {% data variables.product.prodname_ghe_cloud %}.
|
||||
{% elsif ghec or ghes > 3.1 %}
|
||||
{% elsif ghec or ghes %}
|
||||
Para confirmar la identidad de tu organización y mostrar una insignia de "Verificado" en su página de perfil, puedes verificar sus dominios con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ intro: 'Puedes administrar la forma en que {% data variables.product.product_nam
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: '*'
|
||||
ghes: '>=3.2'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
|
||||
@@ -32,33 +32,33 @@ También puedes {% ifversion fpt or ghec %}invitar{% else %}agregar{% endif %} u
|
||||
|
||||
El propietario del repositorio tiene control completo del repositorio. Adicionalmente a las acciones que pudiera realizar cualquier colaborador, el propietario del repositorio puede realizar las siguientes.
|
||||
|
||||
| Acción | Más información |
|
||||
|:------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| {% ifversion fpt or ghec %}Invitar colaboradores{% else %}Agregar colaboradores{% endif %} | |
|
||||
| "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | |
|
||||
| Acción | Más información |
|
||||
|:------------------------------------------------------------------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| {% ifversion fpt or ghec %}Invitar colaboradores{% else %}Agregar colaboradores{% endif %} | |
|
||||
| "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | |
|
||||
| Cambiar la visibilidad del repositorio | "[Configurar la visibilidad del repositorio](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
|
||||
| Limitar las interacciones con el repositorio | "[Limitar las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)"
|
||||
{% endif %}
|
||||
| Renombrar una rama, incluyendo la rama predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" |
|
||||
| Eliminar el repositorio | "[Borrar un repositorio](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
|
||||
| Renombrar una rama, incluyendo la rama predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" |
|
||||
| Eliminar el repositorio | "[Borrar un repositorio](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
|
||||
| Administrar los temas del repositorio | "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
|
||||
| Administrar la seguridad y la configuración de análisis del repositorio | "[Administrar la configuración de análisis y seguridad de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
|
||||
| Habilitar la gráfica de dependencias para un repositorio privado | "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
|
||||
| Borrar y restablecer paquetes | "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
| Habilitar la gráfica de dependencias para un repositorio privado | "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)"
|
||||
{% endif %}
|
||||
| Personalizar la vista previa de las redes sociales de un repositorio | "[Personalizar la vista previa de las redes sociales de tu repositorio](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
|
||||
| Crear una plantilla del repositorio | "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| Control access to {% data variables.product.prodname_dependabot_alerts %} | "[Administrar la configuración de análisis y seguridad de tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %}
|
||||
| Descartar las {% data variables.product.prodname_dependabot_alerts %} en el repositorio | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
|
||||
| Borrar y restablecer paquetes | "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
|
||||
| Personalizar la vista previa de las redes sociales de un repositorio | "[Personalizar la vista previa de las redes sociales de tu repositorio](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
|
||||
| Crear una plantilla del repositorio | "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |
|
||||
| Control access to {% data variables.product.prodname_dependabot_alerts %} | "[Administrar la configuración de análisis y seguridad de tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
|
||||
| Descartar las {% data variables.product.prodname_dependabot_alerts %} en el repositorio | "[Ver y actualizar{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
|
||||
| Administrar el uso de datos para un repositorio privado | "[Administrar la configuración del uso de datos para tu repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"
|
||||
{% endif %}
|
||||
| Definir propietarios del código para un repositorio | "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
|
||||
| Definir propietarios del código para un repositorio | "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
|
||||
| Archivar el repositorio | "[Archivar repositorios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
|
||||
| Crear asesorías de seguridad | "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
|
||||
| Crear asesorías de seguridad | "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
|
||||
| Mostrar el botón del patrocinador | "[Mostrar un botón de patrocinador en tu repositorio](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)"
|
||||
{% endif %}
|
||||
| Permitir o dejar de permitir la fusión automática para las solicitudes de cambios | "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" |
|
||||
| Permitir o dejar de permitir la fusión automática para las solicitudes de cambios | "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" |
|
||||
|
||||
## Acceso de colaborador para un repositorio que pertenezca a una cuenta personal
|
||||
|
||||
@@ -74,9 +74,8 @@ Los colaboradores también pueden realizar las siguientes acciones.
|
||||
|
||||
| Acción | Más información |
|
||||
|:-------------------------------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| Renombrar una rama diferente a la predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)"
|
||||
{% endif %}
|
||||
| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
|
||||
| Renombrar una rama diferente a la predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio | <ul><li>"[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)"</li><li>"[Comentar en una solicitud de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Administrar los comentarios perjudiciales](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
|
||||
| Crear, asignar, cerrar y volver a abrir las propuestas en el repositorio | "[Administrar tu trabajo con las propuestas](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
|
||||
| Administrar las etiquetas para las propuestas y solicitudes de cambios en el repositorio | "[Etiquetar las propuestas y solicitudes de cambios](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
|
||||
|
||||
@@ -179,7 +179,6 @@ Después de que se completa un flujo de trabajo, puedes cargar los artefactos qu
|
||||
|
||||
Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
|
||||
|
||||
|
||||
```yaml
|
||||
name: dotnet package
|
||||
|
||||
@@ -225,10 +224,10 @@ on:
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
packages: write
|
||||
contents: read{% endif %}
|
||||
contents: read
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-dotnet %}
|
||||
|
||||
@@ -279,10 +279,10 @@ on:
|
||||
jobs:
|
||||
build:
|
||||
name: Build + Publish
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
packages: write
|
||||
contents: read{% endif %}
|
||||
contents: read
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
|
||||
@@ -29,7 +29,7 @@ Puedes configurar un flujo de trabajo de {% data variables.product.prodname_acti
|
||||
|
||||
Puedes configurar tu flujo de trabajo de DC para que se ejecute cuando ocurra un evento de {% data variables.product.product_name %} (por ejemplo, cuando se sube código nuevo a la rama predeterminada de tu repositorio), en un horario establecido o cuando ocurre un evento externo que utilice el webhook de despacho. Para obtener más información sobre cuándo puede ejecutarse tu flujo de trabajo, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".
|
||||
|
||||
{% data variables.product.prodname_actions %} Proporciona características que te dan más control sobre los despliegues. Por ejemplo, puedes utilizar ambientes para requerir aprobaciones para que proceda un job, restringir que ramas pueden activar un flujo de trabajo o limitar el acceso a los secretos. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Puedes utilizar la concurrencia para limitar tu mapa de DC a un máximo de un despliegue en curso y uno pendiente. {% endif %}Para obtener más información sobre estas características, consulta las secciones "[Desplegar con las Github Actions](/actions/deployment/deploying-with-github-actions)" y "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)".
|
||||
{% data variables.product.prodname_actions %} Proporciona características que te dan más control sobre los despliegues. Por ejemplo, puedes utilizar ambientes para requerir aprobaciones para que proceda un job, restringir que ramas pueden activar un flujo de trabajo o limitar el acceso a los secretos. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %}
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
## Reglas de protección de ambiente
|
||||
|
||||
Las reglas de protección de ambiente requieren que pasen condiciones específicas antes de que un job que referencia al ambiente pueda proceder. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Puedes utilizar las reglas de protección de ambiente para requerir una aprobación manual, retrasar un job, o restringir el ambiente a ramas específicas.{% else %}Puedes utilizar la protección de ambiente para requerir una aprobación manual o retrasar un job.{% endif %}
|
||||
Las reglas de protección de ambiente requieren que pasen condiciones específicas antes de que un job que referencia al ambiente pueda proceder. Puedes utilizar reglas de protección de ambiente para requerir una aprobación manual, retrasar un job o restringir el ambiente a ramas específicas.
|
||||
|
||||
### Revisores requeridos
|
||||
|
||||
@@ -46,7 +46,6 @@ Para obtener más información sobre cómo revisar jobs que referencian un ambie
|
||||
|
||||
Utiliza un temporizador de espera para retrasar un job durante una cantidad de tiempo específica después de que el job se active inicialmente. El tiempo (en minutos) debe ser un número entero entre 0 y 43,200 (30 días).
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
### Ramas de despliegue
|
||||
|
||||
Utiliza ramas de despliegue para restringir las ramas que pueden hacer despliegues en el ambiente. A continuación encnotrarás las opciones para las ramas de despliegue de un ambiente:
|
||||
@@ -56,7 +55,6 @@ Utiliza ramas de despliegue para restringir las ramas que pueden hacer despliegu
|
||||
* **Ramas selectas**: Solo las ramas que coincidan con tus patrones específicos de nombre podrán hacer despliegues en el ambiente.
|
||||
|
||||
Por ejemplo, si especificas `releases/*` como una regla de rama de despliegue, solo aquellas ramas cuyo nombre inicie con `releases/` podrán hacer despliegues en el ambiente. (Los caracteres de comodín no coincidirán con `/`. Para hacer coincidir las ramas que inicien con `release/` y contengan una diagonal sencilla adicional utiliza `release/*/*`.) Si agregas `main` como regla de rama de despliegue, la rama que se llame `main` también podrá hacer despliegues en el ambiente. Para obtener más información sobre las opciones de sintaxis para las ramas de despliegue, consulta la [documentación de File.fnmatch de Ruby](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
|
||||
{% endif %}
|
||||
## Secretos de ambiente
|
||||
|
||||
Los secretos que se almacenan en un ambiente sólo se encuentran disponibles para los jobs de flujo de trabajo que referencien el ambiente. Si el ambiente requiere aprobación, un job no puede acceder a secretos de ambiente hasta que uno de los revisores requeridos lo apruebe. Para obtener más información sobre los secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)".
|
||||
@@ -101,7 +99,7 @@ Los secretos que se almacenan en un ambiente sólo se encuentran disponibles par
|
||||
1. Ingresa el valor del secreto.
|
||||
1. Haz clic en **Agregar secreto** (Agregar secreto).
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}También puedes crear y configurar ambientes a través de la API de REST. Para obtener más información, consulta las secciones de "[Ambientes](/rest/reference/repos#environments)" y "[Secretos](/rest/reference/actions#secrets)".{% endif %}
|
||||
También puedes crear y configurar ambientes a través de la API de REST. Para obtener más información, consulta las secciones "[Ambientes](/rest/reference/repos#environments)" y "[Secretos](/rest/reference/actions#secrets)".
|
||||
|
||||
El ejecutar un flujo de trabajo que referencie un ambiente que no existe creará un ambiente con el nombre referenciado. El ambiente recién creado no tendrá configurada ninguna regla de protección o secreto. Cualquiera que pueda editar flujos de trabajo en el repositorio podrá crear ambientes a través de un archivo de flujo de trabajo, pero solo los administradoresd e repositorio pueden configurar el ambiente.
|
||||
|
||||
@@ -125,13 +123,13 @@ El borrar un ambiente borrará todos los secretos y reglas de protección asocia
|
||||
1. Junto al ambiente que quieres borrar, haz clic en {% octicon "trash" aria-label="The trash icon" %}.
|
||||
2. Da clic en **Entiendo, borra este ambiente**.
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}También puedes borrar los ambientes a través de la API de REST Para obtener más información, consulta la sección "[Ambientes](/rest/reference/repos#environments)".{% endif %}
|
||||
También puyedes borrar ambientes a través de la API de REST. Para obtener más información, consulta la sección "[Ambientes](/rest/reference/repos#environments)".
|
||||
|
||||
## Cómo se relacionan los ambientes con los desplilegues
|
||||
|
||||
{% data reusables.actions.environment-deployment-event %}
|
||||
|
||||
Puedes acceder a estos objetos a través de la API de REST o la API de GraphQL. También puedes suscribirte a estos eventos de webhook. Para obtener más información, consulta las secciones "[Repositorios](/rest/reference/repos#deployments)" (API de REST), "[Objetos]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)"(API de GraphQL) o "[Cargas útiles y eventos de Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)".
|
||||
Puedes acceder a estos objetos a través de la API de REST o la API de GraphQL. También puedes suscribirte a estos eventos de webhook. Para obtener más información, consulta las secciones "[Repositorios](/rest/reference/repos#deployments)" (API de REST), "[Objetos](/graphql/reference/objects#deployment)"(API de GraphQL) o "[Cargas útiles y eventos de Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)".
|
||||
|
||||
## Pasos siguientes
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.settings-sidebar-actions-runners %}
|
||||
1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
|
||||
1. Under {% ifversion ghes or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
|
||||
{% data reusables.actions.self-hosted-runner-configure %}
|
||||
{% endif %}
|
||||
{% data reusables.actions.self-hosted-runner-check-installation-success %}
|
||||
@@ -77,7 +77,7 @@ You can add self-hosted runners at the organization level, where they can be use
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runners %}
|
||||
1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
|
||||
1. Under {% ifversion ghes or ghae %}"Runners", click **Add new**, then click **New runner**.{% endif %}
|
||||
{% data reusables.actions.self-hosted-runner-configure %}
|
||||
{% endif %}
|
||||
{% data reusables.actions.self-hosted-runner-check-installation-success %}
|
||||
|
||||
@@ -54,23 +54,23 @@ The `prepare_job` command is called when a job is started. {% data variables.pro
|
||||
#### Argumentos
|
||||
|
||||
- `jobContainer`: **Optional**. An object containing information about the specified job container.
|
||||
- `image`: **Required**. A string containing the Docker image.
|
||||
- `image`: **Opcional**. A string containing the Docker image.
|
||||
- `workingDirectory`: **Required**. A string containing the absolute path of the working directory.
|
||||
- `createOptions`: **Optional**. The optional _create_ options specified in the YAML. For more information, see "[Example: Running a job within a container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container)."
|
||||
- `environmentVariables`: **Optional**. Sets a map of key environment variables.
|
||||
- `createOptions`: **Opcional**. The optional _create_ options specified in the YAML. For more information, see "[Example: Running a job within a container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container)."
|
||||
- `environmentVariables`: **Opcional**. Sets a map of key environment variables.
|
||||
- `userMountVolumes`: **Optional**. An array of user mount volumes set in the YAML. For more information, see "[Example: Running a job within a container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container)."
|
||||
- `sourceVolumePath`: **Required**. The source path to the volume that will be mounted into the Docker container.
|
||||
- `targetVolumePath`: **Required**. The target path to the volume that will be mounted into the Docker container.
|
||||
- `readOnly`: **Required**. Determines whether or not the mount should be read-only.
|
||||
- `systemMountVolumes`: **Required**. An array of mounts to mount into the container, same fields as above.
|
||||
- `sourceVolumePath`: **Requerido**. The source path to the volume that will be mounted into the Docker container.
|
||||
- `targetVolumePath`: **Requerido**. The target path to the volume that will be mounted into the Docker container.
|
||||
- `readOnly`: **Opcional**. Determines whether or not the mount should be read-only.
|
||||
- `systemMountVolumes`: **Requerido**. An array of mounts to mount into the container, same fields as above.
|
||||
- `sourceVolumePath`: **Requerido**. The source path to the volume that will be mounted into the Docker container.
|
||||
- `targetVolumePath`: **Requerido**. The target path to the volume that will be mounted into the Docker container.
|
||||
- `readOnly`: **Opcional**. Determines whether or not the mount should be read-only.
|
||||
- `registro` **Optional**. The Docker registry credentials for a private container registry.
|
||||
- `username`: **Optional**. The username of the registry account.
|
||||
- `password`: **Optional**. The password to the registry account.
|
||||
- `serverUrl`: **Optional**. The registry URL.
|
||||
- `portMappings`: **Optional**. A key value hash of _source:target_ ports to map into the container.
|
||||
- `password`: **Opcional**. The password to the registry account.
|
||||
- `serverUrl`: **Opcional**. The registry URL.
|
||||
- `portMappings`: **Opcional**. A key value hash of _source:target_ ports to map into the container.
|
||||
- `services`: **Optional**. An array of service containers to spin up.
|
||||
- `contextName`: **Required**. The name of the service in the Job context.
|
||||
- `image`: **Opcional**. A string containing the Docker image.
|
||||
@@ -251,12 +251,12 @@ The `run_container_step` command is called once for each container action in you
|
||||
|
||||
- `image`: **Optional**. A string containing the docker image. Otherwise a dockerfile must be provided.
|
||||
- `dockerfile`: **Optional**. A string containing the path to the dockerfile, otherwise an image must be provided.
|
||||
- `entryPointArgs`: **Optional**. A list containing the entry point args.
|
||||
- `entryPoint`: **Optional**. The container entry point to use if the default image entrypoint should be overwritten.
|
||||
- `entryPointArgs`: **Opcional**. A list containing the entry point args.
|
||||
- `entryPoint`: **Opcional**. The container entry point to use if the default image entrypoint should be overwritten.
|
||||
- `workingDirectory`: **Required**. A string containing the absolute path of the working directory.
|
||||
- `createOptions`: **Opcional**. The optional _create_ options specified in the YAML. For more information, see "[Example: Running a job within a container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container)."
|
||||
- `environmentVariables`: **Opcional**. Sets a map of key environment variables.
|
||||
- `prependPath`: **Optional**. An array of additional paths to prepend to the `$PATH` variable.
|
||||
- `prependPath`: **Opcional**. An array of additional paths to prepend to the `$PATH` variable.
|
||||
- `userMountVolumes`: **Optional**. an array of user mount volumes set in the YAML. For more information, see "[Example: Running a job within a container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container)."
|
||||
- `sourceVolumePath`: **Requerido**. The source path to the volume that will be mounted into the Docker container.
|
||||
- `targetVolumePath`: **Requerido**. The target path to the volume that will be mounted into the Docker container.
|
||||
@@ -527,4 +527,4 @@ There is currently no timeout setting available for the script executed by `ACTI
|
||||
|
||||
### Reviewing the workflow run log
|
||||
|
||||
To confirm whether your scripts are executing, you can review the logs for that job. For more information on checking the logs, see "[Viewing logs to diagnose failures](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
|
||||
To confirm whether your scripts are executing, you can review the logs for that job. Para obtener más información sobre cómo verificar las bitácoras, consulta la sección "[Visualizar las bitácoras para diagnosticar las fallas](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)".
|
||||
|
||||
@@ -67,7 +67,7 @@ Cuando creas un grupo, debes elegir la política que define qué reositorios{% i
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
|
||||
1. Debajo de {% ifversion ghes > 3.1 or ghae %}"Ejecutores"{% elsif ghes < 3.2 %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar nuevo** y luego en **Grupo nuevo**.
|
||||
1. Debajo de {% ifversion ghes or ghae %}"Ejecutores"{% endif %}, haz clic en **Agregar nuevo** y luego en **Grupo nuevo**.
|
||||
|
||||
|
||||
1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso al repositorio.
|
||||
@@ -204,7 +204,7 @@ Si no especificas un grupo de ejecutores durante el proceso de registro, tus eje
|
||||
2. Selecciona el menú desplegable de **Grupo de ejecutores**.
|
||||
3. En "Mover el ejecutor al grupo", elige un grupo destino para el ejecutor.
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
1. En la sección de {% ifversion ghes > 3.1 or ghae %}"Grupos de ejecutores"{% elsif ghes < 3.2 %}"Ejecutores auto-hospedados"{% endif %} de la página de ajustes, ubica al grupo actual del ejecutor que quieres mover y expande la lista de sus miembros. 
|
||||
1. En la sección {% ifversion ghes or ghae %}"Grupos de ejecutores"{% endif %} de la página de ajustes, ubica el grupo actual del ejecutor que quieras mover y expande la lista de miembros del grupo. 
|
||||
2. Selecciona la casilla junto al ejecutor auto-hospedado y da clic en **Mover a grupo** para ver los destinos disponibles. 
|
||||
3. Para mover el ejecutor, da clic en el grupo de destino. 
|
||||
{% endif %}
|
||||
@@ -213,16 +213,11 @@ Si no especificas un grupo de ejecutores durante el proceso de registro, tus eje
|
||||
|
||||
Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina.
|
||||
|
||||
{% ifversion ghes > 3.1 or ghae or ghec %}
|
||||
{% ifversion ghes or ghae or ghec %}
|
||||
{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
|
||||
1. En la lista de grupos, a la derecha del grupo que quieras borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
|
||||
2. Para eliminar el grupo, da clic en **Eliminar grupo**.
|
||||
3. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**.
|
||||
{% elsif ghes < 3.2 %}
|
||||
1. En la sección de "Ejecutores auto-hospedados" de la página de ajustes, ubica el grupo que quieras borrar y haz clic en el botón {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 
|
||||
|
||||
1. Para eliminar el grupo, da clic en **Eliminar grupo**. 
|
||||
|
||||
1. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**.
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -24,7 +24,7 @@ shortTitle: Monitor & troubleshoot
|
||||
|
||||
{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runners %}
|
||||
1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status.
|
||||
1. Under "Runners", you can view a list of registered runners, including the runner's name, labels, and status.
|
||||
|
||||
The status can be one of the following:
|
||||
|
||||
@@ -167,7 +167,6 @@ If you want to customize the self-hosted runner application service, do not dire
|
||||
|
||||
{% endmac %}
|
||||
|
||||
|
||||
{% windows %}
|
||||
|
||||
## Using PowerShell to check the self-hosted runner application service
|
||||
@@ -265,4 +264,4 @@ User=runner-user
|
||||
{% data reusables.actions.upgrade-runners-before-upgrade-ghes %}
|
||||
|
||||
If your runners are offline for this reason, manually update the runners. For more information, see the installation instructions for [the latest release](https://github.com/actions/runner/releases/latest) in the actions/runner repository.
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -40,7 +40,7 @@ Your custom scripts can use the following features:
|
||||
|
||||
### Handling exit codes
|
||||
|
||||
For pre-job scripts, exit code `0` indicates that the script completed successfully, and the job will then proceed to run. If there is any other exit code, the job will not run and will be marked as failed. To see the results of your pre-job scripts, check the logs for `Set up runner` entries. For more information on checking the logs, see "[Viewing logs to diagnose failures](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
|
||||
For pre-job scripts, exit code `0` indicates that the script completed successfully, and the job will then proceed to run. If there is any other exit code, the job will not run and will be marked as failed. To see the results of your pre-job scripts, check the logs for `Set up runner` entries. Para obtener más información sobre cómo verificar las bitácoras, consulta la sección "[Visualizar las bitácoras para diagnosticar las fallas](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)".
|
||||
|
||||
The [`continue-on-error`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) setting is not supported for use by these scripts.
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ versions:
|
||||
children:
|
||||
- /quickstart
|
||||
- /learn-github-actions
|
||||
- /examples
|
||||
- /examples
|
||||
- /using-workflows
|
||||
- /using-jobs
|
||||
- /managing-workflow-runs
|
||||
@@ -69,3 +69,4 @@ children:
|
||||
- /creating-actions
|
||||
- /guides
|
||||
---
|
||||
|
||||
|
||||
@@ -798,4 +798,4 @@ jobs:
|
||||
{% endraw %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -155,7 +155,7 @@ steps:
|
||||
|
||||
### Utilizar SHAs
|
||||
|
||||
Si necesitas utilizar un versionamiento más confiable, debes utilizar el valor de SHA asociado con la versión de la acción. Los SHA son inmutables y, por lo tanto, más confiables que las etiquetas o las ramas. Sin embargo, este acercamiento significa que no recibirás actualizaciones para una acción automáticamente, incluyendo las correcciones de errores y actualizaciones de seguridad. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Debes utiliza run valor completo del SHA de la confirmación y no un valor abreviado. {% endif %}Este ejemplo apunta al SHA de una acción:
|
||||
Si necesitas utilizar un versionamiento más confiable, debes utilizar el valor de SHA asociado con la versión de la acción. Los SHA son inmutables y, por lo tanto, más confiables que las etiquetas o las ramas. Sin embargo, este acercamiento significa que no recibirás actualizaciones para una acción automáticamente, incluyendo las correcciones de errores y actualizaciones de seguridad. Debes utilizar un valor SHA completo de la confirmación y no un valor abreviado. Este ejemplo apunta al SHA de una acción:
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
|
||||
@@ -60,7 +60,7 @@ Hay algunos límites de uso de {% data variables.product.prodname_actions %} cua
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If required, customers on enterprise plans can request a higher limit for concurrent jobs. For more information, contact {% data variables.contact.contact_ent_support %} or your sales representative.
|
||||
**Nota:** De ser necesario, los clientes con planes empresariales pueden solicitar un límite superior para los jobs simultáneos. Para obtener más información, contacta a {% data variables.contact.contact_ent_support %} o a tu representante de ventas.
|
||||
|
||||
{% endnote %}
|
||||
- **Matiz de jobs** - {% data reusables.actions.usage-matrix-limits %}
|
||||
|
||||
@@ -40,9 +40,9 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
|
||||
- opened
|
||||
jobs:
|
||||
label_issues:
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
issues: write{% endif %}
|
||||
issues: write
|
||||
steps:
|
||||
- name: Label issues
|
||||
uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90
|
||||
|
||||
@@ -37,10 +37,10 @@ En el tutorial, prmero crearás un archivo de flujo de trabajo que utilice la [a
|
||||
|
||||
jobs:
|
||||
close-issues:
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
issues: write
|
||||
pull-requests: write{% endif %}
|
||||
pull-requests: write
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-stale %}
|
||||
with:
|
||||
|
||||
@@ -41,9 +41,9 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
|
||||
jobs:
|
||||
add-comment:
|
||||
if: github.event.label.name == 'help-wanted'
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
issues: write{% endif %}
|
||||
issues: write
|
||||
steps:
|
||||
- name: Add comment
|
||||
uses: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae
|
||||
|
||||
@@ -42,10 +42,10 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
|
||||
jobs:
|
||||
remove_labels:
|
||||
if: github.event.project_card.column_id == '12345678'
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
issues: write
|
||||
pull-requests: write{% endif %}
|
||||
pull-requests: write
|
||||
steps:
|
||||
- name: remove labels
|
||||
uses: andymckay/labeler@5c59dabdfd4dd5bd9c6e6d255b01b9d764af4414
|
||||
|
||||
@@ -40,9 +40,9 @@ En el tutorial, primero crearás un archivo de flujo de trabajo que utilice la [
|
||||
jobs:
|
||||
create_issue:
|
||||
name: Create team sync issue
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
issues: write{% endif %}
|
||||
issues: write
|
||||
steps:
|
||||
- name: Create team sync issue
|
||||
uses: imjohnbo/issue-bot@3daae12aa54d38685d7ff8459fc8a2aee8cea98b
|
||||
|
||||
@@ -14,7 +14,7 @@ versions:
|
||||
|
||||
Los jobs que referencian un ambiente configurado con revisores requeridos esperarán por una aprobación antes de comenzar. Mientras que un job espera su revisión, tendrá un estado de "Waiting". Si un job no se aprueba dentro de 30 días, la ejecución del flujo de trabajo se cancelará automáticamente.
|
||||
|
||||
Para obtener más información sobre los ambientes y aprobaciones requeridos, consulta la sección"[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)".{% ifversion fpt or ghae or ghes > 3.1 or ghec %} Para obtener información sobre cómo revisar los despliegues con la API de REST, consulta la sección "[Ejecuciones de flujo de trabajo](/rest/reference/actions#workflow-runs)".{% endif %}
|
||||
For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." Para obtener más información sobre cómo revisar los despliegues con la API de REST, consulta la sección "[Ejecutores de Flujo de Trabajo](/rest/reference/actions#workflow-runs)".
|
||||
|
||||
## Aprobar o rechazar un job
|
||||
|
||||
|
||||
@@ -22,8 +22,6 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
|
||||
|
||||
### Utilizar la gráfica de visualización
|
||||
|
||||
Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilustra el progreso de la misma. Puedes utilizar esta gráfica para monitorear y depurar los flujos de trabajo. Por ejemplo:
|
||||
@@ -32,8 +30,6 @@ Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilust
|
||||
|
||||
Para obtener más información, consulta la sección "[Utilizar el gráfico de visualización](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Agregar una insignia de estado de flujo de trabajo
|
||||
|
||||
{% data reusables.repositories.actions-workflow-status-badge-intro %}
|
||||
|
||||
@@ -153,10 +153,10 @@ on:
|
||||
jobs:
|
||||
push_to_registry:
|
||||
name: Push Docker image to GitHub Packages
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
packages: write
|
||||
contents: read{% endif %}
|
||||
contents: read
|
||||
steps:
|
||||
- name: Check out the repo
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
@@ -203,10 +203,10 @@ on:
|
||||
jobs:
|
||||
push_to_registries:
|
||||
name: Push Docker image to multiple registries
|
||||
runs-on: {% ifversion ghes %}[self-hosted]{% else %}ubuntu-latest{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: {% ifversion ghes %}[self-hosted]{% else %}ubuntu-latest{% endif %}
|
||||
permissions:
|
||||
packages: write
|
||||
contents: read{% endif %}
|
||||
contents: read
|
||||
steps:
|
||||
- name: Check out the repo
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
|
||||
@@ -154,10 +154,10 @@ on:
|
||||
types: [created]
|
||||
jobs:
|
||||
publish:
|
||||
runs-on: ubuntu-latest {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
contents: read
|
||||
packages: write {% endif %}
|
||||
packages: write
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
@@ -175,7 +175,7 @@ jobs:
|
||||
```
|
||||
|
||||
{% data reusables.actions.gradle-workflow-steps %}
|
||||
1. Ejecuta la acción [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) con el argumento `publish` para publicar al {% data variables.product.prodname_registry %}. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% endif %}
|
||||
1. Ejecuta la acción [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) con el argumento `publish` para publicar al {% data variables.product.prodname_registry %}. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.
|
||||
|
||||
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
|
||||
|
||||
@@ -232,10 +232,10 @@ on:
|
||||
types: [created]
|
||||
jobs:
|
||||
publish:
|
||||
runs-on: ubuntu-latest {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
contents: read
|
||||
packages: write {% endif %}
|
||||
packages: write
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Set up Java
|
||||
@@ -256,6 +256,6 @@ jobs:
|
||||
```
|
||||
|
||||
{% data reusables.actions.gradle-workflow-steps %}
|
||||
1. Ejecuta la acción [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) con el argumento `publish` para publicar en el repositorio `OSSRH` de Maven y en el {% data variables.product.prodname_registry %}. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% endif %}
|
||||
1. Ejecuta la acción [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) con el argumento `publish` para publicar en el repositorio `OSSRH` de Maven y en el {% data variables.product.prodname_registry %}. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.
|
||||
|
||||
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
|
||||
|
||||
@@ -73,7 +73,6 @@ Con esta configuración, puedes crear un flujo de trabajo que publique tu paquet
|
||||
|
||||
En el paso de implementación, necesitarás establecer las variables de entorno para el nombre de usuario con el que te autenticaste en el repositorio y para el secreto que hayas configurado con la contraseña o el token con que autenticarse. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
|
||||
|
||||
|
||||
```yaml{:copy}
|
||||
name: Publish package to the Maven Central Repository
|
||||
on:
|
||||
@@ -143,10 +142,10 @@ on:
|
||||
types: [created]
|
||||
jobs:
|
||||
publish:
|
||||
runs-on: ubuntu-latest {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
contents: read
|
||||
packages: write {% endif %}
|
||||
packages: write
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
@@ -180,10 +179,10 @@ on:
|
||||
types: [created]
|
||||
jobs:
|
||||
publish:
|
||||
runs-on: ubuntu-latest {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
contents: read
|
||||
packages: write {% endif %}
|
||||
packages: write
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Set up Java for publishing to Maven Central Repository
|
||||
|
||||
@@ -128,10 +128,10 @@ on:
|
||||
types: [created]
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
contents: read
|
||||
packages: write {% endif %}
|
||||
packages: write
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
# Setup .npmrc file to publish to GitHub Packages
|
||||
|
||||
@@ -31,13 +31,11 @@ The token is also available in the `github.token` context. For more information,
|
||||
|
||||
You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Important:** An action can access the `GITHUB_TOKEN` through the `github.token` context even if the workflow does not explicitly pass the `GITHUB_TOKEN` to the action. As a good security practice, you should always make sure that actions only have the minimum access they require by limiting the permissions granted to the `GITHUB_TOKEN`. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.actions.actions-do-not-trigger-workflows %}
|
||||
|
||||
@@ -56,9 +54,9 @@ on: [ push ]
|
||||
|
||||
jobs:
|
||||
create_commit:
|
||||
runs-on: ubuntu-latest {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
issues: write {% endif %}
|
||||
issues: write
|
||||
steps:
|
||||
- name: Create issue using REST API
|
||||
run: |
|
||||
@@ -77,7 +75,6 @@ jobs:
|
||||
|
||||
For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
|
||||
|
||||
| Scope | Default access<br>(permissive) | Default access<br>(restricted) | Maximum access<br>by forked repos |
|
||||
@@ -97,24 +94,9 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
|
||||
| repository-projects | read/write | none | read |
|
||||
| security-events | read/write | none | read |
|
||||
| statuses | read/write | none | read |
|
||||
{% else %}
|
||||
| Scope | Access type | Access by forked repos |
|
||||
|----------|-------------|--------------------------|
|
||||
| actions | read/write | read |
|
||||
| checks | read/write | read |
|
||||
| contents | read/write | read |
|
||||
| deployments | read/write | read |
|
||||
| issues | read/write | read |
|
||||
| metadata | read | read |
|
||||
| packages | read/write | read |
|
||||
| pull-requests | read/write | read |
|
||||
| repository-projects | read/write | read |
|
||||
| statuses | read/write | read |
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.actions.workflow-runs-dependabot-note %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
### Modifying the permissions for the `GITHUB_TOKEN`
|
||||
|
||||
You can modify the permissions for the `GITHUB_TOKEN` in individual workflow files. If the default permissions for the `GITHUB_TOKEN` are restrictive, you may have to elevate the permissions to allow some actions and commands to run successfully. If the default permissions are permissive, you can edit the workflow file to remove some permissions from the `GITHUB_TOKEN`. As a good security practice, you should grant the `GITHUB_TOKEN` the least required access.
|
||||
@@ -134,7 +116,6 @@ For full details of the `permissions` key, see "[Workflow syntax for {% data var
|
||||
The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only.
|
||||
|
||||
### Granting additional permissions
|
||||
{% endif %}
|
||||
|
||||
If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a personal access token and set it as a secret in your repository:
|
||||
|
||||
|
||||
@@ -40,8 +40,8 @@ Para ayudar a prevenir la divulgación accidental, {% data variables.product.pro
|
||||
- Audita cómo se utilizan los secretos para ayudarte a garantizar que se manejan como lo esperas. Puedes hacer esto si revisas el código fuente del rpositorio que ejecuta el flujo de trabajo y verificas cualquier acción que se utilice en dicho flujo de trabajo. Por ejemplo, verifica que no se estén enviando a hosts no deseados, o que no se estén imprimiendo explícitamente en la salida de una bitácora.
|
||||
- Visualiza las bitácoras de ejecución de tu flujo de trabajo después de probar las entradas válidas/no válidas y verifica que los secretos se redacten adecuadamente o que no se muestren. No siempre es obvio la forma en la que una herramienta o un comando que estés invocando enviará los errores a `STDOUT` o a `STDERR`, y los secretos pueden terminar siendo bitácoras de errores después. Por consiguiente, es una buena práctica el revisar manualmente las bitácoras de flujo de trabajo después de probar las entradas válidas y no válidas.
|
||||
- **Utiliza credenciales que tengan alcances mínimos**
|
||||
- Asegúrate de que las credenciales que estás utilizando dentro de los flujos de trabajo tengan los menores privilegios requeridos y ten en mente que cualquier usuario con acceso de escritura en tu repositorio tiene acceso de lectura para todos los secretos que has configurado en éste. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
- Las acciones pueden utilizar el `GITHUB_TOKEN` si acceden a él desde el contexto `github.token`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#github-context)". Por lo tanto, debes asegurarte de que se otorguen los permisos mínimos requeridos al `GITHUB_TOKEN`. Configurar el permiso predeterminado el `GITHUB_TOKEN` como acceso de solo lectura para el contenido de los repositorios, es una buena práctica de seguridad. Se puede incrementar los permisos, conforme se requiera, para los jobs individuales dentro del archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". {% endif %}
|
||||
- Asegúrate de que las credenciales que estás utilizando dentro de los flujos de trabajo tengan los menores privilegios requeridos y ten en mente que cualquier usuario con acceso de escritura en tu repositorio tiene acceso de lectura para todos los secretos que has configurado en éste.
|
||||
- Las acciones pueden utilizar el `GITHUB_TOKEN` si acceden a él desde el contexto `github.token`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#github-context)". Por lo tanto, debes asegurarte de que se otorguen los permisos mínimos requeridos al `GITHUB_TOKEN`. Configurar el permiso predeterminado el `GITHUB_TOKEN` como acceso de solo lectura para el contenido de los repositorios, es una buena práctica de seguridad. Se puede incrementar los permisos, conforme se requiera, para los jobs individuales dentro del archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".
|
||||
- **Audita y rota los secretos registrados**
|
||||
- Revisa con frecuencia los secretos que se han registrado para confirmar que aún se requieran. Elimina aquellos que ya no se necesiten.
|
||||
- Rota los secretos con frecuencia para reducir la ventana de tiempo en la que un secreto puesto en riesgo es aún válido.
|
||||
@@ -179,8 +179,6 @@ Puedes ayudar a mitigar este riesgo si sigues estas buenas prácticas:
|
||||
|
||||
Fijar una acción a un SHA de confirmación de longitud completa es actualmente la única forma de utilizar una acción como un lanzamiento inmutable. Fijar las acciones a un SHA en particular ayuda a mitigar el riesgo de que un actor malinencionado agregue una puerta trasera al repositorio de la acción, ya que necesitarían generar una colisión de SHA-1 para una carga útil vlálida de un objeto de Git.
|
||||
|
||||
|
||||
|
||||
* **Audita el código fuente de la acción**
|
||||
|
||||
Asegúrate de que la acción está manejando los secretos y el contenido de tu repositorio como se espera. Por ejemplo, verifica que los secretos no se envíen a hosts no deseados, o que no se registren inadvertidamente.
|
||||
@@ -249,14 +247,14 @@ El servidor atacante puede utilizar la API de {% ifversion fpt or ghec %}{% data
|
||||
|
||||
## Considerar acceso entre repositorios
|
||||
|
||||
{% data variables.product.prodname_actions %} tiene el alcance intencional de un solo repositorio a la vez. El `GITHUB_TOKEN` otorga el mismo nivel de acceso que el de un usuario con acceso de escritura, ya que cualquier usuario con este tipo de acceso puede acceder al token si crea o modifica un archivo de flujo de trabajo {% ifversion fpt or ghes > 3.1 or ghae or ghec %}, lo cual eleva los permisos del `GITHUB_TOKEN` en caso de que sea necesario{% endif %}. Los usuarios tienen permisos específicos para cada repositorio, así que, permitir que el `GITHUB_TOKEN` de un repositorio otorgue acceso a otro de ellos impactará el modelo de permisos de {% data variables.product.prodname_dotcom %} si no se implementa con cuidado. De forma similar, se debe tener cuidado al agregar tokens de autenticación de {% data variables.product.prodname_dotcom %} a un flujo de trabajo, ya que esto también puede afectar el modelo de permisos de {% data variables.product.prodname_dotcom %} al otorgar inadvertidamente un acceso amplio a los colaboradores.
|
||||
{% data variables.product.prodname_actions %} tiene el alcance intencional de un solo repositorio a la vez. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying a workflow file, elevating the permissions of the `GITHUB_TOKEN` if necessary. Los usuarios tienen permisos específicos para cada repositorio, así que, permitir que el `GITHUB_TOKEN` de un repositorio otorgue acceso a otro de ellos impactará el modelo de permisos de {% data variables.product.prodname_dotcom %} si no se implementa con cuidado. De forma similar, se debe tener cuidado al agregar tokens de autenticación de {% data variables.product.prodname_dotcom %} a un flujo de trabajo, ya que esto también puede afectar el modelo de permisos de {% data variables.product.prodname_dotcom %} al otorgar inadvertidamente un acceso amplio a los colaboradores.
|
||||
|
||||
Tenemos [un plan en el itinerario de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap/issues/74) para compatibilizar un flujo que permita acceso entre repositorios dentro de {% data variables.product.product_name %}, pero aún no es una característica compatible. Actualmente, la única forma de realizar interacciones privilegiadas entre repositorios es colocar un token de autenticación de {% data variables.product.prodname_dotcom %} o llave SSH como un secreto dentro del flujo de trabajo. Ya que muchos tipos de tokens de autenticación no permiten el acceso granular a recursos específicos, existe un riesgo significativo en el utilizar el tipo incorrecto de token, ya que puede otorgr un acceso mucho más amplio que lo que se espera.
|
||||
|
||||
Esta lista describe los acercamientos recomendatos para acceder alos datos de un repositorio dentro de un flujo de trabjajo, en orden descendente de preferencia:
|
||||
|
||||
1. **El `GITHUB_TOKEN`**
|
||||
- A este token se le da el alcance, a propósito, del único repositorio que invocó el flujo de trabajo y {% ifversion fpt or ghes > 3.1 or ghae or ghec %}puede tener {% else %}tiene {% endif %} el mismo nivel de acceso que el de un usuario con acceso de escritura en dicho repositorio. El token se crea antes de que inicie cada job y caduca cuando dicho job finaliza. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
|
||||
- This token is intentionally scoped to the single repository that invoked the workflow, and can have the same level of access as a write-access user on the repository. El token se crea antes de que inicie cada job y caduca cuando dicho job finaliza. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
|
||||
- El `GITHUB_TOKEN` debe utilizarse cada que sea posible.
|
||||
2. **Llave de despliegue del repositorio**
|
||||
- Las llaves de despliegue son uno de los únicos tipos de credenciales que otorgan acceso de lectura o escritura en un solo repositorio, y pueden utilizarse para interactuar con otro repositorio dentro de un flujo de trabajo. Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys#deploy-keys)".
|
||||
@@ -277,7 +275,7 @@ Los ejecutores **hospedados en {% data variables.product.prodname_dotcom %}** ej
|
||||
|
||||
{% ifversion fpt or ghec %}Los ejecutores **auto-hospedados**{% elsif ghes or ghae %}Los ejecutores auto-hospedados{% endif %} para {% data variables.product.product_name %} no tienen garantías sobre ejecutar en máquinas virtuales limpias y efímeras y pueden ponerse en riesgo persistentemente mediante el código no confiable en un flujo de trabajo.
|
||||
|
||||
{% ifversion fpt or ghec %}Como resultado, los ejecutores auto-hospedados no deberán [utilizarse casi nunca para repositorios públicos](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) en {% data variables.product.product_name %}, ya que cualquier usuario puede abrir solicitudes de extracción contra este repositorio y poner en riesgo el ambiente. De forma similar, ten{% elsif ghes or ghae %}Ten{% endif %} cuidado al utilizar ejecutores auto-hospedados en repositorios privados o internos, ya que cualquiera que pueda bifurcar el repositorio y abrir una solicitud de cambios (habitualmente, aquellos con acceso de lectura al mismo) pueden poner en riesgo el ambiente del ejecutor auto-hospedado, incluyendo el obtener acceso a los secretos y al `GITHUB_TOKEN` que,{% ifversion fpt or ghes > 3.1 or ghae or ghec %} dependiendo de su configuración, puede otorgar{% else %} otorga{% endif %}acceso de escritura al repositorio. Aunque los flujos de trabajo pueden controlar el acceso a los secretos de ambiente utilizando ambientes y revisiones requeridas, estos flujos de trabajo no se encuentran en un ambiente aislado y aún son susceptibles a los mismos riesgos cuando se ejecutan en un ejecutor auto-hospedado.
|
||||
{% ifversion fpt or ghec %}Como resultado, los ejecutores auto-hospedados no deberán [utilizarse casi nunca para repositorios públicos](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) en {% data variables.product.product_name %}, ya que cualquier usuario puede abrir solicitudes de extracción contra este repositorio y poner en riesgo el ambiente. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Aunque los flujos de trabajo pueden controlar el acceso a los secretos de ambiente utilizando ambientes y revisiones requeridas, estos flujos de trabajo no se encuentran en un ambiente aislado y aún son susceptibles a los mismos riesgos cuando se ejecutan en un ejecutor auto-hospedado.
|
||||
|
||||
Cuando se define un ejecutor auto-hospedado a nivel de organización o de empresa, {% data variables.product.product_name %} puede programar flujos de trabajo de repositorios múltiples en el mismo ejecutor. Como consecuencia, si se pone en riesgo la seguridad de estos ambientes, se puede ocasionar un impacto amplio. Para ayudar a reducir el alcance de esta vulneración, puedes crear límites si organizas tus ejecutores auto-hospedados en grupos separados. Puedes restringir a qué {% ifversion restrict-groups-to-workflows %}flujos de trabajo, {% endif %}organizaciones y repositorios pueden acceder los grupos de ejecutores. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
|
||||
|
||||
@@ -348,21 +346,21 @@ Las siguientes tablas describen los eventos de {% data variables.product.prodnam
|
||||
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `enterprise.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una empresa](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)". |
|
||||
| `enterprise.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. |
|
||||
| `enterprise.runner_group_runners_updated` | Se activa cuando la lista de miembros de un grupo de ejecutores se actualiza. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| `enterprise.runner_group_runners_updated` | Se activa cuando la lista de miembros de un grupo de ejecutores se actualiza. Para obtener más información, consulta la sección "[Configurar ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". |
|
||||
| `enterprise.self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
|
||||
| `enterprise.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
|
||||
| `enterprise.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
|
||||
| `enterprise.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Puede visualizarse utilizando la API de REST y la IU. Este evento no se incluye cuando exportas la bitácora de auditoría como datos de JSON o como un archivo de CSV. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" y "[Revisar la bitácora de auditoría en tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)". |
|
||||
| `org.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". |
|
||||
| `org.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección [Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). |
|
||||
| `org.runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". |
|
||||
| `org.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[cambiar la política de acceso de un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| `org.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". |
|
||||
| `org.self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
|
||||
| `org.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
|
||||
| `org.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
|
||||
| `org.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." |
|
||||
| `repo.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". |
|
||||
| `repo.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)".{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| `repo.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". |
|
||||
| `repo.self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
|
||||
| `repo.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
|
||||
| `repo.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
|
||||
| `repo.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." |
|
||||
|
||||
### Eventos para grupos de ejecutores auto-hospedados
|
||||
|
||||
@@ -923,7 +923,7 @@ on:
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: When a `push` webhook event triggers a workflow run, the Actions UI's "pushed by" field shows the account of the pusher and not the author or committer. However, if the changes are pushed to a repository using SSH authentication with a deploy key, then the "pushed by" field will be the repository admin who verified the deploy key when it was added it to a repository.
|
||||
**Nota**: Cuando un evento de webhook de `push` activa una ejecución de flujo de trabajo, el campo "pushed by" de la IU de la acción muestra la cuenta de la persona que sube información y no del autor o confirmante. Sin embargo, si los cambios se suben a un repositorio utilizando autenticación SSH con una llave de despliegue, entonces el campo "subido por" será el adminsitrador del repositorio quien verificó la llave de despliegue cuando s e agregó al repositorio.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -958,7 +958,7 @@ on:
|
||||
|
||||
#### Ejecutar tu flujo de trabajo únicamente cuando ocurra una subida de etiquetas específicas
|
||||
|
||||
You can use the `tags` or `tags-ignore` filter to configure your workflow to only run when specific tags are pushed. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para las GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)".
|
||||
Puedes utilizar el filtro `tags` o `tags-ignore` para configurar tu flujo de trabajo para que solo se ejecute cuando se suban etiquetas específicas. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para las GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)".
|
||||
|
||||
Por ejemplo, este flujo de trabajo se ejecutará cuando alguien suba una etiqueta que inicie con `v1.`.
|
||||
|
||||
@@ -1013,7 +1013,7 @@ on:
|
||||
|
||||
Ejecuta tu flujo de trabajo cuando ocurre actividad relacionada con el {% data variables.product.prodname_registry %} en tu repositorio. Para obtener más información, consulta la "[Documentación del {% data variables.product.prodname_registry %}](/packages)".
|
||||
|
||||
For example, you can run a workflow when a new package version has been `published`.
|
||||
Por ejemplo, puedes ejecutar un flujo de trabajo cuando una versión de paquete nueva está como `published`.
|
||||
|
||||
```yaml
|
||||
on:
|
||||
|
||||
@@ -184,7 +184,7 @@ Para obtener más información sobre los contextos, consulta la sección "[Conte
|
||||
|
||||
## Controlar aún más la forma en la que se ejecutará tu flujo de trabajo
|
||||
|
||||
Si quieres un control más granular que el que proporcionan los eventos, tipos de actividad de eventos o filtros de evento, puedes utilizar condicionales{% ifversion fpt or ghae or ghes > 3.1 or ghec %} y ambientes{% endif %} para controlar si se ejecutarán los jobs o pasos individuales en tu flujo de trabajo.
|
||||
If you want more granular control than events, event activity types, or event filters provide, you can use conditionals and environments to control whether individual jobs or steps in your workflow will run.
|
||||
|
||||
### Utilziar condicionales
|
||||
|
||||
@@ -237,8 +237,6 @@ jobs:
|
||||
|
||||
Para obtener más información sobre qué tipo de información está disponible ene l contexto del evento, consulta la sección "[Utilizar la información de los eventos](#using-event-information)". Para obtener más información sobre cómo utilizar las condicionales, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
|
||||
### Utilizar ambientes para activar jobs de flujos de trabajo manualmente
|
||||
|
||||
Si quieres activar manualmente un job específico en un flujo de trabajo, puedes utilizar un ambiente que requiera aprobación de un equipo o usuario específico. Primero, configura un ambiente con revisores requeridos. Para obtener más información, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/targeting-different-environments/using-environments-for-deployment)". Luego, referencia el nombre del ambiente en un job de tu flujo de trabajo utilizando la clave `environment:`. No se ejecutará ningún job que referencie el ambiente hasta que por lo menos un revisor lo apruebe.
|
||||
@@ -272,7 +270,6 @@ jobs:
|
||||
{% data reusables.gated-features.environments %}
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
## Eventos disponibles
|
||||
|
||||
|
||||
@@ -174,13 +174,10 @@ A boolean specifying whether the secret must be supplied.
|
||||
|
||||
{% data reusables.actions.workflow-dispatch-inputs %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
## `permissions`
|
||||
|
||||
{% data reusables.actions.jobs.section-assigning-permissions-to-jobs %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## `env`
|
||||
|
||||
A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
|
||||
@@ -204,12 +201,10 @@ env:
|
||||
|
||||
{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-run %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
## `concurrency`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-concurrency %}
|
||||
|
||||
{% endif %}
|
||||
## `jobs`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-jobs-in-a-workflow %}
|
||||
@@ -222,13 +217,10 @@ env:
|
||||
|
||||
{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-name %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
### `jobs.<job_id>.permissions`
|
||||
|
||||
{% data reusables.actions.jobs.section-assigning-permissions-to-jobs-specific %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## `jobs.<job_id>.needs`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-needs %}
|
||||
@@ -245,12 +237,10 @@ env:
|
||||
|
||||
{% data reusables.actions.jobs.section-using-environments-for-jobs %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
## `jobs.<job_id>.concurrency`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-concurrency-jobs %}
|
||||
|
||||
{% endif %}
|
||||
## `jobs.<job_id>.outputs`
|
||||
|
||||
{% data reusables.actions.jobs.section-defining-outputs-for-jobs %}
|
||||
@@ -630,8 +620,8 @@ For information about the software included on GitHub-hosted runners, see "[Spec
|
||||
For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts.
|
||||
|
||||
- `bash`/`sh`:
|
||||
- Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms.
|
||||
- You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`.
|
||||
- Fail-fast behavior using `set -eo pipefail`: This option is set when `shell: bash` is explicitly specified. It is not applied by default.
|
||||
- You can take full control over shell parameters by providing a template string to the shell options. For example, `bash {0}`.
|
||||
- sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code.
|
||||
|
||||
- `powershell`/`pwsh`
|
||||
|
||||
@@ -57,7 +57,7 @@ El conjunto de instrucciones de las SSSE3 se requiere porque el {% data variable
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.advanced-security-tab %}
|
||||
1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %} Seguridad{% endif %}", has clic en **{% data variables.product.prodname_secret_scanning_caps %}**. 
|
||||
1. Under "Security," click **{% data variables.product.prodname_secret_scanning_caps %}**. 
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
## Inhabilitar las {% data variables.product.prodname_secret_scanning %}
|
||||
@@ -67,5 +67,5 @@ El conjunto de instrucciones de las SSSE3 se requiere porque el {% data variable
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.advanced-security-tab %}
|
||||
1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Seguridad{% endif %}", deselecciona **{% data variables.product.prodname_secret_scanning_caps %}**. 
|
||||
1. Under "Security," unselect **{% data variables.product.prodname_secret_scanning_caps %}**. 
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -272,7 +272,7 @@ GitHub te permite evitar utilizar software de terceros que contenga vulnerabilid
|
||||
| Herramienta de administración de dependencias | Descripción |
|
||||
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| Alertas del dependabot | Puedes rastrear las dependencias de tus repositorios y recibir alertas del Dependabot cuando tu empresa detecte dependencias inseguras. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)". |
|
||||
| Gráfica de dependencias | La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Te muestra los ecosistemas y paquetes de los cuales depende tu base de código (sus dependencias) y los repositorios y paquetes que dependen de tu proyecto (sus dependencias). Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)". |{% ifversion ghes > 3.1 or ghec %}
|
||||
| Gráfica de dependencias | La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Te muestra los ecosistemas y paquetes de los cuales depende tu base de código (sus dependencias) y los repositorios y paquetes que dependen de tu proyecto (sus dependencias). Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)". |{% ifversion ghes or ghec %}
|
||||
| Revisión de dependencias | Si una solicitud de cambios contiene cambios a las dependencias, puedes ver un resumen de lo que ha cambiado y si es que existen vulnerabilidades conocidas en cualquiera de estas dependencias. Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" o "[Revisar los cambios de dependencias en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)". |{% endif %} {% ifversion ghec or ghes > 3.2 %}
|
||||
| Actualziaciones de seguridad del dependabot | El dependabot puede corregir las dependencias vulnerables levantando solicitudes de cambios con actualizaciones de seguridad. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de seguridad del dependabot](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)". |
|
||||
| Actualizaciones de versión del dependabot | El dependabot puede utilizarse para mantener actualizados los paquetes que utilizas a su versión más reciente. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". | {% endif %}
|
||||
|
||||
@@ -57,8 +57,8 @@ Para obtener orientación sobre cómo hacer un despliegue en fases de GitHub Adv
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %}
|
||||
1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Seguridad{% endif %}", selecciona las características que quieras habilitar y deselecciona cualquier característica que quieras inhabilitar.
|
||||
{% ifversion ghes > 3.1 %}{% else %}{% endif %}{% else %}
|
||||
1. Under "Security," select the features that you want to enable and deselect any features you want to disable.
|
||||
{% ifversion ghes %}{% else %}{% endif %}{% else %}
|
||||
1. Debajo de "{% data variables.product.prodname_advanced_security %}", da clic en **{% data variables.product.prodname_code_scanning_capc %}**. {% endif %}
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -82,8 +82,8 @@ Por ejemplo, puedes habilitar cualquier característica de {% data variables.pro
|
||||
```shell
|
||||
ghe-config app.secret-scanning.enabled true
|
||||
```
|
||||
- Para habilitar la gráfica de dependencias, {% ifversion ghes > 3.1 %}ingresa el siguiente comando{% else %}ingresa los siguientes comandos{% endif %}.
|
||||
{% ifversion ghes > 3.1 %}```shell
|
||||
- Para habilitar la gráfica de dependencias, {% ifversion ghes %}ingresa el siguiente comando{% else %}ingresa los siguientes comandos{% endif %}.
|
||||
{% ifversion ghes %}```shell
|
||||
ghe-config app.dependency-graph.enabled true
|
||||
```
|
||||
{% else %}```shell
|
||||
@@ -101,8 +101,8 @@ Por ejemplo, puedes habilitar cualquier característica de {% data variables.pro
|
||||
```shell
|
||||
ghe-config app.secret-scanning.enabled false
|
||||
```
|
||||
- Para inhabilitar la gráfica de dependencias, {% ifversion ghes > 3.1 %}ingresa el siguiente comando{% else %}ingresa los siguientes comandos{% endif %}.
|
||||
{% ifversion ghes > 3.1 %}```shell
|
||||
- Para inhabilitar la gráfica de dependencias, {% ifversion ghes %}ingresa el siguiente comando{% else %}ingresa los siguientes comandos{% endif %}.
|
||||
{% ifversion ghes %}```shell
|
||||
ghe-config app.dependency-graph.enabled false
|
||||
```
|
||||
{% else %}```shell
|
||||
|
||||
@@ -18,7 +18,7 @@ topics:
|
||||
|
||||
Después de que habilitas la gráfica de dependencias para tu empresa, puedes habilitar el {% data variables.product.prodname_dependabot %} para que detecte dependencias inseguras en tu repositorio{% ifversion ghes > 3.2 %} y corrija las vulnerabilidades automáticamente{% endif %}. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
|
||||
|
||||
{% ifversion ghes > 3.1 %}
|
||||
{% ifversion ghes %}
|
||||
Puedes habilitar la gráfica de dependencias a través de la {% data variables.enterprise.management_console %} o del shell administrativo. Te recomendamos utilizar la {% data variables.enterprise.management_console %} a menos de que {% data variables.product.product_location %} utilice clústering.
|
||||
|
||||
## Habilitar la gráfica de dependencias a través de la {% data variables.enterprise.management_console %}
|
||||
@@ -35,12 +35,10 @@ Si tu {% data variables.product.product_location %} utiliza clústering, no pued
|
||||
|
||||
## Habilitar la gráfica de dependencias a través del shell administrativo
|
||||
|
||||
{% endif %}{% ifversion ghes < 3.2 %}
|
||||
## Habilitar la gráfica de dependencias
|
||||
{% endif %}
|
||||
{% data reusables.enterprise_site_admin_settings.sign-in %}
|
||||
1. En el shell administrativo, habilita la gráfica de dependencias en {% data variables.product.product_location %}:
|
||||
{% ifversion ghes > 3.1 %}```shell
|
||||
{% ifversion ghes %}```shell
|
||||
ghe-config app.dependency-graph.enabled true
|
||||
```
|
||||
{% else %}```shell
|
||||
|
||||
@@ -36,7 +36,7 @@ Tu certificado también deberá tener configurados Nombres alternativos de sujet
|
||||
|
||||
Puedes generar una solicitud de firma de certificados (CSR) para tu instancia usando el comando `ghe-ssl-generate-csr`. Para obtener más información, consulta "[utilidades de línea de comandos](/enterprise/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)"
|
||||
|
||||
Your key must be an RSA key and must not have a passphrase. Para obtener más información, consulta "[Eliminar la contraseña de tu archivo clave](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
|
||||
Tu llave debe ser RSA y no debe tener una frase de acceso. Para obtener más información, consulta "[Eliminar la contraseña de tu archivo clave](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
|
||||
|
||||
## Cargar un certificado TLS personalizado
|
||||
|
||||
|
||||
@@ -48,7 +48,7 @@ $ ghe-announce -u
|
||||
You can also set an announcement banner using the enterprise settings on {% data variables.product.product_name %}. For more information, see "[Customizing user messages on your instance](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes > 3.1 %}
|
||||
{% ifversion ghes %}
|
||||
<!--For earlier releases of GHES, see the previous service `ghe-resque-info`-->
|
||||
|
||||
### ghe-aqueduct
|
||||
@@ -288,33 +288,6 @@ Use this command to immediately unlock the {% data variables.enterprise.manageme
|
||||
$ ghe-reactivate-admin-login
|
||||
```
|
||||
|
||||
{% ifversion ghes < 3.2 %}
|
||||
<!--For more recent releases of GHES, see the replacement service `ghe-aqueduct`-->
|
||||
|
||||
### ghe-resque-info
|
||||
|
||||
This utility displays information on background jobs, both active and in the queue. It provides the same job count numbers as the admin stats bar at the top of every page.
|
||||
|
||||
This utility can help identify whether the Resque server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Resque:
|
||||
|
||||
* The number of background jobs is increasing, while the active jobs remain the same.
|
||||
* The event feeds are not updating.
|
||||
* Webhooks are not being triggered.
|
||||
* The web interface is not updating after a Git push.
|
||||
|
||||
If you suspect Resque is failing, contact {% data variables.contact.contact_ent_support %} for help.
|
||||
|
||||
With this command, you can also pause or resume jobs in the queue.
|
||||
|
||||
```shell
|
||||
$ ghe-resque-info
|
||||
# lists queues and the number of currently queued jobs
|
||||
$ ghe-resque-info -p <em>QUEUE</em>
|
||||
# pauses the specified queue
|
||||
$ ghe-resque-info -r <em>QUEUE</em>
|
||||
# resumes the specified queue
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
### ghe-saml-mapping-csv
|
||||
|
||||
|
||||
@@ -40,7 +40,7 @@ Setting secondary rate limits protects the overall level of service on {% data v
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% ifversion ghes > 3.1 %}
|
||||
{% ifversion ghes %}
|
||||
2. Under "Rate Limiting", select **Enable Secondary Rate Limiting**.
|
||||
|
||||
{% else %}
|
||||
@@ -101,4 +101,4 @@ By default, the rate limit for {% data variables.product.prodname_actions %} is
|
||||
```
|
||||
1. Wait for the configuration run to complete.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Configurar la política de referente para tu empresa
|
||||
shortTitle: Configurar la política de referente
|
||||
intro: 'Puedes incrementar la privacidad de {% data variables.product.product_location %} si configuras la política para las solicitudes de origen cruzado.'
|
||||
versions:
|
||||
ghes: '>=3.2'
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
|
||||
@@ -16,7 +16,7 @@ permissions: 'Site administrators can configure web commit signing for {% data v
|
||||
|
||||
## About web commit signing
|
||||
|
||||
If you enable web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits users make on the web interface of {% data variables.product.product_location %}. Commits signed by {% data variables.product.product_name %} will have a verified status. Para obtener más información, consulta "[Acerca de la verificación de firmas en las confirmaciones](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
|
||||
If you enable web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits users make on the web interface of {% data variables.product.product_location %}. Las confirmaciones que firme {% data variables.product.product_name %} tendrán un estado de verificado. Para obtener más información, consulta "[Acerca de la verificación de firmas en las confirmaciones](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
|
||||
|
||||
You can enable web commit signing, rotate the private key used for web commit signing, and disable web commit signing.
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ shortTitle: Administrar GitHub Móvil
|
||||
|
||||
Puedes permitir o dejar de permitir que las personas utilicen {% data variables.product.prodname_mobile %} para autenticarse en {% data variables.product.product_location %} y que accedan a los datos de tu instancia. Predeterminadamente, {% data variables.product.prodname_mobile %} está {% ifversion ghes > 3.3 %} habilitado para las personas que utilizan {% data variables.product.product_location %}.{% else %} inhabilitado para las personas que utilizan {% data variables.product.product_location %}. Para permitir la conexión a tu instancia con {% data variables.product.prodname_mobile %}, debes habilitar la característica para esta.{% endif %}
|
||||
|
||||
{% ifversion ghes < 3.6 and ghes > 3.1 %}
|
||||
{% ifversion ghes < 3.6 %}
|
||||
{% note %}
|
||||
|
||||
**Nota:** Si mejoras a {% data variables.product.prodname_ghe_server %} 3.4.0 o posterior y no has inhabilitado o habilitado {% data variables.product.prodname_mobile %} previamente, {% data variables.product.prodname_mobile %} se habilitará predeterminadamente. Si previamente inhabilitaste o habilitaste {% data variables.product.prodname_mobile %} para tu instancia, tu preferencia se preservará cuando lo mejores. Para obtener más información sobre cómo mejorar tu instancia, consulta la sección "[Mejorar {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".
|
||||
|
||||
@@ -5,7 +5,7 @@ intro: 'Puedes verificar tu propiedad de dominios con {% data variables.product.
|
||||
product: '{% data reusables.gated-features.verify-and-approve-domain %}'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.2'
|
||||
ghes: '*'
|
||||
permissions: Enterprise owners can verify or approve a domain for an enterprise account.
|
||||
type: how_to
|
||||
topics:
|
||||
|
||||
@@ -44,7 +44,7 @@ El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para
|
||||
$ ghe-repl-status -vv
|
||||
```
|
||||
|
||||
4. En el aplicativo de réplica, para detener la replicación y promover dicho aplicativo a estado primario, utiliza el comando `ghe-repl-promote`. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible.
|
||||
4. En el aplicativo de réplica, para detener la replicación y promover dicho aplicativo a estado primario, utiliza el comando `ghe-repl-promote`. This will also automatically put the primary node in maintenance mode if it’s reachable.
|
||||
```shell
|
||||
$ ghe-repl-promote
|
||||
```
|
||||
|
||||
@@ -65,8 +65,8 @@ A medida que se suman usuarios {% data variables.product.product_location %}, es
|
||||
{% endwarning %}
|
||||
|
||||
1. Conecta un nuevo disco a tu aparato {% data variables.product.prodname_ghe_server %}.
|
||||
1. Run the `lsblk` command to identify the new disk's device name.
|
||||
1. Run the `parted` command to format the disk, substituting your device name for `/dev/xvdg`:
|
||||
1. Ejecuta el comando `lsblk` para identificar el nombre de dispositivo del disco nuevo.
|
||||
1. Ejecuta el comando `parted` para formatear el disco, sustituyendo el nombre de tu dispositivo por `/dev/xvdg`:
|
||||
```shell
|
||||
$ sudo parted /dev/xvdg mklabel msdos
|
||||
$ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
|
||||
|
||||
@@ -49,8 +49,6 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
|
||||
```
|
||||
Utiliza el número para estimar la cantidad de espacio de disco que los registros de auditoría de MySQL necesitarán. El script también controla tu espacio libre en disco mientras la importación está en progreso. Controlar este número es especialmente útil si tu espacio libre en disco está cerca de la cantidad de espacio en disco necesaria para la migración.
|
||||
|
||||
{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
|
||||
|
||||
## Pasos siguientes
|
||||
|
||||
Después de revisar estas recomendaciones y requisitos, puedes actualizar el {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)."
|
||||
|
||||
@@ -38,8 +38,6 @@ shortTitle: Upgrading GHES
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
|
||||
|
||||
## Taking a snapshot
|
||||
|
||||
A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. We only recommend taking a VM snapshot when the appliance is powered down or in maintenance mode and all background jobs have finished.
|
||||
|
||||
@@ -34,16 +34,7 @@ Este artículo explica cómo los administradores de sitio pueden habilitar {% da
|
||||
|
||||
## Revisar los requisitos de hardware
|
||||
|
||||
|
||||
{%- ifversion ghes < 3.2 %}
|
||||
|
||||
Los recursos de CPU y de memoria que están disponibles para {% data variables.product.product_location %} determinan el rendimiento máximo de jobs para {% data variables.product.prodname_actions %}. {% data reusables.actions.minimum-hardware %}
|
||||
|
||||
Las pruebas internas de {% data variables.product.company_short %} demostraron el siguiente rendimiento máximo para las instancias de {% data variables.product.prodname_ghe_server %} con un rango de CPU y configuraciones de memoria. Puede que vas rendimientos diferentes dependiendo de los niveles generales de actividad en tu instancia.
|
||||
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion ghes > 3.1 %}
|
||||
{%- ifversion ghes %}
|
||||
|
||||
Los recursos de memoria y CPU que {% data variables.product.product_location %} tiene disponibles determinan la cantidad de jobs que se pueden ejecutar simultáneamente sin pérdida de rendimiento. {% data reusables.actions.minimum-hardware %}
|
||||
|
||||
@@ -51,11 +42,6 @@ La cantidad máxima de ejecución simultánea de jobs sin pérdida de rendimient
|
||||
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion ghes < 3.2 %}
|
||||
|
||||
{% data reusables.actions.hardware-requirements-before %}
|
||||
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion ghes = 3.2 %}
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ Puedes poblar el caché de la herramienta del ejecutor si ejecutas un flujo de t
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Solo puedes utilizar un caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %} para un ejecutor auto-hospedado que tenga un sistema operativo y arquitectura idénticos. Por ejemplo, si estás utilizando un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con `ubuntu-18.04` para generar un caché de la herramienta, tu ejecutor auto-hospedado también debe ser una máquina con Ubuntu 18.04 de 64 bits. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for GitHub-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)."
|
||||
**Nota:** Solo puedes utilizar un caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %} para un ejecutor auto-hospedado que tenga un sistema operativo y arquitectura idénticos. Por ejemplo, si estás utilizando un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con `ubuntu-18.04` para generar un caché de la herramienta, tu ejecutor auto-hospedado también debe ser una máquina con Ubuntu 18.04 de 64 bits. Para obtener más información sobre los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en GitHub](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -13,8 +13,8 @@ learningTracks:
|
||||
- '{% ifversion ghae %}get_started_with_github_ae{% endif %}'
|
||||
- '{% ifversion ghes %}deploy_an_instance{% endif %}'
|
||||
- '{% ifversion ghes %}upgrade_your_instance{% endif %}'
|
||||
- adopting_github_actions_for_your_enterprise_ghec
|
||||
- adopting_github_actions_for_your_enterprise_ghes_and_ghae
|
||||
- adopting_github_actions_for_your_enterprise_ghec
|
||||
- adopting_github_actions_for_your_enterprise_ghes_and_ghae
|
||||
- '{% ifversion ghes %}increase_fault_tolerance{% endif %}'
|
||||
- '{% ifversion ghes %}improve_security_of_your_instance{% endif %}'
|
||||
- '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}'
|
||||
@@ -126,7 +126,6 @@ includeGuides:
|
||||
- /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding
|
||||
- /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks
|
||||
- /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
|
||||
- /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise
|
||||
- /admin/user-management/managing-projects-using-jira
|
||||
- /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
|
||||
- /admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
|
||||
|
||||
@@ -30,6 +30,7 @@ children:
|
||||
- /username-considerations-for-external-authentication
|
||||
- /changing-authentication-methods
|
||||
- /allowing-built-in-authentication-for-users-outside-your-provider
|
||||
- /troubleshooting-identity-and-access-management-for-your-enterprise
|
||||
shortTitle: Administrar IAM para tu empresa
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: Troubleshooting identity and access management for your enterprise
|
||||
shortTitle: Troubleshoot IAM
|
||||
intro: Review common issues and solutions for identity and access management for your enterprise.
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Accounts
|
||||
- Authentication
|
||||
- Enterprise
|
||||
- Identity
|
||||
- Security
|
||||
- SSO
|
||||
- Troubleshooting
|
||||
---
|
||||
|
||||
## Username conflicts
|
||||
|
||||
{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} normalizes an identifier provided by your identity provider (IdP) to create each person's username on {% data variables.product.prodname_dotcom %}. If multiple accounts are normalized into the same {% data variables.product.prodname_dotcom %} username, a username conflict occurs, and only the first user account is created. Para obtener más información, consulta la sección "[Consideraciones de nombre de usuario para la autenticación externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)".
|
||||
|
||||
{% ifversion ghec %}
|
||||
## Errors when switching authentication configurations
|
||||
|
||||
If you're experiencing problems while switching between different authentication configurations, such as changing your SAML SSO configuration from an organization to an enterprise account or migrating from SAML to OIDC for {% data variables.product.prodname_emus %}, ensure you're following our best practices for the change.
|
||||
|
||||
- "[Switching your SAML configuration from an organization to an enterprise account](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)"
|
||||
- "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)"
|
||||
|
||||
## Accessing your enterprise when SSO is not available
|
||||
|
||||
When a configuration error or an issue with your identity provider IdP prevents you from using SSO, you can use a recovery code to access your enterprise. Para obtener más información, consulta la sección "[Acceder a tu cuenta empresarial si tu proveedor de identidad no está disponible](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)".
|
||||
{% endif %}
|
||||
|
||||
## SAML authentication errors
|
||||
|
||||
If users are experiencing errors when attempting to authenticate with SAML, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
## Leer más
|
||||
|
||||
- "[Troubleshooting identity and access management for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization)"
|
||||
{% endif %}
|
||||
@@ -23,7 +23,7 @@ shortTitle: Configure built-in authentication
|
||||
|
||||
By default, {% data variables.product.product_name %} uses built-in authentication. Each person creates a user account on {% data variables.product.product_location %} from an invitation or by signing up, and then authenticates with the credentials for the account to access your instance. Your {% data variables.product.product_name %} instance stores the authentication information for the account.
|
||||
|
||||
You can prevent unauthenticated people from creating new user accounts on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)."
|
||||
You can prevent unauthenticated people from creating new user accounts on your instance. Para obtener más información, consulta la sección "[Inhabilitar los inicios de sesión no autenticados](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)".
|
||||
|
||||
{% data reusables.enterprise_user_management.alternatively-enable-external-authentication %}
|
||||
|
||||
|
||||
@@ -127,7 +127,7 @@ Los {% data variables.product.prodname_managed_users_caps %} se deben autenticar
|
||||
|
||||
## Nombres de usuario e información de perfil
|
||||
|
||||
{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
|
||||
{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. Para obtener más información, consulta la sección "[Consideraciones de nombre de usuario para la autenticación externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)".
|
||||
|
||||
A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)."
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Using LDAP for enterprise IAM
|
||||
shortTitle: LDAP for enterprise IAM
|
||||
intro: You can centrally manage accounts and access to {% data variables.product.product_location %} by integrating with your existing LDAP directory.
|
||||
intro: 'You can centrally manage accounts and access to {% data variables.product.product_location %} by integrating with your existing LDAP directory.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
children:
|
||||
|
||||
@@ -51,9 +51,3 @@ Como alternativa, también puedes configurar el SSO de SAML utilizando Okta para
|
||||
1. Haz clic en **Save ** (guardar).
|
||||
{% data reusables.saml.okta-view-setup-instructions %}
|
||||
1. Habilita SAML para tu cuenta empresarial utilizando la información en las instrucciones de configuración. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
|
||||
|
||||
## Crear grupos en Okta
|
||||
|
||||
1. En Okta, crea un grupo para que empate con la organización que pertenezca a tu cuenta empresarial. El nombre de cada grupo debe coincidir con el nombre de cuenta de la organización (no así, con el nombre mostrado de la misma). Por ejemplo, si la URL de la organización es `https://github.com/octo-org`, nombra `octo-org` al grupo.
|
||||
1. Asigna la aplicación que creaste para tu cuenta empresarial a cada grupo. {% data variables.product.prodname_dotcom %} recibirá todos los datos de los `groups` para cada usuario.
|
||||
1. Agrega usuarios a los grupos basándote en las organizaciones a las cuales quisieras que pertenezcan dichos usuarios.
|
||||
|
||||
@@ -33,7 +33,7 @@ To enable encrypted assertions, you must provide {% data variables.product.produ
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Opcionalmente, habilita la depuración de SAML. La depuración de SAML registra las entradas verbosas en la bitácora de autenticación de {% data variables.product.product_name %} y podría ayudarte a solucionar problemas de los intentos de autenticación fallidos. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)."
|
||||
1. Opcionalmente, habilita la depuración de SAML. La depuración de SAML registra las entradas verbosas en la bitácora de autenticación de {% data variables.product.product_name %} y podría ayudarte a solucionar problemas de los intentos de autenticación fallidos. Para obtener más información, consulta la sección "[Solucionar problemas de la autenticación de SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)".
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.authentication %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Managing team synchronization for organizations in your enterprise
|
||||
intro: 'Puedes habilitar la sincronización de equipos entre un proveedor de identidad (IdP) y {% data variables.product.product_name %} para permitir que las organizaciones que pertenezcan a tu cuenta empresarial administren la membrecía de equipo a través de grupos de IdP.'
|
||||
intro: 'You can enable team synchronization between Azure AD and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.'
|
||||
permissions: Enterprise owners can manage team synchronization for an enterprise account.
|
||||
versions:
|
||||
ghec: '*'
|
||||
@@ -22,7 +22,7 @@ shortTitle: Administrar la sincronización de equipos
|
||||
|
||||
## Acerca de la sincronización de equipos para las cuentas empresariales
|
||||
|
||||
Si utilizas Azure AD como tu IdP, puedes habilitar la sincronización de equipos para tu cuenta empresarial para permitir que los propietarios de la organización y mantenedores de equipo sincronicen equipos en las organizaciones que pertenezcan a tus cuentas empresariales con grupos de IdP.
|
||||
If you use SAML at the enterprise level with Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups.
|
||||
|
||||
{% data reusables.identity-and-permissions.about-team-sync %}
|
||||
|
||||
|
||||
@@ -132,6 +132,10 @@ Para prevenir que una persona se autentique con tu IdP y se mantenga autorizad p
|
||||
|
||||
To customize the session duration, you may be able to define the value of the `SessionNotOnOrAfter` attribute on your IdP. If you define a value less than 24 hours, {% data variables.product.product_name %} may prompt people to authenticate every time {% data variables.product.product_name %} initiates a redirect.
|
||||
|
||||
{% ifversion ghec %}
|
||||
To prevent authentication errors, we recommend a minimum session duration of 4 hours. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#users-are-repeatedly-redirected-to-authenticate)."
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notas**:
|
||||
|
||||
@@ -4,6 +4,7 @@ shortTitle: Troubleshoot SAML SSO
|
||||
intro: 'If you use SAML single sign-on (SSO) and people are unable to authenticate to access {% data variables.product.product_location %}, you can troubleshoot the problem.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Accounts
|
||||
@@ -15,6 +16,7 @@ topics:
|
||||
- Troubleshooting
|
||||
---
|
||||
|
||||
{% ifversion ghes %}
|
||||
## About problems with SAML authentication
|
||||
|
||||
{% data variables.product.product_name %} logs error messages for failed SAML authentication in the authentication log at _/var/log/github/auth.log_. You can review responses in this log file, and you can also configure more verbose logging.
|
||||
@@ -100,3 +102,10 @@ La audiencia es no válida. Audience attribute does not match https://<em>YOUR-I
|
||||
```
|
||||
|
||||
Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {% data variables.product.product_location %}, which is the full URL to your instance. Por ejemplo, `https://ghe.corp.example.com`.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.saml.current-time-earlier-than-notbefore-condition %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
{% data reusables.saml.authentication-loop %}
|
||||
{% endif %}
|
||||
|
||||
@@ -15,7 +15,7 @@ topics:
|
||||
|
||||
## About updates to users' SAML `NameID`
|
||||
|
||||
In some situations, you may need to update values associated with a person's account on your SAML IdP. If that identifier is also the `NameID` that you use for authentication on {% data variables.product.product_name %}, you must update the `NameID` mapping on your instance so the person can continue to authenticate successfully. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
|
||||
In some situations, you may need to update values associated with a person's account on your SAML IdP. If that identifier is also the `NameID` that you use for authentication on {% data variables.product.product_name %}, you must update the `NameID` mapping on your instance so the person can continue to authenticate successfully. Para obtener más información, consulta la sección "[Consideraciones de nombre de usuario para la autenticación externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)".
|
||||
|
||||
## Actualizar la `NameID` de SAML de un usuario
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ Para aprender más sobre el {% data variables.product.prodname_github_connect %}
|
||||
|
||||
2. Next to your desired enterprise account, click **Settings**. 
|
||||
|
||||
3. On the left, click **GitHub Connect**. 
|
||||
3. A la izquierda, haz clic en **GitHub Connect**. 
|
||||
|
||||
{% data reusables.server-statistics.csv-download %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Analyzing how your team works with Server Statistics
|
||||
shortTitle: Server Statistics
|
||||
shortTitle: Estadísticas del servidor
|
||||
intro: 'Para analizar la forma en la que trabaja tu equipo, entender el valor que obtienes de {% data variables.product.prodname_ghe_server %} y ayudarnos a mejorar nuestros productos, puedes utilizar las {% data variables.product.prodname_server_statistics %} para revisar tus datos de uso para {% data variables.product.prodname_ghe_server %} y compartir estos datos agregados con {% data variables.product.company_short %}.'
|
||||
versions:
|
||||
feature: server-statistics
|
||||
|
||||
@@ -10,7 +10,7 @@ redirect_from:
|
||||
|
||||
{% data reusables.server-statistics.release-phase %}
|
||||
|
||||
You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)."
|
||||
You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. Estos datos, los cuales incluyen métricas agregadas en los repositorios, propuestas y solicitudes de cambio pueden ayudarte a anticipar las necesidades de tu organización, entender cómo funciona tu equipo y mostrarte el valor que obtienes de {% data variables.product.prodname_ghe_server %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)."
|
||||
|
||||
Before you can use the {% data variables.product.prodname_server_statistics %} REST API, you must enable {% data variables.product.prodname_server_statistics %}. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_server_statistics %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)".
|
||||
|
||||
|
||||
@@ -31,7 +31,6 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.product.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)."
|
||||
{% endif %}
|
||||
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
## Acciones de la categoría `account`
|
||||
|
||||
@@ -92,7 +91,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
{%- ifversion ghec %}
|
||||
| `business.add_support_entitlee` | A support entitlement was added to a member of an enterprise. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)".
|
||||
{%- endif %}
|
||||
{%- ifversion ghes > 3.0 or ghae %}
|
||||
{%- ifversion ghes or ghae %}
|
||||
| `business.advanced_security_policy_update` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} created, updated, or removed a policy for {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".
|
||||
{%- endif %}
|
||||
{%- ifversion ghec %}
|
||||
@@ -114,7 +113,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `business.enterprise_server_license_download` | A {% data variables.product.prodname_ghe_server %} license was downloaded. | `business.import_license_usage` | License usage information was imported from a {% data variables.product.prodname_ghe_server %} instance to an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. | `business.invite_admin` | An invitation for someone to be an enterprise owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was sent. | `business.invite_billing_manager` | An invitation for someone to be an billing manager of an enterprise was sent.
|
||||
{%- endif %}
|
||||
| `business.members_can_update_protected_branches.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unset a policy for whether members of an enterprise can update protected branches on repositories for individual organizations. Los administradores de las organizaciones pudieron elegir si se permitía la actualización de los ajustes de ramas protegidas o no. | `business.members_can_update_protected_branches.disable` | The ability for enterprise members to update branch protection rules was disabled. Solo los propietarios de las empresas pueden actualizar las ramas protegidas. | `business.members_can_update_protected_branches.enable` | The ability for enterprise members to update branch protection rules was enabled. Enterprise owners and members can update protected branches. | `business.remove_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was removed from an enterprise.
|
||||
{%- ifversion ghes > 3.1 %}
|
||||
{%- ifversion ghes %}
|
||||
| `business.referrer_override_enable` | An enterprise owner or site administrator enabled the referrer policy override. Para obtener más información, consulta la sección "[Configurar la política del referente para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)". | `business.referrer_override_disable` | An enterprise owner or site administrator disabled the referrer policy override. Para obtener más información, consulta la sección "[Configurar la política del referente para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".
|
||||
{%- endif %}
|
||||
{%- ifversion ghec %}
|
||||
@@ -236,7 +235,6 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. |
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec or ghes or ghae %}
|
||||
## Acciones de la categoría `dependency_graph`
|
||||
|
||||
| Acción | Descripción |
|
||||
@@ -250,7 +248,6 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `dependency_graph_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the dependency graph for all new repositories. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". |
|
||||
| `dependency_graph_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the dependency graph for all new repositories. |
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
## `discussion` category actions
|
||||
@@ -313,7 +310,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
{%- ifversion ghec %}
|
||||
| `enterprise.runner_group_visiblity_updated` | The visibility of a {% data variables.product.prodname_actions %} self-hosted runner group was updated via the REST API. Para obtener más información, consulta la sección "[Actualizar un grupo de ejecutores auto-hospedados para una organización](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)".
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes > 3.1 or ghae %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `enterprise.self_hosted_runner_online` | The {% data variables.product.prodname_actions %} runner application was started. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `enterprise.self_hosted_runner_offline` | The {% data variables.product.prodname_actions %} runner application was stopped. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes %}
|
||||
@@ -584,17 +581,21 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
|
||||
## acciones de la categoría `org`
|
||||
|
||||
| Acción | Descripción |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
|
||||
| `org.accept_business_invitation` | An invitation sent to an organization to join an enterprise was accepted. |
|
||||
| {% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %} | |
|
||||
| `org.add_billing_manager` | A billing manager was added to an organization. |
|
||||
| {% ifversion fpt or ghec %}For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."{% endif %} | |
|
||||
| `org.add_member` | A user joined an organization. |
|
||||
{%- ifversion ghes > 3.0 or ghae or ghec %}
|
||||
| `org.advanced_security_disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in an organization. | `org.advanced_security_disabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for all repositories in an organization. | `org.advanced_security_enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in an organization. | `org.advanced_security_enabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for all repositories in an organization. | `org.advanced_security_policy_selected_member_disabled` | An enterprise owner prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_selected_member_enabled` | An enterprise owner allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_update` | An organization owner updated polices for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
|
||||
{%- endif %}
|
||||
| `org.async_delete` | A user initiated a background job to delete an organization.
|
||||
| Acción | Descripción |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `org.accept_business_invitation` | An invitation sent to an organization to join an enterprise was accepted. |
|
||||
| {% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %} | |
|
||||
| `org.add_billing_manager` | A billing manager was added to an organization. |
|
||||
| {% ifversion fpt or ghec %}For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."{% endif %} | |
|
||||
| `org.add_member` | A user joined an organization. |
|
||||
| `org.advanced_security_disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in an organization. |
|
||||
| `org.advanced_security_disabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for all repositories in an organization. |
|
||||
| `org.advanced_security_enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in an organization. |
|
||||
| `org.advanced_security_enabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for all repositories in an organization. |
|
||||
| `org.advanced_security_policy_selected_member_disabled` | An enterprise owner prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
|
||||
| `org.advanced_security_policy_selected_member_enabled` | An enterprise owner allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
|
||||
| `org.advanced_security_policy_update` | An organization owner updated polices for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
|
||||
| `org.async_delete` | Un usuario inició una tarea en segundo plano para eliminar una organización. |
|
||||
{%- ifversion ghec %}
|
||||
| `org.audit_log_export` | An organization owner created an export of the organization audit log. Si la exportación incluía una consulta, el registro detallará la consulta utilizada y la cantidad de entradas en el registro de auditoría que coinciden con esa consulta. For more information, see "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
@@ -645,9 +646,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
| `org.self_hosted_runner_online` | The runner application was started. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `org.self_hosted_runner_offline` | The runner application was stopped. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
| `org.self_hosted_runner_updated` | The runner application was updated. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."
|
||||
{%- endif %}
|
||||
@@ -703,7 +702,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `organization_default_label.update` | A default label for repositories in an organization was edited. For more information, see "[Editing a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#editing-a-default-label)." |
|
||||
| `organization_default_label.destroy` | A default label for repositories in an organization was deleted. For more information, see "[Deleting a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#deleting-a-default-label)." |
|
||||
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 %}
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
## `organization_domain` category actions
|
||||
|
||||
| Acción | Descripción |
|
||||
@@ -722,23 +721,21 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `organization_projects_change.enable` | Organization projects were enabled for all organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)". |
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec or ghes > 3.0 or ghae %}
|
||||
## Acciones de la categoría `packages`
|
||||
|
||||
| Acción | Descripción |
|
||||
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `packages.insecure_hash` | Maven published an insecure hash for a specific package version. |
|
||||
| `packages.package_deleted` | A package was deleted from an organization.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `packages.package_published` | A package was published or republished to an organization. |
|
||||
| `packages.package_restored` | An entire package was restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `packages.package_version_deleted` | Se borró una versión específica de un paquete.{% ifversion fpt or ghec or ghes > 3.1 %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
|
||||
| `packages.package_version_published` | A specific package version was published or republished to a package. |
|
||||
| `packages.package_version_restored` | Se borró una versión específica de un paquete.{% ifversion fpt or ghec or ghes > 3.1 %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
|
||||
| `packages.part_upload` | A specific package version was partially uploaded to an organization. |
|
||||
| `packages.upstream_package_fetched` | A specific package version was fetched from the npm upstream proxy. |
|
||||
| `packages.version_download` | A specific package version was downloaded. |
|
||||
| `packages.version_upload` | A specific package version was uploaded. |
|
||||
{%- endif %}
|
||||
| Acción | Descripción |
|
||||
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `packages.insecure_hash` | Maven published an insecure hash for a specific package version. |
|
||||
| `packages.package_deleted` | A package was deleted from an organization.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `packages.package_published` | A package was published or republished to an organization. |
|
||||
| `packages.package_restored` | An entire package was restored.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `packages.package_version_deleted` | Se borró una versión específica de un paquete.{% ifversion fpt or ghec or ghes %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
|
||||
| `packages.package_version_published` | A specific package version was published or republished to a package. |
|
||||
| `packages.package_version_restored` | Se borró una versión específica de un paquete.{% ifversion fpt or ghec or ghes %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
|
||||
| `packages.part_upload` | A specific package version was partially uploaded to an organization. |
|
||||
| `packages.upstream_package_fetched` | A specific package version was fetched from the npm upstream proxy. |
|
||||
| `packages.version_download` | A specific package version was downloaded. |
|
||||
| `packages.version_upload` | A specific package version was uploaded. |
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
## `pages_protected_domain` category actions
|
||||
@@ -809,15 +806,15 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
|
||||
| Acción | Descripción |
|
||||
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `project.access` | A project board visibility was changed. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)". |
|
||||
| `project.close` | A project board was closed. Para obtener más información, consulta "[Cerrar un tablero de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board)". |
|
||||
| `project.create` | A project board was created. Para obtener más información, consulta "[Crear un tablero de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)". |
|
||||
| `project.access` | A project board visibility was changed. For more information, see "[Changing project board visibility](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)." |
|
||||
| `project.close` | A project board was closed. For more information, see "[Closing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board)." |
|
||||
| `project.create` | A project board was created. For more information, see "[Creating a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)." |
|
||||
| `project.delete` | A project board was deleted. For more information, see "[Deleting a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board)." |
|
||||
| `project.link` | A repository was linked to a project board. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)". |
|
||||
| `project.open` | A project board was reopened. For more information, see "[Reopening a closed project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)." |
|
||||
| `project.rename` | A project board was renamed. For more information, see "[Editing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board)." |
|
||||
| `project.unlink` | A repository was unlinked from a project board. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)". |
|
||||
| `project.update_org_permission` | The project's base-level permission for all organization members was changed or removed. Para obtener más información, consulta "[Administrar el acceso a un tablero de proyecto para los miembros de una organización](/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members)." |
|
||||
| `project.update_org_permission` | The project's base-level permission for all organization members was changed or removed. For more information, see "[Managing access to a project board for organization members](/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members)." |
|
||||
| `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)." |
|
||||
| `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)." |
|
||||
|
||||
@@ -831,10 +828,10 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
|
||||
## `project_view` category actions
|
||||
|
||||
| Acción | Descripción |
|
||||
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `project_view.create` | A view was created in a project board. Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)". |
|
||||
| `project_view.delete` | A view was deleted in a project board. Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)". |
|
||||
| Acción | Descripción |
|
||||
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `project_view.create` | A view was created in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)." |
|
||||
| `project_view.delete` | A view was deleted in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)." |
|
||||
{%- endif %}
|
||||
|
||||
## acciones de la categoría `protected_branch`
|
||||
@@ -855,17 +852,16 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
|
||||
## acciones de la categoría `public_key`
|
||||
|
||||
| Acción | Descripción |
|
||||
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `public_key.create` | Una clave SSH se [agregó][add key] a una cuenta de usuario o una [llave de implementación][] se agregó a un repositorio. |
|
||||
| `public_key.delete` | Una clave SSH se eliminó de una cuenta de usuario o una [llave de implementación][] se eliminó de un repositorio. |
|
||||
| `public_key.update` | Se actualizó una llave SSH de una cuenta de usuario o una [llave de despliegue][] de un repositorio. |
|
||||
| `public_key.unverification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be unverified. |
|
||||
| `public_key.unverify` | A user account's SSH key or a repository's [deploy key][] was unverified. |
|
||||
| `public_key.verification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be verified. |
|
||||
| `public_key.verify` | A user account's SSH key or a repository's [deploy key][] was verified. |
|
||||
| Acción | Descripción |
|
||||
| ----------------------------------- | ------------------------------------------------------------------------------------------------ |
|
||||
| `public_key.create` | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository. |
|
||||
| `public_key.delete` | An SSH key was removed from a user account or a [deploy key][] was removed from a repository. |
|
||||
| `public_key.update` | A user account's SSH key or a repository's [deploy key][] was updated. |
|
||||
| `public_key.unverification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be unverified. |
|
||||
| `public_key.unverify` | A user account's SSH key or a repository's [deploy key][] was unverified. |
|
||||
| `public_key.verification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be verified. |
|
||||
| `public_key.verify` | A user account's SSH key or a repository's [deploy key][] was verified. |
|
||||
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
## Acciones de la categoría `pull_request`
|
||||
|
||||
| Acción | Descripción |
|
||||
@@ -899,7 +895,6 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `pull_request_review_comment.create` | A review comment was added to a pull request. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". |
|
||||
| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. |
|
||||
| `pull_request_review_comment.update` | A review comment on a pull request was changed. |
|
||||
{%- endif %}
|
||||
|
||||
## acciones de la categoría `repo`
|
||||
|
||||
@@ -932,11 +927,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `repo.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for a repository. Para obtener más información, consulte la sección "[Configurar la aprobación requerida para los flujos de trabajo desde las bifurcaciones públicas](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)".
|
||||
{%- endif %}
|
||||
| `repo.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in a repository was changed. Para obtener más información, consulta la sección "[Configurar el periodo de retención de los artefactos de las {% data variables.product.prodname_actions %} y las bitácoras en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
| `repo.self_hosted_runner_online` | The runner application was started. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_offline` | The runner application was stopped. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_updated` | The runner application was updated. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."
|
||||
{%- endif %}
|
||||
| `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository. | `repo.transfer` | A user accepted a request to receive a transferred repository. | `repo.transfer_outgoing` | A repository was transferred to another repository network. | `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. | `repo.unarchived` | A repository was unarchived. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository. | `repo.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. | `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed. | `repo.update_default_branch` | The default branch for a repository was changed. | `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_codespaces %} integration secret was updated for a repository. | `repo.update_member` | A user's permission to a repository was changed.
|
||||
| `repo.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in a repository was changed. Para obtener más información, consulta la sección "[Configurar el periodo de retención de los artefactos de las {% data variables.product.prodname_actions %} y las bitácoras en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)". | `repo.self_hosted_runner_online` | The runner application was started. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_offline` | The runner application was stopped. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_updated` | The runner application was updated. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository. | `repo.transfer` | A user accepted a request to receive a transferred repository. | `repo.transfer_outgoing` | A repository was transferred to another repository network. | `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. | `repo.unarchived` | A repository was unarchived. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository. | `repo.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. | `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed. | `repo.update_default_branch` | The default branch for a repository was changed. | `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_codespaces %} integration secret was updated for a repository. | `repo.update_member` | A user's permission to a repository was changed.
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
## acciones de la categoría `repository_advisory`
|
||||
@@ -1024,7 +1015,6 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. |
|
||||
| `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. |
|
||||
|
||||
{%- ifversion fpt or ghec or ghes or ghae %}
|
||||
## acciones de la categoría `repository_vulnerability_alert`
|
||||
|
||||
| Acción | Descripción |
|
||||
@@ -1032,7 +1022,6 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `repository_vulnerability_alert.create` | {% data variables.product.product_name %} created a {% data variables.product.prodname_dependabot %} alert for a repository that uses an insecure dependency. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)". |
|
||||
| `repository_vulnerability_alert.dismiss` | An organization owner or repository administrator dismissed a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. |
|
||||
| `repository_vulnerability_alert.resolve` | Someone with write access to a repository pushed changes to update and resolve a {% data variables.product.prodname_dependabot %} alert in a project dependency. |
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
## acciones de la categoría `repository_vulnerability_alerts`
|
||||
@@ -1051,7 +1040,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `required_status_check.create` | A status check was marked as required for a protected branch. Para obtener más información, consulta la sección "[Requerir verificaciones de estado antes de la fusión](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)". |
|
||||
| `required_status_check.destroy` | A status check was no longer marked as required for a protected branch. Para obtener más información, consulta la sección "[Requerir verificaciones de estado antes de la fusión](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)". |
|
||||
|
||||
{%- ifversion ghec or ghes > 3.1 %}
|
||||
{%- ifversion ghec or ghes %}
|
||||
## `restrict_notification_delivery` category actions
|
||||
|
||||
| Acción | Descripción |
|
||||
@@ -1167,11 +1156,11 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
{%- ifversion ghes %}
|
||||
| `staff.search_audit_log` | A site administrator performed a search of the site admin audit log.
|
||||
{%- endif %}
|
||||
| `staff.set_domain_token_expiration` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff set the verification code expiry time for an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
|
||||
| `staff.set_domain_token_expiration` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff set the verification code expiry time for an organization or enterprise domain. {% ifversion ghec or ghes %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
|
||||
{%- ifversion ghes %}
|
||||
| `staff.unlock` | A site administrator unlocked (temporarily gained full access to) all of a user's private repositories.
|
||||
{%- endif %}
|
||||
| `staff.unverify_domain` | |{% ifversion ghes %}A site administrator or {% endif %}GitHub staff unverified an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}| | `staff.verify_domain` | {% ifversion ghes %}Un administrador de sitio o {% endif %}el personal de GitHub verificó un dominio de empresa u organización. {% ifversion ghec or ghes > 3.1 %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
|
||||
| `staff.unverify_domain` | |{% ifversion ghes %}A site administrator or {% endif %}GitHub staff unverified an organization or enterprise domain. {% ifversion ghec or ghes %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}| | `staff.verify_domain` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff verified an organization or enterprise domain. {% ifversion ghec or ghes %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
|
||||
{%- ifversion ghes %}
|
||||
| `staff.view_audit_log` | A site administrator viewed the site admin audit log.
|
||||
{%- endif %}
|
||||
@@ -1260,11 +1249,9 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `user_license.update` | A seat license type for a user in an enterprise was changed. |
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
## Acciones de la categoría `workflows`
|
||||
|
||||
{% data reusables.audit_log.audit-log-events-workflows %}
|
||||
{%- endif %}
|
||||
|
||||
[OAuth access token]: /developers/apps/building-oauth-apps/authorizing-oauth-apps
|
||||
|
||||
@@ -1273,8 +1260,6 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
[Aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app
|
||||
|
||||
[add key]: /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
|
||||
[llave de implementación]: /developers/overview/managing-deploy-keys#deploy-keys
|
||||
[llave de despliegue]: /developers/overview/managing-deploy-keys#deploy-keys
|
||||
[deploy key]: /developers/overview/managing-deploy-keys#deploy-keys
|
||||
|
||||
[2fa]: /authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication
|
||||
|
||||
@@ -6,7 +6,7 @@ permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% e
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.0'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
@@ -22,7 +22,6 @@ Puedes interactuar con la bitácora de audotaría si utilizas la API de GraphQL{
|
||||
|
||||
Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
|
||||
|
||||
{% ifversion ghec or ghes > 3.0 or ghae %}
|
||||
## Querying the audit log GraphQL API
|
||||
|
||||
To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
|
||||
@@ -107,7 +106,6 @@ This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) inter
|
||||
|
||||
For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries).
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %}
|
||||
## Querying the audit log REST API
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating an enterprise account
|
||||
intro: "If you're currently using {% data variables.product.prodname_ghe_cloud %} with a single organization, you can create an enterprise account to centrally manage multiple organizations."
|
||||
intro: 'If you''re currently using {% data variables.product.prodname_ghe_cloud %} with a single organization, you can create an enterprise account to centrally manage multiple organizations.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
|
||||
@@ -26,7 +26,7 @@ Para prevenir que los paquetes nuevos se carguen, puedes configurar un ecosistem
|
||||
{%- ifversion ghes > 3.4 %}{% note -%}
|
||||
**Nota**: El aislamiento de subdominios debe estar habilitado para alternar las
|
||||
opciones del {% data variables.product.prodname_container_registry %}.
|
||||
{%- endnote %}{%- endif %}{%- ifversion ghes > 3.1 %}
|
||||
{%- endnote %}{%- endif %}{%- ifversion ghes %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -115,7 +115,7 @@ Si se habilita una política para una empresa, esta puede inhabilitarse selectiv
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
{% data reusables.actions.private-repository-forks-configure %}
|
||||
|
||||
{% ifversion ghec or ghes > 3.1 or ghae %}
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
|
||||
## Requerir una política para los permisos de flujo de trabajo en tu empresa
|
||||
|
||||
|
||||
@@ -71,16 +71,16 @@ Si un propietario de empresa deja de permitir que los miembros de ésta creen ci
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Requerir una política para los permisos {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminados{% endif %} del repositorio
|
||||
## Requerir una política para los permisos {% ifversion ghec or ghes or ghae %}base{% else %}predeterminados{% endif %} del repositorio
|
||||
|
||||
En todas las organizaciones que pertenezcan a tu empresa, puedes configurar un nivel de permisos {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminado{% endif %} de los repositorios (ninguno, lectura, escritura o administración) para los miembros organizacionales o permitir que los propietarios administren el ajuste a nivel de organización.
|
||||
En todas las organizaciones que pertenezcan a tu empresa, puedes configurar un nivel de permisos {% ifversion ghec or ghes or ghae %}base{% else %}predeterminado{% endif %} de los repositorios (ninguno, lectura, escritura o administración) para los miembros organizacionales o permitir que los propietarios administren el ajuste a nivel de organización.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.repositories-tab %}
|
||||
4. Debajo de "permisos {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminados{% endif %}", revisa la información sobre cómo cambiar el ajuste. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
|
||||
5. Debajo de "Permisos{% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminados{% endif %}", utiliza el menú desplegable y elige una política.
|
||||
{% ifversion ghec or ghes > 3.1 or ghae %}
|
||||
4. Debajo de "permisos {% ifversion ghec or ghes or ghae %}base{% else %}predeterminados{% endif %}", revisa la información sobre cómo cambiar el ajuste. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
|
||||
5. Debajo de "Permisos{% ifversion ghec or ghes or ghae %}base{% else %}predeterminados{% endif %}", utiliza el menú desplegable y elige una política.
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ intro: Puedes prevenir las fugas de información de tu empresa hacia cuentas de
|
||||
product: '{% data reusables.gated-features.restrict-email-domain %}'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.2'
|
||||
ghes: '*'
|
||||
permissions: Enterprise owners can restrict email notifications for an enterprise.
|
||||
type: how_to
|
||||
topics:
|
||||
|
||||
@@ -8,6 +8,7 @@ redirect_from:
|
||||
- /articles/managing-organizations-in-your-enterprise-account
|
||||
- /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
|
||||
- /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise
|
||||
intro: 'Las organizaciones son ideales para crear grupos diferentes de usuarios dentro de tu empresa, como divisiones o grupos trabajando en proyectos similares. Los repositorios {% ifversion ghae %}internos{% else %}Los repositorios públicos e internos{% endif %} que pertenecen a una organización son accesibles para los miembros de otras organizaciones en la empresa, mientras que los repositorios privados no son accesibles para nadie mas que los miembros de la organización que cuenta con este acceso.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
@@ -17,7 +18,6 @@ topics:
|
||||
- Enterprise
|
||||
children:
|
||||
- /adding-organizations-to-your-enterprise
|
||||
- /managing-unowned-organizations-in-your-enterprise
|
||||
- /configuring-visibility-for-organization-membership
|
||||
- /preventing-users-from-creating-organizations
|
||||
- /requiring-two-factor-authentication-for-an-organization
|
||||
|
||||
@@ -1,22 +0,0 @@
|
||||
---
|
||||
title: Administrar las organizaciones que no te pertenecen en tu empresa
|
||||
intro: Puedes convertirte en propietario de una organización en tu cuenta empresarial si ésta no tiene propietarios actualmente.
|
||||
permissions: Enterprise owners can manage unowned organizations in an enterprise account.
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
|
||||
- /github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account
|
||||
versions:
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Administrator
|
||||
- Enterprise
|
||||
- Organizations
|
||||
shortTitle: Administrar organizaciones que no te pertenecen
|
||||
---
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
2. A la derecha del campo de búsqueda, da clic en **X sin propietario**. 
|
||||
3. A la derecha de la organización sobre la cual quieres asumirte como propietario, da clic en **Convertirte en propietario**. 
|
||||
4. Lee la advertencia y luego da clic en **Convertirte en propietario**. 
|
||||
@@ -108,8 +108,8 @@ También puedes configurar un letrero de anuncio en el shell administrativo util
|
||||
1. {% ifversion ghes or ghae %}A la derecha de{% else %}Debajo de {% endif %} "Anuncio", da clic en **Agregar anuncio**. 
|
||||
1. Debajo de "Anuncio", en el campo de texto, teclea el anuncio que quieras mostrar en un letrero. 
|
||||
1. Opcionalmente, debajo de "Vence en", selecciona el menú desplegable de calendario y da clic en la fecha de vencimiento. {% ifversion ghe-announce-dismiss %}
|
||||
1. Optionally, to allow each user to dismiss the announcement, select **User dismissible**.
|
||||
1. Opcionalmente, para permitir que cada usuario descarte el anuncio, selecciona **Descartable por el usuario**.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
{% data reusables.enterprise_site_admin_settings.message-preview-save %}
|
||||
{% endif %}
|
||||
|
||||
@@ -64,7 +64,6 @@ You can view more information about the person's access to your enterprise, such
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
{% ifversion ghec %}
|
||||
## Viewing pending invitations
|
||||
|
||||
@@ -92,7 +91,6 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in
|
||||
|
||||
|
||||
|
||||
|
||||
## Viewing suspended members in an {% data variables.product.prodname_emu_enterprise %}
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)."
|
||||
@@ -108,7 +106,7 @@ If your enterprise uses {% data variables.product.prodname_emus %}, you can also
|
||||
|
||||
You can view a list of all dormant users {% ifversion ghes or ghae %} who have not been suspended and {% endif %}who are not site administrators. {% data reusables.enterprise-accounts.dormant-user-activity-threshold %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
|
||||
|
||||
{% ifversion ghec or ghes > 3.1 %}
|
||||
{% ifversion ghec or ghes %}
|
||||
## Viewing members without an email address from a verified domain
|
||||
|
||||
You can view a list of members in your enterprise who don't have an email address from a verified domain associated with their user account on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
@@ -20,11 +20,8 @@ shortTitle: Generate new SSH key
|
||||
|
||||
If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
|
||||
If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
|
||||
|
||||
{% endif %}
|
||||
If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
|
||||
|
||||
## Generating a new SSH key
|
||||
@@ -190,7 +187,6 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
|
||||
## Generating a new SSH key for a hardware security key
|
||||
|
||||
If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
|
||||
@@ -246,7 +242,6 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
```
|
||||
7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -99,8 +99,6 @@ If you authenticate without {% data variables.product.prodname_cli %}, you will
|
||||
|
||||
To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
## {% data variables.product.company_short %}'s token formats
|
||||
|
||||
{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type.
|
||||
@@ -113,4 +111,3 @@ To use a personal access token or SSH key to access resources owned by an organi
|
||||
| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" |
|
||||
| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" |
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -55,7 +55,7 @@ Un token sin alcances asignados solo puede acceder a información pública. Para
|
||||
8. Haz clic en **Generar token**. 
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% elsif ghes > 3.1 or ghae %}
|
||||
{% elsif ghes or ghae %}
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ Una aplicación de contraseña única basada en el tiempo (TOTP) genera automát
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.security %}
|
||||
{% data reusables.two_fa.enable-two-factor-authentication %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 %}
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
5. Debajo de "Autenticación bifactorial", selecciona **Configurar utilizando una app** y haz clic en **Continuar**.
|
||||
6. Debajo de "Verificación de autenticación", realiza alguan de las siguientes acciones:
|
||||
- Escanea el código QR con la app del dispositivo móvil. Luego de escanear, la app muestra un código de seis dígitos que puedes ingresar en {% data variables.product.product_name %}.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: 'Error: Unknown key type'
|
||||
intro: Este error significa que el tipo de llave SSH que utilizaste no se reconoció o no es compatible con tu cliente SSH.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.2'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
|
||||
@@ -83,4 +83,4 @@ The following example timeline demonstrates how active committer count for {% da
|
||||
|
||||
{% data reusables.advanced-security.getting-the-most-from-your-license %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -12,7 +12,7 @@ shortTitle: Billing for GitHub Copilot
|
||||
|
||||
If you want to use {% data variables.product.prodname_copilot %}, you will need a subscription for your {% data variables.product.prodname_dotcom %} personal account. Para obtener más información acerca de las {% data variables.product.prodname_copilot %}, consulta la sección "[Acerca del {% data variables.product.prodname_copilot %}](/en/copilot/overview-of-github-copilot/about-github-copilot)".
|
||||
|
||||
Before starting a paid subscription, you can set up a one-time 60-day trial to evaluate {% data variables.product.prodname_copilot %}. To begin a trial, you will need to choose a monthly or yearly billing cycle, and provide a payment method. If you do not cancel the trial before the end of the 60 days, the trial will automatically convert to a paid subscription. You can cancel your {% data variables.product.prodname_copilot %} trial at any time during the 60 days and you won't be charged. If you cancel before the end of the trial, you will continue to have access to {% data variables.product.prodname_copilot %} until the 60-day trial period ends. For more information, see "[Managing your GitHub Copilot subscription](/en/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription)".
|
||||
Before starting a paid subscription, you can set up a one-time 60-day trial to evaluate {% data variables.product.prodname_copilot %}. To begin a trial, you will need to choose a monthly or yearly billing cycle, and provide a payment method. If you do not cancel the trial before the end of the 60 days, the trial will automatically convert to a paid subscription. You can cancel your {% data variables.product.prodname_copilot %} trial at any time during the 60 days and you won't be charged. If you cancel before the end of the trial, you will continue to have access to {% data variables.product.prodname_copilot %} until the 60-day trial period ends. For more information, see "[Managing your GitHub Copilot subscription](/en/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription)."
|
||||
|
||||
## Precios de {% data variables.product.prodname_copilot %}
|
||||
|
||||
|
||||
@@ -71,7 +71,7 @@ Cuando se intenta coincidir con usuarios a lo largo de las empresas, {% data var
|
||||
|
||||
Your license usage is recalculated shortly after each license sync is performed. You can view the timestamp of the last license sync job, and, if a job hasn't run since an email address was updated or verified, to resolve an issue with your consumed license report you can manually trigger one. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
|
||||
|
||||
{% ifversion ghec or ghes > 3.1 %}
|
||||
{% ifversion ghec or ghes %}
|
||||
If your enterprise uses verified domains, review the list of enterprise members who do not have an email address from a verified domain associated with their {% data variables.product.prodname_dotcom_the_website %} account. Often, these are the users who erroneously consume more than one licensed seat. Para obtener más información, consulta la sección "[Ver a los miembros sin un a dirección de correo electrónico desde un dominio verificado](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)".
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ By default, {% data variables.product.prodname_code_scanning %} analyzes your co
|
||||
|
||||
## About alert details
|
||||
|
||||
Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the alert severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
|
||||
Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the alert severity, security severity, and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
|
||||
{% data reusables.code-scanning.alert-default-branch %}
|
||||
@@ -45,16 +45,15 @@ When {% data variables.product.prodname_code_scanning %} reports data-flow alert
|
||||
|
||||
Alert severity levels may be `Error`, `Warning`, or `Note`.
|
||||
|
||||
If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify which severity level of code scanning alerts causes a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
|
||||
If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. You can specify which severity level of code scanning alerts causes a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
### About security severity levels
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
|
||||
|
||||
To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [this blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
|
||||
|
||||
By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
|
||||
By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.4 or ghae-issue-6251 or ghec %}
|
||||
### About analysis origins
|
||||
|
||||
@@ -89,21 +89,15 @@ If you scan pull requests, then the results appear as alerts in a pull request c
|
||||
Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
### Defining the severities causing pull request check failure
|
||||
|
||||
By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1 or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1 or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
|
||||
By default, only alerts with the severity level of `Error` or security severity level of `Critical` or `High` will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities and of security severities that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Code scanning", to the right of "Check Failure", use the drop-down menu to select the level of severity you would like to cause a pull request check failure.
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
### Avoiding unnecessary scans of pull requests
|
||||
|
||||
@@ -186,7 +180,6 @@ jobs:
|
||||
|
||||
For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis{% ifversion not ghes %} on self-hosted machines{% endif %}, see "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
## Specifying the location for {% data variables.product.prodname_codeql %} databases
|
||||
|
||||
In general, you do not need to worry about where the {% data variables.product.prodname_codeql_workflow %} places {% data variables.product.prodname_codeql %} databases since later steps will automatically find databases created by previous steps. However, if you are writing a custom workflow step that requires the {% data variables.product.prodname_codeql %} database to be in a specific disk location, for example to upload the database as a workflow artifact, you can specify that location using the `db-location` parameter under the `init` action.
|
||||
@@ -200,7 +193,6 @@ In general, you do not need to worry about where the {% data variables.product.p
|
||||
The {% data variables.product.prodname_codeql_workflow %} will expect the path provided in `db-location` to be writable, and either not exist, or be an empty directory. When using this parameter in a job running on a self-hosted runner or using a Docker container, it's the responsibility of the user to ensure that the chosen directory is cleared between runs, or that the databases are removed once they are no longer needed. {% ifversion fpt or ghec or ghes %} This is not necessary for jobs running on {% data variables.product.prodname_dotcom %}-hosted runners, which obtain a fresh instance and a clean filesystem each time they run. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."{% endif %}
|
||||
|
||||
If this parameter is not used, the {% data variables.product.prodname_codeql_workflow %} will create databases in a temporary location of its own choice.
|
||||
{% endif %}
|
||||
|
||||
## Changing the languages that are analyzed
|
||||
|
||||
@@ -246,10 +238,10 @@ Alternatively, you can install Python dependencies manually on any operating sys
|
||||
```yaml
|
||||
jobs:
|
||||
CodeQL-Build:
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
security-events: write
|
||||
actions: read{% endif %}
|
||||
actions: read
|
||||
|
||||
steps:
|
||||
- name: Checkout repository
|
||||
@@ -277,7 +269,6 @@ jobs:
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
## Configuring a category for the analysis
|
||||
|
||||
Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
|
||||
@@ -302,8 +293,6 @@ The `category` value will appear as the `<run>.automationDetails.id` property in
|
||||
|
||||
Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Running additional queries
|
||||
|
||||
{% data reusables.code-scanning.run-additional-queries %}
|
||||
|
||||
@@ -37,15 +37,11 @@ By default, the code scanning alerts page is filtered to show alerts for the def
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-code-scanning-alerts %}
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.code-scanning.explore-alert %}
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
|
||||
{% data reusables.code-scanning.alert-default-branch %}
|
||||
{% endif %}
|
||||
@@ -60,7 +56,6 @@ By default, the code scanning alerts page is filtered to show alerts for the def
|
||||
|
||||
For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository.
|
||||
@@ -69,7 +64,6 @@ For example, you can see when the last scan ran, the number of lines of code ana
|
||||
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
## Filtering {% data variables.product.prodname_code_scanning %} alerts
|
||||
|
||||
@@ -101,7 +95,7 @@ You can prefix the `tag` filter with `-` to exclude results with that tag. For e
|
||||
|
||||
You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. See "[About labels for alerts not in application code](#about-labels-for-alerts-that-are-not-found-in-application-code)" above for more information about the types of code that are not application code.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghec %}
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
## Searching {% data variables.product.prodname_code_scanning %} alerts
|
||||
|
||||
@@ -154,15 +148,11 @@ Anyone with write permission for a repository can fix an alert by committing a c
|
||||
|
||||
If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
|
||||
|
||||
You can use{% ifversion fpt or ghes > 3.1 or ghae or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed.
|
||||
You can use the free text search or the filters to display a subset of alerts and then in turn mark all matching alerts as closed.
|
||||
|
||||
Alerts may be fixed in one branch but not in another. You can use the "Branch" filter, on the summary of alerts, to check whether an alert is fixed in a particular branch.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
|
||||
{% data reusables.code-scanning.filter-non-default-branches %}
|
||||
@@ -206,20 +196,17 @@ To dismiss {% ifversion delete-code-scanning-alerts %}or delete{% endif %} alert
|
||||
|
||||
|
||||
|
||||
Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
|
||||
Optionally, you can use the free text search or the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
|
||||
|
||||
{% ifversion ghes > 3.1 or ghae %}
|
||||
{% ifversion ghes or ghae %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}{% endif %}
|
||||
1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
1. Review the alert, then click {% ifversion comment-dismissed-code-scanning-alert %}**Dismiss alert** and choose, or type, a reason for closing the alert.
|
||||
|
||||
{% else %}**Dismiss** and choose a reason for closing the alert.
|
||||
|
||||
@@ -66,10 +66,10 @@ on:
|
||||
jobs:
|
||||
analyze:
|
||||
name: Analyze
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
security-events: write
|
||||
actions: read{% endif %}
|
||||
actions: read
|
||||
|
||||
strategy:
|
||||
fail-fast: false
|
||||
|
||||
@@ -139,11 +139,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re
|
||||
|
||||
**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -181,11 +177,7 @@ There are other situations where there may be no analysis for the latest commit
|
||||
|
||||
To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.
|
||||
|
||||
|
||||
@@ -58,12 +58,11 @@ For all configurations of {% data variables.product.prodname_code_scanning %}, t
|
||||
|
||||
### {% data variables.product.prodname_code_scanning_capc %} results check failures
|
||||
|
||||
If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, `critical`, or `high`,{% endif %} the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds.
|
||||
If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`, `critical`, or `high`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds.
|
||||
|
||||
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1 or ghae or ghec %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".
|
||||
{% endif %}
|
||||
You can override the default behavior in your repository settings, by specifying the level of severities and security severities that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".
|
||||
|
||||
### Other {% data variables.product.prodname_code_scanning %} checks
|
||||
|
||||
|
||||
@@ -74,10 +74,10 @@ Si una compilación automática de código para un lenguaje compilado dentro de
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
analyze:{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
analyze:
|
||||
permissions:
|
||||
security-events: write
|
||||
actions: read{% endif %}
|
||||
actions: read
|
||||
...
|
||||
strategy:
|
||||
fail-fast: false
|
||||
@@ -166,7 +166,6 @@ El artefacto contendrá una copia archivada de los archivos de código fuente qu
|
||||
|
||||
{% data reusables.code-scanning.alerts-found-in-generated-code %}
|
||||
|
||||
|
||||
## Extracción de errores en la base de datos
|
||||
|
||||
El equipo de {% data variables.product.prodname_codeql %} trabaja constantemente en los errores de extracción críticos para asegurarse de que todos los archivos de código fuente pueden escanearse. Sin embargo, los extractores de {% data variables.product.prodname_codeql %} sí generan errores durante la creación de bases de datos ocasionalmente. {% data variables.product.prodname_codeql %} proporciona información acerca de los errores de extracción y las advertencias que se generan durante la creación de bases de datos en un archivo de bitácora. La información de diagnóstico de extracción proporciona una indicación de la salud general de la base de datos. La mayoría de los errores del extractor no impactan el análisis significativamente. Una pequeña parte de los errores del extractor es saludable y, a menudo, indica un buen estado del análisis.
|
||||
@@ -179,7 +178,6 @@ Sin embargo, si ves errores del extractor en la vasta mayoría de archivos que s
|
||||
La característica de `autobuild` de {% data variables.product.prodname_codeql %} utiliza la heurística para compilar el código en un repositorio, sin embargo, algunas veces este acercamiento da como resultado un análisis incompleto de un repositorio. Por ejemplo, cuando existen comandos múltiples de `build.sh` en un solo repositorio, el análisis podría no completarse, ya que el paso de `autobuild` solo se ejecutará en uno de los comandos. La solución es reemplazar el paso de `autobuild` con los pasos de compilación que compilarán todo el código fuente que quieras analizar. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
|
||||
{% endif %}
|
||||
|
||||
|
||||
## La compilación tarda demasiado
|
||||
|
||||
Si tu compilación con análisis de {% data variables.product.prodname_codeql %} toma demasiado para ejecutarse, hay varios acercamientos que puedes intentar para reducir el tiempo de compilación.
|
||||
|
||||
@@ -23,7 +23,6 @@ shortTitle: Visualizar las bitácoras del escaneo de código
|
||||
|
||||
Puedes utilizar diversas herramientas para configurar el {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)".
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
La bitácora y la información diagnóstica que tengas disponible dependerá del método que utilices para el {% data variables.product.prodname_code_scanning %} en tu repositorio. Puedes verificar el tipo de {% data variables.product.prodname_code_scanning %} que estás utilizando en la pestaña de **Seguridad** de tu repositorio si utilizas el menú desplegable de **Herramienta** en la lista de alertas. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)".
|
||||
|
||||
## Acerca del análisis y la información de diagnóstico
|
||||
@@ -46,7 +45,6 @@ Para obtener más información sobre el {% data variables.product.prodname_codeq
|
||||
|
||||
{% data reusables.code-scanning.extractor-diagnostics %}
|
||||
|
||||
{% endif %}
|
||||
## Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
Esta sección aplica a la ejecución del {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_actions %}(de {% data variables.product.prodname_codeql %} o de terceros).
|
||||
@@ -73,10 +71,6 @@ Después de configurar el {% data variables.product.prodname_code_scanning %} pa
|
||||
|
||||
**Nota:** Si levantaste una solicitud de cambios para agregar el flujo de trabajo del {% data variables.product.prodname_code_scanning %} a las alertas del repositorio, las alertas de esa solicitud de cambios no se mostraràn directamente en la pàgina del {% data variables.product.prodname_code_scanning_capc %} hasta que se fusione dicha solicitud. Si se encontrò alguna de las alertas, puedes verlas antes de que se fusione la solicitud de extracciòn dando clic en el enlace de **_n_ alertas encontradas** en el letrero de la pàgina del {% data variables.product.prodname_code_scanning_capc %}.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -33,7 +33,6 @@ To upload a SARIF file from a third-party static code analysis engine, you'll ne
|
||||
|
||||
If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %}{% ifversion codeql-runner-supported %}, using the {% data variables.product.prodname_codeql_runner %},{% endif %} or using the {% data variables.product.prodname_codeql_cli %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)"{% ifversion codeql-runner-supported %}, "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)",{% endif %} or "[Installing CodeQL CLI in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
You can upload multiple SARIF files for the same commit, and display the data from each file as {% data variables.product.prodname_code_scanning %} results. When you upload multiple SARIF files for a commit, you must indicate a "category" for each analysis. The way to specify a category varies according to the analysis method:
|
||||
- Using the {% data variables.product.prodname_codeql_cli %} directly, pass the `--sarif-category` argument to the `codeql database analyze` command when you generate SARIF files. For more information, see "[Configuring CodeQL CLI in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#about-generating-code-scanning-results-with-codeql-cli)."
|
||||
- Using {% data variables.product.prodname_actions %} with `codeql-action/analyze`, the category is set automatically from the workflow name and any matrix variables (typically, `language`). You can override this by specifying a `category` input for the action, which is useful when you analyze different sections of a mono-repository in a single workflow.
|
||||
@@ -41,7 +40,6 @@ You can upload multiple SARIF files for the same commit, and display the data fr
|
||||
- If you are not using either of these approaches, you must specify a unique `runAutomationDetails.id` in each SARIF file to upload. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
|
||||
|
||||
If you upload a second SARIF file for a commit with the same category and from the same tool, the earlier results are overwritten. However, if you try to upload multiple SARIF files for the same tool and category in a single {% data variables.product.prodname_actions %} workflow run, the misconfiguration is detected and the run will fail.
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.prodname_dotcom %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
|
||||
|
||||
@@ -110,9 +108,9 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr
|
||||
| `help.text` | **Required.** Documentation for the rule using text format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results.
|
||||
| `help.markdown` | **Recommended.** Documentation for the rule using Markdown format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. When `help.markdown` is available, it is displayed instead of `help.text`.
|
||||
| `properties.tags[]` | **Optional.** An array of strings. {% data variables.product.prodname_code_scanning_capc %} uses `tags` to allow you to filter results on {% data variables.product.prodname_dotcom %}. For example, it is possible to filter to all results that have the tag `security`.
|
||||
| `properties.precision` | **Recommended.** A string that indicates how often the results indicated by this rule are true. For example, if a rule has a known high false-positive rate, the precision should be `low`. {% data variables.product.prodname_code_scanning_capc %} orders results by precision on {% data variables.product.prodname_dotcom %} so that the results with the highest `level`, and highest `precision` are shown first. Can be one of: `very-high`, `high`, `medium`, or `low`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| `properties.precision` | **Recommended.** A string that indicates how often the results indicated by this rule are true. For example, if a rule has a known high false-positive rate, the precision should be `low`. {% data variables.product.prodname_code_scanning_capc %} orders results by precision on {% data variables.product.prodname_dotcom %} so that the results with the highest `level`, and highest `precision` are shown first. Can be one of: `very-high`, `high`, `medium`, or `low`.
|
||||
| `properties.problem.severity` | **Recommended.** A string that indicates the level of severity of any alerts generated by a non-security query. This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `problem.severity`, and highest `precision` are shown first. Can be one of: `error`, `warning`, or `recommendation`.
|
||||
| `properties.security-severity` | **Recommended.** A string representing a score that indicates the level of severity, between 0.0 and 10.0, for security queries (`@tags` includes `security`). This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `security-severity`, and highest `precision` are shown first. {% data variables.product.prodname_code_scanning_capc %} translates numerical scores as follows: over 9.0 is `critical`, 7.0 to 8.9 is `high`, 4.0 to 6.9 is `medium` and 3.9 or less is `low`. {% endif %}
|
||||
| `properties.security-severity` | **Recommended.** A string representing a score that indicates the level of severity, between 0.0 and 10.0, for security queries (`@tags` includes `security`). This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `security-severity`, and highest `precision` are shown first. {% data variables.product.prodname_code_scanning_capc %} translates numerical scores as follows: over 9.0 is `critical`, 7.0 to 8.9 is `high`, 4.0 to 6.9 is `medium` and 3.9 or less is `low`.
|
||||
|
||||
### `result` object
|
||||
|
||||
@@ -150,7 +148,6 @@ A location within a programming artifact, such as a file in the repository or a
|
||||
| `region.endLine` | **Required.** The line number of the last character in the region.
|
||||
| `region.endColumn` | **Required.** The column number of the character following the end of the region.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
### `runAutomationDetails` object
|
||||
|
||||
The `runAutomationDetails` object contains information that specifies the identity of a run.
|
||||
@@ -187,8 +184,6 @@ For more information about the `runAutomationDetails` object and the `id` field,
|
||||
|
||||
Note that the rest of the supported fields are ignored.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## SARIF output file examples
|
||||
|
||||
These example SARIF output files show supported properties and example values.
|
||||
@@ -255,7 +250,6 @@ This SARIF output file has example values to show the minimum required propertie
|
||||
|
||||
This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}.
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
```json
|
||||
{
|
||||
"$schema": "https://json.schemastore.org/sarif-2.1.0.json",
|
||||
@@ -508,254 +502,4 @@ This SARIF output file has example values to show all supported SARIF properties
|
||||
]
|
||||
}
|
||||
```
|
||||
{% else %}
|
||||
```json
|
||||
{
|
||||
"$schema": "https://json.schemastore.org/sarif-2.1.0.json",
|
||||
"version": "2.1.0",
|
||||
"runs": [
|
||||
{
|
||||
"tool": {
|
||||
"driver": {
|
||||
"name": "Tool Name",
|
||||
"semanticVersion": "2.0.0",
|
||||
"rules": [
|
||||
{
|
||||
"id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
|
||||
"name": "js/unused-local-variable",
|
||||
"shortDescription": {
|
||||
"text": "Unused variable, import, function or class"
|
||||
},
|
||||
"fullDescription": {
|
||||
"text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
|
||||
},
|
||||
"defaultConfiguration": {
|
||||
"level": "note"
|
||||
},
|
||||
"properties": {
|
||||
"tags": [
|
||||
"maintainability"
|
||||
],
|
||||
"precision": "very-high"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
|
||||
"name": "js/inconsistent-use-of-new",
|
||||
"shortDescription": {
|
||||
"text": "Inconsistent use of 'new'"
|
||||
},
|
||||
"fullDescription": {
|
||||
"text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
|
||||
},
|
||||
"properties": {
|
||||
"tags": [
|
||||
"reliability",
|
||||
"correctness",
|
||||
"language-features"
|
||||
],
|
||||
"precision": "very-high"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "R01"
|
||||
}
|
||||
]
|
||||
}
|
||||
},
|
||||
"results": [
|
||||
{
|
||||
"ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
|
||||
"ruleIndex": 0,
|
||||
"message": {
|
||||
"text": "Unused variable foo."
|
||||
},
|
||||
"locations": [
|
||||
{
|
||||
"physicalLocation": {
|
||||
"artifactLocation": {
|
||||
"uri": "main.js",
|
||||
"uriBaseId": "%SRCROOT%"
|
||||
},
|
||||
"region": {
|
||||
"startLine": 2,
|
||||
"startColumn": 7,
|
||||
"endColumn": 10
|
||||
}
|
||||
}
|
||||
}
|
||||
],
|
||||
"partialFingerprints": {
|
||||
"primaryLocationLineHash": "39fa2ee980eb94b0:1",
|
||||
"primaryLocationStartColumnFingerprint": "4"
|
||||
}
|
||||
},
|
||||
{
|
||||
"ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
|
||||
"ruleIndex": 1,
|
||||
"message": {
|
||||
"text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
|
||||
},
|
||||
"locations": [
|
||||
{
|
||||
"physicalLocation": {
|
||||
"artifactLocation": {
|
||||
"uri": "src/promises.js",
|
||||
"uriBaseId": "%SRCROOT%"
|
||||
},
|
||||
"region": {
|
||||
"startLine": 2
|
||||
}
|
||||
}
|
||||
}
|
||||
],
|
||||
"partialFingerprints": {
|
||||
"primaryLocationLineHash": "5061c3315a741b7d:1",
|
||||
"primaryLocationStartColumnFingerprint": "7"
|
||||
},
|
||||
"relatedLocations": [
|
||||
{
|
||||
"id": 1,
|
||||
"physicalLocation": {
|
||||
"artifactLocation": {
|
||||
"uri": "src/ParseObject.js",
|
||||
"uriBaseId": "%SRCROOT%"
|
||||
},
|
||||
"region": {
|
||||
"startLine": 2281,
|
||||
"startColumn": 33,
|
||||
"endColumn": 55
|
||||
}
|
||||
},
|
||||
"message": {
|
||||
"text": "here"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": 2,
|
||||
"physicalLocation": {
|
||||
"artifactLocation": {
|
||||
"uri": "src/LiveQueryClient.js",
|
||||
"uriBaseId": "%SRCROOT%"
|
||||
},
|
||||
"region": {
|
||||
"startLine": 166
|
||||
}
|
||||
},
|
||||
"message": {
|
||||
"text": "here"
|
||||
}
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"ruleId": "R01",
|
||||
"message": {
|
||||
"text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
|
||||
},
|
||||
"level": "error",
|
||||
"locations": [
|
||||
{
|
||||
"physicalLocation": {
|
||||
"artifactLocation": {
|
||||
"uri": "full.sarif",
|
||||
"uriBaseId": "%SRCROOT%"
|
||||
},
|
||||
"region": {
|
||||
"startLine": 54,
|
||||
"startColumn": 10,
|
||||
"endLine": 55,
|
||||
"endColumn": 25
|
||||
}
|
||||
}
|
||||
}
|
||||
],
|
||||
"relatedLocations": [
|
||||
{
|
||||
"id": 1,
|
||||
"physicalLocation": {
|
||||
"artifactLocation": {
|
||||
"uri": "full.sarif"
|
||||
},
|
||||
"region": {
|
||||
"startLine": 81,
|
||||
"startColumn": 10,
|
||||
"endColumn": 18
|
||||
}
|
||||
},
|
||||
"message": {
|
||||
"text": "here"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": 2,
|
||||
"physicalLocation": {
|
||||
"artifactLocation": {
|
||||
"uri": "full.sarif"
|
||||
},
|
||||
"region": {
|
||||
"startLine": 82,
|
||||
"startColumn": 10,
|
||||
"endColumn": 21
|
||||
}
|
||||
},
|
||||
"message": {
|
||||
"text": "here"
|
||||
}
|
||||
}
|
||||
],
|
||||
"codeFlows": [
|
||||
{
|
||||
"threadFlows": [
|
||||
{
|
||||
"locations": [
|
||||
{
|
||||
"location": {
|
||||
"physicalLocation": {
|
||||
"region": {
|
||||
"startLine": 11,
|
||||
"endLine": 29,
|
||||
"startColumn": 10,
|
||||
"endColumn": 18
|
||||
},
|
||||
"artifactLocation": {
|
||||
"uriBaseId": "%SRCROOT%",
|
||||
"uri": "full.sarif"
|
||||
}
|
||||
},
|
||||
"message": {
|
||||
"text": "Rule has index 0"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"location": {
|
||||
"physicalLocation": {
|
||||
"region": {
|
||||
"endColumn": 47,
|
||||
"startColumn": 12,
|
||||
"startLine": 12
|
||||
},
|
||||
"artifactLocation": {
|
||||
"uriBaseId": "%SRCROOT%",
|
||||
"uri": "full.sarif"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"partialFingerprints": {
|
||||
"primaryLocationLineHash": "ABC:2"
|
||||
}
|
||||
}
|
||||
],
|
||||
"columnKind": "utf16CodeUnits"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -84,13 +84,13 @@ on:
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
# required for all workflows
|
||||
security-events: write
|
||||
# only required for workflows in private repositories
|
||||
actions: read
|
||||
contents: read{% endif %}
|
||||
contents: read
|
||||
steps:
|
||||
# This step checks out a copy of your repository.
|
||||
- name: Checkout repository
|
||||
@@ -125,13 +125,13 @@ on:
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
# required for all workflows
|
||||
security-events: write
|
||||
# only required for workflows in private repositories
|
||||
actions: read
|
||||
contents: read{% endif %}
|
||||
contents: read
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Run npm install
|
||||
|
||||
@@ -32,7 +32,6 @@ redirect_from:
|
||||
|
||||
{% data reusables.code-scanning.codeql-context-for-actions-and-third-party-tools %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
<!--Content for GitHub.com, GHAE next, and GHES 3.2 and onward. CodeQL CLI is the preferred method, and CodeQL runner is deprecated. -->
|
||||
|
||||
{% data reusables.code-scanning.codeql-cli-context-for-third-party-tools %}
|
||||
@@ -66,28 +65,5 @@ Since version 2.6.3, the {% data variables.product.prodname_codeql_cli %} has ha
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
<!--Content for GHES 3.1 only. Both CodeQL CLI and CodeQL runner are available -->
|
||||
{% ifversion ghes < 3.2 %}
|
||||
You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
|
||||
|
||||
[{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.6.3 is available now for {% data variables.product.prodname_ghe_server %} 3.0 and later versions. For more information on migrating to the {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)."
|
||||
|
||||
{% data reusables.code-scanning.upload-sarif-ghas %}
|
||||
|
||||
## Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
|
||||
|
||||
{% data reusables.code-scanning.what-is-codeql-cli %}
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} is a deprecated command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions.
|
||||
|
||||
{% data variables.product.prodname_codeql_cli %} 2.6.3 is a complete replacement for the runner with full feature parity. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly.
|
||||
|
||||
For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
|
||||
|
||||
{% data reusables.code-scanning.deprecation-codeql-runner %}
|
||||
|
||||
For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -38,17 +38,10 @@ Once you've made the {% data variables.product.prodname_codeql_cli %} available
|
||||
|
||||
You use three different commands to generate results and upload them to {% data variables.product.product_name %}:
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
<!--Option to analyze multiple languages with one call-->
|
||||
1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository.
|
||||
2. ` database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file.
|
||||
3. `github upload-results` to upload the resulting SARIF files to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts.
|
||||
{% else %}
|
||||
<!--Only one language can be analyzed-->
|
||||
1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of a supported programming language in the repository.
|
||||
2. ` database analyze` to run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file.
|
||||
3. `github upload-results` to upload the resulting SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts.
|
||||
{% endif %}
|
||||
|
||||
You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
|
||||
|
||||
@@ -62,7 +55,7 @@ You can display the command-line help for any command using the <nobr>`--help`</
|
||||
2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
|
||||
3. Find the build command, if any, for the codebase. Typically this is available in a configuration file in the CI system.
|
||||
4. Run `codeql database create` from the checkout root of your repository and build the codebase.
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
```shell
|
||||
# Single supported language - create one CodeQL databsae
|
||||
codeql database create <database> --command<build> --language=<language-identifier>
|
||||
@@ -71,11 +64,7 @@ You can display the command-line help for any command using the <nobr>`--help`</
|
||||
codeql database create <database> --command<build> \
|
||||
--db-cluster --language=<language-identifier>,<language-identifier>
|
||||
```
|
||||
{% else %}
|
||||
```shell
|
||||
codeql database create <database> --command<build> --language=<language-identifier>
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
|
||||
@@ -85,15 +74,15 @@ You can display the command-line help for any command using the <nobr>`--help`</
|
||||
| Option | Required | Usage |
|
||||
|--------|:--------:|-----|
|
||||
| `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory. If you also specify `--db-cluster`, this is the parent directory and a subdirectory is created for each language analyzed.|
|
||||
| <nobr>`--language`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the identifier for the language to create a database for, one of: `{% data reusables.code-scanning.codeql-languages-keywords %}` (use `javascript` to analyze TypeScript code). {% ifversion fpt or ghes > 3.1 or ghae or ghec %}When used with <nobr>`--db-cluster`</nobr>, the option accepts a comma-separated list, or can be specified more than once.{% endif %}
|
||||
| <nobr>`--command`</nobr> | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Not needed for Python and JavaScript/TypeScript analysis. | {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| <nobr>`--language`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the identifier for the language to create a database for, one of: `{% data reusables.code-scanning.codeql-languages-keywords %}` (use `javascript` to analyze TypeScript code). When used with <nobr>`--db-cluster`</nobr>, the option accepts a comma-separated list, or can be specified more than once.
|
||||
| <nobr>`--command`</nobr> | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Not needed for Python and JavaScript/TypeScript analysis. |
|
||||
| <nobr>`--db-cluster`</nobr> | | Optional. Use in multi-language codebases to generate one database for each language specified by <nobr>`--language`</nobr>.
|
||||
| <nobr>`--no-run-unnecessary-builds`</nobr> | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript). {% endif %}
|
||||
| <nobr>`--no-run-unnecessary-builds`</nobr> | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript).
|
||||
| <nobr>`--source-root`</nobr> | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |
|
||||
|
||||
For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
|
||||
|
||||
### {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Single language example{% else %}Basic example{% endif %}
|
||||
### Single language example
|
||||
|
||||
This example creates a {% data variables.product.prodname_codeql %} database for the repository checked out at `/checkouts/example-repo`. It uses the JavaScript extractor to create a hierarchical representation of the JavaScript and TypeScript code in the repository. The resulting database is stored in `/codeql-dbs/example-repo`.
|
||||
|
||||
@@ -111,7 +100,6 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \
|
||||
> Successfully created database at /codeql-dbs/example-repo.
|
||||
```
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
### Multiple language example
|
||||
|
||||
This example creates two {% data variables.product.prodname_codeql %} databases for the repository checked out at `/checkouts/example-repo-multi`. It uses:
|
||||
@@ -142,7 +130,6 @@ Finalizing databases at /codeql-dbs/example-repo-multi.
|
||||
Successfully created databases at /codeql-dbs/example-repo-multi.
|
||||
$
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
## Analyzing a {% data variables.product.prodname_codeql %} database
|
||||
|
||||
@@ -153,7 +140,6 @@ $
|
||||
--output=<output> {% ifversion codeql-packs %}--download <packs,queries>{% else %}<queries>{% endif %}
|
||||
```
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results.
|
||||
@@ -164,31 +150,29 @@ codeql database analyze <database> --format=<format> \
|
||||
{% ifversion codeql-packs %}<packs,queries>{% else %}<queries>{% endif %}
|
||||
```
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
| 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>/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 %}
|
||||
| <nobr>`--output`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.
|
||||
| <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.|{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
|
||||
| <nobr>`--sarif-add-query-help`</nobr> | | Optional. Use if you want to include any available markdown-rendered query help for custom queries used in your analysis. Any query help for custom queries included in the SARIF output will be displayed in the code scanning UI if the relevant query generates an alert. For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/#including-query-help-for-custom-codeql-queries-in-sarif-files) in the documentation for the {% data variables.product.prodname_codeql_cli %}.{% endif %}{% ifversion codeql-packs %}
|
||||
| `<packs>` | | Optional. Use if you want to include CodeQL query packs in your analysis. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} packs](#downloading-and-using-codeql-query-packs)."
|
||||
| <nobr>`--download`</nobr> | | Optional. Use if some of your CodeQL query packs are not yet on disk and need to be downloaded before running queries.{% endif %}
|
||||
| <nobr>`--threads`</nobr> | | Optional. Use if you want to use more than one thread to run queries. The default value is `1`. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify `0`.
|
||||
| <nobr>`--verbose`</nobr> | | Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae or ghec %} and diagnostic data from the database creation process{% endif %}.
|
||||
|
||||
| <nobr>`--verbose`</nobr> | | Optional. Use to get more detailed information about the analysis process and diagnostic data from the database creation process.
|
||||
|
||||
For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
|
||||
|
||||
### Basic example
|
||||
|
||||
This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %}
|
||||
This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.
|
||||
|
||||
```
|
||||
$ codeql database analyze /codeql-dbs/example-repo \
|
||||
javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae or ghec %}--sarif-category=javascript \{% endif %}
|
||||
javascript-code-scanning.qls --sarif-category=javascript \
|
||||
--format={% ifversion fpt or ghae or ghec %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif
|
||||
|
||||
> Running queries.
|
||||
@@ -212,7 +196,7 @@ When you have decided on the most secure and reliable method for your CI server,
|
||||
```shell
|
||||
echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \
|
||||
--ref=<ref> --commit=<commit> --sarif=<file> \
|
||||
{% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin
|
||||
{% ifversion ghes or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin
|
||||
```
|
||||
|
||||
| Option | Required | Usage |
|
||||
@@ -220,7 +204,7 @@ When you have decided on the most secure and reliable method for your CI server,
|
||||
| <nobr>`--repository`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the *OWNER/NAME* of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% ifversion fpt or ghec %}, unless the repository is public{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
|
||||
| <nobr>`--ref`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pull/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pull/NUMBER/merge`.
|
||||
| <nobr>`--commit`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed.
|
||||
| <nobr>`--sarif`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %}
|
||||
| <nobr>`--sarif`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes or ghae %}
|
||||
| <nobr>`--github-url`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %}
|
||||
| <nobr>`--github-auth-stdin`</nobr> | | Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token.
|
||||
|
||||
@@ -233,7 +217,7 @@ This example uploads results from the SARIF file `temp/example-repo-js.sarif` to
|
||||
```
|
||||
$ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \
|
||||
--ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
|
||||
--sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \
|
||||
--sarif=/temp/example-repo-js.sarif {% ifversion ghes or ghae %}--github-url={% data variables.command_line.git_url_example %} \
|
||||
{% endif %}--github-auth-stdin
|
||||
```
|
||||
|
||||
@@ -292,8 +276,6 @@ echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download <scope/name@version:path&g
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
## Example CI configuration for {% data variables.product.prodname_codeql %} analysis
|
||||
|
||||
This is an example of the series of commands that you might use to analyze a codebase with two supported languages and then upload the results to {% data variables.product.product_name %}.
|
||||
@@ -344,8 +326,6 @@ By default, {% data variables.product.prodname_code_scanning %} expects one SARI
|
||||
|
||||
If you want to upload more than one set of results to the {% data variables.product.prodname_code_scanning %} API for a commit in a repository, you must identify each set of results as a unique set. For repositories where you create more than one {% data variables.product.prodname_codeql %} database to analyze for each commit, use the `--sarif-category` option to specify a language or other unique category for each SARIF file that you generate for that repository.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
|
||||
|
||||
@@ -186,8 +186,8 @@ Analyzes the code in the {% data variables.product.prodname_codeql %} databases
|
||||
| `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}. |
|
||||
| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. |
|
||||
| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. |
|
||||
| <nobr>`--no-add-snippets`</nobr> | | None. Excludes code snippets from the SARIF output. |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
| <nobr>`--category`<nobr> | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. |{% endif %}
|
||||
| <nobr>`--no-add-snippets`</nobr> | | None. Excludes code snippets from the SARIF output. |
|
||||
| <nobr>`--category`<nobr> | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. |
|
||||
| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. |
|
||||
| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. |
|
||||
| `--debug` | | None. Prints more verbose output. |
|
||||
|
||||
@@ -103,5 +103,5 @@ You can also see all the {% data variables.product.prodname_dependabot_alerts %}
|
||||
## Leer más
|
||||
|
||||
- "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
|
||||
- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %}
|
||||
- "[Ver y actualizar las {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %}
|
||||
{% ifversion fpt or ghec %}- "[Privacidad en {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configuring notifications for Dependabot alerts
|
||||
shortTitle: Configure notifications
|
||||
title: Configurar las notificaciones para las alertas del Dependabot
|
||||
shortTitle: Configurar notificaciones
|
||||
intro: 'Optimiza la forma en la que recibes notificaciones de {% data variables.product.prodname_dependabot_alerts %}.'
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
|
||||
@@ -21,12 +21,12 @@ topics:
|
||||
- Repositories
|
||||
---
|
||||
|
||||
## About notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
## Acerca de las notificaciones para las {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifica a los mantenedores de los repositorios afectados sobre la alerta nueva de acuerdo con sus preferencias de notificaciones.{% ifversion fpt or ghec %}El {% data variables.product.prodname_dependabot %} se habilita predeterminadamente en todos los repositorios públicos. En el caso de las {% data variables.product.prodname_dependabot_alerts %}, predeterminadamente, recibirás {% data variables.product.prodname_dependabot_alerts %} por correo electrónico, agrupadas por la vulnerabilidad específica.
|
||||
Cuando el {% data variables.product.prodname_dependabot %} detecta dependencias vulnerables{% ifversion GH-advisory-db-supports-malware %} o malware{% endif %} en tus repositorios, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de seguridad del repositorio. {% data variables.product.product_name %} notifica a los mantenedores de los repositorios afectados sobre la alerta nueva de acuerdo con sus preferencias de notificaciones.{% ifversion fpt or ghec %}El {% data variables.product.prodname_dependabot %} se habilita predeterminadamente en todos los repositorios públicos. En el caso de las {% data variables.product.prodname_dependabot_alerts %}, predeterminadamente, recibirás {% data variables.product.prodname_dependabot_alerts %} por correo electrónico, agrupadas por la vulnerabilidad específica.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}Si eres un propietario de organización, puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios en tu organización con un clic. You can also set whether {% data variables.product.prodname_dependabot_alerts %} will be enabled or disabled for newly-created repositories. Para obtener más información, consulta la sección "[Administrar la configuración de análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)".
|
||||
{% ifversion fpt or ghec %}Si eres un propietario de organización, puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios en tu organización con un clic. También puedes configurar si las {% data variables.product.prodname_dependabot_alerts %} se habilitarán o inhabilitarán para los repositorios recién creados. Para obtener más información, consulta la sección "[Administrar la configuración de análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)".
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
@@ -37,7 +37,7 @@ Los propietarios de empresas también pueden habilitar las {% data variables.pro
|
||||
|
||||
## Configurar las notificaciones para las {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghec %}
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
Cuando se detecta una alerta nueva del {% data variables.product.prodname_dependabot %}, {% data variables.product.product_name %} notifica a todos los usuarios del repositorio con acceso a las {% data variables.product.prodname_dependabot_alerts %} de acuerdo con sus preferencias de notificación. Recibirás las alertas si estás observando el repositorio, si habilitas las notificaciones para las alertas de seguridad para toda la actividad del repositorio y si es que no lo estás ignorando. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
|
||||
{% endif %}
|
||||
|
||||
@@ -56,7 +56,7 @@ Puedes configurar los ajustes de notificaciones para ti mismo o para tu organiza
|
||||
|
||||
{% data reusables.repositories.security-alerts-x-github-severity %}Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
|
||||
|
||||
## How to reduce the noise from notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
## Cómo reducir el ruido de las notificacines para las {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
Si te preocupa recibir demasiadas notificaciones para las {% data variables.product.prodname_dependabot_alerts %}, te recomendamos que te unas al resumen semanal por correo electrónico o que apagues las notificaciones mientras mantienes habilitadas las {% data variables.product.prodname_dependabot_alerts %}. Aún puedes navegar para ver tus {% data variables.product.prodname_dependabot_alerts %} en la pestaña de seguridad de tu repositorio. For more information, see "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user