Octomerger Bot
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configuration d’OpenID Connect dans Amazon Web Services
|
||||
shortTitle: Configuring OpenID Connect in Amazon Web Services
|
||||
shortTitle: OpenID Connect in AWS
|
||||
intro: Utilisez OpenID Connect dans vos workflows pour vous authentifier auprès d’Amazon Web Services.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -10,12 +10,12 @@ versions:
|
||||
type: tutorial
|
||||
topics:
|
||||
- Security
|
||||
ms.openlocfilehash: 6b57dc216c3f2ebc1edb73a8d588edb1967aebcb
|
||||
ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
|
||||
ms.openlocfilehash: 597ea408c2f0172eb0eacf07fc2d1ad320872f09
|
||||
ms.sourcegitcommit: 94ba3891ebcc3c05812f468e4adafdd15b99e390
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147876811'
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: '148182256'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -53,7 +53,7 @@ Modifiez la relation de stratégie pour ajouter le champ `sub` aux conditions de
|
||||
}
|
||||
```
|
||||
|
||||
Dans l’exemple suivant, `ForAllValues` est utilisé pour correspondre à plusieurs clés de condition et `StringLike` est utilisé pour correspondre à n’importe quelle référence dans le dépôt spécifié. Notez que `ForAllValues` est [trop permissif](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_multi-value-conditions.html) et ne doit pas être utilisé par lui-même dans un effet `Allow`. Pour cet exemple, l’inclusion de `StringLike` signifie qu’un ensemble vide dans `ForAllValues` ne passe toujours pas la condition :
|
||||
Dans l’exemple suivant, `StringLike` est utilisé avec un opérateur générique (`*`) pour autoriser toute branche, toute branche de fusion de demande de tirage ou tout environnement de l’organisation `octo-org/octo-repo` et du dépôt à assumer un rôle dans AWS.
|
||||
|
||||
```json{:copy}
|
||||
{
|
||||
@@ -69,8 +69,7 @@ Dans l’exemple suivant, `ForAllValues` est utilisé pour correspondre à plusi
|
||||
"StringLike": {
|
||||
"token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:*"
|
||||
},
|
||||
"ForAllValues:StringEquals": {
|
||||
"token.actions.githubusercontent.com:iss": "https://token.actions.githubusercontent.com",
|
||||
"StringEquals": {
|
||||
"token.actions.githubusercontent.com:aud": "sts.amazonaws.com"
|
||||
}
|
||||
}
|
||||
|
||||
@@ -17,12 +17,12 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: cd0c5b4bafc5226a99a75d3632fc5072233f5c1c
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.openlocfilehash: d9a4518f2fcc23d4b49967effb7b9a3022a7c6bd
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180104'
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148184011'
|
||||
---
|
||||
## À propos des restrictions du trafic réseau
|
||||
|
||||
@@ -30,7 +30,7 @@ Par défaut, les utilisateurs autorisés peuvent accéder à votre entreprise à
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
Si votre entreprise utilise des {% data variables.product.prodname_emus %} avec OIDC, vous pouvez choisir d’utiliser la fonctionnalité de liste d’adresses IP autorisées de {% data variables.product.company_short %} ou d’utiliser les restrictions de la liste d’autorisations de votre fournisseur d’identité (IdP). Si votre entreprise n’utilise pas de {% data variables.product.prodname_emus %} avec OIDC, vous pouvez utiliser la fonctionnalité de liste d’autorisations de {% data variables.product.company_short %}.
|
||||
Si votre entreprise utilise des {% data variables.product.prodname_emus %} avec OIDC, vous pouvez choisir d’utiliser la fonctionnalité de liste d’adresses IP autorisées de {% data variables.product.company_short %} ou d’utiliser les restrictions de la liste d’autorisations de votre fournisseur d’identité (IdP). Si votre entreprise n’utilise pas de {% data variables.product.prodname_emus %} avec OIDC, vous pouvez utiliser la fonctionnalité de liste d’autorisations de {% data variables.product.company_short %}.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
@@ -50,8 +50,6 @@ Vous pouvez utiliser la liste d’adresses IP autorisées de {% data variables.p
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
|
||||
|
||||
Vous pouvez aussi configurer des adresses IP autorisées pour une organisation individuelle. Pour plus d’informations, consultez « [Gestion des adresses IP autorisées pour votre organisation](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization) ».
|
||||
|
||||
## À propos de la liste d’autorisations de votre IdP
|
||||
|
||||
Si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC, vous pouvez utiliser la liste d’autorisations de votre IdP.
|
||||
|
||||
@@ -41,7 +41,7 @@ For more information, see "[About identity and access management with SAML singl
|
||||
|
||||
{% data reusables.saml.saml-disabled-linked-identities-removed %}
|
||||
|
||||
{% data reusables.scim.enterprise-account-scim %}
|
||||
{% data reusables.apps.reauthorize-apps-saml %}
|
||||
|
||||
{% elsif ghes or ghae %}
|
||||
|
||||
@@ -73,14 +73,9 @@ After a user successfully authenticates on your IdP, the user's SAML session for
|
||||
|
||||
## Enforcing SAML single-sign on for organizations in your enterprise account
|
||||
|
||||
{% note %}
|
||||
When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
|
||||
|
||||
**Notes:**
|
||||
|
||||
- When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
|
||||
- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
|
||||
|
||||
{% endnote %}
|
||||
When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
|
||||
|
||||
For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)."
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ topics:
|
||||
The scope of the events that appear in your enterprise's audit log depend on whether your enterprise uses {% data variables.product.prodname_emus %}. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
|
||||
|
||||
- If your enterprise does not use {% data variables.product.prodname_emus %}, the audit log only includes events related to the enterprise account and the organizations within the enterprise account, which are listed in this article.
|
||||
- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.enterprise.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)."
|
||||
- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.enterprise.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %} and actions they take within their user account. For a list of these user account events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)."
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
@@ -105,10 +105,12 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `business.clear_members_can_create_repos` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared a restriction on repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."
|
||||
| `business.create` | An enterprise was created.
|
||||
{%- ifversion ghec %}
|
||||
| `business.disable_oidc` | OIDC single sign-on was disabled for an enterprise. For more information, see "[Configuring OIDC for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
| `business.disable_saml` | SAML single sign-on was disabled for an enterprise.
|
||||
{%- endif %}
|
||||
| `business.disable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was disabled.
|
||||
{%- ifversion ghec %}
|
||||
| `business.enable_oidc` | OIDC single sign-on was enabled for an enterprise. For more information, see "[Configuring OIDC for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
| `business.enable_saml` | SAML single sign-on was enabled for an enterprise.
|
||||
{%- endif %}
|
||||
| `business.enable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was enabled.
|
||||
@@ -1336,6 +1338,19 @@ Before you'll see `git` category actions, you must enable Git events in the audi
|
||||
| `ssh_certificate_requirement.disable` | The requirement for members to use SSH certificates to access an organization resources was disabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion sso-redirect %}
|
||||
## `sso_redirect` category actions
|
||||
|
||||
{% data reusables.enterprise-managed.sso-redirect-release-phase %}
|
||||
|
||||
| Action | Description |
|
||||
|--------|------------ |
|
||||
`sso_redirect.enable` | Automatic redirects for users to single sign-on (SSO) was enabled. |
|
||||
`sso_redirect.disable` | Automatic redirects for users to single sign-on (SSO) was disabled. |
|
||||
|
||||
For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
|
||||
{% endif %}
|
||||
|
||||
## `staff` category actions
|
||||
|
||||
| Action | Description
|
||||
|
||||
@@ -111,6 +111,7 @@ Each category has a set of associated actions that you can filter on. For exampl
|
||||
Actions that can be found in your enterprise audit log are grouped within the following categories:
|
||||
|
||||
{% data reusables.audit_log.audit-log-action-categories %}
|
||||
|
||||
### Search based on time of action
|
||||
|
||||
Use the `created` qualifier to filter events in the audit log based on when they occurred.
|
||||
|
||||
@@ -117,6 +117,10 @@ For more information about the audit log REST API, see "[Enterprise administrati
|
||||
|
||||
### Example 1: All events in an enterprise, for a specific date, with pagination
|
||||
|
||||
You can use page-based pagination or cursor based pagination. For more information, see "[Traversing with Pagination](/rest/guides/traversing-with-pagination)."
|
||||
|
||||
#### Example with page-based pagination
|
||||
|
||||
The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination):
|
||||
|
||||
```shell
|
||||
@@ -125,6 +129,32 @@ curl -H "Authorization: Bearer TOKEN" \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
|
||||
```
|
||||
|
||||
#### Example with cursor-based pagination
|
||||
|
||||
The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and returns the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination). The `--include` flag causes the headers to be returned along with the response.
|
||||
|
||||
```
|
||||
curl --include -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&per_page=100"
|
||||
```
|
||||
|
||||
If there are more than 100 results, the `link` header will include URLs to fetch the next, first, and previous pages of results.
|
||||
|
||||
```
|
||||
link: <https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=MS42NjQzODMzNTk5MjdlKzEyfDloQzBxdURzaFdVbVlLWjkxRU9mNXc%3D&before=>; rel="next",
|
||||
<https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=>; rel="first",
|
||||
<https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=MS42Njc4NDA2MjM4MzNlKzEyfExqeG5sUElvNEZMbG1XZHA5akdKTVE%3D>; rel="prev"
|
||||
```
|
||||
|
||||
Copy the corresponding pagination link into your next request. For example:
|
||||
|
||||
```shell
|
||||
curl -I -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=MS42Njc4NDA2MjM5NDFlKzEyfHRYa3AwSkxUd2xyRjA5bWxfOS1RbFE%3D&before="
|
||||
```
|
||||
|
||||
### Example 2: Events for pull requests in an enterprise, for a specific date and actor
|
||||
|
||||
You can specify multiple search phrases, such as `created` and `actor`, by separating them in your formed URL with the `+` symbol or ASCII character code `%20`.
|
||||
@@ -136,3 +166,9 @@ curl -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -84,10 +84,11 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.organizations.delete-ssh-ca %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% ifversion sso-redirect %}
|
||||
## Managing SSO for unauthenticated users
|
||||
|
||||
{% data reusables.enterprise-managed.sso-redirect-release-phase %}
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %}, you can choose what unauthenticated users see when they attempt to access your enterprise's resources. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
|
||||
|
||||
By default, to hide the existence of private resources, when an unauthenticated user attempts to access your enterprise, {% data variables.product.company_short %} displays a 404 error.
|
||||
@@ -106,11 +107,14 @@ To prevent confusion from your developers, you can change this behavior so that
|
||||
1. Under "Single sign-on settings", select or deselect **Automatically redirect users to sign in**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
|
||||
- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{%- endif %}
|
||||
- "[Keeping your organization secure](/organizations/keeping-your-organization-secure)"
|
||||
- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
|
||||
{%- ifversion ghec %}
|
||||
- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghae %}
|
||||
- "[Restricting network traffic with an IP allow list with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)"
|
||||
{%- endif %}
|
||||
|
||||
@@ -84,11 +84,11 @@ When you authorize an {% data variables.product.prodname_oauth_app %} for your p
|
||||
|
||||
- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources.
|
||||
|
||||
If you belong to any organizations that enforce SAML single sign-on, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}.
|
||||
If you belong to any organizations with SAML single sign-on (SSO) enabled, and you have created a linked identity for that organization by authenticating via SAML in the past, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you are encountering errors authenticating to an organization that enforces SAML single sign-on, you may need to revoke the OAuth App from your [account settings page](https://github.com/settings/applications) and repeat the authentication flow to reauthorize the app.
|
||||
**Note:** If you're encountering issues with an authorized {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} accessing an organization that is protected by SAML, you may need to revoke the app from your [Authorized {% data variables.product.prodname_github_apps %}](https://github.com/settings/applications) or [Authorized {% data variables.product.prodname_oauth_apps %}](https://github.com/settings/apps/authorizations) page, visit the organization to authenticate and establish an active SAML session, and then attempt to reauthorize the app by accessing it.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring the CodeQL workflow for compiled languages
|
||||
title: Configuration du workflow CodeQL pour les langages compilés
|
||||
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: 'Vous pouvez configurer la façon dont {% data variables.product.prodname_dotcom %} utilise le {% data variables.code-scanning.codeql_workflow %} pour analyser le code écrit dans des langages compilés pour détecter les vulnérabilités et les erreurs.'
|
||||
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.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
@@ -27,107 +27,106 @@ topics:
|
||||
- C#
|
||||
- Java
|
||||
- Kotlin
|
||||
ms.openlocfilehash: 4c594a9ca19064da6c017155fad27b37b083e7e3
|
||||
ms.sourcegitcommit: dac72908e8660cb4a347fbf73beab61034eed8c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: '148182265'
|
||||
---
|
||||
{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
|
||||
## À propos du {% data variables.code-scanning.codeql_workflow %} et des langages compilés
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
Vous configurez {% data variables.product.prodname_dotcom %} afin d’exécuter l’{% data variables.product.prodname_code_scanning %} pour votre dépôt en ajoutant un workflow {% data variables.product.prodname_actions %} à ce dernier. Pour l’{% data variables.product.prodname_code_scanning %} {% data variables.product.prodname_codeql %}, vous ajoutez le {% data variables.code-scanning.codeql_workflow %}. Pour plus d’informations, consultez « [Configuration de l’{% data variables.product.prodname_code_scanning %} pour un dépôt](/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 %} Pour obtenir des informations générales sur la configuration de l’{% data variables.product.prodname_code_scanning %} et la modification des fichiers de workflow, consultez « [Configuration de l’{% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning) » et « [Découvrir {% 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)."
|
||||
## À propos de la génération automatique pour {% data variables.product.prodname_codeql %}
|
||||
|
||||
{% 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 %}{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
|
||||
L’{% data variables.product.prodname_code_scanning_capc %} fonctionne en exécutant des requêtes sur une ou plusieurs bases de données. Chaque base de données contient une représentation de tout le code dans un langage unique au sein de votre dépôt.
|
||||
Pour les langages compilés C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %}{% ifversion codeql-kotlin-beta %} Kotlin {% endif %} et Java, le processus de remplissage de cette base de données implique la génération du code et l’extraction des données. {% 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.
|
||||
Si votre workflow utilise une matrice `language`, `autobuild` tente de générer chacun des langages compilés listés dans la matrice. Sans matrice, `autobuild` tente de générer le langage compilé pris en charge qui a le plus grand nombre de fichiers sources dans le dépôt. À l’exception de Go, l’analyse d’autres langages compilés dans votre dépôt échoue, sauf si vous fournissez des commandes de build explicites.
|
||||
|
||||
{% 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 %} **Remarque** : {% data reusables.actions.self-hosted-runners-software %} {% else %} **Remarque** : Si vous utilisez des exécuteurs auto-hébergés pour {% data variables.product.prodname_actions %}, vous devrez peut-être installer des logiciels supplémentaires pour utiliser le processus `autobuild`. En outre, si votre dépôt nécessite une version spécifique d’un outil de génération, vous devrez peut-être l’installer manuellement. Pour plus d’informations, consultez « [Spécifications pour les exécuteurs hébergés par {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software) ».
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### C/C++
|
||||
|
||||
| Supported system type | System name |
|
||||
| Type de système pris en charge | Nom système |
|
||||
|----|----|
|
||||
| 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 |
|
||||
| Système d’exploitation | Windows, macOS et Linux |
|
||||
| Système de build | Windows : scripts MSbuild et de build<br/>Linux et macOS : Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild et scripts de 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:
|
||||
Le comportement de l’étape `autobuild` varie en fonction du système d’exploitation sur lequel l’extraction s’exécute. Sur Windows, l’étape `autobuild` tente de détecter automatiquement une méthode de génération appropriée pour C/C++ en utilisant l’approche suivante :
|
||||
|
||||
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. Appeler `MSBuild.exe` sur le fichier solution (`.sln`) ou projet (`.vcxproj`) le plus proche de la racine.
|
||||
Si `autobuild` détecte plusieurs fichiers solution ou projet à la même profondeur (la plus courte) à partir du répertoire de niveau supérieur, il tente de les générer tous.
|
||||
2. Appeler un script qui ressemble à un script de build : _build.bat_, _build.cmd_ et _build.exe_ (dans cet ordre).
|
||||
|
||||
On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
|
||||
Sur Linux et macOS, l’étape `autobuild` passe en revue les fichiers présents dans le dépôt pour déterminer le système de build utilisé :
|
||||
|
||||
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. Rechercher un système de build dans le répertoire racine.
|
||||
2. Si aucun répertoire n’est trouvé, rechercher un répertoire unique avec un système de build pour C/C++.
|
||||
3. Exécuter une commande appropriée pour configurer le système.
|
||||
|
||||
### C#
|
||||
|
||||
| Supported system type | System name |
|
||||
| Type de système pris en charge | Nom système |
|
||||
|----|----|
|
||||
| Operating system | Windows and Linux |
|
||||
| Build system | .NET and MSbuild, as well as build scripts |
|
||||
| Système d’exploitation | Windows et Linux |
|
||||
| Système de build | .NET et MSbuild ainsi que les scripts de build |
|
||||
|
||||
The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
|
||||
Le processus `autobuild` tente de détecter automatiquement une méthode de génération appropriée pour C# en utilisant l’approche suivante :
|
||||
|
||||
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. Appeler `dotnet build` sur le fichier solution (`.sln`) ou projet (`.csproj`) le plus proche de la racine.
|
||||
2. Appeler `MSbuild` (Linux) ou `MSBuild.exe` (Windows) sur le fichier solution ou projet le plus proche de la racine.
|
||||
Si `autobuild` détecte plusieurs fichiers solution ou projet à la même profondeur (la plus courte) à partir du répertoire de niveau supérieur, il tente de les générer tous.
|
||||
3. Appeler un script qui ressemble à un script de build : _build_ et _build.sh_ (dans cet ordre, pour Linux) ou _build.bat_, _build.cmd_ et _build.exe_ (dans cet ordre, pour Windows).
|
||||
|
||||
{% ifversion codeql-go-autobuild %}
|
||||
|
||||
### Go
|
||||
|
||||
| Supported system type | System name |
|
||||
| Type de système pris en charge | Nom système |
|
||||
|----|----|
|
||||
| Operating system | Windows, macOS, and Linux |
|
||||
| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
|
||||
| Système d’exploitation | Windows, macOS et Linux |
|
||||
| Système de build | Modules Go, `dep` et Glide, ainsi que des scripts de génération, notamment des scripts Makefiles et Ninja |
|
||||
|
||||
The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
|
||||
Le processus `autobuild` tente de détecter automatiquement un moyen approprié d’installer les dépendances dont un dépôt Go a besoin avant d’extraire tous les fichiers `.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. Appelez `make`, `ninja`, `./build` ou `./build.sh` (dans cet ordre) jusqu’à ce que l’une de ces commandes réussisse et qu’une commande `go list ./...` ultérieure réussisse également, indiquant que les dépendances nécessaires ont été installées.
|
||||
2. Si aucune de ces commandes ne réussit, recherchez `go.mod`, `Gopkg.toml` ou `glide.yaml`, et exécutez `go get` (sauf si le vendoring est utilisé), `dep ensure -v` ou `glide install` respectivement pour essayer d’installer les dépendances.
|
||||
3. Enfin, si les fichiers de configuration de ces gestionnaires de dépendances sont introuvables, réorganisez la structure de répertoires du dépôt pour l’ajouter à `GOPATH` et utilisez `go get` pour installer les dépendances. La structure de répertoires revient à la normale une fois l’extraction terminée.
|
||||
4. Extrayez tout le code Go dans le dépôt, comme pour l’exécution de `go build ./...`.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Java {% ifversion codeql-kotlin-beta %} and Kotlin {% endif %}
|
||||
### Java {% ifversion codeql-kotlin-beta %} et Kotlin {% endif %}
|
||||
|
||||
| Supported system type | System name |
|
||||
| Type de système pris en charge | Nom système |
|
||||
|----|----|
|
||||
| Operating system | Windows, macOS, and Linux (no restriction) |
|
||||
| Build system | Gradle, Maven and Ant |
|
||||
| Système d’exploitation | Windows, macOS et Linux (sans restriction) |
|
||||
| Système de build | Gradle, Maven et Ant |
|
||||
|
||||
The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
|
||||
Le processus `autobuild` tente de déterminer le système de build pour les codebases Java en appliquant cette stratégie :
|
||||
|
||||
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. Rechercher un fichier de build dans le répertoire racine. Rechercher les fichiers de build Gradle, puis Maven, puis Ant.
|
||||
2. Exécuter le premier fichier de build trouvé. Si les fichiers Gradle et Maven sont présents, le fichier Gradle est utilisé.
|
||||
3. Sinon, rechercher les fichiers de build dans les sous-répertoires directs du répertoire racine. Si un seul sous-répertoire contient des fichiers de build, exécutez le premier fichier identifié dans ce sous-répertoire (en utilisant la même préférence que pour 1). Si plusieurs sous-répertoires contiennent des fichiers de build, signaler une erreur.
|
||||
|
||||
## Adding build steps for a compiled language
|
||||
## Ajout des étapes de build pour un langage compilé
|
||||
|
||||
{% 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 %} Pour plus d’informations sur la modification du fichier de workflow, consultez « [Configuration de l’{% 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.
|
||||
Après avoir supprimé l’étape `autobuild`, supprimez les marques de commentaire de l’étape `run` et ajoutez des commandes de build qui conviennent à votre dépôt. L’étape `run` du workflow exécute des programmes en ligne de commande avec l’interpréteur de commandes du système d’exploitation. Vous pouvez modifier ces commandes et ajouter d’autres commandes pour personnaliser le processus de build.
|
||||
|
||||
``` yaml
|
||||
- run: |
|
||||
@@ -135,9 +134,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)."
|
||||
Pour plus d’informations sur le mot clé`run`, consultez « [Syntaxe de workflow pour {% 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#:
|
||||
Si votre référentiel contient plusieurs langages compilés, vous pouvez spécifier des commandes de build spécifiques à un langage. Par exemple, si votre dépôt contient du code C/C++, C# et Java et que `autobuild` génère correctement le code C/C++ et C#, mais ne parvient pas à générer le code Java, vous pouvez utiliser la configuration suivante dans votre workflow, après l’étape `init`. Cela spécifie les étapes de build pour Java tout en continuant à utiliser `autobuild` pour C/C++ et C# :
|
||||
|
||||
```yaml
|
||||
- if: matrix.language == 'cpp' || matrix.language == 'csharp'
|
||||
@@ -151,8 +150,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)."
|
||||
Pour plus d’informations sur l’instruction conditionnelle `if`, consultez « [Syntaxe de workflow pour 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)."
|
||||
Pour obtenir d’autres conseils et astuces sur la raison pour laquelle `autobuild` ne génère pas votre code, consultez « [Résolution des problèmes liés au workflow {% 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 %}.
|
||||
Si vous avez ajouté des étapes de génération manuelles pour les langages compilés et que l’{% data variables.product.prodname_code_scanning %} ne fonctionne toujours pas sur votre dépôt, contactez le {% data variables.contact.contact_support %}.
|
||||
|
||||
@@ -25,10 +25,9 @@ shortTitle: Enable push protection
|
||||
Up to now, {% data variables.product.prodname_secret_scanning_GHAS %} checks for secrets _after_ a push and alerts users to exposed secrets. {% data reusables.secret-scanning.push-protection-overview %}
|
||||
|
||||
If a contributor bypasses a push protection block for a secret, {% data variables.product.prodname_dotcom %}:
|
||||
- generates an alert.
|
||||
- creates an alert in the "Security" tab of the repository.
|
||||
- creates an alert in the "Security" tab of the repository in the state described in the table below.
|
||||
- adds the bypass event to the audit log.{% ifversion secret-scanning-push-protection-email %}
|
||||
- sends an email alert to organization owners, security managers, and repository administrators, with a link to the related secret and the reason why it was allowed.{% endif %}
|
||||
- sends an email alert to organization owners, security managers, and repository administrators who are watching the repository, with a link to the secret and the reason why it was allowed.{% endif %}
|
||||
|
||||
{% data reusables.secret-scanning.bypass-reasons-and-alerts %}
|
||||
|
||||
|
||||
@@ -33,7 +33,7 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
|
||||
|
||||
## Supported secrets for partner patterns
|
||||
|
||||
{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
|
||||
{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers and alerts the relevant service provider whenever a secret is detected in a commit. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
|
||||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
|
||||
|
||||
@@ -37,9 +37,11 @@ You can secure the code you depend on by creating a vulnerability management pro
|
||||
|
||||
1. Create an inventory of your dependencies.
|
||||
|
||||
2. Know when there is a security vulnerability in a dependency.
|
||||
1. Know when there is a security vulnerability in a dependency.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
1. Enforce dependency reviews on your pull requests.{% endif %}
|
||||
|
||||
3. Assess the impact of that vulnerability on your code and decide what action to take.
|
||||
1. Assess the impact of that vulnerability on your code and decide what action to take.
|
||||
|
||||
### Automatic inventory generation
|
||||
|
||||
@@ -48,6 +50,11 @@ As a first step, you want to make a complete inventory of your dependencies. The
|
||||
### Automatic detection of vulnerabilities in dependencies
|
||||
|
||||
{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
### Automatic detection of vulnerabilities in pull requests
|
||||
|
||||
The {% data variables.product.prodname_dependency_review_action %} enforces a dependency review on your pull requests, making it easy for you to see if a pull request will introduce a vulnerable version of a dependency to your repository. When a vulnerability is detected, the {% data variables.product.prodname_dependency_review_action %} can block the pull request from merging. For more information, see "[Dependency review enforcement](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."{% endif %}
|
||||
|
||||
|
||||
### Assessment of exposure to risk from a vulnerable dependency
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About supply chain security
|
||||
intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes %}, and patching them{% endif %}.'
|
||||
title: À propos de la sécurité de la chaîne d’approvisionnement
|
||||
intro: '{% data variables.product.product_name %} vous aide à sécuriser votre chaîne d’approvisionnement, en comprenant les dépendances de votre environnement et en connaissant les vulnérabilités de ces dépendances{% ifversion fpt or ghec or ghes %}, puis en les corrigeant{% endif %}.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Supply chain security
|
||||
redirect_from:
|
||||
@@ -19,160 +19,157 @@ topics:
|
||||
- Dependencies
|
||||
- Pull requests
|
||||
- Repositories
|
||||
ms.openlocfilehash: d0f743db7d1f5a054a3eb8c7b4dbf81052aca50f
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181235'
|
||||
---
|
||||
## À propos de la sécurité de la chaîne d’approvisionnement chez GitHub
|
||||
|
||||
## About supply chain security at GitHub
|
||||
Avec l’utilisation accélérée de l’open source, la plupart des projets dépendent de centaines de dépendances open source. Cela pose un problème de sécurité : que se passe-t-il si les dépendances que vous utilisez sont vulnérables ? Vous pourriez faire courir à vos utilisateurs le risque d’une attaque de chaîne d’approvisionnement. L’une des choses les plus importantes que vous puissiez faire pour protéger votre chaîne d’approvisionnement est de corriger vos dépendances vulnérables{% ifversion GH-advisory-db-supports-malware %} et de remplacer tout logiciel malveillant{% endif %}.
|
||||
|
||||
With the accelerated use of open source, most projects depend on hundreds of open-source dependencies. This poses a security problem: what if the dependencies you're using are vulnerable? You could be putting your users at risk of a supply chain attack. One of the most important things you can do to protect your supply chain is to patch your vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and replace any malware{% endif %}.
|
||||
Vous ajoutez les dépendances directement à votre chaîne d’approvisionnement quand vous les spécifiez dans un fichier manifeste ou un fichier de verrouillage. Les dépendances peuvent également être incluses transitivement ; même si vous ne spécifiez pas une dépendance particulière, mais qu’une de vos dépendances l’utilise, vous êtes également dépendant de cette dépendance.
|
||||
|
||||
You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency.
|
||||
{% data variables.product.product_name %} offre une gamme de fonctionnalités pour vous aider à comprendre les dépendances dans votre environnement{% ifversion ghae %} et à connaître les vulnérabilités dans ces dépendances{% endif %}{% ifversion fpt or ghec or ghes %}, à connaître les vulnérabilités dans ces dépendances et à les corriger{% endif %}.
|
||||
|
||||
{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes %}, know about vulnerabilities in those dependencies, and patch them{% endif %}.
|
||||
|
||||
The supply chain features on {% data variables.product.product_name %} are:
|
||||
- **Dependency graph**
|
||||
- **Dependency review**
|
||||
- **{% data variables.product.prodname_dependabot_alerts %} **
|
||||
{% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
|
||||
Les fonctionnalités de la chaîne d’approvisionnement sur {% data variables.product.product_name %} sont les suivantes :
|
||||
- **Graphe de dépendances**
|
||||
- **Vérification des dépendances**
|
||||
- **{% data variables.product.prodname_dependabot_alerts %} ** {% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** {% endif %}
|
||||
|
||||
The dependency graph is central to supply chain security. The dependency graph identifies all upstream dependencies and public downstream dependents of a repository or package. You can see your repository’s dependencies and some of their properties, like vulnerability information, on the dependency graph for the repository.
|
||||
Le graphe de dépendances joue un rôle essentiel pour la sécurité de la chaîne d’approvisionnement. Le graphe de dépendances identifie toutes les dépendances en amont et les éléments dépendants en aval publics d’un dépôt ou d’un package. Vous pouvez voir les dépendances de votre dépôt et certaines de leurs propriétés, telles que les informations sur les vulnérabilités, sur le graphe de dépendances du dépôt.
|
||||
|
||||
Other supply chain features on {% data variables.product.prodname_dotcom %} rely on the information provided by the dependency graph.
|
||||
D’autres fonctionnalités de chaîne d’approvisionnement sur {% data variables.product.prodname_dotcom %} reposent sur les informations fournies par le graphe de dépendances.
|
||||
|
||||
- Dependency review uses the dependency graph to identify dependency changes and help you understand the security impact of these changes when you review pull requests.
|
||||
- {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of advisories published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} is detected.
|
||||
{% ifversion fpt or ghec or ghes %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository.
|
||||
- La révision des dépendances utilise le graphe de dépendances pour identifier les modifications de dépendance et vous aider à comprendre l’impact de ces modifications sur la sécurité quand vous passez en revue les demandes de tirage (pull request).
|
||||
- {% data variables.product.prodname_dependabot %} croise les données de dépendance fournies par le graphe de dépendances avec la liste des vulnérabilités connues publiées dans la {% data variables.product.prodname_advisory_database %}, analyse vos dépendances et génère des {% data variables.product.prodname_dependabot_alerts %} lors de la détection d’une vulnérabilité potentielle{% ifversion GH-advisory-db-supports-malware %} ou d’un logiciel malveillant{% endif %}.
|
||||
{% ifversion fpt or ghec or ghes %}- Les {% data variables.product.prodname_dependabot_security_updates %} utilisent le graphe de dépendances et les {% data variables.product.prodname_dependabot_alerts %} pour vous aider à mettre à jour les dépendances ayant des vulnérabilités connues dans votre dépôt.
|
||||
|
||||
{% data variables.product.prodname_dependabot_version_updates %} don't use the dependency graph and rely on the semantic versioning of dependencies instead. {% data variables.product.prodname_dependabot_version_updates %} help you keep your dependencies updated, even when they don’t have any vulnerabilities.
|
||||
Les {% data variables.product.prodname_dependabot_version_updates %} n’utilisent pas le graphe de dépendances et s’appuient plutôt sur le versioning sémantique des dépendances. Les {% data variables.product.prodname_dependabot_version_updates %} vous aident à maintenir vos dépendances mises à jour, même quand elles n’ont pas de vulnérabilités.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)."
|
||||
{% ifversion fpt or ghec or ghes %} Pour obtenir des guides de bonnes pratiques sur la sécurité de la chaîne d’approvisionnement de bout en bout, y compris la protection des comptes personnels, du code et des processus de génération, consultez « [Sécurisation de votre chaîne d’approvisionnement de bout en bout](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview) ».
|
||||
{% endif %}
|
||||
|
||||
## Feature overview
|
||||
## Présentation des fonctionnalités
|
||||
|
||||
### What is the dependency graph
|
||||
### Qu’est-ce que le graphe de dépendances ?
|
||||
|
||||
To generate the dependency graph, {% data variables.product.company_short %} looks at a repository’s explicit dependencies declared in the manifest and lockfiles. When enabled, the dependency graph automatically parses all known package manifest files in the repository, and uses this to construct a graph with known dependency names and versions.
|
||||
Pour générer le graphe de dépendances, {% data variables.product.company_short %} examine les dépendances explicites d’un dépôt déclarées dans le manifeste et les fichiers de verrouillage. Quand il est activé, le graphe de dépendances analyse automatiquement tous les fichiers manifestes de package connus dans le dépôt, puis, à partir des informations recueillies, construit un graphe avec les noms et les versions de dépendances connues.
|
||||
|
||||
- The dependency graph includes information on your _direct_ dependencies and _transitive_ dependencies.
|
||||
- The dependency graph is automatically updated when you push a commit to {% data variables.product.company_short %} that changes or adds a supported manifest or lock file to the default branch, and when anyone pushes a change to the repository of one of your dependencies.
|
||||
- You can see the dependency graph by opening the repository's main page on {% data variables.product.product_name %}, and navigating to the **Insights** tab.
|
||||
- Le graphe de dépendances inclut des informations sur vos dépendances _directes_ et vos dépendances _transitives_.
|
||||
- Le graphe de dépendances est automatiquement mis à jour quand vous poussez (push) un commit vers {% data variables.product.company_short %} qui change ou ajoute un manifeste ou un fichier de verrouillage pris en charge à la branche par défaut et quand toute personne pousse une modification vers le dépôt de l’une de vos dépendances.
|
||||
- Vous pouvez voir le graphe de dépendances en ouvrant la page principale du dépôt sur {% data variables.product.product_name %}, puis en accédant à l’onglet **Insights**.
|
||||
|
||||
{% ifversion dependency-submission-api %}
|
||||
{% data reusables.dependency-submission.dependency-submission-link %}
|
||||
{% endif %}
|
||||
{% ifversion dependency-submission-api %} {% data reusables.dependency-submission.dependency-submission-link %} {% endif %}
|
||||
|
||||
For more information about the dependency graph, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
Pour plus d’informations sur le graphe de dépendances, consultez « [À propos du graphe de dépendances](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph) ».
|
||||
|
||||
### What is dependency review
|
||||
### Qu’est-ce que la révision des dépendances ?
|
||||
|
||||
Dependency review helps reviewers and contributors understand dependency changes and their security impact in every pull request.
|
||||
La révision des dépendances aide les réviseurs et les contributeurs à comprendre les modifications de dépendance et leur impact sur la sécurité dans chaque demande de tirage.
|
||||
|
||||
- Dependency review tells you which dependencies were added, removed, or updated, in a pull request. You can use the release dates, popularity of dependencies, and vulnerability information to help you decide whether to accept the change.
|
||||
- You can see the dependency review for a pull request by showing the rich diff on the **Files Changed** tab.
|
||||
- La révision des dépendances vous indique quelles dépendances ont été ajoutées, supprimées ou mises à jour, dans une demande de tirage. Vous pouvez utiliser les dates de publication, la popularité des dépendances et les informations de vulnérabilité pour vous aider à décider s’il faut accepter la modification.
|
||||
- Vous pouvez voir la révision des dépendances pour une demande de tirage en affichant la différence enrichie sous l’onglet **Fichiers modifiés**.
|
||||
|
||||
For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
Pour plus d’informations sur la révision des dépendances, consultez « [À propos de la révision des dépendances](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review) ».
|
||||
|
||||
### What is Dependabot
|
||||
### Qu’est-ce que Dependabot ?
|
||||
|
||||
{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}.
|
||||
{% data variables.product.prodname_dependabot %} maintient vos dépendances à jour en vous informant des vulnérabilités de sécurité dans vos dépendances{% ifversion fpt or ghec or ghes %} et ouvre automatiquement les demandes de tirage pour mettre à niveau vos dépendances vers la prochaine version sécurisée disponible quand une alerte {% data variables.product.prodname_dependabot %} est déclenchée, ou vers la dernière version quand une mise en production est publiée{% else %} afin que vous puissiez mettre à jour cette dépendance{% endif %}.
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
The term "{% data variables.product.prodname_dependabot %}" encompasses the following features:
|
||||
- {% data variables.product.prodname_dependabot_alerts %}—Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
|
||||
- {% data variables.product.prodname_dependabot_updates %}:
|
||||
- {% data variables.product.prodname_dependabot_security_updates %}—Triggered updates to upgrade your dependencies to a secure version when an alert is triggered.
|
||||
- {% data variables.product.prodname_dependabot_version_updates %}—Scheduled updates to keep your dependencies up to date with the latest version.
|
||||
{% ifversion fpt or ghec or ghes %} Le terme « {% data variables.product.prodname_dependabot %} » englobe les fonctionnalités suivantes :
|
||||
- {% data variables.product.prodname_dependabot_alerts %} : notification affichée sous l’onglet **Sécurité** du dépôt et dans le graphe de dépendances du dépôt. L’alerte contient un lien vers le fichier affecté dans le projet et des informations sur une version corrigée.
|
||||
- {% data variables.product.prodname_dependabot_updates %} :
|
||||
- {% data variables.product.prodname_dependabot_security_updates %} : mises à jour déclenchées pour mettre à niveau vos dépendances vers une version sécurisée quand une alerte est déclenchée.
|
||||
- {% data variables.product.prodname_dependabot_version_updates %} : mises à jour planifiées pour maintenir vos dépendances à jour avec la dernière version.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}, and {% data variables.product.prodname_dependabot_version_updates %} do not use {% data variables.product.prodname_actions %} when they run on {% data variables.product.product_name %}. However, pull requests opened by {% data variables.product.prodname_dependabot %} can trigger workflows that run actions. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions)."
|
||||
Les {% data variables.product.prodname_dependabot_alerts %}, les {% data variables.product.prodname_dependabot_security_updates %} et les {% data variables.product.prodname_dependabot_version_updates %} n’utilisent pas {% data variables.product.prodname_actions %} quand elles s’exécutent sur {% data variables.product.product_name %}. Toutefois, les demandes de tirage ouvertes par {% data variables.product.prodname_dependabot %} peuvent déclencher des workflows qui exécutent des actions. Pour plus d’informations, consultez « [Automatisation de {% data variables.product.prodname_dependabot %} avec {% data variables.product.prodname_actions %}](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions) ».
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %} and {% data variables.product.prodname_dependabot_version_updates %} require {% data variables.product.prodname_actions %} to run on {% data variables.product.product_name %}. {% data variables.product.prodname_dependabot_alerts %} do not require {% data variables.product.prodname_actions %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
Les {% data variables.product.prodname_dependabot_security_updates %} et les {% data variables.product.prodname_dependabot_version_updates %} nécessitent que {% data variables.product.prodname_actions %} s’exécute sur {% data variables.product.product_name %}. Les {% data variables.product.prodname_dependabot_alerts %} ne nécessitent pas {% data variables.product.prodname_actions %}. Pour plus d’informations, consultez « [Activation de {% data variables.product.prodname_dependabot %} pour votre entreprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise) ».
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% data variables.product.prodname_actions %} is not required for {% data variables.product.prodname_dependabot_alerts %} to run on {% data variables.product.product_name %}.
|
||||
{% data variables.product.prodname_actions %} n’est pas nécessaire pour que les {% data variables.product.prodname_dependabot_alerts %} s’exécutent sur {% data variables.product.product_name %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion dependabot-actions-support %}
|
||||
|
||||
{% data reusables.dependabot.dependabot-actions-support %} For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)."
|
||||
{% data reusables.dependabot.dependabot-actions-support %} Pour plus d’informations, consultez « [À propos des {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates) ».
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### What are Dependabot alerts
|
||||
#### Qu’est-ce que les alertes Dependabot ?
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %} highlight repositories affected by a newly discovered vulnerability based on the dependency graph and the {% data variables.product.prodname_advisory_database %}, which contains advisories for known vulnerabilities{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}.
|
||||
Les {% data variables.product.prodname_dependabot_alerts %} mettent en évidence les dépôts affectés par une vulnérabilité nouvellement découverte en fonction du graphe de dépendances et de la {% data variables.product.prodname_advisory_database %}, qui contient les versions sur les listes de vulnérabilités{% ifversion GH-advisory-db-supports-malware %} et programmes malveillants{% endif %}.
|
||||
|
||||
- {% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
|
||||
{% ifversion fpt or ghec %}
|
||||
- A new advisory is added to the {% data variables.product.prodname_advisory_database %}.{% else %}
|
||||
- New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- The dependency graph for the repository changes.
|
||||
- {% data variables.product.prodname_dependabot_alerts %} are displayed {% ifversion fpt or ghec or ghes %} on the **Security** tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version.
|
||||
- {% data variables.product.prodname_dependabot %} effectue une analyse pour détecter les dépendances non sécurisées et émet des {% data variables.product.prodname_dependabot_alerts %} quand :{% ifversion fpt or ghec %}
|
||||
- Un nouvel avis est ajouté à la {% data variables.product.prodname_advisory_database %}.{% else %}
|
||||
- Les nouvelles données d’avis sont synchronisées sur {% data variables.location.product_location %} toutes les heures à partir de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- Le graphe de dépendances d’un dépôt change.
|
||||
- Les {% data variables.product.prodname_dependabot_alerts %} sont affichées {% ifversion fpt or ghec or ghes %} sous l’onglet **Sécurité** du dépôt et{% endif %} dans le graphe de dépendances du dépôt. L’alerte inclut {% ifversion fpt or ghec or ghes %}un lien vers le fichier affecté dans le projet et {% endif %}des informations sur une version corrigée.
|
||||
|
||||
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
|
||||
Pour plus d’informations, consultez « [À propos des {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies) ».
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
#### What are Dependabot updates
|
||||
#### Qu’est-ce que les mises à jour Dependabot ?
|
||||
|
||||
There are two types of {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} _security_ updates and _version_ updates. {% data variables.product.prodname_dependabot %} generates automatic pull requests to update your dependencies in both cases, but there are several differences.
|
||||
Il existe deux types de {% data variables.product.prodname_dependabot_updates %} : les mises à jour de _version_ et les mises à jour de _sécurité_ {% data variables.product.prodname_dependabot %}. {% data variables.product.prodname_dependabot %} génère des demandes de tirage automatiques pour mettre à jour vos dépendances dans les deux cas, mais il existe plusieurs différences.
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %}:
|
||||
- Triggered by a {% data variables.product.prodname_dependabot %} alert
|
||||
- Update dependencies to the minimum version that resolves a known vulnerability
|
||||
- Supported for ecosystems the dependency graph supports
|
||||
- Does not require a configuration file, but you can use one to override the default behavior
|
||||
{% data variables.product.prodname_dependabot_security_updates %} :
|
||||
- Déclenchées par une alerte {% data variables.product.prodname_dependabot %}
|
||||
- Mettent à jour les dépendances vers la version minimale qui résout une vulnérabilité connue
|
||||
- Prises en charge pour les écosystèmes pris en charge par le graphe de dépendances
|
||||
- Ne nécessite pas de fichier de configuration, mais vous pouvez en utiliser un pour remplacer le comportement par défaut
|
||||
|
||||
{% data variables.product.prodname_dependabot_version_updates %}:
|
||||
- Requires a configuration file
|
||||
- Run on a schedule you configure
|
||||
- Update dependencies to the latest version that matches the configuration
|
||||
- Supported for a different group of ecosystems
|
||||
{% data variables.product.prodname_dependabot_version_updates %} :
|
||||
- Requiert un fichier de configuration
|
||||
- Exécutées selon une planification que vous configurez
|
||||
- Mettent à jour les dépendances vers la dernière version qui correspond à la configuration
|
||||
- Prises en charge pour un autre groupe d’écosystèmes
|
||||
|
||||
For more information about {% data variables.product.prodname_dependabot_updates %}, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)" and "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)."
|
||||
Pour plus d’informations sur les {% data variables.product.prodname_dependabot_updates %}, consultez « [À propos des {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates) » et « [À propos des {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates) ».
|
||||
{% endif %}
|
||||
|
||||
## Feature availability
|
||||
## Disponibilité des fonctionnalités
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
Public repositories:
|
||||
- **Dependency graph**—enabled by default and cannot be disabled.
|
||||
- **Dependency review**—enabled by default and cannot be disabled.
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. {% data variables.product.prodname_dotcom %} detects insecure dependencies and displays information in the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %}.
|
||||
You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)."
|
||||
Dépôts publics :
|
||||
- **Graphe de dépendances** : activé par défaut et ne peut pas être désactivé.
|
||||
- **Révision des dépendances** : activée par défaut et ne peut pas être désactivée.
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** : non activées par défaut. {% data variables.product.prodname_dotcom %} détecte les dépendances non sécurisées et affiche des informations dans le graphe de dépendances, mais ne génère pas d’{% data variables.product.prodname_dependabot_alerts %} par défaut. Les propriétaires de dépôts ou les personnes disposant d’un accès administrateur peuvent activer les {% data variables.product.prodname_dependabot_alerts %}.
|
||||
Vous pouvez également activer ou désactiver les alertes Dependabot pour tous les dépôts appartenant à votre compte d’utilisateur ou organisation. Pour plus d’informations, consultez « [Gestion des paramètres de sécurité et d’analyse pour votre compte d’utilisateur](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account) » ou « [Gestion des paramètres de sécurité et d’analyse pour votre organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization) ».
|
||||
|
||||
Private repositories:
|
||||
- **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
|
||||
Dépôts privés :
|
||||
- **Graphe de dépendances** : non activé par défaut. La fonctionnalité peut être activée par les administrateurs de dépôt. Pour plus d’informations, consultez « [Exploration des dépendances d’un dépôt](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository) ».
|
||||
{% ifversion fpt %}
|
||||
- **Dependency review**—available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
|
||||
- **Révision des dépendances** : disponible dans les dépôts privés appartenant aux organisations qui utilisent {% data variables.product.prodname_ghe_cloud %} et qui disposent d’une licence pour {% data variables.product.prodname_GH_advanced_security %}. Pour plus d’informations, consultez la [documentation {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
|
||||
{% elsif ghec %}
|
||||
- **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
|
||||
{% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
|
||||
You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)."
|
||||
- **Révision des dépendances** : disponible dans les dépôts privés appartenant aux organisations, sous réserve que vous disposiez d’une licence pour {% data variables.product.prodname_GH_advanced_security %} et que le graphe de dépendances soit activé. Pour plus d’informations, consultez « [À propos de {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) » et « [Exploration des dépendances d’un dépôt](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository) ». {% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** : non activées par défaut. Les propriétaires de dépôts privés ou les personnes disposant d’un accès administrateur peuvent activer les {% data variables.product.prodname_dependabot_alerts %} en activant le graphe de dépendances et les {% data variables.product.prodname_dependabot_alerts %} pour leurs dépôts.
|
||||
Vous pouvez également activer ou désactiver les alertes Dependabot pour tous les dépôts appartenant à votre compte d’utilisateur ou organisation. Pour plus d’informations, consultez « [Gestion des paramètres de sécurité et d’analyse pour votre compte d’utilisateur](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account) » ou « [Gestion des paramètres de sécurité et d’analyse pour votre organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization) ».
|
||||
|
||||
Any repository type:
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
|
||||
Tout type de dépôt :
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** : non activées par défaut. Vous pouvez activer les {% data variables.product.prodname_dependabot_security_updates %} pour n’importe quel dépôt qui utilise les {% data variables.product.prodname_dependabot_alerts %} et le graphe de dépendances. Pour plus d’informations sur l’activation des mises à jour de sécurité, consultez « [Configuration des {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates) ».
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** : non activées par défaut. Les personnes disposant d’autorisations d’écriture sur un dépôt peuvent activer les {% data variables.product.prodname_dependabot_version_updates %}. Pour obtenir des informations sur l’activation des mises à jour de version, consultez « [Configuration de {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates) ».
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
- **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
- **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
|
||||
{% endif %}
|
||||
{% ifversion ghes %}
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
|
||||
- **Graphe de dépendances** et **{% data variables.product.prodname_dependabot_alerts %}** : non activés par défaut. Les deux fonctionnalités sont configurées au niveau de l’entreprise par le propriétaire de l’entreprise. Pour plus d’informations, consultez {% ifversion ghes %}« [Activation du graphe de dépendances pour votre entreprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise) » et {% endif %}« [Activation de {% data variables.product.prodname_dependabot %} pour votre entreprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise) ».
|
||||
- **Révision des dépendances** : disponible quand le graphe de dépendances est activé pour {% data variables.location.product_location %} et qu’{% data variables.product.prodname_advanced_security %} est activé pour l’organisation ou le dépôt. Pour plus d’informations, consultez « [À propos de {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) ».
|
||||
{% endif %} {% ifversion ghes %}
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** : non activées par défaut. Vous pouvez activer les {% data variables.product.prodname_dependabot_security_updates %} pour n’importe quel dépôt qui utilise les {% data variables.product.prodname_dependabot_alerts %} et le graphe de dépendances. Pour plus d’informations sur l’activation des mises à jour de sécurité, consultez « [Configuration des {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates) ».
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** : non activées par défaut. Les personnes disposant d’autorisations d’écriture sur un dépôt peuvent activer les {% data variables.product.prodname_dependabot_version_updates %}. Pour obtenir des informations sur l’activation des mises à jour de version, consultez « [Configuration de {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates) ».
|
||||
{% endif %}
|
||||
|
||||
@@ -57,10 +57,7 @@ Regardless of where you created or access your codespaces, you can view and mana
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
|
||||
1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the stop icon.
|
||||
|
||||
|
||||
You can stop a codespace from the "Your codespaces" page (see [the web browser instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) or by using {% data variables.product.prodname_cli %} (see [the CLI instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)).
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Présentation des conteneurs de développement
|
||||
intro: 'Lorsque vous travaillez dans un codespace, l’environnement dans lequel vous travaillez est créé à l’aide d’un conteneur de développement hébergé sur une machine virtuelle.'
|
||||
title: Introduction to dev containers
|
||||
intro: 'When you work in a codespace, the environment you are working in is created using a development container, or dev container, hosted on a virtual machine.'
|
||||
permissions: People with write permissions to a repository can create or edit the codespace configuration.
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
|
||||
@@ -16,76 +16,71 @@ topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
- Fundamentals
|
||||
ms.openlocfilehash: 0b47f0292eb3a13467a8227ac323d289f9712223
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158772'
|
||||
---
|
||||
## À propos des conteneurs de développement
|
||||
|
||||
Les conteneurs de développement sont des conteneurs Docker spécifiquement configurés pour fournir un environnement de développement complet. Chaque fois que vous travaillez dans un codespace, vous utilisez un conteneur de développement sur une machine virtuelle.
|
||||
## About dev containers
|
||||
|
||||
Vous pouvez configurer le conteneur de développement pour un dépôt de façon à ce que les codespaces créés pour ce dépôt vous offrent un environnement sur mesure et complet avec l’ensemble des outils et runtimes dont vous avez besoin pour travailler sur un projet spécifique. Si vous ne définissez pas de configuration dans le dépôt, {% data variables.product.prodname_github_codespaces %} utilise une configuration par défaut contenant de nombreux outils courants dont votre équipe pourrait avoir besoin pour le développement de votre projet. Pour plus d’informations, consultez « [Utilisation de la configuration de conteneur de développement par défaut](#using-the-default-dev-container-configuration) ».
|
||||
Development containers, or dev containers, are Docker containers that are specifically configured to provide a fully featured development environment. Whenever you work in a codespace, you are using a dev container on a virtual machine.
|
||||
|
||||
Les fichiers de configuration d’un conteneur de développement sont contenus dans un répertoire `.devcontainer` dans votre dépôt. Vous pouvez utiliser {% data variables.product.prodname_vscode %} pour ajouter des fichiers de configuration à votre place. Vous pouvez opérer un choix dans une sélection de configurations prédéfinies pour différents types de projet. Vous pouvez utiliser celles-ci sans configuration supplémentaire, ou les modifier pour affiner l’environnement de développement qu’elles produisent. Pour plus d’informations, consultez « [Utilisation d’une configuration de conteneur de développement prédéfinie](#using-a-predefined-dev-container-configuration) ».
|
||||
You can configure the dev container for a repository so that codespaces created for that repository give you a tailored development environment, complete with all the tools and runtimes you need to work on a specific project. If you don't define a configuration in the repository then {% data variables.product.prodname_github_codespaces %} uses a default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
|
||||
|
||||
Vous pouvez également ajouter vos propres fichiers de configuration personnalisés. Pour plus d’informations, consultez « [Création d’une configuration de conteneur de développement personnalisée](#creating-a-custom-dev-container-configuration) ».
|
||||
The configuration files for a dev container are contained in a `.devcontainer` directory in your repository. You can use {% data variables.product.prodname_vscode %} to add configuration files for you. You can choose from a selection of predefined configurations for various project types. You can use these without further configuration, or you can edit the configurations to refine the development environment they produce. For more information, see "[Using a predefined dev container configuration](#using-a-predefined-dev-container-configuration)."
|
||||
|
||||
Vous pouvez définir une configuration de conteneur de développement unique pour un dépôt, différentes configurations pour différentes branches ou plusieurs configurations. Lorsque plusieurs configurations sont disponibles, les utilisateurs peuvent choisir leur configuration préférée quand ils créent un codespace. Cela est particulièrement utile pour les dépôts volumineux contenant du code source dans différents langages de programmation ou pour différents projets. Vous pouvez créer un choix de configurations qui permettent à différentes équipes de travailler dans un codespace configuré de manière appropriée pour le travail qu’elles accomplissent.
|
||||
Alternatively, you can add your own custom configuration files. For more information, see "[Creating a custom dev container configuration](#creating-a-custom-dev-container-configuration)."
|
||||
|
||||
Quand vous créez un codespace à partir d’un modèle, vous pouvez commencer avec un ou plusieurs fichiers de configuration de conteneur de développement dans votre espace de travail. Pour configurer davantage votre environnement, vous pouvez ajouter des paramètres à ces fichiers ou en supprimer et regénérer le conteneur pour appliquer les modifications au codespace dans lequel vous travaillez. Si vous publiez votre codespace dans un dépôt sur {% data variables.product.product_name %}, tous les codespaces créés à partir de ce dépôt partagent la configuration que vous avez définie. Pour plus d’informations, consultez « [Application de modifications de configuration à un codespace](#applying-configuration-changes-to-a-codespace) » et « [Création d’un codespace à partir d’un modèle](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository) ».
|
||||
You can define a single dev container configuration for a repository, different configurations for different branches, or multiple configurations. When multiple configurations are available, users can choose their preferred configuration when they create a codespace. This is particularly useful for large repositories that contain source code in different programming languages or for different projects. You can create a choice of configurations that allow different teams to work in a codespace that's set up appropriately for the work they are doing.
|
||||
|
||||
When you create a codespace from a template, you might start with one or more dev container configuration files in your workspace. To configure your environment further, you can add or remove settings from these files and rebuild the container to apply the changes to the codespace you're working in. If you publish your codespace to a repository on {% data variables.product.product_name %}, then any codespaces created from that repository will share the configuration you've defined. For more information, see "[Applying configuration changes to a codespace](#applying-configuration-changes-to-a-codespace)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)."
|
||||
|
||||
### devcontainer.json
|
||||
|
||||
Le fichier principal d’une configuration de conteneur de développement est le fichier `devcontainer.json`. Vous pouvez l’utiliser pour déterminer l’environnement de codespaces créés pour votre dépôt. Le contenu de ce fichier définit un conteneur de développement qui peut inclure des infrastructures, des outils, des extensions et un réacheminement de port. Le fichier `devcontainer.json` contient généralement une référence à un Dockerfile qui est normalement situé à côté du fichier `devcontainer.json`.
|
||||
The primary file in a dev container configuration is the `devcontainer.json` file. You can use this file to determine the environment of codespaces created for your repository. The contents of this file define a dev container that can include frameworks, tools, extensions, and port forwarding. The `devcontainer.json` file usually contains a reference to a Dockerfile, which is typically located alongside the `devcontainer.json` file.
|
||||
|
||||
Si vous créez un codespace à partir d’un dépôt sans fichier `devcontainer.json` ou que vous commencez à partir du modèle vide de {% data variables.product.company_short %}, la configuration de conteneur de développement par défaut est utilisée. Pour plus d’informations, consultez « [Utilisation de la configuration de conteneur de développement par défaut](#using-the-default-dev-container-configuration) ».
|
||||
If you create a codespace from a repository without a `devcontainer.json` file, or if you start from {% data variables.product.company_short %}'s blank template, the default dev container configuration is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
|
||||
|
||||
Le fichier `devcontainer.json` se trouve généralement dans le répertoire `.devcontainer` de votre dépôt. Vous pouvez également le placer directement à la racine du dépôt, auquel cas le nom de fichier doit commencer par un point : `.devcontainer.json`.
|
||||
The `devcontainer.json` file is usually located in the `.devcontainer` directory of your repository. Alternatively, you can locate it directly in the root of the repository, in which case the file name must begin with a period: `.devcontainer.json`.
|
||||
|
||||
Si vous souhaitez disposer d’un choix de configurations de conteneur de développement dans votre dépôt, toutes les alternatives au fichier `.devcontainer/devcontainer.json` (ou `.devcontainer.json`) doivent se trouver dans leur propre sous-répertoire dans le chemin d’accès `.devcontainer/SUBDIRECTORY/devcontainer.json`. Par exemple, vous pourriez avoir le choix entre deux configurations :
|
||||
If you want to have a choice of dev container configurations in your repository, any alternatives to the `.devcontainer/devcontainer.json` (or `.devcontainer.json`) file must be located in their own subdirectory at the path `.devcontainer/SUBDIRECTORY/devcontainer.json`. For example, you could have a choice of two configurations:
|
||||
* `.devcontainer/database-dev/devcontainer.json`
|
||||
* `.devcontainer/gui-dev/devcontainer.json`
|
||||
|
||||
Lorsque vous avez plusieurs fichiers `devcontainer.json` dans votre dépôt, chaque codespace est créé à partir d’une seule des configurations. Des paramètres ne peuvent pas être importés ou hérités entre fichiers `devcontainer.json`. Si un fichier `devcontainer.json` dans un sous-répertoire personnalisé a des fichiers dépendants, tels que le Dockerfile ou des scripts exécutés par des commandes dans le fichier `devcontainer.json`, il est recommandé de colocaliser ces fichiers dans le même sous-répertoire.
|
||||
When you have multiple `devcontainer.json` files in your repository, each codespace is created from only one of the configurations. Settings cannot be imported or inherited between `devcontainer.json` files. If a `devcontainer.json` file in a custom subdirectory has dependent files, such as the Dockerfile or scripts that are run by commands in the `devcontainer.json` file, it's recommended that you co-locate these files in the same subdirectory.
|
||||
|
||||
Pour plus d’informations sur la façon de choisir votre configuration de conteneur de développement préférée quand vous créez un codespace, consultez « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository) ».
|
||||
For information about how to choose your preferred dev container configuration when you create a codespace, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
|
||||
{% data reusables.codespaces.more-info-devcontainer %}
|
||||
|
||||
#### Comment utiliser le devcontainer.json
|
||||
#### How to use the devcontainer.json
|
||||
|
||||
Il est utile de considérer que le fichier `devcontainer.json` fournit une « customisation » plutôt qu’une « personnalisation ». Vous ne devriez inclure que des éléments dont toute personne travaillant sur votre codebase a besoin en tant que composants standard de l’environnement de développement, pas des éléments correspondant à des préférences personnelles. Il est bon de normaliser des éléments tels que des linters en exigeant que chacun les installe, et par conséquent de les inclure dans votre fichier `devcontainer.json`. En revanche, des éléments tels que des éléments décoratifs ou des thèmes d’interface utilisateur sont des choix personnels qui n’ont pas leur place dans le fichier `devcontainer.json`.
|
||||
It's useful to think of the `devcontainer.json` file as providing "customization" rather than "personalization." You should only include things that everyone working on your codebase needs as standard elements of the development environment, not things that are personal preferences. Things like linters are good to standardize on, and to require everyone to have installed, so they're good to include in your `devcontainer.json` file. Things like user interface decorators or themes are personal choices that should not be put in the `devcontainer.json` file.
|
||||
|
||||
Vous pouvez personnaliser vos codespaces à l’aide de dotfiles et d’une Synchronisation des paramètres. Pour plus d’informations, consultez « [Personnalisation de {% data variables.product.prodname_github_codespaces %} pour votre compte](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account) ».
|
||||
You can personalize your codespaces by using dotfiles and Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)."
|
||||
|
||||
### Dockerfile
|
||||
|
||||
Vous pouvez ajouter un Dockerfile à votre configuration de conteneur de développement.
|
||||
You can add a Dockerfile as part of your dev container configuration.
|
||||
|
||||
Le Dockerfile est un fichier texte contenant les instructions nécessaires pour créer une image conteneur Docker. Cette image est utilisée pour générer un conteneur de développement chaque fois que quelqu’un crée un codespace à l’aide du fichier `devcontainer.json` référençant ce Dockerfile. Les instructions figurant dans le Dockerfile commencent généralement par référencer une image parente sur laquelle sera basée la nouvelle image qui sera créée. Viennent ensuite des commandes qui sont exécutées pendant le processus de création de l’image, par exemple, pour installer des packages logiciels.
|
||||
The Dockerfile is a text file that contains the instructions needed to create a Docker container image. This image is used to generate a development container each time someone creates a codespace using the `devcontainer.json` file that references this Dockerfile. The instructions in the Dockerfile typically begin by referencing a parent image on which the new image that will be created is based. This is followed by commands that are run during the image creation process, for example to install software packages.
|
||||
|
||||
Le Dockerfile d’un conteneur de développement se trouve généralement dans le dossier `.devcontainer`, à proximité du `devcontainer.json` dans lequel il est référencé.
|
||||
The Dockerfile for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Remarque** : au lieu d’utiliser un Dockerfile, vous pouvez utiliser la propriété `image` dans le fichier `devcontainer.json` pour faire référence directement à une image existante que vous souhaitez utiliser. L’image que vous spécifiez ici doit être autorisée par toute stratégie d’image d’organisation qui a été définie. Pour plus d’informations, consultez « [Restriction de l’image de base pour les codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces) ». En l’absence de Dockerfile ou d’image, l’image conteneur par défaut est utilisée. Pour plus d’informations, consultez « [Utilisation de la configuration de conteneur de développement par défaut](#using-the-default-dev-container-configuration) ».
|
||||
**Note**: As an alternative to using a Dockerfile you can use the `image` property in the `devcontainer.json` file to refer directly to an existing image you want to use. The image you specify here must be allowed by any organization image policy that has been set. For more information, see "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)." If neither a Dockerfile nor an image is found then the default container image is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
#### Exemple Dockerfile simple
|
||||
#### Simple Dockerfile example
|
||||
|
||||
L’exemple suivant utilise quatre instructions :
|
||||
The following example uses four instructions:
|
||||
|
||||
`ARG` définit une variable de temps de génération.
|
||||
`ARG` defines a build-time variable.
|
||||
|
||||
`FROM` spécifie l’image parente sur laquelle l’image Docker générée sera basée.
|
||||
`FROM` specifies the parent image on which the generated Docker image will be based.
|
||||
|
||||
`COPY` copie un fichier et l’ajoute au système de fichiers.
|
||||
`COPY` copies a file and adds it to the filesystem.
|
||||
|
||||
`RUN` met à jour les listes de packages et exécute un script. Vous pouvez également utiliser une instruction `RUN` pour installer des logiciels, comme l’indiquent les instructions commentées. Pour exécuter plusieurs commandes, utilisez `&&` pour combiner les commandes dans une seule instruction `RUN`.
|
||||
`RUN` updates package lists and runs a script. You can also use a `RUN` instruction to install software, as shown by the commented out instructions. To run multiple commands, use `&&` to combine the commands into a single `RUN` statement.
|
||||
|
||||
```Dockerfile{:copy}
|
||||
ARG VARIANT="16-buster"
|
||||
@@ -102,11 +97,11 @@ COPY library-scripts/github-debian.sh /tmp/library-scripts/
|
||||
RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
|
||||
```
|
||||
|
||||
Pour plus d’informations sur les instructions concernant Dockerfile, consultez « [Dockerfile reference](https://docs.docker.com/engine/reference/builder) » dans la documentation Docker.
|
||||
For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation.
|
||||
|
||||
#### Utilisation d’un Dockerfile
|
||||
#### Using a Dockerfile
|
||||
|
||||
Pour utiliser un Dockerfile dans une configuration de conteneur de développement, référencez-le dans votre fichier `devcontainer.json` à l’aide de la propriété `dockerfile`.
|
||||
To use a Dockerfile as part of a dev container configuration, reference it in your `devcontainer.json` file by using the `dockerfile` property.
|
||||
|
||||
```json{:copy}
|
||||
{
|
||||
@@ -116,130 +111,134 @@ Pour utiliser un Dockerfile dans une configuration de conteneur de développemen
|
||||
}
|
||||
```
|
||||
|
||||
Différentes options s’offrent à vous si vous souhaitez utiliser l’orchestration de conteneur existante dans votre conteneur de développement. Pour plus d’informations, consultez la section « Options d’orchestration » de la [spécification](https://containers.dev/implementors/spec/#orchestration-options) sur le site web Conteneurs de développement.
|
||||
Various options are available to you if you want to use existing container orchestration in your dev container. For more information, see the "Orchestration options" section of the [Specification](https://containers.dev/implementors/spec/#orchestration-options) on the Development Containers website.
|
||||
|
||||
## Utilisation de la configuration de conteneur de développement par défaut
|
||||
## Using the default dev container configuration
|
||||
|
||||
Si vous ne définissez pas de configuration dans votre dépôt, {% data variables.product.prodname_dotcom %} crée un codespace à l’aide d’une image Linux par défaut. Cette image Linux inclut un certain nombre de versions de runtime pour des langages populaires tels que Python, Node, PHP, Java, Go, C++, Ruby et .NET Core/C#. Les dernières versions LTS de ces langages sont utilisées. Il y a également des outils pour prendre en charge la science des données et l’apprentissage automatique, tels que JupyterLab et Conda. L’image inclut également d’autres outils et utilitaires de développement tels que Git, GitHub CLI, yarn, openssh et vim. Pour voir l’ensemble des langages, runtimes et outils inclus, utilisez la commande `devcontainer-info content-url` à l’intérieur de votre terminal codespace, et suivez l’URL que la commande génère.
|
||||
If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace using a default Linux image. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs.
|
||||
|
||||
Pour plus d’informations sur ce qui est inclus dans l’image Linux par défaut, consultez le dépôt [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal).
|
||||
For information about what's included in the default Linux image, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal) repository.
|
||||
|
||||
La configuration par défaut est une bonne option si vous travaillez sur un petit projet utilisant les langages et outils fournis par {% data variables.product.prodname_github_codespaces %}.
|
||||
The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_github_codespaces %} provides.
|
||||
|
||||
## Utilisation d’une configuration de conteneur de développement prédéfinie
|
||||
## Using a predefined dev container configuration
|
||||
|
||||
Si vous utilisez {% data variables.product.prodname_codespaces %} dans {% data variables.product.prodname_vscode %} ou dans un navigateur web, vous pouvez créer une configuration de conteneur de développement pour votre dépôt en choisissant parmi une liste de configurations prédéfinies. Ces configurations fournissent des paramétrages courants pour des types de projets particuliers et peuvent vous aider à démarrer rapidement avec une configuration comprenant déjà les options de conteneur, les paramètres {% data variables.product.prodname_vscode %} et les extensions {% data variables.product.prodname_vscode %} appropriés à installer.
|
||||
If you use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, or in a web browser, you can create a dev container configuration for your repository by choosing from a list of predefined configurations. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
|
||||
|
||||
L’utilisation d’une configuration prédéfinie est une excellente idée si vous avez besoin d’une extensibilité supplémentaire. Vous pouvez également commencer avec une configuration prédéfinie et la modifier en fonction des besoins de votre projet. Pour plus d’informations sur les définitions de conteneurs de développement prédéfinis, consultez le dépôt [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src).
|
||||
Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository.
|
||||
|
||||
Vous pouvez ajouter une configuration de conteneur de développement prédéfinie lorsque vous travaillez dans un codespace ou localement sur un dépôt. Pour y parvenir dans {% data variables.product.prodname_vscode_shortname %} quand vous travaillez localement et que vous n’êtes pas connecté à un codespace, l’extension l’extension « Conteneurs de développement » doit être installée et activée. Pour plus d’informations sur cette extension, consultez la [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). La procédure suivante décrit le processus quand vous utilisez un codespace. Les étapes décrites dans {% data variables.product.prodname_vscode_shortname %} quand vous n’êtes pas connecté à un codespace sont très similaires.
|
||||
You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar.
|
||||
|
||||
{% data reusables.codespaces.command-palette-container %}
|
||||
1. Cliquez sur la définition que vous souhaitez utiliser.
|
||||
1. Click the definition you want to use.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Suivez les invites pour personnaliser votre définition. Pour plus d’informations sur les options permettant de personnaliser votre définition, consultez « [Ajout de fonctionnalités à votre fichier `devcontainer.json`](#adding-additional-features-to-your-devcontainerjson-file) ».
|
||||
1. Cliquez sur **OK**.
|
||||
1. Follow the prompts to customize your definition. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)."
|
||||
1. Click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Si vous travaillez dans un codespace, appliquez vos modifications en cliquant sur **Régénérer maintenant** dans le message en bas à droite de la fenêtre. Pour plus d’informations sur la régénération de votre conteneur, consultez « [Application de modifications à votre configuration](#applying-configuration-changes-to-a-codespace) ».
|
||||
1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)."
|
||||
|
||||
|
||||
|
||||
|
||||
### Ajout de fonctionnalités à votre fichier `devcontainer.json`
|
||||
### Adding additional features to your `devcontainer.json` file
|
||||
|
||||
{% data reusables.codespaces.about-features %} Pour plus d’informations, consultez « [Ajout de fonctionnalités à un fichier `devcontainer.json`](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode) ».
|
||||
{% data reusables.codespaces.about-features %} For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)."
|
||||
|
||||
## Création d’une configuration de conteneur de développement personnalisée
|
||||
## Creating a custom dev container configuration
|
||||
|
||||
Si aucune des configurations prédéfinies ne répond à vos besoins, vous pouvez créer une configuration personnalisée en écrivant votre propre fichier `devcontainer.json`.
|
||||
If none of the predefined configurations meets your needs, you can create a custom configuration by writing your own `devcontainer.json` file.
|
||||
|
||||
* Si vous ajoutez un seul fichier `devcontainer.json` qui sera utilisé par toute personne créant un codespace à partir de votre dépôt, créez le fichier dans un répertoire `.devcontainer` à la racine du dépôt.
|
||||
* Si vous souhaitez offrir aux utilisateurs un choix de configuration, vous pouvez créer plusieurs fichiers `devcontainer.json` personnalisés, chacun situé dans un sous-répertoire distinct du répertoire `.devcontainer`.
|
||||
* If you're adding a single `devcontainer.json` file that will be used by everyone who creates a codespace from your repository, create the file within a `.devcontainer` directory at the root of the repository.
|
||||
* If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Remarques**:
|
||||
- Vous ne pouvez pas placer vos fichiers `devcontainer.json` dans des répertoires situés plusieurs niveaux en dessous de `.devcontainer`. Par exemple, un fichier à l’emplacement `.devcontainer/teamA/devcontainer.json` fonctionnera, mais pas `.devcontainer/teamA/testing/devcontainer.json`.
|
||||
- {% data reusables.codespaces.configuration-choice-templates %} Pour plus d’informations, consultez « [Configuration d’un dépôt modèle pour {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces) ».
|
||||
**Notes**:
|
||||
- You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not.
|
||||
- {% data reusables.codespaces.configuration-choice-templates %} For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Si plusieurs fichiers `devcontainer.json` se trouvent dans le dépôt, ils sont répertoriés dans la page des options de création de codespace. Pour plus d’informations, consultez « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository) ».
|
||||
If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
|
||||
|
||||
|
||||
|
||||
### Ajout d’un fichier `devcontainer.json`
|
||||
### Adding a `devcontainer.json` file
|
||||
|
||||
Si vous n’avez pas encore de fichier `devcontainer.json` dans votre dépôt, vous pouvez rapidement en ajouter un à partir de {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. Accédez à votre dépôt et cliquez sur la liste déroulante **{% octicon "code" aria-label="The code icon" %} Code**.
|
||||
1. Sous l’onglet **Codespaces**, cliquez sur les points de suspension ( **...** ), puis sélectionnez **Configurer le conteneur de développement**.
|
||||
If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown.
|
||||
1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**.
|
||||
|
||||
|
||||
|
||||
|
||||
Un nouveau fichier `.devcontainer/devcontainer.json` s’ouvre dans l’éditeur. Le fichier contient certaines propriétés initiales, notamment un objet `features` auquel vous pouvez ajouter de nouveaux outils, bibliothèques ou runtimes. Pour plus d’informations, consultez « [Ajout de fonctionnalités à un fichier `devcontainer.json`](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui) ».
|
||||
A new `.devcontainer/devcontainer.json` file will open in the editor. The file will contain some initial properties, including a `features` object to which you can add new tools, libraries, or runtimes. For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)."
|
||||
|
||||
Si votre dépôt contient déjà un ou plusieurs fichiers `devcontainer.json`, cliquez sur **Configurer le conteneur de développement** pour ouvrir le fichier `devcontainer.json` existant avec la priorité la plus élevée en fonction de la [spécification](https://containers.dev/implementors/spec/#devcontainerjson) sur containers.dev.
|
||||
If your repository already contains one or more `devcontainer.json` files, then clicking **Configure dev container** will open the existing `devcontainer.json` file with the highest precedence according to the [specification](https://containers.dev/implementors/spec/#devcontainerjson) on containers.dev.
|
||||
|
||||
### Sélection de configuration par défaut lors de la création d’un codespace
|
||||
### Default configuration selection during codespace creation
|
||||
|
||||
Si les fichiers `.devcontainer/devcontainer.json` ou `.devcontainer.json` existent, il s’agit de la sélection par défaut dans la liste des fichiers de configuration disponibles lorsque vous créez un codespace. Si aucun des fichiers n’existe, la configuration du conteneur de développement par défaut est sélectionnée par défaut.
|
||||
If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be the default selection in the list of available configuration files when you create a codespace. If neither file exists, the default dev container configuration will be selected by default.
|
||||
|
||||
|
||||
|
||||
|
||||
### Édition du fichier devcontainer.json
|
||||
### Editing the devcontainer.json file
|
||||
|
||||
Vous pouvez ajouter et modifier les clés de configuration prises en charge dans le fichier `devcontainer.json` pour spécifier des aspects de l’environnement du codespace, comme les extensions {% data variables.product.prodname_vscode_shortname %} qui seront installées. {% data reusables.codespaces.more-info-devcontainer %}
|
||||
You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %}
|
||||
|
||||
Le fichier `devcontainer.json` est écrit au format JSONC (JSON avec commentaires). Cela vous permet d’inclure des commentaires dans le fichier de configuration. Pour plus d’informations, consultez « [Édition de JSON avec {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments) » dans la documentation {% data variables.product.prodname_vscode_shortname %}.
|
||||
The `devcontainer.json` file is written using the JSONC (JSON with comments) format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Remarque** : si vous utilisez un linter pour valider le fichier `devcontainer.json`, assurez-vous que celui-ci est défini sur JSONC, non JSON, sans quoi les commentaires seront signalés comme des erreurs.
|
||||
**Note**: If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Paramètres d’interface pour {% data variables.product.prodname_vscode_shortname %}
|
||||
### Interface settings for {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
Vous pouvez configurer les paramètres d’interface pour {% data variables.product.prodname_vscode_shortname %} avec trois étendues : Espace de travail, [Codespaces] distants et Utilisateur. Vous pouvez afficher ces étendues dans l’éditeur Paramètres de {% data variables.product.prodname_vscode_shortname %}.
|
||||
You can configure the interface settings for {% data variables.product.prodname_vscode_shortname %}, with three scopes: Workspace, Remote [Codespaces], and User. You can view these scopes in the {% data variables.product.prodname_vscode_shortname %} Settings editor.
|
||||
|
||||
|
||||
|
||||
|
||||
Si un paramètre est défini dans plusieurs étendues, les paramètres de l’étendue Espace de travail sont prioritaires, suivis de ceux de l’étendue [Codespaces] distants et de ceux de l’étendue Utilisateur.
|
||||
If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User.
|
||||
|
||||
Vous pouvez définir des paramètres d’interface par défaut pour {% data variables.product.prodname_vscode_shortname %} à deux endroits.
|
||||
You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places.
|
||||
|
||||
* Les paramètres d’interface définis dans le fichier `.vscode/settings.json` dans votre dépôt sont appliqués en tant que paramètres délimités à l’espace de travail dans le codespace.
|
||||
* Les paramètres d’interface définis dans la clé `settings` dans le fichier `devcontainer.json` sont appliqués en tant que paramètres délimités à [Codespaces] distants dans le codespace.
|
||||
* Interface settings defined in the `.vscode/settings.json` file in your repository are applied as Workspace-scoped settings in the codespace.
|
||||
* Interface settings defined in the `settings` key in the `devcontainer.json` file are applied as Remote [Codespaces]-scoped settings in the codespace.
|
||||
|
||||
## Application de modifications de configuration à un codespace
|
||||
## Applying configuration changes to a codespace
|
||||
|
||||
Les modifications apportées à une configuration seront appliquées la prochaine fois que vous créerez un codespace. Toutefois, si vous utilisez un codespace dans un navigateur web, dans {% data variables.product.prodname_vscode_shortname %} ou dans un IDE JetBrains, vous pouvez appliquer des modifications de configuration à l’espace de code actuel en regénérant le conteneur.
|
||||
Changes to a configuration will be applied the next time you create a codespace. However, you can apply your changes to an existing codespace by rebuilding the container. You can do this within a codespace in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application, or you can use {% data variables.product.prodname_cli %}.
|
||||
|
||||
### Regénération du conteneur de développement dans le client web ou l’application de bureau {% data variables.product.prodname_vscode_shortname %}
|
||||
### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application
|
||||
|
||||
{% data reusables.codespaces.rebuild-command %}
|
||||
1. {% data reusables.codespaces.recovery-mode %}
|
||||
|
||||
|
||||
|
||||
|
||||
- Pour diagnostiquer l’erreur en révisant les journaux de création, cliquez sur **Afficher le journal de création**.
|
||||
- Pour corriger les erreurs identifiées dans les journaux, mettez à jour votre fichier `devcontainer.json`.
|
||||
- Pour appliquer les modifications, régénérez votre conteneur.
|
||||
- To diagnose the error by reviewing the creation logs, click **View creation log**.
|
||||
- To fix the errors identified in the logs, update your `devcontainer.json` file.
|
||||
- To apply the changes, rebuild your container.
|
||||
|
||||
### Regénération du conteneur de développement dans un IDE JetBrains
|
||||
### Using {% data variables.product.prodname_cli %} to rebuild a dev container
|
||||
|
||||
{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
|
||||
1. Dans la fenêtre d’outils {% data variables.product.prodname_github_codespaces %}, cliquez sur l’icône de regénération.
|
||||
If you've changed a dev container configuration outside of VS Code (for example, on {% data variables.product.prodname_dotcom_the_website %} or in a JetBrains IDE), you can use {% data variables.product.prodname_cli %} to rebuild the dev container for an existing codespace.
|
||||
|
||||
|
||||
1. In a terminal, enter the following command.
|
||||
|
||||
1. Cliquez sur **Regénérer** quand vous êtes invité à confirmer que vous souhaitez regénérer le conteneur de développement.
|
||||
1. Rouvrez le codespace dans votre IDE JetBrains.
|
||||
```
|
||||
gh cs rebuild
|
||||
```
|
||||
|
||||
Your codespaces are listed.
|
||||
|
||||
1. Use the arrow keys on your keyboard to highlight the required codespace, then press <kbd>Enter</kbd>.
|
||||
|
||||
|
||||
## Pour aller plus loin
|
||||
## Further reading
|
||||
|
||||
- « [Pré-génération de vos codespaces](/codespaces/prebuilding-your-codespaces) »
|
||||
- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)"
|
||||
|
||||
@@ -1,123 +1,123 @@
|
||||
---
|
||||
title: Bien démarrer avec GitHub Copilot dans un IDE JetBrains
|
||||
title: Getting started with GitHub Copilot in a JetBrains IDE
|
||||
shortTitle: JetBrains IDE
|
||||
intro: 'Découvrez comment installer {% data variables.product.prodname_copilot %} dans un IDE JetBrains, et commencez à voir des suggestions lorsque vous écrivez des commentaires et du code.'
|
||||
intro: 'Learn how to install {% data variables.product.prodname_copilot %} in a JetBrains IDE, and start seeing suggestions as you write comments and code.'
|
||||
product: '{% data reusables.gated-features.copilot %}'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
ms.openlocfilehash: 24415504e0abeff6e129321068b07590d265da16
|
||||
ms.sourcegitcommit: 99eb4456062aea31ca381977396417cf92e5798d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179595'
|
||||
---
|
||||
## À propos de {% data variables.product.prodname_copilot %} et des IDE JetBrains
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and JetBrains IDEs
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
Si vous utilisez un IDE JetBrains, vous pouvez visualiser et intégrer les suggestions de {% data variables.product.prodname_copilot %} directement dans l’éditeur. Ce guide montre comment utiliser {% data variables.product.prodname_copilot %} dans un IDE JetBrains pour macOS, Windows ou Linux.
|
||||
If you use a JetBrains IDE, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within a JetBrains IDE for macOS, Windows, or Linux.
|
||||
|
||||
## Prérequis
|
||||
## Prerequisites
|
||||
|
||||
{% data reusables.copilot.jetbrains-ides %}
|
||||
|
||||
## Installation de l’extension {% data variables.product.prodname_copilot %} dans votre IDE JetBrains
|
||||
## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE
|
||||
|
||||
Pour utiliser {% data variables.product.prodname_copilot %} dans un IDE JetBrains, vous devez installer l’extension {% data variables.product.prodname_copilot %}. La procédure suivante vous guide tout au long de l’installation du plug-in {% data variables.product.prodname_copilot %} dans IntelliJ IDEA. Les étapes d’installation du plug-in peuvent différer dans les autres IDE pris en charge.
|
||||
To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} extension. The following procedure will guide you through installation of the {% data variables.product.prodname_copilot %} plugin in IntelliJ IDEA. Steps to install the plugin in another supported IDE may differ.
|
||||
|
||||
1. Dans votre IDE JetBrains, sous le menu **Fichier** pour Windows, ou sous le nom de votre IDE pour Mac (par exemple **, PyCharm** ou **IntelliJ**), cliquez sur **Paramètres** pour Windows ou **Préférences** pour Mac.
|
||||
2. Dans le menu de gauche de la boîte de dialogue **Paramètres/Préférences**, cliquez sur **Plug-ins**.
|
||||
3. En haut de la boîte de dialogue **Paramètres/Préférences**, cliquez sur **Marketplace**. Dans la barre de recherche, recherchez **{% data variables.product.prodname_copilot %}** , puis cliquez sur **Installer**.
|
||||
|
||||
1. Une fois {% data variables.product.prodname_copilot %} installé, cliquez sur **Redémarrer l’IDE**.
|
||||
1. Une fois votre IDE JetBrains redémarré, cliquez sur le menu **Outils**. Cliquez sur **{% data variables.product.prodname_copilot %}** , puis cliquez sur **Se connecter à {% data variables.product.prodname_dotcom %}** .
|
||||
|
||||
1. Dans la boîte de dialogue « Se connecter à {% data variables.product.prodname_dotcom %} », pour copier le code de l’appareil et ouvrir la fenêtre d’activation de l’appareil, cliquez sur **Copier et ouvrir**.
|
||||
|
||||
1. Une fenêtre d’activation d’appareil s’ouvrira dans votre navigateur. Collez le code de l’appareil, puis cliquez sur **Continuer**.
|
||||
1. In your JetBrains IDE, under the **File** menu for Windows or under the name of your IDE for Mac (for example, **PyCharm** or **IntelliJ**), click **Settings** for Windows or **Preferences** for Mac.
|
||||
2. In the left-side menu of the **Settings/Preferences** dialog box, click **Plugins**.
|
||||
3. At the top of the **Settings/Preferences** dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}**, then click **Install**.
|
||||
|
||||
1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**.
|
||||
1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**.
|
||||
|
||||
1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**.
|
||||
|
||||
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
|
||||
|
||||
- Pour coller le code sur un système Windows ou Linux, appuyez sur <kbd>Ctrl</kbd>+<kbd>v</kbd>.
|
||||
- Pour coller le code sur un système macOS, appuyez sur <kbd>commande</kbd>+<kbd>v</kbd>.
|
||||
1. {% data variables.product.prodname_dotcom %} demandera les autorisations nécessaires pour {% data variables.product.prodname_copilot %}. Pour approuver ces autorisations, cliquez sur **Autoriser le plug-in {% data variables.product.prodname_copilot %}** .
|
||||
1. Une fois les autorisations approuvées, votre IDE JetBrains affichera une confirmation. Pour commencer à utiliser {% data variables.product.prodname_copilot %}, cliquez sur **OK**.
|
||||
|
||||
- To paste the code in Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>v</kbd>.
|
||||
- To paste the code in macOS, press <kbd>command</kbd>+<kbd>v</kbd>.
|
||||
1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
|
||||
1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**.
|
||||
|
||||
|
||||
|
||||
## Voir votre première suggestion
|
||||
## Seeing your first suggestion
|
||||
|
||||
{% data reusables.copilot.code-examples-limitations %}
|
||||
|
||||
{% data reusables.copilot.supported-languages %} Les exemples suivants sont en Java. Cependant, d’autres langages ont un fonctionnement similaire.
|
||||
{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly.
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Dans le fichier Java, créez une classe en tapant `class Test`.
|
||||
{% data variables.product.prodname_copilot %} suggère automatiquement un corps de classe en texte grisé, comme indiqué ci-dessous. La suggestion exacte peut varier.
|
||||
 {% data reusables.copilot.accept-suggestion %}
|
||||
1. Pour inviter {% data variables.product.prodname_copilot %} à suggérer un corps de fonction, tapez la ligne suivante sous le crochet de la fonction `main`. La suggestion exacte peut varier.
|
||||
1. In the Java file, create a class by typing `class Test`.
|
||||
{% data variables.product.prodname_copilot %} will automatically suggest a class body in grayed text, as shown below. The exact suggestion may vary.
|
||||
|
||||
{% data reusables.copilot.accept-suggestion %}
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to suggest a function body, type the following line below the bracket of the `main` function. The exact suggestion may vary.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
|
||||
|
||||
 {% data reusables.copilot.accept-suggestion %}
|
||||
|
||||
{% data reusables.copilot.accept-suggestion %}
|
||||
|
||||
{% data variables.product.prodname_copilot %} tentera de correspondre au contexte et au style de votre code. Vous pouvez toujours modifier le code suggéré.
|
||||
{% data variables.product.prodname_copilot %} will attempt to match the context and style of your code. You can always edit the suggested code.
|
||||
|
||||
## Voir d’autres suggestions
|
||||
## Seeing alternative suggestions
|
||||
|
||||
{% data reusables.copilot.alternative-suggestions %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Pour inviter {% data variables.product.prodname_copilot %} à afficher une suggestion, tapez la ligne suivante dans le fichier Java.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} {% data reusables.copilot.see-alternative-suggestions %}
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
|
||||
{% data reusables.copilot.see-alternative-suggestions %}
|
||||
|
||||
| Système d''exploitation | Voir la suggestion suivante | Voir la suggestion précédente |
|
||||
| OS | See next suggestion | See previous suggestion |
|
||||
| :- | :- | :- |
|
||||
| macOS | <kbd>Option</kbd>+<kbd>]</kbd> | <kbd>Option</kbd>+<kbd>[</kbd> |
|
||||
| Windows | <kbd>Alt</kbd>+<kbd>]</kbd> | <kbd>Alt</kbd>+<kbd>[</kbd> |
|
||||
| Linux | <kbd>Alt</kbd>+<kbd>]</kbd> | <kbd>Alt</kbd>+<kbd>[</kbd> |
|
||||
{% data reusables.copilot.accept-or-reject-suggestion %}
|
||||
|
||||
## Affichage de plusieurs suggestions sous un nouvel onglet
|
||||
## Seeing multiple suggestions in a new tab
|
||||
|
||||
{% data reusables.copilot.suggestions-new-tab %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Pour inviter {% data variables.product.prodname_copilot %} à afficher une suggestion, tapez la ligne suivante dans le fichier Java.
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
|
||||
1. Ouvrez un nouvel onglet avec plusieurs suggestions supplémentaires.
|
||||
- Sur macOS, appuyez sur <kbd>Commande</kbd>+<kbd>Maj</kbd>+<kbd>A</kbd>, puis cliquez sur **Ouvrir GitHub Copilot**, ou appuyez sur <kbd>Commande</kbd>+<kbd>Maj</kbd>+<kbd>\</kbd> pour ouvrir immédiatement le nouvel onglet.
|
||||
- Sur Windows ou Linux, appuyez sur <kbd>Ctrl</kbd>+<kbd>Entrée</kbd>, puis cliquez sur **Ouvrir GitHub Copilot**.
|
||||
|
||||
1. Pour accepter une suggestion, au-dessus de celle-ci, cliquez sur **Accepter la solution**. Pour rejeter toutes les suggestions, fermez l’onglet.
|
||||
1. Open a new tab with multiple additional suggestions.
|
||||
- On macOS, press <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>A</kbd>, then click **Open GitHub Copilot**, or press <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> to open the new tab immediately.
|
||||
- On Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>Enter</kbd>, then click **Open GitHub Copilot**.
|
||||
|
||||
1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab.
|
||||
|
||||
## Génération de suggestions de code à partir de commentaires
|
||||
## Generating code suggestions from comments
|
||||
|
||||
{% data reusables.copilot.generating-suggestions-from-comments %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Pour inviter {% data variables.product.prodname_copilot %} à suggérer une implémentation d’une fonction dans le fichier Java, tapez les lignes suivantes.
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to suggest an implementation of a function in the Java file, type the following lines.
|
||||
```java{:copy}
|
||||
// find all images without alternate text
|
||||
// and give them a red border
|
||||
void process () {
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Activation et désactivation de {% data variables.product.prodname_copilot %}
|
||||
## Enabling and disabling {% data variables.product.prodname_copilot %}
|
||||
|
||||
Vous pouvez activer ou désactiver {% data variables.product.prodname_copilot %} pour tous les langages ou seulement certains langages. L’icône d’état {% data variables.product.prodname_copilot %} dans le panneau inférieur de la fenêtre de l’IDE JetBrains indique si {% data variables.product.prodname_copilot %} est activé ou désactivé. Quand cette option est activée, l’icône est mise en évidence. Quand elle est désactivée, l’icône est grisée.
|
||||
You can enable or disable {% data variables.product.prodname_copilot %} for all languages, or for individual languages. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of your JetBrains IDE window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out.
|
||||
|
||||
1. Pour activer ou désactiver {% data variables.product.prodname_copilot %}, cliquez sur l’icône d’état dans le panneau inférieur de la fenêtre JetBrains.
|
||||
|
||||
2. Si vous désactivez {% data variables.product.prodname_copilot %}, il vous sera demandé si vous souhaitez le désactiver entièrement ou seulement pour le langage du fichier que vous êtes en train de modifier.
|
||||
1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window.
|
||||
|
||||
2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable it globally, or for the language of the file you are currently editing.
|
||||
|
||||
- Pour désactiver les suggestions de {% data variables.product.prodname_copilot %} globalement, cliquez sur **Désactiver les saisies semi-automatiques**.
|
||||
- Pour désactiver les suggestions de {% data variables.product.prodname_copilot %} pour le langage spécifié, cliquez sur **Désactiver les saisies semi-automatiques pour _LANGAGE_**.
|
||||
|
||||
- To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Completions**.
|
||||
- To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable Completions for _LANGUAGE_**.
|
||||
|
||||
|
||||
|
||||
## Pour aller plus loin
|
||||
## Further reading
|
||||
|
||||
- [Site web de {% data variables.product.prodname_copilot %}](https://copilot.github.com/)
|
||||
- [À propos de {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides)
|
||||
- [The {% data variables.product.prodname_copilot %} website](https://copilot.github.com/)
|
||||
- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides)
|
||||
|
||||
@@ -9,6 +9,8 @@ topics:
|
||||
- Copilot
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and Neovim
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
@@ -9,6 +9,8 @@ topics:
|
||||
- Copilot
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
@@ -9,6 +9,8 @@ topics:
|
||||
- Copilot
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and Visual Studio
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
@@ -36,7 +36,7 @@ The `git remote add` command takes two arguments:
|
||||
For example:
|
||||
|
||||
```shell
|
||||
$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO>.git
|
||||
$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO.git
|
||||
# Set a new remote
|
||||
|
||||
$ git remote -v
|
||||
|
||||
@@ -70,9 +70,9 @@ After you set up your trial, you can explore {% data variables.product.prodname_
|
||||
|
||||
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.
|
||||
|
||||
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 %}.
|
||||
If you don't purchase {% data variables.product.prodname_enterprise %}, the trial will continue until the end of the 30-day period. You cannot end the trial early. 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 %}.
|
||||
|
||||
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)."
|
||||
Your organization will lose access to any functionality that is not included in the new plan, 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)."
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -142,7 +142,7 @@ externalProducts:
|
||||
electron:
|
||||
id: electron
|
||||
name: Electron
|
||||
href: 'https://electronjs.org/docs'
|
||||
href: 'https://electronjs.org/docs/latest'
|
||||
external: true
|
||||
codeql:
|
||||
id: codeql
|
||||
@@ -154,11 +154,11 @@ externalProducts:
|
||||
name: npm
|
||||
href: 'https://docs.npmjs.com/'
|
||||
external: true
|
||||
ms.openlocfilehash: dad74fe11fc5bfea72ae994e9918683fc7e87b7a
|
||||
ms.sourcegitcommit: bd23217796e6ff442b14ef9d889eaef30e8d6826
|
||||
ms.openlocfilehash: e72ace58cb674661cbde635f97cf7ff0ab70433a
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/16/2022
|
||||
ms.locfileid: '148167303'
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148183971'
|
||||
---
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ You can restrict access to private organization assets by configuring an allow l
|
||||
|
||||
If you set up an allow list you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)."
|
||||
|
||||
You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
|
||||
You can also configure allowed IP addresses at the enterprise account level, and the entries in the enterprise account's allow list are inherited by all the organizations owned by the enterprise. {% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
|
||||
|
||||
## Adding an allowed IP address
|
||||
|
||||
|
||||
@@ -24,6 +24,8 @@ If you enable but don't enforce SAML SSO, organization members who choose not to
|
||||
|
||||
{% data reusables.saml.saml-disabled-linked-identities-removed %}
|
||||
|
||||
{% data reusables.apps.reauthorize-apps-saml %}
|
||||
|
||||
## Enabling and testing SAML single sign-on for your organization
|
||||
|
||||
Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Démarrage rapide pour les packages GitHub
|
||||
intro: 'Publiez sur {% data variables.product.prodname_registry %} avec {% data variables.product.prodname_actions %}.'
|
||||
title: Quickstart for GitHub Packages
|
||||
intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -8,53 +8,48 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Quickstart
|
||||
ms.openlocfilehash: 207b91e821037a6eb61ae7bc9b18c98d8b14fdd2
|
||||
ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '147877110'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Introduction
|
||||
|
||||
Dans ce guide, vous allez créer un workflow {% data variables.product.prodname_actions %} pour tester votre code, puis publiez-le sur {% data variables.product.prodname_registry %}.
|
||||
In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}.
|
||||
|
||||
## Publication de votre package
|
||||
## Publishing your package
|
||||
|
||||
1. Créez un nouveau référentiel sur {% data variables.product.prodname_dotcom %}, en ajoutant le nœud `.gitignore`. Pour plus d’informations, consultez « [Création d’un dépôt](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository) ».
|
||||
2. Clonez le référentiel sur votre ordinateur local.
|
||||
1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
|
||||
2. Clone the repository to your local machine.
|
||||
```shell
|
||||
$ git clone https://{% ifversion ghes or ghae %}<em>YOUR-HOSTNAME</em>{% else %}github.com{% endif %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
|
||||
$ cd <em>YOUR-REPOSITORY</em>
|
||||
$ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
$ cd YOUR-REPOSITORY
|
||||
```
|
||||
3. Créez un fichier `index.js` et ajoutez une alerte de base pour dire « Bonjour le monde ! »
|
||||
3. Create an `index.js` file and add a basic alert to say "Hello world!"
|
||||
{% raw %}
|
||||
```javascript{:copy}
|
||||
console.log("Hello, World!");
|
||||
```
|
||||
{% endraw %}
|
||||
4. Initialisez un package npm avec `npm init`. Dans l’Assistant Initialisation du package, entrez votre package avec le nom : _`@YOUR-USERNAME/YOUR-REPOSITORY`_ et définissez le script de test sur `exit 0`. Cela génère un fichier `package.json` contenant des informations sur votre package.
|
||||
4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package.
|
||||
{% raw %}
|
||||
```shell
|
||||
$ npm init
|
||||
...
|
||||
package name: <em>@YOUR-USERNAME/YOUR-REPOSITORY</em>
|
||||
package name: @YOUR-USERNAME/YOUR-REPOSITORY
|
||||
...
|
||||
test command: <em>exit 0</em>
|
||||
test command: exit 0
|
||||
...
|
||||
```
|
||||
{% endraw %}
|
||||
5. Exécutez `npm install` pour générer le fichier `package-lock.json`, puis validez et envoyez (push) vos modifications à {% data variables.product.prodname_dotcom %}.
|
||||
5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
|
||||
```shell
|
||||
$ npm install
|
||||
$ git add index.js package.json package-lock.json
|
||||
$ git commit -m "initialize npm package"
|
||||
$ git push
|
||||
```
|
||||
6. Créez un répertoire `.github/workflows`. Dans ce répertoire, créez un fichier nommé `release-package.yml`.
|
||||
7. Copiez le contenu YAML suivant dans le fichier `release-package.yml`{% ifversion ghes or ghae %}, en remplaçant `YOUR-HOSTNAME` par le nom de votre entreprise{% endif %}.
|
||||
6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`.
|
||||
7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghes or ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}.
|
||||
```yaml{:copy}
|
||||
name: Node.js Package
|
||||
|
||||
@@ -69,7 +64,7 @@ Dans ce guide, vous allez créer un workflow {% data variables.product.prodname_
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: 12
|
||||
node-version: 16
|
||||
- run: npm ci
|
||||
- run: npm test
|
||||
|
||||
@@ -83,54 +78,58 @@ Dans ce guide, vous allez créer un workflow {% data variables.product.prodname_
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: 12
|
||||
node-version: 16
|
||||
registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %}
|
||||
- run: npm ci
|
||||
- run: npm publish
|
||||
env:
|
||||
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
|
||||
```
|
||||
8. Indiquez à NPM l’étendue et le Registre pour publier des packages à l’aide de l’une des méthodes suivantes :
|
||||
- Ajoutez un fichier de configuration NPM pour le référentiel en créant un fichier `.npmrc` dans le répertoire racine avec le contenu : {% raw %}
|
||||
8. Tell NPM which scope and registry to publish packages to using one of the following methods:
|
||||
- Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
|
||||
{% raw %}
|
||||
```shell
|
||||
<em>@YOUR-USERNAME</em>:registry=https://npm.pkg.github.com
|
||||
@YOUR-USERNAME:registry=https://npm.pkg.github.com
|
||||
```
|
||||
{% endraw %}
|
||||
- Modifiez le fichier `package.json` et spécifiez la clé `publishConfig` : {% raw %}
|
||||
- Edit the `package.json` file and specify the `publishConfig` key:
|
||||
{% raw %}
|
||||
```shell
|
||||
"publishConfig": {
|
||||
"@<em>YOUR-USERNAME</em>:registry": "https://npm.pkg.github.com"
|
||||
}
|
||||
```
|
||||
{% endraw %}
|
||||
9. Validez et envoyez (push) vos modifications à {% data variables.product.prodname_dotcom %}.
|
||||
9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
|
||||
```shell
|
||||
$ git add .github/workflows/release-package.yml
|
||||
# Also add the file you created or edited in the previous step.
|
||||
$ git add <em>.npmrc or package.json</em>
|
||||
$ git add .npmrc or package.json
|
||||
$ git commit -m "workflow to publish package"
|
||||
$ git push
|
||||
```
|
||||
10. Le workflow que vous avez créé s’exécute chaque fois qu’une nouvelle version est créée dans votre référentiel. Si les tests réussissent, le package est publié sur {% data variables.product.prodname_registry %}.
|
||||
10. The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}.
|
||||
|
||||
Pour le tester, accédez à l’onglet **Coder** de votre référentiel et créez une version. Pour plus d’informations, consultez « [Gestion des versions dans un référentiel](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release) ».
|
||||
To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)."
|
||||
|
||||
## Affichage de votre package publié
|
||||
## Viewing your published package
|
||||
|
||||
Vous pouvez afficher tous les packages que vous avez publiés.
|
||||
You can view all of the packages you have published.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.package_registry.packages-from-code-tab %}
|
||||
{% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## Utilisation d’un package publié
|
||||
## Installing a published package
|
||||
|
||||
Maintenant que vous avez publié le package, vous souhaiterez l’utiliser comme dépendance entre vos projets. Pour plus d’informations, consultez « [Utilisation du registre npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package). »
|
||||
Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
|
||||
|
||||
## Étapes suivantes
|
||||
## Next steps
|
||||
|
||||
Le workflow de base que vous venez d’ajouter s’exécute chaque fois qu’une nouvelle version est créée dans votre référentiel. Mais ce n’est que le début de ce que vous pouvez faire avec {% data variables.product.prodname_registry %}. Vous pouvez publier votre package sur plusieurs registres avec un seul workflow, déclencher l’exécution du workflow sur différents événements tels qu’une demande de tirage fusionnée, gérer des conteneurs, etc.
|
||||
The basic workflow you just added runs any time a new release is created in your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
|
||||
|
||||
La combinaison de {% data variables.product.prodname_registry %} et de {% data variables.product.prodname_actions %} peut vous aider à automatiser presque tous les aspects de vos processus de développement d’applications. Vous êtes prêt à commencer ? Voici quelques ressources utiles pour effectuer vos étapes suivantes avec {% data variables.product.prodname_registry %} et {% data variables.product.prodname_actions %} :
|
||||
Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}:
|
||||
|
||||
- « [Découvrir {% data variables.product.prodname_registry %}](/packages/learn-github-packages) » pour obtenir un tutoriel approfondi sur les packages GitHub
|
||||
- « [Découvrir {% data variables.product.prodname_actions %}](/actions/learn-github-actions) » pour obtenir un tutoriel approfondi sur GitHub Actions
|
||||
- « [Utilisation d’un registre {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry) » pour découvrir des cas d’utilisation et des exemples spécifiques
|
||||
- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions
|
||||
- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
|
||||
|
||||
@@ -9,12 +9,12 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: c51d9275950bbf303caa1a03344ba8402618d65b
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 47961c5dfeeb5f320bbac67ffb0573c31709bd5b
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145131444'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181301'
|
||||
---
|
||||
## À propos de l’API Gists
|
||||
|
||||
@@ -38,7 +38,7 @@ Outre le contenu d’un fichier spécifique tronqué, la liste entière des fich
|
||||
|
||||
Il s’agit des types de médias pris en charge pour extraire le contenu d’un gist.
|
||||
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.VERSION.base64
|
||||
application/vnd.github.raw
|
||||
application/vnd.github.base64
|
||||
|
||||
Pour plus d’informations, consultez « [Types de médias](/rest/overview/media-types) ».
|
||||
|
||||
@@ -11,22 +11,22 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: e815b7d7ea3d63ced4c486605891a10dcb870176
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 3b7cac6d268fb4c7e786651a7281ca5ce4241ec5
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147060617'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181244'
|
||||
---
|
||||
## À propos de l’API Git blobs
|
||||
|
||||
Un blob (binary large object) Git est le type d’objet utilisé pour stocker le contenu de chaque fichier dans un dépôt. Le hachage SHA-1 du fichier est calculé et stocké dans l’objet blob. Ces points de terminaison vous permettent de lire et d’écrire des [objets blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) dans votre base de données Git sur {% data variables.product.product_name %}. Les blobs tirent parti de [ces types de médias personnalisés](#custom-media-types-for-blobs). Plus d’informations sur l’utilisation des types de médias dans l’API sont disponibles [ici](/rest/overview/media-types).
|
||||
Un blob (binary large object) Git est le type d’objet utilisé pour stocker le contenu de chaque fichier dans un dépôt. Le hachage SHA-1 du fichier est calculé et stocké dans l’objet blob. Ces points de terminaison vous permettent de lire et d’écrire des [objets blob](https://git-scm.com/book/en/v2/Git-Internals-Git-Objects) dans votre base de données Git sur {% data variables.product.product_name %}. Les blobs tirent parti de [ces types de médias personnalisés](#custom-media-types-for-blobs). Plus d’informations sur l’utilisation des types de médias dans l’API sont disponibles [ici](/rest/overview/media-types).
|
||||
|
||||
### Types de médias personnalisés pour les blobs
|
||||
|
||||
Il s’agit des types de médias pris en charge pour les blobs.
|
||||
|
||||
application/json
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.raw
|
||||
|
||||
Pour plus d’informations, consultez « [Types de médias](/rest/overview/media-types) ».
|
||||
|
||||
@@ -299,7 +299,7 @@ Most operations specify that you should pass an `Accept` header with a value of
|
||||
To send a header with {% data variables.product.prodname_cli %}, use the `--header` or `-H` flag followed by the header in `key: value` format.
|
||||
|
||||
```shell
|
||||
gh api --header 'Accept: application/vnd.github+json' --method GET /octocat
|
||||
gh api --header 'Accept: application/vnd.github+json'{% ifversion api-date-versioning %} --header 'X-GitHub-Api-Version:{{ allVersions[currentVersion].latestApiVersion }}'{% endif %} --method GET /octocat
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
@@ -311,7 +311,8 @@ The Octokit.js library automatically passes the `Accept: application/vnd.github+
|
||||
```javascript
|
||||
await octokit.request("GET /octocat", {
|
||||
headers: {
|
||||
"content-type": "text/plain",
|
||||
"content-type": "text/plain",{% ifversion api-date-versioning %}
|
||||
"X-GitHub-Api-Version": "{{ allVersions[currentVersion].latestApiVersion }}",{% endif %}
|
||||
},
|
||||
});
|
||||
```
|
||||
@@ -326,7 +327,8 @@ To send a header with cURL, use the `--header` or `-H` flag followed by the head
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/octocat" \
|
||||
--header "Accept: application/vnd.github+json" \
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"{% ifversion api-date-versioning %}\
|
||||
--header "X-GitHub-Api-Version: {{ allVersions[currentVersion].latestApiVersion }}"{% endif %}
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
@@ -12,6 +12,7 @@ featuredLinks:
|
||||
- /rest/guides/best-practices-for-integrators
|
||||
popular:
|
||||
- /rest/overview/resources-in-the-rest-api
|
||||
- /rest/overview/api-versions
|
||||
- /rest/overview/other-authentication-methods
|
||||
- /rest/overview/troubleshooting
|
||||
- /rest/overview/endpoints-available-for-github-apps
|
||||
@@ -78,11 +79,11 @@ children:
|
||||
- /teams
|
||||
- /users
|
||||
- /webhooks
|
||||
ms.openlocfilehash: d4d7e93d5bc22833168a932e047525c85e3f8768
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.openlocfilehash: 393b427325e51b3717e882e430662a6517cba551
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147673637'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184389'
|
||||
---
|
||||
|
||||
|
||||
@@ -4,12 +4,12 @@ intro: 'Votre {% data variables.product.pat_v2 %} peut envoyer des requêtes aux
|
||||
versions:
|
||||
feature: pat-v2
|
||||
shortTitle: '{% data variables.product.pat_v2_caps %}-enabled endpoints'
|
||||
ms.openlocfilehash: 7e6b4506a1af51a3c8da5aa8ee905936025aa952
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: e631edb7b723f516ed50eba6df19ba2f94862e7e
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107236'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184220'
|
||||
---
|
||||
## actions
|
||||
|
||||
@@ -37,28 +37,6 @@ ms.locfileid: '148107236'
|
||||
- [`PUT /enterprises/{enterprise}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#list-self-hosted-runner-groups-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#create-self-hosted-runner-group-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#get-a-self-hosted-runner-group-for-an-enterprise)
|
||||
- [`PATCH /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#delete-a-self-hosted-runner-group-from-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#list-organization-access-to-a-self-hosted-runner-group-in-a-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#set-organization-access-to-a-self-hosted-runner-group-in-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#list-self-hosted-runners-in-a-group-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#add-a-self-hosted-runner-to-a-group-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#delete-self-hosted-runner-from-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-enterprise)
|
||||
- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}`](/rest/reference/actions#get-a-job-for-a-workflow-run)
|
||||
- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run)
|
||||
- [`POST /repos/{owner}/{repo}/actions/jobs/{job_id}/rerun`](/rest/reference/actions#re-run-job-for-workflow-run)
|
||||
@@ -155,18 +133,6 @@ ms.locfileid: '148107236'
|
||||
- [`GET /users/{username}/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user)
|
||||
- [`GET /users/{username}/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user)
|
||||
- [`GET /feeds`](/rest/reference/activity#get-feeds)
|
||||
- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user)
|
||||
- [`PUT /notifications`](/rest/reference/activity#mark-notifications-as-read)
|
||||
- [`GET /notifications/threads/{thread_id}`](/rest/reference/activity#get-a-thread)
|
||||
- [`PATCH /notifications/threads/{thread_id}`](/rest/reference/activity#mark-a-thread-as-read)
|
||||
- [`GET /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#get-a-thread-subscription-for-the-authenticated-user)
|
||||
- [`PUT /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#set-a-thread-subscription)
|
||||
- [`DELETE /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#delete-a-thread-subscription)
|
||||
- [`GET /repos/{owner}/{repo}/notifications`](/rest/reference/activity#list-repository-notifications-for-the-authenticated-user)
|
||||
- [`PUT /repos/{owner}/{repo}/notifications`](/rest/reference/activity#mark-repository-notifications-as-read)
|
||||
- [`GET /repos/{owner}/{repo}/subscription`](/rest/reference/activity#get-a-repository-subscription)
|
||||
- [`PUT /repos/{owner}/{repo}/subscription`](/rest/reference/activity#set-a-repository-subscription)
|
||||
- [`DELETE /repos/{owner}/{repo}/subscription`](/rest/reference/activity#delete-a-repository-subscription)
|
||||
- [`GET /repos/{owner}/{repo}/stargazers`](/rest/reference/activity#list-stargazers)
|
||||
- [`GET /repos/{owner}/{repo}/subscribers`](/rest/reference/activity#list-watchers)
|
||||
- [`GET /users/{username}/starred`](/rest/reference/activity#list-repositories-starred-by-a-user)
|
||||
@@ -179,39 +145,7 @@ ms.locfileid: '148107236'
|
||||
|
||||
## applications
|
||||
|
||||
- [`DELETE /applications/{client_id}/grant`](/rest/reference/apps#delete-an-app-authorization)
|
||||
- [`POST /applications/{client_id}/token`](/rest/reference/apps#check-a-token)
|
||||
- [`PATCH /applications/{client_id}/token`](/rest/reference/apps#reset-a-token)
|
||||
- [`DELETE /applications/{client_id}/token`](/rest/reference/apps#delete-an-app-token)
|
||||
- [`POST /applications/{client_id}/token/scoped`](/rest/reference/apps#create-a-scoped-access-token)
|
||||
- [`GET /installation/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-app-installation)
|
||||
- [`DELETE /installation/token`](/rest/reference/apps#revoke-an-installation-access-token)
|
||||
- [`GET /user/installations/{installation_id}/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
|
||||
- [`PUT /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#add-a-repository-to-an-app-installation)
|
||||
- [`DELETE /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#remove-a-repository-from-an-app-installation)
|
||||
- [`POST /app-manifests/{code}/conversions`](/rest/reference/apps#create-a-github-app-from-a-manifest)
|
||||
- [`GET /app`](/rest/reference/apps#get-the-authenticated-app)
|
||||
- [`GET /app/hook/config`](/rest/reference/apps#get-a-webhook-configuration-for-an-app)
|
||||
- [`PATCH /app/hook/config`](/rest/reference/apps#update-a-webhook-configuration-for-an-app)
|
||||
- [`GET /app/hook/deliveries`](/rest/reference/apps#list-deliveries-for-an-app-webhook)
|
||||
- [`GET /app/hook/deliveries/{delivery_id}`](/rest/reference/apps#get-a-delivery-for-an-app-webhook)
|
||||
- [`POST /app/hook/deliveries/{delivery_id}/attempts`](/rest/reference/apps#redeliver-a-delivery-for-an-app-webhook)
|
||||
- [`GET /app/installations`](/rest/reference/apps#list-installations-for-the-authenticated-app)
|
||||
- [`GET /app/installations/{installation_id}`](/rest/reference/apps#get-an-installation-for-the-authenticated-app)
|
||||
- [`DELETE /app/installations/{installation_id}`](/rest/reference/apps#delete-an-installation-for-the-authenticated-app)
|
||||
- [`POST /app/installations/{installation_id}/access_tokens`](/rest/reference/apps/#create-an-installation-access-token-for-an-app)
|
||||
- [`PUT /app/installations/{installation_id}/suspended`](/rest/reference/apps#suspend-an-app-installation)
|
||||
- [`DELETE /app/installations/{installation_id}/suspended`](/rest/reference/apps#unsuspend-an-app-installation)
|
||||
- [`GET /orgs/{org}/installation`](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app)
|
||||
- [`GET /repos/{owner}/{repo}/installation`](/rest/reference/apps#get-a-repository-installation-for-the-authenticated-app)
|
||||
- [`GET /users/{username}/installation`](/rest/reference/apps#get-a-user-installation-for-the-authenticated-app)
|
||||
- [`GET /marketplace_listing/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account)
|
||||
- [`GET /marketplace_listing/plans`](/rest/reference/apps#list-plans)
|
||||
- [`GET /marketplace_listing/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan)
|
||||
- [`GET /marketplace_listing/stubbed/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account-stubbed)
|
||||
- [`GET /marketplace_listing/stubbed/plans`](/rest/reference/apps#list-plans-stubbed)
|
||||
- [`GET /marketplace_listing/stubbed/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan-stubbed)
|
||||
- [`GET /user/installations`](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
|
||||
- [`GET /user/marketplace_purchases`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
|
||||
- [`GET /user/marketplace_purchases/stubbed`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user-stubbed)
|
||||
|
||||
@@ -225,22 +159,14 @@ ms.locfileid: '148107236'
|
||||
- [`GET /users/{username}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-a-user)
|
||||
- [`GET /users/{username}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-a-user)
|
||||
|
||||
## Vérifications
|
||||
## branches
|
||||
|
||||
- [`POST /repos/{owner}/{repo}/check-runs`](/rest/reference/checks#create-a-check-run)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#get-a-check-run)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#update-a-check-run)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations`](/rest/reference/checks#list-check-run-annotations)
|
||||
- [`POST /repos/{owner}/{repo}/check-runs/{check_run_id}/rerequest`](/rest/reference/checks#rerequest-a-check-run)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites`](/rest/reference/checks#create-a-check-suite)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}`](/rest/reference/checks#get-a-check-suite)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites/{check_suite_id}/rerequest`](/rest/reference/checks#rerequest-a-check-suite)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/branches/branches#list-branches)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/branches/branches#sync-a-fork-branch-with-the-upstream-repository)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/branches/branches#merge-a-branch)
|
||||
|
||||
## code-scanning
|
||||
|
||||
- [`GET /enterprises/{enterprise}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-an-enterprise)
|
||||
- [`GET /orgs/{org}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#get-a-code-scanning-alert)
|
||||
@@ -331,6 +257,7 @@ ms.locfileid: '148107236'
|
||||
- [`PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-a-repository-secret)
|
||||
- [`DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-a-repository-secret)
|
||||
- [`GET /repos/{owner}/{repo}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key)
|
||||
- [`GET /orgs/{org}/dependabot/alerts`](/rest/dependabot/alerts#list-dependabot-alerts-for-an-organization)
|
||||
- [`GET /orgs/{org}/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets)
|
||||
- [`GET /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-an-organization-secret)
|
||||
- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-an-organization-secret)
|
||||
@@ -427,7 +354,7 @@ ms.locfileid: '148107236'
|
||||
- [`GET /repos/{owner}/{repo}/issues`](/rest/reference/issues#list-repository-issues)
|
||||
- [`POST /repos/{owner}/{repo}/issues`](/rest/reference/issues#create-an-issue)
|
||||
- [`GET /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#get-an-issue)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues/#update-an-issue)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#update-an-issue)
|
||||
- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#lock-an-issue)
|
||||
- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#unlock-an-issue)
|
||||
- [`GET /user/issues`](/rest/reference/issues#list-user-account-issues-assigned-to-the-authenticated-user)
|
||||
@@ -474,34 +401,12 @@ ms.locfileid: '148107236'
|
||||
- [`GET /repos/{owner}/{repo}/traffic/popular/referrers`](/rest/metrics/traffic#get-top-referral-sources)
|
||||
- [`GET /repos/{owner}/{repo}/traffic/views`](/rest/metrics/traffic#get-page-views)
|
||||
|
||||
## migrations
|
||||
|
||||
- [`GET /orgs/{org}/migrations`](/rest/reference/migrations#list-organization-migrations)
|
||||
- [`POST /orgs/{org}/migrations`](/rest/reference/migrations#start-an-organization-migration)
|
||||
- [`GET /orgs/{org}/migrations/{migration_id}`](/rest/reference/migrations#get-an-organization-migration-status)
|
||||
- [`GET /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#download-an-organization-migration-archive)
|
||||
- [`DELETE /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-an-organization-migration-archive)
|
||||
- [`GET /orgs/{org}/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-in-an-organization-migration)
|
||||
- [`GET /user/migrations`](/rest/reference/migrations#list-user-migrations)
|
||||
- [`POST /user/migrations`](/rest/reference/migrations#start-a-user-migration)
|
||||
- [`GET /user/migrations/{migration_id}`](/rest/reference/migrations#get-a-user-migration-status)
|
||||
- [`GET /user/migrations/{migration_id}/archive`](/rest/reference/migrations#download-a-user-migration-archive)
|
||||
- [`DELETE /user/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-a-user-migration-archive)
|
||||
- [`GET /user/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-for-a-user-migration)
|
||||
- [`GET /repos/{owner}/{repo}/import`](/rest/reference/migrations#get-an-import-status)
|
||||
- [`PUT /repos/{owner}/{repo}/import`](/rest/reference/migrations#start-an-import)
|
||||
- [`PATCH /repos/{owner}/{repo}/import`](/rest/reference/migrations#update-an-import)
|
||||
- [`DELETE /repos/{owner}/{repo}/import`](/rest/reference/migrations#cancel-an-import)
|
||||
- [`GET /repos/{owner}/{repo}/import/authors`](/rest/reference/migrations#get-commit-authors)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/authors/{author_id}`](/rest/reference/migrations#map-a-commit-author)
|
||||
- [`GET /repos/{owner}/{repo}/import/large_files`](/rest/reference/migrations#get-large-files)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/lfs`](/rest/reference/migrations#update-git-lfs-preference)
|
||||
|
||||
## orgs
|
||||
|
||||
{% ifversion ghec %}
|
||||
- [`GET /orgs/{org}/audit-log`](/rest/reference/orgs#get-audit-log){% endif %}
|
||||
- [`GET /organizations/{organization_id}/custom_roles`](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)
|
||||
- [`GET /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs/#get-a-custom-role)
|
||||
- [`PATCH /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#update-a-custom-role)
|
||||
- [`DELETE /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#delete-a-custom-role)
|
||||
- [`GET /orgs/{org}/fine_grained_permissions`](/rest/reference/orgs#list-fine-grained-permissions-for-an-organization)
|
||||
@@ -539,7 +444,7 @@ ms.locfileid: '148107236'
|
||||
- [`DELETE /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#remove-a-security-manager-team)
|
||||
- [`GET /organizations`](/rest/reference/orgs#list-organizations)
|
||||
- [`GET /orgs/{org}`](/rest/reference/orgs#get-an-organization)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs/#update-an-organization)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs#update-an-organization)
|
||||
- [`GET /orgs/{org}/installations`](/rest/reference/orgs#list-app-installations-for-an-organization)
|
||||
- [`GET /users/{username}/orgs`](/rest/reference/orgs#list-organizations-for-a-user)
|
||||
- [`GET /user/memberships/orgs/{org}`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
|
||||
@@ -551,18 +456,10 @@ ms.locfileid: '148107236'
|
||||
- [`PUT /orgs/{org}/blocks/{username}`](/rest/reference/orgs#block-a-user-from-an-organization)
|
||||
- [`DELETE /orgs/{org}/blocks/{username}`](/rest/reference/orgs#unblock-a-user-from-an-organization)
|
||||
|
||||
## packages
|
||||
|
||||
- [`GET /orgs/{org}/packages`](/rest/reference/packages#list-packages-for-an-organization)
|
||||
- [`GET /users/{username}/packages`](/rest/reference/packages#list-packages-for-user)
|
||||
- [`GET /user/packages`](/rest/reference/packages#list-packages-for-the-authenticated-user)
|
||||
|
||||
## pages
|
||||
|
||||
- [`GET /repos/{owner}/{repo}/pages`](/rest/pages#get-a-github-pages-site)
|
||||
- [`POST /repos/{owner}/{repo}/pages`](/rest/pages#create-a-github-pages-site)
|
||||
- [`PUT /repos/{owner}/{repo}/pages`](/rest/pages#update-information-about-a-github-pages-site)
|
||||
- [`DELETE /repos/{owner}/{repo}/pages`](/rest/pages#delete-a-github-pages-site)
|
||||
- [`GET /repos/{owner}/{repo}/pages/builds`](/rest/pages#list-github-pages-builds)
|
||||
- [`POST /repos/{owner}/{repo}/pages/builds`](/rest/pages#request-a-github-pages-build)
|
||||
- [`GET /repos/{owner}/{repo}/pages/builds/{build_id}`](/rest/pages#get-github-pages-build)
|
||||
@@ -570,34 +467,6 @@ ms.locfileid: '148107236'
|
||||
- [`POST /repos/{owner}/{repo}/pages/deployment`](/rest/pages#create-a-github-pages-deployment)
|
||||
- [`GET /repos/{owner}/{repo}/pages/health`](/rest/pages#get-a-dns-health-check-for-github-pages)
|
||||
|
||||
## projects
|
||||
|
||||
- [`GET /projects/{project_id}/collaborators`](/rest/reference/projects#list-project-collaborators)
|
||||
- [`PUT /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#add-project-collaborator)
|
||||
- [`DELETE /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#remove-project-collaborator)
|
||||
- [`GET /projects/{project_id}/collaborators/{username}/permission`](/rest/reference/projects#get-project-permission-for-a-user)
|
||||
- [`GET /orgs/{org}/projects`](/rest/reference/projects#list-organization-projects)
|
||||
- [`POST /orgs/{org}/projects`](/rest/reference/projects#create-an-organization-project)
|
||||
- [`GET /projects/{project_id}`](/rest/reference/projects#get-a-project)
|
||||
- [`PATCH /projects/{project_id}`](/rest/reference/projects#update-a-project)
|
||||
- [`DELETE /projects/{project_id}`](/rest/reference/projects#delete-a-project)
|
||||
- [`GET /projects/{project_id}/columns`](/rest/reference/projects#list-project-columns)
|
||||
- [`POST /projects/{project_id}/columns`](/rest/reference/projects#create-a-project-column)
|
||||
- [`GET /projects/columns/{column_id}`](/rest/reference/projects#get-a-project-column)
|
||||
- [`PATCH /projects/columns/{column_id}`](/rest/reference/projects#update-a-project-column)
|
||||
- [`DELETE /projects/columns/{column_id}`](/rest/reference/projects#delete-a-project-column)
|
||||
- [`GET /projects/columns/{column_id}/cards`](/rest/reference/projects#list-project-cards)
|
||||
- [`POST /projects/columns/{column_id}/cards`](/rest/reference/projects#create-a-project-card)
|
||||
- [`POST /projects/columns/{column_id}/moves`](/rest/reference/projects#move-a-project-column)
|
||||
- [`GET /projects/columns/cards/{card_id}`](/rest/reference/projects#get-a-project-card)
|
||||
- [`PATCH /projects/columns/cards/{card_id}`](/rest/reference/projects#update-a-project-card)
|
||||
- [`DELETE /projects/columns/cards/{card_id}`](/rest/reference/projects#delete-a-project-card)
|
||||
- [`POST /projects/columns/cards/{card_id}/moves`](/rest/reference/projects#move-a-project-card)
|
||||
- [`GET /repos/{owner}/{repo}/projects`](/rest/reference/projects#list-repository-projects)
|
||||
- [`POST /repos/{owner}/{repo}/projects`](/rest/reference/projects#create-a-repository-project)
|
||||
- [`GET /users/{username}/projects`](/rest/reference/projects#list-user-projects)
|
||||
- [`POST /user/projects`](/rest/reference/projects#create-a-user-project)
|
||||
|
||||
## pulls
|
||||
|
||||
- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request)
|
||||
@@ -669,7 +538,7 @@ ms.locfileid: '148107236'
|
||||
- [`POST /orgs/{org}/repos`](/rest/reference/repos#create-an-organization-repository)
|
||||
- [`GET /repositories`](/rest/reference/repos#list-public-repositories)
|
||||
- [`GET /repos/{owner}/{repo}`](/rest/reference/repos#get-a-repository)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/reference/repos/#update-a-repository)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/repos/repos#update-a-repository)
|
||||
- [`DELETE /repos/{owner}/{repo}`](/rest/reference/repos#delete-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/contributors`](/rest/reference/repos#list-repository-contributors)
|
||||
- [`GET /repos/{owner}/{repo}/forks`](/rest/reference/repos#list-forks)
|
||||
@@ -677,7 +546,6 @@ ms.locfileid: '148107236'
|
||||
- [`GET /repos/{owner}/{repo}/languages`](/rest/reference/repos#list-repository-languages)
|
||||
- [`GET /repos/{owner}/{repo}/tags`](/rest/reference/repos#list-repository-tags)
|
||||
- [`GET /repos/{owner}/{repo}/teams`](/rest/reference/repos#list-repository-teams)
|
||||
- [`POST /repos/{owner}/{repo}/transfer`](/rest/reference/repos#transfer-a-repository)
|
||||
- [`GET /users/{username}/repos`](/rest/reference/repos#list-repositories-for-a-user)
|
||||
- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user)
|
||||
- [`POST /user/repos`](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
|
||||
@@ -687,16 +555,11 @@ ms.locfileid: '148107236'
|
||||
- [`DELETE /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#delete-autolink)
|
||||
- [`PUT /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes)
|
||||
- [`DELETE /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/reference/repos#list-branches)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/reference/repos#merge-a-branch)
|
||||
- [`POST /repos/{owner}/{repo}/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event)
|
||||
- [`GET /repos/{owner}/{repo}/keys`](/rest/reference/repos#list-deploy-keys)
|
||||
- [`POST /repos/{owner}/{repo}/keys`](/rest/reference/repos#create-a-deploy-key)
|
||||
- [`GET /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#get-a-deploy-key)
|
||||
- [`DELETE /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#delete-a-deploy-key)
|
||||
- [`PUT /repos/{owner}/{repo}/lfs`](/rest/reference/repos#enable-git-lfs-for-a-repository)
|
||||
- [`DELETE /repos/{owner}/{repo}/lfs`](/rest/reference/repos#disable-git-lfs-for-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/releases`](/rest/reference/repos#list-releases)
|
||||
- [`POST /repos/{owner}/{repo}/releases`](/rest/reference/repos#create-a-release)
|
||||
- [`GET /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#get-a-release)
|
||||
@@ -729,7 +592,6 @@ ms.locfileid: '148107236'
|
||||
|
||||
## secret-scanning
|
||||
|
||||
- [`GET /enterprises/{enterprise}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)
|
||||
- [`GET /orgs/{org}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-organization)
|
||||
- [`GET /repos/{owner}/{repo}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#get-a-secret-scanning-alert)
|
||||
@@ -797,7 +659,6 @@ ms.locfileid: '148107236'
|
||||
- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
|
||||
- [`GET /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
|
||||
- [`DELETE /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
|
||||
- [`GET /users/{username}/hovercard`](/rest/reference/users#get-contextual-information-for-a-user)
|
||||
- [`GET /users/{username}/keys`](/rest/reference/users#list-public-keys-for-a-user)
|
||||
- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
|
||||
- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
|
||||
|
||||
@@ -11,6 +11,7 @@ topics:
|
||||
- API
|
||||
children:
|
||||
- /resources-in-the-rest-api
|
||||
- /api-versions
|
||||
- /media-types
|
||||
- /other-authentication-methods
|
||||
- /troubleshooting
|
||||
@@ -20,12 +21,13 @@ children:
|
||||
- /endpoints-available-for-github-apps
|
||||
- /endpoints-available-for-fine-grained-personal-access-tokens
|
||||
- /permissions-required-for-github-apps
|
||||
- /breaking-changes
|
||||
- /permissions-required-for-fine-grained-personal-access-tokens
|
||||
ms.openlocfilehash: 96d6109d1dcd2571ada7e448459980fdf6a92e05
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 7e5671dcf94766dfcc8d1a39dd47191e20eb1513
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145109174'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184231'
|
||||
---
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -13,8 +13,12 @@ topics:
|
||||
- API
|
||||
---
|
||||
|
||||
{% ifversion api-date-versioning %}
|
||||
## API version
|
||||
|
||||
This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}.
|
||||
Available resources may vary between REST API versions. You should use the `X-GitHub-Api-Version` header to specify an API version. For more information, see "[API Versions](/rest/overview/api-versions)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Schema
|
||||
|
||||
|
||||
@@ -17,6 +17,22 @@ topics:
|
||||
If you're encountering some oddities in the API, here's a list of resolutions to
|
||||
some of the problems you may be experiencing.
|
||||
|
||||
{% ifversion api-date-versioning %}
|
||||
|
||||
## `400` error for an unsupported API version
|
||||
|
||||
You should use the `X-GitHub-Api-Version` header to specify an API version. For example:
|
||||
|
||||
```shell
|
||||
$ curl {% data reusables.rest-api.version-header %} https://api.github.com/zen
|
||||
```
|
||||
|
||||
If you specify a version that does not exist, you will receive a `400` error.
|
||||
|
||||
For more information, see "[API Versions](/rest/overview/api-versions)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## `404` error for an existing repository
|
||||
|
||||
Typically, we send a `404` error when your client isn't properly authenticated.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Pull request review comments
|
||||
title: Commentaires de revues de demande de tirage
|
||||
shortTitle: Review comments
|
||||
intro: ''
|
||||
versions:
|
||||
@@ -11,10 +11,15 @@ topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: d076bead1efdb07c3fcce3472798bddeaf9908e6
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181292'
|
||||
---
|
||||
## À propos de l’API Pull request review comments
|
||||
|
||||
## About the Pull request review comments API
|
||||
|
||||
Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
|
||||
Les commentaires de révision de demande de tirage sont des commentaires sur une partie de la différence unifiée effectuée pendant une révision de demande de tirage. Les commentaires de commit et les commentaires de problème sont différents des commentaires de révision de demande de tirage. Vous appliquez des commentaires de commit directement à un commit et vous appliquez des commentaires de problème sans référencer une partie de la différence unifiée. Pour plus d’informations, consultez « [Créer un commentaire de commit](/rest/reference/commits#create-a-commit-comment) » et « [Créer un commentaire de problème](/rest/reference/issues#create-an-issue-comment) ».
|
||||
|
||||
{% data reusables.pull_requests.issues-media-types %}
|
||||
|
||||
@@ -9,12 +9,12 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 80e4a5a5257a8f2615b402567f91daa9e68a0077
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: b140c41062e4fea4c1cb1299b23de774963913af
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145109101'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181300'
|
||||
---
|
||||
## À propos de l’API Demandes de tirage
|
||||
|
||||
@@ -26,12 +26,12 @@ Chaque demande de tirage est un problème, mais chaque problème n’est pas une
|
||||
|
||||
Il s’agit des types de médias pris en charge pour les demandes de tirage.
|
||||
|
||||
application/vnd.github.VERSION.raw+json
|
||||
application/vnd.github.VERSION.text+json
|
||||
application/vnd.github.VERSION.html+json
|
||||
application/vnd.github.VERSION.full+json
|
||||
application/vnd.github.VERSION.diff
|
||||
application/vnd.github.VERSION.patch
|
||||
application/vnd.github.raw+json
|
||||
application/vnd.github.text+json
|
||||
application/vnd.github.html+json
|
||||
application/vnd.github.full+json
|
||||
application/vnd.github.diff
|
||||
application/vnd.github.patch
|
||||
|
||||
Pour plus d’informations, consultez « [Types de médias personnalisés](/rest/overview/media-types) ».
|
||||
|
||||
|
||||
@@ -11,13 +11,15 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: ee55b646dd58b4f91227c6d629c2e07d834b6dfd
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 6e07a6cbbdb368ef530b81a6c9cc3893e1590ac4
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145109097'
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148184055'
|
||||
---
|
||||
## À propos de l’API Révisions de demande de tirage
|
||||
|
||||
Les Révisions de demande de tirage sont des groupes de commentaires de révision de demande de tirage sur une demande de tirage, regroupés avec un état et un commentaire dont le corps est facultatif.
|
||||
|
||||
{% data reusables.pull_requests.issues-media-types %}
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 50875021a506201a90cbac62db521604a390a586
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: fd3619faeb8ccaeaa70e8a2be050881b4a169b64
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147060329'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181297'
|
||||
---
|
||||
## À propos de l’API de contenu du référentiel
|
||||
|
||||
@@ -26,8 +26,8 @@ Pour demander le format brut ou le rendu HTML (lorsqu’il est pris en charge),
|
||||
|
||||
[README](/rest/reference/repos#get-a-repository-readme), [fichiers](/rest/reference/repos#get-repository-content) et [symlinks](/rest/reference/repos#get-repository-content) prennent en charge les types de médias personnalisés suivants :
|
||||
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.VERSION.html
|
||||
application/vnd.github.raw
|
||||
application/vnd.github.html
|
||||
|
||||
Utilisez le type de média `.raw` pour récupérer le contenu du fichier.
|
||||
|
||||
@@ -35,7 +35,7 @@ Pour les fichiers de balisage, comme Markdown ou AsciiDoc, vous pouvez récupér
|
||||
|
||||
[Tous les objets](/rest/reference/repos#get-repository-content) prennent en charge le type de média personnalisé suivant :
|
||||
|
||||
application/vnd.github.VERSION.object
|
||||
application/vnd.github.object
|
||||
|
||||
Utilisez le paramètre de type de média `object` pour récupérer le contenu dans un format d’objet cohérent, quel que soit le type de contenu. Par exemple, au lieu d’un tableau d’objets pour un répertoire, la réponse est un objet avec un attribut `entries` contenant le tableau d’objets.
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: a0c8b24bacdd41e32d9b8bdd0d8850e7a6ada557
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: a9f12214edcef8a107ad9c447fea7207cfdc48f4
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "145103970"
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148184059"
|
||||
---
|
||||
Quand un travail ou un workflow simultané est mis en file d’attente, si un autre travail ou workflow utilisant le même groupe d’accès concurrentiel dans le dépôt est en cours d’exécution, le travail ou le workflow en file d’attente a la valeur `pending`. Tout travail ou workflow en attente dans le groupe d’accès concurrentiel est annulé. Pour annuler également un travail ou un workflow en cours d’exécution dans le même groupe d’accès concurrentiel, spécifiez `cancel-in-progress: true`.
|
||||
|
||||
@@ -26,7 +26,7 @@ concurrency: ci-${{ github.ref }}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.ref }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
@@ -38,7 +38,7 @@ Si vous créez le nom de groupe avec une propriété définie uniquement pour de
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.head_ref || github.run_id }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
@@ -53,7 +53,7 @@ Pour annuler uniquement les exécutions en cours du même workflow, vous pouvez
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.workflow }}-${{ github.ref }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
|
||||
@@ -1,116 +1,192 @@
|
||||
---
|
||||
ms.openlocfilehash: 42464c33b7846422a3a8bd4f1102b8111f7000a7
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: "148107468"
|
||||
---
|
||||
| Nom de la catégorie | Description
|
||||
| Category name | Description
|
||||
|------------------|-------------------
|
||||
{%- ifversion fpt or ghec %} | `account` | Contient des activités liées à un compte d’organisation.
|
||||
| `advisory_credit` | Contient des activités liées au crédit d’un contributeur pour un avis de sécurité dans les données {% data variables.product.prodname_advisory_database %}. Pour plus d’informations, consultez « [À propos des avis de sécurité {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories) ».
|
||||
{%- endif %} | `artifact` | Contient des activités liées aux artefacts d’exécution de workflow {% data variables.product.prodname_actions %}.
|
||||
{%- ifversion audit-log-streaming %} | `audit_log_streaming` | Contient des activités liées aux journaux d’audit de streaming pour les organisations dans un compte d’entreprise.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `billing` |Contient des activités liées à la facturation d’une organisation.
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | Contient des activités liées aux paramètres métier d’une entreprise.
|
||||
{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_advanced_security` | Contient les activités liées à {% data variables.product.prodname_GH_advanced_security %} dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ».
|
||||
| `business_secret_scanning` | Contient les activités relatives à l’{% data variables.product.prodname_secret_scanning %} dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ».
|
||||
{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | Contient les activités relatives aux modèles personnalisés pour l’{% data variables.product.prodname_secret_scanning %} dans une entreprise.
|
||||
{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_secret_scanning_push_protection` | Contient les activités relatives à la fonctionnalité de protection des poussées de l’{% data variables.product.prodname_secret_scanning %} dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ».
|
||||
| `business_secret_scanning_push_protection_custom_message` | Contient les activités relatives au message personnalisé affiché quand la protection des poussées est déclenchée dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ».
|
||||
{%- endif %} | `checks` | Contient des activités liées aux suites de vérifications et exécutions.
|
||||
{%- ifversion fpt or ghec %} | `codespaces` | Contient des activités liées aux codespaces d’une organisation.
|
||||
{%- endif %} | `commit_comment` | Contient des activités liées à la mise à jour ou à la suppression des commentaires de validation.
|
||||
{%- ifversion ghes %} | `config_entry` | Contient des activités liées aux paramètres de configuration. Ces événements sont visibles uniquement dans le journal d’audit de l’administrateur de site.
|
||||
{%- endif %} | | `dependabot_alerts` | Contient les activités de configuration au niveau de l’organisation pour les {% data variables.product.prodname_dependabot_alerts %} dans les dépôts existants. Pour plus d’informations, consultez « [À propos des {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts) ».
|
||||
| `dependabot_alerts_new_repos` | Contient des activités de configuration au niveau de l’organisation pour {% data variables.product.prodname_dependabot_alerts %} dans des nouveaux référentiels créés dans l’organisation.
|
||||
| `dependabot_repository_access` | Contient des activités liées aux référentiels privés d’une organisation {% data variables.product.prodname_dependabot %} auxquels l’accès est autorisé.
|
||||
{%- ifversion fpt or ghec or ghes %} | `dependabot_security_updates` | Contient les activités de configuration au niveau de l’organisation pour les {% data variables.product.prodname_dependabot_security_updates %} dans les dépôts existants. Pour plus d’informations, consultez « [Configuration des {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates) ».
|
||||
| `dependabot_security_updates_new_repos` | Contient des activités de configuration au niveau de l’organisation pour {% data variables.product.prodname_dependabot_security_updates %} pour les nouveaux référentiels créés dans l’organisation.
|
||||
{%- endif %} | `dependency_graph` | Contient des activités de configuration au niveau de l’organisation pour les graphes des dépendances pour les dépôts. Pour plus d’informations, consultez « [À propos du graphe des dépendances](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) ».
|
||||
| `dependency_graph_new_repos` | Contient des activités de configuration au niveau de l’organisation pour les nouveaux référentiels créés dans l’organisation.
|
||||
{%- ifversion fpt or ghec %} | `discussion` | Contient des activités liées aux discussions d’équipe.
|
||||
| `discussion_comment` | Contient des activités liées aux commentaires publiés dans les discussions sur une page d’équipe.
|
||||
| `discussion_post` | Contient des activités liées aux discussions publiées sur une page d’équipe.
|
||||
| `discussion_post_reply` | Contient des activités liées aux réponses aux discussions publiées sur une page d’équipe.
|
||||
{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | Contient des activités liées à {% data variables.product.prodname_github_connect %}.
|
||||
| `enterprise` | Contient des activités liées aux paramètres d’entreprise.
|
||||
{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | Contient des activités liées aux domaines d’entreprise vérifiés.
|
||||
| `enterprise_installation` | Contient des activités liées aux {% data variables.product.prodname_github_app %} associés à une connexion d’entreprise {% data variables.product.prodname_github_connect %}.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `environment` | Contient des activités liées aux environnements {% data variables.product.prodname_actions %}.
|
||||
{%- endif %} {%- ifversion ghae %} | `external_group` | Contient des activités liées aux groupes Okta.
|
||||
| `external_identity` | Contient des activités liées à un utilisateur dans un groupe Okta.
|
||||
{%- endif %} | `gist` | Contient des activités liées aux Gists.
|
||||
| `hook` | Contient toutes les activités liées aux webhooks.
|
||||
| `integration` | Contient des activités liées aux intégrations dans un compte.
|
||||
| `integration_installation` | Contient des activités liées aux intégrations installées dans un compte.
|
||||
| `integration_installation_request` | Contient des activités liées aux demandes des membres de l’organisation pour que les propriétaires approuvent les intégrations à utiliser dans l’organisation.
|
||||
{%- ifversion ghec or ghae %} | `ip_allow_list` | Contient des activités liées à l’activation ou à la désactivation de la liste d’autorisation des adresses IP pour une organisation.
|
||||
| `ip_allow_list_entry` | Contient des activités liées à la création, à la suppression et à la modification d’une entrée de la liste d’autorisation des adresses IP pour une organisation.
|
||||
{%- endif %} | `issue` | Contient des activités liées à l’épinglage, au transfert ou à la suppression d’un problème dans un référentiel.
|
||||
| `issue_comment` | Contient des activités liées à l’épinglage, au transfert ou à la suppression des commentaires de problème.
|
||||
| `issues` | Contient des activités liées à l’activation ou à la désactivation de la création de problème pour une organisation.
|
||||
{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | Contient des activités liées à la signature du Contrat du développeur {% data variables.product.prodname_marketplace %}.
|
||||
| `marketplace_listing` | Contient des activités liées à la liste des applications dans {% data variables.product.prodname_marketplace %}.
|
||||
{%- endif %} | `members_can_create_pages` | Contient des activités liées à la gestion de la publication des sites {% data variables.product.prodname_pages %} pour les référentiels de l’organisation. Pour plus d’informations, consultez « [Gestion de la publication de sites {% data variables.product.prodname_pages %} pour votre organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization). »
|
||||
| `members_can_create_private_pages` | Contient des activités liées à la gestion de la publication de sites privés {% data variables.product.prodname_pages %} pour les référentiels de l’organisation.
|
||||
| `members_can_create_public_pages` | Contient des activités liées à la gestion de la publication des sites publiques {% data variables.product.prodname_pages %} pour les référentiels de l’organisation.
|
||||
{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | Contient des activités liées à l’activation ou à la désactivation de la création de référentiels pour une organisation.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | Contient des activités de configuration au niveau de l’organisation permettant aux membres de l’organisation d’afficher les insights sur les dépendances.
|
||||
| `migration` | Contient des activités liées au transfert de données à partir d’un emplacement *source* (comme une organisation {% data variables.product.prodname_dotcom_the_website %} ou une instance {% data variables.product.prodname_ghe_server %}) vers une instance {% data variables.product.prodname_ghe_server %} *cible*.
|
||||
{%- endif %} | `oauth_access` | Contient des activités liées aux jetons d’accès OAuth.
|
||||
| `oauth_application` | Contient toutes les activités liées aux applications OAuth.
|
||||
{%- ifversion fpt or ghec %} | `oauth_authorization` | Contient des activités liées à l’autorisation des applications OAuth.
|
||||
{%- endif %} | `org` | Contient des activités liées à l’appartenance à l’organisation.
|
||||
{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | Contient des activités liées à l’autorisation des informations d’identification pour l’authentification unique SAML.
|
||||
{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | Contient des activités liées aux modèles personnalisés pour l’analyse des secrets dans une organisation. Pour plus d’informations, consultez « [Définition de modèles personnalisés pour l’analyse des secrets](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning) ».
|
||||
| `org.secret_scanning_push_protection` | Contient des activités liées aux modèles personnalisés d’analyse des secrets dans une organisation. Pour plus d’informations, consultez « [Protection des poussées avec l’analyse des secrets](/code-security/secret-scanning/protecting-pushes-with-secret-scanning) ».
|
||||
{%- endif %} | `organization_default_label` | Contient des activités liées aux étiquettes par défaut pour les référentiels d’une organisation.
|
||||
{%- ifversion fpt or ghec or ghes %} | `organization_domain` | Contient des activités liées aux domaines d’organisation vérifiés.
|
||||
| `organization_projects_change` | Contient des activités liées aux tableaux de projet à l’échelle de l’organisation dans une entreprise.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | Contient des activités liées aux domaines personnalisés vérifiés pour {% data variables.product.prodname_pages %}.
|
||||
| `payment_method` | Contient des activités liées à la façon dont une organisation paie {% data variables.product.prodname_dotcom %}.
|
||||
| `prebuild_configuration` | Contient des activités liées aux configurations de prébuild pour {% data variables.product.prodname_github_codespaces %}.
|
||||
{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` |Contient des activités liées aux environnements de hooks de pré-réception.
|
||||
| `pre_receive_hook` | Contient des activités liées aux hooks de pré-réception.
|
||||
{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | Contient des activités liées à l’activation du mode privé pour une entreprise.
|
||||
{%- endif %} | `private_repository_forking` | Contient des activités liées à l’autorisation des duplications (forks) de référentiels privés et internes, pour un référentiel, une organisation ou une entreprise.
|
||||
{%- ifversion fpt or ghec %} | `profile_picture` | Contient des activités liées à l’image de profil d’une organisation.
|
||||
{%- endif %} | `project` | Contient des activités liées aux tableaux de projet.
|
||||
| `project_field` | Contient des activités liées à la création et à la suppression de champs dans un tableau de projet.
|
||||
| `project_view` | Contient des activités liées à la création et à la suppression d’affichages dans un tableau de projet.
|
||||
| `protected_branch` | Contient des activités liées aux branches protégées.
|
||||
| `public_key` | Contient des activités liées aux clés SSH et aux clés de déploiement.
|
||||
| `pull_request` | Contient des activités liées aux demandes de tirage.
|
||||
| `pull_request_review` | Contient des activités liées aux révisions de demande de tirage (pull request).
|
||||
| `pull_request_review_comment` | Contient des activités liées aux commentaires de révision de demande de tirage (pull request).
|
||||
| `repo` | Contient des activités liées aux dépôts appartenant à une organisation.
|
||||
{%- ifversion fpt or ghec %} | `repository_advisory` | Contient des activités au niveau du référentiel liées aux avis de sécurité {% data variables.product.prodname_advisory_database %}. Pour plus d’informations, consultez « [À propos des avis de sécurité {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories) ».
|
||||
| `repository_content_analysis` | Contient des activités liées à [l’activation ou à la désactivation de l’utilisation des données pour un référentiel privé](/articles/about-github-s-use-of-your-data).
|
||||
| `repository_dependency_graph` | Contient des activités au niveau du référentiel liées à l’activation ou à la désactivation du graphique de dépendance pour un référentiel privé {% ifversion fpt or ghec %} {% endif %}. Pour plus d’informations, consultez « [À propos du graphe des dépendances](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) ».
|
||||
{%- endif %} | `repository_image` | Contient des activités liées aux images d’un référentiel.
|
||||
| `repository_invitation` | Contient des activités liées aux invitations à rejoindre un référentiel.
|
||||
| `repository_projects_change` | Contient des activités liées à l’activation de projets pour un référentiel ou pour tous les référentiels d’une organisation.
|
||||
{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning` | Contient des activités au niveau du référentiel liées à l’analyse des secrets. Pour plus d’informations, consultez « [À propos de l’analyse des secrets](/github/administering-a-repository/about-secret-scanning) ».
|
||||
{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | Contient des activités liées aux modèles personnalisés d’analyse des secrets dans un dépôt. Pour plus d’informations, consultez « [Définition de modèles personnalisés pour l’analyse des secrets](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning) ». {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | Contient des activités liées aux modèles personnalisés d’analyse des secrets dans un dépôt. Pour plus d’informations, consultez « [Protection des poussées avec l’analyse des secrets](/code-security/secret-scanning/protecting-pushes-with-secret-scanning) ».
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contient des activités liées au fait d’autoriser des membres de l’organisation à modifier les visibilités des référentiels pour l’organisation.
|
||||
{%- endif %} | `repository_vulnerability_alert` | Contient des activités liées aux [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
|
||||
{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | Contient des activités de configuration au niveau du dépôt pour les {% data variables.product.prodname_dependabot_alerts %}.
|
||||
| `required_status_check` | Contient des activités liées aux vérifications d’état requises pour les branches protégées.
|
||||
{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | Contient des activités liées à la restriction des notifications par e-mail aux domaines approuvés ou vérifiés pour une entreprise.
|
||||
{%- endif %} {%- ifversion custom-repository-roles %} | `role` | Contient des activités liées aux [rôles de dépôt personnalisés](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `secret_scanning` | Contient des activités de configuration au niveau de l’organisation pour l’analyse des secrets dans les référentiels existants. Pour plus d’informations, consultez « [À propos de l’analyse des secrets](/github/administering-a-repository/about-secret-scanning) ».
|
||||
| `secret_scanning_new_repos` | Contient des activités de configuration au niveau de l’organisation liées à l’analyse des secrets pour les référentiels créés dans l’organisation.
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | Contient des activités liées à l’inscription et à la suppression des clés de sécurité.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `sponsors` | Contient des événements liés aux boutons Parrainer (consultez « [Affichage d’un bouton de sponsor dans votre référentiel](/articles/displaying-a-sponsor-button-in-your-repository) »).
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | Contient des activités liées à une autorité de certification SSH dans une organisation ou une entreprise.
|
||||
| `ssh_certificate_requirement` | Contient des activités liées à l’obligation pour les membres d’utiliser des certificats SSH pour accéder aux ressources de l’organisation.
|
||||
{%- endif %} | `staff` | Contient des activités liées à un administrateur de site effectuant une action.
|
||||
| `team` | Contient des activités liées aux équipes d’une organisation.
|
||||
| `team_discussions` | Contient des activités liées à la gestion des discussions d’équipe d’une organisation.
|
||||
{%- ifversion ghec %} | `team_sync_tenant` |Contient des activités liées à la synchronisation d’équipe avec un fournisseur d’identité pour une entreprise ou une organisation.
|
||||
{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | Contient des activités liées à l’authentification à 2 facteurs.
|
||||
{%- endif %} | `user` | Contient des activités liées aux utilisateurs d’une organisation ou entreprise.
|
||||
{%- ifversion ghec or ghes %} | `user_license` | Contient des activités liées à un utilisateur occupant un siège sous licence et faisant partie d’une entreprise.
|
||||
{%- endif %} | `workflows` | Contient des activités liées aux workflows {% data variables.product.prodname_actions %}.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `account` | Contains activities related to an organization account.
|
||||
| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
{%- endif %}
|
||||
| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts.
|
||||
{%- ifversion audit-log-streaming %}
|
||||
| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `billing` | Contains activities related to an organization's billing.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `business` | Contains activities related to business settings for an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion code-security-audit-log-events %}
|
||||
| `business_advanced_security` | Contains activities related to {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
| `business_secret_scanning` | Contains activities related to {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for {% data variables.product.prodname_secret_scanning %} in an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion code-security-audit-log-events %}
|
||||
| `business_secret_scanning_push_protection` | Contains activities related to the push protection feature of {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
| `business_secret_scanning_push_protection_custom_message` | Contains activities related to the custom message displayed when push protection is triggered in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
| `checks` | Contains activities related to check suites and runs.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `codespaces` | Contains activities related to an organization's codespaces.
|
||||
{%- endif %}
|
||||
| `commit_comment` | Contains activities related to updating or deleting commit comments.
|
||||
{%- ifversion ghes %}
|
||||
| `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log.
|
||||
{%- endif %}
|
||||
| `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
|
||||
| `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
|
||||
| `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access.
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
| `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
|
||||
| `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.
|
||||
{%- endif %}
|
||||
| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
| `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `discussion` | Contains activities related to team discussions.
|
||||
| `discussion_comment` | Contains activities related to comments posted in discussions on a team page.
|
||||
| `discussion_post` | Contains activities related to discussions posted to a team page.
|
||||
| `discussion_post_reply` | Contains activities related to replies to discussions posted to a team page.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes %}
|
||||
| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}.
|
||||
| `enterprise` | Contains activities related to enterprise settings.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec %}
|
||||
| `enterprise_domain` | Contains activities related to verified enterprise domains.
|
||||
| `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments.
|
||||
{%- endif %}
|
||||
{%- ifversion ghae %}
|
||||
| `external_group` | Contains activities related to Okta groups.
|
||||
| `external_identity` | Contains activities related to a user in an Okta group.
|
||||
{%- endif %}
|
||||
| `gist` | Contains activities related to Gists.
|
||||
| `hook` | Contains activities related to webhooks.
|
||||
| `integration` | Contains activities related to integrations in an account.
|
||||
| `integration_installation` | Contains activities related to integrations installed in an account.
|
||||
| `integration_installation_request` | Contains activities related to organization member requests for owners to approve integrations for use in the organization.
|
||||
{%- ifversion ghec or ghae %}
|
||||
| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization.
|
||||
| `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.
|
||||
{%- endif %}
|
||||
| `issue` | Contains activities related to pinning, transferring, or deleting an issue in a repository.
|
||||
| `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments.
|
||||
| `issues` | Contains activities related to enabling or disabling issue creation for an organization.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
| `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}.
|
||||
{%- endif %}
|
||||
| `members_can_create_pages` | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
|
||||
| `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization.
|
||||
| `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization.
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights.
|
||||
| `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance.
|
||||
{%- endif %}
|
||||
| `oauth_access` | Contains activities related to OAuth access tokens.
|
||||
| `oauth_application` | Contains activities related to OAuth Apps.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `oauth_authorization` | Contains activities related to authorizing OAuth Apps.
|
||||
{%- endif %}
|
||||
| `org` | Contains activities related to organization membership.
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on.
|
||||
{%- endif %}
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
| `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
{%- endif %}
|
||||
| `organization_default_label` | Contains activities related to default labels for repositories in an organization.
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
| `organization_domain` | Contains activities related to verified organization domains.
|
||||
| `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}.
|
||||
| `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}.
|
||||
| `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}.
|
||||
{%- endif %}
|
||||
{%- ifversion ghes %}
|
||||
| `pre_receive_environment` | Contains activities related to pre-receive hook environments.
|
||||
| `pre_receive_hook` | Contains activities related to pre-receive hooks.
|
||||
{%- endif %}
|
||||
{%- ifversion ghes %}
|
||||
| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise.
|
||||
{%- endif %}
|
||||
| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `profile_picture` | Contains activities related to an organization's profile picture.
|
||||
{%- endif %}
|
||||
| `project` | Contains activities related to project boards.
|
||||
| `project_field` | Contains activities related to field creation and deletion in a project board.
|
||||
| `project_view` | Contains activities related to view creation and deletion in a project board.
|
||||
| `protected_branch` | Contains activities related to protected branches.
|
||||
| `public_key` | Contains activities related to SSH keys and deploy keys.
|
||||
| `pull_request` | Contains activities related to pull requests.
|
||||
| `pull_request_review` | Contains activities related to pull request reviews.
|
||||
| `pull_request_review_comment` | Contains activities related to pull request review comments.
|
||||
| `repo` | Contains activities related to the repositories owned by an organization.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
| `repository_content_analysis` | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).
|
||||
| `repository_dependency_graph` | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
{%- endif %}
|
||||
| `repository_image` | Contains activities related to images for a repository.
|
||||
| `repository_invitation` | Contains activities related to invitations to join a repository.
|
||||
| `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization.
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `repository_secret_scanning` | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
{%- endif %}
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization.
|
||||
{%- endif %}
|
||||
| `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.
|
||||
| `required_status_check` | Contains activities related to required status checks for protected branches.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes %}
|
||||
| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion custom-repository-roles %}
|
||||
| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `secret_scanning` | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
| `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `security_key` | Contains activities related to security keys registration and removal.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `sponsors` | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)").
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise.
|
||||
| `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources.
|
||||
{%- endif %}{% ifversion sso-redirect %}
|
||||
| `sso_redirect` | Contains activities related to automatically redirecting users to sign in (see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)").{% endif %}
|
||||
| `staff` | Contains activities related to a site admin performing an action.
|
||||
| `team` | Contains activities related to teams in an organization.
|
||||
| `team_discussions` | Contains activities related to managing team discussions for an organization.
|
||||
{%- ifversion ghec %}
|
||||
| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghes %}
|
||||
| `two_factor_authentication` | Contains activities related to two-factor authentication.
|
||||
{%- endif %}
|
||||
| `user` | Contains activities related to users in an enterprise or organization.
|
||||
{%- ifversion ghec or ghes %}
|
||||
| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise.
|
||||
{%- endif %}
|
||||
| `workflows` | Contains activities related to {% data variables.product.prodname_actions %} workflows.
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
For compiled languages like Java,{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %}{% ifversion codeql-go-autobuild %} Go,{% endif %} C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build ony the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
|
||||
---
|
||||
ms.openlocfilehash: a39c6a75a0b6decf15352f2d164d593f0d020fff
|
||||
ms.sourcegitcommit: dac72908e8660cb4a347fbf73beab61034eed8c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: "148182305"
|
||||
---
|
||||
Pour les langages compilés tels que Java,{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %}{% ifversion codeql-go-autobuild %} Go,{% endif %} C, C++ et C#, {% data variables.product.prodname_codeql %} analyse l’ensemble du code généré au moment de l’exécution du workflow. Pour limiter la quantité de code analysée, générez uniquement le code que vous souhaitez analyser en spécifiant vos propres étapes de génération dans un bloc `run`. Vous pouvez simultanément spécifier vos propres étapes de génération et utiliser les filtres `paths` et `paths-ignore` sur les événements `pull_request` et `push` afin que votre workflow ne s’exécute que quand du code spécifique est modifié. Pour plus d’informations, consultez « [Syntaxe de workflow pour {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) ».
|
||||
|
||||
For languages like{% ifversion codeql-go-autobuild %}{% else %} Go,{% endif %} JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
|
||||
Pour les langages tels que {% ifversion codeql-go-autobuild %}{% else %} Go,{% endif %} JavaScript, Python et TypeScript, que {% data variables.product.prodname_codeql %} analyse sans compiler le code source, vous pouvez spécifier des options de configuration supplémentaires afin de limiter la quantité de code à analyser. Pour plus d’informations, consultez « [Spécification des répertoires à analyser](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan) ».
|
||||
@@ -1,2 +1,10 @@
|
||||
If `autobuild` fails, or you want to analyze a different set of source files from those built by the `autobuild` process, you'll need to remove the `autobuild` step from the workflow, and manually add build steps. For C/C++, C#, Go,{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %} and Java projects, {% data variables.product.prodname_codeql %} will analyze whatever source code is built by your specified build steps.
|
||||
---
|
||||
ms.openlocfilehash: d4d496d4b5c45f557d80aace29013b3b32e478c6
|
||||
ms.sourcegitcommit: dac72908e8660cb4a347fbf73beab61034eed8c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: "148182273"
|
||||
---
|
||||
Si `autobuild` échoue, ou si vous voulez analyser un ensemble de fichiers sources différents de ceux générés par le processus `autobuild`, vous devez supprimer l’étape `autobuild` du workflow et ajouter manuellement les étapes de génération. Pour les projets C/C++, C#, Go,{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %} et Java, {% data variables.product.prodname_codeql %} analyse le code source généré par vos étapes de génération spécifiées.
|
||||
|
||||
|
||||
@@ -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 %}{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %} and Java.
|
||||
---
|
||||
ms.openlocfilehash: 81bb084ee5dcb540c77b4a7b55c67890bab2d47a
|
||||
ms.sourcegitcommit: dac72908e8660cb4a347fbf73beab61034eed8c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: "148182289"
|
||||
---
|
||||
Pour les langages compilés pris en charge, vous pouvez utiliser l’action `autobuild` dans le {% data variables.code-scanning.codeql_workflow %} pour générer votre code. Cela vous évite d’avoir à spécifier des commandes de build explicites pour C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %}{% ifversion codeql-kotlin-beta %} Kotlin {% endif %} et Java.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 10a6df860ab8205845ae90fcb01d95d8e617096c
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181293"
|
||||
---
|
||||
Les {% data variables.product.prodname_dependabot_security_updates %} {% ifversion dependabot-actions-support %} peuvent corriger les dépendances vulnérables dans {% data variables.product.prodname_actions %}. Lorsque les mises à jour de sécurité sont activées, {% data variables.product.prodname_dependabot %} déclenche automatiquement une demande de tirage pour mettre à jour les {% data variables.product.prodname_actions %} vulnérables utilisées dans vos workflows vers la version corrigée minimale. {% endif %}
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
ms.openlocfilehash: 4e7a2b55a6a6db231bacb232e4a4da0b4101dbf1
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 1cb33ecd5b87ac110509c21934a0c8747f2087ae
|
||||
ms.sourcegitcommit: 4c72bcff385d7093cc42df79ad17f05cfd900b5f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147167402"
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148183930"
|
||||
---
|
||||
| Licences utilisateur | Processeurs virtuels | Mémoire | Stockage associé | Stockage racine |
|
||||
| Licences utilisateur | Processeurs virtuels | Mémoire | Stockage racine | Stockage (de données) attaché |
|
||||
| :- | -: | -: | -: | -: |
|
||||
| Essai, démonstration ou 10 utilisateurs légers | 4 | 32 Go | 150 Go | 200 Go |
|
||||
| 10 à 3 000 | 8 | 48 Go | 300 Go | 200 Go |
|
||||
| 3 000 à 5 000 | 12 | 64 Go | 500 Go | 200 Go |
|
||||
| 5 000 à 8 000 | 16 | 96 Go | 750 Go | 200 Go |
|
||||
| 8 000 à 10 000+ | 20 | 160 Go | 1 000 Go | 200 Go |
|
||||
| Essai, démonstration ou 10 utilisateurs légers | 4 | 32 Go | 200 Go | 150 Go |
|
||||
| 10 à 3 000 | 8 | 48 Go | 200 Go | 300 Go |
|
||||
| 3 000 à 5 000 | 12 | 64 Go | 200 Go | 500 Go |
|
||||
| 5 000 à 8 000 | 16 | 96 Go | 200 Go | 750 Go |
|
||||
| 8 000 à 10 000+ | 20 | 160 Go | 200 Go | 1 000 Go |
|
||||
|
||||
@@ -1,11 +1,5 @@
|
||||
---
|
||||
ms.openlocfilehash: 5c02cf240a1d23e9549a534381d9914bd8dc0ebd
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145101598"
|
||||
---
|
||||
Lorsque vous activez la liste verte, les adresses IP que vous avez configurées sont immédiatement ajoutées aux listes vertes des organisations de votre entreprise. Si vous désactivez la liste verte, les adresses sont supprimées des listes vertes des organisations.
|
||||
When you enable the allow list, the IP addresses you have configured are immediately added to the allow lists of organizations in your enterprise. If you disable the allow list, the addresses are removed from the organization allow lists.
|
||||
|
||||
Vous pouvez choisir d’ajouter automatiquement à votre liste verte toutes les adresses IP configurées pour {% data variables.product.prodname_github_apps %} installées dans votre entreprise. Le créateur d’une {% data variables.product.prodname_github_app %} peut configurer une liste verte pour son application, en spécifiant les adresses IP autorisées pour l’exécution de l’application. En héritant de sa liste verte dans la vôtre, vous évitez les refus de demandes de connexion de l’application. Pour plus d’informations, consultez « [Autorisation de l’accès par GitHub Apps](#allowing-access-by-github-apps) ».
|
||||
{% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
|
||||
|
||||
You can choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} installed in your enterprise. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by GitHub Apps](#allowing-access-by-github-apps)."
|
||||
|
||||
@@ -1,2 +1,10 @@
|
||||
1. Under your organization name, click {% ifversion projects-v2 %}{% octicon "table" aria-label="The Projects icon" %}{% else %}{% octicon "project" aria-label="The Projects icon" %}{% endif %} **Projects**.
|
||||
{% ifversion projects-v2 %}{% else %}{% endif %}
|
||||
---
|
||||
ms.openlocfilehash: ce21934ccff5f4f88bf2d3984ae95bcd11e5a41e
|
||||
ms.sourcegitcommit: 9bf175b190674416ad4e11b5c567409f74c00ad2
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/23/2022
|
||||
ms.locfileid: "148181212"
|
||||
---
|
||||
1. Sous le nom de votre organisation, cliquez sur {% ifversion projects-v2 %}{% octicon "table" aria-label="The Projects icon" %}{% else %}{% octicon "project" aria-label="The Projects icon" %}{% endif %} **Projets**.
|
||||
{% ifversion projects-v2 %}{% else %}{% endif %}
|
||||
|
||||
@@ -1,10 +1,8 @@
|
||||
---
|
||||
ms.openlocfilehash: 2f27cc8f89cfa028a5e07512c1528152a9bd4941
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "145107790"
|
||||
---
|
||||
1. Pour exiger que les membres utilisent des certificats SSH, vous pouvez sélectionner **Exiger des certificats SSH**, puis cliquer sur **Enregistrer**.
|
||||
|
||||
1. Optionally, to require members to use SSH certificates, select **Require SSH Certificates**, then click **Save**.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** When you require SSH certificates, the requirement does not apply to authorized third-party integrations or to {% data variables.product.prodname_dotcom %} features such as {% data variables.product.prodname_actions %}{% ifversion fpt or ghec %} and {% data variables.product.prodname_codespaces %}{% endif %}, which are trusted environments within the {% data variables.product.prodname_dotcom %} ecosystem.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
---
|
||||
ms.openlocfilehash: 0e58e5904bbff65341fbe4221fa03ea96e032c42
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: a45f36a89c0e8881fa181cc31f03a6a9cf034aa9
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "145086994"
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181287"
|
||||
---
|
||||
### Types de médias personnalisés
|
||||
|
||||
Il s’agit des types de médias pris en charge pour cette API :
|
||||
|
||||
application/vnd.github.VERSION.raw+json
|
||||
application/vnd.github.VERSION.text+json
|
||||
application/vnd.github.VERSION.html+json
|
||||
application/vnd.github.VERSION.full+json
|
||||
application/vnd.github.raw+json
|
||||
application/vnd.github.text+json
|
||||
application/vnd.github.html+json
|
||||
application/vnd.github.full+json
|
||||
|
||||
Pour plus d’informations sur les types de médias, consultez « [Types de médias personnalisés](/rest/overview/media-types) ».
|
||||
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
ms.openlocfilehash: eb4b729cf490728306961ff3d2ef2835700c8735
|
||||
ms.sourcegitcommit: 80edcdbff4726de4d196584fcb603bca2efffd1f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181798"
|
||||
---
|
||||
Ce tableau montre le comportement des alertes pour chaque façon dont un utilisateur peut contourner un blocage de la protection push.
|
||||
|
||||
| Motif du contournement | Comportement des alertes |
|
||||
|-----------------------|------------------------------------------------------|
|
||||
| Il est utilisé dans des tests | {% data variables.product.prodname_dotcom %} crée une alerte fermée, résolue comme « utilisé dans des tests » |
|
||||
| C'est un faux positif | {% data variables.product.prodname_dotcom %} crée une alerte fermée, résolue comme « faux positif » |
|
||||
| Je le corrigerai plus tard | {% data variables.product.prodname_dotcom %} crée une alerte ouverte |
|
||||
@@ -1,127 +1,135 @@
|
||||
Partner | Supported secret
|
||||
---
|
||||
ms.openlocfilehash: 59e78cbf492110a8949c27e867bf195ae5605307
|
||||
ms.sourcegitcommit: bddda0c0814770ee64e378692891931c618247ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181762"
|
||||
---
|
||||
Partenaire | Secret pris en charge
|
||||
--- | ---
|
||||
Adafruit IO | Adafruit IO Key
|
||||
Adobe | Adobe Device Token
|
||||
Adobe | Adobe Service Token
|
||||
Adobe | Adobe Short-Lived Access Token
|
||||
Adobe | Adobe JSON Web Token
|
||||
Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair
|
||||
Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair
|
||||
Atlassian | Atlassian API Token
|
||||
Atlassian | Atlassian JSON Web Token
|
||||
Azure | Azure Active Directory Application Secret
|
||||
Azure | Azure Batch Key Identifiable
|
||||
Azure | Azure CosmosDB Key Identifiable
|
||||
Azure | Azure DevOps {% data variables.product.pat_generic_title_case %}
|
||||
Azure | Azure ML Studio (classic) Web Service Key
|
||||
Azure | Azure SAS Token
|
||||
Azure | Azure Search Admin Key
|
||||
Azure | Azure Search Query Key
|
||||
Azure | Azure Service Management Certificate
|
||||
Azure | Azure SQL Connection String
|
||||
Azure | Azure Storage Account Key
|
||||
Checkout.com | Checkout.com Production Secret Key
|
||||
Checkout.com | Checkout.com Test Secret Key
|
||||
Chief | Chief Tools Token
|
||||
Clojars | Clojars Deploy Token
|
||||
CloudBees CodeShip | CloudBees CodeShip Credential
|
||||
Contributed Systems | Contributed Systems Credentials
|
||||
Databricks | Databricks Access Token
|
||||
Datadog | Datadog API Key
|
||||
DevCycle | DevCycle Client API Key
|
||||
DevCycle | DevCycle Server API Key
|
||||
DigitalOcean | DigitalOcean {% data variables.product.pat_generic_title_case %}
|
||||
DigitalOcean | DigitalOcean OAuth Token
|
||||
DigitalOcean | DigitalOcean Refresh Token
|
||||
DigitalOcean | DigitalOcean System Token
|
||||
Discord | Discord Bot Token
|
||||
Doppler | Doppler Personal Token
|
||||
Doppler | Doppler Service Token
|
||||
Doppler | Doppler CLI Token
|
||||
Doppler | Doppler SCIM Token
|
||||
Doppler | Doppler Audit Token
|
||||
Dropbox | Dropbox Access Token
|
||||
Dropbox | Dropbox Short Lived Access Token
|
||||
Dynatrace | Dynatrace Access Token
|
||||
Dynatrace | Dynatrace Internal Token
|
||||
E/S Adafruit | Clé d’E/S Adafruit
|
||||
Adobe | Jeton d’appareil Adobe
|
||||
Adobe | Jeton de service Adobe
|
||||
Adobe | Jeton d’accès courte durée Adobe
|
||||
Adobe | Jeton web JSON Adobe
|
||||
Alibaba Cloud | ID de clé d’accès et paire de clé d’accès-secret Alibaba Cloud
|
||||
Amazon Web Services (AWS) | ID de clé d’accès et paire de clé d’accès-secret Amazon AWS
|
||||
Atlassian | Jeton d’API Atlassian
|
||||
Atlassian | Jeton web JSON Atlassian
|
||||
Azure | Secret d’application Azure Active Directory
|
||||
Azure | Clé Azure Batch identifiable
|
||||
Azure | Clé Azure CosmosDB identifiable
|
||||
Azure | {% data variables.product.pat_generic_title_case %} Azure DevOps
|
||||
Azure | Clé du service web Azure ML Studio (classique)
|
||||
Azure | Jeton SAP Azure
|
||||
Azure | Clé d’administration de Recherche Azure
|
||||
Azure | Clé de requête de Recherche Azure
|
||||
Azure | Certificat Azure Service Management
|
||||
Azure | Chaîne de connexion Azure SQL
|
||||
Azure | Clé du compte de Stockage Azure
|
||||
Checkout.com | Clé secrète de production Checkout.com
|
||||
Checkout.com | Clé secrète de test Checkout.com
|
||||
Chief | Jeton Chief Tools
|
||||
Clojars | Jeton de déploiement Clojars
|
||||
CloudBees CodeShip | Informations d’identification CloudBees CodeShip
|
||||
Contributed Systems | Informations d’identification Contributed Systems
|
||||
Databricks | Jeton d’accès Databricks
|
||||
Datadog | Clé API Datadog
|
||||
DevCycle | Clé API client DevCycle
|
||||
DevCycle | Clé API serveur DevCycle
|
||||
DigitalOcean | {% data variables.product.pat_generic_title_case %} DigitalOcean
|
||||
DigitalOcean | Jeton OAuth DigitalOcean
|
||||
DigitalOcean | Jeton d’actualisation DigitalOcean
|
||||
DigitalOcean | Jeton système DigitalOcean
|
||||
Discord | Jeton de bot Discord
|
||||
Doppler | Jeton personnel Doppler
|
||||
Doppler | Jeton de service Doppler
|
||||
Doppler | Jeton CLI Doppler
|
||||
Doppler | Jeton SCIM Doppler
|
||||
Doppler | Jeton d’audit Doppler
|
||||
Dropbox | Jeton d’accès Dropbox
|
||||
Dropbox | Jeton d’accès courte durée Dropbox
|
||||
Dynatrace | Jeton d’accès Dynatrace
|
||||
Dynatrace | Jeton interne Dynatrace
|
||||
Figma | Figma {% data variables.product.pat_generic_title_case %}
|
||||
Finicity | Finicity App Key
|
||||
Frame.io | Frame.io JSON Web Token
|
||||
Frame.io| Frame.io Developer Token
|
||||
FullStory| FullStory API Key
|
||||
GitHub | GitHub {% data variables.product.pat_generic_title_case %}
|
||||
GitHub | GitHub OAuth Access Token
|
||||
GitHub | GitHub Refresh Token
|
||||
GitHub | GitHub App Installation Access Token
|
||||
GitHub | GitHub SSH Private Key
|
||||
GoCardless | GoCardless Live Access Token
|
||||
GoCardless | GoCardless Sandbox Access Token
|
||||
Google Cloud | Google API Key
|
||||
Google Cloud | Google Cloud Private Key ID
|
||||
Hashicorp Terraform | Terraform Cloud / Enterprise API Token
|
||||
Hubspot | Hubspot API Key
|
||||
Hubspot | Hubspot API Personal Access Key
|
||||
Ionic | Ionic {% data variables.product.pat_generic_title_case %}
|
||||
Ionic | Ionic Refresh Token
|
||||
JD Cloud | JD Cloud Access Key
|
||||
Linear | Linear API Key
|
||||
Linear | Linear OAuth Access Token
|
||||
Mailchimp | Mailchimp API Key
|
||||
Mailchimp | Mandrill API Key
|
||||
Mailgun | Mailgun API Key
|
||||
MessageBird | MessageBird API Key
|
||||
Meta | Facebook Access Token
|
||||
npm | npm Access Token
|
||||
NuGet | NuGet API Key
|
||||
Octopus Deploy | Octopus Deploy API Key
|
||||
OpenAI | OpenAI API Key
|
||||
Palantir | Palantir JSON Web Token
|
||||
PlanetScale | PlanetScale Database Password
|
||||
PlanetScale | PlanetScale OAuth Token
|
||||
PlanetScale | PlanetScale Service Token
|
||||
Plivo | Plivo Auth ID and Token
|
||||
Postman | Postman API Key
|
||||
Prefect | Prefect Server API Key
|
||||
Prefect | Prefect User API Token
|
||||
Proctorio | Proctorio Consumer Key
|
||||
Proctorio | Proctorio Linkage Key
|
||||
Proctorio | Proctorio Registration Key
|
||||
Proctorio | Proctorio Secret Key
|
||||
Pulumi | Pulumi Access Token
|
||||
PyPI | PyPI API Token
|
||||
ReadMe | ReadMe API Access Key
|
||||
Finicity | Clé d’application Finicity
|
||||
Frame.io | Jeton web JSON Frame.io
|
||||
Frame.io| Jeton de développeur Frame.io
|
||||
Fullstory| Clé API FullStory
|
||||
GitHub | {% data variables.product.pat_generic_title_case %} GitHub
|
||||
GitHub | Jeton d’accès OAuth GitHub
|
||||
GitHub | Jeton d’actualisation GitHub
|
||||
GitHub | Jeton d’accès d’installation d’application GitHub
|
||||
GitHub | Clé privée SSH GitHub
|
||||
GoCardless | Jeton d’accès dynamique GoCardless
|
||||
GoCardless | Jeton d’accès de bac à sable GoCardless
|
||||
Google Cloud | Clé API Google
|
||||
Google Cloud | ID de clé privée Google Cloud
|
||||
HashiCorp Terraform | Jeton d’API Cloud / Entreprise Terraform
|
||||
Hubspot | Clé API Hubspot
|
||||
Hubspot | Clé d’accès personnel API Hubspot
|
||||
Ionic | {% data variables.product.pat_generic_title_case %} Ionic
|
||||
Ionic | Jeton d’actualisation Ionic
|
||||
JD Cloud | Clé d’accès JD Cloud
|
||||
Linéaire | Clé API Linear
|
||||
Linéaire | Jeton d’accès OAuth Linear
|
||||
MailChimp | Clé API Mailchimp
|
||||
MailChimp | Clé API Mandrill
|
||||
Mailgun | Clé API Mailgun
|
||||
MessageBird | Clé API MessageBird
|
||||
Meta | Jeton d’accès Facebook
|
||||
npm | Jeton d’accès npm
|
||||
NuGet | Clé API NuGet
|
||||
Octopus Deploy | Clé API Octopus Deploy
|
||||
OpenAI | Clé API OpenAI
|
||||
Palantir | Jeton web JSON Palantir
|
||||
PlanetScale | Mot de passe de base de données PlanetScale
|
||||
PlanetScale | Jeton OAuth PlanetScale
|
||||
PlanetScale | Jeton de service PlanetScale
|
||||
Plivo | ID et jeton d’authentification Plivo
|
||||
postman | Clé API Postman
|
||||
Prefect | Clé API du serveur Prefect
|
||||
Prefect | Jeton d’API utilisateur Prefect
|
||||
Proctorio | Clé de consommateur Proctorio
|
||||
Proctorio | Clé de liaison Proctorio
|
||||
Proctorio | Clé d’inscription proctorio
|
||||
Proctorio | Clé secrète Proctorio
|
||||
Pulumi | Jeton d’accès Pulumi
|
||||
PyPI | Jeton d’API PyPI
|
||||
ReadMe | Clé d’accès de l’API ReadMe
|
||||
redirect.pizza | redirect.pizza API Token
|
||||
RubyGems | RubyGems API Key
|
||||
Samsara | Samsara API Token
|
||||
Samsara | Samsara OAuth Access Token
|
||||
SendGrid | SendGrid API Key
|
||||
Sendinblue | Sendinblue API Key
|
||||
Sendinblue | Sendinblue SMTP Key
|
||||
Shopify | Shopify App Shared Secret
|
||||
Shopify | Shopify Access Token
|
||||
Shopify | Shopify Custom App Access Token
|
||||
Shopify | Shopify Private App Password
|
||||
Slack | Slack API Token
|
||||
Slack | Slack Incoming Webhook URL
|
||||
Slack | Slack Workflow Webhook URL
|
||||
SSLMate | SSLMate API Key
|
||||
SSLMate | SSLMate Cluster Secret
|
||||
Stripe | Stripe Live API Secret Key
|
||||
Stripe | Stripe Test API Secret Key
|
||||
Stripe | Stripe Live API Restricted Key
|
||||
Stripe | Stripe Test API Restricted Key
|
||||
Supabase | Supabase Service Key
|
||||
Tencent Cloud | Tencent Cloud Secret ID
|
||||
Tencent WeChat | Tencent WeChat API App ID
|
||||
Twilio | Twilio Account String Identifier
|
||||
Twilio | Twilio API Key
|
||||
Typeform | Typeform {% data variables.product.pat_generic_title_case %}
|
||||
Uniwise | WISEflow API Key
|
||||
Valour | Valour Access Token
|
||||
Yandex | Yandex.Cloud API Key
|
||||
Yandex | Yandex.Cloud IAM Cookie
|
||||
Yandex | Yandex.Cloud IAM Token
|
||||
Yandex | Yandex.Dictionary API Key
|
||||
Yandex | Yandex.Cloud Access Secret
|
||||
Yandex | Yandex.Passport OAuth Token
|
||||
Zuplo | Zuplo Consumer API
|
||||
RubyGems | Clé API RubyGems
|
||||
Samsara | Jeton d’API Samsara
|
||||
Samsara | Jeton d’accès OAuth Samsara
|
||||
SendGrid | Clé API SendGrid
|
||||
Sendinblue | Clé API Sendinblue
|
||||
Sendinblue | Clé SMTP Sendinblue
|
||||
Shopify | Secret partagé d’application Shopify
|
||||
Shopify | Jeton d’accès Shopify
|
||||
Shopify | Jeton d’accès d’application personnalisée Shopify
|
||||
Shopify | Mot de passe d’application privée Shopify
|
||||
Slack | Jeton d’API Slack
|
||||
Slack | URL du webhook entrant Slack
|
||||
Slack | URL du webhook de workflow Slack
|
||||
SSLMate | Clé API SSLMate
|
||||
SSLMate | Secret de cluster SSLMate
|
||||
Stripe | Clé secrète d’API dynamique Stripe
|
||||
Stripe | Clé secrète d’API de test Stripe
|
||||
Stripe | Clé restreinte d’API dynamique Stripe
|
||||
Stripe | Clé restreinte d’API de test Stripe
|
||||
Supabase | Clé de service Supabase
|
||||
Tencent Cloud | ID de secret Tencent Cloud
|
||||
Tencent WeChat | ID d’application de l’API Tencent WeChat
|
||||
Twilio | Identificateur de chaîne de compte Twilio
|
||||
Twilio | Clé API Twilio
|
||||
Typeform | {% data variables.product.pat_generic_title_case %} Typeform
|
||||
Uniwise | Clé API WISEflow
|
||||
Valour | Jeton d’accès Valour
|
||||
Yandex | Clé API Yandex.Cloud
|
||||
Yandex | Cookie IAM Yandex.Cloud
|
||||
Yandex | Jeton Yandex.Cloud
|
||||
Yandex | Clé API Yandex.Dictionary
|
||||
Yandex | Secret d’accès Yandex.Cloud
|
||||
Yandex | Jeton OAuth Yandex.Passport
|
||||
Zuplo | API consommateur Zuplo
|
||||
|
||||
@@ -1,235 +1,267 @@
|
||||
meta:
|
||||
default_description: "Démarrez, dépannez et tirez le meilleur parti de GitHub. Documentation pour les nouveaux utilisateurs, développeurs et administrateurs et pour tous les produits GitHub."
|
||||
default_description: Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
|
||||
header:
|
||||
github_docs: Documentation GitHub
|
||||
github_docs: GitHub Docs
|
||||
contact: Contact
|
||||
notices:
|
||||
ghae_silent_launch: GitHub AE est actuellement en version limitée.
|
||||
ghae_silent_launch: GitHub AE is currently under limited release.
|
||||
release_candidate:
|
||||
# The version name is rendered before the below text via includes/header-notification.html
|
||||
' est actuellement disponible en tant que version Release Candidate. Pour plus d’informations, consultez « <a href="/admin/overview/about-upgrades-to-new-releases">À propos des mises à niveau vers les nouvelles versions</a> »'
|
||||
' is currently available as a release candidate. For more information, see "<a href="/admin/overview/about-upgrades-to-new-releases">About upgrades to new releases</a>."'
|
||||
localization_complete:
|
||||
"Nous publions des mises à jour fréquentes de notre documentation, et la traduction de cette page peut encore être en cours. Pour obtenir les informations les plus récentes, veuillez consulter la <a id=\"to-english-doc\" href=\"/en\">Documentation en anglais</a>."
|
||||
early_access: 📣 Veuillez <b>ne pas partager</b> cette URL publiquement. Cette page contient du contenu sur une fonctionnalité en accès anticipé.
|
||||
release_notes_use_latest: "Veuillez utiliser la dernière version pour bénéficier des dernières mises à jour de sécurité, de performances et de bogues."
|
||||
We publish frequent updates to our documentation, and translation of this page may still be in progress.
|
||||
For the most current information, please visit the
|
||||
<a id="to-english-doc" href="/en">English documentation</a>.
|
||||
early_access: 📣 Please <b>do not share</b> this URL publicly. This page contains content about an early access feature.
|
||||
release_notes_use_latest: Please use the latest release for the latest security, performance, and bug fixes.
|
||||
# GHES release notes
|
||||
ghes_release_notes_upgrade_patch_only: "📣 Il ne s’agit pas de la <a href=\"#{{ latestPatch }}\">dernière version de correctif</a> d’Enterprise Server."
|
||||
ghes_release_notes_upgrade_release_only: "📣 Il ne s’agit pas de la <a href=\"/enterprise-server@{{ latestRelease }}/admin/release-notes\">dernière version</a> d’Enterprise Server."
|
||||
ghes_release_notes_upgrade_patch_and_release: "📣 Il ne s’agit pas de la <a href=\"#{{ latestPatch }}\">dernière version de correctif</a> de cette série de versions, ni de la <a href=\"/enterprise-server@{{ latestRelease }}/admin/release-notes\">dernière version</a> d’Enterprise Server."
|
||||
sign_up_cta: Inscription
|
||||
ghes_release_notes_upgrade_patch_only: 📣 This is not the <a href="#{{ latestPatch }}">latest patch release</a> of Enterprise Server.
|
||||
ghes_release_notes_upgrade_release_only: 📣 This is not the <a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">latest release</a> of Enterprise Server.
|
||||
ghes_release_notes_upgrade_patch_and_release: 📣 This is not the <a href="#{{ latestPatch }}">latest patch release</a> of this release series, and this is not the <a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">latest release</a> of Enterprise Server.
|
||||
sign_up_cta: Sign up
|
||||
picker:
|
||||
language_picker_default_text: Choisir une langue
|
||||
product_picker_default_text: Tous les produits
|
||||
version_picker_default_text: Choisir une version
|
||||
language_picker_default_text: Choose a language
|
||||
product_picker_default_text: All products
|
||||
version_picker_default_text: Choose a version
|
||||
release_notes:
|
||||
banner_text: GitHub a commencé à déployer ces changements pour les entreprises le
|
||||
banner_text: GitHub began rolling these changes out to enterprises on
|
||||
search:
|
||||
need_help: Vous avez besoin d’aide ?
|
||||
placeholder: Recherche dans la documentation GitHub
|
||||
loading: Chargement
|
||||
no_results: Aucun résultat trouvé.
|
||||
search_results_for: Résultats de recherche pour
|
||||
no_content: Aucun contenu
|
||||
matches_displayed: Correspondances affichées
|
||||
search_error: Une erreur s’est produite lors de la tentative de recherche.
|
||||
description: Entrez un terme de recherche pour le trouver dans la documentation GitHub.
|
||||
label: Recherche dans la documentation GitHub
|
||||
results_found: "{n} résultats trouvés en {s} ms"
|
||||
results_page: "Page {page} sur {pages}."
|
||||
nothing_found: Aucun résultat trouvé 😿
|
||||
need_help: Need help?
|
||||
placeholder: Search GitHub Docs
|
||||
loading: Loading
|
||||
no_results: No results found
|
||||
search_results_for: Search results for
|
||||
no_content: No content
|
||||
matches_found: Results found
|
||||
matches_displayed: Matches displayed
|
||||
search_error: An error occurred trying to perform the search.
|
||||
description: Enter a search term to find it in the GitHub Documentation.
|
||||
label: Search GitHub Docs
|
||||
results_found: Found {n} results in {s}ms
|
||||
results_page: This is page {page} of {pages}.
|
||||
nothing_found: Nothing found 😿
|
||||
homepage:
|
||||
explore_by_product: Explorer par produit
|
||||
explore_by_product: Explore by product
|
||||
version_picker: Version
|
||||
description: "De l’aide, où que vous en soyez dans votre parcours sur GitHub."
|
||||
description: Help for wherever you are on your GitHub journey.
|
||||
toc:
|
||||
getting_started: Prise en main
|
||||
popular: Populaire
|
||||
getting_started: Getting started
|
||||
popular: Popular
|
||||
guides: Guides
|
||||
whats_new: Nouveautés
|
||||
videos: Vidéos
|
||||
all_changelogs: Tous les messages du journal des modifications
|
||||
whats_new: What's new
|
||||
videos: Videos
|
||||
all_changelogs: All changelog posts
|
||||
pages:
|
||||
article_version: 'Version de l’article'
|
||||
miniToc: Contenu de cet article
|
||||
contributor_callout: Cet article est rédigé et mis à jour par
|
||||
all_enterprise_releases: Toutes les versions d’Enterprise Server
|
||||
about_versions: À propos des versions
|
||||
article_version: 'Article version'
|
||||
miniToc: In this article
|
||||
contributor_callout: This article is contributed and maintained by
|
||||
all_enterprise_releases: All Enterprise Server releases
|
||||
about_versions: About versions
|
||||
permissions_statement: Who can use this feature
|
||||
errors:
|
||||
oops: Oups !
|
||||
something_went_wrong: Un problème est survenu.
|
||||
we_track_errors: "Nous suivons ces erreurs automatiquement, mais si le problème persiste, n’hésitez pas à nous contacter."
|
||||
page_doesnt_exist: Il semble que cette page n’existe pas.
|
||||
oops: Ooops!
|
||||
something_went_wrong: It looks like something went wrong.
|
||||
we_track_errors: We track these errors automatically, but if the problem persists please feel free to contact us.
|
||||
page_doesnt_exist: It looks like this page doesn't exist.
|
||||
support:
|
||||
still_need_help: Vous avez encore besoin d’aide ?
|
||||
contact_support: Contacter le support technique
|
||||
ask_community: Demander à la communauté GitHub
|
||||
still_need_help: Still need help?
|
||||
contact_support: Contact support
|
||||
ask_community: Ask the GitHub community
|
||||
survey:
|
||||
able_to_find: Ce document vous a-t-il aidé ?
|
||||
able_to_find: Did this doc help you?
|
||||
yes: Yes
|
||||
no: No
|
||||
comment_yes_label: Faites-nous savoir ce que nous faisons bien
|
||||
comment_no_label: Faites-nous savoir ce que nous pouvons faire mieux
|
||||
optional: Facultatif
|
||||
required: Obligatoire
|
||||
comment_yes_label: Let us know what we do well
|
||||
comment_no_label: Let us know what we can do better
|
||||
optional: Optional
|
||||
required: Required
|
||||
email_placeholder: email@example.com
|
||||
email_label: "Si nous pouvons vous contacter pour d’autres questions, veuillez indiquer votre adresse e-mail"
|
||||
email_validation: Entrez une adresse e-mail valide
|
||||
send: Envoyer
|
||||
feedback: Merci ! Nous avons reçu vos commentaires.
|
||||
not_support: "Si vous avez besoin d’une réponse, veuillez plutôt contacter le service de support."
|
||||
privacy_policy: Politique de confidentialité
|
||||
email_label: If we can contact you with more questions, please enter your email address
|
||||
email_validation: Please enter a valid email address
|
||||
send: Send
|
||||
feedback: Thank you! We received your feedback.
|
||||
not_support: If you need a reply, please contact support instead.
|
||||
privacy_policy: Privacy policy
|
||||
contribution_cta:
|
||||
title: Aidez-nous à rendre ces documents formidables !
|
||||
body: Toute la documentation GitHub est open source. Vous voyez quelque chose qui n’est pas correct ou qui n’est pas clair ? Envoyez une demande de tirage.
|
||||
button: Faire une contribution
|
||||
or: "Ou,"
|
||||
to_guidelines: découvrez comment contribuer.
|
||||
title: Help us make these docs great!
|
||||
body: All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.
|
||||
button: Make a contribution
|
||||
or: Or,
|
||||
to_guidelines: learn how to contribute.
|
||||
parameter_table:
|
||||
body: Body parameters
|
||||
default: Default
|
||||
description: Description
|
||||
enum_description_title: Can be one of
|
||||
headers: Headers
|
||||
name: Name
|
||||
path: Path parameters
|
||||
query: Query parameters
|
||||
required: Required
|
||||
see_preview_notice: See preview notice
|
||||
see_preview_notices: See preview notices
|
||||
type: Type
|
||||
single_enum_description: Value
|
||||
products:
|
||||
graphql:
|
||||
reference:
|
||||
implements: Implémentations
|
||||
fields: Champs
|
||||
implements: Implements
|
||||
fields: Fields
|
||||
arguments: Arguments
|
||||
name: Nom
|
||||
name: Name
|
||||
type: Type
|
||||
description: Description
|
||||
input_fields: Champs d’entrée
|
||||
return_fields: Champs de retour
|
||||
implemented_by: Implémenté dans
|
||||
values: Valeurs
|
||||
possible_types: Types possibles
|
||||
preview_notice: Avis de préversion
|
||||
deprecation_notice: Note relative à la suppression de fonctionnalités
|
||||
preview_period: "Pendant la période de préversion, l’API peut être modifiée sans préavis."
|
||||
input_fields: Input fields
|
||||
return_fields: Return fields
|
||||
implemented_by: Implemented by
|
||||
values: Values
|
||||
possible_types: Possible types
|
||||
preview_notice: Preview notice
|
||||
deprecation_notice: Deprecation notice
|
||||
preview_period: During the preview period, the API may change without notice.
|
||||
overview:
|
||||
preview_header: 'Pour activer cette préversion et accéder aux membres du schéma suivants, vous devez fournir un type de média personnalisé dans l’en-tête `Accept` :'
|
||||
preview_schema_members: 'Membres du schéma en préversion'
|
||||
announced: Annoncé
|
||||
updates: Mises à jour
|
||||
preview_header: 'To toggle this preview and access the following schema members, you must provide a custom media type in the `Accept` header:'
|
||||
preview_schema_members: 'Previewed schema members'
|
||||
announced: Announced
|
||||
updates: Updates
|
||||
rest:
|
||||
banner:
|
||||
api_versioned: The REST API is now versioned.
|
||||
api_version_info: For more information, see "<a href="{{ versionWithApiVersion }}/rest/overview/api-versions">About API versioning</a>".
|
||||
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "<a href="/{{ currentVersion }}/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server">About versions of GitHub Docs</a>".
|
||||
versioning:
|
||||
about_versions: About REST API versions
|
||||
reference:
|
||||
default: Default
|
||||
name: Nom
|
||||
in: Dans
|
||||
type: Type
|
||||
in: In
|
||||
description: Description
|
||||
notes: Notes
|
||||
parameters: Paramètres
|
||||
response: response
|
||||
example_response: Exemple de réponse
|
||||
status_code: Code d’état
|
||||
http_status_code: Codes de statut de réponse HTTP
|
||||
code_sample: Exemple de code
|
||||
code_samples: Exemples de code
|
||||
preview_notice: Avis de préversion
|
||||
preview_notices: Avis de préversions
|
||||
see_preview_notice: Voir l’avis de préversion
|
||||
see_preview_notices: Voir les avis de préversions
|
||||
preview_header_is_required: Cet en-tête est <strong>requis</strong>
|
||||
preview_notice_to_change: Cette API est en cours d’élaboration et est susceptible d’être modifiée
|
||||
works_with: Fonctionne avec
|
||||
api_reference: Référence d’API REST
|
||||
enum_description_title: Peut être
|
||||
required: Obligatoire
|
||||
headers: headers
|
||||
query: Paramètres de requête
|
||||
path: Paramètres de chemin d’accès
|
||||
body: Paramètres du corps
|
||||
parameters: Parameters
|
||||
response: Response
|
||||
example_response: Example response
|
||||
status_code: Status code
|
||||
http_status_code: HTTP response status codes
|
||||
code_sample: Code sample
|
||||
code_samples: Code samples
|
||||
preview_notice: Preview notice
|
||||
preview_notices: Preview notices
|
||||
preview_header_is_required: This header is <strong>required</strong>
|
||||
preview_notice_to_change: This API is under preview and subject to change
|
||||
works_with: Works with
|
||||
api_reference: REST API reference
|
||||
enum_description_title: Can be one of
|
||||
required: Required
|
||||
headers: Headers
|
||||
query: Query parameters
|
||||
path: Path parameters
|
||||
body: Body parameters
|
||||
webhooks:
|
||||
action_type_switch_error: There was an error switching webhook action types.
|
||||
action_type: Action type
|
||||
availability: Availability
|
||||
webhook_payload_object: Webhook payload object
|
||||
webhook_payload_example: Webhook payload example
|
||||
rephrase_availability:
|
||||
repository: Repositories
|
||||
organization: Organizations
|
||||
app: GitHub Apps
|
||||
business: Enterprises
|
||||
marketplace: GitHub Marketplace
|
||||
sponsors_listing: Sponsored accounts
|
||||
footer:
|
||||
all_rights_reserved: Tous droits réservés
|
||||
terms: Termes
|
||||
privacy: Confidentialité
|
||||
security: Sécurité
|
||||
all_rights_reserved: All rights reserved
|
||||
terms: Terms
|
||||
privacy: Privacy
|
||||
security: Security
|
||||
product:
|
||||
heading: Produit
|
||||
heading: Product
|
||||
links:
|
||||
features: Fonctionnalités
|
||||
security: Sécurité
|
||||
enterprise: Entreprise
|
||||
case_studies: Études de cas
|
||||
pricing: Tarifs
|
||||
resources: Ressources
|
||||
features: Features
|
||||
security: Security
|
||||
enterprise: Enterprise
|
||||
case_studies: Case Studies
|
||||
pricing: Pricing
|
||||
resources: Resources
|
||||
platform:
|
||||
heading: Plateforme
|
||||
heading: Platform
|
||||
links:
|
||||
developer_api: API pour les développeurs
|
||||
partners: Partenaires
|
||||
developer_api: Developer API
|
||||
partners: Partners
|
||||
atom: Atom
|
||||
electron: Electron
|
||||
github_desktop: GitHub Desktop
|
||||
support:
|
||||
heading: Support
|
||||
links:
|
||||
help: Aide
|
||||
community_forum: Forum de la communauté
|
||||
training: Entrainement
|
||||
status: Statut
|
||||
contact_github: Contacter GitHub
|
||||
help: Help
|
||||
community_forum: Community Forum
|
||||
training: Training
|
||||
status: Status
|
||||
contact_github: Contact GitHub
|
||||
company:
|
||||
heading: Company
|
||||
links:
|
||||
about: À propos
|
||||
about: About
|
||||
blog: Blog
|
||||
careers: Carrières
|
||||
press: Appuyez sur
|
||||
careers: Careers
|
||||
press: Press
|
||||
shop: Shop
|
||||
product_landing:
|
||||
quickstart: Démarrage rapide
|
||||
reference: Informations de référence
|
||||
overview: Vue d’ensemble
|
||||
quickstart: Quickstart
|
||||
reference: Reference
|
||||
overview: Overview
|
||||
guides: Guides
|
||||
code_examples: Exemples de code
|
||||
search_code_examples: Rechercher des exemples de code
|
||||
search_results_for: Résultats de recherche pour
|
||||
matches_displayed: Correspondances affichées
|
||||
show_more: Montrer la suite
|
||||
explore_people_and_projects: Explorer les personnes et les projets
|
||||
sorry: "Désolé, il n’y a pas de résultat pour"
|
||||
no_example: Il semble que nous n’ayons pas d’exemple qui corresponde à votre filtre.
|
||||
try_another: Essayez un autre filtre ou ajoutez votre exemple de code.
|
||||
no_result: "Désolé, il n’y a pas de guides qui correspondent à votre filtre."
|
||||
learn: Apprendre à ajouter un exemple de code
|
||||
communities_using_discussions: Communautés sur GitHub.com utilisant des discussions
|
||||
add_your_community: Ajouter votre communauté
|
||||
sponsor_community: Communauté des sponsors GitHub
|
||||
supported_releases: Versions prises en charge
|
||||
release_notes_for: Notes de publication pour
|
||||
upgrade_from: Mise à niveau à partir de
|
||||
browse_all_docs: Parcourir tous les documents
|
||||
browse_all: Parcourir tout
|
||||
code_examples: Code examples
|
||||
search_code_examples: Search code examples
|
||||
search_results_for: Search results for
|
||||
matches_displayed: Matches displayed
|
||||
show_more: Show more
|
||||
explore_people_and_projects: Explore people and projects
|
||||
sorry: Sorry, there is no result for
|
||||
no_example: It looks like we don't have an example that fits your filter.
|
||||
try_another: Try another filter or add your code example.
|
||||
no_result: Sorry, there are no guides that match your filter.
|
||||
learn: Learn how to add a code example
|
||||
communities_using_discussions: Communities on GitHub.com using discussions
|
||||
add_your_community: Add your community
|
||||
sponsor_community: GitHub Sponsors community
|
||||
supported_releases: Supported releases
|
||||
release_notes_for: Release notes for
|
||||
upgrade_from: Upgrade from
|
||||
browse_all_docs: Browse all docs
|
||||
browse_all: Browse all
|
||||
docs: docs
|
||||
explore_release_notes: Explorer les notes de mise en production
|
||||
view: Afficher tout
|
||||
explore_release_notes: Explore release notes
|
||||
view: View all
|
||||
product_guides:
|
||||
start_path: Commencer un parcours d’apprentissage
|
||||
learning_paths: 'Chemins d’apprentissage {{ productMap[currentProduct].name }}'
|
||||
learning_paths_desc: Les parcours d’apprentissage sont une collection d’articles qui vous aident à maîtriser un sujet particulier.
|
||||
guides: 'Guides {{ productMap[currentProduct].name }}'
|
||||
more_guides: plus de guides
|
||||
load_more: Charger plus de guides
|
||||
all_guides: 'Tous les guides {{ productMap[currentProduct].name }}'
|
||||
filter_instructions: Filtrer la liste des guides à l’aide de ces commandes
|
||||
start_path: Start learning path
|
||||
learning_paths: '{{ productMap[currentProduct].name }} learning paths'
|
||||
learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject.
|
||||
guides: '{{ productMap[currentProduct].name }} guides'
|
||||
more_guides: more guides
|
||||
load_more: Load more guides
|
||||
all_guides: 'All {{ productMap[currentProduct].name }} guides'
|
||||
filter_instructions: Filter the guide list using these controls
|
||||
filters:
|
||||
type: Type
|
||||
topic: Rubrique
|
||||
all: Tous
|
||||
topic: Topic
|
||||
all: All
|
||||
guides_found:
|
||||
multiple: '{n} guides trouvés'
|
||||
one: 1 guide trouvé
|
||||
none: Aucun guide trouvé
|
||||
multiple: '{n} guides found'
|
||||
one: 1 guide found
|
||||
none: No guides found
|
||||
guide_types:
|
||||
overview: Vue d’ensemble
|
||||
quick_start: Démarrage rapide
|
||||
tutorial: Didacticiel
|
||||
how_to: Guide pratique
|
||||
reference: Informations de référence
|
||||
overview: Overview
|
||||
quick_start: Quickstart
|
||||
tutorial: Tutorial
|
||||
how_to: How-to guide
|
||||
reference: Reference
|
||||
learning_track_nav:
|
||||
prevGuide: Guide précédent
|
||||
nextGuide: Guide suivant
|
||||
prevGuide: Previous guide
|
||||
nextGuide: Next guide
|
||||
toggle_images:
|
||||
off: "Les images sont désactivées, cliquez pour les afficher"
|
||||
on: "Les images sont activées, cliquez pour les masquer"
|
||||
hide_single: Masquer l’image
|
||||
show_single: Afficher l’image
|
||||
off: Images are off, click to show
|
||||
on: Images are on, click to hide
|
||||
hide_single: Hide image
|
||||
show_single: Show image
|
||||
scroll_button:
|
||||
scroll_to_top: Faire défiler vers le sommet
|
||||
scroll_to_top: Scroll to top
|
||||
|
||||
@@ -23,7 +23,6 @@ prodname_ghe_cloud: 'GitHub Enterprise Cloud'
|
||||
prodname_ghe_managed: 'GitHub AE'
|
||||
prodname_ghe_one: 'GitHub One'
|
||||
prodname_docs: 'GitHub Docs'
|
||||
|
||||
prodname_free_user: 'GitHub Free'
|
||||
prodname_pro: 'GitHub Pro'
|
||||
prodname_team: 'GitHub Team'
|
||||
|
||||
@@ -25,7 +25,7 @@ By default, authorized users can access your enterprise from any IP address. You
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
@@ -45,8 +45,6 @@ You can use {% data variables.product.company_short %}'s IP allow list to contro
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
|
||||
|
||||
You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
|
||||
|
||||
## About your IdP's allow list
|
||||
|
||||
If you are using {% data variables.product.prodname_emus %} with OIDC, you can use your IdP's allow list.
|
||||
@@ -134,7 +132,7 @@ You can use your IdP's allow list if you use {% data variables.product.prodname_
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
- Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring SAML single sign-on for your enterprise
|
||||
title: 엔터프라이즈에 대한 SAML Single Sign-On 구성
|
||||
shortTitle: Configure SAML SSO
|
||||
intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghes or ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).'
|
||||
intro: '리포지토리, 문제 등의 {% ifversion ghec %}리소스에 대한 액세스를 제어하고 보호할 수 있습니다. 및 엔터프라이즈 조직 내 끌어오기 요청{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}ID 공급자(IdP)를 통해 {% elsif ghes or ghae %}구성{% endif %} SAML SSO(Single Sign-On)를 적용합니다.'
|
||||
permissions: '{% ifversion ghes %}Site administrators{% elsif ghec or ghae %}Enterprise owners{% endif %} can configure SAML SSO for {% ifversion ghec or ghae %}an enterprise on {% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.product_name %} instance{% endif %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
@@ -21,11 +21,16 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account
|
||||
- /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
|
||||
- /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
|
||||
ms.openlocfilehash: 804ba3b262aae15b862e1a14694b82339c8d34a4
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148183958'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-saml-note %}
|
||||
|
||||
## About SAML SSO
|
||||
## SAML SSO 정보
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
@@ -33,21 +38,21 @@ redirect_from:
|
||||
|
||||
{% data reusables.saml.saml-accounts %}
|
||||
|
||||
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)."
|
||||
자세한 내용은 “[SAML Single Sign-On을 사용한 ID 및 액세스 관리 정보](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”를 참조하세요.
|
||||
|
||||
{% data reusables.saml.about-saml-enterprise-accounts %}
|
||||
|
||||
{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
|
||||
{% data reusables.saml.about-saml-access-enterprise-account %} 자세한 내용은 "[엔터프라이즈 계정에 대한 사용자의 SAML 액세스 보기 및 관리](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"를 참조하세요.
|
||||
|
||||
{% data reusables.saml.saml-disabled-linked-identities-removed %}
|
||||
|
||||
{% data reusables.scim.enterprise-account-scim %}
|
||||
{% data reusables.apps.reauthorize-apps-saml %}
|
||||
|
||||
{% elsif ghes or ghae %}
|
||||
|
||||
SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user.
|
||||
SAML SSO를 사용하면 SAML IdP에서 {% data variables.location.product_location %}에 대한 액세스를 중앙에서 제어하고 보호할 수 있습니다. 인증되지 않은 사용자가 브라우저에서 {% data variables.location.product_location %}를 방문하면 {% data variables.product.product_name %}는 사용자를 SAML IdP로 리디렉션하여 인증합니다. 사용자가 IdP의 계정으로 성공적으로 인증되면 IdP는 사용자를 {% data variables.location.product_location %}로 다시 리디렉션합니다. {% data variables.product.product_name %}는 IdP에서 응답의 유효성을 검사한 다음, 사용자에게 액세스 권한을 부여합니다.
|
||||
|
||||
After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.location.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP.
|
||||
사용자가 IdP에서 성공적으로 인증되면 {% data variables.location.product_location %}에 대한 사용자의 SAML 세션이 브라우저에서 24시간 동안 활성화됩니다. 24시간이 지나면 사용자는 IdP에서 다시 인증을 받아야 합니다.
|
||||
|
||||
{% data reusables.saml.saml-ghes-account-revocation %}
|
||||
|
||||
@@ -55,176 +60,161 @@ After a user successfully authenticates on your IdP, the user's SAML session for
|
||||
|
||||
{% data reusables.saml.assert-the-administrator-attribute %}
|
||||
|
||||
{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
|
||||
{% data reusables.scim.after-you-configure-saml %} 자세한 내용은 “[엔터프라이즈에 대한 사용자 프로비저닝 구성](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”을 참조하세요.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Supported identity providers
|
||||
## 지원되는 ID 공급자
|
||||
|
||||
{% data reusables.saml.saml-supported-idps %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Username considerations with SAML
|
||||
## SAML을 사용하는 사용자 이름 고려 사항
|
||||
|
||||
{% ifversion ghec %}If you use {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
|
||||
{% ifversion ghec %} {% data variables.product.prodname_emus %}를 사용하는 경우 {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} 자세한 내용은 "[외부 인증에 대한 사용자 이름 고려 사항](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)"을 참조하세요.
|
||||
|
||||
## Enforcing SAML single-sign on for organizations in your enterprise account
|
||||
## 엔터프라이즈 계정의 조직에서 SAML Single Sign-On 적용
|
||||
|
||||
{% note %}
|
||||
엔터프라이즈에 SAML SSO를 적용하면 엔터프라이즈 구성이 기존 조직 수준 SAML 구성을 재정의합니다. {% data reusables.saml.switching-from-org-to-enterprise %} 자세한 내용은 “[조직에서 엔터프라이즈 계정으로 SAML 구성 전환](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)”을 참조하세요.
|
||||
|
||||
**Notes:**
|
||||
조직에 SAML SSO를 적용하면 {% data variables.product.company_short %}는 SAML IdP에서 성공적으로 인증되지 않은 조직의 멤버를 제거합니다. 엔터프라이즈에 SAML SSO가 필요한 경우 {% data variables.product.company_short %}는 SAML IdP에서 성공적으로 인증되지 않은 엔터프라이즈의 멤버를 제거하지 않습니다. 다음에 멤버가 엔터프라이즈의 리소스에 액세스할 때 멤버는 SAML IdP에서 인증을 받아야 합니다.
|
||||
|
||||
- When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
|
||||
- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
|
||||
OKTA 사용하여 SAML을 사용하도록 설정하는 방법에 대한 자세한 내용은 "[Okta를 사용하여 엔터프라이즈 계정에 대해 SAML Single Sign-On 구성](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"을 참조하세요.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)."
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
|
||||
5. Under "SAML single sign-on", select **Require SAML authentication**.
|
||||
|
||||
6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
|
||||
|
||||
7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages.
|
||||
|
||||
8. Under **Public Certificate**, paste a certificate to verify SAML responses.
|
||||
|
||||
9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer.
|
||||
|
||||
10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. 
|
||||
11. Click **Save**.
|
||||
5. "SAML Single Sign-On"에서 **SAML 인증 필요** 를 선택합니다.
|
||||
|
||||
6. **로그온 URL** 필드에서 Single Sign-On 요청에 대한 IdP의 HTTPS 엔드포인트를 입력합니다. 이 값은 IdP 구성에서 사용할 수 있습니다.
|
||||
|
||||
7. 필요에 따라 **발급자** 필드에 SAML 발급자 URL을 입력하여 보낸 메시지의 신뢰성을 확인합니다.
|
||||
|
||||
8. **퍼블릭 인증서** 아래에 인증서를 붙여넣어 SAML 응답을 확인합니다.
|
||||
|
||||
9. SAML 발급자의 요청 무결성을 확인하려면 {% octicon "pencil" aria-label="The edit icon" %}을 클릭합니다. 그런 다음, "서명 메서드" 및 "다이제스트 메서드" 드롭다운에서 SAML 발급자가 사용하는 해시 알고리즘을 선택합니다.
|
||||
|
||||
10. 엔터프라이즈에 SAML SSO를 사용하도록 설정하기 전에 **SAML 구성 테스트** 를 클릭하여 입력한 정보가 올바른지 확인합니다. 
|
||||
11. **저장** 을 클릭합니다.
|
||||
{% data reusables.enterprise-accounts.download-recovery-codes %}
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
## Configuring SAML SSO
|
||||
## SAML SSO 구성
|
||||
|
||||
You can enable or disable SAML authentication for {% data variables.location.product_location %}, or you can edit an existing configuration. You can view and edit authentication settings for {% data variables.product.product_name %} in the management console. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
|
||||
{% data variables.location.product_location %}에 SAML 인증을 사용하거나 사용하지 않도록 설정하거나 기존 구성을 편집할 수 있습니다. 관리 콘솔에서 {% data variables.product.product_name %}에 대한 인증 설정을 보고 편집할 수 있습니다. 자세한 내용은 “[관리 콘솔 액세스](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)”를 참조하세요.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.enterprise.test-in-staging %}
|
||||
**참고**: {% data reusables.enterprise.test-in-staging %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.authentication %}
|
||||
1. Select **SAML**.
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %}
|
||||
1. **SAML** 을 선택합니다.
|
||||
|
||||
|
||||
|
||||
1. {% data reusables.enterprise_user_management.built-in-authentication-option %}
|
||||
|
||||
|
||||
1. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP.
|
||||
|
||||
1. 필요에 따라 요청되지 않은 응답 SSO를 사용하도록 설정하려면 **IdP 시작 SSO** 를 선택합니다. 기본적으로 {% data variables.product.prodname_ghe_server %}는 원치 않는 IdP(ID 공급자) 시작 요청에 대해 IdP에 `AuthnRequest`로 회신합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}.
|
||||
**참고**: 이 값을 **선택되지 않음** 상태로 유지하는 것이 좋습니다. 드물게 SAML 구현에서 서비스 공급자가 시작한 SSO를 지원하지 않는 경우와 {% data variables.contact.enterprise_support %}에서 권고하는 경우에 **만** 이 기능을 사용하도록 설정해야 합니다.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.location.product_location %}.
|
||||
1. SAML 공급자가 {% data variables.location.product_location %}에서 사용자에 대한 관리자 권한을 결정 **하지 않** 으려면 관리자 **강등/승격 사용 안** 함을 선택합니다.
|
||||
|
||||
|
||||
{%- ifversion ghes > 3.3 %}
|
||||
1. Optionally, to allow {% data variables.location.product_location %} to receive encrypted assertions from your SAML IdP, select **Require encrypted assertions**. You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.location.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)."
|
||||
 {%- ifversion ghes > 3.3 %}
|
||||
1. 필요에 따라 {% data variables.location.product_location %}이(가) SAML IdP에서 암호화된 어설션을 수신하도록 허용하려면 **암호화된 어설션 필요를** 선택합니다. IdP가 암호화된 어설션을 지원하고 관리 콘솔의 암호화 및 키 전송 메서드가 IdP에 구성된 값과 일치하는지 확인해야 합니다. 또한 IdP에 {% data variables.location.product_location %}의 공용 인증서를 제공해야 합니다. 자세한 내용은 “[암호화된 어설션 사용](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)”을 참조하세요.
|
||||
|
||||
|
||||
{%- endif %}
|
||||
1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.location.product_location %} to use internal nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/).
|
||||
 {%- endif %}
|
||||
1. **Single Sign-On URL** 필드에서 Single Sign-On 요청에 대한 IdP에 HTTP 또는 HTTPS 엔드포인트를 입력합니다. 이 값은 IdP 구성에서 제공됩니다. 내부 네트워크에서만 호스트를 사용할 수 있는 경우 내부 [이름 서버를 사용하도록 {% data variables.location.product_location %}을 구성해야 할](/enterprise/admin/guides/installation/configuring-dns-nameservers/) 수 있습니다.
|
||||
|
||||
|
||||
1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.location.product_location %}.
|
||||
|
||||
1. 필요에 따라 **발급자** 필드에 SAML 발급자의 이름을 입력합니다. 이렇게 하면 {% data variables.location.product_location %}로 전송된 메시지의 신뢰성이 확인됩니다.
|
||||
|
||||
|
||||
1. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.location.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu.
|
||||
|
||||
1. **서명 방법** 및 **다이제스트 메서드** 드롭다운 메뉴에서 SAML 발급자에서 사용하는 해시 알고리즘을 선택하여 {% data variables.location.product_location %}에서 요청의 무결성을 확인합니다. **이름 식별자 형식** 드롭다운 메뉴를 사용하여 형식을 지정합니다.
|
||||
|
||||
|
||||
1. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP.
|
||||
|
||||
1. **확인 인증서** 에서 **파일 선택** 을 클릭하고 인증서를 선택하여 IdP에서 SAML 응답의 유효성을 검사합니다.
|
||||
|
||||
|
||||
1. Modify the SAML attribute names to match your IdP if needed, or accept the default names.
|
||||
|
||||
1. 필요한 경우 IdP와 일치하도록 SAML 특성 이름을 수정하거나 기본 이름을 적용합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
## Enabling SAML SSO
|
||||
## SAML SSO 사용
|
||||
|
||||
{% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
|
||||
|
||||
The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
|
||||
다음 IdP는 {% data variables.product.product_name %}에 대한 SAML SSO를 구성하는 방법에 대한 설명서를 제공합니다. IdP가 나열되지 않은 경우 IdP에 문의하여 {% data variables.product.product_name %}에 대한 지원을 요청하세요.
|
||||
|
||||
| IdP | More information |
|
||||
| IdP | 추가 정보 |
|
||||
| :- | :- |
|
||||
| Azure AD | "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" |
|
||||
| Okta | "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" |
|
||||
| Azure AD | "[Azure AD를 사용하여 엔터프라이즈에 대한 인증 및 프로비저닝 구성](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" |
|
||||
| Okta | "[OKTA를 사용하여 엔터프라이즈에 대한 인증 및 프로비저닝 구성](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" |
|
||||
|
||||
During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML service provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)."
|
||||
{% data variables.product.product_name %}를 초기화하는 동안 IdP에서 {% data variables.product.product_name %}를 SAML SP(서비스 공급자)로 구성해야 합니다. {% data variables.product.product_name %}를 유효한 SP로 구성하려면 IdP에 몇 가지 고유한 값을 입력해야 합니다. 자세한 내용은 "[SAML 구성 참조](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)"를 참조하세요.
|
||||
|
||||
## Editing the SAML SSO configuration
|
||||
## SAML SSO 구성 편집
|
||||
|
||||
If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.location.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate.
|
||||
IdP에 대한 세부 정보가 변경되면 {% data variables.location.product_location %}에 대한 SAML SSO 구성을 편집해야 합니다. 예를 들어 IdP에 대한 인증서가 만료되면 퍼블릭 인증서의 값을 편집할 수 있습니다.
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
|
||||
**참고**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "SAML single sign-on", type the new details for your IdP.
|
||||
|
||||
1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
1. "SAML Single Sign-On"에서 IdP에 대한 새 세부 정보를 입력합니다.
|
||||
|
||||
1. 필요에 따라 {% octicon "pencil" aria-label="The edit icon" %}을 클릭하여 새 서명 또는 다이제스트 메서드를 구성합니다.
|
||||
|
||||
|
||||
- Use the drop-down menus and choose the new signature or digest method.
|
||||
|
||||
1. To ensure that the information you've entered is correct, click **Test SAML configuration**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
1. Optionally, to automatically provision and deprovision user accounts for {% data variables.location.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
|
||||
- 드롭다운 메뉴를 사용하고 새 서명 또는 다이제스트 메서드를 선택합니다.
|
||||
|
||||
1. 입력한 정보가 올바른지 확인하려면 **SAML 구성 테스트** 를 클릭합니다.
|
||||
|
||||
1. **저장** 을 클릭합니다.
|
||||
|
||||
1. 필요에 따라 {% data variables.location.product_location %}에 대한 사용자 계정을 자동으로 프로비전 및 프로비전 해제하려면 SCIM을 사용하여 사용자 프로비저닝을 다시 구성합니다. 자세한 내용은 “[엔터프라이즈에 대한 사용자 프로비저닝 구성](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”을 참조하세요.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Disabling SAML SSO
|
||||
## SAML SSO 사용 안 함
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you disable SAML SSO for {% data variables.location.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.location.product_location %}. SAML SSO sessions on {% data variables.location.product_location %} end after 24 hours.
|
||||
**경고**: {% data variables.location.product_location %}에 SAML SSO를 사용하지 않도록 설정하면 기존 SAML SSO 세션이 없는 사용자는 {% data variables.location.product_location %}에 로그인할 수 없습니다. {% data variables.location.product_location %}의 SAML SSO 세션은 24시간 후에 종료됩니다.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
|
||||
**참고**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "SAML single sign-on", unselect **Enable SAML authentication**.
|
||||
|
||||
1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
1. "SAML Single Sign-On"에서 **SAML 인증 사용** 을 선택을 취소합니다.
|
||||
|
||||
1. SAML SSO를 사용하지 않도록 설정하고 초기화 중에 만든 기본 제공 사용자 계정으로 로그인하도록 하려면 **저장** 을 클릭합니다.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -232,13 +222,10 @@ If the details for your IdP change, you'll need to edit the SAML SSO configurati
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
|
||||
## Further reading
|
||||
## 추가 참고 자료
|
||||
|
||||
{%- ifversion ghec %}
|
||||
- "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)"
|
||||
{%- endif %}
|
||||
{%- ifversion ghes %}
|
||||
- "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)"
|
||||
{%- endif %}
|
||||
- "[조직에 대한 SAML Single Sign-On 관리](/organizations/managing-saml-single-sign-on-for-your-organization)" {%- endif %} {%- ifversion ghes %}
|
||||
- "[사이트 관리자 승격 또는 강등](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" {%- endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -28,7 +28,7 @@ topics:
|
||||
The scope of the events that appear in your enterprise's audit log depend on whether your enterprise uses {% data variables.product.prodname_emus %}. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
|
||||
|
||||
- If your enterprise does not use {% data variables.product.prodname_emus %}, the audit log only includes events related to the enterprise account and the organizations within the enterprise account, which are listed in this article.
|
||||
- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.enterprise.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)."
|
||||
- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.enterprise.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %} and actions they take within their user account. For a list of these user account events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)."
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
@@ -105,10 +105,12 @@ The scope of the events that appear in your enterprise's audit log depend on whe
|
||||
| `business.clear_members_can_create_repos` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared a restriction on repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."
|
||||
| `business.create` | An enterprise was created.
|
||||
{%- ifversion ghec %}
|
||||
| `business.disable_oidc` | OIDC single sign-on was disabled for an enterprise. For more information, see "[Configuring OIDC for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
| `business.disable_saml` | SAML single sign-on was disabled for an enterprise.
|
||||
{%- endif %}
|
||||
| `business.disable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was disabled.
|
||||
{%- ifversion ghec %}
|
||||
| `business.enable_oidc` | OIDC single sign-on was enabled for an enterprise. For more information, see "[Configuring OIDC for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
| `business.enable_saml` | SAML single sign-on was enabled for an enterprise.
|
||||
{%- endif %}
|
||||
| `business.enable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was enabled.
|
||||
@@ -1336,6 +1338,19 @@ Before you'll see `git` category actions, you must enable Git events in the audi
|
||||
| `ssh_certificate_requirement.disable` | The requirement for members to use SSH certificates to access an organization resources was disabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion sso-redirect %}
|
||||
## `sso_redirect` category actions
|
||||
|
||||
{% data reusables.enterprise-managed.sso-redirect-release-phase %}
|
||||
|
||||
| Action | Description |
|
||||
|--------|------------ |
|
||||
`sso_redirect.enable` | Automatic redirects for users to single sign-on (SSO) was enabled. |
|
||||
`sso_redirect.disable` | Automatic redirects for users to single sign-on (SSO) was disabled. |
|
||||
|
||||
For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
|
||||
{% endif %}
|
||||
|
||||
## `staff` category actions
|
||||
|
||||
| Action | Description
|
||||
|
||||
@@ -111,6 +111,7 @@ Each category has a set of associated actions that you can filter on. For exampl
|
||||
Actions that can be found in your enterprise audit log are grouped within the following categories:
|
||||
|
||||
{% data reusables.audit_log.audit-log-action-categories %}
|
||||
|
||||
### Search based on time of action
|
||||
|
||||
Use the `created` qualifier to filter events in the audit log based on when they occurred.
|
||||
|
||||
@@ -117,6 +117,10 @@ For more information about the audit log REST API, see "[Enterprise administrati
|
||||
|
||||
### Example 1: All events in an enterprise, for a specific date, with pagination
|
||||
|
||||
You can use page-based pagination or cursor based pagination. For more information, see "[Traversing with Pagination](/rest/guides/traversing-with-pagination)."
|
||||
|
||||
#### Example with page-based pagination
|
||||
|
||||
The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination):
|
||||
|
||||
```shell
|
||||
@@ -125,6 +129,32 @@ curl -H "Authorization: Bearer TOKEN" \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
|
||||
```
|
||||
|
||||
#### Example with cursor-based pagination
|
||||
|
||||
The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and returns the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination). The `--include` flag causes the headers to be returned along with the response.
|
||||
|
||||
```
|
||||
curl --include -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&per_page=100"
|
||||
```
|
||||
|
||||
If there are more than 100 results, the `link` header will include URLs to fetch the next, first, and previous pages of results.
|
||||
|
||||
```
|
||||
link: <https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=MS42NjQzODMzNTk5MjdlKzEyfDloQzBxdURzaFdVbVlLWjkxRU9mNXc%3D&before=>; rel="next",
|
||||
<https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=>; rel="first",
|
||||
<https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=MS42Njc4NDA2MjM4MzNlKzEyfExqeG5sUElvNEZMbG1XZHA5akdKTVE%3D>; rel="prev"
|
||||
```
|
||||
|
||||
Copy the corresponding pagination link into your next request. For example:
|
||||
|
||||
```shell
|
||||
curl -I -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=MS42Njc4NDA2MjM5NDFlKzEyfHRYa3AwSkxUd2xyRjA5bWxfOS1RbFE%3D&before="
|
||||
```
|
||||
|
||||
### Example 2: Events for pull requests in an enterprise, for a specific date and actor
|
||||
|
||||
You can specify multiple search phrases, such as `created` and `actor`, by separating them in your formed URL with the `+` symbol or ASCII character code `%20`.
|
||||
@@ -136,3 +166,9 @@ curl -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -84,10 +84,11 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.organizations.delete-ssh-ca %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% ifversion sso-redirect %}
|
||||
## Managing SSO for unauthenticated users
|
||||
|
||||
{% data reusables.enterprise-managed.sso-redirect-release-phase %}
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %}, you can choose what unauthenticated users see when they attempt to access your enterprise's resources. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
|
||||
|
||||
By default, to hide the existence of private resources, when an unauthenticated user attempts to access your enterprise, {% data variables.product.company_short %} displays a 404 error.
|
||||
@@ -106,11 +107,14 @@ To prevent confusion from your developers, you can change this behavior so that
|
||||
1. Under "Single sign-on settings", select or deselect **Automatically redirect users to sign in**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
|
||||
- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{%- endif %}
|
||||
- "[Keeping your organization secure](/organizations/keeping-your-organization-secure)"
|
||||
- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
|
||||
{%- ifversion ghec %}
|
||||
- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghae %}
|
||||
- "[Restricting network traffic with an IP allow list with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)"
|
||||
{%- endif %}
|
||||
|
||||
@@ -84,11 +84,11 @@ When you authorize an {% data variables.product.prodname_oauth_app %} for your p
|
||||
|
||||
- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources.
|
||||
|
||||
If you belong to any organizations that enforce SAML single sign-on, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}.
|
||||
If you belong to any organizations with SAML single sign-on (SSO) enabled, and you have created a linked identity for that organization by authenticating via SAML in the past, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you are encountering errors authenticating to an organization that enforces SAML single sign-on, you may need to revoke the OAuth App from your [account settings page](https://github.com/settings/applications) and repeat the authentication flow to reauthorize the app.
|
||||
**Note:** If you're encountering issues with an authorized {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} accessing an organization that is protected by SAML, you may need to revoke the app from your [Authorized {% data variables.product.prodname_github_apps %}](https://github.com/settings/applications) or [Authorized {% data variables.product.prodname_oauth_apps %}](https://github.com/settings/apps/authorizations) page, visit the organization to authenticate and establish an active SAML session, and then attempt to reauthorize the app by accessing it.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -25,10 +25,9 @@ shortTitle: Enable push protection
|
||||
Up to now, {% data variables.product.prodname_secret_scanning_GHAS %} checks for secrets _after_ a push and alerts users to exposed secrets. {% data reusables.secret-scanning.push-protection-overview %}
|
||||
|
||||
If a contributor bypasses a push protection block for a secret, {% data variables.product.prodname_dotcom %}:
|
||||
- generates an alert.
|
||||
- creates an alert in the "Security" tab of the repository.
|
||||
- creates an alert in the "Security" tab of the repository in the state described in the table below.
|
||||
- adds the bypass event to the audit log.{% ifversion secret-scanning-push-protection-email %}
|
||||
- sends an email alert to organization owners, security managers, and repository administrators, with a link to the related secret and the reason why it was allowed.{% endif %}
|
||||
- sends an email alert to organization owners, security managers, and repository administrators who are watching the repository, with a link to the secret and the reason why it was allowed.{% endif %}
|
||||
|
||||
{% data reusables.secret-scanning.bypass-reasons-and-alerts %}
|
||||
|
||||
|
||||
@@ -33,7 +33,7 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
|
||||
|
||||
## Supported secrets for partner patterns
|
||||
|
||||
{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
|
||||
{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers and alerts the relevant service provider whenever a secret is detected in a commit. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
|
||||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
|
||||
|
||||
@@ -37,9 +37,11 @@ You can secure the code you depend on by creating a vulnerability management pro
|
||||
|
||||
1. Create an inventory of your dependencies.
|
||||
|
||||
2. Know when there is a security vulnerability in a dependency.
|
||||
1. Know when there is a security vulnerability in a dependency.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
1. Enforce dependency reviews on your pull requests.{% endif %}
|
||||
|
||||
3. Assess the impact of that vulnerability on your code and decide what action to take.
|
||||
1. Assess the impact of that vulnerability on your code and decide what action to take.
|
||||
|
||||
### Automatic inventory generation
|
||||
|
||||
@@ -48,6 +50,11 @@ As a first step, you want to make a complete inventory of your dependencies. The
|
||||
### Automatic detection of vulnerabilities in dependencies
|
||||
|
||||
{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
### Automatic detection of vulnerabilities in pull requests
|
||||
|
||||
The {% data variables.product.prodname_dependency_review_action %} enforces a dependency review on your pull requests, making it easy for you to see if a pull request will introduce a vulnerable version of a dependency to your repository. When a vulnerability is detected, the {% data variables.product.prodname_dependency_review_action %} can block the pull request from merging. For more information, see "[Dependency review enforcement](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."{% endif %}
|
||||
|
||||
|
||||
### Assessment of exposure to risk from a vulnerable dependency
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About supply chain security
|
||||
intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes %}, and patching them{% endif %}.'
|
||||
title: 공급망 보안 정보
|
||||
intro: '{% data variables.product.product_name %}는 사용자 환경의 종속성을 이해하는 것부터 해당 종속성의 취약성에 대해 아는 것{% ifversion fpt or ghec or ghes %}, 패치{% endif %}에 이르기까지 공급망을 보호하는 데 도움이 됩니다.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Supply chain security
|
||||
redirect_from:
|
||||
@@ -19,160 +19,157 @@ topics:
|
||||
- Dependencies
|
||||
- Pull requests
|
||||
- Repositories
|
||||
ms.openlocfilehash: d0f743db7d1f5a054a3eb8c7b4dbf81052aca50f
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181238'
|
||||
---
|
||||
## GitHub의 공급망 보안 정보
|
||||
|
||||
## About supply chain security at GitHub
|
||||
오픈 소스 사용의 가속화로 인해 대부분의 프로젝트는 수백 개의 오픈 소스 종속성에 의존합니다. 해당 현상은 보안 문제를 야기합니다. 사용 중인 종속성이 취약한 경우 어떻게 해야 할까요? 사용자를 공급망 공격의 위험에 빠뜨릴 수 있습니다. 공급망을 보호하기 위해 수행할 수 있는 가장 중요한 작업 중 하나는 취약한 종속성을 패치{% ifversion GH-advisory-db-supports-malware %}하고 맬웨어를 대체{% endif %}하는 것입니다.
|
||||
|
||||
With the accelerated use of open source, most projects depend on hundreds of open-source dependencies. This poses a security problem: what if the dependencies you're using are vulnerable? You could be putting your users at risk of a supply chain attack. One of the most important things you can do to protect your supply chain is to patch your vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and replace any malware{% endif %}.
|
||||
매니페스트 파일 또는 잠금 파일에서 종속성을 지정할 때 공급망에 직접 종속성을 추가합니다. 종속성을 전이적으로 포함할 수도 있습니다. 즉, 특정 종속성을 지정하지 않더라도 자신의 종속성에서 이를 사용하므로 해당 종속성에 종속됩니다.
|
||||
|
||||
You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency.
|
||||
{% data variables.product.product_name %}은 환경의 종속성을 이해하고{% ifversion ghae %} 및 해당 종속성의 취약성에 대해 알고{% endif %}{% ifversion fpt or ghec or ghes %}, 해당 종속성의 취약성에 대해 알고, 패치하는 데 도움이 되는 다양한 기능을 제공합니다{% endif %}.
|
||||
|
||||
{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes %}, know about vulnerabilities in those dependencies, and patch them{% endif %}.
|
||||
|
||||
The supply chain features on {% data variables.product.product_name %} are:
|
||||
- **Dependency graph**
|
||||
- **Dependency review**
|
||||
- **{% data variables.product.prodname_dependabot_alerts %} **
|
||||
{% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
|
||||
{% data variables.product.product_name %}의 공급망 기능은 다음과 같습니다.
|
||||
- **종속성 그래프**
|
||||
- **종속성 검토**
|
||||
- **{% data variables.product.prodname_dependabot_alerts %} ** {% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** {% endif %}
|
||||
|
||||
The dependency graph is central to supply chain security. The dependency graph identifies all upstream dependencies and public downstream dependents of a repository or package. You can see your repository’s dependencies and some of their properties, like vulnerability information, on the dependency graph for the repository.
|
||||
종속성 그래프는 공급망 보안의 핵심입니다. 종속성 그래프는 리포지토리 또는 패키지의 모든 업스트림 종속성 및 퍼블릭 다운스트림 종속 항목을 식별합니다. 리포지토리의 종속성 및 취약성 정보와 같은 일부 속성은 리포지토리의 종속성 그래프에서 확인할 수 있습니다.
|
||||
|
||||
Other supply chain features on {% data variables.product.prodname_dotcom %} rely on the information provided by the dependency graph.
|
||||
{% data variables.product.prodname_dotcom %}의 다른 공급망 기능은 종속성 그래프에서 제공하는 정보를 사용합니다.
|
||||
|
||||
- Dependency review uses the dependency graph to identify dependency changes and help you understand the security impact of these changes when you review pull requests.
|
||||
- {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of advisories published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} is detected.
|
||||
{% ifversion fpt or ghec or ghes %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository.
|
||||
- 종속성 검토는 종속성 그래프를 사용하여 종속성 변경 내용을 식별하고 끌어오기 요청을 검토할 때 변경 내용의 보안 영향을 이해하는 데 도움이 됩니다.
|
||||
- {% data variables.product.prodname_dependabot %}은 종속성 그래프에서 제공하는 종속성 데이터를 {% data variables.product.prodname_advisory_database %}에 게시된 권고 목록과 상호 참조하고, 종속성을 검사하고, 잠재적 취약성{% ifversion GH-advisory-db-supports-malware %}또는 맬웨어{% endif %}가 감지되면 {% data variables.product.prodname_dependabot_alerts %}를 생성합니다.
|
||||
{% ifversion fpt or ghec or ghes %}- {% data variables.product.prodname_dependabot_security_updates %}는 종속성 그래프 및 {% data variables.product.prodname_dependabot_alerts %}를 사용하여 리포지토리의 알려진 취약성으로 종속성을 업데이트하는 데 도움이 됩니다.
|
||||
|
||||
{% data variables.product.prodname_dependabot_version_updates %} don't use the dependency graph and rely on the semantic versioning of dependencies instead. {% data variables.product.prodname_dependabot_version_updates %} help you keep your dependencies updated, even when they don’t have any vulnerabilities.
|
||||
{% data variables.product.prodname_dependabot_version_updates %}는 종속성 그래프를 사용하지 않고 종속성의 의미 체계 버전 관리를 대신 사용합니다. {% data variables.product.prodname_dependabot_version_updates %}는 취약성이 없는 경우에도 종속성을 업데이트된 상태로 유지하는 데 도움이 됩니다.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)."
|
||||
{% ifversion fpt or ghec or ghes %} 개인 계정, 코드, 빌드 프로세스 보호를 포함한 엔드투엔드 공급망 보안에 대한 모범 사례 가이드는 “[엔드투엔드 공급망 보안](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)”을 참조하세요.
|
||||
{% endif %}
|
||||
|
||||
## Feature overview
|
||||
## 기능 개요
|
||||
|
||||
### What is the dependency graph
|
||||
### 종속성 그래프란?
|
||||
|
||||
To generate the dependency graph, {% data variables.product.company_short %} looks at a repository’s explicit dependencies declared in the manifest and lockfiles. When enabled, the dependency graph automatically parses all known package manifest files in the repository, and uses this to construct a graph with known dependency names and versions.
|
||||
종속성 그래프를 생성하기 위해 {% data variables.product.company_short %}는 매니페스트 및 잠금 파일에 선언된 리포지토리의 명시적 종속성을 확인합니다. 사용하도록 설정하면 종속성 그래프는 리포지토리의 알려진 모든 패키지 매니페스트 파일을 자동으로 구문 분석하고 이를 사용하여 알려진 종속성 이름 및 버전으로 그래프를 생성합니다.
|
||||
|
||||
- The dependency graph includes information on your _direct_ dependencies and _transitive_ dependencies.
|
||||
- The dependency graph is automatically updated when you push a commit to {% data variables.product.company_short %} that changes or adds a supported manifest or lock file to the default branch, and when anyone pushes a change to the repository of one of your dependencies.
|
||||
- You can see the dependency graph by opening the repository's main page on {% data variables.product.product_name %}, and navigating to the **Insights** tab.
|
||||
- 종속성 그래프에는 _직접_ 종속성 및 _전이적_ 종속성에 대한 정보가 포함됩니다.
|
||||
- 기본 분기에 지원되는 매니페스트 또는 잠금 파일을 변경하거나 추가하는 {% data variables.product.company_short %}에 커밋을 푸시하고, 누군가가 종속성 중 하나의 리포지토리에 변경 내용을 푸시할 때 종속성 그래프가 자동으로 업데이트됩니다.
|
||||
- {% data variables.product.product_name %}에서 리포지토리의 기본 페이지를 열고 **인사이트** 탭으로 이동하여 종속성 그래프를 볼 수 있습니다.
|
||||
|
||||
{% ifversion dependency-submission-api %}
|
||||
{% data reusables.dependency-submission.dependency-submission-link %}
|
||||
{% endif %}
|
||||
{% ifversion dependency-submission-api %} {% data reusables.dependency-submission.dependency-submission-link %} {% endif %}
|
||||
|
||||
For more information about the dependency graph, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
종속성 그래프에 대한 자세한 내용은 “[종속성 그래프 정보](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”를 참조하세요.
|
||||
|
||||
### What is dependency review
|
||||
### 종속성 검토란?
|
||||
|
||||
Dependency review helps reviewers and contributors understand dependency changes and their security impact in every pull request.
|
||||
종속성 검토는 검토자와 기여자가 모든 끌어오기 요청에서 종속성 변경 내용과 그 보안 영향을 이해하는 데 도움이 됩니다.
|
||||
|
||||
- Dependency review tells you which dependencies were added, removed, or updated, in a pull request. You can use the release dates, popularity of dependencies, and vulnerability information to help you decide whether to accept the change.
|
||||
- You can see the dependency review for a pull request by showing the rich diff on the **Files Changed** tab.
|
||||
- 종속성 검토는 끌어오기 요청에서 추가, 제거 또는 업데이트된 종속성을 알려줍니다. 릴리스 날짜, 종속성 인기도 및 취약성 정보를 사용하여 변경 내용을 허용할지 여부를 결정할 수 있습니다.
|
||||
- **변경된 파일** 탭에 rich diff를 표시하여 끌어오기 요청에 대한 종속성 검토를 볼 수 있습니다.
|
||||
|
||||
For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
종속성 검토에 대한 자세한 내용은 “[종속성 검토 정보](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)”를 참조하세요.
|
||||
|
||||
### What is Dependabot
|
||||
### Dependabot이란?
|
||||
|
||||
{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}.
|
||||
{% data variables.product.prodname_dependabot %}는 종속성의 보안 취약성을 알려 종속성을 최신 상태로 유지합니다{% ifversion fpt or ghec or ghes %}, 및 는 {% data variables.product.prodname_dependabot %} 경고가 트리거될 때 또는 릴리스가 게시될 때 최신 버전으로 종속성을 업그레이드하는 끌어오기 요청을 자동으로 엽니다{% else %} 종속성{% endif %}을(를) 업데이트할 수 있습니다.
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
The term "{% data variables.product.prodname_dependabot %}" encompasses the following features:
|
||||
- {% data variables.product.prodname_dependabot_alerts %}—Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
|
||||
{% ifversion fpt or ghec or ghes %} "{% data variables.product.prodname_dependabot %}"라는 용어는 다음 기능을 포함합니다.
|
||||
- {% data variables.product.prodname_dependabot_alerts %} - 리포지토리의 **보안** 탭 및 리포지토리의 종속성 그래프에 표시된 알림. 경고에는 프로젝트에서 영향을 받는 파일에 대한 링크와 고정 버전에 대한 정보가 포함됩니다.
|
||||
- {% data variables.product.prodname_dependabot_updates %}:
|
||||
- {% data variables.product.prodname_dependabot_security_updates %}—Triggered updates to upgrade your dependencies to a secure version when an alert is triggered.
|
||||
- {% data variables.product.prodname_dependabot_version_updates %}—Scheduled updates to keep your dependencies up to date with the latest version.
|
||||
- {% data variables.product.prodname_dependabot_security_updates %} - 경고가 트리거될 때 종속성을 보안 버전으로 업그레이드하기 위해 트리거된 업데이트.
|
||||
- {% data variables.product.prodname_dependabot_version_updates %} - 종속성을 최신 버전으로 유지하기 위해 예약된 업데이트.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}, and {% data variables.product.prodname_dependabot_version_updates %} do not use {% data variables.product.prodname_actions %} when they run on {% data variables.product.product_name %}. However, pull requests opened by {% data variables.product.prodname_dependabot %} can trigger workflows that run actions. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions)."
|
||||
{% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}, {% data variables.product.prodname_dependabot_version_updates %}는 {% data variables.product.product_name %}에서 실행할 때 {% data variables.product.prodname_actions %}을(를) 사용하지 않습니다. 그러나 {% data variables.product.prodname_dependabot %}에서 연 끌어오기 요청은 작업을 실행하는 워크플로를 트리거할 수 있습니다. 자세한 내용은 “[ {% data variables.product.prodname_actions %}를 사용하여 {% data variables.product.prodname_dependabot %} 자동화](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions)”를 참조하세요.
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %} and {% data variables.product.prodname_dependabot_version_updates %} require {% data variables.product.prodname_actions %} to run on {% data variables.product.product_name %}. {% data variables.product.prodname_dependabot_alerts %} do not require {% data variables.product.prodname_actions %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
{% data variables.product.prodname_dependabot_security_updates %} 및 {% data variables.product.prodname_dependabot_version_updates %}을(를) 실행하려면 {% data variables.product.prodname_actions %}이(가) {% data variables.product.product_name %}에서 실행되어야 합니다. {% data variables.product.prodname_dependabot_alerts %}에는 {% data variables.product.prodname_actions %}이(가) 필요하지 않습니다. 자세한 내용은 “[엔터프라이즈에 {% data variables.product.prodname_dependabot %} 사용](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”을 참조하세요.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% data variables.product.prodname_actions %} is not required for {% data variables.product.prodname_dependabot_alerts %} to run on {% data variables.product.product_name %}.
|
||||
{% data variables.product.prodname_dependabot_alerts %}이(가) {% data variables.product.product_name %}에서 실행하려면 {% data variables.product.prodname_actions %}이(가) 필요하지 않습니다.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion dependabot-actions-support %}
|
||||
|
||||
{% data reusables.dependabot.dependabot-actions-support %} For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)."
|
||||
{% data reusables.dependabot.dependabot-actions-support %} 자세한 내용은 "[{% data variables.product.prodname_dependabot_security_updates %} 정보](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)"를 참조하세요.
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### What are Dependabot alerts
|
||||
#### Dependabot 경고란?
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %} highlight repositories affected by a newly discovered vulnerability based on the dependency graph and the {% data variables.product.prodname_advisory_database %}, which contains advisories for known vulnerabilities{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}.
|
||||
{% data variables.product.prodname_dependabot_alerts %}는 종속성 그래프와 알려진 취약성{% ifversion GH-advisory-db-supports-malware %} 및 맬웨어{% endif %} 목록에 대한 권고를 포함하는 {% data variables.product.prodname_advisory_database %}를 기준으로 새로 검색된 취약성의 영향을 받는 리포지토리를 강조 표시합니다.
|
||||
|
||||
- {% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
|
||||
{% ifversion fpt or ghec %}
|
||||
- A new advisory is added to the {% data variables.product.prodname_advisory_database %}.{% else %}
|
||||
- New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- The dependency graph for the repository changes.
|
||||
- {% data variables.product.prodname_dependabot_alerts %} are displayed {% ifversion fpt or ghec or ghes %} on the **Security** tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version.
|
||||
- {% data variables.product.prodname_dependabot %}은 검사를 수행하여 안전하지 않은 종속성을 검색하고 다음과 같은 경우 {% data variables.product.prodname_dependabot_alerts %}를 보냅니다. {% ifversion fpt or ghec %}
|
||||
- {% data variables.product.prodname_advisory_database %}에 새 권고가 추가됩니다.{% else %}
|
||||
- 새 권고 데이터는 {% data variables.product.prodname_dotcom_the_website %}에서 매시간 {% data variables.location.product_location %}에 동기화됩니다. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- 리포지토리에 대한 종속성 그래프가 변경됩니다.
|
||||
- {% data variables.product.prodname_dependabot_alerts %}가 리포지토리의 {% ifversion fpt or ghec or ghes %} **보안** 탭과{% endif %} 리포지토리의 종속성 그래프에 표시됩니다. 경고에는 {% ifversion fpt or ghec or ghes %}프로젝트에서 영향을 받는 파일에 대한 링크와 {% endif %}고정 버전에 대한 정보가 포함됩니다.
|
||||
|
||||
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
|
||||
자세한 내용은 “[{% data variables.product.prodname_dependabot_alerts %} 정보](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)”를 참조하세요.
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
#### What are Dependabot updates
|
||||
#### Dependabot 업데이트란?
|
||||
|
||||
There are two types of {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} _security_ updates and _version_ updates. {% data variables.product.prodname_dependabot %} generates automatic pull requests to update your dependencies in both cases, but there are several differences.
|
||||
{% data variables.product.prodname_dependabot_updates %}의 두 가지 유형은 {% data variables.product.prodname_dependabot %} _보안_ 업데이트와 _버전_ 업데이트입니다. {% data variables.product.prodname_dependabot %}은 두 경우 모두 종속성을 업데이트하기 위한 자동 끌어오기 요청을 생성하지만 몇 가지 차이점이 있습니다.
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %}:
|
||||
- Triggered by a {% data variables.product.prodname_dependabot %} alert
|
||||
- Update dependencies to the minimum version that resolves a known vulnerability
|
||||
- Supported for ecosystems the dependency graph supports
|
||||
- Does not require a configuration file, but you can use one to override the default behavior
|
||||
- {% data variables.product.prodname_dependabot %} 경고에 의해 트리거됨
|
||||
- 알려진 취약성을 해결하는 최소 버전으로 종속성 업데이트
|
||||
- 종속성 그래프에서 지원하는 에코시스템 지원
|
||||
- 구성 파일이 필요하지 않지만 구성 파일을 사용하여 기본 동작을 재정의할 수 있습니다.
|
||||
|
||||
{% data variables.product.prodname_dependabot_version_updates %}:
|
||||
- Requires a configuration file
|
||||
- Run on a schedule you configure
|
||||
- Update dependencies to the latest version that matches the configuration
|
||||
- Supported for a different group of ecosystems
|
||||
- 구성 파일 필요
|
||||
- 구성한 일정에 따라 실행
|
||||
- 구성과 일치하는 최신 버전으로 종속성 업데이트
|
||||
- 다른 에코시스템 그룹 지원
|
||||
|
||||
For more information about {% data variables.product.prodname_dependabot_updates %}, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)" and "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)."
|
||||
{% data variables.product.prodname_dependabot_updates %}에 대한 자세한 내용은 “[{% data variables.product.prodname_dependabot_security_updates %} 정보”](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates) 및 “[{% data variables.product.prodname_dependabot_version_updates %} 정보”](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)를 참조하세요.
|
||||
{% endif %}
|
||||
|
||||
## Feature availability
|
||||
## 기능 가용성
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
Public repositories:
|
||||
- **Dependency graph**—enabled by default and cannot be disabled.
|
||||
- **Dependency review**—enabled by default and cannot be disabled.
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. {% data variables.product.prodname_dotcom %} detects insecure dependencies and displays information in the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %}.
|
||||
You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)."
|
||||
퍼블릭 리포지토리:
|
||||
- **종속성 그래프** - 기본적으로 사용하도록 설정되어 있으며, 사용하지 않도록 설정할 수 없습니다.
|
||||
- **종속성 검토** - 기본적으로 사용하도록 설정되어 있으며, 사용하지 않도록 설정할 수 없습니다.
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** - 기본적으로 사용하지 않도록 설정됩니다. {% data variables.product.prodname_dotcom %}는 안전하지 않은 종속성을 검색하고 종속성 그래프에 정보를 표시하지만 기본적으로 {% data variables.product.prodname_dependabot_alerts %}를 생성하지는 않습니다. 리포지토리 소유자 또는 관리자 액세스 권한이 있는 사용자는 {% data variables.product.prodname_dependabot_alerts %}를 사용하도록 설정할 수 있습니다.
|
||||
사용자 계정 또는 조직이 소유한 모든 리포지토리에 대해 Dependabot 경고를 사용하거나 사용하지 않도록 설정할 수도 있습니다. 자세한 내용은 “[사용자 계정의 보안 및 분석 설정 관리](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)” 또는 “[조직의 보안 및 분석 설정 관리](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)”를 참조하세요.
|
||||
|
||||
Private repositories:
|
||||
- **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
|
||||
프라이빗 리포지토리:
|
||||
- **종속성 그래프** - 기본적으로 사용하지 않도록 설정됩니다. 리포지토리 관리자는 이 기능을 사용하도록 설정할 수 있습니다. 자세한 내용은 “[리포지토리의 종속성 탐색](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”을 참조하세요.
|
||||
{% ifversion fpt %}
|
||||
- **Dependency review**—available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
|
||||
- **종속성 검토** - {% data variables.product.prodname_ghe_cloud %}를 사용하고 {% data variables.product.prodname_GH_advanced_security %}에 대한 라이선스가 있는 조직이 소유한 프라이빗 리포지토리에서 사용할 수 있습니다. 자세한 내용은 [{% data variables.product.prodname_ghe_cloud %} 설명서](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)를 참조하세요.
|
||||
{% elsif ghec %}
|
||||
- **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
|
||||
{% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
|
||||
You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)."
|
||||
- **종속성 검토** - {% data variables.product.prodname_GH_advanced_security %}에 대한 라이선스가 있고 종속성 그래프를 사용하도록 설정한 경우 조직이 소유한 프라이빗 리포지토리에서 사용할 수 있습니다. 자세한 내용은 “[{% data variables.product.prodname_GH_advanced_security %} 정보](/get-started/learning-about-github/about-github-advanced-security)” 및 “[리포지토리의 종속성 탐색](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”을 참조하세요. {% endif %}
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** - 기본적으로 사용하지 않도록 설정됩니다. 프라이빗 리포지토리의 소유자 또는 관리자 액세스 권한이 있는 사용자는 해당 리포지토리에 대해 종속성 그래프 및 {% data variables.product.prodname_dependabot_alerts %}를 사용하도록 설정하여 {% data variables.product.prodname_dependabot_alerts %}를 사용하도록 설정할 수 있습니다.
|
||||
사용자 계정 또는 조직이 소유한 모든 리포지토리에 대해 Dependabot 경고를 사용하거나 사용하지 않도록 설정할 수도 있습니다. 자세한 내용은 “[사용자 계정의 보안 및 분석 설정 관리](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)” 또는 “[조직의 보안 및 분석 설정 관리](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)”를 참조하세요.
|
||||
|
||||
Any repository type:
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
|
||||
모든 리포지토리 유형:
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** - 기본적으로 사용하지 않도록 설정됩니다. {% data variables.product.prodname_dependabot_alerts %} 및 종속성 그래프를 사용하는 리포지토리에 대해 {% data variables.product.prodname_dependabot_security_updates %}를 사용하도록 설정할 수 있습니다. 보안 업데이트 사용에 대한 자세한 내용은 “[{% data variables.product.prodname_dependabot_security_updates %} 구성](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)”을 참조하세요.
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** - 기본적으로 사용하지 않도록 설정됩니다. 리포지토리에 대한 쓰기 권한이 있는 사용자는 {% data variables.product.prodname_dependabot_version_updates %}를 사용하도록 설정할 수 있습니다. 버전 업데이트 사용에 대한 자세한 내용은 “[{% data variables.product.prodname_dependabot_version_updates %} 구성](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)”을 참조하세요.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
- **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
- **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
|
||||
{% endif %}
|
||||
{% ifversion ghes %}
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
|
||||
- **종속성 그래프** 및 **{% data variables.product.prodname_dependabot_alerts %}** - 기본적으로 사용하지 않도록 설정됩니다. 두 기능 모두 엔터프라이즈 수준에서 엔터프라이즈 소유자에 의해 구성됩니다. 자세한 내용은 {% ifversion ghes %}“[엔터프라이즈에 대해 종속성 그래프 사용](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)” 및 {% endif %}“[엔터프라이즈에 대해 {% data variables.product.prodname_dependabot %} 사용](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”을 참조하세요.
|
||||
- **종속성 검토** - 조직 또는 리포지토리에 대해 {% data variables.location.product_location %}에 대한 종속성 그래프를 사용하도록 설정하고 {% data variables.product.prodname_advanced_security %}을(를) 사용하도록 설정한 경우에 사용할 수 있습니다. 자세한 내용은 “[{% data variables.product.prodname_GH_advanced_security %} 정보](/get-started/learning-about-github/about-github-advanced-security)”를 참조하세요.
|
||||
{% endif %} {% ifversion ghes %}
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** - 기본적으로 사용하지 않도록 설정됩니다. {% data variables.product.prodname_dependabot_alerts %} 및 종속성 그래프를 사용하는 리포지토리에 대해 {% data variables.product.prodname_dependabot_security_updates %}를 사용하도록 설정할 수 있습니다. 보안 업데이트 사용에 대한 자세한 내용은 “[{% data variables.product.prodname_dependabot_security_updates %} 구성](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)”을 참조하세요.
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}** - 기본적으로 사용하지 않도록 설정됩니다. 리포지토리에 대한 쓰기 권한이 있는 사용자는 {% data variables.product.prodname_dependabot_version_updates %}를 사용하도록 설정할 수 있습니다. 버전 업데이트 사용에 대한 자세한 내용은 “[{% data variables.product.prodname_dependabot_version_updates %} 구성](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)”을 참조하세요.
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: codespace 중지 및 시작
|
||||
intro: codespace를 중지하고 시작하여 리소스를 저장하고 작업을 일시 중지할 수 있습니다.
|
||||
title: Stopping and starting a codespace
|
||||
intro: 'You can stop and start your codespace to save resources and to pause work.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,33 +10,28 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Stop a codespace
|
||||
ms.openlocfilehash: 290a39d9d60420230bd9b11d5e2d10119ccc1c72
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158807'
|
||||
---
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## codespace 중지 및 시작 정보
|
||||
## About stopping and starting a codespace
|
||||
|
||||
{% data reusables.codespaces.stopping-a-codespace %}
|
||||
|
||||
codespace를 만들거나 액세스하는 위치에 관계없이 에서 브라우저 https://github.com/codespaces에서 보고 관리할 수 있습니다.
|
||||
Regardless of where you created or access your codespaces, you can view and manage them in your browser at https://github.com/codespaces.
|
||||
|
||||
## Codespace 중지
|
||||
## Stopping a codespace
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-codespaces-page %}
|
||||
1. 중지하려는 codespace 오른쪽에서 elipsis(**...**)를 클릭합니다.
|
||||
1. **codespace 중지** 를 클릭합니다.
|
||||
|
||||
1. To the right of the codespace you want to stop, click the elipsis (**...**).
|
||||
1. Click **Stop codespace**.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -44,7 +39,7 @@ codespace를 만들거나 액세스하는 위치에 관계없이 에서 브라
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
codespace를 중지하려면 하위 명령을 사용한 `gh codespace stop` 다음, 표시되는 목록에서 중지할 codespace를 선택합니다.
|
||||
To stop a codespace use the `gh codespace stop` subcommand and then choose the codespace you want to stop from the list that's displayed.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace stop
|
||||
@@ -55,41 +50,38 @@ codespace를 만들거나 액세스하는 위치에 관계없이 에서 브라
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.vs-code.open-command-palette %}
|
||||
1. **Codespaces: 옵션 목록에서 Codespace 중지** 를 입력 `stop` 하고 선택합니다.
|
||||
1. codespace 목록에서 중지할 codespace를 선택합니다.
|
||||
1. Type `stop` and select **Codespaces: Stop Codespace** from the list of options.
|
||||
1. In the list of codespaces, select the codespace you want to stop.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
|
||||
1. {% data variables.product.prodname_github_codespaces %} 도구 창에서 중지 아이콘을 클릭합니다.
|
||||
|
||||
|
||||
You can stop a codespace from the "Your codespaces" page (see [the web browser instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) or by using {% data variables.product.prodname_cli %} (see [the CLI instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)).
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## codespace 다시 시작
|
||||
## Restarting a codespace
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-codespaces-page %}
|
||||
1. 다시 시작하려는 codespace의 이름을 클릭합니다.
|
||||
|
||||
1. Click the name of the codespace you want to restart.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
codespace를 다시 시작하면 {% data variables.product.prodname_vscode %} 또는 브라우저에서 열도록 선택할 수 있습니다.
|
||||
When you restart a codespace you can choose to open it in {% data variables.product.prodname_vscode %} or in your browser.
|
||||
|
||||
- codespace를 다시 시작하고 {% data variables.product.prodname_vscode %}에서 열려면 하위 명령을 사용한 `gh codespace code` 다음, 표시된 목록에서 다시 시작할 codespace를 선택합니다.
|
||||
- To restart a codespace and open it in {% data variables.product.prodname_vscode %}, use the `gh codespace code` subcommand and then choose the codespace you want to restart from the list that's displayed.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace code
|
||||
```
|
||||
|
||||
- codespace를 다시 시작하고 브라우저에서 열려면 하위 명령을 사용한 `gh codespace open --web` 다음 표시되는 목록에서 다시 시작할 codespace를 선택합니다.
|
||||
- To restart a codespace and open it in your browser, use the `gh codespace open --web` subcommand and then choose the codespace you want to restart from the list that's displayed.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace open --web
|
||||
@@ -100,8 +92,8 @@ codespace를 다시 시작하면 {% data variables.product.prodname_vscode %}
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.vs-code.open-command-palette %}
|
||||
1. **Codespaces: 옵션 목록에서 Codespace에 연결을** 입력 `connect` 하고 선택합니다.
|
||||
1. codespace 목록에서 다시 시작할 codespace를 선택합니다.
|
||||
1. Type `connect` and select **Codespaces: Connect to Codespace** from the list of options.
|
||||
1. In the list of codespaces, select the codespace you want to restart.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -111,6 +103,6 @@ codespace를 다시 시작하면 {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## 추가 정보
|
||||
## Further reading
|
||||
|
||||
- "[codespace 수명 주기](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
|
||||
- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
|
||||
|
||||
@@ -211,7 +211,7 @@ You can define default interface settings for {% data variables.product.prodname
|
||||
|
||||
## Applying configuration changes to a codespace
|
||||
|
||||
Changes to a configuration will be applied the next time you create a codespace. However, if you're using a codespace in a web browser, in {% data variables.product.prodname_vscode_shortname %}, or in a JetBrains IDE, you can apply configuration changes to the current codespace by rebuilding the container.
|
||||
Changes to a configuration will be applied the next time you create a codespace. However, you can apply your changes to an existing codespace by rebuilding the container. You can do this within a codespace in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application, or you can use {% data variables.product.prodname_cli %}.
|
||||
|
||||
### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application
|
||||
|
||||
@@ -224,15 +224,19 @@ Changes to a configuration will be applied the next time you create a codespace.
|
||||
- To fix the errors identified in the logs, update your `devcontainer.json` file.
|
||||
- To apply the changes, rebuild your container.
|
||||
|
||||
### Rebuilding the dev container in a JetBrains IDE
|
||||
### Using {% data variables.product.prodname_cli %} to rebuild a dev container
|
||||
|
||||
{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
|
||||
1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the rebuild icon.
|
||||
If you've changed a dev container configuration outside of VS Code (for example, on {% data variables.product.prodname_dotcom_the_website %} or in a JetBrains IDE), you can use {% data variables.product.prodname_cli %} to rebuild the dev container for an existing codespace.
|
||||
|
||||
|
||||
1. In a terminal, enter the following command.
|
||||
|
||||
1. Click **Rebuild** when prompted to confirm that you want to rebuild the dev container.
|
||||
1. Reopen the codespace in your JetBrains IDE.
|
||||
```
|
||||
gh cs rebuild
|
||||
```
|
||||
|
||||
Your codespaces are listed.
|
||||
|
||||
1. Use the arrow keys on your keyboard to highlight the required codespace, then press <kbd>Enter</kbd>.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -1,123 +1,123 @@
|
||||
---
|
||||
title: JetBrains IDE에서 GitHub Copilot 시작하기
|
||||
title: Getting started with GitHub Copilot in a JetBrains IDE
|
||||
shortTitle: JetBrains IDE
|
||||
intro: 'JetBrains IDE에 {% data variables.product.prodname_copilot %}을 설치하고 메모와 코드를 작성할 때 제안 사항을 확인하는 방법을 알아봅니다.'
|
||||
intro: 'Learn how to install {% data variables.product.prodname_copilot %} in a JetBrains IDE, and start seeing suggestions as you write comments and code.'
|
||||
product: '{% data reusables.gated-features.copilot %}'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
ms.openlocfilehash: 24415504e0abeff6e129321068b07590d265da16
|
||||
ms.sourcegitcommit: 99eb4456062aea31ca381977396417cf92e5798d
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179632'
|
||||
---
|
||||
## {% data variables.product.prodname_copilot %} 및 JetBrains IDE 정보
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and JetBrains IDEs
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
JetBrains IDE를 사용하는 경우 편집기 내에서 직접 {% data variables.product.prodname_copilot %}의 제안을 보고 통합할 수 있습니다. 이 가이드에서는 macOS, Windows 또는 Linux용 JetBrains IDE 내에서 {% data variables.product.prodname_copilot %}을 사용하는 방법을 보여 줍니다.
|
||||
If you use a JetBrains IDE, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within a JetBrains IDE for macOS, Windows, or Linux.
|
||||
|
||||
## 필수 조건
|
||||
## Prerequisites
|
||||
|
||||
{% data reusables.copilot.jetbrains-ides %}
|
||||
|
||||
## JetBrains IDE에 {% data variables.product.prodname_copilot %} 확장 설치
|
||||
## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE
|
||||
|
||||
JetBrains IDE에서 {% data variables.product.prodname_copilot %}을 사용하려면 {% data variables.product.prodname_copilot %} 확장을 설치해야 합니다. 다음 절차에서는 IntelliJ IDEA에서 {% data variables.product.prodname_copilot %} 플러그 인 설치를 안내합니다. 지원되는 다른 IDE에 플러그 인을 설치하는 단계는 다를 수 있습니다.
|
||||
To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} extension. The following procedure will guide you through installation of the {% data variables.product.prodname_copilot %} plugin in IntelliJ IDEA. Steps to install the plugin in another supported IDE may differ.
|
||||
|
||||
1. JetBrains IDE의 Windows용 **파일** 메뉴 또는 Mac용 IDE 이름(예: **PyCharm** 또는 **IntelliJ**)에서 Windows **설정** 또는 Mac용 **기본 설정** 을 클릭합니다.
|
||||
2. **설정/기본 설정** 대화 상자의 왼쪽 메뉴에서 **플러그 인** 을 클릭합니다.
|
||||
3. **설정/기본 설정** 대화 상자의 맨 위에서 **Marketplace** 를 클릭합니다. 검색 창에서 **{% data variables.product.prodname_copilot %}** 을 검색한 다음 **설치** 를 클릭합니다.
|
||||
|
||||
1. {% data variables.product.prodname_copilot %}이 설치되면 **IDE 다시 시작** 을 클릭합니다.
|
||||
1. JetBrains IDE가 다시 시작되면 **도구** 메뉴를 클릭합니다. **{% data variables.product.prodname_copilot %}** 을 클릭한 다음 **{% data variables.product.prodname_dotcom %}에 로그인** 을 클릭합니다.
|
||||
|
||||
1. “{% data variables.product.prodname_dotcom %}에 로그인” 대화 상자에서 디바이스 코드를 복사하고 디바이스 활성화 창을 열려면 **복사하여 열기** 를 클릭합니다.
|
||||
|
||||
1. 브라우저에서 디바이스 활성화 창이 열립니다. 디바이스 코드를 붙여넣은 다음 **계속** 을 클릭합니다.
|
||||
1. In your JetBrains IDE, under the **File** menu for Windows or under the name of your IDE for Mac (for example, **PyCharm** or **IntelliJ**), click **Settings** for Windows or **Preferences** for Mac.
|
||||
2. In the left-side menu of the **Settings/Preferences** dialog box, click **Plugins**.
|
||||
3. At the top of the **Settings/Preferences** dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}**, then click **Install**.
|
||||
|
||||
1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**.
|
||||
1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**.
|
||||
|
||||
1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**.
|
||||
|
||||
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
|
||||
|
||||
- Windows 또는 Linux에 코드를 붙여넣려면 <kbd>Ctrl</kbd>+<kbd>v</kbd>를 누릅니다.
|
||||
- macOS에 코드를 붙여넣려면 <kbd>command</kbd>+<kbd>v</kbd>를 누릅니다.
|
||||
1. {% data variables.product.prodname_dotcom %}는 {% data variables.product.prodname_copilot %}에 필요한 권한을 요청합니다. 이러한 권한을 승인하려면 **{% data variables.product.prodname_copilot %} 플러그 인 권한 승인** 을 클릭합니다.
|
||||
1. 사용 권한이 승인되면 JetBrains IDE에 확인 메시지가 표시됩니다. {% data variables.product.prodname_copilot %}을 사용하려면 **확인** 을 클릭합니다.
|
||||
|
||||
- To paste the code in Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>v</kbd>.
|
||||
- To paste the code in macOS, press <kbd>command</kbd>+<kbd>v</kbd>.
|
||||
1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
|
||||
1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**.
|
||||
|
||||
|
||||
|
||||
## 첫 번째 제안 보기
|
||||
## Seeing your first suggestion
|
||||
|
||||
{% data reusables.copilot.code-examples-limitations %}
|
||||
|
||||
{% data reusables.copilot.supported-languages %} 다음 샘플은 Java이지만 다른 언어도 비슷하게 작동합니다.
|
||||
{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly.
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Java 파일에서 `class Test`를 입력하여 클래스를 만듭니다.
|
||||
{% data variables.product.prodname_copilot %}은 아래와 같이 회색 표시된 텍스트로 클래스 본문을 자동으로 제안합니다. 정확한 제안은 다를 수 있습니다.
|
||||
 {% data reusables.copilot.accept-suggestion %} 스크린샷
|
||||
1. {% data variables.product.prodname_copilot %}에게 함수 본문을 제안하라는 메시지를 표시하려면 `main` 함수의 대괄호 아래에 다음 줄을 입력합니다. 정확한 제안은 다를 수 있습니다.
|
||||
1. In the Java file, create a class by typing `class Test`.
|
||||
{% data variables.product.prodname_copilot %} will automatically suggest a class body in grayed text, as shown below. The exact suggestion may vary.
|
||||
|
||||
{% data reusables.copilot.accept-suggestion %}
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to suggest a function body, type the following line below the bracket of the `main` function. The exact suggestion may vary.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
|
||||
|
||||
 {% data reusables.copilot.accept-suggestion %} 스크린샷
|
||||
|
||||
{% data reusables.copilot.accept-suggestion %}
|
||||
|
||||
{% data variables.product.prodname_copilot %}은 코드의 컨텍스트와 스타일을 일치시키려고 시도합니다. 제안된 코드는 언제든지 편집할 수 있습니다.
|
||||
{% data variables.product.prodname_copilot %} will attempt to match the context and style of your code. You can always edit the suggested code.
|
||||
|
||||
## 대체 제안 보기
|
||||
## Seeing alternative suggestions
|
||||
|
||||
{% data reusables.copilot.alternative-suggestions %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. {% data variables.product.prodname_copilot %}에게 제안 사항을 표시하라는 메시지를 표시하려면 Java 파일에 다음 줄을 입력합니다.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} {% data reusables.copilot.see-alternative-suggestions %}
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
|
||||
{% data reusables.copilot.see-alternative-suggestions %}
|
||||
|
||||
| OS | 다음 제안 참조 | 이전 제안 참조 |
|
||||
| OS | See next suggestion | See previous suggestion |
|
||||
| :- | :- | :- |
|
||||
| macOS | <kbd>옵션</kbd>+<kbd>]</kbd> | <kbd>옵션</kbd>+<kbd>[</kbd> |
|
||||
| macOS | <kbd>Option</kbd>+<kbd>]</kbd> | <kbd>Option</kbd>+<kbd>[</kbd> |
|
||||
| Windows | <kbd>Alt</kbd>+<kbd>]</kbd> | <kbd>Alt</kbd>+<kbd>[</kbd> |
|
||||
| Linux | <kbd>Alt</kbd>+<kbd>]</kbd> | <kbd>Alt</kbd>+<kbd>[</kbd> |
|
||||
{% data reusables.copilot.accept-or-reject-suggestion %}
|
||||
|
||||
## 새 탭에서 여러 제안 표시
|
||||
## Seeing multiple suggestions in a new tab
|
||||
|
||||
{% data reusables.copilot.suggestions-new-tab %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. {% data variables.product.prodname_copilot %}에게 제안 사항을 표시하라는 메시지를 표시하려면 Java 파일에 다음 줄을 입력합니다.
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file.
|
||||
{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
|
||||
1. 여러 개의 추가 제안 사항이 있는 새 탭을 엽니다.
|
||||
- macOS에서 <kbd>command</kbd>+<kbd>Shift</kbd>+<kbd>A</kbd>를 누른 다음 **GitHub Copilot 열기** 를 클릭하거나 <kbd>command</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd>를 눌러 바로 새 탭을 엽니다.
|
||||
- Windows 또는 Linux에서 <kbd>Ctrl</kbd>+<kbd>Enter</kbd> 키를 누른 다음 **GitHub Copilot 열기** 를 클릭합니다.
|
||||
|
||||
1. 제안을 수락하려면 제안 위에서 **솔루션 수락** 을 클릭합니다. 모든 제안을 거부하려면 탭을 닫습니다.
|
||||
1. Open a new tab with multiple additional suggestions.
|
||||
- On macOS, press <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>A</kbd>, then click **Open GitHub Copilot**, or press <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> to open the new tab immediately.
|
||||
- On Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>Enter</kbd>, then click **Open GitHub Copilot**.
|
||||
|
||||
1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab.
|
||||
|
||||
## 주석에서 코드 제안 생성
|
||||
## Generating code suggestions from comments
|
||||
|
||||
{% data reusables.copilot.generating-suggestions-from-comments %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. {% data variables.product.prodname_copilot %}에게 Java 파일의 함수 구현을 제안하라는 메시지를 표시하려면 다음 줄을 입력합니다.
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to suggest an implementation of a function in the Java file, type the following lines.
|
||||
```java{:copy}
|
||||
// find all images without alternate text
|
||||
// and give them a red border
|
||||
void process () {
|
||||
```
|
||||
|
||||
|
||||
|
||||
## {% data variables.product.prodname_copilot %} 사용 및 사용 안 함
|
||||
## Enabling and disabling {% data variables.product.prodname_copilot %}
|
||||
|
||||
모든 언어 또는 개별 언어에 대해 {% data variables.product.prodname_copilot %}을 사용하거나 사용하지 않도록 설정할 수 있습니다. JetBrains IDE 창의 아래쪽 패널에 있는 {% data variables.product.prodname_copilot %} 상태 아이콘은 {% data variables.product.prodname_copilot %}가 활성화되었는지 여부를 나타냅니다. 사용하도록 설정하면 아이콘이 강조 표시됩니다. 사용하지 않도록 설정하면 아이콘이 회색으로 표시됩니다.
|
||||
You can enable or disable {% data variables.product.prodname_copilot %} for all languages, or for individual languages. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of your JetBrains IDE window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out.
|
||||
|
||||
1. {% data variables.product.prodname_copilot %}을 사용하거나 사용하지 않도록 설정하려면 JetBrains 창의 아래쪽 패널에서 상태 아이콘을 클릭합니다.
|
||||
|
||||
2. {% data variables.product.prodname_copilot %}을 사용하지 않도록 설정하는 경우 전역적으로 또는 현재 편집 중인 파일의 언어에 대해 사용하지 않도록 설정할지 묻는 메시지가 표시됩니다.
|
||||
1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window.
|
||||
|
||||
2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable it globally, or for the language of the file you are currently editing.
|
||||
|
||||
- {% data variables.product.prodname_copilot %}에서 제안을 전역적으로 사용하지 않도록 설정하려면 **완료 사용하지 않음** 을 클릭합니다.
|
||||
- 지정된 언어에 대한 {% data variables.product.prodname_copilot %}에서 제안을 사용하지 않으려면 **_언어_ 에 대한 완성을 사용하지 않음** 을 클릭합니다.
|
||||
|
||||
- To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Completions**.
|
||||
- To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable Completions for _LANGUAGE_**.
|
||||
|
||||
|
||||
|
||||
## 추가 참고 자료
|
||||
## Further reading
|
||||
|
||||
- [{% data variables.product.prodname_copilot %} 웹 사이트](https://copilot.github.com/)
|
||||
- [{% data variables.product.prodname_copilot %} 정보](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides)
|
||||
- [The {% data variables.product.prodname_copilot %} website](https://copilot.github.com/)
|
||||
- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides)
|
||||
|
||||
@@ -9,6 +9,8 @@ topics:
|
||||
- Copilot
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and Neovim
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
@@ -9,6 +9,8 @@ topics:
|
||||
- Copilot
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
@@ -9,6 +9,8 @@ topics:
|
||||
- Copilot
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and Visual Studio
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
@@ -36,7 +36,7 @@ The `git remote add` command takes two arguments:
|
||||
For example:
|
||||
|
||||
```shell
|
||||
$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO>.git
|
||||
$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO.git
|
||||
# Set a new remote
|
||||
|
||||
$ git remote -v
|
||||
|
||||
@@ -70,9 +70,9 @@ After you set up your trial, you can explore {% data variables.product.prodname_
|
||||
|
||||
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.
|
||||
|
||||
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 %}.
|
||||
If you don't purchase {% data variables.product.prodname_enterprise %}, the trial will continue until the end of the 30-day period. You cannot end the trial early. 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 %}.
|
||||
|
||||
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)."
|
||||
Your organization will lose access to any functionality that is not included in the new plan, 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)."
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -142,7 +142,7 @@ externalProducts:
|
||||
electron:
|
||||
id: electron
|
||||
name: Electron
|
||||
href: 'https://electronjs.org/docs'
|
||||
href: 'https://electronjs.org/docs/latest'
|
||||
external: true
|
||||
codeql:
|
||||
id: codeql
|
||||
@@ -154,11 +154,11 @@ externalProducts:
|
||||
name: npm
|
||||
href: 'https://docs.npmjs.com/'
|
||||
external: true
|
||||
ms.openlocfilehash: dad74fe11fc5bfea72ae994e9918683fc7e87b7a
|
||||
ms.sourcegitcommit: bd23217796e6ff442b14ef9d889eaef30e8d6826
|
||||
ms.openlocfilehash: e72ace58cb674661cbde635f97cf7ff0ab70433a
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/16/2022
|
||||
ms.locfileid: '148167306'
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148183974'
|
||||
---
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ You can restrict access to private organization assets by configuring an allow l
|
||||
|
||||
If you set up an allow list you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)."
|
||||
|
||||
You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
|
||||
You can also configure allowed IP addresses at the enterprise account level, and the entries in the enterprise account's allow list are inherited by all the organizations owned by the enterprise. {% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
|
||||
|
||||
## Adding an allowed IP address
|
||||
|
||||
|
||||
@@ -24,6 +24,8 @@ If you enable but don't enforce SAML SSO, organization members who choose not to
|
||||
|
||||
{% data reusables.saml.saml-disabled-linked-identities-removed %}
|
||||
|
||||
{% data reusables.apps.reauthorize-apps-saml %}
|
||||
|
||||
## Enabling and testing SAML single sign-on for your organization
|
||||
|
||||
Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
|
||||
|
||||
@@ -9,12 +9,12 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: c51d9275950bbf303caa1a03344ba8402618d65b
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: 47961c5dfeeb5f320bbac67ffb0573c31709bd5b
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145136023'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181325'
|
||||
---
|
||||
## Gist API 정보
|
||||
|
||||
@@ -38,7 +38,7 @@ Gist API는 gist의 각 파일에 대해 최대 1MB의 콘텐츠를 제공합니
|
||||
|
||||
다음은 gist 콘텐츠를 가져오기 위해 지원되는 미디어 유형입니다.
|
||||
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.VERSION.base64
|
||||
application/vnd.github.raw
|
||||
application/vnd.github.base64
|
||||
|
||||
자세한 내용은 “[미디어 유형](/rest/overview/media-types)”을 참조하세요.
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: ae4d0ac726c9b76785876f7884425cab99e89f1f
|
||||
ms.sourcegitcommit: fb740a96852435c748dad95d560327e80b4cef19
|
||||
ms.openlocfilehash: 3b7cac6d268fb4c7e786651a7281ca5ce4241ec5
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 10/24/2022
|
||||
ms.locfileid: '148105689'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181247'
|
||||
---
|
||||
## Git Blob API 정보
|
||||
|
||||
@@ -27,6 +27,6 @@ Git BLOB(Binary Large Object)은 각 파일의 콘텐츠를 리포지토리에
|
||||
다음은 BLOB에 대해 지원되는 미디어 유형입니다.
|
||||
|
||||
application/json
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.raw
|
||||
|
||||
자세한 내용은 “[미디어 유형](/rest/overview/media-types)”을 참조하세요.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Gitignore
|
||||
intro: The Gitignore API fetches `.gitignore` templates that can be used to ignore files and directories.
|
||||
title: gitignore
|
||||
intro: Gitignore API는 파일 및 디렉터리를 무시하는 데 사용할 수 있는 `.gitignore` 템플릿을 가져옵니다.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -11,16 +11,21 @@ topics:
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /rest/reference/gitignore
|
||||
ms.openlocfilehash: e830b0f00d60f3eb121fa2a99a910b073780700e
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181270'
|
||||
---
|
||||
## Gitignore API 정보
|
||||
|
||||
## About the Gitignore API
|
||||
{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}에서 API를 통해 새 리포지토리를 만들 때 [.gitignore 템플릿](/github/getting-started-with-github/ignoring-files) 을 지정하여 리포지토리에 적용할 수 있습니다. .gitignore 템플릿 API는 {% data variables.product.product_name %} [.gitignore 리포지토리](https://github.com/github/gitignore)에서 템플릿을 나열하고 가져옵니다.
|
||||
|
||||
When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. The .gitignore templates API lists and fetches templates from the {% data variables.product.product_name %} [.gitignore repository](https://github.com/github/gitignore).
|
||||
### gitignore에 대한 사용자 지정 미디어 유형
|
||||
|
||||
### Custom media types for gitignore
|
||||
|
||||
You can use this custom media type when getting a gitignore template.
|
||||
gitignore 템플릿을 가져오는 경우 이 사용자 지정 미디어 유형을 사용할 수 있습니다.
|
||||
|
||||
application/vnd.github.raw
|
||||
|
||||
For more information, see "[Media types](/rest/overview/media-types)."
|
||||
자세한 내용은 “[미디어 유형](/rest/overview/media-types)”을 참조하세요.
|
||||
|
||||
@@ -299,7 +299,7 @@ Most operations specify that you should pass an `Accept` header with a value of
|
||||
To send a header with {% data variables.product.prodname_cli %}, use the `--header` or `-H` flag followed by the header in `key: value` format.
|
||||
|
||||
```shell
|
||||
gh api --header 'Accept: application/vnd.github+json' --method GET /octocat
|
||||
gh api --header 'Accept: application/vnd.github+json'{% ifversion api-date-versioning %} --header 'X-GitHub-Api-Version:{{ allVersions[currentVersion].latestApiVersion }}'{% endif %} --method GET /octocat
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
@@ -311,7 +311,8 @@ The Octokit.js library automatically passes the `Accept: application/vnd.github+
|
||||
```javascript
|
||||
await octokit.request("GET /octocat", {
|
||||
headers: {
|
||||
"content-type": "text/plain",
|
||||
"content-type": "text/plain",{% ifversion api-date-versioning %}
|
||||
"X-GitHub-Api-Version": "{{ allVersions[currentVersion].latestApiVersion }}",{% endif %}
|
||||
},
|
||||
});
|
||||
```
|
||||
@@ -326,7 +327,8 @@ To send a header with cURL, use the `--header` or `-H` flag followed by the head
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/octocat" \
|
||||
--header "Accept: application/vnd.github+json" \
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"{% ifversion api-date-versioning %}\
|
||||
--header "X-GitHub-Api-Version: {{ allVersions[currentVersion].latestApiVersion }}"{% endif %}
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
@@ -12,6 +12,7 @@ featuredLinks:
|
||||
- /rest/guides/best-practices-for-integrators
|
||||
popular:
|
||||
- /rest/overview/resources-in-the-rest-api
|
||||
- /rest/overview/api-versions
|
||||
- /rest/overview/other-authentication-methods
|
||||
- /rest/overview/troubleshooting
|
||||
- /rest/overview/endpoints-available-for-github-apps
|
||||
@@ -78,11 +79,11 @@ children:
|
||||
- /teams
|
||||
- /users
|
||||
- /webhooks
|
||||
ms.openlocfilehash: d4d7e93d5bc22833168a932e047525c85e3f8768
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: 393b427325e51b3717e882e430662a6517cba551
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147673640'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184401'
|
||||
---
|
||||
|
||||
|
||||
54
translations/ko-KR/content/rest/overview/api-versions.md
Normal file
54
translations/ko-KR/content/rest/overview/api-versions.md
Normal file
@@ -0,0 +1,54 @@
|
||||
---
|
||||
title: API 버전
|
||||
shortTitle: API Versions
|
||||
intro: REST API를 요청할 때마다 사용할 REST API 버전을 지정해야 합니다.
|
||||
versions:
|
||||
feature: api-date-versioning
|
||||
ms.openlocfilehash: c1209120fab4c4cc26962991ad48b76638627db5
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184402'
|
||||
---
|
||||
## API 버전 관리 정보
|
||||
|
||||
{% data reusables.rest-api.about-api-versions %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## {% data variables.product.prodname_ghe_server %} 버전 관리 및 REST API 버전 관리 정보
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} 버전은 REST API 버전에서 분리됩니다. API 버전이 {% data variables.product.prodname_ghe_server %} 버전에 포함되어 있는 한 {% data variables.product.prodname_ghe_server %} 버전을 업그레이드할 수 있지만 동일한 REST API 버전을 유지할 수 있습니다. 마찬가지로 선택한 새 REST API 버전을 {% data variables.product.prodname_ghe_server %} 버전에 사용할 수 있는 한 {% data variables.product.prodname_ghe_server %} 버전을 업데이트하지 않고 REST API 버전을 업그레이드할 수 있습니다.
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} 릴리스 정보에는 REST API 버전이 더 이상 지원되지 않는 경우 표시됩니다. 자세한 내용은 "[릴리스 정보](/admin/release-notes)"를 참조하세요.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## API 버전 지정
|
||||
|
||||
헤더를 `X-GitHub-Api-Version` 사용하여 API 버전을 지정해야 합니다. 예를 들면 다음과 같습니다.
|
||||
|
||||
```shell
|
||||
$ curl {% data reusables.rest-api.version-header %} https://api.github.com/zen
|
||||
```
|
||||
|
||||
헤더가 없는 요청은 `X-GitHub-Api-Version` 기본적으로 버전을 사용합니다 `{{ initialRestVersioningReleaseDate }}` .
|
||||
|
||||
더 이상 지원되지 않는 API 버전을 지정하면 오류가 발생합니다 `400` .
|
||||
|
||||
## 새 API 버전으로 업그레이드
|
||||
|
||||
새 REST API 버전으로 업그레이드하기 전에 새 API 버전에 대한 호환성이 손상되는 변경 내용의 변경 로그를 읽고 포함된 주요 변경 내용을 이해하고 해당 특정 API 버전으로 업그레이드하는 방법에 대해 자세히 알아보세요. 자세한 내용은 "[호환성이 손상되는 변경"을 참조하세요](/rest/overview/breaking-changes).
|
||||
|
||||
헤더에서 `X-GitHub-Api-Version` 새 API 버전을 지정하도록 통합을 업데이트하는 경우 통합이 새 API 버전과 함께 작동하도록 하는 데 필요한 변경도 수행해야 합니다.
|
||||
|
||||
통합이 업데이트되면 통합을 테스트하여 새 API 버전에서 작동하는지 확인합니다.
|
||||
|
||||
## 지원되는 API 버전
|
||||
|
||||
현재 지원되는 REST API 버전은 다음과 같습니다.
|
||||
|
||||
{% for apiVersion in allVersions[currentVersion].apiVersions %} {{ apiVersion }} {% endfor %}
|
||||
|
||||
API 요청에서 지원되는 모든 API 버전을 가져올 수도 있습니다. 자세한 내용은 "[모든 API 버전 가져오기](/rest/meta#get-all-api-versions)"를 참조하세요.
|
||||
25
translations/ko-KR/content/rest/overview/breaking-changes.md
Normal file
25
translations/ko-KR/content/rest/overview/breaking-changes.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: Breaking changes
|
||||
shortTitle: Breaking changes
|
||||
intro: 'Learn about breaking changes that were introduced in each REST API version.'
|
||||
versions:
|
||||
feature: api-date-versioning
|
||||
---
|
||||
|
||||
## About breaking changes in the REST API
|
||||
|
||||
{% data reusables.rest-api.about-api-versions %}
|
||||
|
||||
For more information about API versions, see "[API Versions](/rest/overview/api-versions)."
|
||||
|
||||
## Upgrading to a new API version
|
||||
|
||||
Before upgrading to a new REST API version, you should read the section on this page that corresponds to the new API version to understand what breaking changes are included and to learn more about how to upgrade to that API version.
|
||||
|
||||
When you update your integration to specify the new API version in the `X-GitHub-Api-Version` header, you'll also need to make any changes required for your integration to work with the new API version.
|
||||
|
||||
Once your integration is updated, test your integration to verify that it works with the new API version.
|
||||
|
||||
## Breaking changes for {{ initialRestVersioningReleaseDate }}
|
||||
|
||||
Version `{{ initialRestVersioningReleaseDate }}` is the first version of the {% data variables.product.product_name %} REST API after date-based versioning was introduced. This version does not include any breaking changes.
|
||||
@@ -4,12 +4,12 @@ intro: '{% data variables.product.pat_v2 %}은(는) 다음 REST 엔드포인트
|
||||
versions:
|
||||
feature: pat-v2
|
||||
shortTitle: '{% data variables.product.pat_v2_caps %}-enabled endpoints'
|
||||
ms.openlocfilehash: 7e6b4506a1af51a3c8da5aa8ee905936025aa952
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: e631edb7b723f516ed50eba6df19ba2f94862e7e
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107239'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184223'
|
||||
---
|
||||
## actions
|
||||
|
||||
@@ -37,28 +37,6 @@ ms.locfileid: '148107239'
|
||||
- [`PUT /enterprises/{enterprise}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#list-self-hosted-runner-groups-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#create-self-hosted-runner-group-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#get-a-self-hosted-runner-group-for-an-enterprise)
|
||||
- [`PATCH /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#delete-a-self-hosted-runner-group-from-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#list-organization-access-to-a-self-hosted-runner-group-in-a-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#set-organization-access-to-a-self-hosted-runner-group-in-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#list-self-hosted-runners-in-a-group-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#add-a-self-hosted-runner-to-a-group-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#delete-self-hosted-runner-from-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`PUT /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-enterprise)
|
||||
- [`GET /enterprises/{enterprise}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-enterprise)
|
||||
- [`POST /enterprises/{enterprise}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-enterprise)
|
||||
- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}`](/rest/reference/actions#get-a-job-for-a-workflow-run)
|
||||
- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run)
|
||||
- [`POST /repos/{owner}/{repo}/actions/jobs/{job_id}/rerun`](/rest/reference/actions#re-run-job-for-workflow-run)
|
||||
@@ -155,18 +133,6 @@ ms.locfileid: '148107239'
|
||||
- [`GET /users/{username}/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user)
|
||||
- [`GET /users/{username}/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user)
|
||||
- [`GET /feeds`](/rest/reference/activity#get-feeds)
|
||||
- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user)
|
||||
- [`PUT /notifications`](/rest/reference/activity#mark-notifications-as-read)
|
||||
- [`GET /notifications/threads/{thread_id}`](/rest/reference/activity#get-a-thread)
|
||||
- [`PATCH /notifications/threads/{thread_id}`](/rest/reference/activity#mark-a-thread-as-read)
|
||||
- [`GET /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#get-a-thread-subscription-for-the-authenticated-user)
|
||||
- [`PUT /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#set-a-thread-subscription)
|
||||
- [`DELETE /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#delete-a-thread-subscription)
|
||||
- [`GET /repos/{owner}/{repo}/notifications`](/rest/reference/activity#list-repository-notifications-for-the-authenticated-user)
|
||||
- [`PUT /repos/{owner}/{repo}/notifications`](/rest/reference/activity#mark-repository-notifications-as-read)
|
||||
- [`GET /repos/{owner}/{repo}/subscription`](/rest/reference/activity#get-a-repository-subscription)
|
||||
- [`PUT /repos/{owner}/{repo}/subscription`](/rest/reference/activity#set-a-repository-subscription)
|
||||
- [`DELETE /repos/{owner}/{repo}/subscription`](/rest/reference/activity#delete-a-repository-subscription)
|
||||
- [`GET /repos/{owner}/{repo}/stargazers`](/rest/reference/activity#list-stargazers)
|
||||
- [`GET /repos/{owner}/{repo}/subscribers`](/rest/reference/activity#list-watchers)
|
||||
- [`GET /users/{username}/starred`](/rest/reference/activity#list-repositories-starred-by-a-user)
|
||||
@@ -179,39 +145,7 @@ ms.locfileid: '148107239'
|
||||
|
||||
## 앱
|
||||
|
||||
- [`DELETE /applications/{client_id}/grant`](/rest/reference/apps#delete-an-app-authorization)
|
||||
- [`POST /applications/{client_id}/token`](/rest/reference/apps#check-a-token)
|
||||
- [`PATCH /applications/{client_id}/token`](/rest/reference/apps#reset-a-token)
|
||||
- [`DELETE /applications/{client_id}/token`](/rest/reference/apps#delete-an-app-token)
|
||||
- [`POST /applications/{client_id}/token/scoped`](/rest/reference/apps#create-a-scoped-access-token)
|
||||
- [`GET /installation/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-app-installation)
|
||||
- [`DELETE /installation/token`](/rest/reference/apps#revoke-an-installation-access-token)
|
||||
- [`GET /user/installations/{installation_id}/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
|
||||
- [`PUT /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#add-a-repository-to-an-app-installation)
|
||||
- [`DELETE /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#remove-a-repository-from-an-app-installation)
|
||||
- [`POST /app-manifests/{code}/conversions`](/rest/reference/apps#create-a-github-app-from-a-manifest)
|
||||
- [`GET /app`](/rest/reference/apps#get-the-authenticated-app)
|
||||
- [`GET /app/hook/config`](/rest/reference/apps#get-a-webhook-configuration-for-an-app)
|
||||
- [`PATCH /app/hook/config`](/rest/reference/apps#update-a-webhook-configuration-for-an-app)
|
||||
- [`GET /app/hook/deliveries`](/rest/reference/apps#list-deliveries-for-an-app-webhook)
|
||||
- [`GET /app/hook/deliveries/{delivery_id}`](/rest/reference/apps#get-a-delivery-for-an-app-webhook)
|
||||
- [`POST /app/hook/deliveries/{delivery_id}/attempts`](/rest/reference/apps#redeliver-a-delivery-for-an-app-webhook)
|
||||
- [`GET /app/installations`](/rest/reference/apps#list-installations-for-the-authenticated-app)
|
||||
- [`GET /app/installations/{installation_id}`](/rest/reference/apps#get-an-installation-for-the-authenticated-app)
|
||||
- [`DELETE /app/installations/{installation_id}`](/rest/reference/apps#delete-an-installation-for-the-authenticated-app)
|
||||
- [`POST /app/installations/{installation_id}/access_tokens`](/rest/reference/apps/#create-an-installation-access-token-for-an-app)
|
||||
- [`PUT /app/installations/{installation_id}/suspended`](/rest/reference/apps#suspend-an-app-installation)
|
||||
- [`DELETE /app/installations/{installation_id}/suspended`](/rest/reference/apps#unsuspend-an-app-installation)
|
||||
- [`GET /orgs/{org}/installation`](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app)
|
||||
- [`GET /repos/{owner}/{repo}/installation`](/rest/reference/apps#get-a-repository-installation-for-the-authenticated-app)
|
||||
- [`GET /users/{username}/installation`](/rest/reference/apps#get-a-user-installation-for-the-authenticated-app)
|
||||
- [`GET /marketplace_listing/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account)
|
||||
- [`GET /marketplace_listing/plans`](/rest/reference/apps#list-plans)
|
||||
- [`GET /marketplace_listing/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan)
|
||||
- [`GET /marketplace_listing/stubbed/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account-stubbed)
|
||||
- [`GET /marketplace_listing/stubbed/plans`](/rest/reference/apps#list-plans-stubbed)
|
||||
- [`GET /marketplace_listing/stubbed/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan-stubbed)
|
||||
- [`GET /user/installations`](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
|
||||
- [`GET /user/marketplace_purchases`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
|
||||
- [`GET /user/marketplace_purchases/stubbed`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user-stubbed)
|
||||
|
||||
@@ -225,22 +159,14 @@ ms.locfileid: '148107239'
|
||||
- [`GET /users/{username}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-a-user)
|
||||
- [`GET /users/{username}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-a-user)
|
||||
|
||||
## checks
|
||||
## 분기
|
||||
|
||||
- [`POST /repos/{owner}/{repo}/check-runs`](/rest/reference/checks#create-a-check-run)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#get-a-check-run)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#update-a-check-run)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations`](/rest/reference/checks#list-check-run-annotations)
|
||||
- [`POST /repos/{owner}/{repo}/check-runs/{check_run_id}/rerequest`](/rest/reference/checks#rerequest-a-check-run)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites`](/rest/reference/checks#create-a-check-suite)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}`](/rest/reference/checks#get-a-check-suite)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites/{check_suite_id}/rerequest`](/rest/reference/checks#rerequest-a-check-suite)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/branches/branches#list-branches)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/branches/branches#sync-a-fork-branch-with-the-upstream-repository)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/branches/branches#merge-a-branch)
|
||||
|
||||
## 코드 검사
|
||||
|
||||
- [`GET /enterprises/{enterprise}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-an-enterprise)
|
||||
- [`GET /orgs/{org}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#get-a-code-scanning-alert)
|
||||
@@ -301,7 +227,7 @@ ms.locfileid: '148107239'
|
||||
- [`PUT /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#add-a-selected-repository-to-a-user-secret)
|
||||
- [`DELETE /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#remove-a-selected-repository-from-a-user-secret)
|
||||
|
||||
## 공동 작업자
|
||||
## 협력자
|
||||
|
||||
- [`GET /repos/{owner}/{repo}/collaborators`](/rest/collaborators/collaborators#list-repository-collaborators)
|
||||
- [`GET /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#check-if-a-user-is-a-repository-collaborator)
|
||||
@@ -331,6 +257,7 @@ ms.locfileid: '148107239'
|
||||
- [`PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-a-repository-secret)
|
||||
- [`DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-a-repository-secret)
|
||||
- [`GET /repos/{owner}/{repo}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key)
|
||||
- [`GET /orgs/{org}/dependabot/alerts`](/rest/dependabot/alerts#list-dependabot-alerts-for-an-organization)
|
||||
- [`GET /orgs/{org}/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets)
|
||||
- [`GET /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-an-organization-secret)
|
||||
- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-an-organization-secret)
|
||||
@@ -427,7 +354,7 @@ ms.locfileid: '148107239'
|
||||
- [`GET /repos/{owner}/{repo}/issues`](/rest/reference/issues#list-repository-issues)
|
||||
- [`POST /repos/{owner}/{repo}/issues`](/rest/reference/issues#create-an-issue)
|
||||
- [`GET /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#get-an-issue)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues/#update-an-issue)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#update-an-issue)
|
||||
- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#lock-an-issue)
|
||||
- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#unlock-an-issue)
|
||||
- [`GET /user/issues`](/rest/reference/issues#list-user-account-issues-assigned-to-the-authenticated-user)
|
||||
@@ -474,34 +401,12 @@ ms.locfileid: '148107239'
|
||||
- [`GET /repos/{owner}/{repo}/traffic/popular/referrers`](/rest/metrics/traffic#get-top-referral-sources)
|
||||
- [`GET /repos/{owner}/{repo}/traffic/views`](/rest/metrics/traffic#get-page-views)
|
||||
|
||||
## 마이그레이션
|
||||
|
||||
- [`GET /orgs/{org}/migrations`](/rest/reference/migrations#list-organization-migrations)
|
||||
- [`POST /orgs/{org}/migrations`](/rest/reference/migrations#start-an-organization-migration)
|
||||
- [`GET /orgs/{org}/migrations/{migration_id}`](/rest/reference/migrations#get-an-organization-migration-status)
|
||||
- [`GET /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#download-an-organization-migration-archive)
|
||||
- [`DELETE /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-an-organization-migration-archive)
|
||||
- [`GET /orgs/{org}/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-in-an-organization-migration)
|
||||
- [`GET /user/migrations`](/rest/reference/migrations#list-user-migrations)
|
||||
- [`POST /user/migrations`](/rest/reference/migrations#start-a-user-migration)
|
||||
- [`GET /user/migrations/{migration_id}`](/rest/reference/migrations#get-a-user-migration-status)
|
||||
- [`GET /user/migrations/{migration_id}/archive`](/rest/reference/migrations#download-a-user-migration-archive)
|
||||
- [`DELETE /user/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-a-user-migration-archive)
|
||||
- [`GET /user/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-for-a-user-migration)
|
||||
- [`GET /repos/{owner}/{repo}/import`](/rest/reference/migrations#get-an-import-status)
|
||||
- [`PUT /repos/{owner}/{repo}/import`](/rest/reference/migrations#start-an-import)
|
||||
- [`PATCH /repos/{owner}/{repo}/import`](/rest/reference/migrations#update-an-import)
|
||||
- [`DELETE /repos/{owner}/{repo}/import`](/rest/reference/migrations#cancel-an-import)
|
||||
- [`GET /repos/{owner}/{repo}/import/authors`](/rest/reference/migrations#get-commit-authors)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/authors/{author_id}`](/rest/reference/migrations#map-a-commit-author)
|
||||
- [`GET /repos/{owner}/{repo}/import/large_files`](/rest/reference/migrations#get-large-files)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/lfs`](/rest/reference/migrations#update-git-lfs-preference)
|
||||
|
||||
## orgs
|
||||
|
||||
{% ifversion ghec %}
|
||||
- [`GET /orgs/{org}/audit-log`](/rest/reference/orgs#get-audit-log){% endif %}
|
||||
- [`GET /organizations/{organization_id}/custom_roles`](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)
|
||||
- [`GET /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs/#get-a-custom-role)
|
||||
- [`PATCH /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#update-a-custom-role)
|
||||
- [`DELETE /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#delete-a-custom-role)
|
||||
- [`GET /orgs/{org}/fine_grained_permissions`](/rest/reference/orgs#list-fine-grained-permissions-for-an-organization)
|
||||
@@ -539,7 +444,7 @@ ms.locfileid: '148107239'
|
||||
- [`DELETE /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#remove-a-security-manager-team)
|
||||
- [`GET /organizations`](/rest/reference/orgs#list-organizations)
|
||||
- [`GET /orgs/{org}`](/rest/reference/orgs#get-an-organization)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs/#update-an-organization)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs#update-an-organization)
|
||||
- [`GET /orgs/{org}/installations`](/rest/reference/orgs#list-app-installations-for-an-organization)
|
||||
- [`GET /users/{username}/orgs`](/rest/reference/orgs#list-organizations-for-a-user)
|
||||
- [`GET /user/memberships/orgs/{org}`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
|
||||
@@ -551,18 +456,10 @@ ms.locfileid: '148107239'
|
||||
- [`PUT /orgs/{org}/blocks/{username}`](/rest/reference/orgs#block-a-user-from-an-organization)
|
||||
- [`DELETE /orgs/{org}/blocks/{username}`](/rest/reference/orgs#unblock-a-user-from-an-organization)
|
||||
|
||||
## 패키지
|
||||
|
||||
- [`GET /orgs/{org}/packages`](/rest/reference/packages#list-packages-for-an-organization)
|
||||
- [`GET /users/{username}/packages`](/rest/reference/packages#list-packages-for-user)
|
||||
- [`GET /user/packages`](/rest/reference/packages#list-packages-for-the-authenticated-user)
|
||||
|
||||
## 페이지
|
||||
|
||||
- [`GET /repos/{owner}/{repo}/pages`](/rest/pages#get-a-github-pages-site)
|
||||
- [`POST /repos/{owner}/{repo}/pages`](/rest/pages#create-a-github-pages-site)
|
||||
- [`PUT /repos/{owner}/{repo}/pages`](/rest/pages#update-information-about-a-github-pages-site)
|
||||
- [`DELETE /repos/{owner}/{repo}/pages`](/rest/pages#delete-a-github-pages-site)
|
||||
- [`GET /repos/{owner}/{repo}/pages/builds`](/rest/pages#list-github-pages-builds)
|
||||
- [`POST /repos/{owner}/{repo}/pages/builds`](/rest/pages#request-a-github-pages-build)
|
||||
- [`GET /repos/{owner}/{repo}/pages/builds/{build_id}`](/rest/pages#get-github-pages-build)
|
||||
@@ -570,34 +467,6 @@ ms.locfileid: '148107239'
|
||||
- [`POST /repos/{owner}/{repo}/pages/deployment`](/rest/pages#create-a-github-pages-deployment)
|
||||
- [`GET /repos/{owner}/{repo}/pages/health`](/rest/pages#get-a-dns-health-check-for-github-pages)
|
||||
|
||||
## projects
|
||||
|
||||
- [`GET /projects/{project_id}/collaborators`](/rest/reference/projects#list-project-collaborators)
|
||||
- [`PUT /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#add-project-collaborator)
|
||||
- [`DELETE /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#remove-project-collaborator)
|
||||
- [`GET /projects/{project_id}/collaborators/{username}/permission`](/rest/reference/projects#get-project-permission-for-a-user)
|
||||
- [`GET /orgs/{org}/projects`](/rest/reference/projects#list-organization-projects)
|
||||
- [`POST /orgs/{org}/projects`](/rest/reference/projects#create-an-organization-project)
|
||||
- [`GET /projects/{project_id}`](/rest/reference/projects#get-a-project)
|
||||
- [`PATCH /projects/{project_id}`](/rest/reference/projects#update-a-project)
|
||||
- [`DELETE /projects/{project_id}`](/rest/reference/projects#delete-a-project)
|
||||
- [`GET /projects/{project_id}/columns`](/rest/reference/projects#list-project-columns)
|
||||
- [`POST /projects/{project_id}/columns`](/rest/reference/projects#create-a-project-column)
|
||||
- [`GET /projects/columns/{column_id}`](/rest/reference/projects#get-a-project-column)
|
||||
- [`PATCH /projects/columns/{column_id}`](/rest/reference/projects#update-a-project-column)
|
||||
- [`DELETE /projects/columns/{column_id}`](/rest/reference/projects#delete-a-project-column)
|
||||
- [`GET /projects/columns/{column_id}/cards`](/rest/reference/projects#list-project-cards)
|
||||
- [`POST /projects/columns/{column_id}/cards`](/rest/reference/projects#create-a-project-card)
|
||||
- [`POST /projects/columns/{column_id}/moves`](/rest/reference/projects#move-a-project-column)
|
||||
- [`GET /projects/columns/cards/{card_id}`](/rest/reference/projects#get-a-project-card)
|
||||
- [`PATCH /projects/columns/cards/{card_id}`](/rest/reference/projects#update-a-project-card)
|
||||
- [`DELETE /projects/columns/cards/{card_id}`](/rest/reference/projects#delete-a-project-card)
|
||||
- [`POST /projects/columns/cards/{card_id}/moves`](/rest/reference/projects#move-a-project-card)
|
||||
- [`GET /repos/{owner}/{repo}/projects`](/rest/reference/projects#list-repository-projects)
|
||||
- [`POST /repos/{owner}/{repo}/projects`](/rest/reference/projects#create-a-repository-project)
|
||||
- [`GET /users/{username}/projects`](/rest/reference/projects#list-user-projects)
|
||||
- [`POST /user/projects`](/rest/reference/projects#create-a-user-project)
|
||||
|
||||
## 끌어
|
||||
|
||||
- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request)
|
||||
@@ -669,7 +538,7 @@ ms.locfileid: '148107239'
|
||||
- [`POST /orgs/{org}/repos`](/rest/reference/repos#create-an-organization-repository)
|
||||
- [`GET /repositories`](/rest/reference/repos#list-public-repositories)
|
||||
- [`GET /repos/{owner}/{repo}`](/rest/reference/repos#get-a-repository)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/reference/repos/#update-a-repository)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/repos/repos#update-a-repository)
|
||||
- [`DELETE /repos/{owner}/{repo}`](/rest/reference/repos#delete-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/contributors`](/rest/reference/repos#list-repository-contributors)
|
||||
- [`GET /repos/{owner}/{repo}/forks`](/rest/reference/repos#list-forks)
|
||||
@@ -677,7 +546,6 @@ ms.locfileid: '148107239'
|
||||
- [`GET /repos/{owner}/{repo}/languages`](/rest/reference/repos#list-repository-languages)
|
||||
- [`GET /repos/{owner}/{repo}/tags`](/rest/reference/repos#list-repository-tags)
|
||||
- [`GET /repos/{owner}/{repo}/teams`](/rest/reference/repos#list-repository-teams)
|
||||
- [`POST /repos/{owner}/{repo}/transfer`](/rest/reference/repos#transfer-a-repository)
|
||||
- [`GET /users/{username}/repos`](/rest/reference/repos#list-repositories-for-a-user)
|
||||
- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user)
|
||||
- [`POST /user/repos`](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
|
||||
@@ -687,16 +555,11 @@ ms.locfileid: '148107239'
|
||||
- [`DELETE /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#delete-autolink)
|
||||
- [`PUT /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes)
|
||||
- [`DELETE /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/reference/repos#list-branches)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/reference/repos#merge-a-branch)
|
||||
- [`POST /repos/{owner}/{repo}/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event)
|
||||
- [`GET /repos/{owner}/{repo}/keys`](/rest/reference/repos#list-deploy-keys)
|
||||
- [`POST /repos/{owner}/{repo}/keys`](/rest/reference/repos#create-a-deploy-key)
|
||||
- [`GET /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#get-a-deploy-key)
|
||||
- [`DELETE /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#delete-a-deploy-key)
|
||||
- [`PUT /repos/{owner}/{repo}/lfs`](/rest/reference/repos#enable-git-lfs-for-a-repository)
|
||||
- [`DELETE /repos/{owner}/{repo}/lfs`](/rest/reference/repos#disable-git-lfs-for-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/releases`](/rest/reference/repos#list-releases)
|
||||
- [`POST /repos/{owner}/{repo}/releases`](/rest/reference/repos#create-a-release)
|
||||
- [`GET /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#get-a-release)
|
||||
@@ -729,7 +592,6 @@ ms.locfileid: '148107239'
|
||||
|
||||
## 비밀 검사
|
||||
|
||||
- [`GET /enterprises/{enterprise}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)
|
||||
- [`GET /orgs/{org}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-organization)
|
||||
- [`GET /repos/{owner}/{repo}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository)
|
||||
- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#get-a-secret-scanning-alert)
|
||||
@@ -797,7 +659,6 @@ ms.locfileid: '148107239'
|
||||
- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
|
||||
- [`GET /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
|
||||
- [`DELETE /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
|
||||
- [`GET /users/{username}/hovercard`](/rest/reference/users#get-contextual-information-for-a-user)
|
||||
- [`GET /users/{username}/keys`](/rest/reference/users#list-public-keys-for-a-user)
|
||||
- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
|
||||
- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
|
||||
|
||||
@@ -11,6 +11,7 @@ topics:
|
||||
- API
|
||||
children:
|
||||
- /resources-in-the-rest-api
|
||||
- /api-versions
|
||||
- /media-types
|
||||
- /other-authentication-methods
|
||||
- /troubleshooting
|
||||
@@ -20,12 +21,13 @@ children:
|
||||
- /endpoints-available-for-github-apps
|
||||
- /endpoints-available-for-fine-grained-personal-access-tokens
|
||||
- /permissions-required-for-github-apps
|
||||
- /breaking-changes
|
||||
- /permissions-required-for-fine-grained-personal-access-tokens
|
||||
ms.openlocfilehash: 413b4771d77508a1916473009891e1444fa5ea32
|
||||
ms.sourcegitcommit: d697e0ea10dc076fd62ce73c28a2b59771174ce8
|
||||
ms.openlocfilehash: 7e5671dcf94766dfcc8d1a39dd47191e20eb1513
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 10/20/2022
|
||||
ms.locfileid: '148098105'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184237'
|
||||
---
|
||||
|
||||
|
||||
@@ -5,18 +5,18 @@ versions:
|
||||
feature: pat-v2
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: '{% data variables.product.pat_v2_caps %} permissions'
|
||||
ms.openlocfilehash: 97154c54229f66f3a6b3bf852f7aabab89a0d2ee
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: 46a82b0212d4cda2b6883c0b33ba2acb2e50b9d0
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107687'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184214'
|
||||
---
|
||||
## {% data variables.product.pat_v2 %}에 필요한 권한 정보
|
||||
|
||||
{% data variables.product.pat_v2 %}을(를) 만들 때 사용 권한 집합을 부여합니다. 권한은 {% data variables.product.prodname_github_app %}이(가) API를 통해 액세스할 수 있는 리소스를 정의합니다. 자세한 내용은 "[{% data variables.product.pat_generic %} 만들기"를 참조하세요](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
||||
{% data variables.product.pat_v2 %}을(를) 만들 때 사용 권한 집합을 부여합니다. 권한은 {% data variables.product.prodname_github_app %}이(가) API를 통해 액세스할 수 있는 리소스를 정의합니다. 자세한 내용은 "[{% data variables.product.pat_generic %} 만들기](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)"를 참조하세요.
|
||||
|
||||
## 동작
|
||||
## 작업
|
||||
|
||||
- [`GET /repos/{owner}/{repo}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-a-repository) (읽기)
|
||||
- [`GET /repos/{owner}/{repo}/actions/caches`](/rest/actions/cache#list-github-actions-caches-for-a-repository) (읽기)
|
||||
@@ -65,11 +65,10 @@ ms.locfileid: '148107687'
|
||||
- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) (쓰기)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) (쓰기)
|
||||
- [`POST /orgs/{org}/repos`](/rest/reference/repos#create-an-organization-repository) (쓰기)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/reference/repos/#update-a-repository) (쓰기)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/repos/repos#update-a-repository) (쓰기)
|
||||
- [`DELETE /repos/{owner}/{repo}`](/rest/reference/repos#delete-a-repository) (쓰기)
|
||||
- [`POST /repos/{owner}/{repo}/forks`](/rest/reference/repos#create-a-fork) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/teams`](/rest/reference/repos#list-repository-teams) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/transfer`](/rest/reference/repos#transfer-a-repository) (쓰기)
|
||||
- [`POST /user/repos`](/rest/reference/repos#create-a-repository-for-the-authenticated-user) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-a-repository) (읽기)
|
||||
- [`PUT /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-a-repository) (쓰기)
|
||||
@@ -130,16 +129,6 @@ ms.locfileid: '148107687'
|
||||
|
||||
## 확인
|
||||
|
||||
- [`POST /repos/{owner}/{repo}/check-runs`](/rest/reference/checks#create-a-check-run) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#get-a-check-run) (읽기)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#update-a-check-run) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations`](/rest/reference/checks#list-check-run-annotations) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/check-runs/{check_run_id}/rerequest`](/rest/reference/checks#rerequest-a-check-run) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites`](/rest/reference/checks#create-a-check-suite) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}`](/rest/reference/checks#get-a-check-suite) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites/{check_suite_id}/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (쓰기)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (쓰기)
|
||||
- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#review-pending-deployments-for-a-workflow-run) (읽기)
|
||||
|
||||
## Codespaces
|
||||
@@ -196,20 +185,12 @@ ms.locfileid: '148107687'
|
||||
- [`POST /repos/{owner}/{repo}/git/refs`](/rest/reference/git#create-a-reference) (쓰기)
|
||||
- [`POST /repos/{owner}/{repo}/git/tags`](/rest/reference/git#create-a-tag-object) (쓰기)
|
||||
- [`POST /repos/{owner}/{repo}/git/trees`](/rest/reference/git#create-a-tree) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/import`](/rest/reference/migrations#get-an-import-status) (읽기)
|
||||
- [`PUT /repos/{owner}/{repo}/import`](/rest/reference/migrations#start-an-import) (쓰기)
|
||||
- [`PATCH /repos/{owner}/{repo}/import`](/rest/reference/migrations#update-an-import) (쓰기)
|
||||
- [`DELETE /repos/{owner}/{repo}/import`](/rest/reference/migrations#cancel-an-import) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/import/authors`](/rest/reference/migrations#get-commit-authors) (읽기)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/authors/{author_id}`](/rest/reference/migrations#map-a-commit-author) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/import/large_files`](/rest/reference/migrations#get-large-files) (읽기)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (쓰기)
|
||||
- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#merge-a-pull-request) (쓰기)
|
||||
- [`POST /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (쓰기)
|
||||
- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-commit-comment-reaction) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/reference/repos#list-branches) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository) (쓰기)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/reference/repos#merge-a-branch) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/branches/branches#list-branches) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/branches/branches#sync-a-fork-branch-with-the-upstream-repository) (쓰기)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/branches/branches#merge-a-branch) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases`](/rest/reference/code-scanning#list-codeql-databases) (읽기)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases/{language}`](/rest/reference/code-scanning#get-codeql-database) (읽기)
|
||||
- [`PATCH /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#update-a-commit-comment) (쓰기)
|
||||
@@ -320,7 +301,7 @@ ms.locfileid: '148107687'
|
||||
- [`GET /repos/{owner}/{repo}/issues`](/rest/reference/issues#list-repository-issues) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/issues`](/rest/reference/issues#create-an-issue) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#get-an-issue) (읽기)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues/#update-an-issue) (쓰기)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#update-an-issue) (쓰기)
|
||||
- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#lock-an-issue) (쓰기)
|
||||
- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#unlock-an-issue) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#list-labels-for-an-issue) (읽기)
|
||||
@@ -409,7 +390,6 @@ ms.locfileid: '148107687'
|
||||
- [`POST /gists/{gist_id}/forks`](/rest/reference/gists#fork-a-gist) (읽기)
|
||||
- [`PUT /gists/{gist_id}/star`](/rest/reference/gists#star-a-gist) (읽기)
|
||||
- [`DELETE /gists/{gist_id}/star`](/rest/reference/gists#unstar-a-gist) (읽기)
|
||||
- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user) (읽기)
|
||||
- [`GET /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#check-team-permissions-for-a-repository) (읽기)
|
||||
- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) (읽기)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) (읽기)
|
||||
@@ -439,10 +419,6 @@ ms.locfileid: '148107687'
|
||||
- [`GET /search/labels`](/rest/reference/search#search-labels) (읽기)
|
||||
- [`GET /repos/{owner}/{repo}/topics`](/rest/reference/repos#get-all-repository-topics) (읽기)
|
||||
|
||||
## 공지
|
||||
|
||||
- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user) (읽기)
|
||||
|
||||
## 조직 관리
|
||||
|
||||
{% ifversion ghec %}- [`GET /orgs/{org}/audit-log`](/rest/reference/orgs#get-audit-log) (읽기){% endif %}
|
||||
@@ -467,7 +443,7 @@ ms.locfileid: '148107687'
|
||||
- [`GET /orgs/{org}/security-managers`](/rest/reference/orgs#list-security-manager-teams) (읽기)
|
||||
- [`PUT /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#add-a-security-manager-team) (쓰기)
|
||||
- [`DELETE /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#remove-a-security-manager-team) (쓰기)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs/#update-an-organization) (쓰기)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs#update-an-organization) (쓰기)
|
||||
- [`GET /orgs/{org}/installations`](/rest/reference/orgs#list-app-installations-for-an-organization) (읽기)
|
||||
|
||||
## 조직 codespaces
|
||||
@@ -491,6 +467,7 @@ ms.locfileid: '148107687'
|
||||
## 조직 사용자 지정 역할
|
||||
|
||||
- [`GET /organizations/{organization_id}/custom_roles`](/rest/reference/orgs#list-custom-repository-roles-in-an-organization) (읽기)
|
||||
- [`GET /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs/#get-a-custom-role) (읽기)
|
||||
- [`PATCH /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#update-a-custom-role) (쓰기)
|
||||
- [`DELETE /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#delete-a-custom-role) (쓰기)
|
||||
- [`GET /orgs/{org}/fine_grained_permissions`](/rest/reference/orgs#list-fine-grained-permissions-for-an-organization) (읽기)
|
||||
@@ -523,13 +500,6 @@ ms.locfileid: '148107687'
|
||||
- [`POST /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/reference/orgs#redeliver-a-delivery-for-an-organization-webhook) (쓰기)
|
||||
- [`POST /orgs/{org}/hooks/{hook_id}/pings`](/rest/reference/orgs#ping-an-organization-webhook) (쓰기)
|
||||
|
||||
## 조직 프로젝트
|
||||
|
||||
- [`PUT /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#add-or-update-team-project-permissions) (관리자)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#remove-a-project-from-a-team) (관리자)
|
||||
- [`GET /orgs/{org}/projects`](/rest/reference/projects#list-organization-projects) (읽기)
|
||||
- [`POST /orgs/{org}/projects`](/rest/reference/projects#create-an-organization-project) (쓰기)
|
||||
|
||||
## 조직 비밀
|
||||
|
||||
- [`GET /orgs/{org}/actions/secrets`](/rest/reference/actions#list-organization-secrets) (읽기)
|
||||
@@ -640,30 +610,6 @@ ms.locfileid: '148107687'
|
||||
- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/pings`](/rest/webhooks/repos#ping-a-repository-webhook) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/tests`](/rest/webhooks/repos#test-the-push-repository-webhook) (읽기)
|
||||
|
||||
## 리포지토리 프로젝트
|
||||
|
||||
- [`GET /projects/{project_id}/collaborators`](/rest/reference/projects#list-project-collaborators) (쓰기)
|
||||
- [`PUT /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#add-project-collaborator) (쓰기)
|
||||
- [`DELETE /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#remove-project-collaborator) (쓰기)
|
||||
- [`GET /projects/{project_id}/collaborators/{username}/permission`](/rest/reference/projects#get-project-permission-for-a-user) (쓰기)
|
||||
- [`GET /projects/{project_id}`](/rest/reference/projects#get-a-project) (읽기)
|
||||
- [`PATCH /projects/{project_id}`](/rest/reference/projects#update-a-project) (쓰기)
|
||||
- [`DELETE /projects/{project_id}`](/rest/reference/projects#delete-a-project) (쓰기)
|
||||
- [`GET /projects/{project_id}/columns`](/rest/reference/projects#list-project-columns) (읽기)
|
||||
- [`POST /projects/{project_id}/columns`](/rest/reference/projects#create-a-project-column) (쓰기)
|
||||
- [`GET /projects/columns/{column_id}`](/rest/reference/projects#get-a-project-column) (읽기)
|
||||
- [`PATCH /projects/columns/{column_id}`](/rest/reference/projects#update-a-project-column) (쓰기)
|
||||
- [`DELETE /projects/columns/{column_id}`](/rest/reference/projects#delete-a-project-column) (쓰기)
|
||||
- [`GET /projects/columns/{column_id}/cards`](/rest/reference/projects#list-project-cards) (읽기)
|
||||
- [`POST /projects/columns/{column_id}/cards`](/rest/reference/projects#create-a-project-card) (쓰기)
|
||||
- [`POST /projects/columns/{column_id}/moves`](/rest/reference/projects#move-a-project-column) (쓰기)
|
||||
- [`GET /projects/columns/cards/{card_id}`](/rest/reference/projects#get-a-project-card) (읽기)
|
||||
- [`PATCH /projects/columns/cards/{card_id}`](/rest/reference/projects#update-a-project-card) (쓰기)
|
||||
- [`DELETE /projects/columns/cards/{card_id}`](/rest/reference/projects#delete-a-project-card) (쓰기)
|
||||
- [`POST /projects/columns/cards/{card_id}/moves`](/rest/reference/projects#move-a-project-card) (쓰기)
|
||||
- [`GET /repos/{owner}/{repo}/projects`](/rest/reference/projects#list-repository-projects) (읽기)
|
||||
- [`POST /repos/{owner}/{repo}/projects`](/rest/reference/projects#create-a-repository-project) (쓰기)
|
||||
|
||||
## 코드 검사 경고
|
||||
|
||||
- [`GET /orgs/{org}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-organization) (읽기)
|
||||
@@ -727,6 +673,10 @@ ms.locfileid: '148107687'
|
||||
- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#update-a-discussion-comment) (쓰기)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#delete-a-discussion-comment) (쓰기)
|
||||
|
||||
## 취약성 경고
|
||||
|
||||
- [`GET /orgs/{org}/dependabot/alerts`](/rest/dependabot/alerts#list-dependabot-alerts-for-an-organization) (읽기)
|
||||
|
||||
## 감시
|
||||
|
||||
- [`GET /users/{username}/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) (읽기)
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -13,8 +13,12 @@ topics:
|
||||
- API
|
||||
---
|
||||
|
||||
{% ifversion api-date-versioning %}
|
||||
## API version
|
||||
|
||||
This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}.
|
||||
Available resources may vary between REST API versions. You should use the `X-GitHub-Api-Version` header to specify an API version. For more information, see "[API Versions](/rest/overview/api-versions)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Schema
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting
|
||||
intro: Learn how to resolve the most common problems people encounter in the REST API.
|
||||
title: 문제 해결
|
||||
intro: REST API에서 발생하는 가장 일반적인 문제를 해결하는 방법을 알아봅니다.
|
||||
redirect_from:
|
||||
- /v3/troubleshooting
|
||||
versions:
|
||||
@@ -10,62 +10,73 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: ecfa3a360ef9b042d96a1f80a2f0cde49390727f
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184236'
|
||||
---
|
||||
API에서 몇 가지 이상한 점이 발생하는 경우 발생할 수 있는 몇 가지 문제에 대한 해결 목록은 다음과 같습니다.
|
||||
|
||||
{% ifversion api-date-versioning %}
|
||||
|
||||
## `400` 지원되지 않는 API 버전에 대한 오류
|
||||
|
||||
If you're encountering some oddities in the API, here's a list of resolutions to
|
||||
some of the problems you may be experiencing.
|
||||
헤더를 `X-GitHub-Api-Version` 사용하여 API 버전을 지정해야 합니다. 예를 들면 다음과 같습니다.
|
||||
|
||||
## `404` error for an existing repository
|
||||
```shell
|
||||
$ curl {% data reusables.rest-api.version-header %} https://api.github.com/zen
|
||||
```
|
||||
|
||||
Typically, we send a `404` error when your client isn't properly authenticated.
|
||||
You might expect to see a `403 Forbidden` in these cases. However, since we don't
|
||||
want to provide _any_ information about private repositories, the API returns a
|
||||
`404` error instead.
|
||||
존재하지 않는 버전을 지정하면 오류가 발생합니다 `400` .
|
||||
|
||||
To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), [third-party application restrictions][oap-guide] are not blocking access, and that [the token has not expired or been revoked](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
|
||||
자세한 내용은 "[API 버전"을 참조하세요](/rest/overview/api-versions).
|
||||
|
||||
## Not all results returned
|
||||
{% endif %}
|
||||
|
||||
Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support
|
||||
pagination. If you're making requests and receiving an incomplete set of results, you're
|
||||
probably only seeing the first page. You'll need to request the remaining pages
|
||||
in order to get more results.
|
||||
## 기존 리포지토리에 대한 `404` 오류
|
||||
|
||||
It's important to *not* try and guess the format of the pagination URL. Not every
|
||||
API call uses the same structure. Instead, extract the pagination information from
|
||||
[the Link Header](/rest#pagination), which is sent with every request.
|
||||
일반적으로 클라이언트가 제대로 인증되지 않으면 `404` 오류가 발생합니다.
|
||||
이러한 경우에 `403 Forbidden`이 표시될 것으로 예상할 수 있습니다. 그러나 프라이빗 리포지토리에 대한 어떤 정보도 제공하지 않기 때문에 API는 대신 `404` 오류를 반환합니다.
|
||||
|
||||
문제를 해결하려면 [올바르게 인증하고](/guides/getting-started/), [OAuth 액세스 토큰에 필요한 범위가 있고](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), [타사 애플리케이션 제한][oap-guide]이 액세스를 차단하지 않으며, [토큰이 만료되거나 해지되지 않았는지](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation) 확인합니다.
|
||||
|
||||
## 모든 결과가 반환되지는 않음
|
||||
|
||||
대부분의 API 호출은 리소스 목록(예: 사용자, 문제 등)에 액세스하여 페이지 매김을 지원합니다. 요청을 수행하고 불완전한 결과 집합을 수신하는 경우 첫 번째 페이지만 표시할 수 있습니다. 더 많은 결과를 얻으려면 나머지 페이지를 요청해야 합니다.
|
||||
|
||||
페이지 매김 URL의 형식을 시도하고 추측하지 않는 것이 중요합니다. 모든 API 호출이 동일한 구조를 사용하는 것은 아닙니다. 대신 모든 요청과 함께 전송되는 [링크 헤더](/rest#pagination)에서 페이지 매김 정보를 추출합니다.
|
||||
|
||||
[oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Basic authentication errors
|
||||
## 기본 인증 오류
|
||||
|
||||
On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work.
|
||||
2020년 11월 13일에 REST API 및 OAuth 권한 부여 API에 대한 사용자 이름 및 암호 인증은 더 이상 사용되지 않으며 더 이상 작동하지 않습니다.
|
||||
|
||||
### Using `username`/`password` for basic authentication
|
||||
### 기본 인증에 `username`/`password` 사용
|
||||
|
||||
If you're using `username` and `password` for API calls, then they are no longer able to authenticate. For example:
|
||||
API 호출에 `username` 및 `password`를 사용하는 경우 더 이상 인증할 수 없습니다. 예를 들면 다음과 같습니다.
|
||||
|
||||
```bash
|
||||
curl -u my_user:my_password https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
Instead, use a [{% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development:
|
||||
대신 엔드포인트를 테스트하거나 로컬 개발을 수행할 때 [{% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) 를 사용합니다.
|
||||
|
||||
```bash
|
||||
curl -H 'Authorization: Bearer my_access_token' https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header:
|
||||
OAuth 앱의 경우 [웹 애플리케이션 흐름](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)을 사용하여 API 호출의 헤더에 사용할 OAuth 토큰을 생성해야 합니다.
|
||||
|
||||
```bash
|
||||
curl -H 'Authorization: Bearer my-oauth-token' https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
## Timeouts
|
||||
## 시간 제한
|
||||
|
||||
If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response.
|
||||
{% data variables.product.product_name %}이(가) API 요청을 처리하는 데 10초 이상 걸리면 {% data variables.product.product_name %}이(가) 요청을 종료하고 시간 제한 응답을 받게 됩니다.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Pull request review comments
|
||||
title: 끌어오기 요청 검토 설명
|
||||
shortTitle: Review comments
|
||||
intro: ''
|
||||
versions:
|
||||
@@ -11,10 +11,15 @@ topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: d076bead1efdb07c3fcce3472798bddeaf9908e6
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181308'
|
||||
---
|
||||
## 끌어오기 요청 검토 주석 API 정보
|
||||
|
||||
## About the Pull request review comments API
|
||||
|
||||
Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
|
||||
끌어오기 요청 검토 주석은 끌어오기 요청 검토 중에 만든 통합 차이의 일부에 대한 주석입니다. 주석 커밋 및 주석 발행은 끌어오기 요청 검토 주석과 다릅니다. 커밋에 직접 커밋 주석을 적용하고 통합 차이의 일부를 참조하지 않고 문제 주석을 적용합니다. 자세한 내용은 “[커밋 주석 만들기](/rest/reference/commits#create-a-commit-comment)” 및 “[문제 주석 만들기](/rest/reference/issues#create-an-issue-comment)”를 참조하세요.
|
||||
|
||||
{% data reusables.pull_requests.issues-media-types %}
|
||||
|
||||
@@ -9,12 +9,12 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 80e4a5a5257a8f2615b402567f91daa9e68a0077
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: b140c41062e4fea4c1cb1299b23de774963913af
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145124966'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181324'
|
||||
---
|
||||
## 끌어오기 API 정보
|
||||
|
||||
@@ -26,12 +26,12 @@ ms.locfileid: '145124966'
|
||||
|
||||
끌어오기 요청에 지원되는 미디어 유형입니다.
|
||||
|
||||
application/vnd.github.VERSION.raw+json
|
||||
application/vnd.github.VERSION.text+json
|
||||
application/vnd.github.VERSION.html+json
|
||||
application/vnd.github.VERSION.full+json
|
||||
application/vnd.github.VERSION.diff
|
||||
application/vnd.github.VERSION.patch
|
||||
application/vnd.github.raw+json
|
||||
application/vnd.github.text+json
|
||||
application/vnd.github.html+json
|
||||
application/vnd.github.full+json
|
||||
application/vnd.github.diff
|
||||
application/vnd.github.patch
|
||||
|
||||
자세한 내용은 “[사용자 지정 미디어 유형](/rest/overview/media-types)”을 참조하세요.
|
||||
|
||||
|
||||
@@ -11,13 +11,15 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: ee55b646dd58b4f91227c6d629c2e07d834b6dfd
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: 6e07a6cbbdb368ef530b81a6c9cc3893e1590ac4
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145124960'
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148184080'
|
||||
---
|
||||
## 끌어오기 요청 검토 API 정보
|
||||
|
||||
끌어오기 요청 검토는 끌어오기 요청에 대한 끌어오기 요청 검토 주석 그룹이며 상태 및 선택적 본문 주석과 함께 그룹화됩니다.
|
||||
|
||||
{% data reusables.pull_requests.issues-media-types %}
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 50875021a506201a90cbac62db521604a390a586
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: fd3619faeb8ccaeaa70e8a2be050881b4a169b64
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147060332'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181317'
|
||||
---
|
||||
## 리포지토리 콘텐츠 API 정보
|
||||
|
||||
@@ -26,8 +26,8 @@ ms.locfileid: '147060332'
|
||||
|
||||
[README](/rest/reference/repos#get-a-repository-readme), [파일](/rest/reference/repos#get-repository-content), [symlink](/rest/reference/repos#get-repository-content)는 다음과 같은 사용자 지정 미디어 형식을 지원합니다.
|
||||
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.VERSION.html
|
||||
application/vnd.github.raw
|
||||
application/vnd.github.html
|
||||
|
||||
파일 내용을 검색하려면 `.raw` 미디어 형식을 사용합니다.
|
||||
|
||||
@@ -35,7 +35,7 @@ Markdown 또는 AsciiDoc와 같은 태그 파일의 경우 `.html` 미디어 형
|
||||
|
||||
[모든 개체](/rest/reference/repos#get-repository-content)는 다음과 같은 사용자 지정 미디어 형식을 지원합니다.
|
||||
|
||||
application/vnd.github.VERSION.object
|
||||
application/vnd.github.object
|
||||
|
||||
콘텐츠 형식에 관계없이 일관된 개체 형식으로 콘텐츠를 검색하려면 `object` 미디어 형식 매개 변수를 사용합니다. 예를 들어 응답은 디렉터리의 개체 배열 대신 개체 배열을 포함하는 `entries` 특성이 있는 개체가 됩니다.
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: a0c8b24bacdd41e32d9b8bdd0d8850e7a6ada557
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: a9f12214edcef8a107ad9c447fea7207cfdc48f4
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "145114751"
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148184088"
|
||||
---
|
||||
동시 작업 또는 워크플로가 큐에 대기 중인 경우 리포지토리의 동일한 동시성 그룹을 사용하는 다른 작업 또는 워크플로가 진행 중이면 대기 중인 작업 또는 워크플로는 `pending` 상태가 됩니다. 동시성 그룹에서 이전에 보류 중인 작업 또는 워크플로는 모두 취소됩니다. 동일한 동시성 그룹에서 현재 실행 중인 작업 또는 워크플로도 취소하려면 `cancel-in-progress: true`를 지정합니다.
|
||||
|
||||
@@ -26,7 +26,7 @@ concurrency: ci-${{ github.ref }}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.ref }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
@@ -38,7 +38,7 @@ concurrency:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.head_ref || github.run_id }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
@@ -53,7 +53,7 @@ concurrency:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.workflow }}-${{ github.ref }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: a95067136ba91760fb48dae77a42cf9b9377dbeb
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148184069"
|
||||
---
|
||||
SAML SSO를 사용하도록 설정한 후 {% data variables.product.prodname_oauth_app %} 및 {% data variables.product.prodname_github_app %} 권한 부여를 취소하고 다시 인증해야 조직에 액세스할 수 있습니다. 자세한 내용은 "[{% data variables.product.prodname_oauth_apps %} 권한 부여](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps#oauth-apps-and-organizations)"를 참조하세요.
|
||||
@@ -1,116 +1,192 @@
|
||||
---
|
||||
ms.openlocfilehash: e0bf1f4b7bbd5fcb145a6e869dd442fd8e53108a
|
||||
ms.sourcegitcommit: b4996daba2e75b3368f39316e6929602f13b961b
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 10/31/2022
|
||||
ms.locfileid: "148120536"
|
||||
---
|
||||
| 범주 이름. | 설명
|
||||
| Category name | Description
|
||||
|------------------|-------------------
|
||||
{%- ifversion fpt or ghec %} | `account` | 조직 계정과 관련된 활동을 포함합니다.
|
||||
| `advisory_credit` | {% data variables.product.prodname_advisory_database %}의 보안 권고에 대한 기여자 크레딧과 관련된 활동을 포함합니다. 자세한 내용은 “[{% data variables.product.prodname_dotcom %} 보안 공지 정보](/github/managing-security-vulnerabilities/about-github-security-advisories)”를 참조하세요.
|
||||
{%- endif %} | `artifact` | {% data variables.product.prodname_actions %} 워크플로 실행 아티팩트와 관련된 활동을 포함합니다.
|
||||
{%- ifversion audit-log-streaming %} | `audit_log_streaming` | 엔터프라이즈 계정의 조직에 대한 스트리밍 감사 로그와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `billing` | 조직의 청구와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | 엔터프라이즈의 비즈니스 설정과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_advanced_security` | 엔터프라이즈의 {% data variables.product.prodname_GH_advanced_security %}과 관련된 활동을 포함합니다. 자세한 내용은 "[엔터프라이즈에 대한 {% data variables.product.prodname_GH_advanced_security %} 기능 관리](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)"를 참조하세요.
|
||||
| `business_secret_scanning` | 엔터프라이즈의 {% data variables.product.prodname_secret_scanning %}과 관련된 활동을 포함합니다. 자세한 내용은 "[엔터프라이즈에 대한 {% data variables.product.prodname_GH_advanced_security %} 기능 관리](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)"를 참조하세요.
|
||||
{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | 엔터프라이즈의 {% data variables.product.prodname_secret_scanning %}에 대한 사용자 지정 패턴과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_secret_scanning_push_protection` | 엔터프라이즈에서 {% data variables.product.prodname_secret_scanning %}의 푸시 보호 기능과 관련된 활동을 포함합니다. 자세한 내용은 "[엔터프라이즈에 대한 {% data variables.product.prodname_GH_advanced_security %} 기능 관리](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)"를 참조하세요.
|
||||
| `business_secret_scanning_push_protection_custom_message` | 엔터프라이즈에서 푸시 보호가 트리거될 때 표시되는 사용자 지정 메시지와 관련된 활동을 포함합니다. 자세한 내용은 "[엔터프라이즈에 대한 {% data variables.product.prodname_GH_advanced_security %} 기능 관리](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)"를 참조하세요.
|
||||
{%- endif %} | `checks` | 도구 모음 및 실행 확인과 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %} | `codespaces` | 조직 codespace와 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `commit_comment` | 커밋 주석 업데이트 또는 삭제와 관련된 활동을 포함합니다.
|
||||
{%- ifversion ghes %} | `config_entry` | 구성 설정과 관련된 활동을 포함합니다. 이러한 이벤트는 사이트 관리자 감사 로그에만 표시됩니다.
|
||||
{%- endif %} | `dependabot_alerts` | 기존 리포지토리의 {% data variables.product.prodname_dependabot_alerts %}에 대한 조직 수준 구성 활동을 포함합니다. 자세한 내용은 “[{% data variables.product.prodname_dependabot_alerts %} 정보](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)”를 참조하세요.
|
||||
| `dependabot_alerts_new_repos` | 조직에서 만든 새 리포지토리의 {% data variables.product.prodname_dependabot_alerts %}에 대한 조직 수준 구성 활동을 포함합니다.
|
||||
| `dependabot_repository_access` | 조직 {% data variables.product.prodname_dependabot %}에서 액세스할 수 있는 프라이빗 리포지토리와 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec or ghes %} | `dependabot_security_updates` | 기존 리포지토리의 {% data variables.product.prodname_dependabot_security_updates %}에 대한 조직 수준 구성 활동을 포함합니다. 자세한 내용은 “[{% data variables.product.prodname_dependabot_security_updates %} 구성](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)”을 참조하세요.
|
||||
| `dependabot_security_updates_new_repos` | 조직에서 만든 새 리포지토리의 {% data variables.product.prodname_dependabot_security_updates %}에 대한 조직 수준 구성 활동을 포함합니다.
|
||||
{%- endif %} | `dependency_graph` | 리포지토리에 대한 종속성 그래프에 대한 조직 수준 구성 활동을 포함합니다. 자세한 내용은 “[종속성 그래프 정보](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”를 참조하세요.
|
||||
| `dependency_graph_new_repos` | 조직에서 만든 새 리포지토리에 대한 조직 수준 구성 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %} | `discussion` | 팀 토론과 관련된 활동을 포함합니다.
|
||||
| `discussion_comment` | 팀 페이지의 토론에 게시된 주석과 관련된 활동을 포함합니다.
|
||||
| `discussion_post` | 팀 페이지에 게시된 토론과 관련된 활동을 포함합니다.
|
||||
| `discussion_post_reply` | 팀 페이지에 게시된 토론에 대한 응답과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | {% data variables.product.prodname_github_connect %}와(과) 관련된 활동을 포함합니다.
|
||||
| `enterprise` | 엔터프라이즈 설정과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | 확인된 엔터프라이즈 도메인과 관련된 활동을 포함합니다.
|
||||
| `enterprise_installation` | {% data variables.product.prodname_github_connect %} 엔터프라이즈 연결과 연결된 {% data variables.product.prodname_github_app %}와(과) 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `environment` | {% data variables.product.prodname_actions %} 환경과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghae %} | `external_group` | OKTA 그룹과 관련된 활동을 포함합니다.
|
||||
| `external_identity` | OKTA 그룹의 사용자와 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `gist` | gist와 관련된 활동을 포함합니다.
|
||||
| `hook` | 웹후크와 관련된 활동을 포함합니다.
|
||||
| `integration` | 계정의 통합과 관련된 활동을 포함합니다.
|
||||
| `integration_installation` | 계정에 설치된 통합과 관련된 활동을 포함합니다.
|
||||
| `integration_installation_request` | 소유자가 조직에서 사용할 통합을 승인하도록 조직 구성원 요청과 관련된 활동을 포함합니다.
|
||||
{%- ifversion ghec or ghae %} | `ip_allow_list` | 조직에 대한 IP 허용 목록을 사용하거나 사용하지 않도록 설정하는 작업과 관련된 활동을 포함합니다.
|
||||
| `ip_allow_list_entry` | 조직에 대한 IP 허용 목록 항목의 생성, 삭제, 편집과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `issue` | 리포지토리의 문제 고정, 전송 또는 삭제와 관련된 활동을 포함합니다.
|
||||
| `issue_comment` | 문제 주석 고정, 전송 또는 삭제와 관련된 활동을 포함합니다.
|
||||
| `issues` | 조직에 대한 문제 만들기를 사용하거나 사용하지 않도록 설정하는 작업과 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | {% data variables.product.prodname_marketplace %} 개발자 계약 서명과 관련된 활동을 포함합니다.
|
||||
| `marketplace_listing` | {% data variables.product.prodname_marketplace %}의 앱 나열과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `members_can_create_pages` | 조직의 리포지토리에 대한 {% data variables.product.prodname_pages %} 사이트의 게시 관리와 관련된 활동을 포함합니다. 자세한 내용은 “[조직의 {% data variables.product.prodname_pages %} 사이트의 게시 관리](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”를 참조하세요.
|
||||
| `members_can_create_private_pages` | 조직의 리포지토리에 대한 프라이빗 {% data variables.product.prodname_pages %} 사이트의 게시 관리와 관련된 활동을 포함합니다.
|
||||
| `members_can_create_public_pages` | 조직의 리포지토리에 대한 퍼블릭 {% data variables.product.prodname_pages %} 사이트의 게시 관리와 관련된 활동을 포함합니다.
|
||||
{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | 조직에 대한 리포지토리 생성을 사용하거나 사용하지 않도록 설정하는 작업과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | 조직 구성원이 종속성 인사이트를 볼 수 있도록 하는 조직 수준 구성 활동을 포함합니다.
|
||||
| `migration` | 원본 위치(예: {% data variables.product.prodname_dotcom_the_website %} 조직 또는 {% data variables.product.prodname_ghe_server %} 인스턴스)에서 대상 {% data variables.product.prodname_ghe_server %} 인스턴스로 데이터를 전송하는 작업과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `oauth_access` | OAuth 액세스 토큰과 관련된 활동을 포함합니다.
|
||||
| `oauth_application` | OAuth 앱과 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %} | `oauth_authorization` | OAuth 앱 권한 부여와 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `org` | 조직 멤버 자격과 관련된 활동을 포함합니다.
|
||||
{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | SAML Single Sign-On에 사용할 자격 증명 권한 부여와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | 조직에서 비밀 검색을 위한 사용자 지정 패턴과 관련된 활동을 포함합니다. 자세한 내용은 “[비밀 검사를 위한 사용자 지정 패턴 정의](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”를 참조하세요.
|
||||
| `org.secret_scanning_push_protection` | 조직의 비밀 검사 사용자 지정 패턴과 관련된 활동을 포함합니다. 자세한 내용은 “[비밀 검사를 사용하여 푸시 보호](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”를 참조하세요.
|
||||
{%- endif %} | `organization_default_label` | 조직의 리포지토리에 대한 기본 레이블과 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec or ghes %} | `organization_domain` | 확인된 조직 도메인과 관련된 활동을 포함합니다.
|
||||
| `organization_projects_change` | 엔터프라이즈의 조직 전체 프로젝트 보드와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | {% data variables.product.prodname_pages %}에 대해 확인된 사용자 지정 도메인과 관련된 활동을 포함합니다.
|
||||
| `payment_method` | 조직이 {% data variables.product.prodname_dotcom %}에 대해 지불하는 방법과 관련된 활동을 포함합니다.
|
||||
| `prebuild_configuration` | {% data variables.product.prodname_github_codespaces %}에 대한 사전 빌드 구성과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` | 사전 수신 후크 환경과 관련된 활동을 포함합니다.
|
||||
| `pre_receive_hook` | 사전 수신 후크와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | 엔터프라이즈에 대한 프라이빗 모드를 사용하도록 설정하는 작업과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `private_repository_forking` | 리포지토리, 조직 또는 엔터프라이즈에 대한 프라이빗 및 내부 리포지토리의 포크 허용과 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %} | `profile_picture` | 조직의 프로필 사진과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `project` | 프로젝트 보드와 관련된 작업을 포함합니다.
|
||||
| `project_field` | 프로젝트 보드의 필드 만들기 및 삭제와 관련된 활동을 포함합니다.
|
||||
| `project_view` | 프로젝트 보드의 보기 만들기 및 삭제와 관련된 활동을 포함합니다.
|
||||
| `protected_branch` | 보호된 분기와 관련된 활동을 포함합니다.
|
||||
| `public_key` | SSH 키 및 배포 키와 관련된 활동을 포함합니다.
|
||||
| `pull_request` | 끌어오기 요청과 관련된 활동을 포함합니다.
|
||||
| `pull_request_review` | 끌어오기 요청 검토와 관련된 활동을 포함합니다.
|
||||
| `pull_request_review_comment` | 끌어오기 요청 검토 주석과 관련된 활동을 포함합니다.
|
||||
| `repo` | 조직에서 소유한 리포지토리와 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %} | `repository_advisory` | {% data variables.product.prodname_advisory_database %}의 보안 권고와 관련된 리포지토리 수준 활동을 포함합니다. 자세한 내용은 “[{% data variables.product.prodname_dotcom %} 보안 공지 정보](/github/managing-security-vulnerabilities/about-github-security-advisories)”를 참조하세요.
|
||||
| `repository_content_analysis` | [프라이빗 리포지토리에 대한 데이터 사용을 사용하거나 사용하지 않도록 설정하는](/articles/about-github-s-use-of-your-data) 작업과 관련된 활동을 포함합니다.
|
||||
| `repository_dependency_graph` | {% ifversion fpt or ghec %}프라이빗 {% endif %}리포지토리에 대한 종속성 그래프를 사용하거나 사용하지 않도록 설정하는 작업과 관련된 리포지토리 수준 활동을 포함합니다. 자세한 내용은 “[종속성 그래프 정보](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”를 참조하세요.
|
||||
{%- endif %} | `repository_image` | 리포지토리의 이미지와 관련된 활동을 포함합니다.
|
||||
| `repository_invitation` | 리포지토리에 참가하기 위한 초대와 관련된 활동을 포함합니다.
|
||||
| `repository_projects_change` | 리포지토리 또는 조직의 모든 리포지토리에 대한 프로젝트 사용과 관련된 활동을 포함합니다.
|
||||
{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning` | 비밀 검사와 관련된 리포지토리 수준 활동을 포함합니다. 자세한 내용은 “[비밀 검사 정보](/github/administering-a-repository/about-secret-scanning)”를 참조하세요.
|
||||
{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | 리포지토리에서 비밀 검색 사용자 지정 패턴과 관련된 활동을 포함합니다. 자세한 내용은 “[비밀 검사를 위한 사용자 지정 패턴 정의](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”를 참조하세요. {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | 리포지토리에서 비밀 검색 사용자 지정 패턴과 관련된 활동을 포함합니다. 자세한 내용은 “[비밀 검사를 사용하여 푸시 보호](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”를 참조하세요.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | 조직 구성원이 조직의 리포지토리 표시 유형을 변경할 수 있도록 허용하는 작업과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `repository_vulnerability_alert` | [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)와 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | {% data variables.product.prodname_dependabot_alerts %}에 대한 리포지토리 수준 구성 활동을 포함합니다.
|
||||
| `required_status_check` | 보호된 분기에 대한 필수 상태 검사와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | 엔터프라이즈의 승인되거나 확인된 도메인에 대한 메일 알림 제한과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion custom-repository-roles %} | `role` | [사용자 지정 리포지토리 역할](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)과 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `secret_scanning` | 기존 리포지토리에서 비밀 검사를 위한 조직 수준 구성 활동을 포함합니다. 자세한 내용은 “[비밀 검사 정보](/github/administering-a-repository/about-secret-scanning)”를 참조하세요.
|
||||
| `secret_scanning_new_repos` | 조직에서 만든 새 리포지토리에 대한 비밀 검사를 위한 조직 수준 구성 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | 보안 키 등록 및 제거와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `sponsors` | 스폰서 단추와 관련된 이벤트를 포함합니다(“[리포지토리에 스폰서 단추 표시](/articles/displaying-a-sponsor-button-in-your-repository)” 참조).
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | 조직 또는 엔터프라이즈의 SSH 인증 기관과 관련된 활동을 포함합니다.
|
||||
| `ssh_certificate_requirement` | 구성원이 SSH 인증서를 사용하여 조직 리소스에 액세스하도록 요구하는 작업과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `staff` | 작업을 수행하는 사이트 관리자와 관련된 활동을 포함합니다.
|
||||
| `team` | 조직의 팀과 관련된 활동을 포함합니다.
|
||||
| `team_discussions` | 조직의 팀 토론 관리와 관련된 활동을 포함합니다.
|
||||
{%- ifversion ghec %} | `team_sync_tenant` | 엔터프라이즈 또는 조직의 IdP와 팀 동기화와 관련된 활동을 포함합니다.
|
||||
{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | 2단계 인증과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `user` | 엔터프라이즈 또는 조직의 사용자와 관련된 활동을 포함합니다.
|
||||
{%- ifversion ghec or ghes %} | `user_license` | 사용자가 엔터프라이즈에서 라이선스를 취득하고 엔터프라이즈의 구성원이 되는 작업과 관련된 활동을 포함합니다.
|
||||
{%- endif %} | `workflows` | {% data variables.product.prodname_actions %} 워크플로와 관련된 활동을 포함합니다.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `account` | Contains activities related to an organization account.
|
||||
| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
{%- endif %}
|
||||
| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts.
|
||||
{%- ifversion audit-log-streaming %}
|
||||
| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `billing` | Contains activities related to an organization's billing.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `business` | Contains activities related to business settings for an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion code-security-audit-log-events %}
|
||||
| `business_advanced_security` | Contains activities related to {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
| `business_secret_scanning` | Contains activities related to {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for {% data variables.product.prodname_secret_scanning %} in an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion code-security-audit-log-events %}
|
||||
| `business_secret_scanning_push_protection` | Contains activities related to the push protection feature of {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
| `business_secret_scanning_push_protection_custom_message` | Contains activities related to the custom message displayed when push protection is triggered in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
| `checks` | Contains activities related to check suites and runs.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `codespaces` | Contains activities related to an organization's codespaces.
|
||||
{%- endif %}
|
||||
| `commit_comment` | Contains activities related to updating or deleting commit comments.
|
||||
{%- ifversion ghes %}
|
||||
| `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log.
|
||||
{%- endif %}
|
||||
| `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
|
||||
| `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
|
||||
| `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access.
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
| `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
|
||||
| `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.
|
||||
{%- endif %}
|
||||
| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
| `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `discussion` | Contains activities related to team discussions.
|
||||
| `discussion_comment` | Contains activities related to comments posted in discussions on a team page.
|
||||
| `discussion_post` | Contains activities related to discussions posted to a team page.
|
||||
| `discussion_post_reply` | Contains activities related to replies to discussions posted to a team page.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes %}
|
||||
| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}.
|
||||
| `enterprise` | Contains activities related to enterprise settings.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec %}
|
||||
| `enterprise_domain` | Contains activities related to verified enterprise domains.
|
||||
| `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments.
|
||||
{%- endif %}
|
||||
{%- ifversion ghae %}
|
||||
| `external_group` | Contains activities related to Okta groups.
|
||||
| `external_identity` | Contains activities related to a user in an Okta group.
|
||||
{%- endif %}
|
||||
| `gist` | Contains activities related to Gists.
|
||||
| `hook` | Contains activities related to webhooks.
|
||||
| `integration` | Contains activities related to integrations in an account.
|
||||
| `integration_installation` | Contains activities related to integrations installed in an account.
|
||||
| `integration_installation_request` | Contains activities related to organization member requests for owners to approve integrations for use in the organization.
|
||||
{%- ifversion ghec or ghae %}
|
||||
| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization.
|
||||
| `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.
|
||||
{%- endif %}
|
||||
| `issue` | Contains activities related to pinning, transferring, or deleting an issue in a repository.
|
||||
| `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments.
|
||||
| `issues` | Contains activities related to enabling or disabling issue creation for an organization.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
| `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}.
|
||||
{%- endif %}
|
||||
| `members_can_create_pages` | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
|
||||
| `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization.
|
||||
| `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization.
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights.
|
||||
| `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance.
|
||||
{%- endif %}
|
||||
| `oauth_access` | Contains activities related to OAuth access tokens.
|
||||
| `oauth_application` | Contains activities related to OAuth Apps.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `oauth_authorization` | Contains activities related to authorizing OAuth Apps.
|
||||
{%- endif %}
|
||||
| `org` | Contains activities related to organization membership.
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on.
|
||||
{%- endif %}
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
| `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
{%- endif %}
|
||||
| `organization_default_label` | Contains activities related to default labels for repositories in an organization.
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
| `organization_domain` | Contains activities related to verified organization domains.
|
||||
| `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}.
|
||||
| `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}.
|
||||
| `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}.
|
||||
{%- endif %}
|
||||
{%- ifversion ghes %}
|
||||
| `pre_receive_environment` | Contains activities related to pre-receive hook environments.
|
||||
| `pre_receive_hook` | Contains activities related to pre-receive hooks.
|
||||
{%- endif %}
|
||||
{%- ifversion ghes %}
|
||||
| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise.
|
||||
{%- endif %}
|
||||
| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `profile_picture` | Contains activities related to an organization's profile picture.
|
||||
{%- endif %}
|
||||
| `project` | Contains activities related to project boards.
|
||||
| `project_field` | Contains activities related to field creation and deletion in a project board.
|
||||
| `project_view` | Contains activities related to view creation and deletion in a project board.
|
||||
| `protected_branch` | Contains activities related to protected branches.
|
||||
| `public_key` | Contains activities related to SSH keys and deploy keys.
|
||||
| `pull_request` | Contains activities related to pull requests.
|
||||
| `pull_request_review` | Contains activities related to pull request reviews.
|
||||
| `pull_request_review_comment` | Contains activities related to pull request review comments.
|
||||
| `repo` | Contains activities related to the repositories owned by an organization.
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
| `repository_content_analysis` | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).
|
||||
| `repository_dependency_graph` | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
{%- endif %}
|
||||
| `repository_image` | Contains activities related to images for a repository.
|
||||
| `repository_invitation` | Contains activities related to invitations to join a repository.
|
||||
| `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization.
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `repository_secret_scanning` | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
{%- endif %}
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization.
|
||||
{%- endif %}
|
||||
| `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.
|
||||
| `required_status_check` | Contains activities related to required status checks for protected branches.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes %}
|
||||
| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise.
|
||||
{%- endif %}
|
||||
{%- ifversion custom-repository-roles %}
|
||||
| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `secret_scanning` | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
| `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization.
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `security_key` | Contains activities related to security keys registration and removal.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
| `sponsors` | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)").
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes or ghae %}
|
||||
| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise.
|
||||
| `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources.
|
||||
{%- endif %}{% ifversion sso-redirect %}
|
||||
| `sso_redirect` | Contains activities related to automatically redirecting users to sign in (see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)").{% endif %}
|
||||
| `staff` | Contains activities related to a site admin performing an action.
|
||||
| `team` | Contains activities related to teams in an organization.
|
||||
| `team_discussions` | Contains activities related to managing team discussions for an organization.
|
||||
{%- ifversion ghec %}
|
||||
| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization.
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghes %}
|
||||
| `two_factor_authentication` | Contains activities related to two-factor authentication.
|
||||
{%- endif %}
|
||||
| `user` | Contains activities related to users in an enterprise or organization.
|
||||
{%- ifversion ghec or ghes %}
|
||||
| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise.
|
||||
{%- endif %}
|
||||
| `workflows` | Contains activities related to {% data variables.product.prodname_actions %} workflows.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 10a6df860ab8205845ae90fcb01d95d8e617096c
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181309"
|
||||
---
|
||||
{% ifversion dependabot-actions-support %} {% data variables.product.prodname_dependabot_security_updates %}는 {% data variables.product.prodname_actions %}의 취약한 종속성을 해결할 수 있습니다. 보안 업데이트를 사용하도록 설정하면 {% data variables.product.prodname_dependabot %}는 워크플로에 사용되는 취약한 {% data variables.product.prodname_actions %}을(를) 패치된 최소 버전으로 업데이트하기 위해 끌어오기 요청을 자동으로 발생합니다. {% endif %}
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: f246dbf76575a4338b8fa28ffbd5439c4121505f
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148184077"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**참고:** 로그인하도록 사용자를 자동으로 리디렉션하는 것은 현재 {% data variables.product.prodname_emus %}에 대한 베타 버전이며 변경될 수 있습니다.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
ms.openlocfilehash: 4e7a2b55a6a6db231bacb232e4a4da0b4101dbf1
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: 1cb33ecd5b87ac110509c21934a0c8747f2087ae
|
||||
ms.sourcegitcommit: 4c72bcff385d7093cc42df79ad17f05cfd900b5f
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147167405"
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148183933"
|
||||
---
|
||||
| 사용자 라이선스 | vCPU | 메모리 | 연결된 스토리지 | 루트 스토리지 |
|
||||
| 사용자 라이선스 | vCPU | 메모리 | 루트 스토리지 | 연결된(데이터) 스토리지 |
|
||||
| :- | -: | -: | -: | -: |
|
||||
| 평가판, 데모 또는 라이트 사용자 10명 | 4 | 32GB | 150GB | 200GB |
|
||||
| 10~3,000 | 8 | 48GB | 300GB | 200GB |
|
||||
| 3,000~5000 | 12 | 64GB | 500GB | 200GB |
|
||||
| 5,000~8000 | 16 | 96GB | 750GB | 200GB |
|
||||
| 8,000~10,000 이상 | 20 | 160 GB | 1000GB | 200GB |
|
||||
| 평가판, 데모 또는 라이트 사용자 10명 | 4 | 32GB | 200GB | 150GB |
|
||||
| 10~3,000 | 8 | 48GB | 200GB | 300GB |
|
||||
| 3,000~5000 | 12 | 64GB | 200GB | 500GB |
|
||||
| 5,000~8000 | 16 | 96GB | 200GB | 750GB |
|
||||
| 8,000~10,000 이상 | 20 | 160 GB | 200GB | 1000GB |
|
||||
|
||||
@@ -1,11 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 5c02cf240a1d23e9549a534381d9914bd8dc0ebd
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: f88150299e77eff08e5db75a7ef5bf5bd460328b
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145110007"
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148184093"
|
||||
---
|
||||
허용 목록을 활성화하면 구성한 IP 주소가 엔터프라이즈 내 조직의 허용 목록에 즉시 추가됩니다. 허용 목록을 비활성화하면 조직 허용 목록에서 주소가 제거됩니다.
|
||||
허용 목록을 활성화하면 구성한 IP 주소가 엔터프라이즈 내 조직의 허용 목록에 즉시 추가됩니다. 허용 목록을 비활성화하면 조직 허용 목록에서 주소가 제거됩니다.
|
||||
|
||||
{% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} 자세한 내용은 "[조직에 허용되는 IP 주소 관리"를 참조하세요](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization).
|
||||
|
||||
엔터프라이즈에 설치된 {% data variables.product.prodname_github_apps %}에 대해 구성된 모든 IP 주소를 허용 목록에 자동으로 추가하도록 선택할 수 있습니다. {% data variables.product.prodname_github_app %}의 작성자는 애플리케이션이 실행되는 IP 주소를 지정하는 애플리케이션의 허용 목록을 구성할 수 있습니다. 본인의 허용 목록을 사용자의 허용 목록으로 상속하면 애플리케이션의 연결 요청 거부를 방지할 수 있습니다. 자세한 내용은 "[GitHub 앱에서 액세스 허용](#allowing-access-by-github-apps)"을 참조하세요.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 5ce9d5cc32dc07a1fe4ead5b16b75a7b10509467
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148184072"
|
||||
---
|
||||
조직 소유자는 조직의 허용 목록에 항목을 추가할 수 있지만 엔터프라이즈 계정의 허용 목록에서 상속된 항목을 관리할 수 없으며 엔터프라이즈 소유자는 조직의 허용 목록에 추가된 항목을 관리할 수 없습니다.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user