Octomerger Bot
@@ -66,24 +66,35 @@ The custom label is created and assigned to the self-hosted runner. Custom label
|
||||
1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.actions.actions-unused-labels %}
|
||||
{% endif %}
|
||||
|
||||
## Using the configuration script to create and assign labels
|
||||
## Programmatically assign labels
|
||||
|
||||
You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner.
|
||||
You can programmatically assign labels to a self-hosted runner after the runner is created, or during its initial configuration.
|
||||
|
||||
```shell
|
||||
./config.sh --labels gpu
|
||||
```
|
||||
* To programmatically assign labels to an existing self-hosted runner, you must use the REST API. For more information, see the "[Self-hosted runners](/rest/actions/self-hosted-runners)" REST API.
|
||||
* To programmatically assign labels to a self-hosted runner during the initial runner configuration, you can pass label names to the `config` script using the `labels` parameter.
|
||||
|
||||
The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
|
||||
{% note %}
|
||||
|
||||
**Note:** You cannot use the `config` script to assign labels to an existing self-hosted runner.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use comma separation to assign multiple labels. For example:
|
||||
For example, this command assigns a label named `gpu` when configuring a new self-hosted runner:
|
||||
|
||||
```shell
|
||||
./config.sh --labels gpu,x64,linux
|
||||
```
|
||||
```
|
||||
./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu
|
||||
```
|
||||
|
||||
{% note %}
|
||||
The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
|
||||
|
||||
** Note:** If you replace an existing runner, then you must reassign any custom labels.
|
||||
You can use comma separation to assign multiple labels. For example:
|
||||
|
||||
{% endnote %}
|
||||
```
|
||||
./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu,x64,linux
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
** Note:** If you replace an existing runner, then you must reassign any custom labels.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -16,12 +16,12 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
ms.openlocfilehash: 69853702258a6a0acaa3501e007c8c20a52874d5
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: b34a96bb62a885031584f3da017fd86b7469a277
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106889'
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160836'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -570,6 +570,8 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro
|
||||
|
||||
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.
|
||||
|
||||
La mayoría de los comandos de los ejemplos siguientes usan comillas dobles para las cadenas de eco, que intentarán interpolar caracteres como `$` para nombres de variables de shell. Para usar siempre valores literales en cadenas entre comillas, puedes usar comillas simples en su lugar.
|
||||
|
||||
{% powershell %}
|
||||
|
||||
{% note %}
|
||||
@@ -696,7 +698,7 @@ steps:
|
||||
id: step_one
|
||||
run: |
|
||||
echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
|
||||
curl https://example.lab >> $GITHUB_ENV
|
||||
curl https://example.com >> $GITHUB_ENV
|
||||
echo 'EOF' >> $GITHUB_ENV
|
||||
```
|
||||
|
||||
@@ -710,7 +712,7 @@ steps:
|
||||
id: step_one
|
||||
run: |
|
||||
"JSON_RESPONSE<<EOF" >> $env:GITHUB_ENV
|
||||
(Invoke-WebRequest -Uri "https://example.lab").Content >> $env:GITHUB_ENV
|
||||
(Invoke-WebRequest -Uri "https://example.com").Content >> $env:GITHUB_ENV
|
||||
"EOF" >> $env:GITHUB_ENV
|
||||
shell: pwsh
|
||||
```
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Network ports
|
||||
title: Puertos de red
|
||||
redirect_from:
|
||||
- /enterprise/admin/articles/configuring-firewalls
|
||||
- /enterprise/admin/articles/firewall
|
||||
@@ -8,7 +8,7 @@ redirect_from:
|
||||
- /enterprise/admin/installation/network-ports
|
||||
- /enterprise/admin/configuration/network-ports
|
||||
- /admin/configuration/network-ports
|
||||
intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
|
||||
intro: 'Abre los puertos de red de forma selectiva en base a los servicios de red que necesitas exponer a los administradores, usuarios finales y apoyo de correo electrónico.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
type: reference
|
||||
@@ -17,56 +17,62 @@ topics:
|
||||
- Infrastructure
|
||||
- Networking
|
||||
- Security
|
||||
ms.openlocfilehash: 048b27ed44cea11057c781ae3043078a825f8d1a
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160660'
|
||||
---
|
||||
## Administrative ports
|
||||
## Puertos administrativos
|
||||
|
||||
Some administrative ports are required to configure {% data variables.location.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
|
||||
En algunos puertos administrativos es necesario configurar {% data variables.location.product_location %} y ejecutar determinadas funciones. No se requieren puertos administrativos para el uso de la aplicación básica por parte de los usuarios finales.
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | Servicio | Descripción |
|
||||
|---|---|---|
|
||||
| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
|
||||
| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless TLS is disabled manually. |
|
||||
| 122 | SSH | Shell access for {% data variables.location.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
|
||||
| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
|
||||
| 123/UDP| NTP | Required for time protocol operation. |
|
||||
| 161/UDP | SNMP | Required for network monitoring protocol operation. |
|
||||
| 8443 | HTTPS | {% data variables.enterprise.management_console %} segura basada en la web. Necesario para la instalación y la configuración básicas. |
|
||||
| 8080 | HTTP | {% data variables.enterprise.management_console %} basada en la web de texto simple. No se requiere a menos de que el TLS se inhabilite manualmente. |
|
||||
| 122 | SSH | Acceso de shell para {% data variables.location.product_location %}. Se necesita abierto a las conexiones entrantes entre todos los nodos en una configuración de disponibilidad alta. El puerto SSH predeterminado (22) está destinado al tráfico de red de la aplicación SSH y Git. |
|
||||
| 1194/UDP | VPN | Túnel de red de replicación segura en la configuración de alta disponibilidad. Se requiere abierto a las comunicaciones entre todos los nodos en la configuración.|
|
||||
| 123/UDP| NTP | Se requiere para operar el protocolo de tiempo. |
|
||||
| 161/UDP | SNMP | Se requiere para operar el protocolo de revisión de red. |
|
||||
|
||||
## Application ports for end users
|
||||
## Puertos de la aplicación para usuarios finales
|
||||
|
||||
Application ports provide web application and Git access for end users.
|
||||
Los puertos de la aplicación permiten que los usuarios finales accedan a Git y a las aplicaciones web.
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | Servicio | Descripción |
|
||||
|---|---|---|
|
||||
| 443 | HTTPS | Access to the web application and Git over HTTPS. |
|
||||
| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port if TLS is configured. |
|
||||
| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
|
||||
| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
|
||||
| 443 | HTTPS | Acceso a la aplicación web y a Git por HTTPS. |
|
||||
| 80 | HTTP | Acceso a la aplicación web. Todas las solicitudes se redirigen al puerto HTTPS si se configura el TLS. |
|
||||
| 22 | SSH | Acceso a Git por SSH. Admite las operaciones clonar, extraer y subir a los repositorios privados y públicos. |
|
||||
| 9418 | Git | El puerto de protocolo Git admite las operaciones clonar y extraer a los repositorios públicos con comunicación de red desencriptada. {% data reusables.enterprise_installation.when-9418-necessary %} |
|
||||
|
||||
{% data reusables.enterprise_installation.terminating-tls %}
|
||||
|
||||
## Email ports
|
||||
## Puertos de correo electrónico
|
||||
|
||||
Email ports must be accessible directly or via relay for inbound email support for end users.
|
||||
Los puertos de correo electrónico deben ser accesibles directamente o por medio de la retransmisión del correo electrónico entrante para los usuarios finales.
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | Servicio | Descripción |
|
||||
|---|---|---|
|
||||
| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
|
||||
| 25 | SMTP | Soporte para SMTP con encriptación (STARTTLS). |
|
||||
|
||||
## {% data variables.product.prodname_actions %} ports
|
||||
## Puertos de las {% data variables.product.prodname_actions %}
|
||||
|
||||
{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.location.product_location %}. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)."
|
||||
Los puertos de las {% data variables.product.prodname_actions %} deben ser accesibles para que los ejecutores auto-hospedados se conecten a {% data variables.location.product_location %}. Para más información, consulte [Seguridad del ejecutor autohospedado con repositorios públicos](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server).
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | Servicio | Descripción |
|
||||
|---|---|---|
|
||||
| 443 | HTTPS | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is configured.
|
||||
| 80 | HTTP | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured.
|
||||
| 443 | HTTPS | Los ejecutores auto-hospedados se conectan a {% data variables.location.product_location %} para recibir asignaciones de jobs y para descargar versiones nuevas de la aplicación ejecutora. Requerido si se configura TLS.
|
||||
| 80 | HTTP | Los ejecutores auto-hospedados se conectan a {% data variables.location.product_location %} para recibir asignaciones de jobs y para descargar versiones nuevas de la aplicación ejecutora. Requerido si no se configura TLS.
|
||||
|
||||
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)."
|
||||
Si habilitas el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_actions %} siempre buscará primero una acción en {% data variables.location.product_location %}, a través de estos puertos, antes de revisar en {% 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/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
|
||||
## puertos {% data variables.product.prodname_github_connect %}
|
||||
|
||||
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)."
|
||||
Si habilita los datos {% data variables.product.prodname_github_connect %}, la conexión entre los datos {% data variables.product.product_name %} y {% data variables.product.prodname_dotcom_the_website %} usa HTTPS a través de los puertos 443 o 80 y se requiere TLS. Para más información, vea "[Acerca de {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)"
|
||||
- "[Configuración de TLS](/admin/configuration/configuring-network-settings/configuring-tls)"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Acerca de la autenticación para tu empresa
|
||||
title: About authentication for your enterprise
|
||||
shortTitle: About authentication
|
||||
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 %}.'
|
||||
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 %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
@@ -13,140 +13,136 @@ 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'
|
||||
---
|
||||
## Acerca de la autenticación para tu empresa
|
||||
|
||||
## About authentication for your enterprise
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
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.
|
||||
Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources.
|
||||
|
||||
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.
|
||||
{% data reusables.enterprise.ghec-authentication-options %}
|
||||
|
||||
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)".
|
||||
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)."
|
||||
|
||||
## Métodos de autenticación para {% data variables.product.product_name %}
|
||||
## Authentication methods for {% 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 %}.
|
||||
The following options are available for account management and authentication on {% data variables.product.product_name %}.
|
||||
|
||||
- [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 %}](#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 {% 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 %}.
|
||||
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 %}.
|
||||
|
||||
### Autenticación a través de {% data variables.location.product_location %} con restricción de acceso SAML adicional
|
||||
### Authentication through {% data variables.location.product_location %} with additional SAML access restriction
|
||||
|
||||
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 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 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)".
|
||||
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)."
|
||||
|
||||
### Autenticación con {% data variables.product.prodname_emus %} y federación
|
||||
### Authentication with {% data variables.product.prodname_emus %} and federation
|
||||
|
||||
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)".
|
||||
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)."
|
||||
|
||||
## Identificación del mejor método de autenticación para la empresa
|
||||
## Identifying the best authentication method for your enterprise
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions.
|
||||
|
||||
- [¿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?](#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?
|
||||
|
||||
{% 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.
|
||||
{% 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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
### ¿Qué proveedor de identidades usa tu empresa?
|
||||
### Which identity provider does your enterprise use?
|
||||
|
||||
{% 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)".
|
||||
{% 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)."
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
### ¿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 {% data variables.product.prodname_pages %} sites?
|
||||
|
||||
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)".
|
||||
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)."
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
### ¿Los desarrolladores se basan en colaboraciones fuera de la empresa?
|
||||
### Do your developers rely on collaboration outside of your enterprise?
|
||||
|
||||
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.
|
||||
{% 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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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)".
|
||||
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)."
|
||||
|
||||
### ¿La empresa depende de colaboradores externos?
|
||||
### Does your enterprise rely on outside collaborators?
|
||||
|
||||
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 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 {% 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.
|
||||
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.
|
||||
|
||||
### ¿Puede la empresa tolerar costes de migración?
|
||||
### Can your enterprise tolerate migration costs?
|
||||
|
||||
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 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 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)".
|
||||
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)."
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
## Métodos de autenticación para {% data variables.product.product_name %}
|
||||
## Authentication methods for {% data variables.product.product_name %}
|
||||
|
||||
Los siguientes métodos de autenticación están disponibles para {% data variables.product.product_name %}.
|
||||
The following authentication methods are available for {% data variables.product.product_name %}.
|
||||
|
||||
- [Autenticación integrada](#built-in-authentication)
|
||||
- [Autenticación externa](#external-authentication)
|
||||
- [Built-in authentication](#built-in-authentication)
|
||||
- [External authentication](#external-authentication)
|
||||
|
||||
### Autenticación integrada
|
||||
### 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)".
|
||||
{% 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)."
|
||||
|
||||
### Autenticación externa
|
||||
### External authentication
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
- "[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)"
|
||||
- "[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)"
|
||||
|
||||
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)".
|
||||
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)."
|
||||
|
||||
{% ifversion scim-for-ghes %}
|
||||
|
||||
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)".
|
||||
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)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% 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)".
|
||||
{% 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)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[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)"
|
||||
- "[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)"
|
||||
{% endif %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring SCIM provisioning for Enterprise Managed Users with Okta
|
||||
title: Configurar el aprovisionamiento de SCIM para los Usuarios Administrados Empresariales con Okta
|
||||
shortTitle: Set up provisioning with Okta
|
||||
intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider.
|
||||
intro: Puedes aprovisionar usuarios nuevos y administrar la membrecía de tu empresa y equipos utilizando Okta como tu proveedor de identidad.
|
||||
product: '{% data reusables.gated-features.emus %}'
|
||||
versions:
|
||||
ghec: '*'
|
||||
@@ -17,81 +17,86 @@ topics:
|
||||
- Authentication
|
||||
- Enterprise
|
||||
- SSO
|
||||
ms.openlocfilehash: b8c086d1d91c1248fa5a0349bb6f8ef32c3bbdf0
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160716'
|
||||
---
|
||||
## Acerca del aprovisionamiento con Okta
|
||||
|
||||
## About provisioning with Okta
|
||||
Puedes utilizar los {% data variables.product.prodname_emus %} con Okta como tu proveedor de identidad para aprovisionar cuentas nuevas, administrar la membrecía empresarial y administrar las membrecías de equipo para las organizaciones de tu empresa. Para obtener más información sobre el aprovisionamiento de {% data variables.product.prodname_emus %}, vea "[Configurar el aprovisionamiento de SCIM para usuarios administrados de la empresa](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)".
|
||||
|
||||
You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, 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)."
|
||||
Antes de que puedas configurar el aprovisionamiento con Okta, debes configurar el inicio de sesión único de SAML. Para obtener más información, vea "[Configurar el inicio de sesión único de SAML para usuarios administrados de la empresa](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)".
|
||||
|
||||
Before you can configure provisioning with Okta, you must configure SAML single-sign on. 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)."
|
||||
Para configurar el aprovisionamiento con Okta, debes configurar el nombre de tu empresa en la aplicación de {% data variables.product.prodname_emu_idp_application %} e ingresar {% data variables.product.pat_generic %}. Entonces podrás aprovisionar usuarios en Okta.
|
||||
|
||||
To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's {% data variables.product.pat_generic %}. You can then start provisioning users in Okta.
|
||||
## Características admitidas
|
||||
|
||||
## Supported features
|
||||
{% data variables.product.prodname_emus %} es compatible con muchas características de aprovisionamiento en Okta.
|
||||
|
||||
{% data variables.product.prodname_emus %} supports many provisioning features in Okta.
|
||||
|
||||
| Feature | Description |
|
||||
| Característica | Descripción |
|
||||
| --- | --- |
|
||||
| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. |
|
||||
| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. |
|
||||
| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. |
|
||||
| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. |
|
||||
| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. |
|
||||
| Subir Usuarios Nuevos | Los usuarios que se asignan a la aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta se crean automáticamente en la empresa en {% data variables.product.product_name %}. |
|
||||
| Subir la Actualización de Perfil | Las actualizaciones que se hacen al perfil del usuario en Oktan se subirán a {% data variables.product.product_name %}. |
|
||||
| Grupos de Subida | Los Grupos en Okta que se hayan asignado a la aplicación de {% data variables.product.prodname_emu_idp_application %} como Grupos de Subida se crearán automáticamente en la empresa en {% data variables.product.product_name %}. |
|
||||
| Subir Desactivaciones de Usuarios | El desasignar al usuario de la aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta lo inhabilitará en {% data variables.product.product_name %}. El usuario no podrá iniciar sesión, pero la información del usuario se mantendrá. |
|
||||
| Reactivar Usuarios | Se habilitarán los usuarios en Okta cuyas cuentas de Okta se reactiven y quienes se asignen de vuelta a la aplicación de {% data variables.product.prodname_emu_idp_application %}. |
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames.
|
||||
**Nota**: {% data variables.product.prodname_emus %} no admite modificaciones en los nombres de usuario.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Setting your enterprise name
|
||||
## Configurar el nombre de tu empresa
|
||||
|
||||
After your {% data variables.enterprise.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta.
|
||||
Después de que se haya creado tu {% data variables.enterprise.prodname_emu_enterprise %}, puedes comenzar a configurar el aprovisionamiento configurando el nombre de tu empresa en Okta.
|
||||
|
||||
1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
|
||||
1. Click the **Sign On** tab.
|
||||
1. To make changes, click **Edit**.
|
||||
1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc".
|
||||
|
||||
1. To save your enterprise name, click **Save**.
|
||||
1. Navega a tu aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta.
|
||||
1. Haga clic en la pestaña **Sign On** (Iniciar sesión).
|
||||
1. Haga clic en **Edit** (Editar) para realizar cambios.
|
||||
1. Debajo de "Ajustes avanzados de inicio de sesión", en la caja de texto de "Nombre de empresa", teclea el nombre de tu empresa. Por ejemplo, si accede a la empresa en `https://github.com/enterprises/octoinc`, el nombre de la empresa sería "octoinc".
|
||||
|
||||
1. Para guardar el nombre de la empresa, haga clic en **Save** (Guardar).
|
||||
|
||||
## Configuring provisioning
|
||||
## Configurar el aprovisionamiento
|
||||
|
||||
After setting your enterprise name, you can proceed to configure provisioning settings.
|
||||
Después de que configures el nombre de tu empresa, puedes proceder a configurar los ajustes de aprovisionamiento.
|
||||
|
||||
To configure provisioning, the setup user with the **@<em>SHORT-CODE</em>_admin** username will need to provide a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)."
|
||||
Para configurar el aprovisionamiento, el usuario de configuración con el nombre de usuario **@<em>SHORT-CODE</em>_admin** deberá proporcionar un {% data variables.product.pat_v1 %} con el ámbito **admin:enterprise**. Para obtener más información sobre cómo crear un nuevo token, consulta "[Creación de un {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)".
|
||||
|
||||
1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
|
||||
1. Click the **Provisioning** tab.
|
||||
1. In the settings menu, click **Integration**.
|
||||
1. To make changes, click **Edit**.
|
||||
1. Select **Enable API integration**.
|
||||
1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user.
|
||||
|
||||
1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen.
|
||||
1. To save the token, click **Save**.
|
||||
1. In the settings menu, click **To App**.
|
||||
|
||||
1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**.
|
||||
1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**.
|
||||
|
||||
1. To finish configuring provisioning, click **Save**.
|
||||
1. Navega a tu aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta.
|
||||
1. Haga clic en el **Provisioning** ficha.
|
||||
1. En el menú de configuración, haga clic en **Integration** (Integración).
|
||||
1. Haga clic en **Edit** (Editar) para realizar cambios.
|
||||
1. Seleccione **Enable API integration** (Habilitar la integración de la API).
|
||||
1. En el campo "API Token" (Token de la API), escriba el {% data variables.product.pat_v1 %} con el ámbito **admin:enterprise** que pertenece al usuario de configuración.
|
||||
|
||||
1. Haga clic en **Test API Credentials** (Probar credenciales de API). Si la prueba tiene éxito, se mostrará un mensaje de verificación en la parte superior de la pantalla.
|
||||
1. Para guardar el token, haga clic en **Save** (Guardar).
|
||||
1. En el menú de configuración, haga clic en **To App** (En la aplicación).
|
||||
|
||||
1. A la derecha de "Provisioning to App" (Aprovisionar en la aplicación), para permitir que se realicen cambios, haga clic en **Edit** (Editar).
|
||||
1. Seleccione **Enable** (Habilitar) para **Create Users** (Crear usuarios), **Update User Attributes** (Actualizar atributos de usuario) y **Deactivate Users** (Desactivar usuarios).
|
||||
|
||||
1. Para finalizar la configuración del aprovisionamiento, haga clic en **Save** (Guardar).
|
||||
|
||||
## Assigning users and groups
|
||||
## Asignación de usuarios y grupos
|
||||
|
||||
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.
|
||||
Después de haber configurado el SSO de SAML y el aprovisionamiento, podrás aprovisionar usuarios nuevos en {% data variables.product.prodname_dotcom_the_website %} asignando usuarios o grupos a la aplicación de {% data variables.product.prodname_emu_idp_application %}.
|
||||
|
||||
{% data reusables.scim.emu-scim-rate-limit %}
|
||||
|
||||
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)."
|
||||
También puedes administrar automáticamente la pertenencia a organizaciones agregando grupos a la pestaña de "Push Groups" en Okta. Cuando el grupo se aprovisione con éxito, este estará disponible para conectarse a los equipos en las organizaciones de la empresa. Para obtener más información sobre cómo administrar equipos, vea "[Administrar 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)".
|
||||
|
||||
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)."
|
||||
Cuando asignas usuarios, puedes utilizar el atributo de "Roles" en la aplicación de {% data variables.product.prodname_emu_idp_application %} para configurar el rol de un usuario en tu empresa en {% data variables.product.product_name %}. Para obtener más información sobre los roles, vea "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)".
|
||||
|
||||
|
||||
|
||||
|
||||
## Deprovisioning users and groups
|
||||
## Desaprovisionamiento de usuarios y grupos
|
||||
|
||||
To remove a user or group from {% data variables.product.product_name %}, remove the user or group from both the "Assignments" tab and the "Push groups" tab in Okta. For users, make sure the user is removed from all groups in the "Push Groups" tab.
|
||||
Para quitar un usuario o un grupo de {% data variables.product.product_name %}, quítalo tanto de la pestaña "Asignaciones" como de la pestaña "Grupos de inserción" en Okta. En el caso de los usuarios, asegúrate de se quiten de todos los grupos en la pestaña "Grupos de inserción".
|
||||
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing team memberships with identity provider groups
|
||||
title: Administrar membrecías de equipo con grupos de proveedor de identidad
|
||||
shortTitle: Manage teams with your IdP
|
||||
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 %}.'
|
||||
intro: 'Puedes administrar la pertenencia de equipos y organización en {% data variables.product.product_name %} mediante tu proveedor de identidad (IdP) si conectas grupos de IdP con equipos en tu {% 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
|
||||
@@ -16,77 +16,74 @@ topics:
|
||||
- Enterprise
|
||||
- SSO
|
||||
- Teams
|
||||
ms.openlocfilehash: 179835d6642cd5718a565869337b5420b29407a5
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160828'
|
||||
---
|
||||
## Acerca de la administración de equipos con {% data variables.product.prodname_emus %}
|
||||
|
||||
## About team management with {% data variables.product.prodname_emus %}
|
||||
Con {% data variables.product.prodname_emus %}, puede administrar la pertenencia a equipos y organizaciones dentro de su empresa a través de su IdP mediante la conexión de los equipos de {% data variables.product.prodname_dotcom %} con grupos de IdP. Cuando conectas un equipo en una de las organizaciones de tu empresa a un grupo de IdP, los cambios a la membrecía desde el grupo de IdP se reflejan automáticamente en tu empresa, lo cual reduce la necesidad de hacer actualizaciones manuales y scripts personalizados.
|
||||
|
||||
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. 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.
|
||||
Cuando un cambio a un grupo de IdP o una conexión de equipo nueva da como resultado que un {% data variables.enterprise.prodname_managed_user %} se una a un equipo en una organización de la cual no fueran ya miembros, el {% data variables.enterprise.prodname_managed_user %} se agregará automáticamente a dicha organización. Cuando desconectas un grupo de un equipo, los usuarios que se convirtieron en miembros de la organización a través de la membrecía de equipo se eliminan de esta si no se les asignó una membrecía en dicha organización por cualquier otro medio.
|
||||
|
||||
{% note %}
|
||||
|
||||
**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.
|
||||
**Nota:** Los propietarios de la organización también pueden agregar datos {% data variables.enterprise.prodname_managed_users %} a las organizaciones manualmente, siempre y cuando las cuentas ya se hayan aprovisionado a través de 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.
|
||||
Cuando cambia la membrecía de grupo en tu IdP, este envía una solicitud de SCIM con los cambios a {% data variables.product.prodname_dotcom_the_website %} de acuerdo con la programación que determinó tu IdP, así que el cambio podría no reflejarse de inmediato. Cualquier solicitud que cambie la membrecía de organización o equipo de se registrará en la bitácora de auditoría como cambios que realizó la cuenta que se utilizó para configurar el aprovisionamiento de usuarios.
|
||||
|
||||
Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team.
|
||||
Los equipos que se conectan con los grupos de IdP no pueden ser equipos padres ni hijos de otro equipo. Si el equipo que quieres conectar a un grupo de IdP es un equipo padre o hijo, te recomendamos crear un equipo nuevo o eliminar las relaciones anidadas que hacen de tu equipo un equipo padre.
|
||||
|
||||
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)".
|
||||
Para administrar el acceso a los repositorios de cualquier equipo en tu empresa, incluyendo los equipos conectados a un grupo de IdP, debes hacer cambios en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulte "[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)".
|
||||
|
||||
## Requirements for connecting IdP groups with teams
|
||||
## Requisitos para conectar grupos de IdP con equipos
|
||||
|
||||
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)."
|
||||
Para poder conectar un grupo de IdP con un equipo en {% data variables.product.prodname_dotcom %}, debe asignar el grupo a la aplicación {% data variables.product.prodname_emu_idp_application %} en el IdP. Para obtener más información, consulta "[Acerca del aprovisionamiento de SCIM para {% 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.
|
||||
Puedes conectar a un equipo de tu empresa a un grupo de IdP. Puedes asignar el mismo grupo de IdP a varios equipos de tu empresa.
|
||||
|
||||
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 %}.
|
||||
Si estás conectando un equipo a un grupo de IdP, primero debes eliminar a cualquier miembro que se haya agregado manualmente. Después de que conectas a un equipo de tu empresa a un grupo de IdP, tu administrador de IdP debe hacer cambios de membrecía de equipo a través de tu proveedor de identidad. No puedes administrar la membrecía de los equipos en {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
## Creating a new team connected to an IdP group
|
||||
## Crear un equipo nuevo conectado a un grupo de IdP
|
||||
|
||||
Any member of an organization can create a new team and connect the team to an IdP group.
|
||||
Cualquier miembro de una organización puede crear un equipo nuevo y conectarlo a un grupo de IdP.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.new_team %}
|
||||
{% data reusables.organizations.team_name %}
|
||||
{% data reusables.organizations.team_description %}
|
||||
1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect.
|
||||
|
||||
{% data reusables.organizations.team_visibility %}
|
||||
{% data reusables.organizations.create_team %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %}
|
||||
1. Para conectar a un equipo, selecciona el menú desplegable de "Grupos de Proveedor de Identidad" y haz clic en aquél que quieras conectar.
|
||||
 {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %}
|
||||
|
||||
## Managing the connection between an existing team and an IdP group
|
||||
## Administrar la conexión entre un equipo existente y un grupo de IdP
|
||||
|
||||
Organization owners and team maintainers can manage the existing connection between an IdP group and a team.
|
||||
Los propietarios organizacionales y mantenedores de equipos pueden administrar la conexión existente entre un grupo de IdP y un equipo.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)."
|
||||
**Nota**: Antes de conectar un equipo existente en {% data variables.product.prodname_dotcom_the_website %} a un grupo de IdP por primera vez, primero se deben quitar todos los miembros del equipo en {% data variables.product.prodname_dotcom_the_website %}. Para más información, vea "[Eliminación de miembros de la organización de un equipo](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}.
|
||||
|
||||
1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list.
|
||||
|
||||
1. Click **Save changes**.
|
||||
{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
|
||||
1. Opcionalmente, debajo de "Grupo de Proveedor de Identidad", a la derecha del grupo de IdP que quieres desconectar, haz clic en {% octicon "x" aria-label="X symbol" %}.
|
||||
|
||||
1. Para conectar un grupo de IdP, debajo de "Grupo de Proveedor de Identidad"; selecciona el menú desplegable y haz clic en un grupo de proveedor de identidad de la lista.
|
||||
|
||||
1. Haga clic en **Guardar cambios**.
|
||||
|
||||
## Viewing IdP groups, group membership, and connected teams
|
||||
## Ver los grupos de IdP, la membrecía de grupos y los equipos conectados
|
||||
|
||||
You can review a list of IdP groups, see any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP.
|
||||
Puedes revisar una lista de grupos de IdP, ver cualquier equipo que esté conectado en un grupo de IdP y ver la membrecía de cada grupo de IdP en {% data variables.product.product_name %}. Debes editar la membrecía de un grupo en tu IdP.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-label="The key icon" %} **Identity provider**.
|
||||
|
||||
2. To see the members and teams connected to an IdP group, click the group's name.
|
||||
|
||||
4. To view the teams connected to the IdP group, click **Teams**.
|
||||
|
||||
1. Para ver una lista de grupos de IdP, en la barra lateral izquierda, haga clic en {% octicon "key" aria-label="The key icon" %} **Identity provider** (Proveedor de identidades).
|
||||
|
||||
2. Para ver a los miembros y equipos conectados a un grupo de IdP, haz clic en el nombre del grupo.
|
||||
|
||||
4. Para ver los equipos conectados al grupo de IdP, haga clic en **Teams** (Equipos).
|
||||
|
||||
|
||||
@@ -16,6 +16,7 @@ children:
|
||||
- /about-enterprise-accounts
|
||||
- /system-overview
|
||||
- /about-the-github-enterprise-api
|
||||
- /best-practices-for-enterprises
|
||||
- /creating-an-enterprise-account
|
||||
- /accessing-compliance-reports-for-your-enterprise
|
||||
ms.openlocfilehash: d936542993310333e314efcc9d5bb5689be00701
|
||||
|
||||
@@ -54,9 +54,12 @@ If you downgrade your organization from {% data variables.product.prodname_team
|
||||
If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
**Notes:**
|
||||
- If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see "[Removing organizations from your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
|
||||
- If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: Configuring private vulnerability reporting for a repository
|
||||
intro: Owners and administrators of public repositories can allow security researchers to report vulnerabilities securely in the repository by enabling private vulnerability reporting.
|
||||
permissions: 'Anyone with admin permissions to a public repository can enable and disable private vulnerability reporting for the repository.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Configure private vulnerability reporting
|
||||
---
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
|
||||
|
||||
## About privately reporting a security vulnerability
|
||||
|
||||
Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-overview %}
|
||||
|
||||
For maintainers, the benefits of using private vulnerability reporting are:
|
||||
- Less risk of being contacted publicly, or via undesired means.
|
||||
- Receive reports in the same platform you resolve them in for simplicity
|
||||
- The security researcher creates or at least initiates the advisory report on the behalf of maintainers.
|
||||
- Maintainers receive reports in the same platform as the one used to discuss and resolve the advisories.
|
||||
- Vulnerability less likely to be in the public eye.
|
||||
- The opportunity to discuss vulnerability details privately with security researchers and collaborate on the patch.
|
||||
|
||||
## Enabling or disabling private vulnerability reporting for a repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
|
||||
|
||||
|
||||
|
||||
When a maintainer enables private security reporting for their repository, security researchers will see a new button in the **Advisories** page of the repository. The security researcher can click this button to privately report a security vulnerability to the repository maintainer.
|
||||
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ shortTitle: About the security overview
|
||||
|
||||
## About the security overview
|
||||
|
||||
The security overview provides 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 overview 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 %}
|
||||
{% data reusables.security-overview.about-the-security-overview %} {% 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 shows which security features are enabled for repositories and consolidate alerts for each feature.
|
||||
|
||||
@@ -46,8 +46,6 @@ The dependency review feature becomes available when you enable the dependency g
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
## Dependency review enforcement
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-action-beta-note %}
|
||||
|
||||
The action is available for all {% ifversion fpt or ghec %}public repositories, as well as private {% endif %}repositories that have {% data variables.product.prodname_GH_advanced_security %} enabled.
|
||||
|
||||
{% data reusables.dependency-review.action-enterprise %}
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Configuración de la revisión de dependencias
|
||||
intro: Puedes usar la revisión de dependencias para detectar vulnerabilidades antes de que se agreguen al proyecto.
|
||||
title: Configuring dependency review
|
||||
intro: You can use dependency review to catch vulnerabilities before they are added to your project.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Configure dependency review
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -14,90 +15,201 @@ topics:
|
||||
- Vulnerabilities
|
||||
- Dependencies
|
||||
- Pull requests
|
||||
ms.openlocfilehash: e7fae5d42e4f7c14098414c28e5b5eb857c39687
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107505'
|
||||
---
|
||||
## Acerca de la revisión de dependencias
|
||||
|
||||
## About dependency review
|
||||
|
||||
{% data reusables.dependency-review.feature-overview %}
|
||||
|
||||
Para obtener más información, consulta «[Acerca de la revisión de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)» y «[Revisión de los cambios de dependencia en una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)».
|
||||
For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" and "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
|
||||
|
||||
## Acerca de la configuración de la revisión de dependencias
|
||||
## About configuring dependency review
|
||||
|
||||
{% ifversion fpt %} La revisión de dependencias está disponible en todos los repositorios públicos de todos los productos y no puede deshabilitarse. La revisión de dependencias está disponible en repositorios privados propiedad de las organizaciones que usan GitHub Enterprise Cloud y que tienen una licencia para [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-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/configuring-dependency-review).
|
||||
{% ifversion fpt %}
|
||||
Dependency review is available in all public repositories in all products and cannot be disabled. Dependency review is available in private repositories owned by organizations that use GitHub Enterprise Cloud and have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-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/configuring-dependency-review).
|
||||
|
||||
{% elsif ghec %} La revisión de dependencias se incluye en {% data variables.product.product_name %} para los repositorios públicos. Para usar la revisión de dependencias en repositorios privados propiedad de las organizaciones, debes tener una licencia para [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) y tener habilitado el gráfico de dependencias.
|
||||
{% elsif ghec %}
|
||||
Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) and have the dependency graph enabled.
|
||||
|
||||
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
|
||||
1. Si «{% data variables.product.prodname_GH_advanced_security %}» no está habilitado, haz clic en **Habilitar** junto a la característica.
|
||||
|
||||
1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature.
|
||||
|
||||
|
||||
{% elsif ghes or ghae %}
|
||||
|
||||
La revisión de dependencias está disponible cuando el gráfico de dependencias está habilitado para {% data variables.location.product_location %} y {% data variables.product.prodname_advanced_security %} está habilitado para la organización o el repositorio.{% ifversion ghes %} Para obtener más información, consulta "[Habilitación de {% data variables.product.prodname_GH_advanced_security %} para la empresa](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)".{% endif %}
|
||||
Dependency review is 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.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %}
|
||||
|
||||
### Comprobación de si el gráfico de dependencias está habilitado
|
||||
### Checking if the dependency graph is enabled
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. En «Configurar características de seguridad y análisis», comprueba si el gráfico de dependencias está habilitado.
|
||||
1. Si el gráfico de dependencias está habilitado, haz clic en **Habilitar** junto a «{% data variables.product.prodname_GH_advanced_security %}» para habilitar {% data variables.product.prodname_advanced_security %}, incluida la revisión de dependencias. El botón Habilitar está deshabilitado si tu empresa no tiene licencias disponibles para{% data variables.product.prodname_advanced_security %}.{% ifversion ghes %} {% endif %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Configure security and analysis features", check if the dependency graph is enabled.
|
||||
1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion dependency-review-action-configuration %}
|
||||
## Configuración de la {% data variables.product.prodname_dependency_review_action %}
|
||||
## About configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-action-beta-note %} {% data reusables.dependency-review.dependency-review-action-overview %}
|
||||
{% data reusables.dependency-review.dependency-review-action-overview %}
|
||||
|
||||
Están disponibles las siguientes opciones de configuración.
|
||||
The following configuration options are available.
|
||||
|
||||
| Opción | Obligatorio | Uso |
|
||||
| Option | Required | Usage |
|
||||
|------------------|-------------------------------|--------|
|
||||
| `fail-on-severity` | Opcionales | Define el umbral del nivel de gravedad (`low`, `moderate`, `high` y `critical`).</br>La acción generará un error en las solicitudes de incorporación de cambios que introduzcan vulnerabilidades del nivel de gravedad especificado o superior. |
|
||||
{%- ifversion dependency-review-action-licenses %} | `allow-licenses` | Opcional | Contiene una lista de licencias permitidas. Encontrarás los valores posibles para este parámetro en la página [Licencias](/rest/licenses) de la documentación de la API.</br>La acción producirá un error en las solicitudes de incorporación de cambios que introducen dependencias con licencias que no coinciden con la lista.{% endif %} {%- ifversion dependency-review-action-licenses %} | `deny-licenses` | Opcional | Contiene una lista de licencias prohibidas. Encontrarás los valores posibles para este parámetro en la página [Licencias](/rest/licenses) de la documentación de la API.</br>La acción producirá un error en las solicitudes de incorporación de cambios que introducen dependencias con licencias que coincidan con las de la lista.|{% endif %}
|
||||
| `fail-on-severity` | Optional | Defines the threshold for level of severity (`low`, `moderate`, `high`, `critical`).</br>The action will fail on any pull requests that introduce vulnerabilities of the specified severity level or higher. |
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
| `fail-on-scopes` | Optional | Contains a list of strings representing the build environments you want to support (`development`, `runtime`, `unknown`). </br>The action will fail on pull requests that introduce vulnerabilites in the scopes that match the list.|{% endif %}
|
||||
| `allow-ghsas` | Optional | Contains a list of {% data variables.product.prodname_advisory_database %} IDs that can be skipped during detection. You can find the possible values for this parameter in the [{% data variables.product.prodname_advisory_database %}](https://github.com/advisories). |
|
||||
| `config-file` | Optional | Specifies a path to a configuration file. The configuration file can be local to the repository or a file located in an external repository.|
|
||||
| `external-repo-token` | Optional | Specifies a token for fetching the configuration file, if the file resides in a private external repository. The token must have read access to the repository.|
|
||||
|
||||
{% ifversion dependency-review-action-licenses %} {% tip %}
|
||||
|
||||
**Sugerencia**: Las opciones `allow-licenses` y `deny-licenses` se excluyen mutuamente.
|
||||
|
||||
{% endtip %} {% endif %}
|
||||
|
||||
En este archivo de ejemplo de {% data variables.product.prodname_dependency_review_action %} se muestra cómo se pueden usar estas opciones de configuración. Observa que en el ejemplo se usa el número de versión corta para la acción (`v2`) en lugar de un número de versión de gravedad (por ejemplo, `v2.0.8`). Esto garantiza que uses la versión secundaria más reciente de la acción.
|
||||
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v2
|
||||
with:
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
# allow-licenses: GPL-3.0, BSD-3-Clause, MIT
|
||||
{% tip %}
|
||||
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
# deny-licenses: LGPL-2.0, BSD-2-Clause
|
||||
{% endif %}
|
||||
```
|
||||
**Tip:** The `allow-licenses` and `deny-licenses` options are mutually exclusive.
|
||||
|
||||
Para obtener más información sobre las opciones de configuración, consulta [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
## Configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
There are two methods of configuring the {% data variables.product.prodname_dependency_review_action %}:
|
||||
- Inlining the configuration options in your workflow file.
|
||||
- Referencing a configuration file in your workflow file.
|
||||
|
||||
Notice that all of the examples use a short version number for the action (`v3`) instead of a semver release number (for example, `v3.0.8`). This ensures that you use the most recent minor version of the action.
|
||||
### Using inline configuration to set up the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
```
|
||||
1. Specify your settings.
|
||||
|
||||
This {% data variables.product.prodname_dependency_review_action %} example file illustrates how you can use the available configuration options.
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
with:
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
allow-licenses: GPL-3.0, BSD-3-Clause, MIT
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
deny-licenses: LGPL-2.0, BSD-2-Clause
|
||||
{% endif %}
|
||||
# ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
|
||||
# Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories
|
||||
allow-ghsas: GHSA-abcd-1234-5679, GHSA-efgh-1234-5679
|
||||
{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
# ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
|
||||
# Possible values: "development", "runtime", "unknown"
|
||||
fail-on-scopes: development, runtime
|
||||
{% endif %}
|
||||
```
|
||||
### Using a configuration file to set up {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder and use `config-file` to specify that you are using a configuration file.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
with:
|
||||
# ([String]). Representing a path to a configuration file local to the repository or in an external repository.
|
||||
# Possible values: An absolute path to a local file or an external file.
|
||||
config-file: './.github/dependency-review-config.yml'
|
||||
# Syntax for an external file: OWNER/REPOSITORY/FILENAME@BRANCH
|
||||
config-file: 'github/octorepo/dependency-review-config.yml@main'
|
||||
|
||||
# ([Token]) Use if your configuration file resides in a private external repository.
|
||||
# Possible values: Any GitHub token with read access to the private external repository.
|
||||
external-repo-token: 'ghp_123456789abcde'
|
||||
```
|
||||
1. Create the configuration file in the path you have specified.
|
||||
|
||||
This YAML example file illustrates how you can use the available configuration options.
|
||||
```yaml{:copy}
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
allow-licenses:
|
||||
- GPL-3.0
|
||||
- BSD-3-Clause
|
||||
- MIT
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
deny-licenses:
|
||||
- LGPL-2.0
|
||||
- BSD-2-Clause
|
||||
{% endif %}
|
||||
# ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
|
||||
# Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories
|
||||
allow-ghsas:
|
||||
- GHSA-abcd-1234-5679
|
||||
- GHSA-efgh-1234-5679
|
||||
{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
# ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
|
||||
# Possible values: "development", "runtime", "unknown"
|
||||
fail-on-scopes:
|
||||
- development
|
||||
- runtime
|
||||
{% endif %}
|
||||
```
|
||||
For further details about the configuration options, see [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
|
||||
{% endif %}
|
||||
|
||||
@@ -42,7 +42,7 @@ You can work with {% data variables.product.prodname_github_codespaces %} in the
|
||||
|
||||
If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account.
|
||||
|
||||
To use `gh` to work with {% data variables.product.prodname_github_codespaces %}, type `gh codespace <COMMAND>` or its alias `gh cs <COMMAND>`.
|
||||
To use `gh` to work with {% data variables.product.prodname_github_codespaces %}, type `gh codespace SUBCOMMAND` or its alias `gh cs SUBCOMMAND`.
|
||||
|
||||
As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could:
|
||||
|
||||
@@ -51,15 +51,15 @@ As an example of a series of commands you might use to work with {% data variabl
|
||||
* Create a new codespace for the required repository branch:<br>
|
||||
`gh codespace create -r github/docs -b main`
|
||||
* SSH into the new codespace:<br>
|
||||
`gh codespace ssh -c mona-github-docs-v4qxrv7rfwv9w`
|
||||
`gh codespace ssh -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
|
||||
* Forward a port to your local machine:<br>
|
||||
`gh codespace ports forward 8000:8000 -c mona-github-docs-v4qxrv7rfwv9w`
|
||||
`gh codespace ports forward 8000:8000 -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
|
||||
|
||||
## `gh` commands for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
The sections below give example commands for each of the available operations.
|
||||
|
||||
For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, use `gh codespace [<SUBCOMMAND>...] --help` on the command line.
|
||||
For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, on the command line, use `gh codespace --help` for general help or `gh codespace SUBCOMMAND --help` for help with a specific subcommand.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -163,7 +163,7 @@ The location of files and directories on the codespace is relative to the home d
|
||||
|
||||
* Copy a file to the directory in which a repository is checked out in a codespace:
|
||||
|
||||
`gh codespace cp myfile.txt remote:/workspaces/<REPOSITORY-NAME>`
|
||||
`gh codespace cp myfile.txt remote:/workspaces/REPOSITORY-NAME`
|
||||
|
||||
* Copy a file from a codespace to the current directory on the local machine:
|
||||
|
||||
@@ -233,7 +233,7 @@ You can use the {% data variables.product.prodname_cli %} extension to create a
|
||||
### Change the machine type of a codespace
|
||||
|
||||
```shell
|
||||
gh codespace edit -m <em>machine-type-name</em>
|
||||
gh codespace edit -m MACHINE-TYPE-NAME
|
||||
```
|
||||
|
||||
For more information, see the "{% data variables.product.prodname_cli %}" tab of "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: GitHub Codespaces overview
|
||||
title: Resumen de GitHub Codespaces
|
||||
shortTitle: Overview
|
||||
intro: 'This guide introduces {% data variables.product.prodname_github_codespaces %} and provides details on how it works and how to use it.'
|
||||
intro: 'En esta guía se presenta {% data variables.product.prodname_github_codespaces %} y se proporcionan detalles de cómo funciona y cómo usarlo.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-reference/about-codespaces
|
||||
@@ -15,52 +15,57 @@ versions:
|
||||
type: overview
|
||||
topics:
|
||||
- Codespaces
|
||||
ms.openlocfilehash: a1618c86671bc5b06474c41803c6b34576a897aa
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160804'
|
||||
---
|
||||
## ¿Qué es un codespace?
|
||||
|
||||
## What is a codespace?
|
||||
Un codespace es un ambiente de desarrollo que se hospeda en la nube. Puedes personalizar tu proyecto para {% data variables.product.prodname_github_codespaces %} confirmando los [archivos de configuración](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) en el repositorio (lo que se conoce a menudo como configuración como código). Esta acción crea una configuración de codespace repetible para todos los usuarios del proyecto.
|
||||
|
||||
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.
|
||||
Cada codespace se ejecuta en una máquina virtual hospedada por {% data variables.product.prodname_dotcom %}. Puedes elegir el tipo de máquina que deseas usar, en función de los recursos que necesites. Hay disponibles varios tipos de máquina, empezando por un procesador de 2 núcleos, 4 GB de RAM y 32 GB de almacenamiento.
|
||||
|
||||
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.
|
||||
Puedes conectarte a tus codespaces desde el explorador, desde {% data variables.product.prodname_vscode %}, desde la aplicación de puerta de enlace de JetBrains o mediante {% data variables.product.prodname_cli %}.
|
||||
|
||||
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 %}.
|
||||
|
||||
|
||||
|
||||
## Uso de {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
## Using {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
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.
|
||||
Para comenzar a desarrollar utilizando recursos de cómputo basados en la nube, puedes crear un codespace desde una plantilla o cualquier rama o confirmación en un repositorio. Al crear un codespace a partir de una plantilla, puedes empezar desde una plantilla en blanco o elegir una plantilla adecuada para el trabajo que estás haciendo.
|
||||
|
||||
{% data reusables.codespaces.links-to-get-started %}
|
||||
|
||||
### Using codespaces owned by your personal account
|
||||
### Uso de codespaces propiedad de tu cuenta personal
|
||||
|
||||
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.
|
||||
Todas las cuentas de {% data variables.product.prodname_dotcom_the_website %} tienen una cuota mensual de uso gratuito de {% data variables.product.prodname_github_codespaces %} incluida en el plan Gratis o Pro. Puedes empezar a usar {% data variables.product.prodname_github_codespaces %} en tu cuenta personal sin cambiar ninguna configuración ni proporcionar detalles de pago.
|
||||
|
||||
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.
|
||||
Puedes crear y usar un codespace para cualquier repositorio que puedas clonar. También puedes usar una plantilla para crear codespaces que no estén asociados inicialmente a un repositorio. Si creas un codespace desde un repositorio propiedad de la organización, el uso del codespace se cobrará a la organización (si la organización está configurada para ello) o a tu cuenta personal. Los codespaces creados a partir de plantillas siempre se cobran a tu cuenta personal.
|
||||
|
||||
{% data reusables.codespaces.codespaces-continue-by-paying %}
|
||||
|
||||
### Using organization-owned codespaces
|
||||
### Uso de codespaces propiedad de la organización
|
||||
|
||||
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)."
|
||||
Los propietarios de la organización pueden habilitar el uso de {% data variables.product.prodname_github_codespaces %}, facturables a la organización o a la cuenta de empresa. Esto se aplica a codespaces creados a partir de repositorios propiedad de la organizació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)". Puedes establecer un límite de gasto para el uso de {% data variables.product.prodname_github_codespaces %} en tu organización o cuenta empresarial. 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-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)."
|
||||
Si el uso de un codespace va a facturarse a una organización o empresa, se muestra cuando se crea el codespace. Para obtener más información, consulta "[Creación de un codespace para un repositorio](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)". Los codespaces que se facturan a una organización, o a su empresa matriz, son propiedad de la organización y pueden ser eliminados por un propietario de la organización. Para más información, vea "[Eliminación de un codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)".
|
||||
|
||||
### Customizing {% data variables.product.prodname_github_codespaces %}
|
||||
### Personalización de {% 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.
|
||||
Para personalizar los runtimes y las herramientas del codespace, puedes crear una o varias configuraciones de contenedor de desarrollo para el repositorio. Agregar configuraciones de contenedor de desarrollo al repositorio permite definir una elección de diferentes entornos de desarrollo que sean adecuados para el trabajo que harán las personas en el repositorio.
|
||||
|
||||
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)."
|
||||
Si creas un codespace desde un repositorio sin configuraciones de contenedor de desarrollo, {% data variables.product.prodname_github_codespaces %} clonará tu repositorio en un entorno con la imagen de codespace predeterminada que incluye muchas herramientas, lenguajes y entornos en tiempo de ejecución. Si creas un codespace a partir de una plantilla, puedes empezar con alguna configuración inicial sobre la imagen predeterminada. 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)".
|
||||
|
||||
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 %}.
|
||||
Puedes personalizar aspectos del entorno de codespace mediante un repositorio de [dotfiles](https://dotfiles.github.io/tutorials/) público. Puedes usar dotfiles para establecer alias y preferencias de shell, o para instalar tus preferencias personales de las herramientas que quieras usar. Si usas {% data variables.product.prodname_github_codespaces %} en el explorador o en {% data variables.product.prodname_vscode %}, puedes usar [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) para proporcionar al editor de codespace la misma configuración, métodos abreviados de teclado, fragmentos de código y extensiones que has configurado en la instalación local de {% data variables.product.prodname_vscode %}.
|
||||
|
||||
For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)".
|
||||
Para más información, vea "[Personalización del codespace](/codespaces/customizing-your-codespace)".
|
||||
|
||||
## Billing for {% data variables.product.prodname_codespaces %}
|
||||
## Facturación para {% 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)."
|
||||
Para obtener más información sobre los precios, el almacenamiento y el uso de {% data variables.product.prodname_github_codespaces %}, consulta "[Acerca de la facturación de {% 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)."
|
||||
{% data reusables.codespaces.codespaces-monthly-billing %} Para obtener información sobre cómo los propietarios de las organizaciones y los administradores de facturación pueden controlar el límite de gasto de {% data variables.product.prodname_github_codespaces %} en una organización, consulta "[Administración de los límites de gasto de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)".
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: The github.dev web-based editor
|
||||
intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.'
|
||||
title: El editor basado en web de github.dev
|
||||
intro: 'Utiliza el github.dev {% data variables.product.prodname_serverless %} desde tu repositorio o solicitud de incorporación de cambios para crear y confirmar cambios.'
|
||||
versions:
|
||||
feature: githubdev-editor
|
||||
type: how_to
|
||||
@@ -12,104 +12,108 @@ topics:
|
||||
shortTitle: Web-based editor
|
||||
redirect_from:
|
||||
- /codespaces/developing-in-codespaces/web-based-editor
|
||||
ms.openlocfilehash: d1c21f3e75ecc4fec282c9156943c137287d203c
|
||||
ms.sourcegitcommit: caab4edbbeedf23e9062e48a67c35224772b6efa
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160481'
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/general).
|
||||
**Nota:** github.dev {% data variables.product.prodname_serverless %} se encuentra actualmente en versión preliminar beta. Puede proporcionar comentarios [en nuestros debates](https://github.com/community/community/discussions/categories/general).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About the {% data variables.product.prodname_serverless %}
|
||||
## Acerca de {% data variables.product.prodname_serverless %}
|
||||
|
||||
The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor.
|
||||
El {% data variables.product.prodname_serverless %} presenta una experiencia de edición ligera que se ejecuta completamente en tu buscador. Con el {% data variables.product.prodname_serverless %}, puedes navegar por los archivos y repositorios de código abierto desde {% data variables.product.prodname_dotcom %} y hacer y confirmar cambios de código. Puedes abrir cualquier repositorio, bifurcación o solicitud de cambios en el editor.
|
||||
|
||||
The {% data variables.product.prodname_serverless %} is available to everyone for free on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
El {% data variables.product.prodname_serverless %} se encuentra disponible gratuitamente para todos en {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode_shortname %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
El {% data variables.product.prodname_serverless %} proporciona muchos de los beneficios de {% data variables.product.prodname_vscode %}, tales como búsqueda, resaltado de sintaxis y vista de control de código fuente. También puedes utilizar la sincronización de la configuración para compartir tus propios valores de configuración de {% data variables.product.prodname_vscode_shortname %} con el editor. Para obtener más información, consulta "[Sincronización de la configuración](https://code.visualstudio.com/docs/editor/settings-sync)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.
|
||||
El {% data variables.product.prodname_serverless %} se ejecuta completamente en el área de pruebas de tu buscador. El editor no clona el repositorio, sino que usa la [extensión GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) para llevar a cabo la mayor parte de la funcionalidad que usará. Tu trabajo se guarda en el almacenamiento local de tu buscador hasta que lo confirmes. Debes confirmar tus cambios frecuentemente para asegurarte de que siempre sean accesibles.
|
||||
|
||||
You must be signed in to use the web-based editor.
|
||||
Debes haber iniciado sesión para usar el editor basado en web.
|
||||
|
||||
## Opening the {% data variables.product.prodname_serverless %}
|
||||
## Abrir el {% data variables.product.prodname_serverless %}
|
||||
|
||||
You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways:
|
||||
Puedes abrir cualquier repositorio de {% data variables.product.prodname_dotcom %} en el {% data variables.product.prodname_serverless %} en cualquiera de las siguientes formas:
|
||||
|
||||
- To open the repository in the same browser tab, press <kbd>.</kbd> while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
|
||||
- Para abrir el repositorio en la misma pestaña del explorador, presiona <kbd>.</kbd> mientras buscas cualquier repositorio o solicitud de incorporación de cambios en {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
To open the repository in a new browser tab, press <kbd>></kbd>.
|
||||
Para abrir el repositorio en una pestaña nueva del explorador, presiona <kbd>></kbd>.
|
||||
|
||||
- Change the URL from "github.com" to "github.dev".
|
||||
- When viewing a file, use the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and select **Open in github.dev**.
|
||||
- Cambiando la URL de "github.com" a "github.dev".
|
||||
- Al ver un archivo, usa el menú desplegable situado junto a {% octicon "pencil" aria-label="The edit icon" %} y selecciona **Abrir en github.dev**.
|
||||
|
||||
|
||||
|
||||
|
||||
## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %}
|
||||
## {% data variables.product.prodname_codespaces %} y el {% data variables.product.prodname_serverless %}
|
||||
|
||||
Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_github_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case.
|
||||
Tanto el {% data variables.product.prodname_serverless %} como los {% data variables.product.prodname_github_codespaces %} te permiten editar el código directamente desde tu repositorio. Sin embargo, ambos tienen beneficios ligeramente diferentes, dependiendo de tu caso de uso.
|
||||
|
||||
|| {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_github_codespaces %}|
|
||||
|-|----------------|---------|
|
||||
| **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 %}.|
|
||||
| **Costee** | Libre. | Cuota mensual gratuita de uso para cuentas personales. Para obtener información sobre precios, consulta "[Acerca de la facturación de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)".|
|
||||
| **Disponibilidad** | Disponible para todos en GitHub.com. | Disponible para todos en GitHub.com. |
|
||||
| **Inicio** | El {% data variables.product.prodname_serverless %} se abre instantáneamente al presionar una tecla y puedes comenzar a usarlo de inmediato sin tener que esperar por configuraciones o instalaciones adicionales. | Al crear o reanudar un codespace, se le asigna una máquina virtual y el contenedor se configura en función del contenido de un archivo `devcontainer.json`. Esta configuración puede tomar algunos minutos para crear el ambiente. Para obtener más información, consulta "[Creación de un codespace para un repositorio](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)". |
|
||||
| **Proceso** | No hay cálculos asociados, así que no podrás compilar y ejecutar tu código ni utilizar la terminal integrada. | Con {% data variables.product.prodname_github_codespaces %}, obtienes el poder de una VM dedicada en la que ejecutas y depuras tu aplicación.|
|
||||
| **Acceso al terminal** | Ninguno. | {% data variables.product.prodname_github_codespaces %} proporciona un conjunto común de herramientas de manera predeterminada, lo que significa que puedes utilizar el terminal como lo harías en tu entorno local.|
|
||||
| **Extensiones** | Solo un subconjunto de extensiones que pueden ejecutarse en la web aparecerá en la Vista de Extensiones y podrá instalarse. Para más información, vea "[Uso de extensiones](#using-extensions)".| Con {% data variables.product.prodname_github_codespaces %}, puedes usar la mayoría de extensiones de {% data variables.product.prodname_vscode_marketplace %}.|
|
||||
|
||||
### Continue working on {% data variables.product.prodname_codespaces %}
|
||||
### Continuación del trabajo en {% data variables.product.prodname_codespaces %}
|
||||
|
||||
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 %}.
|
||||
Puede iniciar el flujo de trabajo en {% data variables.product.prodname_serverless %} y seguir trabajando en un codespace. Si intentas acceder a la Vista de Ejecución y Depuración o a la Terminal, se ten notificará que no están disponibles en {% 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.
|
||||
Para continuar el trabajo en un codespace, haga clic en **Continuar trabajando en...** y seleccione **Crear codespace** para crear un codespace en la rama actual. Antes de que elijas esta opción, debes confirmar cualquier cambio.
|
||||
|
||||
|
||||
|
||||
|
||||
## Using source control
|
||||
## Utilizar el control de código fuente
|
||||
|
||||
When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
Cuando utilizas el {% data variables.product.prodname_serverless %}, todas las acciones se administran a través de la Vista de Control de Código Fuente, la cual se ubica en la barra de actividad en la parte izquierda. Para obtener más información sobre la vista Control de código fuente, consulta "[Control de versiones](https://code.visualstudio.com/docs/editor/versioncontrol)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
Ya que el editor basado en web utiliza la extensión de repositorios de GitHub para alimentar su funcionalidad, puedes cambiar de rama sin necesidad de acumular cambios. Para obtener más información, consulta "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
### Create a new branch
|
||||
### Creación de una rama
|
||||
|
||||
{% data reusables.codespaces.create-or-switch-branch %}
|
||||
Any uncommitted changes you have made in your old branch will be available on your new branch.
|
||||
{% data reusables.codespaces.create-or-switch-branch %} Los cambios sin confirmar que haya realizado en la rama anterior estarán disponibles en la nueva.
|
||||
|
||||
### Commit your changes
|
||||
### Confirmación de los cambios
|
||||
|
||||
{% data reusables.codespaces.source-control-commit-changes %}
|
||||
5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}.
|
||||
### Create a pull request
|
||||
5. Una vez que hayas confirmado tus cambios, estos se subirán automáticamente a tu rama de {% data variables.product.prodname_dotcom %}.
|
||||
### Creación de una solicitud de incorporación de cambios
|
||||
|
||||
{% data reusables.codespaces.source-control-pull-request %}
|
||||
|
||||
### Working with an existing pull request
|
||||
### Trabajar con una solicitud de cambios existente
|
||||
|
||||
You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request.
|
||||
Puedes utilizar el {% data variables.product.prodname_serverless %} para trabajar con una solicitud de cambios existente.
|
||||
|
||||
1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}.
|
||||
2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}.
|
||||
3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes.
|
||||
1. Navega hasta la solicitud de cambios que te gustaría utilizar en el {% data variables.product.prodname_serverless %}.
|
||||
2. Presione `.` para abrir la solicitud de incorporación de cambios en {% data variables.product.prodname_serverless %}.
|
||||
3. Una vez que haya realizado los cambios, confírmelos siguiendo los pasos descritos en [Confirmación de los cambios](#commit-your-changes). Tus cambios se confirmarán directamente en la rama, no es necesario subirlos.
|
||||
|
||||
## Using extensions
|
||||
## Uso de extensiones
|
||||
|
||||
The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode_shortname %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
El {% data variables.product.prodname_serverless %} es compatible con las extensiones de {% data variables.product.prodname_vscode_shortname %} que se hayan creado o actualizado específicamente para ejecutarse en la web. A estas extensiones se les conoce como "extensiones web". Para obtener información sobre cómo puedes crear una extensión web o actualizar la extensión existente a fin de que funcione para la web, consulta "[Extensiones web](https://code.visualstudio.com/api/extension-guides/web-extensions)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
Las extensiones que puedan ejecutarse en {% data variables.product.prodname_serverless %} aparecerán en la Vista de Extensiones y podrán instalarse. Si utilizas la sincronización de ajustes, cualquier extensión compatible también se instala automáticamente. Para obtener información, consulta "[Sincronización de la configuración](https://code.visualstudio.com/docs/editor/settings-sync)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
|
||||
## Troubleshooting
|
||||
## Solución de problemas
|
||||
|
||||
If you have issues opening the {% data variables.product.prodname_serverless %}, try the following:
|
||||
Si tienes problemas para abrir el {% data variables.product.prodname_serverless %}, intenta lo siguiente:
|
||||
|
||||
- Make sure you are signed in to {% data variables.product.prodname_dotcom %}.
|
||||
- Disable any ad blockers.
|
||||
- Use a non-incognito window in your browser to open the {% data variables.product.prodname_serverless %}.
|
||||
- Asegúrate de estar firmado en {% data variables.product.prodname_dotcom %}.
|
||||
- Inhabilita cualquier bloqueador de anuncios.
|
||||
- Utiliza una ventana de tu buscador que no esté en modo incógnito para abrir el {% data variables.product.prodname_serverless %}.
|
||||
|
||||
### Known limitations
|
||||
### Limitaciones conocidas
|
||||
|
||||
- The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
|
||||
- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
- `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`.
|
||||
- El {% data variables.product.prodname_serverless %} es actualmente compatible en Chrome (y en varios otros buscadores basados en Chromium), Edge, Firefox y Safari. Te recomendamos que utilices las últimas versiones de estos buscadores.
|
||||
- Es posible que algunos enlaces de teclas no funcionen, dependiendo del buscador que estás utilizando. Estas limitaciones de enlace de claves se documentan en la sección "[Limitaciones y adaptaciones conocidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" de la documentación de {% data variables.product.prodname_vscode_shortname %}.
|
||||
- Es posible que `.` no funcione para abrir {% data variables.product.prodname_serverless %} según el diseño de teclado local. En ese caso, puede abrir cualquier repositorio de {% data variables.product.prodname_dotcom %} en {% data variables.product.prodname_serverless %} si cambia la dirección URL de `github.com` a `github.dev`.
|
||||
|
||||
@@ -1,41 +1,46 @@
|
||||
---
|
||||
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.'
|
||||
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 %}.'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
shortTitle: About GitHub Copilot
|
||||
ms.openlocfilehash: dd4538cb4cf6fc9dd84bb3f0d05bf8a85559d5ec
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160644'
|
||||
---
|
||||
## Acerca de {% data variables.product.prodname_copilot %}
|
||||
|
||||
## About {% 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. {% 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 %} se entrena en todos los idiomas que aparecen en repositorios públicos. Para cada idioma, la calidad de las sugerencias que reciba puede depender del volumen y la diversidad de datos de entrenamiento para ese idioma. Por ejemplo, JavaScript está bien representado en repositorios públicos y es uno de los mejores lenguajes admitidos de {% data variables.product.prodname_copilot %}. Los lenguajes con menos representación en repositorios públicos pueden producir menos sugerencias o menos sólidas.
|
||||
|
||||
{% 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.
|
||||
{% 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 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)."
|
||||
## Uso de {% data variables.product.prodname_copilot %}
|
||||
|
||||
## Using {% data variables.product.prodname_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/).
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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)".
|
||||
|
||||
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)."
|
||||
|
||||
{% 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 %} 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.
|
||||
|
||||
{% data reusables.copilot.emus-cannot-use-copilot %}
|
||||
|
||||
## About billing for {% data variables.product.prodname_copilot %}
|
||||
## Acerca de la facturación para {% data variables.product.prodname_copilot %}
|
||||
|
||||
{% 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)."
|
||||
{% data variables.product.prodname_copilot %} es una característica de pago que requiere una suscripción mensual o anual. Los alumnos, profesores 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)".
|
||||
|
||||
## About the license for the {% data variables.product.prodname_copilot %} plugin in JetBrains IDEs
|
||||
## Sobre la licencia del complemento {% data variables.product.prodname_copilot %} en los IDE de JetBrains
|
||||
|
||||
{% 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.
|
||||
{% 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.
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- "[{% 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)"
|
||||
- "[{% 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)"
|
||||
|
||||
@@ -205,6 +205,8 @@ Members of your organization or enterprise can use GitHub's learning and support
|
||||
### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot.
|
||||
|
||||
|
||||
@@ -119,6 +119,8 @@ Your enterprise members can learn more about Git and {% data variables.product.p
|
||||
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
{% data reusables.getting-started.learning-enterprise %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub glossary
|
||||
intro: 'This glossary introduces common Git and {% data variables.product.prodname_dotcom %} terminology.'
|
||||
title: Glosario de GitHub
|
||||
intro: 'Este glosario te presenta la terminología común de Git y de {% data variables.product.prodname_dotcom %}.'
|
||||
redirect_from:
|
||||
- /articles/github-glossary
|
||||
- /github/getting-started-with-github/github-glossary
|
||||
@@ -10,6 +10,12 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
ms.openlocfilehash: 3595b29a43cd7181bf5203f892b3bee84a237c29
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160853'
|
||||
---
|
||||
{% for glossary in glossaries %}
|
||||
### {{ glossary.term }}
|
||||
@@ -19,8 +25,8 @@ versions:
|
||||
|
||||
---
|
||||
|
||||
## Further reading
|
||||
## Información adicional
|
||||
|
||||
- [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)
|
||||
- [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)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configurar una prueba de la nube de GitHub Enterprise
|
||||
intro: 'Puedes probar {% data variables.product.prodname_ghe_cloud %} de manera gratuita.'
|
||||
title: Setting up a trial of GitHub Enterprise Cloud
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
|
||||
redirect_from:
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-cloud
|
||||
- /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
|
||||
@@ -12,74 +12,73 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Cloud trial
|
||||
ms.openlocfilehash: 13cb43b5dfd4a9e207a9a1cca090b223c56f4678
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147389959'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise.ghec-cta-button %}
|
||||
|
||||
|
||||
## Acerca de {% data variables.product.prodname_ghe_cloud %}
|
||||
## About {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} es un plan para negocios o equipos grandes que colaboran en {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise.about-github-for-enterprises %}
|
||||
{% data variables.product.prodname_ghe_cloud %} is a plan for large businesses or teams who collaborate on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise.about-github-for-enterprises %}
|
||||
|
||||
{% data reusables.organizations.about-organizations %} Para más información sobre los tipos de cuenta, vea "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
|
||||
{% data reusables.organizations.about-organizations %} For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
|
||||
|
||||
Puedes utilizar organizaciones gratuitamente con {% data variables.product.prodname_free_team %}, las cuales incluyen características limitadas. Para encontrar características adicionales, tales como el inicio de sesión único (SSO) de SAML, el control de accesos para las {% data variables.product.prodname_pages %} y los minutos incluidos de las {% data variables.product.prodname_actions %}, puedes mejorar a {% data variables.product.prodname_ghe_cloud %}. Para obtener una lista detallada de las características disponibles con {% data variables.product.prodname_ghe_cloud %}, vea nuestra página [Precios](https://github.com/pricing).
|
||||
You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
|
||||
|
||||
Puedes configurar un periodo de prueba para {% data variables.product.prodname_ghe_cloud %} y evaluar estas características adicionales en una cuenta organizacional nueva o existente.
|
||||
You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
|
||||
|
||||
También hay pruebas disponibles para {% data variables.product.prodname_ghe_server %}. Para más información, vea "[Configuración de una versión de prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)".
|
||||
Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## Acerca de las pruebas de {% data variables.product.prodname_ghe_cloud %}
|
||||
## About trials of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
Puede configurar un periodo de 30 días de prueba para evaluar {% data variables.product.prodname_ghe_cloud %}. No es necesario que proporciones un método de pago durante la prueba a menos que agreges aplicaciones de {% data variables.product.prodname_marketplace %} en tu organización que requieran de un método de pago. Para más información, vea "[Acerca de la facturación de {% data variables.product.prodname_marketplace %}](/enterprise-cloud@latest/articles/about-billing-for-github-marketplace/)".
|
||||
You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/enterprise-cloud@latest/articles/about-billing-for-github-marketplace/)."
|
||||
|
||||
Tu prueba incluye 50 asientos. Si necesitas más plazas para evaluar a {% data variables.product.prodname_ghe_cloud %}, contacta a {% data variables.contact.contact_enterprise_sales %}. Al finalizar la prueba, puedes elegir una cantidad diferente de asientos.
|
||||
Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
|
||||
|
||||
{% data reusables.saml.saml-accounts %}
|
||||
|
||||
Para más información, vea "[Acerca de la administración de identidades y acceso con el inicio de sesión único de SAML](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
|
||||
For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
Las {% data variables.product.prodname_emus %} no son parte de la prueba gratuita de {% data variables.product.prodname_ghe_cloud %}. Si está interesado en {% data variables.product.prodname_emus %}, póngase en contacto con el [equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
|
||||
{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
|
||||
|
||||
## Configurar tu prueba de {% data variables.product.prodname_ghe_cloud %}
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
Antes de probar {% data variables.product.prodname_ghe_cloud %}, debes haber iniciado sesión en una cuenta personal. Si aún no tienes una cuenta personal en {% data variables.product.prodname_dotcom_the_website %}, debes crear una. Para más información, vea "[Suscripción a una nueva cuenta de {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/articles/signing-up-for-a-new-github-account)"
|
||||
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a personal account. If you don't already have a personal account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/free-pro-team@latest/articles/signing-up-for-a-new-github-account)."
|
||||
|
||||
1. Vaya a [{% data variables.product.prodname_dotcom %} para empresas](https://github.com/enterprise).
|
||||
1. Haga clic en **Iniciar una evaluación gratuita**.
|
||||
|
||||
1. Haga clic en **Nube de Enterprise**
|
||||
|
||||
1. Sigue los mensajes para configurar tu prueba.
|
||||
1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
|
||||
1. Click **Start a free trial**.
|
||||
|
||||
1. Click **Enterprise Cloud**.
|
||||
|
||||
1. Follow the prompts to configure your trial.
|
||||
|
||||
## Explorar {% data variables.product.prodname_ghe_cloud %}
|
||||
## Exploring {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
Después de configurar la versión de prueba, puedes explorar {% data variables.product.prodname_ghe_cloud %} siguiendo las tareas sugeridas en la pestaña "Información general" de la organización. Si has descartado las tareas con anterioridad, puedes volver a acceder a ellas haciendo clic en **Introducción a las tareas sugeridas** en la parte superior de la página.
|
||||
After you set up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the suggested tasks on the "Overview" tab of your organization. If you've previously dismissed the tasks, you can access them again by clicking **Get started with suggested tasks** at the top of the page.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.docs.you-can-read-docs-for-your-product %}
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## Terminar tu prueba
|
||||
## Finishing your trial
|
||||
|
||||
Puedes comprar {% data variables.product.prodname_enterprise %} en cualquier momento durante tu periodo de prueba. El comprar {% data variables.product.prodname_enterprise %} terminará tu periodo de prueba, eliminando el máximo de 50 plazas e iniciando el periodo de pagos.
|
||||
You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
|
||||
|
||||
Si no compras {% data variables.product.prodname_enterprise %}, cuando termine el periodo de prueba, tu organización bajará de nivel. Si utilzaste una organización existente para la prueba, esta bajará de nivel al producto que estabas utilizando antes de dicho periodo. Si creaste una organización nueva para la prueba, esta bajará de nivel a {% data variables.product.prodname_free_team %}.
|
||||
If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}.
|
||||
|
||||
Tu organización perderá el acceso a cualquier funcionalidad que no se incluya en el producto nuevo, tal como las características avanzadas como {% data variables.product.prodname_pages %} para los repositorios privados. Si no planeas mejorar tu plan, evita perder el acceso a las características avanzadas y considera convertir a los repositorios afectados en públicos antes de que termine tu periodo de prueba. Para más información, vea "[Configuración de la visibilidad de un repositorio](/articles/setting-repository-visibility)".
|
||||
Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
|
||||
|
||||
El bajar de categoría también inhabilita los ajustes de SAML que se configuraron durante el periodo de prueba. Si posteriormente compras {% data variables.product.prodname_enterprise %}, tus ajustes de SAML se habilitarán nuevamente para que se autentiquen los usuarios de tu organización.
|
||||
Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.billing_plans %}
|
||||
5. En "Evaluación gratuita de {% data variables.product.prodname_ghe_cloud %}", haga clic en **Comprar Enterprise** o **Cambiar a una versión anterior de equipo**.
|
||||
|
||||
6. Siga las indicaciones para escribir el método de pago y, después, haga clic en **Enviar**.
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
|
||||
|
||||
6. Follow the prompts to enter your payment method, then click **Submit**.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configurar una prueba del servidor de GitHub Enterprise
|
||||
intro: 'Puedes probar {% data variables.product.prodname_ghe_server %} de manera gratuita.'
|
||||
title: Setting up a trial of GitHub Enterprise Server
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
|
||||
redirect_from:
|
||||
- /articles/requesting-a-trial-of-github-enterprise
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-server
|
||||
@@ -13,61 +13,58 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Server trial
|
||||
ms.openlocfilehash: eba705715818c03cb7fd1316ede6507111728806
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146454241'
|
||||
---
|
||||
## Acerca de las pruebas de {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
Puedes solicitar una prueba de 45 días para evaluar {% data variables.product.prodname_ghe_server %}. La prueba se instalará a modo de aparato virtual, con opciones para la implementación en el entorno local o en la nube. Para más información sobre {% data variables.product.prodname_ghe_server %}, y para obtener una lista de plataformas de virtualización admitidas, consulta "[Acerca de {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)".
|
||||
## About trials of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Las alertas de seguridad {% endif %} y {% data variables.product.prodname_github_connect %} no están disponibles en este momento en las evaluaciones gratuitas de {% data variables.product.prodname_ghe_server %}. Para obtener una demostración de estas características, contacta a {% data variables.contact.contact_enterprise_sales %}. Para obtener más información sobre estas características, consulte ["Acerca de {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Conexión de la cuenta empresarial a {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For more information about {% data variables.product.prodname_ghe_server %}, and for a list of supported virtualization platforms, see "[About {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)."
|
||||
|
||||
También hay pruebas disponibles para {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulte "[Configuración de una evaluación gratuita de {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)".
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
|
||||
Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## Configurar tu prueba de {% data variables.product.prodname_ghe_server %}
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} está instalado como aparato virtual. Determine quién es la mejor persona de su organización para configurar una máquina virtual y pida a esa persona que envíe una [solicitud de evaluación gratuita](https://enterprise.github.com/trial). Puedes comenzar tu prueba de forma inmediata después de enviar una solicitud.
|
||||
{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
|
||||
|
||||
Para configurar una cuenta para el {% data variables.product.prodname_enterprise %} portal web, haz clic en el enlace del correo electrónico que recibiste después de enviar tu solicitud de prueba y sigue las instrucciones. A continuación, descarga tu archivo de licencia. Para obtener más información, consulte "[Administración de la licencia de {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)".
|
||||
To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
|
||||
|
||||
Para instalar {% data variables.product.prodname_ghe_server %}, descarga los elementos necesarios y carga tu archivo de licencia. Para obtener más información, consulte las instrucciones de la plataforma de visualización elegida en "[Configuración de una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)".
|
||||
To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
|
||||
## Pasos siguientes
|
||||
## Next steps
|
||||
|
||||
Para sacar el mejor provecho de tu prueba, sigue los siguientes pasos:
|
||||
To get the most out of your trial, follow these steps:
|
||||
|
||||
1. [Cree una organización](/enterprise-server@latest/admin/user-management/creating-organizations).
|
||||
2. Para aprender lo básico para usar {% data variables.product.prodname_dotcom %}, consulta lo siguiente:
|
||||
- Webcast [Introducción a {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/)
|
||||
- Guías de [descripción del flujo de {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow/) en {% data variables.product.prodname_dotcom %}
|
||||
- Guías de [Hola mundo](https://guides.github.com/activities/hello-world/) en {% data variables.product.prodname_dotcom %}
|
||||
- "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
|
||||
3. Para configurar la instancia a fin de satisfacer las necesidades de su organización, consulte "[Configuración de la empresa](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)".
|
||||
4. Para integrar {% data variables.product.prodname_ghe_server %} con el proveedor de identidades, consulte "[Uso de SAML](/enterprise-server@latest/admin/user-management/using-saml)" y "[Uso de LDAP](/enterprise-server@latest/admin/authentication/using-ldap)".
|
||||
5. Invita a una cantidad ilimitada de personas a unirse a tu prueba.
|
||||
- Agregar usuarios a tu instancia {% data variables.product.prodname_ghe_server %} utilizando la autenticación incorporada o tu proveedor de identidad configurado. Para obtener más información, consulte "[Uso de la autenticación integrada](/enterprise-server@latest/admin/user-management/using-built-in-authentication)".
|
||||
- Para invitar a los usuarios a convertirse en administradores de cuentas, visite el [portal web de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/login).
|
||||
1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
|
||||
2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
|
||||
- [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast
|
||||
- [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
|
||||
3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
|
||||
4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
|
||||
5. Invite an unlimited number of people to join your trial.
|
||||
- Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
|
||||
- To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Las personas a las que invite a convertirse en administradores de cuenta recibirán un correo electrónico con un vínculo para aceptar la invitación.
|
||||
**Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## Terminar tu prueba
|
||||
## Finishing your trial
|
||||
|
||||
Puede actualizar a licencias completas en el [portal web de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/login) en cualquier momento durante el periodo de evaluación gratuita.
|
||||
You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
|
||||
|
||||
Si no has subido la categoría para el último día de tu prueba, recibirás un correo electrónico notificando que tu prueba ha terminado. Si necesitas más tiempo para evaluar {% data variables.product.prodname_enterprise %}, contacta a {% data variables.contact.contact_enterprise_sales %} para solicitar una extensión.
|
||||
If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Configuración de una evaluación gratuita de {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
|
||||
- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Acerca de las organizaciones
|
||||
intro: 'Las organizaciones son cuentas compartidas en las que las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez, con características sofisticadas de seguridad y administrativas.'
|
||||
title: About organizations
|
||||
intro: 'Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.'
|
||||
redirect_from:
|
||||
- /articles/about-organizations
|
||||
- /github/setting-up-and-managing-organizations-and-teams/about-organizations
|
||||
@@ -12,48 +12,48 @@ versions:
|
||||
topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
ms.openlocfilehash: e18c95475e06db0623aee67515eeb6d8a1ee641f
|
||||
ms.sourcegitcommit: e98b752895109965b32cb277610985da5799f8a1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/01/2022
|
||||
ms.locfileid: '148127639'
|
||||
---
|
||||
## Acerca de las organizaciones
|
||||
|
||||
{% data reusables.organizations.about-organizations %} Para obtener más información sobre los tipos de cuenta, vea "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
|
||||
## About organizations
|
||||
|
||||
Puedes invitar a un número ilimitado de personas a unirse a tu organización y, después, proporcionar a estos miembros una variedad de roles que conceden distintos niveles de acceso a la organización y sus datos. Para más información, vea "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
|
||||
{% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
|
||||
|
||||
Además de administrar el acceso a la propia organización, puedes administrar por separado el acceso a los repositorios, paneles de proyecto y aplicaciones de la organización. Para obtener más información, consulta "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Permisos de panel de proyecto para una organización](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)" y "[Administración del acceso a las aplicaciones de la organización](/organizations/managing-access-to-your-organizations-apps)".
|
||||
You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
|
||||
Para simplificar la administración de acceso y mejorar la colaboración, puedes crear equipos anidados que reflejen la estructura del grupo, con permisos de acceso en cascada y menciones. Para más información, vea "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)".
|
||||
In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)", and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)."
|
||||
|
||||
Puedes configurar la organización para satisfacer las necesidades únicas del grupo administrando la configuración, como restringir los tipos de repositorios que los miembros pueden crear. Para obtener más información, consulta "[Administración de la configuración de una organización](/organizations/managing-organization-settings)".
|
||||
To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
|
||||
|
||||
Para proteger la seguridad de la organización, puedes aplicar los requisitos de seguridad y revisar el registro de auditoría de esta. Para obtener más información, consulte "[Protección de la organización](/organizations/keeping-your-organization-secure)".
|
||||
You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "[Managing organization settings](/organizations/managing-organization-settings)."
|
||||
|
||||
{% data reusables.organizations.org-ownership-recommendation %} Para obtener más información, vea "[Mantener la continuidad de la propiedad para su organización](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)".
|
||||
To harden your organization's security, you can enforce security requirements and review the organization's audit log. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
|
||||
|
||||
To learn how to use organizations most effectively, see "[Best practices for organizations](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Acerca de la disponibilidad de características
|
||||
## About feature availability
|
||||
|
||||
{% data reusables.organizations.organization-plans %} {% endif %}
|
||||
{% data reusables.organizations.organization-plans %}
|
||||
{% endif %}
|
||||
|
||||
## Organizaciones y cuentas de empresa
|
||||
## Organizations and enterprise accounts
|
||||
|
||||
{% ifversion fpt %} Las cuentas de empresa son una característica de {% data variables.product.prodname_ghe_cloud %} que permiten a los propietarios administrar de forma centralizada la directiva y la facturación de varias organizaciones. Para obtener más información, vea la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
|
||||
{% else %} {% ifversion ghec %}En el caso de las organizaciones que pertenecen a una cuenta de empresa, la facturación se administra en el nivel de cuenta de empresa y la configuración de facturación no está disponible en el nivel de organización.{% endif %} Los propietarios de empresas pueden establecer la directiva para todas las organizaciones de la cuenta de empresa o permitir que los propietarios de la organización establezcan la directiva en el nivel de organización. Los propietarios de la organización no pueden cambiar los parámetros implementados para tu organización en el nivel de cuenta de empresa. Si tienes consultas sobre una política o la configuración para tu organización, comunícate con el propietario de tu cuenta de empresa.
|
||||
{% ifversion fpt %}
|
||||
Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
|
||||
{% else %}
|
||||
{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
|
||||
|
||||
{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} Para obtener más información, vea "[Crear una cuenta de empresa](/admin/overview/creating-an-enterprise-account)".
|
||||
{% ifversion ghec %}
|
||||
{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
|
||||
|
||||
{% data reusables.enterprise-accounts.invite-organization %}
|
||||
|
||||
{% endif %} {% endif %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Términos de servicio y protección de datos para organizaciones
|
||||
## Terms of service and data protection for organizations
|
||||
|
||||
Una entidad, como una empresa, una organización sin fines de lucro o un grupo, puede aceptar los Términos de servicio estándar o los Términos de servicio corporativos para su organización. Para obtener más información, vea "[Actualizar a los términos del servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)".
|
||||
An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -16,6 +16,7 @@ topics:
|
||||
children:
|
||||
- /about-organizations
|
||||
- /about-your-organization-dashboard
|
||||
- /best-practices-for-organizations
|
||||
- /creating-a-new-organization-from-scratch
|
||||
- /accessing-your-organizations-settings
|
||||
- /customizing-your-organizations-profile
|
||||
|
||||
@@ -1,134 +1,135 @@
|
||||
---
|
||||
title: About custom repository roles
|
||||
intro: You can more granularly control access to your organization's repositories with custom repository roles.
|
||||
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.
|
||||
versions:
|
||||
feature: custom-repository-roles
|
||||
topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
shortTitle: About custom roles
|
||||
ms.openlocfilehash: c4e7f791b9402b45160b31aab2653bf80150ddee
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160692'
|
||||
---
|
||||
|
||||
{% data reusables.organizations.custom-repo-roles-ghec-only %}
|
||||
|
||||
## About custom repository roles
|
||||
## Acerca de los roles de repositorio personalizados
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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)."
|
||||
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)".
|
||||
|
||||
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).
|
||||
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)".
|
||||
|
||||
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)."
|
||||
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)".
|
||||
|
||||
{% ifversion custom-repo-role-api %}
|
||||
|
||||
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)."
|
||||
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)".
|
||||
|
||||
{% else %}
|
||||
|
||||
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)."
|
||||
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)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
## About the inherited role
|
||||
## Acerca del rol heredado
|
||||
|
||||
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)."
|
||||
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)".
|
||||
|
||||
Your options for the inherited role are standardized for different types of contributors in your repository.
|
||||
Tus opciones para escoger el rol heredado se estandarizan para tipos diferentes de contribuyentes en tu repositorio.
|
||||
|
||||
| Inherited role | Designed for |
|
||||
| Rol heredado | Diseñada para |
|
||||
|----|----|
|
||||
| **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 |
|
||||
| **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 |
|
||||
|
||||
## Custom role examples
|
||||
## Roles personalizados de ejemplo
|
||||
|
||||
Here are some examples of custom repository roles you can configure.
|
||||
Aquí te mostramos ejemplos de los roles de repositorio personalizados que puedes configurar.
|
||||
|
||||
| Custom repository role | Summary | Inherited role | Additional permissions |
|
||||
| Rol de repositorio personalizado | Resumen | Rol heredado | Permisos adicionales |
|
||||
|----|----|----|----|
|
||||
| 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 <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
|
||||
| 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 <br> - Administrar la configuración de la página de GitHub <br> - Administrar la configuración de la wiki <br> - Establecer la versión preliminar social <br> - Editar metadatos del repositorio <br> - Discusiones de evaluación de prioridades |
|
||||
|
||||
## Additional permissions for custom roles
|
||||
## Permisos adicionales para los roles personalizados
|
||||
|
||||
After choosing an inherited role, you can select additional permissions for your custom role.
|
||||
Después de haber elegido un rol heredado, puedes seleccionar los permisos adicionales para tu rol personalizado.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
{% ifversion discussions %}
|
||||
### Discussions
|
||||
### Debates
|
||||
|
||||
- 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
|
||||
- Crear una categoría de debate
|
||||
- Editar una categoría de debate
|
||||
- Eliminar una categoría de debate
|
||||
- Marcar o desmarcar respuestas de debate
|
||||
- Ocultar o mostrar comentarios de debate
|
||||
- Convertir incidencias en debates
|
||||
|
||||
For more information, see "[{% data variables.product.prodname_discussions %}](/discussions)."
|
||||
Para más información, vea "[{% data variables.product.prodname_discussions %}](/discussions)".
|
||||
{% endif %}
|
||||
|
||||
### Issue and Pull Requests
|
||||
### Propuestas y solicitudes de cambios
|
||||
|
||||
- Assign or remove a user
|
||||
- Add or remove a label
|
||||
- Asignar o quitar un usuario
|
||||
- Adición o eliminación de etiquetas
|
||||
|
||||
### Issue
|
||||
### Problema
|
||||
|
||||
- Close an issue
|
||||
- Reopen a closed issue
|
||||
- Delete an issue
|
||||
- Mark an issue as a duplicate
|
||||
- Cerrar una incidencia
|
||||
- Volver a abrir una incidencia que se había cerrado
|
||||
- Eliminar una incidencia
|
||||
- Marcar una incidencia como duplicada
|
||||
|
||||
### Pull Request
|
||||
### Solicitud de incorporación de cambios
|
||||
|
||||
- Close a pull request
|
||||
- Reopen a closed pull request
|
||||
- Request a pull request review
|
||||
- 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 extracción
|
||||
|
||||
### Repository
|
||||
### Repositorio
|
||||
|
||||
- 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 %}
|
||||
- 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 hitos
|
||||
- Administrar la configuración de la wiki
|
||||
- Administrar la configuración del proyecto
|
||||
- Administrar la configuración de combinación de solicitudes de incorporación de cambios
|
||||
- Administrar la configuración de {% data variables.product.prodname_pages %} (consulte "[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
|
||||
- Administrar las claves de implementación
|
||||
- Editar metadatos del repositorio {%- ifversion ghec %}
|
||||
- Establecer límites de interacción {%- endif %}
|
||||
- Establecer la versión preliminar social
|
||||
- Confirmaciones de inserción en ramas protegidas (se seguirán aplicando reglas de protección de ramas)
|
||||
- Crear etiquetas protegidas
|
||||
- Eliminar etiquetas protegidas {%- ifversion bypass-branch-protections %}
|
||||
- Omitir protecciones de rama {%- endif %}
|
||||
|
||||
### Security
|
||||
### Seguridad
|
||||
|
||||
- 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
|
||||
- Ver {% data variables.product.prodname_code_scanning %} results
|
||||
- Descartar o volver a abrir los resultados de {% data variables.product.prodname_code_scanning %}
|
||||
- Eliminar {% data variables.product.prodname_code_scanning %} results
|
||||
- Ver {% data variables.product.prodname_dependabot_alerts %}
|
||||
- Descartar o volver a abrir {% data variables.product.prodname_dependabot_alerts %}
|
||||
- Ver los resultados de {% data variables.product.prodname_secret_scanning %}
|
||||
- Descartar o volver a abrir los resultados de {% data variables.product.prodname_secret_scanning %}
|
||||
|
||||
## Precedence for different levels of access
|
||||
## Precedencia de los distintos niveles de acceso
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
{% data reusables.organizations.mixed-roles-warning %}
|
||||
|
||||
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)"
|
||||
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)"
|
||||
|
||||
@@ -13,6 +13,7 @@ topics:
|
||||
- Repositories
|
||||
children:
|
||||
- /about-repositories
|
||||
- /best-practices-for-repositories
|
||||
- /creating-a-new-repository
|
||||
- /creating-a-repository-from-a-template
|
||||
- /creating-a-template-repository
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Acerca de los archivos README
|
||||
intro: 'Puedes agregar un archivo README a tu repositorio para comentarle a otras personas por qué tu proyecto es útil, qué pueden hacer con tu proyecto y cómo lo pueden usar.'
|
||||
title: About READMEs
|
||||
intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
|
||||
redirect_from:
|
||||
- /articles/section-links-on-readmes-and-blob-pages
|
||||
- /articles/relative-links-in-readmes
|
||||
@@ -14,31 +14,25 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
ms.openlocfilehash: 7a18ed7051b0babdb5408821ce44a728968869d5
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148110133'
|
||||
---
|
||||
## Acerca de los archivos README
|
||||
## About READMEs
|
||||
|
||||
Puedes agregar un archivo README a un repositorio para comunicar información importante sobre tu proyecto. Un archivo LÉAME, junto con una licencia de repositorio, un archivo de cita{% ifversion fpt or ghec %}, instrucciones de contribución y un código de conducta{% elsif ghes %} e instrucciones de contribución{% endif %}, comunica las expectativas de tu proyecto y te ayuda a administrar las contribuciones.
|
||||
{% data reusables.repositories.about-READMEs %}
|
||||
|
||||
Para obtener más información sobre cómo proporcionar instrucciones para el proyecto, consulta {% ifversion fpt or ghec %}"[Adición de un código de conducta al proyecto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y {% endif %}"[Configuración del proyecto para contribuciones correctas](/communities/setting-up-your-project-for-healthy-contributions)".
|
||||
For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
|
||||
|
||||
Un archivo README suele ser el primer elemento que verá un visitante cuando entre a tu repositorio. Los archivos README habitualmente incluyen información sobre:
|
||||
- Qué hace el proyecto.
|
||||
- Por qué el proyecto es útil.
|
||||
- Cómo pueden comenzar los usuarios con el proyecto.
|
||||
- Dónde pueden recibir ayuda los usuarios con tu proyecto
|
||||
- Quién mantiene y contribuye con el proyecto.
|
||||
A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
|
||||
- What the project does
|
||||
- Why the project is useful
|
||||
- How users can get started with the project
|
||||
- Where users can get help with your project
|
||||
- Who maintains and contributes to the project
|
||||
|
||||
Si colocas tu archivo README en el directorio `.github`, raíz o `docs` oculto de tu repositorio, {% data variables.product.product_name %} lo reconocerá y automáticamente expondrá tu archivo README a los visitantes del repositorio.
|
||||
If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
|
||||
|
||||
Si un repositorio contiene más de un archivo README, el archivo que se muestra se elige de las ubicaciones en el siguiente orden: el directorio `.github`, luego el directorio raíz del repositorio y finalmente el directorio `docs`.
|
||||
If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
@@ -46,28 +40,30 @@ Si un repositorio contiene más de un archivo README, el archivo que se muestra
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
## Índice auto-generado de los archivos README
|
||||
## Auto-generated table of contents for README files
|
||||
|
||||
Para la versión interpretada de cualquier archivo de lenguaje de marcado en un repositorio, incluyendo los archivos README, {% data variables.product.product_name %} generará un índice automáticamente con base en los encabezados de sección. Puedes ver el índice de un archivo README si haces clic en el icono de menú {% octicon "list-unordered" aria-label="The unordered list icon" %} en la parte superior izquierda de la página interpretada.
|
||||
For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %} menu icon at the top left of the rendered page.
|
||||
|
||||
|
||||
|
||||
|
||||
## Enlaces de sección en los archivos README y las páginas blob
|
||||
## Section links in README files and blob pages
|
||||
|
||||
{% data reusables.repositories.section-links %}
|
||||
|
||||
## Enlaces relativos y rutas con imágenes en los archivos README
|
||||
## Relative links and image paths in README files
|
||||
|
||||
{% data reusables.repositories.relative-links %}
|
||||
|
||||
## Wikis
|
||||
|
||||
Un archivo README debe contener solo la información necesaria para que los desarrolladores comiencen a hacer contribuciones en tu proyecto. La documentación más grande es mejor para los wikis. Para obtener más información, consulta "[Acerca de las wikis](/communities/documenting-your-project-with-wikis/about-wikis)".
|
||||
A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)"
|
||||
- 18F's "[Convertir en legible archivos READMEs](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" {%- ifversion fpt or ghec %}
|
||||
- "[Adición de un distintivo "Abrir en GitHub Codespaces"](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)" {%- endif %}
|
||||
- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
|
||||
- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
|
||||
{%- ifversion fpt or ghec %}
|
||||
- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
|
||||
{%- endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Revisión de dependencias
|
||||
intro: 'La API de Revisión de dependencias permite comprender los cambios de dependencia, y el impacto en la seguridad de estos cambios, antes de agregarlos al entorno.'
|
||||
title: Dependency review
|
||||
intro: 'The Dependency review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.6'
|
||||
@@ -10,15 +10,8 @@ topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 64cb77b737927e8d44315fd40b51f68c77c50c54
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147064878'
|
||||
---
|
||||
## Acerca de Dependency review API
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-api-beta-note %}
|
||||
## About the Dependency review API
|
||||
|
||||
La API de Revisión de dependencias permite comprender los cambios de dependencia, y el impacto en la seguridad de estos cambios, antes de agregarlos al entorno. Puede ver la diferencia de dependencias entre dos confirmaciones de un repositorio, incluidos los datos de vulnerabilidad de las actualizaciones de versiones con vulnerabilidades conocidas. Para obtener 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)".
|
||||
The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
|
||||
@@ -11,25 +11,25 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4fa9e97ca9fa3803cfbd0cf0e21d3d2253a7aa60
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: aa139c0d25354260ccf688079f3e15a871b627bd
|
||||
ms.sourcegitcommit: 0ed77777360ec29eee7cd4fc212ae36fdd97c0bc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146769161'
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: '148160966'
|
||||
---
|
||||
<div class="jumbotron libraries-jumbotron">
|
||||
<img src="/assets/images/gundamcat.png" class="gundamcat" alt="The Gundamcat" />
|
||||
<h1>El Octokit tiene muchos sabores</h1>
|
||||
<p class="lead">Utiliza la biblioteca oficial de Octokit, o elige entre cualquiera de las bibliotecas de terceros disponibles.</p>
|
||||
<div class="octokit-links"><br/>
|
||||
<div class="octokit-language"><span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
|
||||
<div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
|
||||
<div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
# Bibliotecas de terceros
|
||||
## El Octokit tiene muchos sabores
|
||||
|
||||
Utiliza la biblioteca oficial de Octokit, o elige entre cualquiera de las bibliotecas de terceros disponibles.
|
||||
|
||||
- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
|
||||
## Bibliotecas de terceros
|
||||
|
||||
### Clojure
|
||||
|
||||
@@ -130,6 +130,7 @@ ms.locfileid: '146769161'
|
||||
|**octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub)|
|
||||
|**github-flask**|[github-flask (sitio web oficial)](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1,9 @@
|
||||
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.
|
||||
---
|
||||
ms.openlocfilehash: 982b04961e4f780a5f1e284dad5620157f68569b
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: "148161066"
|
||||
---
|
||||
Para los lenguajes compilados compatibles, puedes utilizar la acción `autobuild` en {% data variables.code-scanning.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.
|
||||
@@ -1,4 +1,12 @@
|
||||
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.
|
||||
---
|
||||
ms.openlocfilehash: e6d7a33506174bf50d70ae9b5d4ac9857cd880ae
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: "148161242"
|
||||
---
|
||||
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.
|
||||
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
|
||||
@@ -9,7 +17,7 @@
|
||||
> POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms
|
||||
> Successfully uploaded results
|
||||
```
|
||||
2. To upload {% data variables.product.prodname_code_scanning %} results as pull request checks, specify the pull request using the <nobr>`--ref`</nobr> 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.
|
||||
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 <nobr>`--ref`</nobr>. Se recomienda configurar {% data variables.code-scanning.codeql_runner %} para que se ejecute en el evento de webhook [`pull_request`](/developers/webhooks-and-events/webhook-events-and-payloads#pull_request).
|
||||
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
|
||||
@@ -21,4 +29,4 @@
|
||||
> Successfully uploaded results
|
||||
```
|
||||
|
||||
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)."
|
||||
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)".
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 323e67dec23f2baa8b6e43779ed89e549d5ca198
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160788"
|
||||
---
|
||||
Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden usar {% data variables.product.prodname_copilot %}.
|
||||
@@ -1,13 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: d1a631c8bcd74e56e3bd849292180f341f0ee75e
|
||||
ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: "147878604"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Nota**: La API de revisión de dependencias está actualmente en versión beta pública y está sujeta a cambios.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 7527008260476000ac3460c800abd76b2fb202fe
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.openlocfilehash: b1c9d6341bb404267c34fa75e1a9c4c5eb401956
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: "145070015"
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160854"
|
||||
---
|
||||
{% ifversion ghec%} {% note %}
|
||||
|
||||
**Nota**: Si en la empresa se usa {% data variables.product.prodname_emus %}, no puede utilizar la sincronización de equipos y, en su lugar, tendrá que configurar SCIM para administrar la pertenencia con el proveedor de identidades. Para más información, vea "[Configuración del aprovisionamiento de SCIM para usuarios administrados de la empresa](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)".
|
||||
**Nota**: Si la empresa usa {% data variables.product.prodname_emus %}, no es necesario usar la sincronización de equipos. En su lugar, puede administrar la pertenencia al equipo a través de la configuración de SCIM que creó al configurar la empresa. 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)".
|
||||
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
{% 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 %}<br><br>
|
||||
---
|
||||
ms.openlocfilehash: c408676063e80cca29eb7392181c00c4ecf7f76d
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160785"
|
||||
---
|
||||
{% 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 reusables.copilot.emus-cannot-use-copilot %}<br><br>
|
||||
|
||||
{% 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)."
|
||||
{% data variables.product.prodname_copilot %} es gratis para los alumnos comprobados, profesores y los mantenedores de proyectos populares de código abierto. Si no eres alumno, profesor, 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)".
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 3492d399c754d53fea2091a08c95b212455a8e18
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160784"
|
||||
---
|
||||
La conexión usa HTTPS a través de los puertos 443 o 80 y está protegido por TLS.
|
||||
@@ -1,12 +1,11 @@
|
||||
---
|
||||
ms.openlocfilehash: dc6bad5b656bb5d755196146b017213b66d1730e
|
||||
ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
|
||||
ms.openlocfilehash: adefefb787099214cf17f7b2276a8f44f3fe8e56
|
||||
ms.sourcegitcommit: f54d01e643f994ce48f0774dbc680ad77dd6193f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "147884724"
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160576"
|
||||
---
|
||||
1. Para configurar tu clave de firma SSH en Git, pega el texto siguiente en sustitución del contenido del Portapapeles de la clave que quieras utilizar. Dado que la clave contiene espacios, debes ponerlo entre comillas:
|
||||
1. Para configurar tu clave de firma SSH en Git, pega el texto siguiente sustituyendo **/PATH/TO/KEY.PUB** por la ruta de la clave pública que quieras utilizar.
|
||||
```bash
|
||||
$ git config --global user.signingkey 'ssh-ed25519 AAAAC3(...) user@example.com'
|
||||
```
|
||||
$ git config --global user.signingkey=/PATH/TO/.SSH/KEY.PUB
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 85c7f83e66e8519c6d62346fe69b6e3f0b413ff1
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 478008cfe79ec4fe3c32c154af38692879f5c807
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147419900"
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160781"
|
||||
---
|
||||
{% warning %}
|
||||
|
||||
**Advertencia:** Si adjuntas un archivo a una solicitud de incorporación de cambios, al comentario de una incidencia o a un vale en {% data variables.contact.support_portal %}, cualquiera podrá ver la URL anonimizada sin autenticación, incluso si la solicitud de incorporación de cambios se encuentra en un repositorio privado{% ifversion ghes %}, o si se ha habilitado el modo privado{% endif %}. Para mantener privados archivos de medios sensibles, estos se deben servir desde una red o servidor privados que requieran autenticación. {% ifversion fpt or ghec %}Para más información sobre las direcciones URL anonimizadas,vea "[Acerca de las direcciones URL anonimizadas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
|
||||
**Advertencia:** Cuando carga una imagen o vídeo a una solicitud de incorporación de cambios o un comentario de incidencia, o carga un archivo a un vale en {% data variables.contact.support_portal %}, cualquiera podrá ver la URL anonimizada sin autenticación, incluso si la solicitud de incorporación de cambios o incidencia se encuentra en un repositorio privado{% ifversion ghes %}, o si se ha habilitado el modo privado{% endif %}. Para mantener privados archivos de medios sensibles, estos se deben servir desde una red o servidor privados que requieran autenticación. {% ifversion fpt or ghec %}Para más información sobre las direcciones URL anonimizadas,vea "[Acerca de las direcciones URL anonimizadas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -1,12 +1,20 @@
|
||||
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).
|
||||
---
|
||||
ms.openlocfilehash: d077bcd717f353297cf908b1261c821a4e759b78
|
||||
ms.sourcegitcommit: f0ae3d979782cb532427c0df026d25bfd0d0db80
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160464"
|
||||
---
|
||||
Agregamos asesorías a la {% data variables.product.prodname_advisory_database %} desde los siguientes orígenes:
|
||||
- Asesorías de seguridad que se reportan en {% data variables.product.prodname_dotcom %}
|
||||
- La [base de datos de vulnerabilidades nacional](https://nvd.nist.gov/)
|
||||
- La [base de datos de advertencias de seguridad de npm](https://github.com/advisories?query=type%3Areviewed+ecosystem%3Anpm)
|
||||
- La [base de datos FriendsOfPHP](https://github.com/FriendsOfPHP/security-advisories)
|
||||
- La [base de datos Go Vulncheck](https://pkg.go.dev/golang.org/x/vuln/vulncheck)
|
||||
- La [base de datos de asesoramiento de empaquetado de Python](https://github.com/pypa/advisory-database)
|
||||
- La [base de datos de asesoramiento de Ruby](https://rubysec.com/)
|
||||
- La [base de datos de asesoramiento de RustSec](https://rustsec.org/)
|
||||
- Aportaciones de la comunidad. Para más información, vea [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).
|
||||
Si conoce otra base de datos de la que deberíamos importar avisos, háganoslo saber si abre un problema en [https://github.com/github/advisory-database](https://github.com/github/advisory-database).
|
||||
|
||||
@@ -66,24 +66,35 @@ The custom label is created and assigned to the self-hosted runner. Custom label
|
||||
1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.actions.actions-unused-labels %}
|
||||
{% endif %}
|
||||
|
||||
## Using the configuration script to create and assign labels
|
||||
## Programmatically assign labels
|
||||
|
||||
You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner.
|
||||
You can programmatically assign labels to a self-hosted runner after the runner is created, or during its initial configuration.
|
||||
|
||||
```shell
|
||||
./config.sh --labels gpu
|
||||
```
|
||||
* To programmatically assign labels to an existing self-hosted runner, you must use the REST API. For more information, see the "[Self-hosted runners](/rest/actions/self-hosted-runners)" REST API.
|
||||
* To programmatically assign labels to a self-hosted runner during the initial runner configuration, you can pass label names to the `config` script using the `labels` parameter.
|
||||
|
||||
The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
|
||||
{% note %}
|
||||
|
||||
**Note:** You cannot use the `config` script to assign labels to an existing self-hosted runner.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use comma separation to assign multiple labels. For example:
|
||||
For example, this command assigns a label named `gpu` when configuring a new self-hosted runner:
|
||||
|
||||
```shell
|
||||
./config.sh --labels gpu,x64,linux
|
||||
```
|
||||
```
|
||||
./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu
|
||||
```
|
||||
|
||||
{% note %}
|
||||
The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
|
||||
|
||||
** Note:** If you replace an existing runner, then you must reassign any custom labels.
|
||||
You can use comma separation to assign multiple labels. For example:
|
||||
|
||||
{% endnote %}
|
||||
```
|
||||
./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu,x64,linux
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
** Note:** If you replace an existing runner, then you must reassign any custom labels.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing GitHub Connect
|
||||
title: GitHub Connect の管理
|
||||
shortTitle: Manage GitHub Connect
|
||||
intro: 'You can enable {% data variables.product.prodname_github_connect %} to access additional features and workflows for {% data variables.location.product_location %}.'
|
||||
intro: '{% data variables.product.prodname_github_connect %} を有効にすると、{% data variables.location.product_location %}の追加の機能とワークフローにアクセスできます。'
|
||||
redirect_from:
|
||||
- /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com
|
||||
- /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com
|
||||
@@ -20,71 +20,65 @@ topics:
|
||||
- GitHub Connect
|
||||
- Infrastructure
|
||||
- Networking
|
||||
ms.openlocfilehash: 30a170543b63c390aa8975b1ca57c265bc7fa8fa
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160650'
|
||||
---
|
||||
|
||||
{% data reusables.github-connect.beta %}
|
||||
|
||||
## About {% data variables.product.prodname_github_connect %}
|
||||
## {% data variables.product.prodname_github_connect %} について
|
||||
|
||||
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)."
|
||||
{% data variables.product.prodname_github_connect %} を有効にすると、{% data variables.location.product_location %}の追加の機能とワークフローにアクセスできます。 詳しい情報については、「[{% 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 %}. {% data reusables.github-connect.connection-port-protocol %}
|
||||
{% data variables.product.prodname_github_connect %} を有効にするときに、{% data variables.location.product_location %}と {% data variables.product.prodname_ghe_cloud %} の Organization または Enterprise アカウントとの間の接続を構成します。 {% 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 %}.
|
||||
{% data variables.product.prodname_github_connect %} を有効にすると、Organization または Enterprise アカウントによって所有された {% data variables.product.prodname_github_app %} が {% data variables.product.prodname_ghe_cloud %} 上に作成されます。 {% data variables.product.product_name %} で {% data variables.product.prodname_github_app %} の資格情報を使って {% 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 %}.
|
||||
- An authentication token, which is valid for one hour
|
||||
- A private key, which is used to generate a new authentication token
|
||||
{% ifversion ghes %}{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_github_app %} からの資格情報が保存されます。 次の資格情報が高可用性またはクラスター環境のすべてのノードにレプリケートされ、{% data variables.product.prodname_enterprise_backup_utilities %} によって作成されたスナップショットを含むすべてのバックアップに保存されます。
|
||||
- 1 時間にわたって有効な認証トークン
|
||||
- 新しい認証トークンを生成するために使われる秘密キー {% endif %}
|
||||
|
||||
## 前提条件
|
||||
|
||||
{% data variables.product.prodname_github_connect %} を使うには、{% data variables.product.prodname_dotcom_the_website %} で {% data variables.product.prodname_ghe_cloud %} を使う Organization または Enterprise アカウントを持っている必要があります。 {% data variables.product.prodname_ghe_cloud %} は、ご利用のプランに既に含まれている場合があります。 {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dotcom_the_website %} の Organization または Enterprise アカウントで IP 許可リストを使う場合は、{% data variables.location.product_location %}の IP アドレスまたはネットワークを {% data variables.product.prodname_dotcom_the_website %} の IP 許可リストに追加する必要があります。 詳しい情報については、{% data variables.product.prodname_ghe_cloud %} のドキュメントで「[Organization に対する許可 IP アドレスを管理する](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)」と「[Enterprise でセキュリティ設定のポリシーを適用する](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)」を参照してください。
|
||||
|
||||
接続を構成するには、プロキシ構成で `github.com`、`api.github.com`、`uploads.github.com` への接続が許可されている必要があります。 詳しい情報については、「[アウトバウンドの Web プロキシ サーバーの構成](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)」を参照してください。
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
## {% data variables.product.prodname_github_connect %} の有効化
|
||||
|
||||
To use {% data variables.product.prodname_github_connect %}, you must have an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. You may already have {% data variables.product.prodname_ghe_cloud %} included in your plan. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% data variables.product.prodname_ghe_cloud %} を使う Organization または Enterprise アカウントの所有者でもある Enterprise 所有者は、{% data variables.product.prodname_github_connect %} を有効にすることができます。
|
||||
|
||||
{% data variables.location.product_location %}を、Enterprise アカウントで所有していない {% data variables.product.prodname_ghe_cloud %} の Organization に接続する場合は、Organization 所有者として {% data variables.product.prodname_dotcom_the_website %} にサインインする必要があります。
|
||||
|
||||
{% data variables.location.product_location %}を、Enterprise アカウントで所有している {% data variables.product.prodname_ghe_cloud %} の Organization に、またはその Enterprise アカウント自体に接続する場合は、Enterprise 所有者として {% data variables.product.prodname_dotcom_the_website %} にサインインする必要があります。
|
||||
|
||||
{% ifversion ghes %}
|
||||
If your organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} uses IP allow lists, you must add the IP address or network for {% data variables.location.product_location %} to your IP allow list on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing allowed IP addresses for your organization](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[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-allowed-ip-addresses-for-organizations-in-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
|
||||
|
||||
To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)."
|
||||
{% endif %}
|
||||
|
||||
## Enabling {% data variables.product.prodname_github_connect %}
|
||||
|
||||
Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}.
|
||||
|
||||
If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner.
|
||||
|
||||
If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner.
|
||||
|
||||
{% ifversion ghes %}
|
||||
1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
|
||||
1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. {% data variables.location.product_location %}と {% data variables.product.prodname_dotcom_the_website %} にサインインします。
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
|
||||
1. {% data variables.location.product_location %}と {% data variables.product.prodname_dotcom_the_website %} にサインインします。
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
|
||||
1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features</a>."
|
||||
{% ifversion ghes %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Next to the enterprise account or organization you'd like to connect, click **Connect**.
|
||||
|
||||
1. [{% data variables.product.prodname_github_connect %} はまだ有効になっていません] で、 **[{% data variables.product.prodname_github_connect %} を有効にする]** をクリックします。 **[{% data variables.product.prodname_github_connect %} を有効にする]** をクリックすると、「<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %} 追加製品および機能の利用規約</a>」に同意したことになります。
|
||||
{% ifversion ghes %} {% else %}  {% endif %}
|
||||
1. 接続しようとする Enterprise アカウントまたは Organization の横にある **[接続]** をクリックします。
|
||||
|
||||
|
||||
## Disabling {% data variables.product.prodname_github_connect %}
|
||||
## {% data variables.product.prodname_github_connect %} を無効にする
|
||||
|
||||
Enterprise owners can disable {% data variables.product.prodname_github_connect %}.
|
||||
Enterprise 所有者は {% data variables.product.prodname_github_connect %} を無効にすることができます。
|
||||
|
||||
When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.location.product_location %} are deleted.
|
||||
{% data variables.product.prodname_ghe_cloud %} から切断すると、Enterprise アカウントまたは Organization から {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} が削除され、{% data variables.location.product_location %}に保存されている資格情報が削除されます。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.github-connect-tab %}
|
||||
1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**.
|
||||
{% ifversion ghes %}
|
||||
|
||||
1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
|
||||
|
||||
{% else %}
|
||||
|
||||
1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
|
||||
1. 切断しようとする Enterprise アカウントまたは Organization の横にある **[{% data variables.product.prodname_github_connect %} を無効にする]** をクリックします。
|
||||
{% ifversion ghes %} 
|
||||
1. 切断に関する情報を読み、 **[{% data variables.product.prodname_github_connect %} を無効にする]** をクリックします。
|
||||
|
||||
{% else %} 
|
||||
1. 切断に関する情報を読み、 **[{% data variables.product.prodname_github_connect %} を無効にする]** をクリックします。
|
||||
 {% endif %}
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Network ports
|
||||
title: ネットワーク ポート
|
||||
redirect_from:
|
||||
- /enterprise/admin/articles/configuring-firewalls
|
||||
- /enterprise/admin/articles/firewall
|
||||
@@ -8,7 +8,7 @@ redirect_from:
|
||||
- /enterprise/admin/installation/network-ports
|
||||
- /enterprise/admin/configuration/network-ports
|
||||
- /admin/configuration/network-ports
|
||||
intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
|
||||
intro: オープンするネットワークポートは、管理者、エンドユーザ、メールサポートへ公開する必要があるネットワークサービスに応じて選択してください。
|
||||
versions:
|
||||
ghes: '*'
|
||||
type: reference
|
||||
@@ -17,56 +17,62 @@ topics:
|
||||
- Infrastructure
|
||||
- Networking
|
||||
- Security
|
||||
ms.openlocfilehash: 048b27ed44cea11057c781ae3043078a825f8d1a
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160655'
|
||||
---
|
||||
## Administrative ports
|
||||
## 管理ポート
|
||||
|
||||
Some administrative ports are required to configure {% data variables.location.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
|
||||
{% data variables.location.product_location %}を構成し、特定の機能を実行するには、いくつかの管理ポートが必要です。 管理ポートは、エンドユーザが基本的なアプリケーションを利用するためには必要ありません。
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | サービス | 説明 |
|
||||
|---|---|---|
|
||||
| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
|
||||
| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless TLS is disabled manually. |
|
||||
| 122 | SSH | Shell access for {% data variables.location.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
|
||||
| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
|
||||
| 123/UDP| NTP | Required for time protocol operation. |
|
||||
| 161/UDP | SNMP | Required for network monitoring protocol operation. |
|
||||
| 8443 | HTTPS | 安全な Web ベースの {% data variables.enterprise.management_console %}。 基本的なインストールと設定に必要です。 |
|
||||
| 8080 | HTTP | プレーンテキストの Web ベースの {% data variables.enterprise.management_console %}。 TLS を手動で無効にしない限り必要ありません。 |
|
||||
| 122 | SSH | {% data variables.location.product_location %}用のシェル アクセス。 高可用性構成ではすべてのノード間の着信接続に対して開いている必要があります。 デフォルトの SSHポート (22) は Git と SSH のアプリケーションネットワークトラフィック専用です。 |
|
||||
| 1194/UDP | VPN | High Availability設定でのセキュアなレプリケーションネットワークトンネル。 構成内のすべてのノード間の通信のために開いている必要があります。|
|
||||
| 123/UDP| NTP | timeプロトコルの処理に必要。 |
|
||||
| 161/UDP | SNMP | ネットワークモニタリングプロトコルの処理に必要。 |
|
||||
|
||||
## Application ports for end users
|
||||
## エンドユーザーのためのアプリケーションポート
|
||||
|
||||
Application ports provide web application and Git access for end users.
|
||||
アプリケーションのポートは、エンドユーザーにWebアプリケーションとGitへのアクセスを提供します。
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | サービス | 説明 |
|
||||
|---|---|---|
|
||||
| 443 | HTTPS | Access to the web application and Git over HTTPS. |
|
||||
| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port if TLS is configured. |
|
||||
| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
|
||||
| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
|
||||
| 443 | HTTPS | WebアプリケーションとGit over HTTPSのアクセス。 |
|
||||
| 80 | HTTP | Web アプリケーションへのアクセス。 TLS が構成されている場合、すべての要求は HTTPS ポートにリダイレクトされます。 |
|
||||
| 22 | SSH | Git over SSH へのアクセス。 パブリックとプライベートリポジトリへの clone、fetch、push 操作をサポートします。 |
|
||||
| 9418 | Git | Gitプロトコルのポート。暗号化されないネットワーク通信でのパブリックなリポジトリへのclone及びfetch操作をサポートする。 {% data reusables.enterprise_installation.when-9418-necessary %} |
|
||||
|
||||
{% data reusables.enterprise_installation.terminating-tls %}
|
||||
|
||||
## Email ports
|
||||
## メールのポート
|
||||
|
||||
Email ports must be accessible directly or via relay for inbound email support for end users.
|
||||
メールのポートは直接あるいはエンドユーザ用のインバウンドメールサポートのリレーを経由してアクセスできなければなりません。
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | サービス | 説明 |
|
||||
|---|---|---|
|
||||
| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
|
||||
| 25 | SMTP | 暗号化ありのSMTP（STARTTLS）のサポート。 |
|
||||
|
||||
## {% data variables.product.prodname_actions %} ports
|
||||
## {% data variables.product.prodname_actions %} ポート
|
||||
|
||||
{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.location.product_location %}. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)."
|
||||
セルフホステッド ランナーが{% data variables.product.prodname_actions %}に接続されるには、{% data variables.location.product_location %} ポートへのアクセスが可能である必要があります。 詳細については、[セルフホステッド ランナー](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)に関する記述をご覧ください。
|
||||
|
||||
| Port | Service | Description |
|
||||
| Port | サービス | 説明 |
|
||||
|---|---|---|
|
||||
| 443 | HTTPS | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is configured.
|
||||
| 80 | HTTP | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured.
|
||||
| 443 | HTTPS | セルフホステッド ランナーが{% data variables.location.product_location %}に接続されると、ジョブの割り当てが送信され、ランナー アプリケーションの新しいバージョンがダウンロードされます。 TLS が構成されている場合は必須です。
|
||||
| 80 | HTTP | セルフホステッド ランナーが{% data variables.location.product_location %}に接続されると、ジョブの割り当てが送信され、ランナー アプリケーションの新しいバージョンがダウンロードされます。 TLS が構成されていない場合は必須です。
|
||||
|
||||
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_dotcom_the_website %} アクションへの自動アクセスを有効にすると、{% data variables.product.prodname_dotcom_the_website %} をチェックする前に、これらのポートを介して、常に {% data variables.product.prodname_actions %} によって、{% data variables.location.product_location %}に対するアクションの検索が最初に行われます。 詳細については、「[{% data variables.product.prodname_github_connect %} を使用して {% 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#about-resolution-for-actions-using-github-connect)」を参照してください。
|
||||
|
||||
## {% data variables.product.prodname_github_connect %} ports
|
||||
## {% data variables.product.prodname_github_connect %} ポート
|
||||
|
||||
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)."
|
||||
{% data variables.product.prodname_github_connect %} を有効にすると、{% data variables.product.product_name %} と {% data variables.product.prodname_dotcom_the_website %} の間の接続でポート 443 または 80 経由の HTTPS が使用され、TLS が必須になります。 詳しい情報については、「[{% 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)"
|
||||
- 「[TLS の設定](/admin/configuration/configuring-network-settings/configuring-tls)」
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Enterprise の認証について
|
||||
title: About authentication for your enterprise
|
||||
shortTitle: About authentication
|
||||
intro: '{% ifversion ghec %}{% data variables.product.product_name %} 上にある Enterprise のリソース{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %} 上にある Enterprise {% endif %}にユーザーがアクセスできるように{% ifversion ghae %} SAML シングル サインオン (SSO) を構成する必要があります{% else %}ユーザーを認証する方法を選ぶことができます{% data variables.product.product_name %}{% endif %}。'
|
||||
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 %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
@@ -13,140 +13,136 @@ topics:
|
||||
- Enterprise
|
||||
- Identity
|
||||
- SSO
|
||||
ms.openlocfilehash: 9931a13150ff98d7ab113d37df9622b43367fa1b
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107022'
|
||||
---
|
||||
## Enterprise の認証について
|
||||
|
||||
## About authentication for your enterprise
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data variables.product.product_name %} の Enterprise 所有者は、Enterprise のリソースに対する認証とアクセスに関する要件を制御できます。
|
||||
Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources.
|
||||
|
||||
メンバーがユーザー アカウントを作成して管理できるようにするか、Enterprise で {% data variables.product.prodname_emus %} を使用してメンバーのアカウントを作成、管理できるようにするかを選ぶことができます。 メンバーが自分のアカウントを管理できるようにする場合は、SAML 認証を構成して、チームで使用される Web アプリケーションのセキュリティを強化し、ID とアクセスを一元化することもできます。
|
||||
{% data reusables.enterprise.ghec-authentication-options %}
|
||||
|
||||
これらのオプションの詳しい情報を学習した後、Enterprise に最適な方法を決定するには、「[Enterprise に最適な認証方法を特定する](#identifying-the-best-authentication-method-for-your-enterprise)」を参照してください。
|
||||
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)."
|
||||
|
||||
## {% data variables.product.product_name %} の認証方法
|
||||
## Authentication methods for {% data variables.product.product_name %}
|
||||
|
||||
{% data variables.product.product_name %} のアカウント管理と認証には、次のオプションを使用できます。
|
||||
The following options are available for account management and authentication on {% data variables.product.product_name %}.
|
||||
|
||||
- [{% data variables.location.product_location %} による認証](#authentication-through-githubcom)
|
||||
- [追加の SAML アクセス制限を使用した {% data variables.location.product_location %} による認証](#authentication-through-githubcom-with-additional-saml-access-restriction)
|
||||
- [{% data variables.product.prodname_emus %} とフェデレーションを使用した認証](#authentication-with-enterprise-managed-users-and-federation)
|
||||
- [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)
|
||||
|
||||
### {% data variables.location.product_location %} による認証
|
||||
### Authentication through {% data variables.location.product_location %}
|
||||
|
||||
既定では、各メンバーは {% data variables.location.product_location %} に個人アカウントを作成する必要があります。 Enterprise へのアクセス権を付与すると、メンバーは {% data variables.location.product_location %} のアカウントにサインインした後、Enterprise のリソースにアクセスできます。 メンバーはアカウントを管理し、{% data variables.location.product_location %} の他の Enterprise、Organization、リポジトリに投稿できます。
|
||||
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 %}.
|
||||
|
||||
### 追加の SAML アクセス制限を使用した {% data variables.location.product_location %} による認証
|
||||
### Authentication through {% data variables.location.product_location %} with additional SAML access restriction
|
||||
|
||||
追加の SAML アクセス制限を構成する場合は、各メンバーが {% data variables.location.product_location %} の個人アカウントを作成して管理する必要があります。 Enterprise へのアクセス権を付与すると、メンバーは {% data variables.location.product_location %} のアカウントにサインインし、SAML ID プロバイダー (IdP) で正常に認証した後に、Enterprise のリソースにアクセスできます。 メンバーは個人アカウントを使用して、{% data variables.location.product_location %} の他の Enterprise、Organization、リポジトリに投稿できます。 Enterprise のリソースへのすべてのアクセスに SAML 認証を要求する方法について詳しくは、「[Enterprise IAM の SAML について](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)」を参照してください。
|
||||
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)."
|
||||
|
||||
{% data variables.product.product_name %} でスタンドアロン Organization を使用する場合、または Enterprise 内のすべての Organization に対して SAML 認証を使用しない場合は、個々の Organization に対して SAML を構成できます。 詳細については、「[SAML シングル サインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。
|
||||
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)."
|
||||
|
||||
### {% data variables.product.prodname_emus %} とフェデレーションを使用した認証
|
||||
### Authentication with {% data variables.product.prodname_emus %} and federation
|
||||
|
||||
{% data variables.location.product_location %} の Enterprise メンバーのアカウントをより細かく制御する必要がある場合は、{% data variables.product.prodname_emus %} を使用できます。 {% data variables.product.prodname_emus %} では、IdP を使用し、{% data variables.location.product_location %} の Enterprise メンバーのアカウントをプロビジョニングして管理します。 作成されたアカウントに各メンバーがサインインすると、Enterprise でそのアカウントが管理されます。 {% data variables.product.prodname_dotcom_the_website %} の残りの部分への投稿は制限されています。 詳細については、「[{% data variables.product.prodname_emus %} について](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)」を参照してください。
|
||||
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)."
|
||||
|
||||
## Enterprise に最適な認証方法を特定する
|
||||
## Identifying the best authentication method for your enterprise
|
||||
|
||||
SAML SSO と {% data variables.product.prodname_emus %} の両方で、Enterprise のリソースのセキュリティが強化されます。 さらに、{% data variables.product.prodname_emus %} を使用すると、Enterprise メンバーのユーザー アカウントを管理し、アカウントで実行できる操作を制限できます。 ただし、これらの制限によって開発者のワークフローが妨げられる場合、Enterprise ではそれらを受け入れられないことがあります。
|
||||
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.
|
||||
|
||||
Enterprise が SAML SSO と {% data variables.product.prodname_emus %} のどちらから、より多くのメリットを得られるかを判断するには、これらの質問を自問してください。
|
||||
To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions.
|
||||
|
||||
- [ユーザーのユーザー アカウントを自分で管理したいか?](#do-you-want-to-control-the-user-accounts-for-your-users)
|
||||
- [Enterprise でどの ID プロバイダーを使用するか?](#which-identity-provider-does-your-enterprise-use)
|
||||
- [開発者はパブリック リポジトリ、gist、{% data variables.product.prodname_pages %} サイトのどれで作業するか?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
|
||||
- [開発者は Enterprise 外部のコラボレーションに依存しているか?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
|
||||
- [Enterprise は外部のコラボレーターに依存しているか?](#does-your-enterprise-rely-on-outside-collaborators)
|
||||
- [会社が移行コストを許容できるか?](#can-your-enterprise-tolerate-migration-costs)
|
||||
- [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)
|
||||
|
||||
### ユーザーのユーザー アカウントを自分で管理したいか?
|
||||
### Do you want to control the user accounts for your users?
|
||||
|
||||
{% data variables.product.prodname_emus %} は、Enterprise メンバーが {% data variables.product.prodname_dotcom_the_website %} で自分の個人アカウントを使って Enterprise のリソースにアクセスすることを望まない場合に、適している可能性があります。
|
||||
{% 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.
|
||||
|
||||
SAML SSO を使用すると、開発者は自分の個人アカウントを作成して管理でき、各アカウントは IdP の SAML ID にリンクされます。 {% data variables.product.prodname_emus %} は、ご自身でユーザーのアカウントをプロビジョニングするため、他の使い慣れた SSO ソリューションと同様に機能します。 また、ユーザー名とアカウントに関連付けられるメール アドレスを管理することで、ユーザー アカウントが会社の ID に準拠していることを確実にすることもできます。
|
||||
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.
|
||||
|
||||
現在、ユーザーに対して、{% data variables.product.prodname_dotcom_the_website %} で新しいアカウントを作成して Enterprise でのみ使用するように要求している場合は、{% data variables.product.prodname_emus %} が適している可能性があります。 ただし、IdP をユーザー向けの信頼できるソースとして使用し、アクセス管理が複雑すぎる場合は、SAML SSO の方が適切なオプションである可能性があります。 たとえば、IdP で新しいユーザーをオンボードするための確立されたプロセスが Enterprise にない場合があります。
|
||||
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.
|
||||
|
||||
### Enterprise でどの ID プロバイダーを使用するか?
|
||||
### Which identity provider does your enterprise use?
|
||||
|
||||
{% data variables.product.prodname_emus %} がサポートされている IdP の数は限られています。SAML SSO を使用すると、多数の IdP に対する完全なサポートと、SAML 2.0 標準を実装しているすべての IdP に対する制限付きサポートが提供されます。 各オプションでサポートされている IdP の一覧については、「[{% 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)」および「[Enterprise IAM の SAML について](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)」を参照してください。
|
||||
{% 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)."
|
||||
|
||||
サポートされていない IdP で {% data variables.product.prodname_emus %} を使用できるのは、サポートされていない IdP をサポートされている IdP にフェデレーションして統合ポイントとして使用する場合のみです。 このような余分な複雑さを避けたい場合は、SAML SSO の方が優れたソリューションになる可能性があります。
|
||||
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.
|
||||
|
||||
### 開発者はパブリック リポジトリ、gist、{% data variables.product.prodname_pages %} サイトのどれで作業するか?
|
||||
### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?
|
||||
|
||||
Enterprise メンバーが誤って {% data variables.product.prodname_dotcom_the_website %} で Enterprise 所有のコンテンツを一般に漏洩させることがないように、{% data variables.product.prodname_emus %} では、ユーザーが実行できる操作に対して強力な制限が課されます。 たとえば、{% data variables.enterprise.prodname_managed_users %} では、パブリック リポジトリ、任意の可視性を持つ gist、または Enterprise 外部で閲覧できる {% data variables.product.prodname_pages %} サイトを作成することはできません。 制限の完全な一覧については、「[{% 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)」を参照してください。
|
||||
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)."
|
||||
|
||||
これらの制限が受け入れらない Enterprise もあります。 {% data variables.product.prodname_emus %} がご自身に適しているかどうかを判断するには、開発者と共に制限事項を確認し、いずれかの制限によって既存のワークフローが妨げられるかどうかを確認します。 該当する場合は、お使いの Enterprise には SAML SSO が適している可能性があります。
|
||||
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.
|
||||
|
||||
### 開発者は Enterprise 外部のコラボレーションに依存しているか?
|
||||
### Do your developers rely on collaboration outside of your enterprise?
|
||||
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} では、Enterprise 内部のリポジトリにのみ投稿できます。 開発者がプライベート リポジトリを含め、エンタープライズ内と外部の両方のリポジトリに投稿する必要がある場合、{% data variables.product.prodname_emus %}はエンタープライズに適していない可能性があります。 SAML SSO の方が優れたソリューションになる可能性があります。
|
||||
{% 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.
|
||||
|
||||
一部の会社では、{% data variables.location.product_location %} に SAML SSO を使用して既存の Enterprise 内のリポジトリを保持し、{% data variables.enterprise.prodname_emu_enterprise %}も作成します。 1 つのワークステーションから両方の Enterprise によって所有されるリポジトリに投稿する開発者は、1 つのブラウザー内で {% data variables.location.product_location %} のアカウントを切り替えるか、アカウントごとに異なるブラウザーを使用する必要があります。 開発者は、2 つのアカウントに対応するようにワークステーションの Git 構成をカスタマイズする必要がある場合もあります。 このワークフローの複雑さは、内部コードを誤って一般に漏洩させるリスクを高める可能性があります。
|
||||
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.
|
||||
|
||||
{% data variables.enterprise.prodname_emu_enterprise %}を作成する場合に、開発者が 1 つのワークステーションから Enterprise 外のリソースに投稿する必要がある場合は、開発者のローカル Git 構成でアカウントを切り替えるためのサポートを提供できます。 詳細については、「[{% 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)」を参照してください。
|
||||
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)."
|
||||
|
||||
### Enterprise は外部のコラボレーターに依存しているか?
|
||||
### Does your enterprise rely on outside collaborators?
|
||||
|
||||
SAML SSO を使用すると、外部コラボレーター ロールを使用して、IdP のディレクトリのメンバーではないユーザーに特定のリポジトリへのアクセスを許可できます。 これは、社外のコラボレーター (請負業者など) に対して特に役立ちます。 詳しい情報については、「[外部のコラボレーターを Organization のリポジトリに追加する](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)」を参照してください。
|
||||
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)."
|
||||
|
||||
{% data variables.product.prodname_emus %} の場合、外部コラボレーター ロールは存在しません。 Enterprise のリソースには、常に IdP によってプロビジョニングされる {% data variables.enterprise.prodname_managed_users %} のみがアクセスできます。 外部コラボレーターに Enterprise へのアクセスを許可するには、IdP でゲスト アカウントを使用する必要があります。 {% data variables.product.prodname_emus %} に関心がある場合は、開発者に、これによって既存のワークフローが妨げられるかどうかを確認してください。 該当する場合は、SAML SSO の方が優れたソリューションになる可能性があります。
|
||||
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.
|
||||
|
||||
### 会社が移行コストを許容できるか?
|
||||
### Can your enterprise tolerate migration costs?
|
||||
|
||||
会社で {% data variables.product.prodname_dotcom_the_website %} を初めて使用する場合、SAML SSO と {% data variables.product.prodname_emus %} は同じように簡単に導入できます。
|
||||
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.
|
||||
|
||||
既に {% data variables.product.prodname_dotcom_the_website %} を使用していて、開発者が各自のユーザー アカウントを管理している場合は、{% data variables.product.prodname_emus %} を導入するには、新しい Enterprise アカウントに移行する必要があります。 詳しい情報については、「[{% data variables.enterprise.prodname_managed_users %} を含む Enterprise について](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)」を参照してください。
|
||||
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)."
|
||||
|
||||
{% data variables.product.prodname_emus %} は無料ですが、移行プロセスにはチームの時間またはコストが必要になる場合があります。 この移行プロセスが、ご自身のビジネスと開発者に許容されることを確認してください。 そうでない場合は、SAML SSO が適している可能性があります。
|
||||
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.
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
サイト管理者は、ユーザーが {% data variables.product.product_name %} インスタンスにアクセスするための認証方法を決定できます。 {% data variables.product.product_name %} のビルトイン認証を使用することができます。チームで使用される Web アプリケーションの ID とアクセス管理を一元化する場合は、外部認証方法を構成できます。
|
||||
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.
|
||||
|
||||
## {% data variables.product.product_name %} の認証方法
|
||||
## Authentication methods for {% data variables.product.product_name %}
|
||||
|
||||
{% data variables.product.product_name %} では、次の認証方法を使用できます。
|
||||
The following authentication methods are available for {% data variables.product.product_name %}.
|
||||
|
||||
- [ビルトイン認証](#built-in-authentication)
|
||||
- [外部認証](#external-authentication)
|
||||
- [Built-in authentication](#built-in-authentication)
|
||||
- [External authentication](#external-authentication)
|
||||
|
||||
### ビルトイン認証
|
||||
### Built-in authentication
|
||||
|
||||
{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} インスタンスにアクセスするために、ユーザーはアカウントの資格情報を使用して認証します。 詳しくは、「[ビルトイン認証の設定](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)」を参照してください。
|
||||
{% 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)."
|
||||
|
||||
### 外部認証
|
||||
### External authentication
|
||||
|
||||
外部ディレクトリまたは ID プロバイダー (IdP) を使用して複数の Web アプリケーションへのアクセスを一元化する場合は、{% data variables.location.product_location %} の外部認証を構成できる可能性があります。 詳細については、次の記事を参照してください。
|
||||
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.
|
||||
|
||||
- [Enterprise IAM での CAS の使用](/admin/identity-and-access-management/using-cas-for-enterprise-iam)
|
||||
- 「[Enterprise IAM での LDAP の使用](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)」
|
||||
- [Enterprise IAM での SAML の使用](/admin/identity-and-access-management/using-saml-for-enterprise-iam)
|
||||
- "[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)"
|
||||
|
||||
外部認証を使用することにした場合は、外部認証プロバイダーにアカウントを持っていないユーザーのフォールバック認証を構成することもできます。 たとえば、請負業者またはコンピューター ユーザーにアクセス権を付与できます。 詳しくは、「[プロバイダー外のユーザーのためのビルトイン認証の許可](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)」を参照してください。
|
||||
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)."
|
||||
|
||||
{% ifversion scim-for-ghes %}
|
||||
|
||||
認証に SAML SSO を使用する場合は、SCIM を使用してユーザーをプロビジョニングし、IdP グループをチームにマップすることもできます。 詳しくは、「[Enterprise 用の SCIM を使用したユーザーのプロビジョニングを構成する](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)」を参照してください。
|
||||
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)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% data variables.product.product_name %}では認証に SAML SSO が使用されます。 Enterprise 所有者は、初期化中に SAML ID プロバイダー (IdP) で SAML SSO を構成する必要があります。 詳しくは、「[Enterprise IAM の SAML について](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)」を参照してください。
|
||||
{% 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)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- [{% data variables.product.company_short %} アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)
|
||||
- [Enterprise アカウントについて](/admin/overview/about-enterprise-accounts){%- ifversion ghec %}
|
||||
- [私の Organization に所属する人のためにアカウントを作成できますか?](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)
|
||||
- "[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)"
|
||||
{% endif %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About {% data variables.product.prodname_emus %}
|
||||
title: '{% data variables.product.prodname_emus %} について'
|
||||
shortTitle: About managed users
|
||||
intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
|
||||
intro: 'ID プロバイダーから {% data variables.product.prodname_dotcom %} 上のエンタープライズ メンバーの ID とアクセスを一元管理することができます。'
|
||||
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,50 +17,55 @@ topics:
|
||||
- Enterprise
|
||||
- SSO
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 82a8b8c29ea38d57f0481146f2a857c2dcba8413
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160729'
|
||||
---
|
||||
## {% data variables.product.prodname_emus %} について
|
||||
|
||||
## About {% data variables.product.prodname_emus %}
|
||||
{% data variables.product.prodname_emus %} を使用すると、ID プロバイダー (IdP) を使用して Enterprise メンバーのユーザー アカウントを制御できます。 IdP で {% data variables.product.prodname_emu_idp_application %} アプリケーションに割り当てられたユーザーは、{% data variables.product.prodname_dotcom %} の新しいユーザー アカウントとしてプロビジョニングされ、Enterprise に追加されます。 IdP からユーザー アカウントのユーザー名、プロファイル データ、チーム メンバーシップ、リポジトリへのアクセスを制御します。
|
||||
|
||||
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)."
|
||||
IdP では、各{% data variables.enterprise.prodname_managed_user %}に、ユーザー、Enterprise 所有者、または課金マネージャーのロールを付与できます。 {% data variables.enterprise.prodname_managed_users_caps %}は、Enterprise 内の Organization を所有でき、他の{% data variables.enterprise.prodname_managed_users %}を Organization とその中の Team に追加できます。 詳細については、「[Enterprise におけるロール](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)」および「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。
|
||||
|
||||
{% ifversion oidc-for-emu %}
|
||||
|
||||
{% 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)."
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %}詳細については、「[IdP の条件付きアクセス ポリシー](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)」を参照してください。
|
||||
|
||||
{% endif %}
|
||||
|
||||
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)."
|
||||
{% data variables.enterprise.prodname_managed_users %}に、Enterprise 内のリポジトリへのアクセス権と、そこに投稿する機能を付与できますが、{% data variables.enterprise.prodname_managed_users %}では、パブリック コンテンツを作成したり、残りの {% data variables.product.prodname_dotcom %} で他のユーザー、Organization、Enterprise と共同作業を行ったりすることはできません。 詳しい情報については、「[{% data variables.enterprise.prodname_managed_users %}の機能と制限](#abilities-and-restrictions-of-enterprise-managed-users)」を参照してください。
|
||||
|
||||
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)."
|
||||
Enterprise の{% data variables.enterprise.prodname_managed_users %}のユーザー名とそのプロファイル情報 (表示名やメール アドレスなど) は、IdP によって設定され、ユーザー自身が変更することはできません。 詳細については、「[ユーザー名とプロファイル情報](#usernames-and-profile-information)」を参照してください。
|
||||
|
||||
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)."
|
||||
Enterprise 所有者は、{% data variables.product.prodname_dotcom %} に対する{% data variables.enterprise.prodname_managed_users %}のすべてのアクションを監査できます。 詳細については、「[エンタープライズの監査ログ イベント](/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)」を参照してください。
|
||||
|
||||
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)."
|
||||
{% data variables.product.prodname_emus %} を使用するには、{% data variables.product.prodname_emus %} を有効にした別の種類の Enterprise アカウントが必要です。 このアカウントの作成の詳細については、「[Managed User を含む Enterprise について](#about-enterprises-with-managed-users)」を参照してください。
|
||||
|
||||
{% note %}
|
||||
|
||||
**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)."
|
||||
**注:** {% data variables.product.prodname_ghe_cloud %} を使った ID とアクセスの管理には複数のオプションがあるので、{% data variables.product.prodname_emus %} はすべてのお客様にとって最適なソリューションではありません。 {% data variables.product.prodname_emus %} がお客様の企業に適しているかどうかについては、「[企業の認証について](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)」を参照してください。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About organization membership management
|
||||
## Organization メンバーシップの管理について
|
||||
|
||||
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)."
|
||||
Organization メンバーシップは、手動で管理することも、IdP グループを使用して自動的に更新することもできます。 IdP を使用して Organization メンバーシップを管理するには、メンバーを IdP グループに追加し、IdP グループを Organization 内の Team に接続する必要があります。 Organization および Team のメンバーシップの管理に関する詳しい情報については、「[ID プロバイダー グループによる Team メンバーシップの管理](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)」を参照してください。
|
||||
|
||||
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.
|
||||
Enterprise によって所有されている Organization にメンバーを追加する方法によって、Organization からメンバーを削除する方法が決定されます。
|
||||
|
||||
- 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.
|
||||
- メンバーを手動で Organization に追加した場合、手動で削除する必要があります。 IdP 上の {% data variables.product.prodname_emu_idp_application %} アプリケーションからユーザーの割り当て解除を行うと、ユーザーは停止されますが、Organization から削除されません。
|
||||
- Organization 内の 1 つ以上の Team にマップされた IdP グループに追加されたために、ユーザーが Organization のメンバーになった場合、Organization に関連付けられている "すべて" のマップされた IdP グループからユーザーを削除すると、ユーザーは Organization から削除されます。
|
||||
|
||||
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)."
|
||||
メンバーが Organization に追加された方法を確認するには、メンバー リストを種類でフィルター処理できます。 詳細については、「[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)」 (Enterprise のメンバーを表示する) を参照してください。
|
||||
|
||||
## Identity provider support
|
||||
## ID プロバイダーのサポート
|
||||
|
||||
{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
|
||||
{% data variables.product.prodname_emus %} は、以下の IdP{% ifversion oidc-for-emu %} と認証方法をサポートしています。
|
||||
|
||||
| | SAML | OIDC (beta) |
|
||||
| | SAML | OIDC (ベータ) |
|
||||
|----------------------------------|-----------------------------------------------|-----------------------------------------------|
|
||||
| Azure Active Directory | {% octicon "check" aria-label="Check icon" %} | {% octicon "check" aria-label="Check icon" %} |
|
||||
| Okta | {% octicon "check" aria-label="Check icon" %} | |
|
||||
@@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
|
||||
## {% data variables.enterprise.prodname_managed_users %}の機能と制限
|
||||
|
||||
{% 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.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %}で投稿できるのは、その Enterprise 内のプライベートおよび内部リポジトリと、そのユーザー アカウントによって所有されているプライベート リポジトリのみです。 {% data variables.enterprise.prodname_managed_users_caps %}には、より広範な {% data variables.product.prodname_dotcom %} コミュニティへの読み取り専用アクセス権が必要です。 ユーザーとコンテンツに対するこれらの可視性とアクセスの制限は、API 要求を含むすべての要求に適用されます。
|
||||
|
||||
* {% 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 variables.enterprise.prodname_managed_users_caps %}を Enterprise 外部の Organization またはリポジトリに招待することも、{% data variables.enterprise.prodname_managed_users %}を他の Enterprise に招待することもできません。
|
||||
* 外部のコラボレーターは、{% data variables.product.prodname_emus %} ではサポートされていません。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}では、Enterprise 外部のリポジトリでの Issue または pull request の作成、Enterprise 外部のリポジトリへのリアクションの追加、Enterprise 外部のリポジトリに対する Star、Watch または Fork 操作を行うことはできません。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}で {% data variables.product.prodname_dotcom_the_website %} のすべてのパブリック リポジトリを表示することはできますが、Enterprise 外部のリポジトリにコードをプッシュすることはできません。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}と作成されたコンテンツは、その Enterprise の他のメンバーにのみ表示されます。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}では、Enterprise 外部のユーザーをフォローできません。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}では、gists を作成したり、gists に対してコメントしたりすることはできません。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}では、{% data variables.product.prodname_actions %} のスターター ワークフローを作成できません。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}では、そのユーザー アカウントに {% data variables.product.prodname_github_apps %} をインストールできません。
|
||||
* 他の {% data variables.product.prodname_dotcom %} ユーザーは、{% data variables.enterprise.prodname_managed_user %}を表示またはメンションしたり、共同作業に招待したりすることはできません。
|
||||
* ユーザー アカウントによって所有されるリポジトリを{% data variables.enterprise.prodname_managed_users %}で作成できるかどうかを選ぶことができます。 詳細については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)」を参照してください。
|
||||
* ユーザー アカウントによって所有されるリポジトリの作成を{% data variables.enterprise.prodname_managed_users %}に許可した場合、所有できるのはプライベート リポジトリのみであり、他のエンタープライズ メンバーを招待して共同作業を行うことができるのは、ユーザー所有のリポジトリのみです。
|
||||
* {% data reusables.enterprise-accounts.emu-forks %}
|
||||
* 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 variables.enterprise.prodname_emu_enterprise %} が所有する Organization では、Organization および Enterprise リポジトリの可視性の設定に応じて、プライベートおよび内部リポジトリのみを作成できます。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %}は、{% data variables.product.prodname_pages %} の使用が制限されます。 詳細については、「[{% 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 %}
|
||||
|
||||
## Getting started with {% data variables.product.prodname_emus %}
|
||||
## {% data variables.product.prodname_emus %} の概要
|
||||
|
||||
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.
|
||||
お客様の開発者が {% data variables.product.prodname_ghe_cloud %} と {% data variables.product.prodname_emus %} を使用できるようにするには、お客様が一連の構成手順を実行する必要があります。
|
||||
|
||||
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).
|
||||
1. {% data variables.product.prodname_emus %} を使用するには、{% data variables.product.prodname_emus %} を有効にした別の種類の Enterprise アカウントが必要です。 {% data variables.product.prodname_emus %} を試用するか、既存の Enterprise から移行するためのオプションについて検討するには、[{% data variables.product.prodname_dotcom %} の営業チーム](https://enterprise.github.com/contact)にお問い合わせください。
|
||||
|
||||
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)."
|
||||
GitHub セールス チームの担当者が、新しい {% data variables.enterprise.prodname_emu_enterprise %} を作成するために協力します。 Enterprise を設定するユーザーのメール アドレスと、Enterprise メンバーのユーザー名のサフィックスとして使用されるショートコードを指定する必要があります。 {% data reusables.enterprise-accounts.emu-shortcode %} 詳細については、「[ユーザー名とプロファイル情報](#usernames-and-profile-information)」を参照してください。
|
||||
|
||||
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`.
|
||||
2. Enterprise を作成すると、{% data variables.product.prodname_dotcom %} からメールが届き、Enterprise のセットアップ ユーザーのパスワードを選択するよう求められます。このユーザーは、Enterprise の最初の所有者になります。 パスワードを設定する際は、Incognito ウィンドウまたはプライベート ブラウズ ウィンドウを使用します。 セットアップ ユーザーは、エンタープライズのシングル サインオンと SCIM プロビジョニング統合を構成するためにのみ使用されます。 SSO が正常に有効になると、エンタープライズ アカウントを管理するためのアクセス権はなくなります。 セットアップ ユーザーのユーザー名は、Enterprise のショートコードにサフィックス `_admin` が付きます。
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
|
||||
|
||||
{% endnote %}
|
||||
|
||||
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)."
|
||||
3. セットアップ ユーザーとしたログインしたら、2 要素認証を有効にすることをお勧めします。 詳細については、「[2 要素認証の構成](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)」を参照してください。
|
||||
|
||||
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 %}
|
||||
1. まず、{% ifversion oidc-for-emu %}メンバーが認証する方法を構成します。 Azure Active Directory を ID プロバイダーとして使っている場合、OpenID Connect (OIDC) と Security Assertion Markup Language (SAML) のいずれかを選択できます。 どちらのオプションでもメンバーにシームレスなサインイン エクスペリエンスを提供できますが、条件付きアクセス ポリシー (CAP) のサポートが含まれているの OIDC のみです。 ID プロバイダーとして Okta を使っている場合、SAML を使ってメンバーを認証することができます。{% else %}エンタープライズ用に SAML SSO を構成します。 詳細については、「[エンタープライズ マネージド ユーザーの SAML シングル サインオンの構成](/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 %}
|
||||
|
||||
To get started, read the guide for your chosen authentication method.
|
||||
まず、選択した認証方法のガイドを参照してください。
|
||||
|
||||
- "[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)."
|
||||
- 「[エンタープライズ マネージド ユーザーの OIDC の構成](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)」
|
||||
- 「[エンタープライズ マネージド ユーザーの SAML シングル サインオンの構成](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)」
|
||||
|
||||
{% endif %}
|
||||
|
||||
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)."
|
||||
4. SSO を構成したら、SCIM のプロビジョニングを構成できます。 SCIM は、ID プロバイダーを使って {% data variables.product.prodname_dotcom_the_website %} に{% data variables.enterprise.prodname_managed_users %}を作成する方法です。 SCIM のプロビジョニングを構成する場合の詳細については、「[エンタープライズ マネージド ユーザーの SCIM プロビジョニングの構成](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)」を参照してください。
|
||||
|
||||
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)."
|
||||
5. 認証とプロビジョニングが構成されたら、IdP グループを Team と同期することで、{% data variables.enterprise.prodname_managed_users %}の Organization メンバーシップの管理を開始できます。 詳細については、「[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)」 (ID プロバイダー グループを使用して Team のメンバーシップを管理する) を参照してください。
|
||||
|
||||
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)."
|
||||
Enterprise のメンバーが 1 つのワークステーションを使って、{% data variables.enterprise.prodname_managed_user %}と個人アカウントの両方から、{% data variables.location.product_location %} のリポジトリに投稿する必要がある場合は、サポートを提供できます。 詳しくは、「[{% data variables.product.prodname_dotcom_the_website %} で複数のユーザー アカウントを持つ開発者をサポートする](#supporting-developers-with-multiple-user-accounts-on-githubcom)」をご覧ください。
|
||||
|
||||
## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
|
||||
## {% data variables.enterprise.prodname_managed_user %}として認証を行う
|
||||
|
||||
{% 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 %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %}は、ID プロバイダーを介して認証を行う必要があります。 {% data variables.enterprise.prodname_managed_user %}は、認証を行うために、IdP アプリケーション ポータルにアクセスするか、{% data variables.product.prodname_dotcom_the_website %} のログイン ページを使用できます。
|
||||
|
||||
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 variables.product.prodname_emus %} を使用する Enterprise にアクセスしようとすると、{% data variables.product.company_short %} によって 404 エラーが表示されます。 Enterprise 所有者は、必要に応じて、404 の代わりにシングル サインオン (SSO) への自動リダイレクトを有効にすることができます。 詳細については、「[エンタープライズでのセキュリティ設定のポリシーの適用](/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 %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)."
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} 詳細については、「[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)」 (Enterprise の復旧コードの管理) を参照してください。
|
||||
|
||||
### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
|
||||
### {% data variables.product.prodname_dotcom_the_website %} を介して{% data variables.enterprise.prodname_managed_user %}として認証を行う
|
||||
|
||||
1. Navigate to [https://github.com/login](https://github.com/login).
|
||||
1. In the "Username or email address" text box, enter your username including the underscore and short code.
|
||||
|
||||
When the form recognizes your username, the form will update. You do not need to enter your password on this form.
|
||||
1. To continue to your identity provider, click **Sign in with your identity provider**.
|
||||
|
||||
1. [https://github.com/login](https://github.com/login) に移動します。
|
||||
1. [Username or email address] テキスト ボックスに、アンダースコアとショートコードを含むユーザー名を入力します。
|
||||
 このフォームでユーザー名が認識されると、フォームは更新されます。 このフォームでパスワードを入力する必要はありません。
|
||||
1. ID プロバイダーに進むには、 **[Sign in with your identity provider]** をクリックします。
|
||||
![[Sign in with your identity provider] ボタンを示すスクリーンショット](/assets/images/help/enterprises/emu-login-submit.png)
|
||||
|
||||
## Usernames and profile information
|
||||
## ユーザー名とプロファイル情報
|
||||
|
||||
{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
|
||||
{% data variables.product.product_name %} は、IdP から提供された識別子を正規化することにより、各自のユーザー名を自動的に作成します。 詳細については、「[外部認証におけるユーザー名の考慮事項](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)」を参照してください。
|
||||
|
||||
A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
|
||||
IdP から提供された識別子の一意の部分が正規化中に削除されると、ユーザーをプロビジョニングするときに競合が発生する場合があります。 ユーザー名の競合が原因でユーザーをプロビジョニングできない場合は、IdP によって提供されるユーザー名を変更する必要があります。 詳しい情報については、「[ユーザー名の問題の解決](/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 %}
|
||||
|
||||
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.
|
||||
{% data variables.enterprise.prodname_managed_user %}のプロファイル名とメール アドレスも IdP によって提供されます。 {% data variables.enterprise.prodname_managed_users_caps %}では、{% data variables.product.prodname_dotcom %} 上のプロファイル名またはメール アドレスを変更できません。IdP が提供できるメール アドレスは 1 つのみです。
|
||||
|
||||
## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
|
||||
## {% data variables.location.product_location %} で複数のユーザー アカウントを持つ開発者をサポートする
|
||||
|
||||
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.
|
||||
Team のユーザーは、{% data variables.enterprise.prodname_emu_enterprise %} の外部にある {% data variables.location.product_location %} のリソースに投稿することが必要になる場合があります。 たとえば、会社のオープンソース プロジェクト用に別のエンタープライズを保持したい場合があります。 {% data variables.enterprise.prodname_managed_user %}ではパブリック リソースに投稿できないため、ユーザーはこの作業のために個別の個人アカウントを維持する必要があります。
|
||||
|
||||
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)."
|
||||
1 つのワークステーションを使用して {% data variables.location.product_location %} で 2 つのユーザー アカウントから投稿する必要があるユーザーは、Git を設定してプロセスを簡略化できます。 詳しくは、「[複数のアカウントの管理](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)」をご覧ください。
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring SCIM provisioning for Enterprise Managed Users with Okta
|
||||
title: Okta でのエンタープライズ マネージド ユーザーの SCIM プロビジョニングの構成
|
||||
shortTitle: Set up provisioning with Okta
|
||||
intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider.
|
||||
intro: ID プロバイダーとして Okta を使って、新しいユーザーをプロビジョニングし、エンタープライズとチームのメンバーシップを管理することができます。
|
||||
product: '{% data reusables.gated-features.emus %}'
|
||||
versions:
|
||||
ghec: '*'
|
||||
@@ -17,81 +17,86 @@ topics:
|
||||
- Authentication
|
||||
- Enterprise
|
||||
- SSO
|
||||
ms.openlocfilehash: b8c086d1d91c1248fa5a0349bb6f8ef32c3bbdf0
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160713'
|
||||
---
|
||||
## Okta でのプロビジョニングについて
|
||||
|
||||
## About provisioning with Okta
|
||||
ID プロバイダーとして Okta と共に {% data variables.product.prodname_emus %} を使用して、新しいアカウントのプロビジョニング、エンタープライズ メンバーシップの管理、エンタープライズ内の組織のチーム メンバーシップの管理を行うことができます。 {% data variables.product.prodname_emus %} のプロビジョニングの詳細については、「[エンタープライズ マネージド ユーザーの SCIM プロビジョニングの構成](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)」を参照してください。
|
||||
|
||||
You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, 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)."
|
||||
Okta でプロビジョニングを構成する前に、SAML シングル サインオンを構成する必要があります。 詳細については、「[エンタープライズ マネージド ユーザーの SAML シングル サインオンの構成](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)」を参照してください。
|
||||
|
||||
Before you can configure provisioning with Okta, you must configure SAML single-sign on. 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)."
|
||||
Okta でプロビジョニングを構成するには、{% data variables.product.prodname_emu_idp_application %} アプリケーションで Enterprise の名前を設定し、セットアップ ユーザーの{% data variables.product.pat_generic %}を入力する必要があります。 その後、Okta でユーザーのプロビジョニングを開始できます。
|
||||
|
||||
To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's {% data variables.product.pat_generic %}. You can then start provisioning users in Okta.
|
||||
## サポートされている機能
|
||||
|
||||
## Supported features
|
||||
{% data variables.product.prodname_emus %} では、Okta の多くのプロビジョニング機能をサポートしています。
|
||||
|
||||
{% data variables.product.prodname_emus %} supports many provisioning features in Okta.
|
||||
|
||||
| Feature | Description |
|
||||
| 機能 | 説明 |
|
||||
| --- | --- |
|
||||
| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. |
|
||||
| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. |
|
||||
| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. |
|
||||
| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. |
|
||||
| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. |
|
||||
| 新しいユーザのプッシュ | Okta の {% data variables.product.prodname_emu_idp_application %} アプリケーションに割り当てられているユーザーは、{% data variables.product.product_name %} 上のエンタープライズで自動的に作成されます。 |
|
||||
| プロファイルの更新をプッシュする | Okta でユーザーのプロファイルに対して行われた更新は、{% data variables.product.product_name %} にプッシュされます。 |
|
||||
| プッシュ グループ | プッシュ グループとして {% data variables.product.prodname_emu_idp_application %} アプリケーションに割り当てられている Okta のグループは、{% data variables.product.product_name %} 上のエンタープライズで自動的に作成されます。 |
|
||||
| ユーザ無効化のプッシュ | Okta の {% data variables.product.prodname_emu_idp_application %} アプリケーションからユーザーの割り当てを解除すると、{% data variables.product.product_name %} のユーザーが無効になります。 ユーザーはサインインできませんが、ユーザーの情報は保持されます。 |
|
||||
| ユーザの再アクティブ化 | Okta アカウントが再アクティブ化され、{% data variables.product.prodname_emu_idp_application %} アプリケーションに再度割り当てられた Okta のユーザーが有効になります。 |
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames.
|
||||
**注:** {% data variables.product.prodname_emus %} は、ユーザー名の変更をサポートしていません。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Setting your enterprise name
|
||||
## エンタープライズ名の設定
|
||||
|
||||
After your {% data variables.enterprise.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta.
|
||||
{% data variables.enterprise.prodname_emu_enterprise %} が作成されたら、Okta で Enterprise 名を設定してプロビジョニングの構成を開始できます。
|
||||
|
||||
1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
|
||||
1. Click the **Sign On** tab.
|
||||
1. To make changes, click **Edit**.
|
||||
1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc".
|
||||
|
||||
1. To save your enterprise name, click **Save**.
|
||||
1. Okta の {% data variables.product.prodname_emu_idp_application %} アプリケーションに移動します。
|
||||
1. **[サインオン]** タブをクリックします。
|
||||
1. 変更するには、 **[編集]** をクリックします。
|
||||
1. [Advanced Sign-on Settings]\(詳細なサインオン設定\) の [エンタープライズ名] テキスト ボックスに、エンタープライズ名を入力します。 たとえば、`https://github.com/enterprises/octoinc` でエンタープライズにアクセスする場合、エンタープライズ名は "octoinc" になります。
|
||||
![Okta の [エンタープライズ名] フィールドのスクリーンショット](/assets/images/help/enterprises/okta-emu-enterprise-name.png)
|
||||
1. エンタープライズ名を保存するには、 **[保存]** をクリックします。
|
||||
|
||||
## Configuring provisioning
|
||||
## プロビジョニングの構成
|
||||
|
||||
After setting your enterprise name, you can proceed to configure provisioning settings.
|
||||
エンタープライズ名を設定したら、プロビジョニング設定の構成に進むことができます。
|
||||
|
||||
To configure provisioning, the setup user with the **@<em>SHORT-CODE</em>_admin** username will need to provide a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)."
|
||||
プロビジョニングを構成するには、 **@<em>SHORT-CODE</em>_admin** ユーザー名を持つセットアップ ユーザーは、**admin:enterprise** スコープで{% data variables.product.pat_v1 %}を指定する必要があります。 新しいトークンの作成について詳しくは、「[{% data variables.product.pat_generic %}の作成](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)」を参照してください。
|
||||
|
||||
1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
|
||||
1. Click the **Provisioning** tab.
|
||||
1. In the settings menu, click **Integration**.
|
||||
1. To make changes, click **Edit**.
|
||||
1. Select **Enable API integration**.
|
||||
1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user.
|
||||
|
||||
1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen.
|
||||
1. To save the token, click **Save**.
|
||||
1. In the settings menu, click **To App**.
|
||||
|
||||
1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**.
|
||||
1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**.
|
||||
|
||||
1. To finish configuring provisioning, click **Save**.
|
||||
1. Okta の {% data variables.product.prodname_emu_idp_application %} アプリケーションに移動します。
|
||||
1. [プロビジョニング] タブをクリックします。
|
||||
1. [設定] メニューで、 **[統合]** をクリックします。
|
||||
1. 変更するには、 **[編集]** をクリックします。
|
||||
1. **[Enable API integration]\(API 統合を有効にする\)** を選択します。
|
||||
1. [API トークン] フィールドに、セットアップ ユーザーに属する **admin:enterprise** スコープを使って、{% data variables.product.pat_v1 %} を入力します。
|
||||
![Okta の [API トークン] フィールドを示すスクリーンショット](/assets/images/help/enterprises/okta-emu-token.png)
|
||||
1. **[Test API Credentials]\(API 資格情報のテスト\)** をクリックします。 テストが成功すると、確認メッセージが画面の上部に表示されます。
|
||||
1. トークンを保存するには、 **[保存]** をクリックします。
|
||||
1. [設定] メニューで **[To App]\(アプリへ\)** をクリックします。
|
||||
![Okta の [To App]\(アプリへ\) メニュー項目を示すスクリーンショット](/assets/images/help/enterprises/okta-emu-to-app-menu.png)
|
||||
1. [Provisioning to App]\(アプリへのプロビジョニング\) の右側で、変更を許可するには、 **[編集]** をクリックします。
|
||||
1. **[ユーザーの作成]** 、 **[Update User Attributes]\(ユーザー属性の更新\)** 、および **[ユーザーの非アクティブ化]** の **[有効化]** を選択します。
|
||||
|
||||
1. プロビジョニングの構成を完了するには、 **[保存]** をクリックします。
|
||||
|
||||
## Assigning users and groups
|
||||
## ユーザーとグループの割り当て
|
||||
|
||||
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.
|
||||
SAML SSO とプロビジョニングを構成したら、{% data variables.product.prodname_emu_idp_application %} アプリケーションにユーザーまたはグループを割り当てることで、{% data variables.product.prodname_dotcom_the_website %} に新しいユーザーをプロビジョニングできるようになります。
|
||||
|
||||
{% data reusables.scim.emu-scim-rate-limit %}
|
||||
|
||||
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)."
|
||||
また、Okta の [プッシュ グループ] タブにグループを追加することで、Organization のメンバーシップを自動的に管理することもできます。 グループが正常にプロビジョニングされると、エンタープライズの組織のチームに接続できるようになります。 チームの管理の詳細については、「[ID プロバイダー グループを使用したチーム メンバーシップの管理](/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)."
|
||||
ユーザーを割り当てるときは、{% data variables.product.prodname_emu_idp_application %} アプリケーションの [ロール] 属性を使用して、エンタープライズのユーザーのロールを {% data variables.product.product_name %} で設定できます。 ロールの詳細については、「[エンタープライズでのロール](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)」を参照してください。
|
||||
|
||||
|
||||
|
||||
|
||||
## Deprovisioning users and groups
|
||||
## ユーザーとグループのプロビジョニング解除
|
||||
|
||||
To remove a user or group from {% data variables.product.product_name %}, remove the user or group from both the "Assignments" tab and the "Push groups" tab in Okta. For users, make sure the user is removed from all groups in the "Push Groups" tab.
|
||||
{% data variables.product.product_name %} からユーザーまたはグループを削除するには、Okta の [割り当て] タブと [プッシュ グループ] タブの両方からユーザーまたはグループを削除します。 ユーザーの場合は、[プッシュ グループ] タブのすべてのグループからユーザーが削除されていることを確認してください。
|
||||
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing team memberships with identity provider groups
|
||||
title: ID プロバイダー グループを使用したチーム メンバーシップの管理
|
||||
shortTitle: Manage teams with your IdP
|
||||
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 %}.'
|
||||
intro: 'ID プロバイダー (IdP) を介して {% data variables.product.product_name %} の Team と Organization のメンバーシップを管理するには、IdP グループを {% data variables.enterprise.prodname_emu_enterprise %} 内の Team に接続します。'
|
||||
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
|
||||
@@ -16,77 +16,74 @@ topics:
|
||||
- Enterprise
|
||||
- SSO
|
||||
- Teams
|
||||
ms.openlocfilehash: 179835d6642cd5718a565869337b5420b29407a5
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160825'
|
||||
---
|
||||
## {% data variables.product.prodname_emus %} を使用したチーム管理について
|
||||
|
||||
## About team management with {% data variables.product.prodname_emus %}
|
||||
{% data variables.product.prodname_emus %} を使うと、{% data variables.product.prodname_dotcom %} Team を IdP グループに接続することで、IdP を介して Enterprise 内の Team と Organization のメンバーシップを管理できます。 エンタープライズの組織のいずれかのチームを IdP グループに接続すると、IdP グループのメンバーシップに対する変更が自動的にエンタープライズに反映されるため、手動での更新やカスタム スクリプトの必要性が軽減されます。
|
||||
|
||||
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. 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.
|
||||
IdP グループまたは新しい Team 接続に変更を加えることで、{% data variables.enterprise.prodname_managed_user %}がメンバーではない Organization の Team に参加することになった場合、その{% data variables.enterprise.prodname_managed_user %}は自動的にその Organization に追加されます。 チームからグループを切断すると、他の方法で組織のメンバーシップが割り当てられない場合、チーム メンバーシップを使用して組織のメンバーになったユーザーは組織から削除されます。
|
||||
|
||||
{% note %}
|
||||
|
||||
**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.
|
||||
**メモ:** Organization の所有者は、アカウントが SCIM 経由でプロビジョニング済みである限り、{% data variables.enterprise.prodname_managed_users %}を Organization に手動で追加することもできます。
|
||||
|
||||
{% 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.
|
||||
IdP 上でグループ メンバーシップが変更された場合、IdP は、IdP によって決定されたスケジュールに従い、その変更と共に SCIM 要求を {% data variables.product.prodname_dotcom_the_website %} に送信するため、変更が直ちに行われるわけではありません。 チームまたは組織のメンバーシップを変更する要求は、ユーザー プロビジョニングの構成に使用されたアカウントによって行われた変更として監査ログに登録されます。
|
||||
|
||||
Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team.
|
||||
IdP グループに接続されているチームは、他のチームの親や別のチームの子にすることはできません。 IdP グループに接続したいチームが親または子チームの場合、新しいチームを作るか、チームを親チームにしている入れ子関係を削除することをお勧めします。
|
||||
|
||||
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)".
|
||||
IdP グループに接続されたチームを含む、エンタープライズ内の任意のチームによるリポジトリへのアクセスを管理するには、{% data variables.product.prodname_dotcom_the_website %} 上で変更を行わなければなりません。 詳細については、「[組織のリポジトリに対するチームのアクセスの管理](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)」を参照してください。
|
||||
|
||||
## Requirements for connecting IdP groups with teams
|
||||
## IdP グループを Team に接続するための要件
|
||||
|
||||
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)."
|
||||
IdP グループを {% data variables.product.prodname_dotcom %} の Team に接続するには、そのグループを IdP 内の {% data variables.product.prodname_emu_idp_application %} アプリケーションに割り当てる必要があります。 詳しくは、[{% data variables.product.prodname_emus %} の SCIM プロビジョニングの構成に関するページ](/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.
|
||||
エンタープライズ内のチームを 1 つの IdP グループに接続できます。 同じ IdP グループをエンタープライズ内の複数のチームに割り当てることができます。
|
||||
|
||||
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 %}.
|
||||
既存のチームを IdP グループに接続する場合は、最初に手動で追加されたすべてのメンバーを削除する必要があります。 エンタープライズ内のチームを IdP グループに接続した後、IdP 管理者は ID プロバイダーを通じてチーム メンバーシップを変更する必要があります。 チーム メンバーシップを {% data variables.product.prodname_dotcom_the_website %} で管理することはできません。
|
||||
|
||||
## Creating a new team connected to an IdP group
|
||||
## IdP グループに接続された新しいチームの作成
|
||||
|
||||
Any member of an organization can create a new team and connect the team to an IdP group.
|
||||
組織のメンバーは、新しいチームを作成し、チームを IdP グループに接続できます。
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.new_team %}
|
||||
{% data reusables.organizations.team_name %}
|
||||
{% data reusables.organizations.team_description %}
|
||||
1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect.
|
||||
|
||||
{% data reusables.organizations.team_visibility %}
|
||||
{% data reusables.organizations.create_team %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %}
|
||||
1. チームを接続するには、[Identity Provider Groups]\(ID プロバイダー グループ\) ドロップダウン メニューを選択し、接続するチームをクリックします。
|
||||
 {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %}
|
||||
|
||||
## Managing the connection between an existing team and an IdP group
|
||||
## 既存のチームと IdP グループ間の接続の管理
|
||||
|
||||
Organization owners and team maintainers can manage the existing connection between an IdP group and a team.
|
||||
組織の所有者とチームの保守担当者は、IdP グループとチームの間の既存の接続を管理できます。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)."
|
||||
**注**: {% data variables.product.prodname_dotcom_the_website %} の既存のチームを初めて IdP グループに接続する前に、{% data variables.product.prodname_dotcom_the_website %} のチームのすべてのメンバーを最初に削除する必要があります。 詳細については、「[Team から Organization メンバーを削除する](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)」を参照してください。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}.
|
||||
|
||||
1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list.
|
||||
|
||||
1. Click **Save changes**.
|
||||
{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
|
||||
1. 必要に応じて、[Identity Provider Groups]\(ID プロバイダー グループ\) で、切断したい IdP グループの右にある {% octicon "x" aria-label="X symbol" %} をクリックします。
|
||||
|
||||
1. IdP グループを接続するには、[Identity Provider Groups]\(ID プロバイダー グループ\) で、ドロップダウン メニューを使用してリストから ID プロバイダー グループを選択します。
|
||||
|
||||
1. **[変更を保存]** をクリックします。
|
||||
|
||||
## Viewing IdP groups, group membership, and connected teams
|
||||
## IdP グループ、グループ メンバーシップ、接続されたチームの表示
|
||||
|
||||
You can review a list of IdP groups, see any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP.
|
||||
IdP グループの一覧を確認したり、IdP グループに接続されているチームを確認したり、{% data variables.product.product_name %}. の各 IdP グループのメンバーシップを確認したりできます。 IdP のグループのメンバーシップを編集する必要があります。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-label="The key icon" %} **Identity provider**.
|
||||
|
||||
2. To see the members and teams connected to an IdP group, click the group's name.
|
||||
|
||||
4. To view the teams connected to the IdP group, click **Teams**.
|
||||
|
||||
1. IdP グループの一覧を確認するには、左側のサイドバーで {% octicon "key" aria-label="The key icon" %} **[ID プロバイダー]** をクリックします。
|
||||
![エンタープライズ サイドバーの [ID プロバイダー] タブを示すスクリーンショット](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png)
|
||||
2. IdP グループに接続されているメンバーとチームを表示するには、グループの名前をクリックします。
|
||||
|
||||
4. IdP グループに接続されているチームを表示するには、 **[チーム]** をクリックします。
|
||||
![[チーム] ボタンを示すスクリーンショット](/assets/images/help/enterprises/idp-groups-team-switcher.png)
|
||||
|
||||
@@ -16,6 +16,7 @@ children:
|
||||
- /about-enterprise-accounts
|
||||
- /system-overview
|
||||
- /about-the-github-enterprise-api
|
||||
- /best-practices-for-enterprises
|
||||
- /creating-an-enterprise-account
|
||||
- /accessing-compliance-reports-for-your-enterprise
|
||||
ms.openlocfilehash: d936542993310333e314efcc9d5bb5689be00701
|
||||
|
||||
@@ -54,9 +54,12 @@ If you downgrade your organization from {% data variables.product.prodname_team
|
||||
If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
**Notes:**
|
||||
- If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see "[Removing organizations from your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
|
||||
- If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring the CodeQL workflow for compiled languages
|
||||
title: コンパイル済み言語の CodeQL ワークフローを構成する
|
||||
shortTitle: Configure compiled languages
|
||||
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.'
|
||||
intro: '{% data variables.product.prodname_dotcom %} による {% data variables.code-scanning.codeql_workflow %}の使用方法を構成すると、コンパイル型言語で脆弱性とエラーが記述されているコードをスキャンできます。'
|
||||
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:
|
||||
@@ -25,107 +25,106 @@ topics:
|
||||
- C/C++
|
||||
- C#
|
||||
- Java
|
||||
ms.openlocfilehash: 91983e79a6381b4a38cbb1de4f6d7f228637b192
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: '148161200'
|
||||
---
|
||||
{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
|
||||
## {% data variables.code-scanning.codeql_workflow %}とコンパイル型言語について
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
{% data variables.product.prodname_dotcom %} がリポジトリに対して {% data variables.product.prodname_code_scanning %} を実行できるようにするには、{% data variables.product.prodname_actions %} ワークフローをリポジトリに追加します。 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} では、{% data variables.code-scanning.codeql_workflow %}を追加できます。 詳細については、「[リポジトリの {% data variables.product.prodname_code_scanning %} の設定](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」を参照してください。
|
||||
|
||||
## About the {% data variables.code-scanning.codeql_workflow %} and compiled languages
|
||||
{% data reusables.code-scanning.edit-workflow %} {% data variables.product.prodname_code_scanning %} の構成とワークフロー ファイルの編集に関する一般的な情報については、「[{% data variables.product.prodname_code_scanning %} を構成する](/code-security/secure-coding/configuring-code-scanning)」および「[{% data variables.product.prodname_actions %} について学ぶ](/actions/learn-github-actions)」をご覧ください。
|
||||
|
||||
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 variables.product.prodname_codeql %} の autobuild について
|
||||
|
||||
{% 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)."
|
||||
|
||||
## About autobuild for {% data variables.product.prodname_codeql %}
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.
|
||||
For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
|
||||
{% data variables.product.prodname_code_scanning_capc %} は、1 つ以上のデータベースに対してクエリを実行することにより機能します。 各データベースには、リポジトリにあるすべてのコードを 1 つの言語で表わしたものが含まれています。
|
||||
コンパイル型言語の C/C++、C#、{% ifversion codeql-go-autobuild %}Go、{% endif %}Java では、このデータベースを生成するプロセスに、コードのビルドとデータの抽出が含まれています。 {% data reusables.code-scanning.analyze-go %}
|
||||
|
||||
{% data reusables.code-scanning.autobuild-compiled-languages %}
|
||||
|
||||
If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
|
||||
ワークフローで `language` マトリックスを使っている場合、`autobuild` はマトリックスに列記された各コンパイル型言語のビルドを試行します。 マトリックスがない場合、`autobuild` は、サポートされているコンパイル型言語で、リポジトリ内のソース ファイルの数が最も多いもののビルドを試みます。 Go を除いて、明示的にビルドコマンドを使用しない限り、リポジトリにある他のコンパイル型言語の解析は失敗します。
|
||||
|
||||
{% note %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
**Note**: {% data reusables.actions.self-hosted-runners-software %}
|
||||
{% else %}
|
||||
**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
|
||||
{% ifversion ghae %} **注**: {% data reusables.actions.self-hosted-runners-software %} {% else %} **注**: {% data variables.product.prodname_actions %} にセルフホステッド ランナーを使う場合は、`autobuild` プロセスを使うために追加のソフトウェアをインストールすることが必要になる場合があります。 さらに、リポジトリに特定のバージョンのビルドツールが必要な場合は、手動でインストールする必要があります。 詳しくは、「[{% data variables.product.prodname_dotcom %} ホステッド ランナーの概要](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」をご覧ください。
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### C/C++
|
||||
|
||||
| Supported system type | System name |
|
||||
| サポートされているシステムの種類 | システム名 |
|
||||
|----|----|
|
||||
| Operating system | Windows, macOS, and Linux |
|
||||
| Build system | Windows: MSbuild and build scripts<br/>Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts |
|
||||
| オペレーティング システム | Windows、macOS、Linux |
|
||||
| ビルドシステム | Windows: MSbuild スクリプトと build スクリプト<br/>Linux と macOS: Autoconf、Make、CMake、qmake、 Meson、Waf、SCons、Linux Kbuild、build の各スクリプト |
|
||||
|
||||
The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach:
|
||||
`autobuild` ステップの動作は、抽出を実行するオペレーティング システムによって異なります。 Windows の `autobuild` ステップでは、以下の方法を使って C/C++ に適したビルド方法の自動検出が試みられます。
|
||||
|
||||
1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root.
|
||||
If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
|
||||
2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order).
|
||||
1. ルートに最も近いソリューション (`.sln`) またはプロジェクト (`.vcxproj`) ファイルで `MSBuild.exe` を呼び出します。
|
||||
`autobuild` が最上位ディレクトリから同じ (最短) 深度で複数のソリューションまたはプロジェクト ファイルを検出した場合、それらすべてのビルドが試みられます。
|
||||
2. ビルド スクリプトのように見えるスクリプト、つまり _build.bat_、_build.cmd_、_build.exe_ を、この順番で呼び出します。
|
||||
|
||||
On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
|
||||
Linux と macOS の `autobuild` ステップでは、リポジトリ内にあるファイルが確認されて、使われているビルド システムが特定されます。
|
||||
|
||||
1. Look for a build system in the root directory.
|
||||
2. If none are found, search subdirectories for a unique directory with a build system for C/C++.
|
||||
3. Run an appropriate command to configure the system.
|
||||
1. ルートディレクトリでビルドシステムを探します。
|
||||
2. 何も見つからない場合は、C/C++ のビルドシステムで一意のディレクトリをサブディレクトリで検索します。
|
||||
3. 適切なコマンドを実行してシステムを設定します。
|
||||
|
||||
### C#
|
||||
|
||||
| Supported system type | System name |
|
||||
| サポートされているシステムの種類 | システム名 |
|
||||
|----|----|
|
||||
| Operating system | Windows and Linux |
|
||||
| Build system | .NET and MSbuild, as well as build scripts |
|
||||
| オペレーティング システム | Windows と Linux |
|
||||
| ビルドシステム | .NET と MSbuild、およびビルドスクリプト |
|
||||
|
||||
The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
|
||||
`autobuild` プロセスは、次の方法を使って C# に適したビルド方法の自動検出を試みます。
|
||||
|
||||
1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root.
|
||||
2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root.
|
||||
If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
|
||||
3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
|
||||
1. ルートに最も近いソリューション (`.sln`) またはプロジェクト (`.csproj`) ファイルで `dotnet build` を呼び出します。
|
||||
2. ルートに最も近いソリューションまたはプロジェクト ファイルで、`MSbuild` (Linux) または `MSBuild.exe` (Windows) を呼び出します。
|
||||
`autobuild` が最上位ディレクトリから同じ (最短) 深度で複数のソリューションまたはプロジェクト ファイルを検出した場合、それらすべてのビルドが試みられます。
|
||||
3. ビルド スクリプトのように見えるスクリプト、つまり _build_ と _build.sh_ (Linux の場合、この順序で) または _build.bat_、_build.cmd_、_and build.exe_ (Windows の場合、この順序で) を呼び出します。
|
||||
|
||||
{% ifversion codeql-go-autobuild %}
|
||||
|
||||
### Go
|
||||
|
||||
| Supported system type | System name |
|
||||
| サポートされているシステムの種類 | システム名 |
|
||||
|----|----|
|
||||
| Operating system | Windows, macOS, and Linux |
|
||||
| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
|
||||
| オペレーティング システム | Windows、macOS、Linux |
|
||||
| ビルドシステム | Go モジュール、`dep`、Glide、およびメイクファイルや Ninja スクリプトを含むビルド スクリプト |
|
||||
|
||||
The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
|
||||
`autobuild` プロセスは、すべての `.go` ファイルを抽出する前に、Go リポジトリで必要な依存関係をインストールする適切な方法の自動検出を試みます。
|
||||
|
||||
1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed.
|
||||
2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies.
|
||||
3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes.
|
||||
4. Extract all Go code in the repository, similar to running `go build ./...`.
|
||||
1. `make`、`ninja`、または `./build` を、これらのコマンドのいずれかが成功し、その後の `./build.sh` も成功して、必要な依存関係がインストールされたことを示すまで、(この順序で) 呼び出`go list ./...`します。
|
||||
2. これらのコマンドがいずれも成功しなかった場合は、`go.mod`、`Gopkg.toml`、または `glide.yaml` を探し、それぞれの `go get` (ベンダーが使用していない場合)、`dep ensure -v`、または `glide install` を実行して、依存関係のインストールを試みます。
|
||||
3. 最後に、これらの依存関係マネージャーの構成ファイルが見つからない場合は、`GOPATH` に追加するのに適したリポジトリ ディレクトリ構造に調整し直し、`go get` を使って依存関係をインストールします。 抽出が完了すると、ディレクトリ構造は通常に戻ります。
|
||||
4. `go build ./...` を実行するのと同じようにして、リポジトリ内のすべての Go コードを抽出します。
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Java
|
||||
|
||||
| Supported system type | System name |
|
||||
| サポートされているシステムの種類 | システム名 |
|
||||
|----|----|
|
||||
| Operating system | Windows, macOS, and Linux (no restriction) |
|
||||
| Build system | Gradle, Maven and Ant |
|
||||
| オペレーティング システム | Windows、macOS、Linux (制限なし) |
|
||||
| ビルドシステム | Gradle、Maven、Ant |
|
||||
|
||||
The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
|
||||
`autobuild` プロセスは、この戦略を適用して、Java コードベース用のビルド システムの特定を試みます。
|
||||
|
||||
1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files.
|
||||
2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used.
|
||||
3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error.
|
||||
1. ルートディレクトリでビルドファイルを検索します。 Gradle、Maven、Ant の各ビルドファイルを確認します。
|
||||
2. 最初に見つかったビルドファイルを実行します。 Gradle ファイルと Maven ファイルの両方が存在する場合は、Gradle ファイルが使用されます。
|
||||
3. それ以外の場合は、ルートディレクトリの直接サブディレクトリ内でビルドファイルを検索します。 1 つのサブディレクトリにのみビルドファイルが含まれている場合は、そのサブディレクトリで識別された最初のファイルを実行します（1 と同じ環境設定を使用）。 複数のサブディレクトリにビルドファイルが含まれている場合は、エラーを報告します。
|
||||
|
||||
## Adding build steps for a compiled language
|
||||
## コンパイル言語のビルドステップを追加する
|
||||
|
||||
{% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
|
||||
{% data reusables.code-scanning.autobuild-add-build-steps %}ワークフロー ファイルの編集方法については、「[{% data variables.product.prodname_code_scanning %} を構成する](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)」をご覧ください。
|
||||
|
||||
After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process.
|
||||
`autobuild` ステップを削除したら、`run` ステップをコメント解除して、リポジトリに適したビルド コマンドを追加します。 ワークフローの `run` ステップでは、オペレーティング システムのシェルを使ってコマンド ライン プログラムが実行されます。 これらのコマンドを変更し、別のコマンドを追加してビルド プロセスをカスタマイズできます。
|
||||
|
||||
``` yaml
|
||||
- run: |
|
||||
@@ -133,9 +132,9 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm
|
||||
make release
|
||||
```
|
||||
|
||||
For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
|
||||
`run` キーワードについて詳しくは、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)」をご覧ください。
|
||||
|
||||
If your repository contains multiple compiled languages, you can specify language-specific build commands. For example, if your repository contains C/C++, C# and Java, and `autobuild` correctly builds C/C++ and C# but fails to build Java, you could use the following configuration in your workflow, after the `init` step. This specifies build steps for Java while still using `autobuild` for C/C++ and C#:
|
||||
リポジトリに複数のコンパイル済み言語が含まれている場合は、言語固有のビルド コマンドを指定できます。 たとえば、リポジトリに C/C++、C#、Java が含まれていて、`autobuild` によって C/C++ と C# は正しくビルドされるが、Java のビルドは失敗する場合は、ワークフローの `init` ステップの後で次の構成を使用できます。 これにより、C/C++ と C# には `autobuild` をそのまま使用しつつ、Java のビルド ステップを指定します。
|
||||
|
||||
```yaml
|
||||
- if: matrix.language == 'cpp' || matrix.language == 'csharp'
|
||||
@@ -149,8 +148,8 @@ If your repository contains multiple compiled languages, you can specify languag
|
||||
make release
|
||||
```
|
||||
|
||||
For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)."
|
||||
`if` 条件について詳しくは、「[GitHub Actions のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)」をご覧ください。
|
||||
|
||||
For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
|
||||
`autobuild` でコードがビルドされない理由に関するその他のヒントとテクニックについては、「[{% data variables.product.prodname_codeql %} ワークフローのトラブルシューティング](/code-security/secure-coding/troubleshooting-the-codeql-workflow)」をご覧ください。
|
||||
|
||||
If you added manual build steps for compiled languages and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
|
||||
コンパイル言語にマニュアルのビルドステップを追加しても、リポジトリで依然として{% data variables.product.prodname_code_scanning %}が動作しない場合は、{% data variables.contact.contact_support %}にお問い合わせください。
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Uploading a SARIF file to GitHub
|
||||
title: SARIF ファイルを 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,54 +23,57 @@ topics:
|
||||
- Repositories
|
||||
- CI
|
||||
- SARIF
|
||||
ms.openlocfilehash: 3def104e487f54e2c48d462d1dcfe8bab63c6fa3
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: '148161162'
|
||||
---
|
||||
{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
## {% data variables.product.prodname_code_scanning %} に対する SARIF ファイルのアップロードについて
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
{% data variables.product.prodname_dotcom %} は、静的分析結果交換形式 (SARIF) ファイルの情報を使用して、リポジトリに {% data variables.product.prodname_code_scanning %} アラートを作成します。 SARIF ファイルは、API または {% data variables.product.prodname_actions %} を使用してリポジトリにアップロードできます。 詳細については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートの管理](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)」を参照してください。
|
||||
|
||||
## About SARIF file uploads for {% data variables.product.prodname_code_scanning %}
|
||||
SARIF ファイルは、{% data variables.product.prodname_codeql %} を含む多くの静的解析セキュリティテストツールを使用して生成できます。 結果は SARIF バージョン 2.1.0 を使用する必要があります。 詳細については、「[{% data variables.product.prodname_code_scanning %} の SARIF サポート](/code-security/secure-coding/sarif-support-for-code-scanning)」を参照してください。
|
||||
|
||||
{% 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 %}、{% data variables.product.prodname_code_scanning %} API、{% ifversion codeql-runner-supported %} {% data variables.code-scanning.codeql_runner %}、{% endif %}または {% data variables.product.prodname_codeql_cli %} を使ってアップロードできます。 最適なアップロード方法は、SARIF ファイルの生成方法によって異なります。以下、例を示します。
|
||||
|
||||
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 variables.product.prodname_actions %} を使用して {% data variables.product.prodname_codeql %} アクションを実行している場合、追加のアクションは不要です。 {% data variables.product.prodname_codeql %} アクションは、分析の完了時に SARIF ファイルを自動的にアップロードします。
|
||||
- {% data variables.product.prodname_actions %} を使用して SARIF 互換の分析ツールを実行します。ワークフローを更新して、結果をアップロードする最後の手順を含めることができます (下記を参照)。
|
||||
- {% data variables.product.prodname_codeql_cli %} は、CI システムで {% data variables.product.prodname_code_scanning %} を実行するために、CLI を使用して結果を {% data variables.product.prodname_dotcom %} にアップロードできます (詳細については、「[CI システムでの {% data variables.product.prodname_codeql_cli %} のインストール](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)」を参照してください)。{% ifversion codeql-runner-supported %}
|
||||
- {% data variables.code-scanning.codeql_runner %}は、CI システムで {% data variables.product.prodname_code_scanning %} を実行するためのものであり、既定では、完了時に、このランナーによって結果が {% data variables.product.prodname_dotcom %} に自動的にアップロードされます。 自動アップロードをブロックする場合、結果をアップロードする準備ができたら、`upload` コマンドを使うことができます (詳しくは、「[CI システムでの {% data variables.code-scanning.codeql_runner %}の実行](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)」を参照してください)。{% endif %}
|
||||
- リポジトリの外部で成果物として結果を生成するツールでは、{% data variables.product.prodname_code_scanning %} API を使用してファイルをアップロードできます (詳細については、「[SARIF データとして分析をアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)」を参照してください)。
|
||||
|
||||
{% data reusables.code-scanning.not-available %}
|
||||
|
||||
## Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
|
||||
## {% data variables.product.prodname_actions %} での {% data variables.product.prodname_code_scanning %} 分析をアップロードする
|
||||
|
||||
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)."
|
||||
{% data variables.product.prodname_actions %} を使用してサードパーティの SARIF ファイルをリポジトリにアップロードするには、ワークフローが必要です。 詳細については、「[{% data variables.product.prodname_actions %} について学ぶ](/actions/learn-github-actions)」を参照してください。
|
||||
|
||||
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:
|
||||
ワークフローでは、`github/codeql-action` リポジトリの一部である `upload-sarif` アクションを使用する必要があります。 これには、アップロードの設定に使用できる入力パラメータがあります。 使用する主な入力パラメーターは次のとおりです。
|
||||
|
||||
- `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.
|
||||
- `sarif-file` は、アップロードする SARIF ファイルのファイルまたはディレクトリを構成します。 ディレクトリまたはファイルのパスは、リポジトリのルートからの相対パスです。
|
||||
- `category` (省略可能) は、SARIF ファイルで結果のカテゴリを割り当てます。 これにより、複数の方法で同じコミットを分析し、{% data variables.product.prodname_dotcom %} の {% data variables.product.prodname_code_scanning %} ビューを使用して結果を確認できます。 たとえば、複数のツールを使用して分析できます。mono リポジトリでは、変更されたファイルのサブセットに基づいてリポジトリのさまざまなスライスを分析できます。
|
||||
|
||||
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).
|
||||
詳細については、「[`upload-sarif` アクション](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif)」を参照してください。
|
||||
|
||||
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)."
|
||||
`upload-sarif` アクションは、`push` および `scheduled` イベントが発生したときに実行されるように構成できます。 {% data variables.product.prodname_actions %} イベントの詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
|
||||
|
||||
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)."
|
||||
SARIFファイルに `partialFingerprints` が含まれていない場合、`upload-sarif` アクションは `partialFingerprints` フィールドを自動的に計算して、重複するアラートが発生しないようにします。 {% data variables.product.prodname_dotcom %} では、リポジトリに SARIF ファイルと、スタティック分析で使用されるソース コードの両方が含まれている場合にのみ、`partialFingerprints` を作成できます。 重複するアラートの防止方法の詳細については、[コード スキャンの SARIF サポート](/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 %}
|
||||
|
||||
### Example workflow for SARIF files generated outside of a repository
|
||||
### リポジトリ外で生成された SARIF ファイルのワークフロー例
|
||||
|
||||
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.
|
||||
SARIF ファイルをリポジトリにコミットした後でアップロードする新しいワークフローを作成できます。 これは、SARIF ファイルがご自分のリポジトリの外部の成果物として生成される場合に便利です。
|
||||
|
||||
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)."
|
||||
この例のワークフローは、コミットがリポジトリにプッシュされるたびに実行されます。 このアクションでは、`partialFingerprints` プロパティを使用して、変更が発生したかどうかを確認します。 コミットがプッシュされたときの実行に加えて、ワークフローは週に 1 回実行されるようにスケジュールされています。 詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
|
||||
|
||||
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)."
|
||||
このワークフローは、リポジトリのルートにある `results.sarif` ファイルをアップロードします。 ワークフロー ファイルの作成の詳細については、「[{% data variables.product.prodname_actions %} について学ぶ](/actions/learn-github-actions)」を参照してください。
|
||||
|
||||
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)."
|
||||
または、このワークフローを変更して、SARIF ファイルのディレクトリをアップロードすることもできます。 たとえば、すべての SARIF ファイルをリポジトリのルートにある `sarif-output` というディレクトリに配置し、アクションの入力パラメーター `sarif_file` を `sarif-output` に設定できます。 ディレクトリをアップロードする場合、各 SARIF ファイルには、結果のカテゴリを定義するための一意の `runAutomationDetails.id` が含まれている必要があることにご注意ください。 詳細については、「[`runAutomationDetails` オブジェクト](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)」を参照してください。
|
||||
|
||||
```yaml
|
||||
name: "Upload SARIF"
|
||||
@@ -105,13 +108,13 @@ jobs:
|
||||
category: my-analysis-tool
|
||||
```
|
||||
|
||||
### Example workflow that runs the ESLint analysis tool
|
||||
### ESLint 分析ツールを実行するワークフローの例
|
||||
|
||||
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)."
|
||||
継続的インテグレーション (CI) ワークフローの一部としてサードパーティの SARIF ファイルを生成する場合は、CI テストを実行した後に `upload-sarif` アクションをステップとして追加できます。 CI ワークフローがない場合は、{% data variables.product.prodname_actions %} テンプレートを使用して作成できます。 詳細については、[{% data variables.product.prodname_actions %} クイックスタート](/actions/quickstart)に関するページを参照してください。
|
||||
|
||||
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)."
|
||||
この例のワークフローは、コミットがリポジトリにプッシュされるたびに実行されます。 このアクションでは、`partialFingerprints` プロパティを使用して、変更が発生したかどうかを確認します。 コミットがプッシュされたときの実行に加えて、ワークフローは週に 1 回実行されるようにスケジュールされています。 詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
|
||||
|
||||
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)."
|
||||
ワークフローでは、ESLint 静的分析ツールをワークフローのステップとして実行する例を示しています。 `Run ESLint` ステップは、ESLint ツールを実行し、`results.sarif` ファイルを出力します。 その後、ワークフローにより、`upload-sarif` アクションが使用され `results.sarif` ファイルが {% data variables.product.prodname_dotcom %} にアップロードされます。 ワークフロー ファイルの作成の詳細については、「[GitHub Actions の概要](/actions/learn-github-actions/introduction-to-github-actions)」を参照してください。
|
||||
|
||||
```yaml
|
||||
name: "ESLint analysis"
|
||||
@@ -147,9 +150,9 @@ jobs:
|
||||
sarif_file: results.sarif
|
||||
```
|
||||
|
||||
## Further reading
|
||||
## 参考資料
|
||||
|
||||
- "[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)"
|
||||
- [{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)
|
||||
- "[ワークフローの履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)"
|
||||
- "[CI システムでの {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} について](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"
|
||||
- "[分析を SARIF データとしてアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: Configuring private vulnerability reporting for a repository
|
||||
intro: Owners and administrators of public repositories can allow security researchers to report vulnerabilities securely in the repository by enabling private vulnerability reporting.
|
||||
permissions: 'Anyone with admin permissions to a public repository can enable and disable private vulnerability reporting for the repository.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Configure private vulnerability reporting
|
||||
---
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
|
||||
|
||||
## About privately reporting a security vulnerability
|
||||
|
||||
Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-overview %}
|
||||
|
||||
For maintainers, the benefits of using private vulnerability reporting are:
|
||||
- Less risk of being contacted publicly, or via undesired means.
|
||||
- Receive reports in the same platform you resolve them in for simplicity
|
||||
- The security researcher creates or at least initiates the advisory report on the behalf of maintainers.
|
||||
- Maintainers receive reports in the same platform as the one used to discuss and resolve the advisories.
|
||||
- Vulnerability less likely to be in the public eye.
|
||||
- The opportunity to discuss vulnerability details privately with security researchers and collaborate on the patch.
|
||||
|
||||
## Enabling or disabling private vulnerability reporting for a repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
|
||||
|
||||
|
||||
|
||||
When a maintainer enables private security reporting for their repository, security researchers will see a new button in the **Advisories** page of the repository. The security researcher can click this button to privately report a security vulnerability to the repository maintainer.
|
||||
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ shortTitle: About the security overview
|
||||
|
||||
## About the security overview
|
||||
|
||||
The security overview provides 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 overview 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 %}
|
||||
{% data reusables.security-overview.about-the-security-overview %} {% 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 shows which security features are enabled for repositories and consolidate alerts for each feature.
|
||||
|
||||
@@ -46,8 +46,6 @@ The dependency review feature becomes available when you enable the dependency g
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
## Dependency review enforcement
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-action-beta-note %}
|
||||
|
||||
The action is available for all {% ifversion fpt or ghec %}public repositories, as well as private {% endif %}repositories that have {% data variables.product.prodname_GH_advanced_security %} enabled.
|
||||
|
||||
{% data reusables.dependency-review.action-enterprise %}
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: 依存関係レビューの構成
|
||||
intro: 依存関係レビューを使用して、脆弱性がプロジェクトに追加される前に捕捉できます。
|
||||
title: Configuring dependency review
|
||||
intro: You can use dependency review to catch vulnerabilities before they are added to your project.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Configure dependency review
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -14,90 +15,201 @@ topics:
|
||||
- Vulnerabilities
|
||||
- Dependencies
|
||||
- Pull requests
|
||||
ms.openlocfilehash: e7fae5d42e4f7c14098414c28e5b5eb857c39687
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107502'
|
||||
---
|
||||
## 依存関係の確認について
|
||||
|
||||
## About dependency review
|
||||
|
||||
{% data reusables.dependency-review.feature-overview %}
|
||||
|
||||
詳細については、「[依存関係レビューについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)」と「[pull request 内の依存関係の変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。
|
||||
For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" and "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
|
||||
|
||||
## 依存関係レビューの構成について
|
||||
## About configuring dependency review
|
||||
|
||||
{% ifversion fpt %}依存関係レビューは、すべての製品のすべてのパブリック リポジトリで使用できます。また、無効にすることはできません。 依存関係レビューは、GitHub Enterprise Cloud を使い、[{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) のライセンスを持つ組織が所有するプライベート リポジトリで利用できます。 詳細については、[{% data variables.product.prodname_ghe_cloud %} ドキュメント](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review)を参照してください。
|
||||
{% ifversion fpt %}
|
||||
Dependency review is available in all public repositories in all products and cannot be disabled. Dependency review is available in private repositories owned by organizations that use GitHub Enterprise Cloud and have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-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/configuring-dependency-review).
|
||||
|
||||
{% elsif ghec %}依存関係レビューは、パブリック リポジトリの {% data variables.product.product_name %} に含まれています。 組織が所有するプライベート リポジトリで依存関係レビューを使うには、[{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) のライセンスがあり、依存関係グラフを有効にする必要があります。
|
||||
{% elsif ghec %}
|
||||
Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) and have the dependency graph enabled.
|
||||
|
||||
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
|
||||
1. まだ "{% data variables.product.prodname_GH_advanced_security %}" が有効になっていない場合は、機能の横にある **[Enable]\(有効にする\)** をクリックします。
|
||||
![[Enable]\(有効にする\) ボタンが強調表示された GitHub Advanced Security 機能のスクリーンショット](/assets/images/help/security/enable-ghas-private-repo.png)
|
||||
1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature.
|
||||
|
||||
|
||||
{% elsif ghes or ghae %}
|
||||
|
||||
依存関係の確認は、{% data variables.location.product_location %}に対して依存関係グラフが有効になっており、{% data variables.product.prodname_advanced_security %} が組織またはリポジトリで有効になっている場合に使用できます。{% ifversion ghes %}詳細については、「[エンタープライズで {% data variables.product.prodname_GH_advanced_security %} を有効にする](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)」を参照してください。{% endif %}
|
||||
Dependency review is 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.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %}
|
||||
|
||||
### 依存関係グラフが有効になっているかどうかを確認する
|
||||
### Checking if the dependency graph is enabled
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. [Configure security and analysis features]\(セキュリティと分析機能の構成\) で、依存関係グラフが有効になっているかどうかを確認します。
|
||||
1. 依存関係グラフが有効である場合は、"{% data variables.product.prodname_GH_advanced_security %}" の横にある **[Enable]\(有効にする\)** をクリックして、依存関係レビューを含む {% data variables.product.prodname_advanced_security %} を有効にします。 エンタープライズに {% data variables.product.prodname_advanced_security %} に使用できるライセンスがない場合、[有効にする] ボタンは無効です。{% ifversion ghes %}{% endif %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Configure security and analysis features", check if the dependency graph is enabled.
|
||||
1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion dependency-review-action-configuration %}
|
||||
## {% data variables.product.prodname_dependency_review_action %} の構成
|
||||
## About configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-action-beta-note %} {% data reusables.dependency-review.dependency-review-action-overview %}
|
||||
{% data reusables.dependency-review.dependency-review-action-overview %}
|
||||
|
||||
次の構成オプションを使用できます。
|
||||
The following configuration options are available.
|
||||
|
||||
| オプション | 必須 | 使用法 |
|
||||
| Option | Required | Usage |
|
||||
|------------------|-------------------------------|--------|
|
||||
| `fail-on-severity` | オプション | 重大度レベル (`low`、`moderate`、`high`、`critical`) のしきい値を定義します。</br>アクションは、指定した重大度レベル以上の脆弱性を引き起こす pull request で失敗します。 |
|
||||
{%- ifversion dependency-review-action-licenses %} | `allow-licenses` | 省略可能 | 許可されているライセンスの一覧が含まれています。 このパラメーターに使用できる値は、API ドキュメントの「[ライセンス](/rest/licenses)」のページで確認できます。</br>このアクションは、list.| と一致しないライセンスを持つ依存関係を導入するプル要求で失敗します。{% endif %} {%- ifversion dependency-review-action-licenses %} | `deny-licenses` |省略可能な|禁止されているライセンスの一覧が含まれています。 このパラメーターに使用できる値は、API ドキュメントの「[ライセンス](/rest/licenses)」のページで確認できます。</br>アクションは、リストに一致するライセンスを持つ依存関係を導入する pull request で失敗します。|{% endif %}
|
||||
| `fail-on-severity` | Optional | Defines the threshold for level of severity (`low`, `moderate`, `high`, `critical`).</br>The action will fail on any pull requests that introduce vulnerabilities of the specified severity level or higher. |
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
| `fail-on-scopes` | Optional | Contains a list of strings representing the build environments you want to support (`development`, `runtime`, `unknown`). </br>The action will fail on pull requests that introduce vulnerabilites in the scopes that match the list.|{% endif %}
|
||||
| `allow-ghsas` | Optional | Contains a list of {% data variables.product.prodname_advisory_database %} IDs that can be skipped during detection. You can find the possible values for this parameter in the [{% data variables.product.prodname_advisory_database %}](https://github.com/advisories). |
|
||||
| `config-file` | Optional | Specifies a path to a configuration file. The configuration file can be local to the repository or a file located in an external repository.|
|
||||
| `external-repo-token` | Optional | Specifies a token for fetching the configuration file, if the file resides in a private external repository. The token must have read access to the repository.|
|
||||
|
||||
{% ifversion dependency-review-action-licenses %} {% tip %}
|
||||
|
||||
**ヒント:** オプション `allow-licenses` と `deny-licenses` は同時に指定できません。
|
||||
|
||||
{% endtip %} {% endif %}
|
||||
|
||||
この {% data variables.product.prodname_dependency_review_action %} サンプル ファイルは、これらの構成オプションを使用する方法を示しています。 この例では、アクションに対して、semver リリース番号 (`v2.0.8` など) ではなく、短いバージョン番号 (`v2`) が使われています。 これにより、アクションの最新のマイナー バージョンを使うことができます。
|
||||
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v2
|
||||
with:
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
# allow-licenses: GPL-3.0, BSD-3-Clause, MIT
|
||||
{% tip %}
|
||||
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
# deny-licenses: LGPL-2.0, BSD-2-Clause
|
||||
{% endif %}
|
||||
```
|
||||
**Tip:** The `allow-licenses` and `deny-licenses` options are mutually exclusive.
|
||||
|
||||
構成オプションの詳細については、「[`dependency-review-action`](https://github.com/actions/dependency-review-action#readme)」を参照してください。
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
## Configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
There are two methods of configuring the {% data variables.product.prodname_dependency_review_action %}:
|
||||
- Inlining the configuration options in your workflow file.
|
||||
- Referencing a configuration file in your workflow file.
|
||||
|
||||
Notice that all of the examples use a short version number for the action (`v3`) instead of a semver release number (for example, `v3.0.8`). This ensures that you use the most recent minor version of the action.
|
||||
### Using inline configuration to set up the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
```
|
||||
1. Specify your settings.
|
||||
|
||||
This {% data variables.product.prodname_dependency_review_action %} example file illustrates how you can use the available configuration options.
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
with:
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
allow-licenses: GPL-3.0, BSD-3-Clause, MIT
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
deny-licenses: LGPL-2.0, BSD-2-Clause
|
||||
{% endif %}
|
||||
# ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
|
||||
# Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories
|
||||
allow-ghsas: GHSA-abcd-1234-5679, GHSA-efgh-1234-5679
|
||||
{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
# ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
|
||||
# Possible values: "development", "runtime", "unknown"
|
||||
fail-on-scopes: development, runtime
|
||||
{% endif %}
|
||||
```
|
||||
### Using a configuration file to set up {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder and use `config-file` to specify that you are using a configuration file.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
with:
|
||||
# ([String]). Representing a path to a configuration file local to the repository or in an external repository.
|
||||
# Possible values: An absolute path to a local file or an external file.
|
||||
config-file: './.github/dependency-review-config.yml'
|
||||
# Syntax for an external file: OWNER/REPOSITORY/FILENAME@BRANCH
|
||||
config-file: 'github/octorepo/dependency-review-config.yml@main'
|
||||
|
||||
# ([Token]) Use if your configuration file resides in a private external repository.
|
||||
# Possible values: Any GitHub token with read access to the private external repository.
|
||||
external-repo-token: 'ghp_123456789abcde'
|
||||
```
|
||||
1. Create the configuration file in the path you have specified.
|
||||
|
||||
This YAML example file illustrates how you can use the available configuration options.
|
||||
```yaml{:copy}
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
allow-licenses:
|
||||
- GPL-3.0
|
||||
- BSD-3-Clause
|
||||
- MIT
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
deny-licenses:
|
||||
- LGPL-2.0
|
||||
- BSD-2-Clause
|
||||
{% endif %}
|
||||
# ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
|
||||
# Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories
|
||||
allow-ghsas:
|
||||
- GHSA-abcd-1234-5679
|
||||
- GHSA-efgh-1234-5679
|
||||
{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
# ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
|
||||
# Possible values: "development", "runtime", "unknown"
|
||||
fail-on-scopes:
|
||||
- development
|
||||
- runtime
|
||||
{% endif %}
|
||||
```
|
||||
For further details about the configuration options, see [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
|
||||
{% endif %}
|
||||
|
||||
@@ -42,7 +42,7 @@ You can work with {% data variables.product.prodname_github_codespaces %} in the
|
||||
|
||||
If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account.
|
||||
|
||||
To use `gh` to work with {% data variables.product.prodname_github_codespaces %}, type `gh codespace <COMMAND>` or its alias `gh cs <COMMAND>`.
|
||||
To use `gh` to work with {% data variables.product.prodname_github_codespaces %}, type `gh codespace SUBCOMMAND` or its alias `gh cs SUBCOMMAND`.
|
||||
|
||||
As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could:
|
||||
|
||||
@@ -51,15 +51,15 @@ As an example of a series of commands you might use to work with {% data variabl
|
||||
* Create a new codespace for the required repository branch:<br>
|
||||
`gh codespace create -r github/docs -b main`
|
||||
* SSH into the new codespace:<br>
|
||||
`gh codespace ssh -c mona-github-docs-v4qxrv7rfwv9w`
|
||||
`gh codespace ssh -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
|
||||
* Forward a port to your local machine:<br>
|
||||
`gh codespace ports forward 8000:8000 -c mona-github-docs-v4qxrv7rfwv9w`
|
||||
`gh codespace ports forward 8000:8000 -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
|
||||
|
||||
## `gh` commands for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
The sections below give example commands for each of the available operations.
|
||||
|
||||
For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, use `gh codespace [<SUBCOMMAND>...] --help` on the command line.
|
||||
For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, on the command line, use `gh codespace --help` for general help or `gh codespace SUBCOMMAND --help` for help with a specific subcommand.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -163,7 +163,7 @@ The location of files and directories on the codespace is relative to the home d
|
||||
|
||||
* Copy a file to the directory in which a repository is checked out in a codespace:
|
||||
|
||||
`gh codespace cp myfile.txt remote:/workspaces/<REPOSITORY-NAME>`
|
||||
`gh codespace cp myfile.txt remote:/workspaces/REPOSITORY-NAME`
|
||||
|
||||
* Copy a file from a codespace to the current directory on the local machine:
|
||||
|
||||
@@ -233,7 +233,7 @@ You can use the {% data variables.product.prodname_cli %} extension to create a
|
||||
### Change the machine type of a codespace
|
||||
|
||||
```shell
|
||||
gh codespace edit -m <em>machine-type-name</em>
|
||||
gh codespace edit -m MACHINE-TYPE-NAME
|
||||
```
|
||||
|
||||
For more information, see the "{% data variables.product.prodname_cli %}" tab of "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: The github.dev web-based editor
|
||||
intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.'
|
||||
title: github.dev Web ベース エディター
|
||||
intro: 'リポジトリから github.dev {% data variables.product.prodname_serverless %} を使用するか、pull request を使用して変更を作成およびコミットします。'
|
||||
versions:
|
||||
feature: githubdev-editor
|
||||
type: how_to
|
||||
@@ -12,104 +12,108 @@ topics:
|
||||
shortTitle: Web-based editor
|
||||
redirect_from:
|
||||
- /codespaces/developing-in-codespaces/web-based-editor
|
||||
ms.openlocfilehash: d1c21f3e75ecc4fec282c9156943c137287d203c
|
||||
ms.sourcegitcommit: caab4edbbeedf23e9062e48a67c35224772b6efa
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160478'
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/general).
|
||||
**注：** 現在、github.dev {% data variables.product.prodname_serverless %} はベータ プレビュー段階です。 ユーザーは[ディスカッションで](https://github.com/community/community/discussions/categories/general)フィードバックを提供できます。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About the {% data variables.product.prodname_serverless %}
|
||||
## {% data variables.product.prodname_serverless %} について
|
||||
|
||||
The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor.
|
||||
{% data variables.product.prodname_serverless %} では、完全にブラウザー内で実行される軽量な編集エクスペリエンスが導入されています。 {% data variables.product.prodname_serverless %} を使用すると、{% data variables.product.prodname_dotcom %} からファイルとソース コード リポジトリに移動し、コードの変更を行ってコミットできます。 ユーザーは任意のリポジトリ、フォーク、または pull request をエディターで開くことができます。
|
||||
|
||||
The {% data variables.product.prodname_serverless %} is available to everyone for free on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% data variables.product.prodname_serverless %} は、{% data variables.product.prodname_dotcom_the_website %} から誰でも無料で入手できます。
|
||||
|
||||
The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode_shortname %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data variables.product.prodname_serverless %} では、検索、構文の強調表示、ソース管理ビューなど、{% data variables.product.prodname_vscode %} の多くの利点が提供されます。 Settings Sync を使用して、独自の {% data variables.product.prodname_vscode_shortname %} 設定をエディターと共有することもできます。 詳しい情報については、{% data variables.product.prodname_vscode_shortname %} ドキュメントの「[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)」を参照してください。
|
||||
|
||||
The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.
|
||||
{% data variables.product.prodname_serverless %} は、完全にブラウザーのサンドボックス内で実行されます。 エディターではリポジトリは複製されず、代わりに [GitHub Repositories 拡張機能](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)を使用して、ユーザーが使用するほとんどの機能が実行されます。 作業内容は、コミットするまでブラウザーのローカル ストレージに保存されます。 変更内容に常にアクセスできるようにするために、変更を定期的にコミットするようにしてください。
|
||||
|
||||
You must be signed in to use the web-based editor.
|
||||
Web ベースのエディターを使用するには、サインインする必要があります。
|
||||
|
||||
## Opening the {% data variables.product.prodname_serverless %}
|
||||
## {% data variables.product.prodname_serverless %} を開く
|
||||
|
||||
You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways:
|
||||
{% data variables.product.prodname_serverless %} で {% data variables.product.prodname_dotcom %} リポジトリを開くには、次のいずれかの方法を使用できます。
|
||||
|
||||
- To open the repository in the same browser tab, press <kbd>.</kbd> while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
|
||||
- 同じブラウザー タブでリポジトリを開くには、<kbd>.</kbd> キーを押します ({% data variables.product.prodname_dotcom %} のリポジトリまたは pull request を参照しているとき)。
|
||||
|
||||
To open the repository in a new browser tab, press <kbd>></kbd>.
|
||||
新しいブラウザー タブでリポジトリを開くには、<kbd>></kbd> キーを押します。
|
||||
|
||||
- Change the URL from "github.com" to "github.dev".
|
||||
- When viewing a file, use the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and select **Open in github.dev**.
|
||||
- URL を "github.com" から "github.dev" に変更します。
|
||||
- ファイルを表示する場合は、{% octicon "pencil" aria-label="The edit icon" %} の横にあるドロップダウン メニューを使用し、 **[github.dev で開く]** を選びます。
|
||||
|
||||
|
||||
|
||||
|
||||
## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %}
|
||||
## {% data variables.product.prodname_codespaces %} と {% data variables.product.prodname_serverless %}
|
||||
|
||||
Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_github_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case.
|
||||
{% data variables.product.prodname_serverless %} と {% data variables.product.prodname_github_codespaces %} のどちらでも、リポジトリから直接コードを編集できます。 ただし、ユース ケースによって、それぞれの利点が若干異なります。
|
||||
|
||||
|| {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_github_codespaces %}|
|
||||
|-|----------------|---------|
|
||||
| **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 %}.|
|
||||
| **コスト** | フリー。 | 個人用アカウントでの 1 か月あたりの使用量の Free クォータ。 詳しくは、「[{% data variables.product.prodname_github_codespaces %} の課金について](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)」を参照してください。|
|
||||
| **可用性** | GitHub.com のすべてのユーザーが利用できます。 | GitHub.com のすべてのユーザーが利用できます。 |
|
||||
| **起動** | {% data variables.product.prodname_serverless %} は、キーを押すとすぐに開き、追加の構成やインストールを待たずにすぐに使用を開始できます。 | codespace を作成または再開すると、codespace に VM が割り当てられ、`devcontainer.json` ファイルの内容に基づいてコンテナーが構成されます。 この設定では、環境の作成に数分かかる場合があります。 詳しくは、「[リポジトリの codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)」を参照してください。 |
|
||||
| **Compute** | 関連付けられたコンピューティングがないので、コードをビルドして実行したり、統合ターミナルを使用したりすることはできません。 | {% data variables.product.prodname_github_codespaces %} を使うと、専用の VM を通じてアプリケーションを実行およびデバッグできます。|
|
||||
| **ターミナル アクセス** | [なし] : | {% data variables.product.prodname_github_codespaces %} には、既定で共通のツール セットが用意されています。つまり、ローカル環境の場合とまったく同じようにターミナルを使用できます。|
|
||||
| **拡張機能** | Web で実行できる拡張機能のサブセットのみが拡張機能ビューに表示され、それらをインストールできます。 詳細については、「[拡張機能の使用](#using-extensions)」を参照してください。| {% data variables.product.prodname_github_codespaces %} では、{% data variables.product.prodname_vscode_marketplace %} のほとんどの拡張機能を使用できます。|
|
||||
|
||||
### Continue working on {% data variables.product.prodname_codespaces %}
|
||||
### 引き続き {% data variables.product.prodname_codespaces %} で作業する
|
||||
|
||||
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 %}.
|
||||
{% data variables.product.prodname_serverless %}でワークフローを開始して、codespace で作業を続けることができます。 実行およびデバッグ ビューまたはターミナルにアクセスしようとすると、{% 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.
|
||||
codespace で作業を続行するには、 **[Continue Working on…]\(作業の続行...\)** をクリックし、 **[Create New Codespace]\(新しい codespace の作成\)** を選択して、現在のブランチに codespace を作成します。 このオプションを選択する前に、変更をコミットする必要があります。
|
||||
|
||||
|
||||
![UI の [Continue Working on]\(作業の続行\) ボタンを示すスクリーンショット](/assets/images/help/codespaces/codespaces-continue-working.png)
|
||||
|
||||
## Using source control
|
||||
## ソース管理の使用
|
||||
|
||||
When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data variables.product.prodname_serverless %} を使用する場合、すべてのアクションは左側のアクティビティ バーにあるソース管理ビューで管理されます。 ソース管理ビューの詳細については、{% data variables.product.prodname_vscode_shortname %} ドキュメントの「[バージョン管理](https://code.visualstudio.com/docs/editor/versioncontrol)」を参照してください。
|
||||
|
||||
Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
Web ベース エディターでは GitHub Repositories 拡張機能を使用して機能が強化されるため、変更を一時退避することなくブランチを切り替えることができます。 詳しい情報については、{% data variables.product.prodname_vscode_shortname %} ドキュメントの「[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)」を参照してください。
|
||||
|
||||
### Create a new branch
|
||||
### 新しいブランチを作成する
|
||||
|
||||
{% data reusables.codespaces.create-or-switch-branch %}
|
||||
Any uncommitted changes you have made in your old branch will be available on your new branch.
|
||||
{% data reusables.codespaces.create-or-switch-branch %} 古いブランチで行った変更のうち、コミットされていないものは新しいブランチで使用できます。
|
||||
|
||||
### Commit your changes
|
||||
### 変更をコミットする
|
||||
|
||||
{% data reusables.codespaces.source-control-commit-changes %}
|
||||
5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}.
|
||||
### Create a pull request
|
||||
5. 変更をコミットすると、{% data variables.product.prodname_dotcom %} のブランチに自動的にプッシュされます。
|
||||
### pull request を作成する
|
||||
|
||||
{% data reusables.codespaces.source-control-pull-request %}
|
||||
|
||||
### Working with an existing pull request
|
||||
### 既存の pull request の操作
|
||||
|
||||
You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request.
|
||||
既存の pull request は、{% data variables.product.prodname_serverless %}を使用して操作できます。
|
||||
|
||||
1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}.
|
||||
2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}.
|
||||
3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes.
|
||||
1. {% data variables.product.prodname_serverless %} で開きたい pull request を参照します。
|
||||
2. `.` を押して、{% data variables.product.prodname_serverless %} で pull request を開きます。
|
||||
3. 変更を行ったら、「[変更をコミットする](#commit-your-changes)」の手順を使用して変更をコミットします。 変更はブランチに直接コミットされます。変更をプッシュする必要はありません。
|
||||
|
||||
## Using extensions
|
||||
## 拡張機能の使用
|
||||
|
||||
The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode_shortname %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data variables.product.prodname_serverless %} では、Web で実行するために作成または更新された {% data variables.product.prodname_vscode_shortname %} 拡張機能がサポートされています。 これらの拡張機能は、"Web 拡張機能" と呼ばれます。 Web 拡張機能を作成する方法、または Web で動作するように既存の拡張機能を更新する方法については、{% data variables.product.prodname_vscode_shortname %} ドキュメントの「[Web 拡張機能](https://code.visualstudio.com/api/extension-guides/web-extensions)」を参照してください。
|
||||
|
||||
Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data variables.product.prodname_serverless %} で実行できる拡張機能は、拡張機能ビューに表示され、インストールできます。 Settings Sync を使用すると、互換性のある拡張機能も自動的にインストールされます。 詳細については、{% data variables.product.prodname_vscode_shortname %} ドキュメントの「[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)」を参照してください。
|
||||
|
||||
|
||||
## Troubleshooting
|
||||
## トラブルシューティング
|
||||
|
||||
If you have issues opening the {% data variables.product.prodname_serverless %}, try the following:
|
||||
{% data variables.product.prodname_serverless %}を開くときに問題が発生した場合は、次の手順を試してください。
|
||||
|
||||
- Make sure you are signed in to {% data variables.product.prodname_dotcom %}.
|
||||
- Disable any ad blockers.
|
||||
- Use a non-incognito window in your browser to open the {% data variables.product.prodname_serverless %}.
|
||||
- {% data variables.product.prodname_dotcom %} にサインインしていることを確認します。
|
||||
- 広告ブロッカーを無効にします。
|
||||
- ブラウザーで incognito 以外のウィンドウを使用して、{% data variables.product.prodname_serverless %}を開きます。
|
||||
|
||||
### Known limitations
|
||||
### 既知の制限事項
|
||||
|
||||
- The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
|
||||
- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
- `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`.
|
||||
- 現在、{% data variables.product.prodname_serverless %}は、Chrome (およびその他の各種 Chromium ベース ブラウザー)、Edge、Firefox、Safari でサポートされています。 最新バージョンの SDK を使用することをお勧めします。
|
||||
- 使用しているブラウザーによっては、一部のキー バインドが機能しない場合があります。 これらのキー バインドの制限事項は、{% data variables.product.prodname_vscode_shortname %} ドキュメントの[既知の制限事項と対応](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)に関するセクションに記載されています。
|
||||
- ご使用のローカル キーボード レイアウトによっては、`.` で {% data variables.product.prodname_serverless %}を開くことができない場合があります。 その場合は、URL を `github.com` から `github.dev` に変更することで、{% data variables.product.prodname_dotcom %} リポジトリを {% data variables.product.prodname_serverless %}で開くことができます。
|
||||
|
||||
@@ -1,41 +1,46 @@
|
||||
---
|
||||
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.'
|
||||
title: GitHub Copilot について
|
||||
intro: '{% data variables.product.prodname_copilot %} はオートコンプリート スタイルの候補を提示することでコーディングを支援します。 {% data variables.product.prodname_copilot %} を使うための注意点や、{% data variables.product.prodname_copilot %} のしくみについて説明します。'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
shortTitle: About GitHub Copilot
|
||||
ms.openlocfilehash: dd4538cb4cf6fc9dd84bb3f0d05bf8a85559d5ec
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160641'
|
||||
---
|
||||
## {% data variables.product.prodname_copilot %} について
|
||||
|
||||
## About {% data variables.product.prodname_copilot %}
|
||||
{% data variables.product.prodname_copilot %} では、コーディング時にオートコンプリート スタイルの候補を提示する AI ペア プログラマーです。 使用するコードを書き始めるか、そのコードに何をさせたいかを自然言語のコメントで記述することで、{% data variables.product.prodname_copilot %} から候補を取り入れることができます。 {% data variables.product.prodname_copilot %} は、編集中のファイルや関連ファイルのコンテキストを分析し、テキスト エディター内から候補の提示を行います。 {% data variables.product.prodname_copilot %} は、OpenAI によって作成された新しい AI システムである OpenAI Codex を利用しています。
|
||||
|
||||
{% 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 %} は、パブリック リポジトリに表示されるすべて言語でトレーニングされます。 各言語で、受け取る提案の品質は、その言語のトレーニング データの量と多様性によって異なります。 たとえば、JavaScript は、パブリック リポジトリで適切に表現されており、{% data variables.product.prodname_copilot %} でサポートされている最適な言語の 1 つです。 パブリック リポジトリでの表現が少ない言語では、生成される候補の信頼性が低下する可能性があります。
|
||||
|
||||
{% 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.
|
||||
{% data variables.product.prodname_copilot %} は、Visual Studio Code、Visual Studio、Neovim、JetBrains での一連の IDE で拡張機能として使用できます。 詳しくは、「[{% data variables.product.prodname_copilot %} の概要](/copilot/getting-started-with-github-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)."
|
||||
## {% data variables.product.prodname_copilot %} の使用
|
||||
|
||||
## Using {% data variables.product.prodname_copilot %}
|
||||
{% data variables.product.prodname_copilot %} の動作する実際の例を確認することができます。 詳しくは、[{% data variables.product.prodname_copilot %}](https://copilot.github.com/) の Web サイトを参照してください。
|
||||
|
||||
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.
|
||||
GitHub Copilot は、OpenAI が何十億行ものオープンソース コードにより構築されたモデルから候補を提示します。 その結果、{% data variables.product.prodname_copilot %} のトレーニング セットには、安全でないコーディング パターン、バグ、または古い API やイディオムへの参照が含まれている可能性があります。 {% data variables.product.prodname_copilot %} がこのトレーニング データに基づいて候補を生成する場合、それらの候補にも望ましくないパターンが含まれる場合があります。
|
||||
|
||||
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 %} で生成されたコードを使うときは、自分自身で書いていないコードを使うときと同じ予防措置を講じることをお勧めします。 これらの予防措置には、厳密なテスト、IP スキャン、セキュリティの脆弱性の追跡などが含まれます。 {% data variables.product.company_short %} には、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_dependabot %}、{% data variables.product.prodname_codeql %}、{% data variables.product.prodname_code_scanning %} など、コード品質を監視および改善できる多数の機能が用意されています。 これらの機能はすべて、パブリック リポジトリで自由に使用できます。 詳しくは、「[{% data variables.product.prodname_actions %} について](/actions/learn-github-actions/understanding-github-actions)」と「[{% data variables.product.company_short %} のセキュリティ機能](/code-security/getting-started/github-security-features)」を参照してください。
|
||||
|
||||
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)."
|
||||
|
||||
{% 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 %} では、プロンプト内の不快な単語をブロックし、機密性の高いコンテキストにある候補を生成しないようにフィルターを使っています。 私たちは、{% data variables.product.prodname_copilot %} によって生成された不快な候補 (偏った、差別的、または虐待的な出力など) をよりインテリジェントに検出して削除するため、フィルター システムを常に改善することに取り組んでいます。 {% data variables.product.prodname_copilot %} によって生成された不快な候補が表示される場合は、安全対策を改善できるように、その候補を copilot-safety@github.com に直接報告してください。
|
||||
|
||||
{% data reusables.copilot.emus-cannot-use-copilot %}
|
||||
|
||||
## About billing for {% data variables.product.prodname_copilot %}
|
||||
## {% data variables.product.prodname_copilot %} の課金について
|
||||
|
||||
{% 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)."
|
||||
{% data variables.product.prodname_copilot %} は有料機能であり、月単位または年単位のサブスクリプションが必要です。 確認が取れている学生、教師、および {% data variables.product.prodname_dotcom %} 上のオープン ソース プロジェクトのメンテナンス担当者は、{% data variables.product.prodname_copilot %} を無料で使うことができます。 無料の {% data variables.product.prodname_copilot %} サブスクリプションの条件を満たしている場合は、{% data variables.product.prodname_copilot %} サブスクリプション ページにアクセスしたときに、自動的に通知されます。 無料の {% data variables.product.prodname_copilot %} サブスクリプションの条件を満たしていない場合、60 日間の無料試用版が提供され、その後継続して使うには有料のサブスクリプションが必要になります。 詳細については、「[{% data variables.product.prodname_copilot %} の課金について](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
|
||||
|
||||
## About the license for the {% data variables.product.prodname_copilot %} plugin in JetBrains IDEs
|
||||
## JetBrains IDE での {% data variables.product.prodname_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.
|
||||
{% data variables.product.prodname_dotcom %}, Inc. は、JetBrains プラグインのライセンサーです。 このプラグインのエンド ユーザー ライセンス契約は、[{% data variables.product.prodname_dotcom %} 追加製品および機能の利用規約](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)であり、このプラグインの使用はこれらの利用規約の対象となります。 JetBrains は、本プラグインまたはかかる契約に関連して、一切の責任または義務を負わないものとします。 プラグインを使うことにより、お客様は前述の利用規約に同意したものと見なされます。
|
||||
|
||||
## 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)"
|
||||
- 「[{% data variables.product.company_short %} 追加製品および機能の利用規約](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)」
|
||||
|
||||
@@ -6,12 +6,12 @@ versions:
|
||||
topics:
|
||||
- Webhooks
|
||||
shortTitle: Receiving webhooks with the GitHub CLI
|
||||
ms.openlocfilehash: 2772a9d4208d0afe77871255ad6510b7f39de8d5
|
||||
ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
|
||||
ms.openlocfilehash: 11bc5b476a191a61594cb73f1e6ce1be5bb6cf9b
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/04/2022
|
||||
ms.locfileid: '148132964'
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160665'
|
||||
---
|
||||
## {% data variables.product.prodname_cli %} を使った Webhook の受信について
|
||||
|
||||
|
||||
@@ -205,6 +205,8 @@ Members of your organization or enterprise can use GitHub's learning and support
|
||||
### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot.
|
||||
|
||||
|
||||
@@ -119,6 +119,8 @@ Your enterprise members can learn more about Git and {% data variables.product.p
|
||||
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
{% data reusables.getting-started.learning-enterprise %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub glossary
|
||||
intro: 'This glossary introduces common Git and {% data variables.product.prodname_dotcom %} terminology.'
|
||||
title: GitHub 用語集
|
||||
intro: 'この用語集では、一般的な Git と {% data variables.product.prodname_dotcom %} の用語が紹介されています。'
|
||||
redirect_from:
|
||||
- /articles/github-glossary
|
||||
- /github/getting-started-with-github/github-glossary
|
||||
@@ -10,6 +10,12 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
ms.openlocfilehash: 3595b29a43cd7181bf5203f892b3bee84a237c29
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160845'
|
||||
---
|
||||
{% for glossary in glossaries %}
|
||||
### {{ glossary.term }}
|
||||
@@ -19,8 +25,8 @@ versions:
|
||||
|
||||
---
|
||||
|
||||
## Further reading
|
||||
## 参考資料
|
||||
|
||||
- [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)
|
||||
- [公式 Git 用語集](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html)
|
||||
- [Git のドキュメント](https://git-scm.com/doc)
|
||||
- [Git コマンド一覧](https://git-scm.com/docs)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Enterprise Cloud のトライアルを設定する
|
||||
intro: '{% data variables.product.prodname_ghe_cloud %} を無料で試すことができます。'
|
||||
title: Setting up a trial of GitHub Enterprise Cloud
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
|
||||
redirect_from:
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-cloud
|
||||
- /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
|
||||
@@ -12,74 +12,73 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Cloud trial
|
||||
ms.openlocfilehash: 13cb43b5dfd4a9e207a9a1cca090b223c56f4678
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147389955'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise.ghec-cta-button %}
|
||||
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %} について
|
||||
## About {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} は、{% data variables.product.prodname_dotcom_the_website %} で共同作業を行う大企業またはチーム向けのプランです。 {% data reusables.enterprise.about-github-for-enterprises %}
|
||||
{% data variables.product.prodname_ghe_cloud %} is a plan for large businesses or teams who collaborate on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise.about-github-for-enterprises %}
|
||||
|
||||
{% data reusables.organizations.about-organizations %} アカウントの詳細については、「[{% data variables.product.prodname_dotcom %} アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」を参照してください。
|
||||
{% data reusables.organizations.about-organizations %} For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
|
||||
|
||||
限られた機能を含む {% data variables.product.prodname_free_team %} を使用して、組織を無料で使用できます。 SAML シングル サインオン (SSO)、{% data variables.product.prodname_pages %} のアクセス制御、含まれる {% data variables.product.prodname_actions %} 分などの追加機能が必要な場合は、{% data variables.product.prodname_ghe_cloud %} にアップグレードできます。 {% data variables.product.prodname_ghe_cloud %} で使用できる機能の詳細な一覧については、[価格](https://github.com/pricing)に関するページを参照してください。
|
||||
You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} の試用版を設定して、新規または既存の組織アカウントでこれらの追加機能を評価できます。
|
||||
You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} のトライアルも利用できます。 詳細については、「[{% data variables.product.prodname_ghe_server %} の試用版を設定する](/articles/setting-up-a-trial-of-github-enterprise-server)」を参照してください。
|
||||
Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %} の試用版について
|
||||
## About trials of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} を評価するための 30 日間の試用版を設定できます。 支払方法が必要な {% data variables.product.prodname_marketplace %} アプリを Organization に追加しない限り、トライアル期間中に支払方法を指定する必要はありません。 詳細については、「[{% data variables.product.prodname_marketplace %} の請求について](/enterprise-cloud@latest/articles/about-billing-for-github-marketplace/)」を参照してください。
|
||||
You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/enterprise-cloud@latest/articles/about-billing-for-github-marketplace/)."
|
||||
|
||||
トライアルには50シートが含まれています。 {% data variables.product.prodname_ghe_cloud %} を評価するためにより多くのシートが必要な場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 トライアルの終了時に、別のシート数を選択できます。
|
||||
Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
|
||||
|
||||
{% data reusables.saml.saml-accounts %}
|
||||
|
||||
詳細については、{% ifversion not ghec %}{% data variables.product.prodname_ghe_cloud %} ドキュメントの{% else %}「[SAML シングル サインオンによる ID とアクセスの管理について](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。{% endif %}
|
||||
For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
{% data variables.product.prodname_emus %} は、{% data variables.product.prodname_ghe_cloud %} の無料試用版の一部ではありません。 {% data variables.product.prodname_emus %} に関心がある場合は、[{% data variables.product.prodname_dotcom %} の営業チーム](https://enterprise.github.com/contact)にお問い合わせください。
|
||||
{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %} のトライアルを設定する
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} を試す前に、個人アカウントにサインインする必要があります。 {% data variables.product.prodname_dotcom_the_website %} の個人アカウントをまだ持っていない場合、作成する必要があります。 詳細については、「[新しい {% data variables.product.prodname_dotcom %} アカウントにサインアップする](/free-pro-team@latest/articles/signing-up-for-a-new-github-account)」を参照してください。
|
||||
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a personal account. If you don't already have a personal account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/free-pro-team@latest/articles/signing-up-for-a-new-github-account)."
|
||||
|
||||
1. [エンタープライズの {% data variables.product.prodname_dotcom %}](https://github.com/enterprise) に移動します。
|
||||
1. **[無料試用版を開始する]** をクリックします。
|
||||
![[無料試用版を開始する] ボタン](/assets/images/help/organizations/start-a-free-trial-button.png)
|
||||
1. **[Enterprise Cloud]** をクリックします。
|
||||
![[Enterprise Cloud] ボタン](/assets/images/help/organizations/enterprise-cloud-trial-option.png)
|
||||
1. プロンプトに従って試用版を構成します。
|
||||
1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
|
||||
1. Click **Start a free trial**.
|
||||
|
||||
1. Click **Enterprise Cloud**.
|
||||
|
||||
1. Follow the prompts to configure your trial.
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %} に触れる
|
||||
## Exploring {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
試用版の設定後、Organization の [概要] タブで提案されているタスクに従い、{% data variables.product.prodname_ghe_cloud %} をいろいろ試すことができます。 以前にタスクを閉じていた場合、ページの上部にある **[提案されたタスクを始める]** をクリックしてそのタスクにもう一度アクセスできます。
|
||||
After you set up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the suggested tasks on the "Overview" tab of your organization. If you've previously dismissed the tasks, you can access them again by clicking **Get started with suggested tasks** at the top of the page.
|
||||
|
||||
![[提案されたタスクを始める] ボタン](/assets/images/help/organizations/suggested-tasks-button.png)
|
||||
|
||||
|
||||
{% data reusables.docs.you-can-read-docs-for-your-product %}
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## トライアルを終了する
|
||||
## Finishing your trial
|
||||
|
||||
{% data variables.product.prodname_enterprise %} は、試用期間中いつでも購入できます。 {% data variables.product.prodname_enterprise %} を購入すると試用期間が終了し、50 シートの上限が削除され、支払いが開始されます。
|
||||
You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
|
||||
|
||||
{% data variables.product.prodname_enterprise %} を購入しない場合、試用期間が終了すると、組織はダウングレードされます。 試用版に既存の組織を使用した場合、試用版の前に使用していた製品に組織がダウングレードされます。 試用版用に新しい組織を作成した場合、組織は {% data variables.product.prodname_free_team %} にダウングレードされます。
|
||||
If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}.
|
||||
|
||||
組織は、プライベート リポジトリの {% data variables.product.prodname_pages %} などの高度な機能など、新しい製品に含まれていない機能にアクセスできなくなります。 アップグレードする予定がない場合は、高度な機能へのアクセスを失わないように、試用期間の終了前にリポジトリを公開してください。 詳細については、「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。
|
||||
Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
|
||||
|
||||
ダウングレードすると、試用期間中に構成された SAML 設定も無効になります。 その後 {% data variables.product.prodname_enterprise %} を購入すると、組織内のユーザーが認証できるように SAML 設定が再度有効になります。
|
||||
Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.billing_plans %}
|
||||
5. [{% data variables.product.prodname_ghe_cloud %} 無料試用版] で、 **[エンタープライズの購入]** または **[チームにダウングレード]** をクリックします。
|
||||
![[エンタープライズの購入] ボタンと [チームにダウングレード] ボタン](/assets/images/help/organizations/finish-trial-buttons.png)
|
||||
6. プロンプトに従って支払い方法を入力し、 **[送信]** をクリックします。
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
|
||||
|
||||
6. Follow the prompts to enter your payment method, then click **Submit**.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Enterprise Server のトライアルを設定する
|
||||
intro: '{% data variables.product.prodname_ghe_server %} のトライアルは無料でできます。'
|
||||
title: Setting up a trial of GitHub Enterprise Server
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
|
||||
redirect_from:
|
||||
- /articles/requesting-a-trial-of-github-enterprise
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-server
|
||||
@@ -13,61 +13,58 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Server trial
|
||||
ms.openlocfilehash: eba705715818c03cb7fd1316ede6507111728806
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146454238'
|
||||
---
|
||||
## {% data variables.product.prodname_ghe_server %} の試用版について
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} を評価するための 45 日間トライアルをリクエストできます。 トライアルは仮想アプライアンスとしてインストールされ、オンプレミスまたはクラウドでのデプロイメントのオプションがあります。 {% data variables.product.prodname_ghe_server %} に関する詳しい情報と、サポートされている仮想化プラットフォームの一覧については、「[{% data variables.product.prodname_ghe_server %} について](/enterprise-server/admin/overview/about-github-enterprise-server)」を参照してください。
|
||||
## About trials of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}セキュリティ{% endif %} アラートと {% data variables.product.prodname_github_connect %} は、{% data variables.product.prodname_ghe_server %} の試用版では現在利用できません。 これらの機能のデモについては、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 これらの機能の詳細については、「[{% data variables.product.prodname_dependabot_alerts %} について](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」と「[エンタープライズ アカウントを {% data variables.product.prodname_ghe_cloud %} に接続する](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)」を参照してください。
|
||||
You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For more information about {% data variables.product.prodname_ghe_server %}, and for a list of supported virtualization platforms, see "[About {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)."
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} のトライアルも利用できます。 詳細については、「[{% data variables.product.prodname_ghe_cloud %} の試用版を設定する](/articles/setting-up-a-trial-of-github-enterprise-cloud)」を参照してください。
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
|
||||
Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## {% data variables.product.prodname_ghe_server %} のトライアルを設定する
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} は仮想アプライアンスとしてインストールされます。 組織で仮想マシンをセットアップするのに最適な担当者を決定し、その担当者に[試用版のリクエスト](https://enterprise.github.com/trial)をサブミットするよう依頼してください。 トライアルはリクエストをサブミットした直後に開始できます。
|
||||
{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
|
||||
|
||||
{% data variables.product.prodname_enterprise %} ウェブポータルのアカウントをセットアップするため、トライアルリクエストをサブミットした後に受信したメールにあるリンクをクリックして、プロンプトに従います。 次に、ライセンスファイルをダウンロードします。 詳細については、「[{% data variables.product.prodname_enterprise %} のライセンスの管理](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)」を参照してください。
|
||||
To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} をインストールするために必要なコンポーネントをダウンロードしてライセンスファイルをアップロードします。 詳細については、「[{% data variables.product.prodname_ghe_server %} インスタンスを設定する](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)」の選択した視覚化プラットフォームの手順を参照してください。
|
||||
To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
|
||||
## 次の手順
|
||||
## Next steps
|
||||
|
||||
トライアルを最大限に活用するためには、次の手順に従ってください:
|
||||
To get the most out of your trial, follow these steps:
|
||||
|
||||
1. [組織の作成](/enterprise-server@latest/admin/user-management/creating-organizations)。
|
||||
2. {% data variables.product.prodname_dotcom %} の基本的な使い方を学ぶには、次を参照してください:
|
||||
- [{% data variables.product.prodname_dotcom %} の概要](https://resources.github.com/devops/methodology/maximizing-devops-roi/) Web キャスト
|
||||
- {% data variables.product.prodname_dotcom %} ガイドの [{% data variables.product.prodname_dotcom %} フローについて](https://guides.github.com/introduction/flow/)
|
||||
- {% data variables.product.prodname_dotcom %} ガイドの [Hello World](https://guides.github.com/activities/hello-world/)
|
||||
- 「[{% data variables.product.prodname_docs %} のバージョンについて](/get-started/learning-about-github/about-versions-of-github-docs)」
|
||||
3. 組織のニーズを満たすようにインスタンスを構成するには、「[エンタープライズの構成](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)」を参照してください。
|
||||
4. {% data variables.product.prodname_ghe_server %} を ID プロバイダーと統合するには、「[SAML の使用](/enterprise-server@latest/admin/user-management/using-saml)」および「[LDAP の使用](/enterprise-server@latest/admin/authentication/using-ldap)」を参照してください。
|
||||
5. 個人をトライアルに招待します。人数制限はありません。
|
||||
- ビルトイン認証または設定済みアイデンティティプロバイダを使用して、ユーザを {% data variables.product.prodname_ghe_server %} インスタンスに追加します。 詳細については、「[ビルトイン認証を使用する](/enterprise-server@latest/admin/user-management/using-built-in-authentication)」を参照してください。
|
||||
- ユーザーをアカウント管理者に招待するには、[{% data variables.product.prodname_enterprise %} Web ポータル](https://enterprise.github.com/login)にアクセスします。
|
||||
1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
|
||||
2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
|
||||
- [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast
|
||||
- [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
|
||||
3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
|
||||
4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
|
||||
5. Invite an unlimited number of people to join your trial.
|
||||
- Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
|
||||
- To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** アカウント管理者になるよう招待された個人は、招待を承諾するためのリンクを含むメールを受信します。
|
||||
**Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## トライアルを終了する
|
||||
## Finishing your trial
|
||||
|
||||
試用期間中いつでも [{% data variables.product.prodname_enterprise %} Web ポータル](https://enterprise.github.com/login)でフル ライセンスにアップグレードできます。
|
||||
You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
|
||||
|
||||
トライアル最終日になってもアップグレードしていない場合、トライアルが終了したことを通知するメールが送信されます。 {% data variables.product.prodname_enterprise %} を評価するための時間がさらに必要な場合は、{% data variables.contact.contact_enterprise_sales %} に連絡して延長をリクエストしてください。
|
||||
If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- 「[{% data variables.product.prodname_ghe_cloud %} の試用版を設定する](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)」
|
||||
- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Attaching files
|
||||
intro: You can convey information by attaching a variety of file types to your issues and pull requests.
|
||||
title: ファイルのアタッチ
|
||||
intro: さまざまな種類のファイルを issue や pull request に添付することで、情報を伝達できます。
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/file-attachments-on-issues-and-pull-requests
|
||||
- /articles/issue-attachments
|
||||
@@ -14,48 +14,51 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Pull requests
|
||||
ms.openlocfilehash: 28ce895a23c83f410d4755ad4036673e5c816155
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160764'
|
||||
---
|
||||
|
||||
{% data reusables.repositories.anyone-can-view-anonymized-url %}
|
||||
|
||||
To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer.
|
||||
Issue やプルリクエストの会話にファイルを添付するには、コメントボックスにファイルをドラッグアンドドロップします。 または、コメントボックスの下部にあるバーをクリックしてコンピュータからファイルを参照、選択、追加することもできます。
|
||||
|
||||
|
||||
|
||||
|
||||
When you attach a file, it is uploaded immediately to {% data variables.product.product_name %} and the text field is updated to show the anonymized URL for the file. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
|
||||
ファイルを添付すると、ファイルが {% data variables.product.product_name %} にすぐにアップロードされ、テキスト フィールドが更新されて、ファイルの匿名化された URL が表示されます。 {% ifversion fpt or ghec %}匿名化された URL の詳細については、「[匿名化された URL について](/github/authenticating-to-github/about-anonymized-urls)」を参照してください。{% endif %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** In many browsers, you can copy-and-paste images directly into the box.
|
||||
**ヒント:** 多くのブラウザーでは、画像をコピーしてボックスに直接貼り付けることができます。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
The maximum file size is:
|
||||
- 10MB for images and gifs{% ifversion fpt or ghec %}
|
||||
- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
|
||||
- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif ghes %}
|
||||
- 100MB for videos{% endif %}
|
||||
- 25MB for all other files
|
||||
最大ファイル サイズ:
|
||||
- 画像と gif については 10MB{% ifversion fpt or ghec %}
|
||||
- 無料の GitHub プランのユーザーまたは組織が所有するリポジトリにアップロードされた動画については 10MB
|
||||
- 有料の GitHub プランのユーザーまたは Organization が所有するリポジトリにアップロードされた動画については 100 MB{% elsif ghes %}
|
||||
- 動画については 100MB{% endif %}
|
||||
- その他のすべてのファイルでは 25MB
|
||||
|
||||
We support these files:
|
||||
以下のファイルがサポートされています:
|
||||
|
||||
* PNG (*.png*)
|
||||
* GIF (*.gif*)
|
||||
* JPEG (*.jpg*)
|
||||
{%- ifversion svg-support %}
|
||||
* SVG (*.svg*)
|
||||
{%- endif %}
|
||||
* Log files (*.log*)
|
||||
* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
|
||||
* Text files (*.txt*)
|
||||
* PDFs (*.pdf*)
|
||||
* ZIP (*.zip*, *.gz*, *.tgz*){% ifversion fpt or ghec or ghes %}
|
||||
* Video (*.mp4*, *.mov*, *.webm*){% endif %}
|
||||
* PNG ( *.png*)
|
||||
* GIF ( *.gif*)
|
||||
* JPEG ( *.jpg*) {%- ifversion svg-support %}
|
||||
* SVG ( *.svg*) {%- endif %}
|
||||
* ログ ファイル ( *.log*)
|
||||
* Microsoft Word ( *.docx*)、Powerpoint ( *.pptx*)、Excel ( *.xlsx*) の各ドキュメント
|
||||
* テキスト ファイル ( *.txt*)
|
||||
* PDF ( *.pdf*)
|
||||
* ZIP ( *.zip*、 *.gz*、 *.tgz*){% ifversion fpt or ghec or ghes %}
|
||||
* 動画 ( *.mp4*、 *.mov*、 *.webm*){% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}{% note %}
|
||||
|
||||
**Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using h.264 for greatest compatibility.
|
||||
**注意:** 動画コーデックの互換性はブラウザー固有であり、あるブラウザーにアップロードした動画が別のブラウザーでは表示されない可能性があります。 現時点では、最大の互換性がある h.264 を使うことをお勧めします。
|
||||
|
||||
{% endnote %}{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Organizationについて
|
||||
intro: Organization は、高度なセキュリティと管理機能を使って、企業とオープンソース プロジェクトが一度に多くのプロジェクト間で共同作業ができる共有アカウントです。
|
||||
title: About organizations
|
||||
intro: 'Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.'
|
||||
redirect_from:
|
||||
- /articles/about-organizations
|
||||
- /github/setting-up-and-managing-organizations-and-teams/about-organizations
|
||||
@@ -12,48 +12,48 @@ versions:
|
||||
topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
ms.openlocfilehash: e18c95475e06db0623aee67515eeb6d8a1ee641f
|
||||
ms.sourcegitcommit: e98b752895109965b32cb277610985da5799f8a1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/01/2022
|
||||
ms.locfileid: '148127636'
|
||||
---
|
||||
## Organizationについて
|
||||
|
||||
{% data reusables.organizations.about-organizations %} アカウントの種類のについて詳しくは、「[{% data variables.product.prodname_dotcom %} アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」をご覧ください。
|
||||
## About organizations
|
||||
|
||||
Organization に参加するために招待するユーザーの数に制限はなく、Organization のメンバーには、Organization とそのデータへのさまざまなレベルのアクセス権を許可するさまざまなロールを許可することができます。 詳細については、「[Organization のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」を参照してください。
|
||||
{% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
|
||||
|
||||
また、Organization 自体へのアクセスを管理するだけでなく、Organization のリポジトリ、プロジェクト ボード、アプリへのアクセスを個別に管理できます。 詳しくは、「[Organization のリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」、「[Organization のプロジェクトボード権限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)」、「[Organization のアプリケーションに対するアクセスを管理する](/organizations/managing-access-to-your-organizations-apps)」をご覧ください。
|
||||
You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
|
||||
アクセス管理を簡素化し、コラボレーションを向上するために、連鎖アクセス許可とメンションを使って、グループの構造を反映する入れ子になったチームを作成できます。 詳細については、「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
|
||||
In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)", and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)."
|
||||
|
||||
メンバーが作成できるリポジトリの種類を制限するなど、設定を管理して、グループ固有のニーズを満たすように Organization を構成できます。 詳しくは、「[Organization の設定を管理する](/organizations/managing-organization-settings)」をご覧ください。
|
||||
To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
|
||||
|
||||
Organization のセキュリティを強化するために、セキュリティ要件を適用し、Organization の監査ログを確認できます。 詳しくは、「[Organization を安全に保つ](/organizations/keeping-your-organization-secure)」をご覧ください。
|
||||
You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "[Managing organization settings](/organizations/managing-organization-settings)."
|
||||
|
||||
{% data reusables.organizations.org-ownership-recommendation %}詳しくは、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」をご覧ください。
|
||||
To harden your organization's security, you can enforce security requirements and review the organization's audit log. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
|
||||
|
||||
To learn how to use organizations most effectively, see "[Best practices for organizations](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 使用できる機能について
|
||||
## About feature availability
|
||||
|
||||
{% data reusables.organizations.organization-plans %} {% endif %}
|
||||
{% data reusables.organizations.organization-plans %}
|
||||
{% endif %}
|
||||
|
||||
## Organization と Enterprise アカウント
|
||||
## Organizations and enterprise accounts
|
||||
|
||||
{% ifversion fpt %}Enterprise アカウントは、所有者が複数の Organization のポリシーと支払いを集中管理できるようにする {% data variables.product.prodname_ghe_cloud %} の機能です。 詳細については、[{% data variables.product.prodname_ghe_cloud %} ドキュメント](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)を参照してください。
|
||||
{% else %}{% ifversion ghec %}Enterprise アカウントに属する Organization では、支払いは Enterprise アカウントのレベルで管理され、支払い設定は Organization レベルでは利用できません。{% endif %}Enterprise 所有者は Enterprise アカウント内のすべての Organization のポリシーを設定するか、Organization 所有者に Organization レベルでのポリシーの設定を許可することができます。 Organization のオーナーは、Enterprise アカウントのレベルで Organization に強制された設定を変更することはできません。 Organization のポリシーや設定について質問がある場合は Enterprise アカウントのオーナーに問い合わせてください。
|
||||
{% ifversion fpt %}
|
||||
Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
|
||||
{% else %}
|
||||
{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
|
||||
|
||||
{% ifversion ghec %}{% data reusables.enterprise.create-an-enterprise-account %}詳しくは、「[Enterprise アカウントの作成](/admin/overview/creating-an-enterprise-account)」をご覧ください。
|
||||
{% ifversion ghec %}
|
||||
{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
|
||||
|
||||
{% data reusables.enterprise-accounts.invite-organization %}
|
||||
|
||||
{% endif %} {% endif %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Organization の利用規約とデータ保護
|
||||
## Terms of service and data protection for organizations
|
||||
|
||||
会社、非営利団体、グループなどは、Organization として標準の利用規約あるいは企業向け利用規約に合意できます。 詳しくは、「[企業利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」をご覧ください。
|
||||
An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -16,6 +16,7 @@ topics:
|
||||
children:
|
||||
- /about-organizations
|
||||
- /about-your-organization-dashboard
|
||||
- /best-practices-for-organizations
|
||||
- /creating-a-new-organization-from-scratch
|
||||
- /accessing-your-organizations-settings
|
||||
- /customizing-your-organizations-profile
|
||||
|
||||
@@ -1,134 +1,135 @@
|
||||
---
|
||||
title: About custom repository roles
|
||||
intro: You can more granularly control access to your organization's repositories with custom repository roles.
|
||||
title: カスタムリポジトリロールについて
|
||||
intro: カスタムのリポジトリロールを作成することで、Organization のリポジトリへのアクセスをよりきめ細かく制御できます。
|
||||
versions:
|
||||
feature: custom-repository-roles
|
||||
topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
shortTitle: About custom roles
|
||||
ms.openlocfilehash: c4e7f791b9402b45160b31aab2653bf80150ddee
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160689'
|
||||
---
|
||||
|
||||
{% data reusables.organizations.custom-repo-roles-ghec-only %}
|
||||
|
||||
## About custom repository roles
|
||||
## カスタムリポジトリロールについて
|
||||
|
||||
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.
|
||||
リポジトリでのPull Requestの作成やOrganizationの支払い設定の変更など、{% data variables.product.product_name %}でなんらかのアクションを行うためには、ユーザは関連するアカウントやリソースに対する十分なアクセス権を持っていなければなりません。 このアクセスは、権限によって制御されます。 権限は、特定のアクションを行える能力です。 たとえばIssueを削除する能力は権限です。 ロールは、個人やTeamに割り当てることができる権限のセットです。
|
||||
|
||||
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)."
|
||||
Organization内では、ロールをOrganization、Team、リポジトリのレベルで割り当てることができます。 さまざまなレベルのロールについて詳しくは、「[Organization 内のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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).
|
||||
最大 3 つのカスタム リポジトリ ロールを作成することで、リポジトリ レベルで付与するアクセス許可をより細かく制御できます。 {% data reusables.organizations.about-custom-repo-roles %} 詳しくは、「[Organization のカスタム リポジトリ ロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。
|
||||
|
||||
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)."
|
||||
カスタムロールを作成すると、リポジトリへの管理アクセスを持つユーザはそのロールを個人やTeamに割り当てることができます。 詳細については、「[組織のリポジトリに対する個人のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)」と「[組織のリポジトリに対するチームのアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)」を参照してください。
|
||||
|
||||
{% ifversion custom-repo-role-api %}
|
||||
|
||||
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)."
|
||||
REST API を使って、カスタム リポジトリ ロールを作成して管理することもできます。 詳細については、「[カスタム リポジトリ ロール](/rest/orgs/custom-roles)」を参照してください。
|
||||
|
||||
{% else %}
|
||||
|
||||
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)."
|
||||
REST API を使って、組織で使用できるカスタム リポジトリ ロールを一覧表示することもできます。 詳細については、[カスタム リポジトリ ロールの API](/rest/orgs/custom-roles) を参照してください。
|
||||
|
||||
{% endif %}
|
||||
|
||||
## About the inherited role
|
||||
## 継承されたロールについて
|
||||
|
||||
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)."
|
||||
カスタムリポジトリロールを作成する際は、事前設定された選択肢のセットから継承されたロールを選択することから始めます。 継承されたロールは、カスタムロールに含まれる権限の初期セットを決定します。 そして、そのロールは付与する追加権限を選択することによって、さらにカスタマイズできます。 使用可能なアクセス許可の完全なリストについては、「[カスタム ロールの追加のアクセス許可](#additional-permissions-for-custom-roles)」を参照してください。
|
||||
|
||||
Your options for the inherited role are standardized for different types of contributors in your repository.
|
||||
継承されたロールの選択肢については、リポジトリの様々な種類のコントリビューターに対して標準化されています。
|
||||
|
||||
| Inherited role | Designed for |
|
||||
| 継承されたロール | 対象 |
|
||||
|----|----|
|
||||
| **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 |
|
||||
| **読み取り** | プロジェクトの表示やディスカッションを行いたい、コードを書かないコントリビューターにお勧めします |
|
||||
| **トリアージ** | 書き込みアクセスなしで、積極的に Issue や Pull Request を管理する必要があるコントリビューター |
|
||||
| **書き込み** | 積極的にプロジェクトに対してプッシュを行う Organization のメンバーとコントリビューター。 |
|
||||
| **管理** | 機密の、あるいは破壊的なアクションへのアクセスなしにリポジトリを管理する必要があるプロジェクトマネージャー |
|
||||
|
||||
## Custom role examples
|
||||
## カスタム ロールの例
|
||||
|
||||
Here are some examples of custom repository roles you can configure.
|
||||
以下は、設定できるカスタムリポジトリロールの例です。
|
||||
|
||||
| Custom repository role | Summary | Inherited role | Additional permissions |
|
||||
| カスタムリポジトリロール | まとめ | 継承されたロール | 追加の権限 |
|
||||
|----|----|----|----|
|
||||
| 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 <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
|
||||
| セキュリティ エンジニア | コードをコントリビュートし、セキュリティパイプラインをメンテナンスできる | **管理** | Code scanningの結果の削除 |
|
||||
| Contractor | webhookのインテグレーションを開発できる | **書き込み** | webhookの管理 |
|
||||
| Community manager | コードをコントリビュートすることなく、コミュニティのすべてのやりとりを扱える | **読み取り** | - issue を複製としてマークする <br> - GitHub ページの設定を管理する <br> - Wiki 設定を管理する <br> - ソーシャル プレビューを設定する <br> - リポジトリのメタデータを編集する <br> - ディスカッションをトリアージする |
|
||||
|
||||
## Additional permissions for custom roles
|
||||
## カスタムロールの追加権限
|
||||
|
||||
After choosing an inherited role, you can select additional permissions for your custom role.
|
||||
継承されたロールを選択した後、カスタムロールの追加権限を選択できます。
|
||||
|
||||
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.
|
||||
継承されたロールにまだ含まれていない場合にのみ、追加の権限を選択できます。 たとえば、継承されたロールでリポジトリへの **書き込み** アクセスが提供されている場合は、"pull request をクローズする" 権限は継承されたロールに既に含まれています。
|
||||
|
||||
{% ifversion discussions %}
|
||||
### Discussions
|
||||
### ディスカッション
|
||||
|
||||
- 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
|
||||
- ディスカッション カテゴリを作成する
|
||||
- ディスカッション カテゴリを編集する
|
||||
- ディスカッション カテゴリを削除する
|
||||
- ディスカッションの回答をマークまたはマーク解除する
|
||||
- ディスカッション コメントを非表示または非表示解除する
|
||||
- issue をディスカッションに変換する
|
||||
|
||||
For more information, see "[{% data variables.product.prodname_discussions %}](/discussions)."
|
||||
詳しくは、「[{% data variables.product.prodname_discussions %}](/discussions)」を参照してください。
|
||||
{% endif %}
|
||||
|
||||
### Issue and Pull Requests
|
||||
### IssueとPull Request
|
||||
|
||||
- Assign or remove a user
|
||||
- Add or remove a label
|
||||
- ユーザーの割り当てまたは削除
|
||||
- ラベルの追加または削除
|
||||
|
||||
### Issue
|
||||
### 問題
|
||||
|
||||
- Close an issue
|
||||
- Reopen a closed issue
|
||||
- Delete an issue
|
||||
- Mark an issue as a duplicate
|
||||
- issue をクローズする
|
||||
- クローズされた issue を再オープンする
|
||||
- issue を削除する
|
||||
- issue を複製としてマークする
|
||||
|
||||
### Pull Request
|
||||
|
||||
- Close a pull request
|
||||
- Reopen a closed pull request
|
||||
- Request a pull request review
|
||||
- pull request をクローズする
|
||||
- クローズされた pull request を再オープンする
|
||||
- pull request レビューを要求する
|
||||
|
||||
### Repository
|
||||
### リポジトリ
|
||||
|
||||
- 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 %}
|
||||
- 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 %}
|
||||
- マイルストーンを設定する
|
||||
- wiki 設定を管理する
|
||||
- プロジェクト設定を管理する
|
||||
- pull request のマージ設定を管理する
|
||||
- {% data variables.product.prodname_pages %} 設定を管理する (「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)」を参照してください)
|
||||
- webhookの管理
|
||||
- デプロイキーの管理
|
||||
- リポジトリ メタデータの編集 {%- ifversion ghec %}
|
||||
- 相互作用の制限を設定する {%- endif %}
|
||||
- ソーシャル プレビューを設定する
|
||||
- 保護されたブランチにコミットをプッシュする (ブランチ保護規則は引き続き適用されます)
|
||||
- 保護されたタグを作成する
|
||||
- 保護されたタグを削除する {%- ifversion bypass-branch-protections %}
|
||||
- ブランチ保護をバイパスする {%- endif %}
|
||||
|
||||
### Security
|
||||
### セキュリティ
|
||||
|
||||
- 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
|
||||
- {% data variables.product.prodname_code_scanning %} の結果を表示する
|
||||
- {% data variables.product.prodname_code_scanning %} を閉じる、またはもう一度開く
|
||||
- {% data variables.product.prodname_code_scanning %} の結果を削除する
|
||||
- {% data variables.product.prodname_dependabot_alerts %}を表示する
|
||||
- {% data variables.product.prodname_dependabot_alerts %}を閉じる、またはもう一度開く
|
||||
- {% data variables.product.prodname_secret_scanning %} の結果を表示する
|
||||
- {% data variables.product.prodname_secret_scanning %} を閉じる、またはもう一度開く
|
||||
|
||||
## Precedence for different levels of access
|
||||
## 様々なアクセスレベルの優先順位
|
||||
|
||||
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.
|
||||
TeamのメンバーシップやOrganizationの基本権限など、様々な方法を通じて様々なレベルのアクセスを与えられている場合、最上位のアクセスが他よりも優先されます。 たとえば、OrganizationのオーナーがOrganizationのメンバーに継承ロールの"Read"を使うカスタムロールを与え、そしてOrganizationのオーナーがOrganizationの基本権限を"Write"にした場合、このカスタムロールはカスタムロールに含まれている追加の権限とともに、書き込みアクセスを持つことになります。
|
||||
|
||||
{% data reusables.organizations.mixed-roles-warning %}
|
||||
|
||||
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)"
|
||||
競合するアクセスを解決するには、Organizationの基本アクセスあるいはTeamのアクセスを調整するか、カスタムロールを編集してください。 詳細については、次を参照してください。
|
||||
- [Organization の基本レベルの権限の設定](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)
|
||||
- [Organization のリポジトリに対するチームのアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)
|
||||
- [リポジトリ ロールの編集](#editing-a-repository-role)
|
||||
|
||||
@@ -13,6 +13,7 @@ topics:
|
||||
- Repositories
|
||||
children:
|
||||
- /about-repositories
|
||||
- /best-practices-for-repositories
|
||||
- /creating-a-new-repository
|
||||
- /creating-a-repository-from-a-template
|
||||
- /creating-a-template-repository
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: READMEについて
|
||||
intro: リポジトリにREADMEファイルを追加して、そのプロジェクトがなぜ有益なのか、そのプロジェクトで何ができるか、そのプロジェクトをどのように使えるかを他者に伝えることができます。
|
||||
title: About READMEs
|
||||
intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
|
||||
redirect_from:
|
||||
- /articles/section-links-on-readmes-and-blob-pages
|
||||
- /articles/relative-links-in-readmes
|
||||
@@ -14,31 +14,25 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
ms.openlocfilehash: 7a18ed7051b0babdb5408821ce44a728968869d5
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109776'
|
||||
---
|
||||
## READMEについて
|
||||
## About READMEs
|
||||
|
||||
README ファイルをリポジトリに追加して、プロジェクトに関する重要な情報を伝えることができます。 README は、リポジトリ ライセンス、引用ファイル{% ifversion fpt or ghec %}、コントリビューション ガイドライン、倫理規定{% elsif ghes %}、コントリビューション ガイドライン{% endif %}と並んで、プロジェクトに期待されるものを伝え、コントリビューションを管理しやすくします。
|
||||
{% data reusables.repositories.about-READMEs %}
|
||||
|
||||
プロジェクトのガイドラインを提供する方法について詳しくは、{% ifversion fpt or ghec %}「[プロジェクトへの行動規範の追加](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」および{% endif %}「[健全なコントリビューションを促すプロジェクトをセットアップする](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。
|
||||
For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
|
||||
|
||||
多くの場合、READMEはリポジトリへの訪問者が最初に目にするアイテムです。 通常、README ファイルには以下の情報が含まれています:
|
||||
- このプロジェクトが行うこと
|
||||
- このプロジェクトが有益な理由
|
||||
- このプロジェクトの使い始め方
|
||||
- このプロジェクトに関するヘルプをどこで得るか
|
||||
- このプロジェクトのメンテナンス者とコントリビューター
|
||||
A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
|
||||
- What the project does
|
||||
- Why the project is useful
|
||||
- How users can get started with the project
|
||||
- Where users can get help with your project
|
||||
- Who maintains and contributes to the project
|
||||
|
||||
README ファイルをリポジトリの隠れ `.github` ルートまたは `docs` ディレクトリに置けば、{% data variables.product.product_name %} はそれを認識して自動的に README をリポジトリへの訪問者に提示します。
|
||||
If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
|
||||
|
||||
リポジトリに複数の README ファイルが含まれている場合、表示されるファイルは、`.github` ディレクトリ、リポジトリのルート ディレクトリ、最後に `docs` ディレクトリの順に選択されます。
|
||||
If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
@@ -46,28 +40,30 @@ README ファイルをリポジトリの隠れ `.github` ルートまたは `doc
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
## README ファイルの自動生成された目次
|
||||
## Auto-generated table of contents for README files
|
||||
|
||||
README ファイルなど、リポジトリの Markdown ファイルをレンダリングすると、{% data variables.product.product_name %} によって、セクション見出しに基づいて目次が自動的に生成されます。 レンダリングされたページの左上にある {% octicon "list-unordered" aria-label="The unordered list icon" %} メニューアイコンをクリックすると、README ファイルの目次を表示できます。
|
||||
For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %} menu icon at the top left of the rendered page.
|
||||
|
||||
|
||||
|
||||
|
||||
## READMEファイルのセクションリンクとblobページ
|
||||
## Section links in README files and blob pages
|
||||
|
||||
{% data reusables.repositories.section-links %}
|
||||
|
||||
## READMEファイル中の相対リンクと画像パス
|
||||
## Relative links and image paths in README files
|
||||
|
||||
{% data reusables.repositories.relative-links %}
|
||||
|
||||
## Wiki
|
||||
## Wikis
|
||||
|
||||
README には、開発者がプロジェクトを使用し、プロジェクトに貢献するために必要な情報のみを含めてください。 長いドキュメントは Wiki に最適です。 詳しくは、「[Wiki について](/communities/documenting-your-project-with-wikis/about-wikis)」を参照してください。
|
||||
A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- "[ファイルをリポジトリに追加する](/articles/adding-a-file-to-a-repository)"
|
||||
- 18F の「[README を読み取り可能にする](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)」{%- ifversion fpt or ghec %}
|
||||
- 「[[GitHub Codespaces で開く] バッジを追加する](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)」{%- endif %}
|
||||
- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
|
||||
- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
|
||||
{%- ifversion fpt or ghec %}
|
||||
- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
|
||||
{%- endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 依存関係の確認
|
||||
intro: 依存関係の確認 API を使用すると、依存関係の変更やこの変更がセキュリティに及ぼす影響を把握したうえで、この変更を環境に追加することができます。
|
||||
title: Dependency review
|
||||
intro: 'The Dependency review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.6'
|
||||
@@ -10,15 +10,8 @@ topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 64cb77b737927e8d44315fd40b51f68c77c50c54
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147064875'
|
||||
---
|
||||
## 依存関係の確認 API について
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-api-beta-note %}
|
||||
## About the Dependency review API
|
||||
|
||||
依存関係レビュー API を使用すると、依存関係の変更やこの変更がセキュリティに及ぼす影響を把握したうえで、この変更を環境に追加することができます。 既知の脆弱性を含むすべてのバージョン アップデートの脆弱性データを含め、リポジトリの 2 つのコミット間の依存関係の差分を確認することができます。 依存関係レビューの詳細については、「[依存関係のレビューについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)」を参照してください。
|
||||
The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
|
||||
@@ -11,25 +11,25 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4fa9e97ca9fa3803cfbd0cf0e21d3d2253a7aa60
|
||||
ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
|
||||
ms.openlocfilehash: aa139c0d25354260ccf688079f3e15a871b627bd
|
||||
ms.sourcegitcommit: 0ed77777360ec29eee7cd4fc212ae36fdd97c0bc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '146769158'
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: '148160963'
|
||||
---
|
||||
<div class="jumbotron libraries-jumbotron">
|
||||
<img src="/assets/images/gundamcat.png" class="gundamcat" alt="The Gundamcat" />
|
||||
<h1>Octokit にはいくつかの種類があります</h1>
|
||||
<p class="lead">公式の Octokit ライブラリを使用するか、利用可能なサードパーティライブラリのいずれかを選択します。</p>
|
||||
<div class="octokit-links"><br/>
|
||||
<div class="octokit-language"><span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
|
||||
<div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
|
||||
<div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
# サードパーティ製ライブラリ
|
||||
## Octokit にはいくつかの種類があります
|
||||
|
||||
公式の Octokit ライブラリを使用するか、利用可能なサードパーティライブラリのいずれかを選択します。
|
||||
|
||||
- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
|
||||
## サードパーティ製ライブラリ
|
||||
|
||||
### Clojure
|
||||
|
||||
@@ -130,6 +130,7 @@ ms.locfileid: '146769158'
|
||||
|**octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub)|
|
||||
|**github-flask**|[github-flask (公式 Web サイト)](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1,9 @@
|
||||
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.
|
||||
---
|
||||
ms.openlocfilehash: 982b04961e4f780a5f1e284dad5620157f68569b
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: "148161063"
|
||||
---
|
||||
サポートされているコンパイル言語の場合、{% data variables.code-scanning.codeql_workflow %}の `autobuild` アクションを使ってコードをビルドできます。 これにより、C/C++、C#、{% ifversion codeql-go-autobuild %}Go、{% endif %}および Java の明示的なビルド コマンドを指定する必要がなくなります。
|
||||
@@ -1,4 +1,12 @@
|
||||
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.
|
||||
---
|
||||
ms.openlocfilehash: e6d7a33506174bf50d70ae9b5d4ac9857cd880ae
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: "148161243"
|
||||
---
|
||||
1. {% data variables.product.prodname_codeql %}データベースを展開し、分析し、その結果を{% data variables.product.product_name %}にアップロードしてください。 結果は、リポジトリの **[セキュリティ]** タブに表示されます。
|
||||
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
|
||||
@@ -9,7 +17,7 @@
|
||||
> POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms
|
||||
> Successfully uploaded results
|
||||
```
|
||||
2. To upload {% data variables.product.prodname_code_scanning %} results as pull request checks, specify the pull request using the <nobr>`--ref`</nobr> 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.
|
||||
2. {% data variables.product.prodname_code_scanning %} の結果をプルリクエストのチェックとしてアップロードするには、<nobr>`--ref`</nobr> フラグを使用してプルリクエストを指定します。 [`pull_request`](/developers/webhooks-and-events/webhook-events-and-payloads#pull_request) Webhook イベントで実行されるように {% data variables.code-scanning.codeql_runner %}を設定することをお勧めします。
|
||||
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
|
||||
@@ -21,4 +29,4 @@
|
||||
> Successfully uploaded results
|
||||
```
|
||||
|
||||
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)."
|
||||
{% data variables.product.prodname_code_scanning %} アラートの表示の詳細については、「[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)」および「[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)」を参照してください。
|
||||
|
||||
@@ -1 +1,9 @@
|
||||
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.
|
||||
---
|
||||
ms.openlocfilehash: a697342c2435c479a3309cfb4619c15d4521098e
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: "148161228"
|
||||
---
|
||||
通常、{% data variables.product.prodname_code_scanning %} のデフォルトのワークフローを編集する必要はありません。 ただし、必要な場合にはワークフローを編集して設定の一部をカスタマイズできます。 たとえば、{% data variables.product.prodname_dotcom %} の {% data variables.code-scanning.codeql_workflow %}を編集すると、スキャンの頻度、スキャンする言語やディレクトリ、{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を使ったコード内での検索対象を指定できます。 コードのコンパイルに特定のコマンド セットを使う場合にも、{% data variables.code-scanning.codeql_workflow %}の編集が必要となる場合があります。
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: d1a631c8bcd74e56e3bd849292180f341f0ee75e
|
||||
ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: "147878607"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**注**: 依存関係のレビュー API は現在パブリック ベータ版であり、変更される可能性があります。
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 7527008260476000ac3460c800abd76b2fb202fe
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.openlocfilehash: b1c9d6341bb404267c34fa75e1a9c4c5eb401956
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: "145068879"
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160846"
|
||||
---
|
||||
{% ifversion ghec%} {% note %}
|
||||
|
||||
**注**: エンタープライズで {% data variables.product.prodname_emus %} を使用している場合、チーム同期は使用できず、代わりに SCIM を構成して ID プロバイダーのメンバーシップを管理する必要があります。 詳細については、「[Configuring SCIM provisioning for Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)」 (エンタープライズ マネージド ユーザー用の SCIM のプロビジョニングの構成) を参照してください。
|
||||
**メモ**: Enterprise で {% data variables.product.prodname_emus %} を使う場合は、Team 同期を使う必要はありません。 代わりに、Enterprise のセットアップ中に作成した SCIM 構成を使って、Team のメンバーシップを管理できます。 詳細については、「[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)」 (ID プロバイダー グループを使用して Team のメンバーシップを管理する) を参照してください。
|
||||
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
{% 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 %}<br><br>
|
||||
---
|
||||
ms.openlocfilehash: c408676063e80cca29eb7392181c00c4ecf7f76d
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160773"
|
||||
---
|
||||
{% data variables.product.company_short %} のお客様は、{% data variables.product.prodname_dotcom_the_website %} の個人アカウントで {% data variables.product.prodname_copilot %} を利用できます。 {% data reusables.copilot.emus-cannot-use-copilot %}<br><br>
|
||||
|
||||
{% 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)."
|
||||
確認が取れている学生、教師、およびパブリックのオープン ソース プロジェクトのメンテナンス担当者は、{% data variables.product.prodname_copilot %} を無料で使うことができます。 学生、教師、または一般的なオープンソース プロジェクトのメンテナンス担当者ではない場合にも、1 回限りの 60 日間の試用版で {% data variables.product.prodname_copilot %} を無料で試すことができます。 無料試用期間の後、継続して使うには有料サブスクリプションが必要になります。 詳しくは、「[{% data variables.product.prodname_copilot %} の課金について](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」をご覧ください。
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 3492d399c754d53fea2091a08c95b212455a8e18
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160770"
|
||||
---
|
||||
接続には、ポート 443 または 80 経由の HTTPS が使用され、TLS によって保護されます。
|
||||
@@ -1,12 +1,11 @@
|
||||
---
|
||||
ms.openlocfilehash: dc6bad5b656bb5d755196146b017213b66d1730e
|
||||
ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
|
||||
ms.openlocfilehash: adefefb787099214cf17f7b2276a8f44f3fe8e56
|
||||
ms.sourcegitcommit: f54d01e643f994ce48f0774dbc680ad77dd6193f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "147884721"
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160573"
|
||||
---
|
||||
1. Git で SSH 署名キーを設定するには、以下のテキストを貼り付けて、使いたいキーにクリップボードの内容を置き換えます。 キーにはスペースが含まれるため、引用符で囲む必要があります。
|
||||
1. Git に SSH 署名キーを設定するには、次のテキストを貼り付けて、 **/PATH/TO/KEY.PUB** の部分を、使いたい公開キーへのパスに置き換えます。
|
||||
```bash
|
||||
$ git config --global user.signingkey 'ssh-ed25519 AAAAC3(...) user@example.com'
|
||||
```
|
||||
$ git config --global user.signingkey=/PATH/TO/.SSH/KEY.PUB
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 85c7f83e66e8519c6d62346fe69b6e3f0b413ff1
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 478008cfe79ec4fe3c32c154af38692879f5c807
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147419893"
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160767"
|
||||
---
|
||||
{% warning %}
|
||||
|
||||
**警告:** pull request、issue のコメント、または {% data variables.contact.support_portal %} のチケットにファイルを添付した場合、その pull request がプライベート リポジトリにあっても、{% ifversion ghes %}またはプライベート モードが有効になっていても、{% endif %}匿名化された URL を誰でも認証なしに見ることができます。 機密性の高いメディア ファイルを非公開にしておきたい場合は、認証を必要とするプライベート ネットワークやサーバーから配信してください。 {% ifversion fpt or ghec %}匿名化された URL の詳細については、「[匿名化された URL について](/github/authenticating-to-github/about-anonymized-urls)」を参照してください。{% endif %}
|
||||
**警告:** イメージまたは動画を pull request または issue コメントにアップロードしたり、ファイルを {% data variables.contact.support_portal %}内のチケットにアップロードしたりする場合、その pull request または issue がプライベート リポジトリ内にある場合{% ifversion ghes %}、またはプライベート モードが有効になっている場合であっても、匿名化された URL が許可なくすべてのユーザーに表示されます。{% endif %}. 機密性の高いメディア ファイルを非公開にしておきたい場合は、認証を必要とするプライベート ネットワークやサーバーから配信してください。 {% ifversion fpt or ghec %}匿名化された URL の詳細については、「[匿名化された URL について](/github/authenticating-to-github/about-anonymized-urls)」を参照してください。{% endif %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -1,12 +1,20 @@
|
||||
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).
|
||||
---
|
||||
ms.openlocfilehash: d077bcd717f353297cf908b1261c821a4e759b78
|
||||
ms.sourcegitcommit: f0ae3d979782cb532427c0df026d25bfd0d0db80
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160461"
|
||||
---
|
||||
アドバイザリは、以下のソースから {% data variables.product.prodname_advisory_database %} に追加されます。
|
||||
- {% data variables.product.prodname_dotcom %}で報告されたセキュリティアドバイザリ
|
||||
- [National Vulnerability Database](https://nvd.nist.gov/)
|
||||
- [npm セキュリティ アドバイザリ データベース](https://github.com/advisories?query=type%3Areviewed+ecosystem%3Anpm)
|
||||
- [FriendsOfPHP データベース](https://github.com/FriendsOfPHP/security-advisories)
|
||||
- [Go Vulncheck データベース](https://pkg.go.dev/golang.org/x/vuln/vulncheck)
|
||||
- [GitHub Packaging Advisory データベース](https://github.com/pypa/advisory-database)
|
||||
- [Ruby Advisory データベース](https://rubysec.com/)
|
||||
- [RustSec Advisory データベース](https://rustsec.org/)
|
||||
- コミュニティのコード提供。 詳細については、「[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).
|
||||
アドバイザリのインポート元として他のデータベースに心当たりがある場合は、[https://github.com/github/advisory-database](https://github.com/github/advisory-database) で issue をオープンしてお知らせください。
|
||||
|
||||
@@ -384,6 +384,7 @@ translations/es-ES/data/reusables/codespaces/review-pr.md,file deleted because i
|
||||
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/dependency-review/dependency-review-api-beta-note.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
|
||||
@@ -527,7 +528,7 @@ translations/es-ES/content/actions/using-workflows/sharing-workflows-secrets-and
|
||||
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-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-code-scanning-for-your-appliance.md,rendering error
|
||||
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/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
|
||||
@@ -545,7 +546,6 @@ translations/es-ES/content/admin/configuration/configuring-network-settings/conf
|
||||
translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
|
||||
translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
|
||||
@@ -589,6 +589,7 @@ translations/es-ES/content/admin/github-actions/getting-started-with-github-acti
|
||||
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/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
|
||||
@@ -602,9 +603,7 @@ translations/es-ES/content/admin/identity-and-access-management/using-enterprise
|
||||
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
|
||||
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,broken liquid tags
|
||||
translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
|
||||
translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md,broken liquid tags
|
||||
translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,rendering error
|
||||
translations/es-ES/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
|
||||
translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags
|
||||
@@ -757,6 +756,7 @@ 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/configuring-private-vulnerability-reporting-for-a-repository.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
|
||||
@@ -764,6 +764,7 @@ translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply
|
||||
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-the-dependency-graph.md,rendering error
|
||||
translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,broken liquid tags
|
||||
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/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
|
||||
@@ -801,7 +802,6 @@ translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypte
|
||||
translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags
|
||||
translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags
|
||||
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
|
||||
@@ -813,7 +813,6 @@ translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/set
|
||||
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
|
||||
translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,broken liquid tags
|
||||
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/index.md,broken liquid tags
|
||||
@@ -831,7 +830,6 @@ 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
|
||||
@@ -893,7 +891,8 @@ translations/es-ES/content/get-started/quickstart/contributing-to-projects.md,re
|
||||
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,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/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
|
||||
translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
|
||||
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
|
||||
@@ -924,6 +923,7 @@ translations/es-ES/content/issues/organizing-your-work-with-project-boards/manag
|
||||
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-organizations.md,broken liquid tags
|
||||
translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
|
||||
translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
|
||||
translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
|
||||
@@ -939,7 +939,6 @@ 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
|
||||
@@ -1002,6 +1001,7 @@ translations/es-ES/content/repositories/creating-and-managing-repositories/creat
|
||||
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-readmes.md,broken liquid tags
|
||||
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
|
||||
@@ -1020,6 +1020,7 @@ 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
|
||||
translations/es-ES/content/rest/dependabot/index.md,broken liquid tags
|
||||
translations/es-ES/content/rest/dependency-graph/dependency-review.md,broken liquid tags
|
||||
translations/es-ES/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
|
||||
translations/es-ES/content/rest/enterprise-admin/announcement.md,broken liquid tags
|
||||
translations/es-ES/content/rest/enterprise-admin/billing.md,broken liquid tags
|
||||
@@ -1127,11 +1128,9 @@ 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,rendering error
|
||||
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
|
||||
@@ -1191,7 +1190,6 @@ 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
|
||||
@@ -1247,7 +1245,6 @@ 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
|
||||
|
||||
|
@@ -390,6 +390,7 @@ translations/ja-JP/data/reusables/codespaces/review-pr.md,file deleted because i
|
||||
translations/ja-JP/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/dependency-review/dependency-review-api-beta-note.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md,file deleted because it no longer exists in main
|
||||
@@ -525,7 +526,7 @@ translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and
|
||||
translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,rendering error
|
||||
translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md,rendering error
|
||||
translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
|
||||
@@ -535,14 +536,12 @@ translations/ja-JP/content/admin/configuration/configuring-github-connect/enabli
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/managing-github-connect.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
|
||||
@@ -586,6 +585,7 @@ translations/ja-JP/content/admin/github-actions/getting-started-with-github-acti
|
||||
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/index.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
|
||||
@@ -595,13 +595,10 @@ translations/ja-JP/content/admin/identity-and-access-management/using-built-in-a
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags
|
||||
translations/ja-JP/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/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,rendering error
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags
|
||||
@@ -709,7 +706,6 @@ translations/ja-JP/content/code-security/adopting-github-advanced-security-at-sc
|
||||
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
|
||||
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
|
||||
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
|
||||
translations/ja-JP/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/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
|
||||
translations/ja-JP/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/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
|
||||
@@ -719,7 +715,6 @@ translations/ja-JP/content/code-security/code-scanning/automatically-scanning-yo
|
||||
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
|
||||
translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
|
||||
translations/ja-JP/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/ja-JP/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/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
|
||||
@@ -753,6 +748,7 @@ translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-se
|
||||
translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error
|
||||
translations/ja-JP/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
|
||||
translations/ja-JP/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
|
||||
translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
|
||||
translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md,rendering error
|
||||
translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
|
||||
translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
|
||||
@@ -760,6 +756,7 @@ translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply
|
||||
translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md,rendering error
|
||||
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,rendering error
|
||||
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
|
||||
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
@@ -809,7 +806,6 @@ translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/set
|
||||
translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/troubleshooting/index.md,broken liquid tags
|
||||
@@ -826,7 +822,6 @@ translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-s
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/overview-of-github-copilot/about-github-copilot.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/quickstart.md,broken liquid tags
|
||||
translations/ja-JP/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/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
|
||||
@@ -886,7 +881,8 @@ translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md,re
|
||||
translations/ja-JP/content/get-started/quickstart/create-a-repo.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/quickstart/fork-a-repo.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/quickstart/github-glossary.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/about-git-rebase.md,broken liquid tags
|
||||
@@ -899,7 +895,6 @@ translations/ja-JP/content/get-started/using-github/troubleshooting-connectivity
|
||||
translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
|
||||
translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md,rendering error
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error
|
||||
translations/ja-JP/content/github-cli/github-cli/quickstart.md,rendering error
|
||||
@@ -919,6 +914,7 @@ translations/ja-JP/content/issues/organizing-your-work-with-project-boards/manag
|
||||
translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md,broken liquid tags
|
||||
translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,broken liquid tags
|
||||
translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
|
||||
translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
|
||||
translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
|
||||
@@ -934,7 +930,6 @@ translations/ja-JP/content/organizations/managing-organization-settings/managing
|
||||
translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
|
||||
translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
|
||||
translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md,broken liquid tags
|
||||
translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md,rendering error
|
||||
translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
|
||||
translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
|
||||
@@ -1000,6 +995,7 @@ translations/ja-JP/content/repositories/creating-and-managing-repositories/creat
|
||||
translations/ja-JP/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
|
||||
translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
|
||||
translations/ja-JP/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
|
||||
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,broken liquid tags
|
||||
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
|
||||
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
|
||||
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
|
||||
@@ -1018,6 +1014,7 @@ translations/ja-JP/content/rest/activity/notifications.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/apps/oauth-applications.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/codespaces/codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/dependabot/index.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/dependency-graph/dependency-review.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/enterprise-admin/announcement.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/enterprise-admin/billing.md,broken liquid tags
|
||||
@@ -1126,13 +1123,10 @@ translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
|
||||
translations/ja-JP/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/classroom/about-autograding.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
|
||||
translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
|
||||
translations/ja-JP/data/reusables/code-scanning/codeql-runner-analyze-example.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
|
||||
translations/ja-JP/data/reusables/code-scanning/edit-workflow.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
|
||||
@@ -1192,7 +1186,6 @@ translations/ja-JP/data/reusables/enterprise_user_management/consider-usernames-
|
||||
translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/files/choose-commit-email.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/gated-features/copilot.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
|
||||
translations/ja-JP/data/reusables/gated-features/secret-scanning-partner.md,rendering error
|
||||
translations/ja-JP/data/reusables/gated-features/secret-scanning.md,rendering error
|
||||
@@ -1249,7 +1242,6 @@ translations/ja-JP/data/reusables/repositories/navigate-to-repo.md,broken liquid
|
||||
translations/ja-JP/data/reusables/repositories/repository-branches.md,rendering error
|
||||
translations/ja-JP/data/reusables/repositories/sidebar-notifications.md,rendering error
|
||||
translations/ja-JP/data/reusables/repositories/suggest-changes.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/repositories/tracks-vulnerabilities.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/repositories/you-can-fork.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error
|
||||
translations/ja-JP/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
|
||||
|
||||
|
Reference in New Issue
Block a user