diff --git a/translations/es-ES/content/actions/learn-github-actions/contexts.md b/translations/es-ES/content/actions/learn-github-actions/contexts.md index e3ff6f9ca30f..47f5f8227b11 100644 --- a/translations/es-ES/content/actions/learn-github-actions/contexts.md +++ b/translations/es-ES/content/actions/learn-github-actions/contexts.md @@ -181,12 +181,12 @@ The `github` context contains information about the workflow run and the event t | `github` | `object` | The top-level context available during any job or step in a workflow. This object contains all the properties listed below. | | `github.action` | `string` | The name of the action currently running, or the [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) of a step. {% data variables.product.prodname_dotcom %} removes special characters, and uses the name `__run` when the current step runs a script without an `id`. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. | | `github.action_path` | `string` | The path where an action is located. This property is only supported in composite actions. You can use this path to access files located in the same repository as the action. | -| `github.action_ref` | `string` | For a step executing an action, this is the ref of the action being executed. For example, `v2`. -| `github.action_repository` | `string` | For a step executing an action, this is the owner and repository name of the action. For example, `actions/checkout`. +| `github.action_ref` | `string` | For a step executing an action, this is the ref of the action being executed. For example, `v2`. | +| `github.action_repository` | `string` | For a step executing an action, this is the owner and repository name of the action. For example, `actions/checkout`. | | `github.actor` | `string` | The username of the user that initiated the workflow run. | | `github.api_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} REST API. | | `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | -| `github.env` | `string` | Path on the runner to the file that sets environment variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)." +| `github.env` | `string` | Path on the runner to the file that sets environment variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)." | | `github.event` | `object` | The full event webhook payload. You can access individual properties of the event using this context. This object is identical to the webhook payload of the event that triggered the workflow run, and is different for each event. The webhooks for each {% data variables.product.prodname_actions %} event is linked in "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." For example, for a workflow run triggered by the [`push` event](/actions/using-workflows/events-that-trigger-workflows#push), this object contains the contents of the [push webhook payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push). | | `github.event_name` | `string` | The name of the event that triggered the workflow run. | | `github.event_path` | `string` | The path to the file on the runner that contains the full event webhook payload. | diff --git a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md index f2b4a0b5745d..741eb53f882d 100644 --- a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md +++ b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md @@ -113,7 +113,7 @@ Puedes definir entradas y secretos, las cuales pueden pasarse desde el flujo de runs-on: ubuntu-latest environment: production steps: - - uses: ./.github/actions/my-action + - uses: ./.github/workflows/my-action with: username: ${{ inputs.username }} token: ${{ secrets.envPAT }} @@ -154,7 +154,7 @@ jobs: name: Pass input and secrets to my-action runs-on: ubuntu-latest steps: - - uses: ./.github/actions/my-action + - uses: ./.github/workflows/my-action with: username: ${{ inputs.username }} token: ${{ secrets.token }} diff --git a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md index fd774e012e21..746a20ed8912 100644 --- a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md +++ b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md @@ -195,7 +195,11 @@ Si quieres un control más granular que el que proporcionan los eventos, tipos d ### Utilziar condicionales -Puedes utilizar condicionales para controlar aún más si se ejecutarán los jobs o pasos de tu flujo de trabajo. Por ejemplo, si quieres que el flujo de trabajo se ejecute cuando se agrega una etiqueta específica a una propuesta, puedes activar el tipo de actividad de evento `issues labeled` y utilizar una condicional para verificar qué etiqueta activó el flujo de trabajo. El siguiente flujo de trabajo se ejecutará cuando se agregue cualquier etiqueta a una propuesta en su repositorio, pero el job `run_if_label_matches` solo se ejecutará si la etiqueta se nombra `bug`. +Puedes utilizar condicionales para controlar aún más si se ejecutarán los jobs o pasos de tu flujo de trabajo. + +#### Example using a value in the event payload + +Por ejemplo, si quieres que el flujo de trabajo se ejecute cuando se agrega una etiqueta específica a una propuesta, puedes activar el tipo de actividad de evento `issues labeled` y utilizar una condicional para verificar qué etiqueta activó el flujo de trabajo. El siguiente flujo de trabajo se ejecutará cuando se agregue cualquier etiqueta a una propuesta en su repositorio, pero el job `run_if_label_matches` solo se ejecutará si la etiqueta se nombra `bug`. ```yaml on: @@ -211,7 +215,34 @@ jobs: - run: echo 'The label was bug' ``` -Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". +#### Example using event type + +For example, if you want to run different jobs or steps depending on what event triggered the workflow, you can use a conditional to check whether a specific event type exists in the event context. The following workflow will run whenever an issue or pull request is closed. If the workflow ran because an issue was closed, the `github.event` context will contain a value for `issue` but not for `pull_request`. Therefore, the `if_issue` step will run but the `if_pr` step will not run. Conversely, if the workflow ran because a pull request was closed, the `if_pr` step will run but the `if_issue` step will not run. + +```yaml +on: + issues: + types: + - closed + pull_request: + types: + - closed + +jobs: + state_event_type: + runs-on: ubuntu-latest + steps: + - name: if_issue + if: github.event.issue + run: | + echo An issue was closed + - name: if_pr + if: github.event.pull_request + run: | + echo A pull request was closed +``` + +For more information about what information is available in the event context, see "[Using event information](#using-event-information)." For more information about how to use conditionals, see "[Expressions](/actions/learn-github-actions/expressions)." {% ifversion fpt or ghae or ghes > 3.1 or ghec %} diff --git a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md index 8b277fe2080b..e217e7bb58d8 100644 --- a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md +++ b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md @@ -50,7 +50,7 @@ For more information about the management of policies for your enterprise accoun {% ifversion ghes or ghae %} -From your enterprise account on {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.prodname_ghe_server %} instance{% endif %}, administrators can view enterprise membership and manage the following for the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %}. +From your enterprise account on {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.prodname_ghe_server %} instance{% endif %}, administrators can view{% if remove-enterprise-members %} and manage{% endif %} enterprise membership{% if enterprise-owner-join-org %}, manage their own membership in organizations owned by the enterprise,{% endif %} and manage the following for the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %}. {% ifversion ghes %} - License usage{% endif %} @@ -65,7 +65,7 @@ From your enterprise account on {% ifversion ghae %}{% data variables.product.pr {% endif %} -{% ifversion ghec or ghes %}When you try or purchase {% data variables.product.prodname_enterprise %}, you can{% ifversion ghes %} also{% endif %} create an enterprise account for {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. Administrators for the enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view membership and manage the following for the enterprise account{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. +{% ifversion ghec or ghes %}When you try or purchase {% data variables.product.prodname_enterprise %}, you can{% ifversion ghes %} also{% endif %} create an enterprise account for {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. Administrators for the enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view {% if remove-enterprise-members %} and manage{% endif %} enterprise membership{% if enterprise-owner-join-org %}, manage their own membership in organizations owned by the enterprise,{% endif %} and manage the following for the enterprise account{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. - Billing and usage (services on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, user licenses) - Security (single sign-on, IP allow lists, SSH certificate authorities, two-factor authentication) diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md index 8a20b20a58f6..43ef1bfb0eee 100644 --- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md @@ -25,6 +25,7 @@ children: - /adding-people-to-teams - /viewing-the-audit-logs-for-organizations-in-your-enterprise - /streaming-the-audit-logs-for-organizations-in-your-enterprise-account + - /managing-your-role-in-an-organization-owned-by-your-enterprise - /removing-users-from-teams-and-organizations - /removing-organizations-from-your-enterprise - /restoring-a-deleted-organization diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md new file mode 100644 index 000000000000..7019d7d26ce3 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md @@ -0,0 +1,54 @@ +--- +title: Managing your role in an organization owned by your enterprise +intro: You can manage your membership in any organization owned by your enterprise and change your role within the organization. +permissions: Enterprise owners can manage their role in an organization owned by the enterprise. +versions: + feature: enterprise-owner-join-org +type: how_to +topics: + - Administrator + - Enterprise + - Organizations +shortTitle: Manage your organization roles +--- + +{% note %} + +**Note:** The ability for enterprise owners to manage their role in an organization owned by the enterprise is in beta and subject to change. + +{% endnote %} + +## About role management + +You can choose to join an organization owned by your enterprise as a member or as an organization owner, change your role within the organization, or leave the organization. + +{% warning %} + +**Warning**: If an organization uses SCIM to provision users, joining the organization this way could have unintended consequences. Para obtener más información, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + +{% endwarning %} + +## Managing your role with the enterprise settings + +You can join an organization owned by your enterprise and manage your role within the organization, directly from the settings for your enterprise account. + +If an organization enforces SAML single sign-on (SSO), you cannot use the enterprise settings to join the organization. Instead, you must join the organization using that organization's identity provider (IdP). Then, you can manage your role in your enterprise settings. For more information, see "[Joining an organization that enforces SAML SSO](#joining-an-organization-that-enforces-saml-sso)." + +{% data reusables.enterprise-accounts.access-enterprise %} +1. On the **Organizations** tab, to the right of the organization you want to manage your role in, select the {% octicon "gear" aria-label="The gear icon" %} dropdown menu and click the action you want to take. + + ![Screenshot of the dropdown menu for the gear icon for an organization](/assets/images/help/business-accounts/change-role-in-org.png) + +## Joining an organization that enforces SAML SSO + +If an organization enforces SAML SSO, you cannot use the enterprise settings to join the organization. Instead, you must join the organization using that organization's identity provider (IdP). + +1. You must be assigned access in your IdP to the application for {% data variables.product.prodname_ghe_cloud %} that is used by the organization. If you're unable to configure your IdP yourself, contact your IdP administrator. +1. Authenticate to the organization using SAML SSO. + + - If the organization uses SCIM, accept the organization invitation that will be generated by the SCIM integration. + - If the organization does not use SCIM, visit the following URL, replacing ORGANIZATION with the name of the organization, then follow the prompts to authenticate. + + `https://github.com/orgs/ORGANIZATION/sso` + +After you've joined the organization, you can use the enterprise settings to manage your role in the organization, such as becoming an organization owner. For more information, see "[Managing your role with the enterprise settings](#managing-your-role-with-the-enterprise-settings)." diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md index 4b8443a83452..1aa1b4e0e61c 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md @@ -27,6 +27,7 @@ children: - /viewing-and-managing-a-users-saml-access-to-your-enterprise - /auditing-users-across-your-enterprise - /impersonating-a-user + - /removing-a-member-from-your-enterprise - /managing-dormant-users - /suspending-and-unsuspending-users - /placing-a-legal-hold-on-a-user-or-organization diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md new file mode 100644 index 000000000000..baac07f7a48c --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md @@ -0,0 +1,39 @@ +--- +title: Removing a member from your enterprise +intro: You can remove a member from all organizations owned by your enterprise. +permissions: Enterprise owners can remove an enterprise member from the enterprise. +versions: + feature: remove-enterprise-members +type: how_to +topics: + - Enterprise +shortTitle: Remove member +--- + +{% note %} + +**Note:** The ability to remove enterprise members is in beta and subject to change. + +{% endnote %} + +## About removal of enterprise members + +When you remove an enterprise member from your enterprise, the member is removed from all organizations owned by your enterprise. + +If the enterprise member you're removing is the last owner of an organization owned by your enterprise, you will become an owner of that organization. + +If your enterprise or any of the organizations owned by your enterprise uses an identity provider (IdP) to manage organization membership, the member may be added back to the organization by the IdP. Make sure to also make any necessary changes in your IdP. + +## Removing a member from your enterprise + +{% note %} + +**Note:** If an enterprise member uses only {% data variables.product.prodname_ghe_server %}, and not {% data variables.product.prodname_ghe_cloud %}, you cannot remove the enterprise member this way. + +{% endnote %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +1. To the right of the person you want to remove, select the {% octicon "gear" aria-label="The gear icon" %} dropdown menu and click **Remove from enterprise**. + + ![Screenshot of the "Remove from enterprise" option for an enterprise member](/assets/images/help/business-accounts/remove-member.png) diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md index 63653d566a41..896f06aa9c19 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -30,16 +30,23 @@ Para obtener más información acerca de cómo agregar personas a tu empresa, co {% endif %} -## Propietario de empresa +## Enterprise owners Los propietarios de las empresas tienen el control absoluto de las mismas y pueden tomar todas las acciones, incluyendo: - Gestionar administradores -- {% ifversion ghec %}Agregar y eliminar {% elsif ghae or ghes %}Administrar{% endif %} organizaciones{% ifversion ghec %}to and from {% elsif ghae or ghes %} en{% endif %} la empresa +- {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise{% if remove-enterprise-members %} +- Removing enterprise members from all organizations owned by the enterprise{% endif %} - Administrar parámetros de la empresa - Aplicar políticas en las organizaciones {% ifversion ghec %}- Administrar la configuración de facturación{% endif %} +{% if enterprise-owner-join-org %} +Enterprise owners do not have access to organization settings or content by default. To gain access, enterprise owners can join any organization owned by their enterprise. 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)." + +Owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. +{% else %} Los propietarios de empresa no pueden acceder a los parámetros o el contenido de la organización, a menos que se conviertan en propietarios de la organización o que se les otorgue acceso directo al repositorio que le pertenece a una organización. De forma similar, los propietarios de las organizaciones en tu empresa no tienen acceso a la empresa misma a menos de que los conviertas en propietarios de ella. +{% endif %} Un propietario de la empresa solo consumirá una licencia si son propietarios o miembros de por lo menos una organización dentro de la emrpesa. Incluso si un propietario de empresa tiene un rol en varias organizaciones, consumirán una sola licencia. {% ifversion ghec %}Los propietrios de la empresa deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}.{% endif %} Como mejor práctica, te recomendamos que solo algunas personas en tu compañía se conviertan en propietarios, para reducir el riesgo en tu negocio. @@ -55,7 +62,7 @@ Las personas con acceso de colaborador externo a los repositorios que pertenecen {% ifversion ghec %} -## Gerente de facturación +## Gerentes de facturación Los gerentes de facturación solo tienen acceso a la configuración de facturación de tu empresa. Los gerentes de facturación de tu empresa pueden: - Ver y administrar las licencias de usuario, {% data variables.large_files.product_name_short %} los paquetes y otros parámetros de facturación diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index 1db95024d683..88c73a58db0c 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -55,6 +55,12 @@ Para mayor seguridad, habilita la autenticación de dos factores además de camb Consulta "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)" para recibir indicaciones sobre revisar y eliminar tokens de acceso. Para generar tokens de acceso nuevos, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". +{% ifversion not ghae %} + +If you have reset your account password and would also like to trigger a sign-out from the GitHub Mobile app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." + +{% endif %} + ## Actualizar tus claves SSH Consulta "[Revisar tus claves SSH](/articles/reviewing-your-ssh-keys)" para obtener indicaciones sobre la revisar y eliminar claves SSH. Para generar y agregar claves SSH nuevas, consulta "[Generar una clave SSH](/articles/generating-an-ssh-key)". diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md b/translations/es-ES/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md index 54b1468a6798..a42ba15f7b9b 100644 --- a/translations/es-ES/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md +++ b/translations/es-ES/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md @@ -15,9 +15,9 @@ topics: shortTitle: Permiso denegado (publickey) --- -## ¿El comando `sudo` se debe usar con Git? +## Should the `sudo` command or elevated privileges be used with Git? -No deberías estar usando el comando `sudo` con Git. Si tienes una *muy buena razón* para usar `sudo`, asegúrate de estar usándolo con todos los comandos (probablemente es mejor que uses `su` para obtener un shell como raíz en este punto). Si [generas claves SSH](/articles/generating-an-ssh-key) sin `sudo` y luego intentas usar un comando como `sudo git push`, no estarás usando las mismas claves que generaste. +You should not be using the `sudo` command or elevated privileges, such as administrator permissions, with Git. Si tienes una *muy buena razón* para usar `sudo`, asegúrate de estar usándolo con todos los comandos (probablemente es mejor que uses `su` para obtener un shell como raíz en este punto). Si [generas claves SSH](/articles/generating-an-ssh-key) sin `sudo` y luego intentas usar un comando como `sudo git push`, no estarás usando las mismas claves que generaste. ## Verifica si estás conectado al servidor correcto 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 b09f76140214..cf338bf0ad91 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 @@ -64,6 +64,9 @@ The dependency graph allows you to explore the ecosystems and packages that your You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} +### Security overview for repositories +For all public repositories, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features that are not currently enabled. + ## Available with {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.ghas-availability %} @@ -84,8 +87,8 @@ Automatically detect tokens or credentials that have been checked into a reposit Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -{% ifversion ghec or ghes > 3.1 %} -### Security overview +{% ifversion ghec or ghes > 3.1 or ghae-issue-4554 %} +### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, 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)." {% endif %} 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 620562769081..1997a6f55d71 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 @@ -26,11 +26,7 @@ shortTitle: Acerca del resumen de seguridad ## Acerca del resumen de seguridad -Puedes utilizar el resumen de seguirdad para tener una vista de nivel alto del estado de seguridad de tu organización o para identificar repositorios problemáticos que requieren intervención. - -- A nivel organizacional, el resumen de seguridad muestra seguridad agregada y específica del repositorio para aquellos que pertenezcan a tu organización. También puedes filtrar la información de acuerdo con la característica de seguridad. -- A nivel de equipo, el resumen de seguridad muestra la información de seguridad específica del repositorio para aquellos en los que el equipo tenga privilegios de administración. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". -- En el nivel del repositorio, el resumen de seguridad muestra qué características de seguridad se encuentran habilitadas para este y ofrece la opción de configurar cualquier característica de seguridad disponible que no se esté utilizando actualmente. +Puedes utilizar el resumen de seguirdad para tener una vista de nivel alto del estado de seguridad de tu organización o para identificar repositorios problemáticos que requieren intervención. You can view aggregate or repository-specific security information in the security overview. You can also use the security overview to see which which security features are enabled for your repositories and to configure any available security features that are not currently in use. El resumen de seguridad indica si se encuentran habilitadas las características de {% ifversion fpt or ghes > 3.1 or ghec %}seguridad{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} para los repositorios que pertenecen a tu organización y consolida las alertas para cada característica.{% ifversion fpt or ghes > 3.1 or ghec %} Las características de seguridad incluyen aquellas de {% data variables.product.prodname_GH_advanced_security %}, como el {% data variables.product.prodname_code_scanning %} y el {% data variables.product.prodname_secret_scanning %}, así como las {% data variables.product.prodname_dependabot_alerts %}.{% endif %} Para obtener más información sobre las características de la {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)".{% ifversion fpt or ghes > 3.1 or ghec %} Para obtener más información sobre las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)".{% endif %} @@ -63,3 +59,24 @@ Para cada repositorio en el resumen de seguridad, verás iconos de cada tipo de | {% octicon "x" aria-label="x" %} | La característica de seguridad no es compatible con este repositorio. | El resumen de seguridad muestra alertas activas que levantan las características de seguridad. Si no hay alertas en el resumen de seguridad de un repositorio, las vulnerabilidades de seguridad no detectadas o los errores de código podrían aún existir. + +### About the organization-level security overview + +A nivel organizacional, el resumen de seguridad muestra seguridad agregada y específica del repositorio para aquellos que pertenezcan a tu organización. You can filter information by security features at the organization-level. + +{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} +### 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 or view all {% data variables.product.prodname_secret_scanning %} alerts from across your enterprise. + +Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to. + +{% 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. +{% endif %} + +### About the team-level security overview +A nivel de equipo, el resumen de seguridad muestra la información de seguridad específica del repositorio para aquellos en los que el equipo tenga privilegios de administración. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". + +### About the repository-level security overview +At the repository-level, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features that are not currently enabled. 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 c7efd3961497..9f2ffae308de 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 @@ -36,6 +36,13 @@ shortTitle: View the 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. Opcionalmente, filtra la lista de alertas. Cada vista tiene su propia selección de filtros disponibles. Puedes hacer clic en varios filtros de los menús desplegables de filtros para especificar tu búsqueda. También puedes teclear calificadores de búsqueda en el campo de búsqueda. Para obtener más información sobre los calificadores disponibles, consulta la sección "[Filtrar las alertas en el resumen de seguridad](/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) +{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} +## Viewing the security overview for an enterprise + +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Security**. +{% endif %} + ## Viewing alerts for a repository {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md new file mode 100644 index 000000000000..f9ea9891fd09 --- /dev/null +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md @@ -0,0 +1,34 @@ +--- +title: Creating a branch to work on an issue +intro: You can create a branch to work on an issue directly from the issue page and get started right away. +versions: + fpt: '*' + ghes: '>=3.5' + ghae: issue-6234 + ghec: '*' +allowTitleToDifferFromFilename: true +topics: + - Issues +shortTitle: Create branch for issue +--- + +{% note %} + +**Note:** The ability to create a branch for an issue is currently in public beta and subject to change. + +{% endnote %} + +## About branches connected to an issue +Branches connected to an issue are shown under the "Development" section in the sidebar of an issue. When you create a pull request for one of these branches, it is automatically linked to the issue. The connection with that branch is removed and only the pull request is shown in the "Development" section. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)". + +## Creating a branch for an issue + +Anyone with write permission to a repository can create a branch for an issue. You can link multiple branches for an issue. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +3. In the list of issues, click the issue that you would like to create a branch for. +4. In the right sidebar under "Development", click **Create a branch**. If the issue already has a linked branch or pull request, click {% octicon "gear" aria-label="The Gear icon" %} and at the bottom of the drop-down menu click **Create a branch**. ![Screenshot showing Create a branch option highlighted in sidebar](/assets/images/help/issues/create-a-branch.png) +5. By default, the new branch is created in the current repository from the default branch. Edit the branch name and details as required in the "Create a branch for this issue" dialog. ![Screenshot showing Create a branch dialog options](/assets/images/help/issues/create-a-branch-options.png) +6. Choose whether to work on the branch locally or to open it in GitHub Desktop. +7. When you are ready to create the branch, click **Create branch**. 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 6602f1f9d06f..66725cb89b9d 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 @@ -15,6 +15,7 @@ children: - /creating-an-issue - /about-task-lists - /linking-a-pull-request-to-an-issue + - /creating-a-branch-for-an-issue - /assigning-issues-and-pull-requests-to-other-github-users - /viewing-all-of-your-issues-and-pull-requests - /filtering-and-searching-issues-and-pull-requests diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 8eca5faf19d0..a9afba1623d9 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -71,8 +71,12 @@ You can manually link up to ten issues to each pull request. The issue and pull {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} 3. In the list of pull requests, click the pull request that you'd like to link to an issue. +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6234 %} +4. In the right sidebar, in the "Development" section click {% octicon "gear" aria-label="The Gear icon" %}. +{% else %} 4. In the right sidebar, click **Linked issues**. ![Linked issues in the right sidebar](/assets/images/help/pull_requests/linked-issues.png) +{% endif %} 5. Click the issue you want to link to the pull request. ![Drop down to link issue](/assets/images/help/pull_requests/link-issue-drop-down.png) {% endif %} diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 4371232ae777..99c14b100765 100644 --- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -13,10 +13,9 @@ topics: - Organizations - Teams shortTitle: Eliminar a un miembro +permissions: Organization owners can remove members from an organization. --- -Solo los propietarios de la organización pueden eliminar usuarios de una organización. - {% ifversion fpt or ghec %} {% warning %} @@ -63,4 +62,5 @@ Para ayudar con la transición de la persona que estás eliminando de tu organiz ## Leer más -- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)" +- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"{% if remove-enterprise-members %} +- "[Removing a member from your enterprise](/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise)"{% endif %} diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md index 611d2cbd6f1c..0165c96d3c03 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -31,6 +31,10 @@ Los propietarios de una organización tienen acceso administrativo completo a la {% endnote %} +{% if enterprise-owner-join-org %} +If your organization is owned by an enterprise account, any enterprise owner can make themself an owner of your organization. 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 %} + ## Designar un propietario de organización {% data reusables.profile.access_org %} diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 316885514ee4..d94ef979fe9e 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -29,6 +29,10 @@ Organization-level roles are sets of permissions that can be assigned to individ You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "[Permissions for organization roles](#permissions-for-organization-roles)." +{% if enterprise-owner-join-org %} +If your organization is owned by an enterprise account, enterprise owners can choose to join your organization with any role. 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 %} + ### Organization owners Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index ad92e749fc02..509ac6b663e1 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -28,11 +28,10 @@ Estos proveedores de identidad son compatibles con la API de SCIM de {% data var {% endnote %} +{% data reusables.scim.changes-should-come-from-idp %} + {% data reusables.scim.enterprise-account-scim %} ## Leer más -- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[Conectar tu proveedor de identidad a tu organización](/articles/connecting-your-identity-provider-to-your-organization)" -- "[Activar y probar el inicio de sesión único de SAML para tu organización](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" - "[Visualizar y administrar un acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md index 856bc7d9bf44..970fadc02482 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md @@ -11,7 +11,11 @@ shortTitle: Troubleshooting access ## Some users are not provisioned or deprovisioned by SCIM -When you encounter provisioning issues with users, we recommend that you check if the users are missing SCIM metadata. If an organization member has missing SCIM metadata, then you can re-provision SCIM for the user manually through your IdP. +When you encounter provisioning issues with users, we recommend that you check if the users are missing SCIM metadata. + +{% data reusables.scim.changes-should-come-from-idp %} + +If an organization member has missing SCIM metadata, then you can re-provision SCIM for the user manually through your IdP. ### Auditing users for missing SCIM metadata @@ -78,7 +82,7 @@ For more information on using the GraphQL API, see: ### Re-provisioning SCIM for users through your identity provider -You can re-provision SCIM for users manually through your IdP. For example, to resolve provisioning errors, in the Okta admin portal, you can unassign and reassign users to the {% data variables.product.prodname_dotcom %} app. This should trigger Okta to make an API call to populate the SCIM metadata for these users on {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Desasignar a los usuarios de las aplicaciones](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-unassign-apps.htm)" o "[Asignar a los usuarios a las aplicaciones](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm)" en la documentación de Okta. +You can re-provision SCIM for users manually through your IdP. For example, to resolve provisioning errors for Okta, in the Okta admin portal, you can unassign and reassign users to the {% data variables.product.prodname_dotcom %} app. This should trigger Okta to make an API call to populate the SCIM metadata for these users on {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Desasignar a los usuarios de las aplicaciones](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-unassign-apps.htm)" o "[Asignar a los usuarios a las aplicaciones](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm)" en la documentación de Okta. To confirm that a user's SCIM identity is created, we recommend testing this process with a single organization member whom you have confirmed doesn't have a SCIM external identity. After manually updating the users in your IdP, you can check if the user's SCIM identity was created using the SCIM API or on {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Auditar usuarios para los metadatos de SCIM no presentes](#auditing-users-for-missing-scim-metadata)" o la terminal de la API de REST "[Obtener información de aprovisionamiento de SCIM para un usuario](/rest/reference/scim#get-scim-provisioning-information-for-a-user)". diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index ea4610c2fc75..f1fecbd82ad3 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -28,6 +28,18 @@ permissions: People with write access for a forked repository can sync the fork If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. +## Syncing a fork with the {% data variables.product.prodname_cli %} + +{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." + +To update the remote fork from its parent, use the `gh repo sync` subcommand and supply your fork name as argument. + +```shell +$ gh repo sync owner/cli-fork +``` + +If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. + ## Syncing a fork from the command line {% endif %} diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 4447bf7fac96..8770d005edf6 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -68,7 +68,7 @@ When you create a branch rule, the branch you specify doesn't have to exist yet - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements. + - Optionally, to allow specific people or teams to push code to the branch without creating pull requests when they're required, select **Allow specific actors to bypass required pull requests**. Then, search for and select the people or teams who should be allowed to skip creating a pull request. ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png) {% endif %} - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." diff --git a/translations/es-ES/data/features/enterprise-owner-join-org.yml b/translations/es-ES/data/features/enterprise-owner-join-org.yml new file mode 100644 index 000000000000..847a54f8b56d --- /dev/null +++ b/translations/es-ES/data/features/enterprise-owner-join-org.yml @@ -0,0 +1,5 @@ +--- +versions: + ghec: '*' + ghes: '>=3.5' + ghae: 'issue-5740' diff --git a/translations/es-ES/data/features/remove-enterprise-members.yml b/translations/es-ES/data/features/remove-enterprise-members.yml new file mode 100644 index 000000000000..a9ef5be6d690 --- /dev/null +++ b/translations/es-ES/data/features/remove-enterprise-members.yml @@ -0,0 +1,5 @@ +--- +versions: + ghec: '*' + ghes: '>=3.5' + ghae: 'issue-5739' diff --git a/translations/es-ES/data/reusables/scim/changes-should-come-from-idp.md b/translations/es-ES/data/reusables/scim/changes-should-come-from-idp.md new file mode 100644 index 000000000000..d6b8dee0d999 --- /dev/null +++ b/translations/es-ES/data/reusables/scim/changes-should-come-from-idp.md @@ -0,0 +1 @@ +If SCIM provisioning is implemented for your organization, any changes to a user's organization membership should be triggered from the identity provider. If a user is invited to an organization manually instead of by an existing SCIM integration, their user account may not get properly linked to their SCIM identity. This can prevent the user account from being deprovisioned via SCIM in the future. If a user is removed manually instead of by an existing SCIM integration, a stale linked identity will remain, which can lead to issues if the user needs to re-join the organization. diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml index a835c13cf07f..c4771ad88c3f 100644 --- a/translations/es-ES/data/ui.yml +++ b/translations/es-ES/data/ui.yml @@ -94,6 +94,11 @@ products: deprecation_notice: Aviso de depreciación rest: reference: + default: Predeterminado + name: Nombre + in: In + type: Tipo + description: Descripción notes: Notas parameters: Parámetros response: Respuesta @@ -104,6 +109,7 @@ products: see_preview_notice: Ver aviso de previsualización see_preview_notices: Ver avisos de previsualización preview_header_is_required: El encabezado es requerido + preview_notice_to_change: This API is under preview and subject to change works_with_github_apps: Works with GitHub Apps footer: all_rights_reserved: Todos los derechos reservados