Merge branch 'main' into repo-sync
This commit is contained in:
Octomerger Bot
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Konfigurieren von OpenID Connect in Amazon Web Services
|
||||
shortTitle: Configuring OpenID Connect in Amazon Web Services
|
||||
shortTitle: OpenID Connect in AWS
|
||||
intro: 'Verwende OpenID Connect in deinen Workflows, um dich bei Amazon Web Services zu authentifizieren.'
|
||||
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: de-DE
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147876810'
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: '148182257'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -53,7 +53,7 @@ Bearbeite die Vertrauensstellungsrichtlinie, um das `sub`-Feld den Überprüfung
|
||||
}
|
||||
```
|
||||
|
||||
Im folgenden Beispiel wird `ForAllValues` verwendet, um einen Abgleich mit mehreren Bedingungsschlüsseln durchzuführen. `StringLike` wird verwendet, um einen Abgleich mit beliebigen Referenzen im angegebenen Repository durchzuführen. Beachte, dass `ForAllValues` [übermäßige Berechtigungen hat](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_multi-value-conditions.html) und nicht allein in einem `Allow`-Effekt verwendet werden sollte. In diesem Beispiel bedeutet die Aufnahme von `StringLike`, dass eine leere Gruppe in `ForAllValues` die Bedingung weiterhin nicht übergibt:
|
||||
Im folgenden Beispiel wird `StringLike` mit einem Platzhalteroperator (`*`) verwendet, um jedem Branch, jedem Branch für das Mergen des Pull Requests oder jeder Umgebung aus der Organisation und dem Repository `octo-org/octo-repo` die Übernahme einer Rolle in AWS zu ermöglichen.
|
||||
|
||||
```json{:copy}
|
||||
{
|
||||
@@ -69,8 +69,7 @@ Im folgenden Beispiel wird `ForAllValues` verwendet, um einen Abgleich mit mehre
|
||||
"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"
|
||||
}
|
||||
}
|
||||
|
||||
@@ -0,0 +1,166 @@
|
||||
---
|
||||
title: Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen
|
||||
shortTitle: Restricting network traffic
|
||||
intro: 'Du kannst den Zugriff auf dein Unternehmen einschränken und den Zugriff auf deine Ressourcen nur von angegebenen IP-Adressen aus zulassen, indem du eine Liste zugelassener IP-Adressen verwendest.'
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Access management
|
||||
- Enterprise
|
||||
- Fundamentals
|
||||
- Networking
|
||||
- Security
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: d9a4518f2fcc23d4b49967effb7b9a3022a7c6bd
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148184012'
|
||||
---
|
||||
## Informationen zu Einschränkungen beim Netzwerkdatenverkehr
|
||||
|
||||
Standardmäßig können autorisierte Benutzer von einer beliebigen IP-Adresse aus auf dein Unternehmen zugreifen. Du kannst den Zugriff auf Ressourcen {% ifversion ghec %}im Besitz von Organisationen in Enterprise-Konten {% endif %}einschränken, indem du eine Liste zugelassener IP-Adressen konfigurierst. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
Wenn dein Unternehmen {% data variables.product.prodname_emus %} mit OIDC verwendet, kannst du entscheiden, ob du das Feature für Listen zugelassener IP-Adressen von {% data variables.product.company_short %} oder die Einschränkungen per Liste zugelassener IP-Adressen von deinem Identitätsanbieter (IdP) verwenden möchtest. Wenn dein Unternehmen {% data variables.product.prodname_emus %} ohne OIDC verwendet, kannst du das Feature für Listen zugelassener IP-Adressen von {% data variables.product.company_short %} verwenden.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
Standardmäßig werden die Ports 22, 80, 443 und 25 durch die Azure-NSG-Regeln (Network Security Group, Netzwerksicherheitsgruppe) für den gesamten eingehenden Datenverkehr geöffnet. Du kannst dich an den {% data variables.contact.github_support %} wenden, um Zugangsbeschränkungen für {% data variables.product.product_name %} zu konfigurieren.
|
||||
|
||||
Für Einschränkungen mithilfe von Azure-Netzwerksicherheitsgruppen kontaktierst du den {% data variables.contact.github_support %} und gibst die IP-Adressen an, die auf {% data variables.product.product_name %} zugreifen dürfen sollen. Gib die Adressbereiche im Standardformat CIDR (Classless Inter-Domain Routing, klassenloses domänenübergreifendes Routing) an. {% data variables.contact.github_support %} konfiguriert geeignete Firewallregeln, um den Netzwerkzugriff über HTTP, SSH, HTTPS und SMTP zu beschränken. Weitere Informationen findest du unter [Anfordern von Unterstützung beim {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support).
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Informationen zu Listen zugelassener IP-Adressen von {% data variables.product.company_short %}
|
||||
|
||||
Du kannst die Liste zugelassener IP-Adressen von {% data variables.product.company_short %} verwenden, um den Zugriff auf dein Unternehmen und die Ressourcen im Besitz von Organisationen in deinem Unternehmen zu steuern.
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
|
||||
|
||||
## Informationen zur Liste zugelassener IP-Adressen deines Identitätsanbieters
|
||||
|
||||
Wenn du {% data variables.product.prodname_emus %} mit OIDC verwendest, kannst du die Liste zugelassener IP-Adressen deines Identitätsanbieters verwenden.
|
||||
|
||||
Wenn du die Liste zugelassener IP-Adressen deines Identitätsanbieters verwendest, deaktivierst du damit die Konfigurationen der Liste zugelassener IP-Adressen von {% data variables.product.company_short %} für alle Organisationen in deinem Unternehmen und die GraphQL-APIs zum Aktivieren und Verwalten von Listen zugelassener IP-Adressen.
|
||||
|
||||
Standardmäßig führt dein Identitätsanbieter die CAPs bei der anfänglichen interaktiven SAML- oder OIDC-Anmeldung bei {% data variables.product.company_short %} für jede ausgewählte Konfiguration einer Liste zugelassener IP-Adressen aus.
|
||||
|
||||
Die OIDC-CAP gilt nur für Anforderungen an die API, die ein Benutzer-zu-Server-Token verwenden, z. B. ein Token für eine {% data variables.product.prodname_oauth_app %} oder eine {% data variables.product.prodname_github_app %} im Namen von Benutzer*innen. Die OIDC-CAP gilt nicht, wenn eine {% data variables.product.prodname_github_app %} ein Server-zu-Server-Token verwendet. Weitere Informationen findest du unter [Authentifizieren mit {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation) und [Informationen zur Unterstützung von Richtlinie für bedingten Zugriff von Identitätsanbietern](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps).
|
||||
|
||||
Um eine nahtlose Verwendung der OIDC-CAP zu gewährleisten und gleichzeitig die Richtlinie auf Benutzer-zu-Server-Token anzuwenden, musst du alle IP-Bereiche aus jedem {% data variables.product.prodname_github_app %} kopieren, die dein Unternehmen in seiner IdP-Richtlinie verwendet.
|
||||
|
||||
## Verwenden der Liste zugelassener IP-Adressen von {% data variables.product.company_short %}
|
||||
|
||||
### Aktivieren der Liste zugelassener IP-Adressen von {% data variables.product.company_short %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Aktiviere unter „Liste zugelassener IP-Adressen“ die Liste zugelassener IP-Adressen.
|
||||
- Wenn du {% data variables.product.prodname_emus %} mit OIDC verwendest, wählst du das Dropdownmenü aus und klickst auf **GitHub**.
|
||||
|
||||
|
||||
Wähle **Liste zugelassener IP-Adressen aktivieren** aus.
|
||||
|
||||
|
||||
- Wenn du {% data variables.product.prodname_emus %} ohne OIDC verwendest, wählst du **Liste zugelassener IP-Adressen aktivieren** aus.
|
||||
|
||||
1. Klicke auf **Speichern**.
|
||||
|
||||
### Eine zugelassene IP-Adresse hinzufügen
|
||||
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ipv6-allow-lists %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Zulassen des Zugriffs durch {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Eine zugelassene IP-Adresse bearbeiten
|
||||
|
||||
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Klicke auf **Aktualisieren**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Überprüfen der Zulässigkeit einer IP-Adresse
|
||||
|
||||
{% data reusables.identity-and-permissions.about-checking-ip-address %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
|
||||
### Eine zugelassene IP-Adresse löschen
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
|
||||
## Verwenden der Liste zugelassener IP-Adressen deines Identitätsanbieters
|
||||
|
||||
Du kannst die Liste zugelassener IP-Adressen deines Identitätsanbieters verwenden, wenn du {% data variables.product.prodname_emus %} mit OIDC verwendest.
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Wähle unter „Liste zugelassener IP-Adressen“ die Dropdownliste aus, und klicke auf **Identitätsanbieter**.
|
||||
|
||||
|
||||
- Wähle optional die Option **Skip IdP check for applications** (IdP-Überprüfung für Anwendungen überspringen) aus, damit die installierten {% data variables.product.company_short %} und {% data variables.product.prodname_oauth_apps %} auf dein Unternehmen zugreifen können.
|
||||
|
||||
|
||||
1. Klicke auf **Speichern**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Zugelassene IP-Adressen aktivieren
|
||||
|
||||
{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Wähle unter „Liste zugelassener IP-Adressen“ die Option **Liste zugelassener IP-Adressen aktivieren** aus.
|
||||
|
||||
4. Klicke auf **Speichern**.
|
||||
|
||||
## Eine zugelassene IP-Adresse hinzufügen
|
||||
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Zulassen des Zugriffs durch {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Eine zugelassene IP-Adresse bearbeiten
|
||||
|
||||
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Klicke auf **Aktualisieren**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Überprüfen der Zulässigkeit einer IP-Adresse
|
||||
|
||||
{% data reusables.identity-and-permissions.about-checking-ip-address %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
|
||||
## Eine zugelassene IP-Adresse löschen
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_actions %} mit einer IP-Zulassungsliste verwenden
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About SAML for enterprise IAM
|
||||
title: Informationen zu SAML für Enterprise IAM
|
||||
shortTitle: About SAML for IAM
|
||||
intro: 'You can use SAML single sign-on (SSO) {% ifversion ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.location.product_location %}{% elsif ghae %}to {% data variables.location.product_location %}{% endif %}.'
|
||||
intro: 'Du kannst SAML-SSO {% ifversion ghae %}und SCIM (System for Cross-domain Identity Management) {% endif %}verwenden, um zentral den Zugriff {% ifversion ghec %}auf Organisationen im Besitz deines Unternehmens auf {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %} auf {% data variables.location.product_location %}{% elsif ghae %} auf {% data variables.location.product_location %}{% endif %}zu verwalten.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
@@ -22,41 +22,46 @@ redirect_from:
|
||||
- /admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise
|
||||
- /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise
|
||||
- /admin/identity-and-access-management/using-saml-for-enterprise-iam/about-identity-and-access-management-for-your-enterprise
|
||||
ms.openlocfilehash: d719ef81948cef75018b0976fc97ef45c267469f
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180029'
|
||||
---
|
||||
|
||||
## About SAML SSO for {% ifversion ghec or ghae %}your enterprise on {% endif %}{% ifversion ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}
|
||||
## Informationen zu SAML-SSO für {% ifversion ghec or ghae %}dein Unternehmen auf {% endif %}{% ifversion ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your enterprise members manage their own user accounts on {% data variables.location.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %}
|
||||
Wenn deine Unternehmensmitglieder ihre eigenen Benutzerkonten auf {% data variables.location.product_location %} verwalten, kannst du die SAML-Authentifizierung als zusätzliche Zugriffsbeschränkung für dein Unternehmen oder deine Organisation konfigurieren. {% data reusables.saml.dotcom-saml-explanation %}
|
||||
|
||||
{% data reusables.saml.saml-accounts %}
|
||||
|
||||
{% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
|
||||
{% data reusables.saml.about-saml-enterprise-accounts %} Weitere Informationen findest du unter [Konfigurieren von SAML-SSO für dein Unternehmen](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
|
||||
|
||||
Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)."
|
||||
Optional kannst du die Konten deiner Unternehmensmitglieder mit {% data variables.product.prodname_emus %} bereitstellen und verwalten. Informationen dazu, ob SAML-SSO oder {% data variables.product.prodname_emus %} für dein Unternehmen besser geeignet sind, findest du unter [Informationen zur Authentifizierung für dein Unternehmen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise).
|
||||
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)."
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} Weitere Informationen findest du unter [Verwalten von Wiederherstellungscodes für dein Unternehmen](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise).
|
||||
|
||||
After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features.
|
||||
Nach der Aktivierung von SAML SSO kannst du je nach IdP zusätzliche Identitäts- und Zugriffsverwaltungsfeatures aktivieren.
|
||||
|
||||
If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
|
||||
Wenn du Azure AD als IdP verwendest, kannst du mithilfe der Teamsynchronisierung die Teammitgliedschaft für die einzelnen Organisationen verwalten. {% data reusables.identity-and-permissions.about-team-sync %} Weitere Informationen findest du unter [Verwalten der Teamsynchronisierung für Organisationen in deinem Unternehmenskonto](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You cannot use SCIM at the enterprise level unless your enterprise is enabled for {% data variables.product.prodname_emus %}.
|
||||
**Hinweis:** Du kannst SCIM nur auf Unternehmensebene verwenden, wenn {% data variables.product.prodname_emus %} für dein Unternehmen aktiviert ist.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% 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)."
|
||||
{% data reusables.saml.switching-from-org-to-enterprise %} Weitere Informationen findest du unter [Umstellen der SAML-Konfiguration von einer Organisation auf ein Unternehmenskonto](/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).
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
SAML SSO allows people to authenticate and access {% data variables.location.product_location %} through an external system for identity management.
|
||||
Mithilfe von SAML-SSO können sich Personen über ein externes System für die Identitätsverwaltung in {% data variables.location.product_location %} authentifizieren und darauf zugreifen.
|
||||
|
||||
SAML is an XML-based standard for authentication and authorization. When you configure SAML for {% data variables.location.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information about the SAML standard, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia.
|
||||
SAML ist ein XML-basierter Standard für die Authentifizierung und Autorisierung. Wenn du SAML für {% data variables.location.product_location %} konfigurierst, wird das externe System für die Authentifizierung als Identitätsanbieter (Identity Provider, IdP) bezeichnet. Deine Instanz fungiert als SAML-Dienstanbieter (Service Provider, SP). Weitere Informationen zum SAML-Standard findest du auf Wikipedia unter [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language).
|
||||
|
||||
For more information about the configuration of SAML SSO on {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)."
|
||||
Weitere Informationen zur Konfiguration von SAML SSO in {% data variables.product.product_name %} findest du unter [Konfigurieren von SAML Single Sign-On für dein Unternehmen](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise).
|
||||
|
||||
{% data reusables.saml.saml-ghes-account-revocation %}
|
||||
|
||||
@@ -68,23 +73,23 @@ For more information about the configuration of SAML SSO on {% data variables.pr
|
||||
|
||||
{% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
|
||||
|
||||
After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.location.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
|
||||
Nachdem du die Anwendung bei deinem Identitätsanbieter (IdP) für {% data variables.product.product_name %} konfiguriert hast, kannst du Zugriff auf {% data variables.location.product_location %} bereitstellen, indem du die Anwendung Benutzer*innen und Gruppen bei deinem IdP zuweist. Weitere Informationen zu SAML SSO für {% data variables.product.product_name %} findest du unter [Konfigurieren von SAML Single Sign-On für dein Unternehmen](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise).
|
||||
|
||||
{% 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 %} Weitere Informationen findest du unter [Konfigurieren der Benutzerbereitstellung für dein Unternehmen](/admin/authentication/configuring-user-provisioning-for-your-enterprise).
|
||||
|
||||
To learn how to configure both authentication and user provisioning for {% data variables.location.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)."
|
||||
Informationen zum Konfigurieren der Authentifizierung und der Benutzerbereitstellung für {% data variables.location.product_location %} bei deinem Identitätsanbieter findest du unter [Konfigurieren der Authentifizierung und Bereitstellung bei deinem Identitätsanbieter](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Supported IdPs
|
||||
## Unterstützte IdPs
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
|
||||
Wir testen und unterstützen offiziell die folgenden IdPs. Für SAML SSO bieten wir begrenzten Support für alle Identitätsanbieter, die den SAML 2.0-Standard implementieren. Weitere Informationen findest du im [SAML-Wiki](https://wiki.oasis-open.org/security) auf der OASIS-Website.
|
||||
|
||||
IdP | SAML | Team synchronization |
|
||||
IdP | SAML | Teamsynchronisierung |
|
||||
--- | :--: | :-------: |
|
||||
Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | |
|
||||
Active Directory-Verbunddienste (Active Directory Federation Services, AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | |
|
||||
Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} |
|
||||
Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
|
||||
OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
|
||||
@@ -97,7 +102,7 @@ Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
|
||||
|
||||
{% ifversion ghes > 3.3 %}
|
||||
|
||||
If your IdP supports encrypted assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process.
|
||||
Wenn dein IdP verschlüsselte SAML-Assertionen unterstützt, kannst du verschlüsselte Assertionen in {% data variables.product.product_name %} konfigurieren und so während des Authentifizierungsprozesses erhöhte Sicherheit gewährleisten.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -105,7 +110,7 @@ If your IdP supports encrypted assertions, you can configure encrypted assertion
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}.
|
||||
Die folgenden IdPs werden offiziell für die Integration mit {% data variables.product.prodname_ghe_managed %} unterstützt.
|
||||
|
||||
{% data reusables.saml.okta-ae-sso-beta %}
|
||||
|
||||
@@ -115,16 +120,14 @@ The following IdPs are officially supported for integration with {% data variabl
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Mapping {% data variables.product.prodname_ghe_managed %} teams to Okta groups
|
||||
## Zuordnen von {% data variables.product.prodname_ghe_managed %}-Teams zu Okta-Gruppen
|
||||
|
||||
If you use Okta as your IdP, you can map your Okta groups to teams on {% data variables.product.product_name %}. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
|
||||
Wenn du Okta als IdP verwendest, kannst du deine Okta-Gruppen in {% data variables.product.product_name %} zu Teams zuordnen. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
## Weiterführende Themen
|
||||
|
||||
- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website
|
||||
- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website
|
||||
{%- ifversion ghae %}
|
||||
- "[Restricting network traffic to your enterprise with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)"
|
||||
{%- endif %}
|
||||
- [SAML-Wiki](https://wiki.oasis-open.org/security) auf der OASIS-Website
|
||||
- [SCIM (System for Cross-Domain Identity Management): Protokoll (RFC 7644)](https://tools.ietf.org/html/rfc7644) auf der IETF-Website {%- ifversion ghae %}
|
||||
- [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list) {%- endif %}
|
||||
|
||||
@@ -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"
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -7,12 +7,12 @@ type: overview
|
||||
topics:
|
||||
- Enterprise
|
||||
- Fundamentals
|
||||
ms.openlocfilehash: 9e7769fca5b36252fad5566450ba156120491649
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 388e271c17c182a318e8c2d095811ac27633a414
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147389851'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180146'
|
||||
---
|
||||
## Informationen zu {% data variables.product.prodname_ghe_managed %}
|
||||
|
||||
@@ -38,7 +38,7 @@ Optional können Unternehmensbesitzer*innen die eingeschränkte Integration zwis
|
||||
|
||||
## Eingeschränkter Netzwerkzugriff
|
||||
|
||||
Sichere den Zugriff auf dein Unternehmen unter {% data variables.product.prodname_ghe_managed %} mit eingeschränktem Netzwerkzugriff, sodass auf deine Daten nur aus deinem Netzwerk zugegriffen werden kann. Weitere Informationen findest du unter „[Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen](/admin/configuration/restricting-network-traffic-to-your-enterprise)“.
|
||||
Sichere den Zugriff auf dein Unternehmen unter {% data variables.product.prodname_ghe_managed %} mit eingeschränktem Netzwerkzugriff, sodass auf deine Daten nur aus deinem Netzwerk zugegriffen werden kann. Weitere Informationen findest du unter [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).
|
||||
|
||||
## Kommerzielle und staatliche Umgebungen
|
||||
|
||||
|
||||
@@ -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,6 +1,6 @@
|
||||
---
|
||||
title: Telling Git about your signing key
|
||||
intro: 'To sign commits locally, you need to inform Git that there''s a GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or X.509 key you''d like to use.'
|
||||
title: Git zu Signaturschlüsseln benachrichtigen
|
||||
intro: 'Um Commits lokal zu signieren, musst du Git darüber informieren, dass es einen GPG-{% ifversion ssh-commit-verification %}, SSH-{% endif %} oder X.509-Schlüssel gibt, den du verwenden möchtest.'
|
||||
redirect_from:
|
||||
- /articles/telling-git-about-your-gpg-key
|
||||
- /articles/telling-git-about-your-signing-key
|
||||
@@ -15,38 +15,39 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: Tell Git your signing key
|
||||
ms.openlocfilehash: d70911bdf3ff5de93537f7c9acb1374a4f2c90e3
|
||||
ms.sourcegitcommit: aded2711e14a0c2473049d3d7e05c82a74e4c634
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179949'
|
||||
---
|
||||
{% mac %}
|
||||
|
||||
## Telling Git about your GPG key
|
||||
## Git deinen GPG-Schlüssel mitteilen
|
||||
|
||||
If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags.
|
||||
Wenn du einen GPG-Schlüssel verwendest, der mit deiner Committer-Identität und deiner verifizierten E-Mail-Adresse übereinstimmt, die mit deinem Konto auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} verknüpft ist, kannst du mit dem Signieren von Commits und Tags beginnen.
|
||||
|
||||
{% note %}
|
||||
|
||||
If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
|
||||
Wenn du keinen GPG-Schlüssel hast, der deiner Beitragender-Identität entspricht, musst du deinen Schlüssel mit einer E-Mail-Adresse verknüpfen. Weitere Informationen findest du unter „[Zuordnen einer E-Mail zu deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key).“
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you have multiple GPG keys, you need to tell Git which one to use.
|
||||
Wenn du mehrere GPG-Schlüssel hast, musst du Git mitteilen, welcher zu verwenden ist.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
{% data reusables.gpg.configure-gpg-signing %}
|
||||
{% data reusables.gpg.list-keys-with-note %}
|
||||
{% data reusables.gpg.copy-gpg-key-id %}
|
||||
{% data reusables.gpg.paste-gpg-key-id %}
|
||||
{% data reusables.gpg.set-auto-sign %}
|
||||
1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file:
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
|
||||
1. Wenn du die GPG-Suite nicht verwendest, führe den folgenden Befehl in der `zsh` Shell aus, um den GPG-Schlüssel zu deiner `.zshrc` Datei hinzuzufügen, sofern vorhanden, oder zu deiner `.zprofile`Datei:
|
||||
```shell
|
||||
$ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \
|
||||
else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi
|
||||
```
|
||||
Alternatively, if you use the `bash` shell, run this command:
|
||||
Wenn du die `bash` Shell verwendest, führe diesen Befehl aus:
|
||||
```shell
|
||||
$ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
|
||||
else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
|
||||
```
|
||||
1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/):
|
||||
1. Wenn du zur Eingabe einer PIN oder Passphrase aufgefordert werden möchtest, installiere optional `pinentry-mac`. Verwende z. B. [Homebrew](https://brew.sh/):
|
||||
```shell
|
||||
$ brew install pinentry-mac
|
||||
$ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf
|
||||
@@ -57,69 +58,56 @@ If you have multiple GPG keys, you need to tell Git which one to use.
|
||||
|
||||
{% windows %}
|
||||
|
||||
## Telling Git about your GPG key
|
||||
## Git deinen GPG-Schlüssel mitteilen
|
||||
|
||||
If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags.
|
||||
Wenn du einen GPG-Schlüssel verwendest, der mit deiner Committer-Identität und deiner verifizierten E-Mail-Adresse übereinstimmt, die mit deinem Konto auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} verknüpft ist, kannst du mit dem Signieren von Commits und Tags beginnen.
|
||||
|
||||
{% note %}
|
||||
|
||||
If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
|
||||
Wenn du keinen GPG-Schlüssel hast, der deiner Beitragender-Identität entspricht, musst du deinen Schlüssel mit einer E-Mail-Adresse verknüpfen. Weitere Informationen findest du unter „[Zuordnen einer E-Mail zu deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key).“
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you have multiple GPG keys, you need to tell Git which one to use.
|
||||
Wenn du mehrere GPG-Schlüssel hast, musst du Git mitteilen, welcher zu verwenden ist.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
{% data reusables.gpg.configure-gpg-signing %}
|
||||
{% data reusables.gpg.list-keys-with-note %}
|
||||
{% data reusables.gpg.copy-gpg-key-id %}
|
||||
{% data reusables.gpg.paste-gpg-key-id %}
|
||||
{% data reusables.gpg.set-auto-sign %}
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
{% linux %}
|
||||
|
||||
## Telling Git about your GPG key
|
||||
## Git deinen GPG-Schlüssel mitteilen
|
||||
|
||||
If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags.
|
||||
Wenn du einen GPG-Schlüssel verwendest, der mit deiner Committer-Identität und deiner verifizierten E-Mail-Adresse übereinstimmt, die mit deinem Konto auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} verknüpft ist, kannst du mit dem Signieren von Commits und Tags beginnen.
|
||||
|
||||
{% note %}
|
||||
|
||||
If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
|
||||
Wenn du keinen GPG-Schlüssel hast, der deiner Beitragender-Identität entspricht, musst du deinen Schlüssel mit einer E-Mail-Adresse verknüpfen. Weitere Informationen findest du unter „[Zuordnen einer E-Mail zu deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key).“
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you have multiple GPG keys, you need to tell Git which one to use.
|
||||
Wenn du mehrere GPG-Schlüssel hast, musst du Git mitteilen, welcher zu verwenden ist.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
{% data reusables.gpg.configure-gpg-signing %}
|
||||
{% data reusables.gpg.list-keys-with-note %}
|
||||
{% data reusables.gpg.copy-gpg-key-id %}
|
||||
{% data reusables.gpg.paste-gpg-key-id %}
|
||||
{% data reusables.gpg.set-auto-sign %}
|
||||
1. To add your GPG key to your `.bashrc` startup file, run the following command:
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
|
||||
1. Führe zum Hinzufügen des `.bashrc` GPG-Schlüssels zur Startdatei den folgenden Befehl aus:
|
||||
```bash
|
||||
$ [ -f ~/.bashrc ] && echo 'export GPG_TTY=$(tty)' >> ~/.bashrc
|
||||
```
|
||||
{% endlinux %}
|
||||
{% ifversion ssh-commit-verification %}
|
||||
{% endlinux %} {% ifversion ssh-commit-verification %}
|
||||
|
||||
## Telling Git about your SSH key
|
||||
## Mitteilung über deinen SSH-Schlüssel an Git
|
||||
|
||||
You can use an existing SSH key to sign commits and tags, or generate a new one specifically for signing. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
|
||||
Du kannst einen vorhandenen SSH-Schlüssel zum Signieren von Commits und Tags verwenden oder einen neuen Schlüssel speziell zum Signieren generieren. Weitere Informationen findest du unter [Generieren eines neuen SSH-Schlüssels und Hinzufügen des Schlüssels zum SSH-Agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
|
||||
|
||||
{% data reusables.gpg.ssh-git-version %}
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
{% data reusables.gpg.configure-ssh-signing %}
|
||||
{% data reusables.gpg.paste-ssh-public-key %}
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-ssh-signing %} {% data reusables.gpg.paste-ssh-public-key %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.gpg.x-509-key %}
|
||||
## Further reading
|
||||
## Weiterführende Themen
|
||||
|
||||
- "[Adding a new SSH key to your GitHub account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)."
|
||||
- "[Signing commits](/articles/signing-commits)"
|
||||
- "[Signing tags](/articles/signing-tags)"
|
||||
- [Hinzufügen eines neuen SSH-Schlüssels zu deinem GitHub-Konto](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
||||
- [Signieren von Commits](/articles/signing-commits)
|
||||
- [Signieren von Tags](/articles/signing-tags)
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring the CodeQL workflow for compiled languages
|
||||
title: Konfigurieren des CodeQL-Workflows für kompilierte Sprachen
|
||||
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: 'Du kannst konfigurieren, wie {% data variables.product.prodname_dotcom %} mithilfe des {% data variables.code-scanning.codeql_workflow %} Code scannt, der in kompilierten Sprachen für Sicherheitsrisiken und Fehler geschrieben wurde.'
|
||||
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: de-DE
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: '148182266'
|
||||
---
|
||||
{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
|
||||
## Informationen zum {% data variables.code-scanning.codeql_workflow %} und kompilierten Sprachen
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
Um {% data variables.product.prodname_dotcom %} für das {% data variables.product.prodname_code_scanning %} deines Repositorys zu konfigurieren, musst du dem Repository einen {% data variables.product.prodname_actions %}-Workflow hinzufügen. Für {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} füge {% data variables.code-scanning.codeql_workflow %} hinzu. Weitere Informationen findest du unter [Einrichten des {% data variables.product.prodname_code_scanning %} für ein Repository](/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 %} Allgemeine Informationen zum Konfigurieren des {% data variables.product.prodname_code_scanning %} und zum Bearbeiten von Workflowdateien findest du unter [Konfigurieren von {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning) und [Einführung in {% 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)."
|
||||
## Informationen zu „autobuild“ für {% 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 %}
|
||||
{% data variables.product.prodname_code_scanning_capc %} funktioniert durch die Ausführung von Abfragen einer oder mehrerer Datenbanken. Jede Datenbank enthält eine Darstellung des gesamten Codes, der in einer einzelnen Sprache in deinem Repository vorliegt.
|
||||
In den kompilierten Sprachen C/C++, C#,{% ifversion codeql-go-autobuild %} Go{% endif %}{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %} und Java müssen beim Auffüllen dieser Datenbank zunächst der Code kompiliert und Daten extrahiert werden. {% 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.
|
||||
Wenn dein Workflow eine `language`-Matrix verwendet, versucht `autobuild`, jede der kompilierten Sprachen zu kompilieren, die in der Matrix aufgeführt ist. Ohne eine Matrix, versucht `autobuild`, die unterstützte kompilierte Sprache mit den meisten Quelldateien im Repository zu kompilieren. Mit Ausnahme von Go schlägt die Analyse anderer kompilierter Sprachen in deinem Repository fehl, sofern du keine expliziten Buildbefehle angibst.
|
||||
|
||||
{% 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 %} **Hinweis:** {% data reusables.actions.self-hosted-runners-software %} {% else %} **Hinweis:** Wenn du selbst gehostete Runner für {% data variables.product.prodname_actions %} verwendest, musst du möglicherweise zusätzliche Software für den `autobuild`-Prozess installieren. Wenn dein Repository zudem eine bestimmte Version eines Buildtools erfordert, musst du dieses möglicherweise manuell installieren. Weitere Informationen findest du unter [Spezifikationen für auf {% data variables.product.prodname_dotcom %} gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### C/C++
|
||||
|
||||
| Supported system type | System name |
|
||||
| Unterstütztes System | Systemname |
|
||||
|----|----|
|
||||
| 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 |
|
||||
| Betriebssystem | Windows, macOS und Linux |
|
||||
| Buildsystem | Windows: MSbuild und Buildskripts<br/>Linux und macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild und Buildskripts |
|
||||
|
||||
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:
|
||||
Das Verhalten des `autobuild`-Schritts variiert je nach Betriebssystem, auf dem die Extraktion ausgeführt wird. Unter Windows versucht der `autobuild`-Schritt, mit dem folgenden Ansatz automatisch eine geeignete Buildmethode für C/C++ zu erkennen:
|
||||
|
||||
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. Für die Projektmappe (`.sln`) oder Projektdatei (`.vcxproj`), die sich am nächsten beim Stamm befindet, wird `MSBuild.exe` aufgerufen.
|
||||
Wenn `autobuild` mehrere Projektmappen oder Projektdateien mit dem gleichen (kürzesten) Abstand zum obersten Verzeichnis erkennt, versucht autobuild, alle zu kompilieren.
|
||||
2. Ein Skript wird aufgerufen, das wie ein Buildskript aussieht: _build.bat_, _build.cmd_ und _build.exe_ (in dieser Reihenfolge).
|
||||
|
||||
On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
|
||||
Unter Linux und macOS werden die im Repository vorhandenen Dateien vom `autobuild`-Schritt überprüft, um das verwendete Buildsystem zu bestimmen:
|
||||
|
||||
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. Im Stammverzeichnis wird nach einem Buildsystem gesucht.
|
||||
2. Wenn keines gefunden wird, werden die Unterverzeichnisse nach einem eindeutigen Verzeichnis mit einem Buildsystem für C/C++ durchsucht.
|
||||
3. Ein passender Befehl wird ausgeführt, um das System zu konfigurieren.
|
||||
|
||||
### C#
|
||||
|
||||
| Supported system type | System name |
|
||||
| Unterstütztes System | Systemname |
|
||||
|----|----|
|
||||
| Operating system | Windows and Linux |
|
||||
| Build system | .NET and MSbuild, as well as build scripts |
|
||||
| Betriebssystem | Windows und Linux |
|
||||
| Buildsystem | .NET und MSbuild sowie Buildskripts |
|
||||
|
||||
The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
|
||||
Der `autobuild`-Prozess versucht, mit dem folgenden Ansatz automatisch eine geeignete Buildmethode für C# zu erkennen:
|
||||
|
||||
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. Für die Projektmappe (`.sln`) oder Projektdatei (`.csproj`), die sich am nächsten beim Stamm befindet, wird `dotnet build` aufgerufen.
|
||||
2. Für die Projektmappe oder Projektdatei, die sich am nächsten beim Stamm befindet, wird `MSbuild` (Linux) oder `MSBuild.exe` (Windows) aufgerufen.
|
||||
Wenn `autobuild` mehrere Projektmappen oder Projektdateien mit dem gleichen (kürzesten) Abstand zum obersten Verzeichnis erkennt, versucht autobuild, alle zu kompilieren.
|
||||
3. Ein Skript wird aufgerufen, das wie ein Buildskript aussieht: _build_ und _build.sh_ (für Linux in dieser Reihenfolge) oder _build.bat_, _build.cmd_ und _build.exe_ (für Windows in dieser Reihenfolge).
|
||||
|
||||
{% ifversion codeql-go-autobuild %}
|
||||
|
||||
### Go
|
||||
|
||||
| Supported system type | System name |
|
||||
| Unterstütztes System | Systemname |
|
||||
|----|----|
|
||||
| Operating system | Windows, macOS, and Linux |
|
||||
| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
|
||||
| Betriebssystem | Windows, macOS und Linux |
|
||||
| Buildsystem | Go-Module, `dep` und Glide sowie Buildskripts, einschließlich Makefiles und Ninja-Skripts |
|
||||
|
||||
The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
|
||||
Der `autobuild`-Prozess versucht, automatisch einen geeigneten Weg zu finden, die von einem Go-Repository benötigten Abhängigkeiten zu installieren, bevor alle `.go`-Dateien extrahiert werden:
|
||||
|
||||
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. Rufe `make`, `ninja`, `./build` oder `./build.sh` (in dieser Reihenfolge) auf, bis einer dieser Befehle und ein nachfolgendes `go list ./...` auch erfolgreich ist, was zeigt, dass die erforderlichen Abhängigkeiten installiert wurden.
|
||||
2. Wenn keiner dieser Befehle erfolgreich war, suche nach `go.mod`, `Gopkg.toml` oder `glide.yaml` und führe entsprechend `go get` (sofern Vendoring nicht verwendet wird), `dep ensure -v` oder `glide install` aus, um zu versuchen, Abhängigkeiten zu installieren.
|
||||
3. Wenn keine Konfigurationsdateien für diese Abhängigkeits-Manager gefunden werden, ordne schließlich die Repositoryverzeichnisstruktur so neu an, dass sie `GOPATH` hinzugefügt werden kann, und installiere mit `go get` Abhängigkeiten. Die Verzeichnisstruktur wird nach Abschluss der Extraktion in die Normalität zurückgesetzt.
|
||||
4. Extrahiere den gesamten Go-Code im Repository, ähnlich der Ausführung von `go build ./...`.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Java {% ifversion codeql-kotlin-beta %} and Kotlin {% endif %}
|
||||
### Java {% ifversion codeql-kotlin-beta %} und Kotlin {% endif %}
|
||||
|
||||
| Supported system type | System name |
|
||||
| Unterstütztes System | Systemname |
|
||||
|----|----|
|
||||
| Operating system | Windows, macOS, and Linux (no restriction) |
|
||||
| Build system | Gradle, Maven and Ant |
|
||||
| Betriebssystem | Windows, macOS und Linux (keine Einschränkung) |
|
||||
| Buildsystem | Gradle, Maven und Ant |
|
||||
|
||||
The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
|
||||
Der `autobuild`-Prozess versucht, mithilfe dieser Strategie das Buildsystem für Java-Codebasen zu bestimmen:
|
||||
|
||||
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. Im Stammverzeichnis wird nach einer Builddatei gesucht. Eine Prüfung auf Gradle-, dann Maven-, dann Ant-Builddateien erfolgt.
|
||||
2. Die erste gefundene Builddatei wird ausgeführt. Wenn sowohl Gradle- als auch Maven-Dateien vorhanden sind, wird die Gradle-Datei verwendet.
|
||||
3. Andernfalls wird in direkten Unterverzeichnissen des Stammverzeichnisses nach Builddateien gesucht. Wenn nur ein Unterverzeichnis Builddateien enthält, wird die erste Datei ausgeführt, die in diesem Unterverzeichnis ermittelt wurde (mit derselben Einstellung wie für 1). Wenn mehrere Unterverzeichnisse Builddateien enthalten, wird ein Fehler gemeldet.
|
||||
|
||||
## Adding build steps for a compiled language
|
||||
## Hinzufügen von Buildschritten für eine kompilierte Sprache
|
||||
|
||||
{% 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 %} Informationen zum Bearbeiten der Workflowdatei findest du unter [Konfigurieren des {% 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.
|
||||
Nachdem du den `autobuild`-Schritt entfernt hast, hebe die Auskommentierung für den `run`-Schritt auf, und füge für dein Repository geeignete Buildbefehle hinzu. Der `run`-Schritt des Workflows führt Befehlszeilenprogramme mithilfe der Shell des Betriebssystems aus. Du kannst diese Befehle ändern und weitere Befehle hinzufügen, um den Buildprozess anzupassen.
|
||||
|
||||
``` 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)."
|
||||
Weitere Informationen zum Schlüsselwort `run` findest du unter [Workflowsyntax für {% 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#:
|
||||
Wenn dein Repository mehrere kompilierte Sprachen enthält, kannst du sprachspezifische Buildbefehle angeben. Wenn dein Repository z. B. C/C++-, C#- und Java-Code enthält und `autobuild` C/C++ und C# ordnungsgemäß kompilieren kann, jedoch nicht Java, kannst du nach dem `init`-Schritt die folgende Konfiguration in deinem Workflow verwenden. Hiermit werden Buildschritte für Java angegeben, während weiterhin `autobuild` für C/C++ und C# verwendet wird:
|
||||
|
||||
```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)."
|
||||
Weitere Informationen zur `if`-Bedingung findest du unter [Workflowsyntax für 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)."
|
||||
Weitere Tipps und Tricks bei Buildproblemen mit `autobuild` findest du unter [Problembehandlung des {% data variables.product.prodname_codeql %}-Workflows](/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 %}.
|
||||
Wenn du manuelle Buildschritte für kompilierte Sprachen hinzugefügt hast und {% data variables.product.prodname_code_scanning %} in deinem Repository noch immer nicht funktioniert, kontaktiere {% 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 %}
|
||||
|
||||
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Managing privately reported security vulnerabilities
|
||||
intro: Repository maintainers can manage security vulnerabilities that have been privately reported to them by security reseachers for repositories where private vulnerability reporting is enabled.
|
||||
permissions: 'Anyone with admin permissions to a repository can see, review, and manage privately-reported vulnerabilities for the repository.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Manage vulnerability reports
|
||||
---
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
|
||||
|
||||
## About privately reporting a security vulnerability
|
||||
|
||||
Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to you using a simple form.
|
||||
|
||||
When a security researcher reports a vulnerability privately, you are notified and can choose to either accept it, ask more questions, or reject it. If you accept the report, you're ready to collaborate on a fix for the vulnerability in private with the security researcher.
|
||||
|
||||
## Managing security vulnerabilities that are privately reported
|
||||
|
||||
{% data variables.product.prodname_dotcom %} notifies repository maintainers when security researchers privately report vulnerabilities in their repository, and sends notifications if maintainers watch the repository or if they have notifications enabled for the repository. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-advisories %}
|
||||
1. Click the advisory you want to review. An advisory that is privately reported will have a status of `Needs triage`.
|
||||
|
||||
|
||||
|
||||
2. Carefully review the report. You can:
|
||||
- Collaborate with the security researcher on a patch in private, by clicking **Start a temporary private fork**. This gives you a place for further discussions with the contributor without changing the status of the proposed advisory from `Needs triage`.
|
||||
- Accept the vulnerability report as a draft advisory on {% data variables.product.prodname_dotcom %}, by clicking **Accept and open as draft**. If you choose this option:
|
||||
- This doesn't make the report public.
|
||||
- The report becomes a draft repository security advisory and you can work on it in the same way as any draft advisory that you create.
|
||||
For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
|
||||
- Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
|
||||
|
||||
|
||||
@@ -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: Informationen zur Lieferkettensicherheit
|
||||
intro: 'Mit {% data variables.product.product_name %} kannst du deine Lieferkette absichern, indem du Informationen über die Abhängigkeiten in deiner Umgebung bis zu den Sicherheitsrisiken dieser Abhängigkeiten erhältst{% ifversion fpt or ghec or ghes %} und diese patchen kannst{% 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: de-DE
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181236'
|
||||
---
|
||||
## Informationen zur Lieferkettensicherheit auf GitHub
|
||||
|
||||
## About supply chain security at GitHub
|
||||
Aufgrund der zunehmenden Verwendung von Open-Source-Lösungen hängen die meisten Projekte von Hunderten von Open-Source-Abhängigkeiten ab. Dies stellt ein Sicherheitsproblem dar: Was ist, wenn die von Ihnen verwendeten Abhängigkeiten Sicherheitsrisiken aufweisen? Du könntest deine Benutzer*innen dem Risiko eines Lieferkettenangriffs aussetzen. Eine der wichtigsten Maßnahmen zum Schutz deiner Lieferkette besteht darin, deine anfälligen Abhängigkeiten zu patchen{% ifversion GH-advisory-db-supports-malware %} und jegliche Schadsoftware zu ersetzen{% 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 %}.
|
||||
Du fügst Abhängigkeiten direkt deiner Lieferkette hinzu, wenn du sie in einer Manifest- oder Sperrdatei angibst. Abhängigkeiten können aber auch transitiv eingeschlossen werden. Dies bedeutet, dass, auch wenn du eine bestimmte Abhängigkeit nicht angibst, eine deiner Abhängigkeiten diese jedoch verwendet, du ebenfalls von dieser Abhängigkeit abhängig bist.
|
||||
|
||||
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 %} bietet eine Reihe von Features, die dir dabei helfen, die Abhängigkeiten in deiner Umgebung{% ifversion ghae %} und die Sicherheitsrisiken dieser Abhängigkeiten zu verstehen{% endif %}{% ifversion fpt or ghec or ghes %}und die Sicherheitsrisiken dieser Abhängigkeiten zu verstehen und diese zu patchen{% 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 %}**
|
||||
Die Lieferkettenfeatures auf {% data variables.product.product_name %} sind:
|
||||
- **Abhängigkeitsdiagramm**
|
||||
- **Abhängigkeitsüberprüfung**
|
||||
- **{% 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 %}
|
||||
|
||||
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.
|
||||
Das Abhängigkeitsdiagramm ist von zentraler Bedeutung für die Lieferkettensicherheit. Es zeigt alle Upstreamabhängigkeiten eines Repositorys oder Pakets sowie alle öffentlichen Downstreamelemente, die von diesem Repository bzw. Paket abhängig sind. Im Abhängigkeitsdiagramm für das Repository kannst du die Abhängigkeiten deines Repositorys sowie einige der Eigenschaften dieser Abhängigkeiten sehen, z. B. Informationen zu Sicherheitsrisiken.
|
||||
|
||||
Other supply chain features on {% data variables.product.prodname_dotcom %} rely on the information provided by the dependency graph.
|
||||
Andere Lieferkettenfeatures auf {% data variables.product.prodname_dotcom %} nutzen die Informationen aus dem Abhängigkeitsdiagramm.
|
||||
|
||||
- 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.
|
||||
- Die Abhängigkeitsüberprüfung verwendet das Abhängigkeitsdiagramm, um Änderungen bei Abhängigkeiten zu erkennen und Ihnen dabei zu helfen, beim Überprüfen von Pull Requests die Auswirkungen dieser Änderungen auf die Sicherheit zu verstehen.
|
||||
- {% data variables.product.prodname_dependabot %} gleicht die vom Abhängigkeitsdiagramm bereitgestellten Abhängigkeitsdaten mit der in {% data variables.product.prodname_advisory_database %} veröffentlichten Empfehlungsliste ab, überprüft deine Abhängigkeiten und generiert {% data variables.product.prodname_dependabot_alerts %}, wenn ein potenzielles Sicherheitsrisiko {% ifversion GH-advisory-db-supports-malware %}oder Schadsoftware{% endif %} erkannt wurde.
|
||||
{% ifversion fpt or ghec or ghes %} – {% data variables.product.prodname_dependabot_security_updates %} verwenden das Abhängigkeitsdiagramm und {% data variables.product.prodname_dependabot_alerts %}, um dich beim Aktualisieren von Abhängigkeiten mit bekannten Sicherheitsrisiken in deinem Repository zu unterstützen.
|
||||
|
||||
{% 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 %} verwenden nicht das Abhängigkeitsdiagramm, sondern die semantische Versionierung von Abhängigkeiten. {% data variables.product.prodname_dependabot_version_updates %} hilft dir dabei, deine Abhängigkeiten auf dem jeweils aktuellen Stand zu halten, auch wenn keine Sicherheitsrisiken vorliegen.
|
||||
{% 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 %} Leitlinien mit bewährten Methoden zur Sicherheit der gesamten Lieferkette, einschließlich des Schutzes von persönlichen Konten, Code und Prozessen, findest du unter [Sichern einer End-to-End-Lieferkette](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview).
|
||||
{% endif %}
|
||||
|
||||
## Feature overview
|
||||
## Funktionsübersicht
|
||||
|
||||
### What is the dependency graph
|
||||
### Was ist das Abhängigkeitsdiagramm?
|
||||
|
||||
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.
|
||||
Zum Generieren des Abhängigkeitsdiagramms überprüft {% data variables.product.company_short %} die expliziten, im Manifest und in Sperrdateien deklarierten Abhängigkeiten eines Repositorys. Wenn das Abhängigkeitsdiagramm aktiviert ist, parst es automatisch alle bekannten Paketmanifestdateien im Repository und verwendet diese, um ein Diagramm mit den Namen und Versionen bekannter Abhängigkeiten zu erstellen.
|
||||
|
||||
- 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.
|
||||
- Das Abhängigkeitsdiagramm enthält Informationen zu deinen _direkten_ und _transitiven_ Abhängigkeiten.
|
||||
- Das Abhängigkeitsdiagramm wird automatisch aktualisiert, wenn du einen Commit an {% data variables.product.company_short %} pushst, der eine unterstützte Manifest- oder Sperrdatei für den Standardbranch ändert oder hinzufügt, und wenn jemand eine Änderung an das Repository einer deiner Abhängigkeiten pusht.
|
||||
- Du kannst das Abhängigkeitsdiagramm anzeigen, indem du die Hauptseite des Repositorys auf {% data variables.product.product_name %} öffnest und zur Registerkarte **Erkenntnisse** navigierst.
|
||||
|
||||
{% 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)."
|
||||
Weitere Informationen zum Abhängigkeitsdiagramm findest du unter [Informationen zum Abhängigkeitsdiagramm](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).
|
||||
|
||||
### What is dependency review
|
||||
### Was ist die Abhängigkeitsüberprüfung?
|
||||
|
||||
Dependency review helps reviewers and contributors understand dependency changes and their security impact in every pull request.
|
||||
Die Abhängigkeitsüberprüfung hilft Reviewer*innen und Mitwirkenden dabei, Änderungen bei Abhängigkeiten und deren Auswirkungen auf die Sicherheit in allen Pull Requests zu verstehen.
|
||||
|
||||
- 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.
|
||||
- Die Abhängigkeitsüberprüfung teilt Ihnen mit, welche Abhängigkeiten in einem Pull Request hinzugefügt, entfernt oder aktualisiert wurden. Du kannst das Veröffentlichungsdatum, die Beliebtheit von Abhängigkeiten und Informationen zu Sicherheitsrisiken verwenden, um zu entscheiden, ob du die Änderung annehmen möchtest.
|
||||
- Du kannst die Abhängigkeitsüberprüfung für einen Pull Request einsehen, indem du auf der Registerkarte **Geänderte Dateien** das Rich-Diff anzeigst.
|
||||
|
||||
For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
Weitere Informationen zur Abhängigkeitsüberprüfung findest du unter [Informationen zur Abhängigkeitsüberprüfung](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
|
||||
|
||||
### What is Dependabot
|
||||
### Was ist 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 %} hält deine Abhängigkeiten auf dem jeweils aktuellen Stand, indem du über Sicherheitsrisiken bei deinen Abhängigkeiten informiert wirst{% ifversion fpt or ghec or ghes %} und automatisch Pull Requests zum Upgraden deiner Abhängigkeiten auf die nächste verfügbare sichere Version geöffnet werden, wenn eine {% data variables.product.prodname_dependabot %}-Warnung ausgelöst wird, oder zum Upgraden auf die aktuelle Version, wenn ein Release veröffentlicht wird{% else %}, damit du die betreffende Abhängigkeit aktualisieren kannst{% 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 %} Der Begriff „{% data variables.product.prodname_dependabot %}“ beschreibt die folgenden Features:
|
||||
- {% data variables.product.prodname_dependabot_alerts %}: Hierbei handelt es sich um eine Benachrichtigung, die auf der Registerkarte **Sicherheit** für das Repository sowie im Abhängigkeitsdiagramm des Repositorys angezeigt wird. Die Warnung enthält einen Link zur betroffenen Datei im Projekt sowie Informationen zu einer Version, bei der das Problem behoben wurde.
|
||||
- {% 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 %}: Hierbei handelt es sich um Updates, die ausgelöst werden, damit deine Abhängigkeiten auf eine sichere Version upgegradet werden, sobald eine Warnung ausgelöst wird.
|
||||
- {% data variables.product.prodname_dependabot_version_updates %}: Hierbei handelt es sich um geplante Updates, mit denen deine Abhängigkeiten auf dem neuesten Stand (aktuelle Version) gehalten werden.
|
||||
|
||||
{% 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 %} und {% data variables.product.prodname_dependabot_version_updates %} nutzen {% data variables.product.prodname_actions %} nicht, wenn sie auf {% data variables.product.product_name %} ausgeführt werden. Allerdings können Pull Requests, die von {% data variables.product.prodname_dependabot %} geöffnet werden, Workflows zum Ausführen von Aktionen auslösen. Weitere Informationen findest du unter [Automatisieren von {% data variables.product.prodname_dependabot %} mit {% 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)."
|
||||
{% data variables.product.prodname_dependabot_security_updates %} und {% data variables.product.prodname_dependabot_version_updates %} benötigen {% data variables.product.prodname_actions %}, um auf {% data variables.product.product_name %} ausgeführt zu werden. Für {% data variables.product.prodname_dependabot_alerts %} wird {% data variables.product.prodname_actions %} nicht benötigt. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/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 %} wird nicht benötigt, um {% data variables.product.prodname_dependabot_alerts %} auf {% data variables.product.product_name %} auszuführen.
|
||||
|
||||
{% 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 %} Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates).
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### What are Dependabot alerts
|
||||
#### Was sind Dependabot-Warnungen?
|
||||
|
||||
{% 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 %} heben Repositorys hervor, die von einem neu entdeckten Sicherheitsrisiko betroffen sind, basierend auf dem Abhängigkeitsdiagramm sowie {% data variables.product.prodname_advisory_database %} hervor. Diese Datenbank enthält Empfehlungen für bekannte Sicherheitsrisiken{% ifversion GH-advisory-db-supports-malware %} und Schadsoftware{% 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 %} führt eine Überprüfung zur Erkennung von unsicheren Abhängigkeiten durch und sendet {% data variables.product.prodname_dependabot_alerts %}, wenn: {% ifversion fpt or ghec %}
|
||||
- Ein neues Sicherheitsrisiko wird {% data variables.product.prodname_advisory_database %} hinzugefügt.{% else %}
|
||||
- Neue Empfehlungsdaten werden stündlich zwischen {% data variables.product.prodname_dotcom_the_website %} und {% data variables.location.product_location %} synchronisiert. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- Das Abhängigkeitsdiagramm für das Repository sich ändert
|
||||
- {% data variables.product.prodname_dependabot_alerts %} werden {% ifversion fpt or ghec or ghes %} auf der Registerkarte **Sicherheit** des Repositorys sowie{% endif %} im Abhängigkeitsdiagramm des Repositorys angezeigt. Die Warnung enthält {% ifversion fpt or ghec or ghes %} einen Link zur betroffenen Datei im Projekt sowie {% endif %}Informationen zu einer Version, bei der das Problem behoben wurde.
|
||||
|
||||
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)."
|
||||
Weitere Informationen findest du unter [Informationen zu {% 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
|
||||
#### Was sind Dependabot-Updates?
|
||||
|
||||
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.
|
||||
Es gibt zwei Arten von {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %}-_Sicherheitsupdates_ und -_Versionsupdates_. {% data variables.product.prodname_dependabot %} generiert zwar in beiden Fällen automatische Pull Requests zum Aktualisieren deiner Abhängigkeiten, es gibt jedoch einige Unterschiede.
|
||||
|
||||
{% 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
|
||||
- Werden durch eine {% data variables.product.prodname_dependabot %}-Warnung ausgelöst
|
||||
- Aktualisieren Abhängigkeiten auf die niedrigste Version, in der ein bekanntes Sicherheitsrisiko beseitigt wurde
|
||||
- Werden für die Ökosysteme unterstützt, die das Abhängigkeitsdiagramm unterstützt
|
||||
- Erfordert keine Konfigurationsdatei. Du kannst jedoch eine verwenden, um das Standardverhalten außer Kraft zu setzen.
|
||||
|
||||
{% 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
|
||||
- Erfordert eine Konfigurationsdatei
|
||||
- Werden basierend auf einem von Ihnen konfigurierten Zeitplan ausgeführt
|
||||
- Aktualisieren Abhängigkeiten auf die aktuellste Version für die Konfiguration
|
||||
- Werden für eine andere Gruppe von Ökosystemen unterstützt
|
||||
|
||||
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)."
|
||||
Weitere Informationen zu {% data variables.product.prodname_dependabot_updates %} findest du unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates) und [Informationen zu {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates).
|
||||
{% endif %}
|
||||
|
||||
## Feature availability
|
||||
## Verfügbarkeit von Funktionen
|
||||
|
||||
{% 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)."
|
||||
Öffentliche Repositorys:
|
||||
- **Abhängigkeitsdiagramm**: standardmäßig aktiviert und kann nicht deaktiviert werden
|
||||
- **Abhängigkeitsüberprüfung**: standardmäßig aktiviert und kann nicht deaktiviert werden
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}**: nicht standardmäßig aktiviert. {% data variables.product.prodname_dotcom %} erkennt unsichere Abhängigkeiten und zeigt Informationen im Abhängigkeitsdiagramm an, generiert aber nicht standardmäßig {% data variables.product.prodname_dependabot_alerts %}. Repositorybesitzer*innen oder Personen mit Administratorzugriff können {% data variables.product.prodname_dependabot_alerts %} aktivieren.
|
||||
Zudem kannst du Dependabot-Warnungen für alle Repositorys aktivieren oder deaktivieren, die deinem Benutzerkonto oder deiner Organisation gehören. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Benutzerkonto](/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) oder [Verwalten von Sicherheits- und Analyseeinstellungen für deine 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)."
|
||||
Private Repositorys:
|
||||
- **Abhängigkeitsdiagramm**: standardmäßig nicht aktiviert. Das Feature kann von Repositoryadministrator*innen aktiviert werden. Weitere Informationen findest du unter [Untersuchen der Abhängigkeiten eines Repositorys](/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).
|
||||
- **Abhängigkeitsüberprüfung**: verfügbar in privaten Repositorys, die Organisationen gehören, die {% data variables.product.prodname_ghe_cloud %} verwenden und über eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} verfügen. Weitere Informationen findest du unter [Dokumentation zu {% 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)."
|
||||
- **Abhängigkeitsüberprüfung**: verfügbar in privaten Repositorys, die Organisationen gehören, vorausgesetzt, du verfügst über eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} und das Abhängigkeitsdiagramm ist aktiviert. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) und [Untersuchen der Abhängigkeiten eines Repositorys](/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 %}**: nicht standardmäßig aktiviert. Besitzer*innen privater Repositorys oder Personen mit Administratorzugriff können {% data variables.product.prodname_dependabot_alerts %} aktivieren, indem sie das Abhängigkeitsdiagramm und {% data variables.product.prodname_dependabot_alerts %} für ihre Repositorys aktivieren.
|
||||
Zudem kannst du Dependabot-Warnungen für alle Repositorys aktivieren oder deaktivieren, die deinem Benutzerkonto oder deiner Organisation gehören. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Benutzerkonto](/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) oder [Verwalten von Sicherheits- und Analyseeinstellungen für deine 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)."
|
||||
Alle Repositorytypen:
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}**: nicht standardmäßig aktiviert. Du kannst {% data variables.product.prodname_dependabot_security_updates %} für jedes Repository aktivieren, das {% data variables.product.prodname_dependabot_alerts %} und das Abhängigkeitsdiagramm verwendet. Weitere Informationen zum Aktivieren von Sicherheitsupdates findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates).
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**: nicht standardmäßig aktiviert. Personen mit Schreibberechtigungen für ein Repository können {% data variables.product.prodname_dependabot_version_updates %} aktivieren. Weitere Informationen zum Aktivieren von Versionsupdates findest du unter [Konfigurieren von {% 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)."
|
||||
- **Abhängigkeitsdiagramm** und **{% data variables.product.prodname_dependabot_alerts %}**: nicht standardmäßig aktiviert. Beide Features werden auf Unternehmensebene vom Unternehmensinhaber bzw. von der Unternehmensinhaberin konfiguriert. Weitere Informationen findest du unter {% ifversion ghes %}[Aktivieren des Abhängigkeitsdiagramms für dein Unternehmen](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise) und {% endif %}[Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
|
||||
- **Abhängigkeitsüberprüfung**: Verfügbar, wenn das Abhängigkeitsdiagramm für {% data variables.location.product_location %} und {% data variables.product.prodname_advanced_security %} für die Organisation oder das Repository aktiviert sind. Weitere Informationen findest du unter [Informationen zu {% 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 %}**: nicht standardmäßig aktiviert. Du kannst {% data variables.product.prodname_dependabot_security_updates %} für jedes Repository aktivieren, das {% data variables.product.prodname_dependabot_alerts %} und das Abhängigkeitsdiagramm verwendet. Weitere Informationen zum Aktivieren von Sicherheitsupdates findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates).
|
||||
- **{% data variables.product.prodname_dependabot_version_updates %}**: nicht standardmäßig aktiviert. Personen mit Schreibberechtigungen für ein Repository können {% data variables.product.prodname_dependabot_version_updates %} aktivieren. Weitere Informationen zum Aktivieren von Versionsupdates findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates).
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configuring dependency review
|
||||
intro: You can use dependency review to catch vulnerabilities before they are added to your project.
|
||||
title: Konfigurieren der Abhängigkeitsüberprüfung
|
||||
intro: 'Du kannst die Abhängigkeitsüberprüfung verwenden, um Sicherheitsrisiken abzufangen, bevor sie deinem Projekt hinzugefügt werden.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Configure dependency review
|
||||
versions:
|
||||
@@ -15,80 +15,71 @@ topics:
|
||||
- Vulnerabilities
|
||||
- Dependencies
|
||||
- Pull requests
|
||||
ms.openlocfilehash: b5e5ccb5107cd96d1a88f896fd46d5b948a365cd
|
||||
ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: '148163352'
|
||||
---
|
||||
|
||||
## About dependency review
|
||||
## Informationen zur Abhängigkeitsüberprüfung
|
||||
|
||||
{% data reusables.dependency-review.feature-overview %}
|
||||
|
||||
For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" and "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
|
||||
Weitere Informationen findest du unter [Informationen zur Abhängigkeitsprüfung](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review) oder [Überprüfen von Abhängigkeitsänderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request).
|
||||
|
||||
## About configuring dependency review
|
||||
## Informationen zur Abhängigkeitsüberprüfung
|
||||
|
||||
{% ifversion fpt %}
|
||||
Dependency review is available in all public repositories in all products and cannot be disabled. Dependency review is available in private repositories owned by organizations that use GitHub Enterprise Cloud and have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security). For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review).
|
||||
{% ifversion fpt %} Die Abhängigkeitsüberprüfung ist in allen öffentlichen Repositorys in allen Produkten verfügbar und kann nicht deaktiviert werden. Die Abhängigkeitsüberprüfung ist in privaten Repositorys verfügbar, die Organisationen gehören, die GitHub Enterprise Cloud verwenden und über eine Lizenz für [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) verfügen. Weitere Informationen findest du unter [Dokumentation zu {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review).
|
||||
|
||||
{% elsif ghec %}
|
||||
Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) and have the dependency graph enabled.
|
||||
{% elsif ghec %} Abhängigkeitsüberprüfungen sind in {% data variables.product.product_name %} für öffentliche Repositorys enthalten. Damit Abhängigkeitsüberprüfungen in privaten Repositorys verwendet werden können, die Organisationen gehören, wird eine Lizenz für [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) benötigt, und das Abhängigkeitsdiagramm muss aktiviert sein.
|
||||
|
||||
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
|
||||
1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature.
|
||||
|
||||
1. Wenn {% data variables.product.prodname_GH_advanced_security %} nicht aktiviert ist, klicke neben dem Feature auf **Aktivieren**.
|
||||
|
||||
|
||||
{% elsif ghes or ghae %}
|
||||
|
||||
Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %}
|
||||
Die Abhängigkeitsüberprüfung ist verfügbar, wenn das Abhängigkeitsdiagramm für {% data variables.location.product_location %} aktiviert ist und {% data variables.product.prodname_advanced_security %} für das Unternehmen oder Repository aktiviert ist.{% ifversion ghes %} Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_GH_advanced_security %} für dein Unternehmen](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise).{% endif %}
|
||||
|
||||
### Checking if the dependency graph is enabled
|
||||
### Überprüfen des Status des Abhängigkeitsdiagramms
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Configure security and analysis features", check if the dependency graph is enabled.
|
||||
1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %}
|
||||
{% endif %}
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Überprüfe unter „Sicherheits- und Analysefeatures konfigurieren“, ob das Abhängigkeitsdiagramm aktiviert ist.
|
||||
1. Wenn das Abhängigkeitsdiagramm aktiviert ist, kannst du neben {% data variables.product.prodname_GH_advanced_security %} auf **Aktivieren** klicken, um {% data variables.product.prodname_advanced_security %} einschließlich des Abhängigkeitsdiagramms zu aktivieren. Die Schaltfläche „Aktivieren“ ist deaktiviert, wenn dein Unternehmen keine Lizenz für {% data variables.product.prodname_advanced_security %} besitzt.{% ifversion ghes %} {% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion dependency-review-action-configuration %}
|
||||
## About configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
## Informationen zum Konfigurieren der {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-action-overview %}
|
||||
|
||||
The following configuration options are available.
|
||||
Die folgenden Konfigurationsoptionen stehen zur Verfügung.
|
||||
|
||||
| Option | Required | Usage |
|
||||
| Option | Erforderlich | Verbrauch |
|
||||
|------------------|-------------------------------|--------|
|
||||
| `fail-on-severity` | Optional | Defines the threshold for level of severity (`low`, `moderate`, `high`, `critical`).</br>The action will fail on any pull requests that introduce vulnerabilities of the specified severity level or higher. |
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
| `fail-on-scopes` | Optional | Contains a list of strings representing the build environments you want to support (`development`, `runtime`, `unknown`). </br>The action will fail on pull requests that introduce vulnerabilites in the scopes that match the list.|{% endif %}
|
||||
| `allow-ghsas` | Optional | Contains a list of {% data variables.product.prodname_advisory_database %} IDs that can be skipped during detection. You can find the possible values for this parameter in the [{% data variables.product.prodname_advisory_database %}](https://github.com/advisories). |
|
||||
| `config-file` | Optional | Specifies a path to a configuration file. The configuration file can be local to the repository or a file located in an external repository.|
|
||||
| `external-repo-token` | Optional | Specifies a token for fetching the configuration file, if the file resides in a private external repository. The token must have read access to the repository.|
|
||||
| `fail-on-severity` | Optional | Definiert den Schwellenwert für den Schweregrad (`low`, `moderate`, `high`, `critical`).</br>Die Aktion schlägt bei allen Pull Requests fehl, die Sicherheitsrisiken des angegebenen oder eines höheren Schweregrads einführen. |
|
||||
{%- ifversion dependency-review-action-licenses %} | `allow-licenses` | Optional | Enthält eine Liste der zulässigen Lizenzen. Du findest die möglichen Werte für diesen Parameter auf der Seite [Lizenzen](/rest/licenses) der API-Dokumentation.</br>Die Aktion schlägt bei Pull Requests fehl, die Abhängigkeiten mit Lizenzen einführen, die nicht der Liste entsprechen.|{% endif %} {%- ifversion dependency-review-action-licenses %} | `deny-licenses` | Optional | Enthält eine Liste der verbotenen Lizenzen. Du findest die möglichen Werte für diesen Parameter auf der Seite [Lizenzen](/rest/licenses) der API-Dokumentation.</br>Die Aktion schlägt bei Pull Requests fehl, die Abhängigkeiten von Lizenzen einführen, die der Liste entsprechen.|{% endif %}{% ifversion dependency-review-action-fail-on-scopes %} | `fail-on-scopes` | Optional | Enthält eine Liste von Zeichenfolgen für die Buildumgebungen, die du unterstützen möchtest (`development`, `runtime`, `unknown`). </br>Die Aktion schlägt bei Pull Requests fehl, die Sicherheitsrisiken in Bereichen einführen, die der Liste entsprechen.|{% endif %} | `allow-ghsas` | Optional | Enthält eine Liste von {% data variables.product.prodname_advisory_database %}-IDs, die bei der Erkennung übersprungen werden können. Die möglichen Werte für diesen Parameter findest du in der [{% data variables.product.prodname_advisory_database %}](https://github.com/advisories). | | `config-file` | Optional | Gibt einen Pfad zu einer Konfigurationsdatei an. Die Konfigurationsdatei kann lokal im Repository oder eine Datei in einem externen Repository vorliegen.| | `external-repo-token` | Optional | Gibt ein Token zum Abrufen der Konfigurationsdatei an, wenn sich die Datei in einem privaten externen Repository befindet. Das Token benötigt Lesezugriff auf das Repository.|
|
||||
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
{% tip %}
|
||||
{% ifversion dependency-review-action-licenses %} {% tip %}
|
||||
|
||||
**Tip:** The `allow-licenses` and `deny-licenses` options are mutually exclusive.
|
||||
**Tipp:** Die Optionen `allow-licenses` und `deny-licenses` schließen sich gegenseitig aus.
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
{% endtip %} {% endif %}
|
||||
|
||||
## Configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
## Konfigurieren der {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
There are two methods of configuring the {% data variables.product.prodname_dependency_review_action %}:
|
||||
- Inlining the configuration options in your workflow file.
|
||||
- Referencing a configuration file in your workflow file.
|
||||
Es gibt zwei Methoden zum Konfigurieren der {% data variables.product.prodname_dependency_review_action %}:
|
||||
- Inlinekonfiguration der Konfigurationsoptionen in deiner Workflowdatei
|
||||
- Verweis auf eine Konfigurationsdatei in deiner Workflowdatei
|
||||
|
||||
Notice that all of the examples use a short version number for the action (`v3`) instead of a semver release number (for example, `v3.0.8`). This ensures that you use the most recent minor version of the action.
|
||||
### Using inline configuration to set up the {% data variables.product.prodname_dependency_review_action %}
|
||||
Beachte, dass in allen Beispielen anstelle der SemVer-Versionsnummer (z. B. `v3.0.8`) eine kurze Versionsnummer für die Aktion verwendet wird (`v3`). Dadurch wird sichergestellt, dass du die neueste Nebenversion der Aktion verwendest.
|
||||
### Einrichten der {% data variables.product.prodname_dependency_review_action %} mithilfe der Inlinekonfiguration
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder.
|
||||
1. Füge deinem Ordner `.github/workflows` einen neuen YAML-Workflow hinzu.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
{% ifversion ghes %}Für `runs-on` lautet die Standardbezeichnung `self-hosted`. Du kannst die Standardbezeichnung durch die Bezeichnung für einen beliebigen deiner Runner ersetzen.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
@@ -106,9 +97,9 @@ Notice that all of the examples use a short version number for the action (`v3`)
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
```
|
||||
1. Specify your settings.
|
||||
1. Lege die Einstellungen fest.
|
||||
|
||||
This {% data variables.product.prodname_dependency_review_action %} example file illustrates how you can use the available configuration options.
|
||||
Diese Beispieldatei für die {% data variables.product.prodname_dependency_review_action %} veranschaulicht, wie du die verfügbaren Konfigurationsoptionen verwenden kannst.
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
@@ -146,11 +137,11 @@ Notice that all of the examples use a short version number for the action (`v3`)
|
||||
fail-on-scopes: development, runtime
|
||||
{% endif %}
|
||||
```
|
||||
### Using a configuration file to set up {% data variables.product.prodname_dependency_review_action %}
|
||||
### Einrichten der {% data variables.product.prodname_dependency_review_action %} mithilfe einer Konfigurationsdatei
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder and use `config-file` to specify that you are using a configuration file.
|
||||
1. Füge deinem Ordner `.github/workflows` einen neuen YAML-Workflow hinzu, und gib mithilfe von `config-file` an, dass du eine Konfigurationsdatei verwendest.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
{% ifversion ghes %}Für `runs-on` lautet die Standardbezeichnung `self-hosted`. Du kannst die Standardbezeichnung durch die Bezeichnung für einen beliebigen deiner Runner ersetzen.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
@@ -178,9 +169,9 @@ Notice that all of the examples use a short version number for the action (`v3`)
|
||||
# Possible values: Any GitHub token with read access to the private external repository.
|
||||
external-repo-token: 'ghp_123456789abcde'
|
||||
```
|
||||
1. Create the configuration file in the path you have specified.
|
||||
1. Erstelle die Konfigurationsdatei in dem von dir angegebenen Pfad.
|
||||
|
||||
This YAML example file illustrates how you can use the available configuration options.
|
||||
Diese YAML-Beispieldatei veranschaulicht, wie du die verfügbaren Konfigurationsoptionen verwenden kannst.
|
||||
```yaml{:copy}
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
@@ -211,5 +202,5 @@ Notice that all of the examples use a short version number for the action (`v3`)
|
||||
- runtime
|
||||
{% endif %}
|
||||
```
|
||||
For further details about the configuration options, see [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
|
||||
Weitere Details zu den Konfigurationsoptionen findest du unter [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
|
||||
{% endif %}
|
||||
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
title: Durchführen einer vollständigen Neuerstellung eines Containers
|
||||
intro: 'Wenn du wenig Speicherplatz auf dem Datenträger hast oder sicherstellen möchtest, dass deine Entwicklungscontainerkonfiguration in neuen Codespaces funktioniert, kannst du eine vollständige Neuerstellung eines Containers durchführen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Full rebuilds
|
||||
ms.openlocfilehash: f844d5f92073adf01c3b1a1100e6fe1912b2d7ad
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180840'
|
||||
---
|
||||
## Informationen zum Neuerstellen eines Containers
|
||||
|
||||
Wenn du in einem Codespace arbeitest, ist deine Entwicklungsumgebung ein Docker-Container, der auf einem virtuellen Computer ausgeführt wird. Wenn du Änderungen an der Konfiguration deines Entwicklungscontainers von einem Codespace aus vornimmst, und diese Änderungen auf den aktuellen Codespace anwenden möchtest, musst du den Container neu erstellen.
|
||||
|
||||
Wenn du einen Container neu erstellst, beschleunigt {% data variables.product.prodname_github_codespaces %} standardmäßig den Buildprozess, indem zwischengespeicherte Images aus früheren Builds des Containers wiederverwendet werden. Dies ist in der Regel die schnellste Möglichkeit, Änderungen an deiner Entwicklungscontainerkonfiguration zu implementieren, und zwar aus folgenden Gründen.
|
||||
- {% data variables.product.prodname_github_codespaces %} kann Images in deinem Cache wiederverwenden, anstatt sie erneut aus Containerregistrierungen zu pullen.
|
||||
- Die Teile deiner Entwicklungscontainerkonfiguration, die definieren, wie der Container erstellt wird, z. B. Entwicklercontainerfeatures und Dockerfile-Anweisungen, wurden möglicherweise bereits in Imageebenen in deinem Cache implementiert, sodass du nicht warten musst, bis diese Prozesse erneut ausgeführt werden. (Befehle in deiner Konfiguration, die nach dem Erstellen des Containers ausgeführt werden, z. B. `onCreateCommand`, werden jedoch erneut ausgeführt.)
|
||||
|
||||
Gelegentlich kannst du eine vollständige Neuerstellung deines Containers durchführen. Bei einer vollständigen Neuerstellung bereinigt {% data variables.product.prodname_github_codespaces %} alle Docker-Container, Images und Volumes aus dem Cache und erstellt deinen Container dann mit neu gepullten Images neu. Das gesamte in deiner Konfiguration definierte Setup wird erneut ausgeführt, wodurch neue Imageebenen generiert werden. In Situationen wie der folgenden kannst du nach vielen Iterationen der Neuerstellung deines Containers mit zwischengespeicherten Images eine vollständige Neuerstellung durchführen.
|
||||
|
||||
- Du solltest sicherstellen, dass das in deiner Konfiguration definierte Setup nicht von zwischengespeicherten Images abhängig ist, und wie erforderlich ausgeführt wird, wenn basierend auf der Konfiguration ein neuer Codespace erstellt wird. Beispielsweise kann eine Abhängigkeit aus dem Basisimage entfernt worden sein, seit es zuletzt in deinen Codespace gepullt wurde.
|
||||
- Du solltest den von deinem Cache verwendeten Speicherplatz auf dem Datenträger freigeben, wenn bspw. der Speicherplatz auf dem Datenträger knapp ist, oder du die Speichergebühren minimieren möchtest. Dein Imagecache benötigt möglicherweise erheblichen Speicherplatz auf dem Datenträger, wenn du dein Basisimage mehrmals geändert hast, eine große Anzahl iterativer Änderungen an deiner Konfiguration vorgenommen hast oder du mehrere Container mit Docker Compose ausführst.
|
||||
|
||||
## Ausführen einer vollständigen Neuerstellung
|
||||
|
||||
Du kannst eine vollständige Neuerstellung in {% data variables.product.prodname_vscode %} durchführen.
|
||||
|
||||
{% data reusables.codespaces.command-pallette %}
|
||||
1. Beginne mit der Eingabe von „Neu erstellen“, und wähle **Codespaces: Container vollständig neu erstellen** aus.
|
||||
|
||||
|
||||
|
||||
## Eine vollständige Neuerstellung übergreifendes Beibehalten von Daten
|
||||
|
||||
Alle Dateien und Ordner im Verzeichnis `/workspaces` deines Codespaces werden bei einer Neuerstellung immer beibehalten. Du musst weder Einstellungen ändern noch eine Konfiguration hinzufügen, um den Inhalt dieses Verzeichnisses eine vollständige Neuerstellung übergreifend beizubehalten.
|
||||
|
||||
Wenn Daten außerhalb des Verzeichnisses `/workspaces` eine vollständige Neuerstellung übergreifend beibehalten werden sollen, kannst du eine symbolische Verknüpfung (Symlink) mit dem persistenten Verzeichnis am gewünschten Speicherort innerhalb des Containers erstellen. Du kannst z. B. in deinem `/workspaces/.devcontainer`-Verzeichnis ein `config`-Verzeichnis erstellen, das bei einer Neuerstellung beibehalten wird. Anschließend erstellst du eine symbolische Verknüpfung für das `config`-Verzeichnis und seinen Inhalt als `postCreateCommand` in deiner `devcontainer.json`-Datei.
|
||||
|
||||
```json
|
||||
{
|
||||
"image": "mcr.microsoft.com/vscode/devcontainers/base:alpine",
|
||||
"postCreateCommand": ".devcontainer/postCreate.sh"
|
||||
}
|
||||
```
|
||||
|
||||
In der nachstehenden Beispieldatei `postCreate.sh` werden die Inhalte des `config`-Verzeichnisses symbolisch mit dem Basisverzeichnis verknüpft.
|
||||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
ln -sf $PWD/.devcontainer/config $HOME/config && set +x
|
||||
```
|
||||
|
||||
## Weiterführende Themen
|
||||
- [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using the Visual Studio Code Command Palette in GitHub Codespaces
|
||||
intro: 'You can use the Command Palette feature of {% data variables.product.prodname_vscode %} to access many commands in {% data variables.product.prodname_github_codespaces %}.'
|
||||
title: Verwenden der Visual Studio Code-Befehlspalette in GitHub Codespaces
|
||||
intro: 'Du kannst über das Feature „Befehlspalette“ von {% data variables.product.prodname_vscode %} auf viele Befehle in {% data variables.product.prodname_github_codespaces %} zugreifen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -12,62 +12,67 @@ shortTitle: VS Code Command Palette
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-reference/using-the-command-palette-in-codespaces
|
||||
ms.openlocfilehash: acd462dd1c0b60dced529d7471b9c8638e2f6e91
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180811'
|
||||
---
|
||||
## Informationen zur {% data variables.product.prodname_vscode_command_palette %}
|
||||
|
||||
## About the {% data variables.product.prodname_vscode_command_palette %}
|
||||
Die {% data variables.product.prodname_vscode_command_palette_shortname %} ist eines der zentralen Features von {% data variables.product.prodname_vscode %} und steht dir zur Verwendung in {% data variables.product.prodname_github_codespaces %} zur Verfügung. Die Befehlspalette ermöglicht dir den Zugriff auf viele Befehle für {% data variables.product.prodname_github_codespaces %} und {% data variables.product.prodname_vscode_shortname %}. Weitere Informationen zur Verwendung von {% data variables.product.prodname_vscode_command_palette_shortname %} findest du unter [Benutzeroberfläche](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette) in der {% data variables.product.prodname_vscode_shortname %}-Dokumentation.
|
||||
|
||||
The {% data variables.product.prodname_vscode_command_palette_shortname %} is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in {% data variables.product.prodname_github_codespaces %}. The Command Palette allows you to access many commands for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
## Zugreifen auf die {% data variables.product.prodname_vscode_command_palette_shortname %}
|
||||
|
||||
## Accessing the {% data variables.product.prodname_vscode_command_palette_shortname %}
|
||||
Du kannst auf die {% data variables.product.prodname_vscode_command_palette_shortname %} auf verschiedene Weisen zugreifen.
|
||||
|
||||
You can access the {% data variables.product.prodname_vscode_command_palette_shortname %} in a number of ways.
|
||||
- <kbd>Umschalt</kbd>+<kbd>Befehl</kbd>+<kbd>P</kbd> (Mac) / <kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux).
|
||||
|
||||
- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
|
||||
|
||||
Note that this command is a reserved keyboard shortcut in Firefox.
|
||||
Beachte, dass dieser Befehl eine reservierte Tastenkombination in Firefox ist.
|
||||
- <kbd>F1</kbd>
|
||||
- From the Application Menu, click **View > Command Palette…**.
|
||||
- Klicke im Anwendungsmenü auf **Ansicht > Befehlspalette...**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Commands for {% data variables.product.prodname_codespaces %}
|
||||
## Befehle für {% data variables.product.prodname_codespaces %}
|
||||
|
||||
To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces".
|
||||
Um alle Befehle zu {% data variables.product.prodname_github_codespaces %} anzuzeigen, [öffne die {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) und gib dann „Codespaces“ ein.
|
||||
|
||||
|
||||
|
||||
|
||||
### Suspending or stopping a codespace
|
||||
### Anhalten oder Beenden eines Codespaces
|
||||
|
||||
If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes.
|
||||
Wenn du ein neues Geheimnis hinzufügst oder den Computertyp änderst, musst du den Codespace beenden und neu starten, um deine Änderungen zu übernehmen.
|
||||
|
||||
To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "stop". Select **Codespaces: Stop Current Codespace**.
|
||||
Um den Container deines Codespaces zu anzuhalten oder zu beenden, greife auf die [{% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) zu. Beginne dann mit der Eingabe von „stop“. Wähle **Codespaces: Aktuellen Codespace beenden** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
### Adding a predefined dev container configuration
|
||||
### Hinzufügen einer vordefinierten Entwicklungscontainerkonfiguration
|
||||
|
||||
To add a predefined dev container configuration, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...**
|
||||
Um eine vordefinierte Entwicklungscontainerkonfiguration hinzuzufügen, [greife auf die {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) zu. Beginne dann mit der Eingabe von „dev container“. Wähle **Codespaces: Konfigurationsdateien für Entwicklungscontainer hinzufügen...** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
### Rebuilding a codespace
|
||||
### Neuerstellen eines Codespaces
|
||||
|
||||
If you add a dev container or edit any of the configuration files (`devcontainer.json` and `Dockerfile`), you'll have to rebuild your codespace for it to apply your changes.
|
||||
Wenn du einen Dev-Container hinzufügst oder eine der Konfigurationsdateien (`devcontainer.json` und `Dockerfile`) bearbeitst, musst du deinen Codespace neu erstellen, damit deine Änderungen übernommen werden.
|
||||
|
||||
To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
|
||||
Zur Neuerstellung deines Containers [greifst du auf die {% data variables.product.prodname_vscode_command_palette_shortname %} zu](#accessing-the-command-palette). Beginne dann mit der Eingabe von „rebuild“. Wähle **Codespaces: Container neu erstellen** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.full-rebuild-tip %}
|
||||
|
||||
### Codespaces logs
|
||||
### Codespaces-Protokolle
|
||||
|
||||
You can use the {% data variables.product.prodname_vscode_command_palette_shortname %} to access the codespace creation logs, or you can use it export all logs.
|
||||
Du kannst die {% data variables.product.prodname_vscode_command_palette_shortname %} verwenden, um auf die Erstellungsprotokolle für den Codespace zuzugreifen, oder du kannst damit alle Protokolle exportieren.
|
||||
|
||||
To retrieve the logs for {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to {% data variables.product.prodname_github_codespaces %} or select **Codespaces: View Creation Logs** to view logs related to the setup.
|
||||
Um die Protokolle für {% data variables.product.prodname_github_codespaces %} abzurufen, [öffne die {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), und beginne dann mit der Eingabe von „Protokoll“. Wähle **Codespaces: Protokolle exportieren** aus, um alle Protokolle im Zusammenhang mit {% data variables.product.prodname_github_codespaces %} zu exportieren, oder **Codespaces: Erstellungsprotokolle anzeigen**, um Protokolle im Zusammenhang mit dem Setup einzusehen.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
## Weiterführende Themen
|
||||
|
||||
- "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
|
||||
- [Verwenden von {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)
|
||||
|
||||
@@ -0,0 +1,145 @@
|
||||
---
|
||||
title: Creating a codespace for a repository
|
||||
intro: You can create a codespace for a branch in a repository to develop online.
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/creating-a-codespace
|
||||
- /github/developing-online-with-codespaces/creating-a-codespace
|
||||
- /codespaces/developing-in-codespaces/creating-a-codespace
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Create a codespace for a repo
|
||||
---
|
||||
|
||||
## About creating a codespace for a repository
|
||||
|
||||
{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace.
|
||||
|
||||
{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %}
|
||||
|
||||
Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-are-personal %}
|
||||
|
||||
If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
|
||||
|
||||
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
|
||||
|
||||
### The codespace creation process
|
||||
|
||||
When you create a codespace, a number of steps happen to create and connect you to your development environment:
|
||||
|
||||
- Step 1: VM and storage are assigned to your codespace.
|
||||
- Step 2: Container is created and your repository is cloned.
|
||||
- Step 3: You can connect to the codespace.
|
||||
- Step 4: Codespace continues with post-creation setup.
|
||||
|
||||
For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
|
||||
|
||||
For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)."
|
||||
|
||||
If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
{% data reusables.codespaces.use-visual-studio-features %}
|
||||
|
||||
{% data reusables.codespaces.prebuilds-crossreference %}
|
||||
|
||||
## Creating a codespace for a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for.
|
||||
|
||||
|
||||
|
||||
1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
|
||||
|
||||
|
||||
|
||||
If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
|
||||
|
||||
1. Create your codespace, either using the default options, or after configuring advanced options:
|
||||
|
||||
* **Use the default options**
|
||||
|
||||
To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**.
|
||||
|
||||
* **Configure options**
|
||||
|
||||
To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
|
||||
|
||||
1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**.
|
||||
|
||||
|
||||
|
||||
1. On the options page for your codespace, choose your preferred options from the dropdown menus.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**
|
||||
|
||||
* You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
|
||||
* The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
|
||||
* For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
|
||||
* For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
|
||||
* {% data reusables.codespaces.codespaces-machine-type-availability %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Click **Create codespace**.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.codespaces.creating-a-codespace-in-vscode %}
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To create a new codespace, use the `gh codespace create` subcommand.
|
||||
|
||||
```shell
|
||||
gh codespace create
|
||||
```
|
||||
|
||||
You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
|
||||
|
||||
Alternatively, you can use flags to specify some or all of the options:
|
||||
|
||||
```shell
|
||||
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
|
||||
```
|
||||
|
||||
In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
|
||||
|
||||
Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
|
||||
Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
|
||||
|
||||
For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Further reading
|
||||
- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
|
||||
- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Getting started with GitHub Codespaces for machine learning
|
||||
title: Erste Schritte mit GitHub Codespaces für maschinelles Lernen
|
||||
shortTitle: Machine learning
|
||||
intro: 'Learn about working on machine learning projects with {% data variables.product.prodname_github_codespaces %} and its out-of-the-box tools.'
|
||||
intro: 'Erfahre mehr über die Arbeit an ML-Projekten mit {% data variables.product.prodname_github_codespaces %} und den zugehörigen Tools.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -9,58 +9,63 @@ type: tutorial
|
||||
topics:
|
||||
- Codespaces
|
||||
- Developer
|
||||
ms.openlocfilehash: 905d5b14bfba5e47d1fdfdd7f0be75b16750652d
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158917'
|
||||
---
|
||||
## Einführung
|
||||
|
||||
## Introduction
|
||||
Dieser Leitfaden enthält eine Einführung in maschinelles Lernen mit {% data variables.product.prodname_github_codespaces %}. Du erstellst eine einfache Bildklassifizierung, lernst einige der Tools kennen, die in {% data variables.product.prodname_github_codespaces %} vorinstalliert sind, konfigurierst deine Entwicklungsumgebung für NVIDIA CUDA und öffnest deinen Codespace in JupyterLab.
|
||||
|
||||
This guide introduces you to machine learning with {% data variables.product.prodname_github_codespaces %}. You’ll build a simple image classifier, learn about some of the tools that come preinstalled in {% data variables.product.prodname_github_codespaces %}, configure your development environment for NVIDIA CUDA, and open your codespace in JupyterLab.
|
||||
## Erstellen einer einfachen Bildklassifizierung
|
||||
|
||||
## Building a simple image classifier
|
||||
Wir verwenden ein Jupyter-Notebook, um eine einfache Bildklassifizierung zu erstellen.
|
||||
|
||||
We'll use a Jupyter notebook to build a simple image classifier.
|
||||
Jupyter-Notebooks sind Gruppen von Zellen, die nacheinander ausgeführt werden können. Das Notebook, das wir verwenden, enthält eine Reihe von Zellen, die eine Bildklassifizierung mithilfe von [PyTorch](https://pytorch.org/) erstellen. Jede Zelle ist eine andere Phase dieses Prozesses: Herunterladen eines Datasets, Einrichten eines neuronales Netzes, Trainieren eines Modells und anschließendes Testen dieses Modells.
|
||||
|
||||
Jupyter notebooks are sets of cells that you can execute one after another. The notebook we'll use includes a number of cells that build an image classifier using [PyTorch](https://pytorch.org/). Each cell is a different phase of that process: download a dataset, set up a neural network, train a model, and then test that model.
|
||||
Wir führen alle Zellen nacheinander aus, um alle Phasen zum Erstellen der Bildklassifizierung auszuführen. Dabei speichert Jupyter die Ausgabe zurück in das Notebook, damit du die Ergebnisse untersuchen kannst.
|
||||
|
||||
We'll run all of the cells, in sequence, to perform all phases of building the image classifier. When we do this Jupyter saves the output back into the notebook so that you can examine the results.
|
||||
### Einen Codespace erstellen
|
||||
|
||||
### Creating a codespace
|
||||
|
||||
1. Go to the [github/codespaces-jupyter](https://github.com/github/codespaces-jupyter) template repository.
|
||||
1. Navigiere zum Vorlagenrepository [github/codespaces-jupyter](https://github.com/github/codespaces-jupyter).
|
||||
{% data reusables.codespaces.open-template-in-codespace-step %}
|
||||
|
||||
A codespace for this template will open in a web-based version of {% data variables.product.prodname_vscode %}.
|
||||
Ein Codespace für diese Vorlage wird in einer webbasierten Version von {% data variables.product.prodname_vscode %} geöffnet.
|
||||
|
||||
### Opening the image classifier notebook
|
||||
### Öffnen des Notebooks zur Bildklassifizierung
|
||||
|
||||
The default container image that's used by {% data variables.product.prodname_github_codespaces %} includes a set of machine learning libraries that are preinstalled in your codespace. For example, Numpy, pandas, SciPy, Matplotlib, seaborn, scikit-learn, Keras, PyTorch, Requests, and Plotly. For more information about the default image, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration)" and [the `devcontainers/images` repository](https://github.com/devcontainers/images/tree/main/src/universal).
|
||||
Das von {% data variables.product.prodname_github_codespaces %} verwendete Standardcontainerimage umfasst eine Reihe von ML-Bibliotheken, die in deinem Codespace vorinstalliert sind. Dazu gehören beispielsweise Numpy, pandas, SciPy, Matplotlib, seaborn, scikit-learn, Keras, PyTorch, Requests und Plotly. Weitere Informationen zum Standardimage findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration) und [im `devcontainers/images`-Repository](https://github.com/devcontainers/images/tree/main/src/universal).
|
||||
|
||||
1. In the {% data variables.product.prodname_vscode_shortname %} editor, close any "Get Started" tabs that are displayed.
|
||||
1. Open the `notebooks/image-classifier.ipynb` notebook file.
|
||||
1. Schließe im {% data variables.product.prodname_vscode_shortname %}-Editor alle angezeigten Registerkarten „Erste Schritte“.
|
||||
1. Öffne die Notebook-Datei `notebooks/image-classifier.ipynb`.
|
||||
|
||||
### Building the image classifier
|
||||
### Erstellen der Bildklassifizierung
|
||||
|
||||
The image classifier notebook contains all the code you need to download a dataset, train a neural network, and evaluate its performance.
|
||||
Das Notebook zur Bildklassifizierung enthält den gesamten Code, den du benötigst, um ein Dataset herunterzuladen, ein neuronales Netz zu trainieren und die Leistung zu bewerten.
|
||||
|
||||
1. Click **Run All** to execute all of the notebook’s cells.
|
||||
1. Klicke auf **Alle ausführen**, um alle Zellen des Notebooks auszuführen.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Scroll down to view the output of each cell.
|
||||
1. Scrolle nach unten, um die Ausgabe der einzelnen Zellen anzuzeigen.
|
||||
|
||||
|
||||
|
||||
|
||||
## Configuring NVIDIA CUDA for your codespace
|
||||
## Konfigurieren von NVIDIA CUDA für deinen Codespace
|
||||
|
||||
Some software requires you to install NVIDIA CUDA to use your codespace’s GPU. Where this is the case, you can create your own custom configuration, by using a `devcontainer.json` file, and specify that CUDA should be installed. For more information on creating a custom configuration, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
|
||||
Einige Software erfordert die Installation von NVIDIA CUDA, damit die GPU deines Codespace verwendet werden kann. Wenn dies der Fall ist, kannst du deine eigene benutzerdefinierte Konfiguration erstellen, indem du eine `devcontainer.json`-Datei verwendest und angibst, dass CUDA installiert werden soll. Weitere Informationen zum Erstellen einer benutzerdefinierten Konfiguration findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: For full details of the script that's run when you add the `nvidia-cuda` feature, see [the devcontainers/features repository](https://github.com/devcontainers/features/tree/main/src/nvidia-cuda).
|
||||
**Hinweis**: Ausführliche Informationen zu dem Skript, das ausgeführt wird, wenn du das `nvidia-cuda`-Feature hinzufügst, findest du im [Repository „devcontainers/features“](https://github.com/devcontainers/features/tree/main/src/nvidia-cuda).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Within the codespace, open the `.devcontainer/devcontainer.json` file in the editor.
|
||||
1. Add a top-level `features` object with the following contents:
|
||||
1. Öffne in einem Codespace die Datei `.devcontainer/devcontainer.json` im Editor.
|
||||
1. Füge ein `features`-Objekt auf oberster Ebene mit den folgenden Inhalten hinzu:
|
||||
|
||||
```json{:copy}
|
||||
"features": {
|
||||
@@ -70,9 +75,9 @@ Some software requires you to install NVIDIA CUDA to use your codespace’s GPU.
|
||||
}
|
||||
```
|
||||
|
||||
For more information about the `features` object, see the [development containers specification](https://containers.dev/implementors/features/#devcontainer-json-properties).
|
||||
Weitere Informationen zum `features`-Objekt findest du in der [Spezifikation für Entwicklungscontainer](https://containers.dev/implementors/features/#devcontainer-json-properties).
|
||||
|
||||
If you are using the `devcontainer.json` file from the image classifier repository you created for this tutorial, your `devcontainer.json` file will now look like this:
|
||||
Wenn du die Datei `devcontainer.json` aus dem Bildklassifizierungsrepository verwendest, das du für dieses Tutorial erstellt hast, sieht die Datei `devcontainer.json` nun wie folgt aus:
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -92,13 +97,12 @@ Some software requires you to install NVIDIA CUDA to use your codespace’s GPU.
|
||||
}
|
||||
```
|
||||
|
||||
1. Save the change.
|
||||
{% data reusables.codespaces.rebuild-command %}
|
||||
The codespace container will be rebuilt. This will take several minutes. When the rebuild is complete the codespace is automatically reopened.
|
||||
1. Publish your change to a repository so that CUDA will be installed in any new codespaces you create from this repository in future. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-from-vs-code)."
|
||||
1. Speichere die Änderungen.
|
||||
{% data reusables.codespaces.rebuild-command %} Der Codespacecontainer wird neu erstellt. Dies dauert einige Minuten. Wenn die Neuerstellung abgeschlossen ist, wird der Codespace automatisch erneut geöffnet.
|
||||
1. Veröffentliche die Änderung in einem Repository, damit CUDA in allen neuen Codespaces installiert wird, die du in Zukunft von diesem Repository aus erstellst. Weitere Informationen findest du unter [Erstellen eines Codespace mithilfe einer Vorlage](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-from-vs-code).
|
||||
|
||||
## Opening your codespace in JupyterLab
|
||||
## Öffnen deines Codespace in JupyterLab
|
||||
|
||||
You can open your codespace in JupyterLab from the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces), or by using {% data variables.product.prodname_cli %}. For more information, see "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)."
|
||||
Du kannst deinen Codespace in JupyterLab über die Seite „Deine Codespaces“ unter [github.com/codespaces](https://github.com/codespaces) oder mithilfe der {% data variables.product.prodname_cli %} öffnen. Weitere Informationen findest du unter [Öffnen eines vorhandenen Codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace).
|
||||
|
||||
{% data reusables.codespaces.jupyterlab-installed-in-codespace %}
|
||||
{% data reusables.codespaces.jupyterlab-installed-in-codespace %}
|
||||
|
||||
@@ -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: The codespace lifecycle
|
||||
intro: 'You can develop in a {% data variables.product.prodname_github_codespaces %} environment and maintain your data throughout the entire codespace lifecycle.'
|
||||
title: Der Codespace-Lebenszyklus
|
||||
intro: 'Du kannst in einer {% data variables.product.prodname_github_codespaces %}-Umgebung entwickeln und deine Daten während des gesamten Codespace-Lebenszyklus verwalten.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,58 +10,63 @@ topics:
|
||||
- Developer
|
||||
redirect_from:
|
||||
- /codespaces/developing-in-codespaces/codespaces-lifecycle
|
||||
ms.openlocfilehash: 660ced63e34c6de8025c65946542baca43534cfe
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180795'
|
||||
---
|
||||
## Informationen zum Lebenszyklus eines Codespaces
|
||||
|
||||
## About the lifecycle of a codespace
|
||||
Der Lebenszyklus eines Codespaces beginnt beim Erstellen des Codespaces und endet, wenn du den Codespace löschst. Du kannst eine Verbindung mit einem aktiven Codespace trennen und erneut herstellen, ohne dass die ausgeführten Prozesse dadurch beeinträchtigt werden. Du kannst einen Codespace beenden und neu starten, ohne Änderungen zu verlieren, die du an deinem Projekt vorgenommen hast.
|
||||
|
||||
The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project.
|
||||
## Einen Codespace erstellen
|
||||
|
||||
## Creating a codespace
|
||||
Wenn du an einem Projekt arbeiten möchtest, kannst du einen neuen Codespace erstellen oder einen vorhandenen Codespace öffnen. Wenn du in {% data variables.product.prodname_github_codespaces %} entwickelst, kannst du einen neuen Codespace anhand eines Branches deines Repositorys erstellen oder einen Codespace mit langer Ausführungsdauer für ein Feature nutzen. {% data reusables.codespaces.starting-new-project-template %} Weitere Informationen findest du unter „[Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)“ und „[Erstellen eines Codespaces aus einer Vorlage](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)“.
|
||||
|
||||
When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your repository each time you develop in {% data variables.product.prodname_github_codespaces %} or keep a long-running codespace for a feature. {% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
|
||||
{% data reusables.codespaces.max-number-codespaces %} Wenn du die maximale Anzahl aktiver Codespaces erreichst und versuchst, andere zu starten, wirst du aufgefordert, einen deiner aktiven Codespaces zu beenden.
|
||||
|
||||
{% data reusables.codespaces.max-number-codespaces %} Similarly, if you reach the maximum number of active codespaces and you try to start another, you are prompted to stop one of your active codespaces.
|
||||
|
||||
If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine.
|
||||
Falls du jedes Mal, wenn du an einem Projekt arbeitest, einen neuen Codespace erstellst, solltest du deine Änderungen regelmäßig pushen, damit neue Commits auf {% data variables.product.prodname_dotcom %} verfügbar sind. Wenn du für dein Projekt einen Codespace mit langer Ausführungsdauer verwendest, solltest du Inhalte aus dem Standardbranch deines Repositorys pullen, sobald du mit der Arbeit in deinem Codespace beginnst. Auf diese Weise verfügt deine Umgebung über die aktuellen Commits. Dieser Workflow ist mit der Arbeit an einem Projekt auf deinem lokalen Computer vergleichbar.
|
||||
|
||||
{% data reusables.codespaces.prebuilds-crossreference %}
|
||||
|
||||
## Saving changes in a codespace
|
||||
## Speichern von Änderungen in einem Codespace
|
||||
|
||||
When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
Wenn du über das Internet eine Verbindung mit einem Codespace herstellst, ist die Funktion für automatisches Speichern automatisch für den Web-Editor aktiviert und so konfiguriert, dass Änderungen nach einer bestimmten Verzögerung gespeichert werden. Wenn du über {% data variables.product.prodname_vscode %} auf deinem Desktop eine Verbindung mit einem Codespace herstellst, musst du die Funktion für automatisches Speichern aktivieren. Weitere Informationen findest du unter [Speichern/Automatisch Speichern](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in der {% data variables.product.prodname_vscode %}-Dokumentation.
|
||||
|
||||
Your work will be saved on a virtual machine in the cloud. You can close and stop a codespace and return to the saved work later. If you have unsaved changes, your editor will prompt you to save them before exiting. However, if your codespace is deleted, then your work will be deleted too. To persist your work, you will need to commit your changes and push them to your remote repository, or publish your work to a new remote repository if you created your codespace from a template. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)."
|
||||
Deine Arbeit wird auf einem virtuellen Computer in der Cloud gespeichert. Du kannst einen Codespace schließen und beenden und später zur gespeicherten Arbeit zurückkehren. Wenn du über Änderungen verfügst, die noch nicht gespeichert wurden, fordert dein Editor dich zum Speichern auf, bevor du das Programm beendest. Wenn dein Codespace jedoch gelöscht wird, wird auch deine Arbeit gelöscht. Um deine Arbeit beizubehalten, musst du deine Änderungen committen und in dein Remoterepository pushen oder deine Arbeit in einem neuen Remoterepository veröffentlichen, wenn du deinen Codespace aus einer Vorlage erstellt hast. Weitere Informationen findest du unter [Verwenden der Quellcodeverwaltung in deinem Codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace).
|
||||
|
||||
## Timeouts for {% data variables.product.prodname_github_codespaces %}
|
||||
## Timeouts für {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)."
|
||||
Wenn ein Codespace ohne Interaktion ausgeführt wird oder du deinen Codespace beendest, ohne ihn explizit anzuhalten, tritt nach einer bestimmten Dauer an Inaktivität ein Timeout auf, und der Codespace wird beendet. Standardmäßig wird ein Codespace nach einer Inaktivitätsperiode von 30 Minuten mit einem Timeout beendet. Du kannst diesen Zeitraum bei Codespaces, die du neu erstellst, jedoch anpassen. Weitere Informationen zum Festlegen des Standard-Timeoutzeitraums für deine Codespaces findest du unter [Festlegen des Timeoutzeitraums für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces). Weitere Informationen zum Anhalten eines Codespaces findest du unter [Anhalten eines Codespaces](#stopping-a-codespace).
|
||||
|
||||
When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
|
||||
Wenn ein Timeout für einen Codespace auftritt, werden deine Daten zum Zeitpunkt des letzten Speichervorgangs beibehalten. Weitere Informationen findest du unter [Speichern von Änderungen in einem Codespace](#saving-changes-in-a-codespace).
|
||||
|
||||
## Rebuilding a codespace
|
||||
## Neuerstellen eines Codespaces
|
||||
|
||||
You can rebuild your codespace to implement changes to your dev container configuration. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. By default, when you rebuild your codespace, {% data variables.product.prodname_github_codespaces %} will reuse images from your cache to speed up the rebuild process. Alternatively, you can perform a full rebuild, which clears your cache and rebuilds the container with fresh images.
|
||||
Du kannst deinen Codespace neu erstellen, um Änderungen an deiner Entwicklungscontainerkonfiguration zu implementieren. Für die meisten Anwendungsfälle ist das Erstellen eines neuen Codespaces eine Alternative zum Neuerstellen eines Codespaces. Wenn Du deinen Codespace neu erstellst, verwendet {% data variables.product.prodname_github_codespaces %} standardmäßig Images aus deinem Cache neu, um den Neuerstellungsprozess zu beschleunigen. Alternativ kannst du eine vollständige Neuerstellung durchführen, wodurch der Cache gelöscht und der Container mit neuen Images neu erstellt wird.
|
||||
|
||||
For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)" and "[Performing a full rebuild of a container](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container)."
|
||||
Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace) und [Durchführen einer vollständigen Neuerstellung eines Containers](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container).
|
||||
|
||||
## Stopping a codespace
|
||||
## Beenden eines Codespaces
|
||||
|
||||
{% data reusables.codespaces.stopping-a-codespace %} For more information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)."
|
||||
{% data reusables.codespaces.stopping-a-codespace %} Weitere Informationen findest du unter „[Beenden und Starten eines Codespaces](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)“.
|
||||
|
||||
## Deleting a codespace
|
||||
## Einen Codespace löschen
|
||||
|
||||
You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch.
|
||||
Du kannst einen Codespace für eine bestimmte Aufgabe erstellen und den Codespace sicher löschen, nachdem du deine Änderungen an einen Remotebranch gepusht hast.
|
||||
|
||||
If you try to delete a codespace with unpushed git commits, your editor will notify you that you have changes that have not been pushed to a remote branch. You can push any desired changes and then delete your codespace, or continue to delete your codespace and any uncommitted changes. You can also export your code to a new branch without creating a new codespace. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
|
||||
Wenn du versuchst, einen Codespace mit nicht gepushten Git-Commits zu löschen, wirst du in deinem Editor benachrichtigt, dass Änderungen vorliegen, die nicht an einen Remotebranch gepusht wurden. In diesem Fall kannst du alle gewünschten Änderungen pushen und deinen Codespace anschließend löschen, oder du löschst deinen Codespace mitsamt allen ausgecheckten Änderungen. Du kannst deinen Code auch in einen neuen Branch exportieren, ohne einen neuen Codespace zu erstellen. Weitere Informationen findest du unter [Exportieren von Änderungen in einen Branch](/codespaces/troubleshooting/exporting-changes-to-a-branch).
|
||||
|
||||
Codespaces that have been stopped and remain inactive for a specified period of time will be deleted automatically. By default, inactive codespaces are deleted after 30 days, but you can customize your codespace retention period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
Codespaces, die angehalten wurden und für einen bestimmten Zeitraum inaktiv bleiben, werden automatisch gelöscht. Standardmäßig werden inaktive Codespaces nach 30 Tagen gelöscht, du kannst allerdings den Aufbewahrungszeitraum für Codespaces anpassen. Weitere Informationen findest du unter [Konfigurieren des automatischen Löschens deiner Codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces).
|
||||
|
||||
If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)." Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
Wenn du einen Codespace erstellst, fallen weiterhin Speichergebühren an, bis er gelöscht wird, unabhängig davon, ob er aktiv oder beendet ist. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage). Das Löschen eines Codespaces verringert nicht den aktuellen abrechenbaren Betrag für {% data variables.product.prodname_github_codespaces %}, der während jedes monatlichen Abrechnungszyklus akkumuliert wird. Weitere Informationen findest du unter „[Anzeigen der {% data variables.product.prodname_github_codespaces %}-Nutzung](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)“.
|
||||
|
||||
For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
Weitere Informationen zum Löschen eines Codespaces findest du unter [Löschen eines Codespaces](/codespaces/developing-in-codespaces/deleting-a-codespace).
|
||||
|
||||
## Losing the connection while using {% data variables.product.prodname_github_codespaces %}
|
||||
## Unterbrechung der Verbindung bei Verwendung von {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often.
|
||||
{% data variables.product.prodname_github_codespaces %} ist eine cloudbasierte Entwicklungsumgebung, für die eine Internetverbindung erforderlich ist. Wenn die Internetverbindung unterbrochen wird, während du in einem Codespace arbeitest, kannst du nicht auf deinen Codespace zugreifen. Alle ausgecheckten Änderungen werden jedoch gespeichert. Sobald die Internetverbindung wiederhergestellt ist, kannst du dich erneut mit deinem Codespace verbinden. Der Codespace weist in diesem Fall den exakt selben Zustand auf wie vor der Verbindungsunterbrechung. Wenn deine Internetverbindung instabil ist, solltest du deine Änderungen häufig committen und pushen.
|
||||
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["Dev Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) for {% data variables.product.prodname_vscode_shortname %} to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
Wenn du weißt, dass du häufig offline arbeiten wirst, kannst du deine `devcontainer.json`-Datei mit der Erweiterung [„Dev Containers“](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) für {% data variables.product.prodname_vscode_shortname %} verwenden, um einen lokalen Entwicklungscontainer für dein Repository zu erstellen und anzufügen. Weitere Informationen findest du unter [Entwickeln innerhalb eines Containers](https://code.visualstudio.com/docs/remote/containers) in der {% data variables.product.prodname_vscode %}-Dokumentation.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Listing the codespaces in your organization
|
||||
title: Auflisten der Codespaces in deiner Organisation
|
||||
shortTitle: List organization codespaces
|
||||
intro: 'You can list all of the currently active or stopped codespaces for your organization.'
|
||||
intro: Du kannst alle aktuell aktiven oder beendeten Codespaces für deine Organisation auflisten.
|
||||
permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -10,31 +10,36 @@ type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Administrator
|
||||
ms.openlocfilehash: e3d475560c76449ed20b70fbce29ef6273f788fc
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158629'
|
||||
---
|
||||
## Übersicht
|
||||
|
||||
## Overview
|
||||
Als Organisationsbesitzer können alle aktuell aktiven oder beendeten Codespaces für deine Organisation auflisten. Möglicherweise möchtest du so vorgehen, um zu überprüfen, wie viele Codespaces Benutzer erstellen, um sicherzustellen, dass sie keine unnötigen Kosten verursachen. Informationen zu den Kosten findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces).
|
||||
|
||||
As an organization owner, you can list all of the currently active and stopped codespaces for your organization. You might want to do this to check how many codespaces users are creating, to make sure they aren't incurring unnecessary costs. For information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
Die einfachste Möglichkeit zum Auflisten der Codespaces für eine Organisation besteht darin, {% data variables.product.prodname_cli %} zu verwenden. Du kannst auch die REST-API verwenden, die weitere Informationen zu jedem Codespace bereitstellt.
|
||||
|
||||
The easiest way to list the codespaces for an organization is by using {% data variables.product.prodname_cli %}. You can also use the REST API, which provides more information about each codespace.
|
||||
Informationen zum Anzeigen der aktuellen Gesamtsumme der {% data variables.product.prodname_codespaces %}-Nutzung für deine Organisation oder dein Unternehmen und zum Generieren eines detaillierten Berichts findest du unter [Anzeigen deiner {% data variables.product.prodname_github_codespaces %}-Nutzung](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage).
|
||||
|
||||
For information on how to see the current total {% data variables.product.prodname_codespaces %} usage for your organization or enterprise, and generate a detailed report, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
### Verwenden von {% data variables.product.prodname_cli %} zum Auflisten von Codespaces
|
||||
|
||||
### Using {% data variables.product.prodname_cli %} to list codespaces
|
||||
|
||||
To list all of the current codespaces for a specified organization, use the following command.
|
||||
Wenn du alle aktuellen Codespaces für eine bestimmte Organisation auflisten möchtest, verwende den folgenden Befehl.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace list --org ORGANIZATION
|
||||
```
|
||||
|
||||
This command returns a list that includes the following information for each codespace:
|
||||
- The name and display name
|
||||
- The user who created the codespace
|
||||
- The repository and branch
|
||||
- The current state of the codespace
|
||||
Dieser Befehl gibt eine Liste zurück, die die folgenden Informationen für jeden Codespace enthält:
|
||||
- Den Namen und den Anzeigenamen
|
||||
- Den Benutzer, der den Codespace erstellt hat
|
||||
- Das Repository und den Branch
|
||||
- Den aktuellen Status des Codespace
|
||||
|
||||
To list all of the current codespaces for an organization that were created by a specific user, use the following command.
|
||||
Wenn du alle aktuellen Codespaces für eine Organisation auflisten möchtest, die von einem bestimmten Benutzer erstellt wurden, verwendest du den folgenden Befehl.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace list --org ORGANIZATION --user USER
|
||||
@@ -42,12 +47,12 @@ gh codespace list --org ORGANIZATION --user USER
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: In the above commands, replace `ORGANIZATION` with the name of the organization you are querying. You must be an owner of the organization.
|
||||
**Hinweis**: Ersetze in den oben genannten Befehlen `ORGANIZATION` durch den Namen der Organisation, die du abfragst. Du musst Besitzer der Organisation sein.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Using the REST API to list codespaces
|
||||
### Verwenden der REST-API zum Auflisten von Codespaces
|
||||
|
||||
You can use the `/orgs/{org}/codespaces` API endpoint as an alternative method of listing the current codespaces for an organization. This returns more information than {% data variables.product.prodname_cli %}; for example, the machine type details.
|
||||
Du kannst den API-Endpunkt `/orgs/{org}/codespaces` als alternative Methode zum Auflisten der aktuellen Codespaces für eine Organisation verwenden. Dieser Endpunkt gibt mehr Informationen als {% data variables.product.prodname_cli %} zurück, z. B. die Details des Computertyps.
|
||||
|
||||
For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)."
|
||||
Weitere Informationen zu diesem Endpunkt findest du unter [Codespaceorganisationen](/rest/codespaces/organizations#list-codespaces-for-the-organization).
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Adding features to a devcontainer.json file
|
||||
title: Hinzufügen von Features zu einer Datei vom Typ „devcontainer.json“
|
||||
shortTitle: Adding features
|
||||
intro: With features, you can quickly add tools, runtimes, or libraries to your dev container configuration.
|
||||
intro: 'Mit Features kannst du Schnell Tools, Runtimes oder Bibliotheken zu deiner Entwicklungscontainerkonfiguration hinzufügen.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -10,34 +10,39 @@ type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
ms.openlocfilehash: 7e72739e93e83995d86baf19d62f7bf2e1c5b6bc
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180827'
|
||||
---
|
||||
{% data reusables.codespaces.about-features %} Verwende die Registerkarten in diesem Artikel, um Anweisungen für die einzelnen Möglichkeiten zum Hinzufügen von Features anzuzeigen.
|
||||
|
||||
{% data reusables.codespaces.about-features %} Use the tabs in this article to display instructions for each of these ways of adding features.
|
||||
|
||||
## Adding features to a `devcontainer.json` file
|
||||
## Hinzufügen von Features zu einer Datei vom Typ `devcontainer.json`
|
||||
|
||||
{% webui %}
|
||||
|
||||
1. Navigate to your repository on {% data variables.product.prodname_dotcom_the_website %}, find your `devcontainer.json` file, and click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
|
||||
1. Navigiere zu deinem Repository auf {% data variables.product.prodname_dotcom_the_website %}, suche deine `devcontainer.json`-Datei, und klicke auf {% octicon "pencil" aria-label="The edit icon" %}, um die Datei zu bearbeiten.
|
||||
|
||||
If you don't already have a `devcontainer.json` file, you can create one now. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
|
||||
1. To the right of the file editor, in the **Marketplace** tab, browse or search for the feature you want to add, then click the name of the feature.
|
||||
Ist noch keine Datei vom Typ `devcontainer.json` vorhanden, kannst du jetzt eine erstellen. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration).
|
||||
1. Navigiere rechts neben dem Datei-Editor auf der Registerkarte **Marketplace** zu dem Feature, das du hinzufügen möchtest, oder suche nach diesem, und klicke dann auf den Namen des Features.
|
||||
|
||||
|
||||
3. Under "Installation," click the code snippet to copy it to your clipboard, then paste the snippet into the `features` object in your `devcontainer.json` file.
|
||||
|
||||
3. Klicke unter „Installation“ auf den Codeschnipsel, um ihn in die Zwischenablage zu kopieren, und füge ihn dann in das `features`-Objekt in deiner `devcontainer.json`-Datei ein.
|
||||
|
||||
|
||||
|
||||
|
||||
```JSON
|
||||
"features": {
|
||||
...
|
||||
"ghcr.io/devcontainers/features/terraform:1": {},
|
||||
...
|
||||
}
|
||||
}
|
||||
```
|
||||
1. By default, the latest version of the feature will be used. To choose a different version, or configure other options for the feature, expand the properties listed under "Options" to view the available values, then add the options by manually editing the object in your `devcontainer.json` file.
|
||||
1. Standardmäßig wird die neueste Version des Features verwendet. Um eine andere Version auszuwählen oder andere Optionen für das Feature zu konfigurieren, erweitere die unter „Optionen“ aufgeführten Eigenschaften, um die verfügbaren Werte anzuzeigen, und füge dann die Optionen hinzu, indem du das Objekt in deiner `devcontainer.json`-Datei manuell bearbeitest.
|
||||
|
||||
|
||||
|
||||
|
||||
```JSON
|
||||
"features": {
|
||||
@@ -47,11 +52,11 @@ topics:
|
||||
"tflint": "latest"
|
||||
},
|
||||
...
|
||||
}
|
||||
}
|
||||
```
|
||||
1. Commit the changes to your `devcontainer.json` file.
|
||||
1. Committe die Änderungen an der Datei `devcontainer.json`.
|
||||
|
||||
The configuration changes will take effect in new codespaces created from the repository. To make the changes take effect in existing codespaces, you will need to pull the updates to the `devcontainer.json` file into your codespace, then rebuild the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
|
||||
Die Konfigurationsänderungen werden in neuen Codespaces wirksam, die aus dem Repository erstellt wurden. Damit die Änderungen in vorhandenen Codespaces wirksam werden, musst du die Aktualisierungen der Datei `devcontainer.json` in deinen Codespace pullen und dann den Container für den Codespace neu erstellen. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace).
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -59,21 +64,21 @@ The configuration changes will take effect in new codespaces created from the re
|
||||
|
||||
{% note %}
|
||||
|
||||
To add features 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).
|
||||
Wenn du lokal arbeitest und keine Verbindung mit einem Codespace besteht, musst du zum Hinzufügen von Features in {% data variables.product.prodname_vscode_shortname %} die Erweiterung „Dev Containers“ installieren und aktivieren. Weitere Informationen zu dieser Erweiterung findest du unter [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.codespaces.command-pallette %}
|
||||
2. Start typing "Configure" and select **Codespaces: Configure Dev Container Features**.
|
||||
2. Beginne mit der Eingabe von „Konfigurieren“, und wähle **Codespaces: Konfigurieren von Features für Entwicklungscontainer** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Update your feature selections, then click **OK**.
|
||||
3. Aktualisiere deine Featureauswahl, und klicke dann auf **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. If you're working in a codespace, a prompt will appear in the lower-right corner. To rebuild the container and apply the changes to the codespace you're working in, click **Rebuild Now**.
|
||||
4. Wenn du in einem Codespace arbeitest, wird in der unteren rechten Ecke eine Eingabeaufforderung angezeigt. Klicke auf **Jetzt neu erstellen**, um den Container neu zu erstellen und die Änderungen auf den Codespace anzuwenden, in dem du arbeitest.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endvscode %}
|
||||
{% endvscode %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Einführung in Entwicklungscontainer
|
||||
intro: 'Wenn du in einem Codespace arbeitest, wird die Umgebung mithilfe eines Entwicklungscontainers erstellt, der auf einem virtuellen Computer gehostet wird.'
|
||||
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: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158773'
|
||||
---
|
||||
## Informationen zu Entwicklungscontainern
|
||||
|
||||
Entwicklungscontainer (auch „Dev-Container“ genannt) sind Docker-Container, die speziell für die Bereitstellung einer Entwicklungsumgebung mit vollem Funktionsumfang konfiguriert sind. Wenn du in einem Codespace arbeitest, verwendest du einen Dev-Container auf einem virtuellen Computer.
|
||||
## About dev containers
|
||||
|
||||
Du kannst den Dev-Container für ein Repository so konfigurieren, dass für dieses Repository erstellte Codespaces eine maßgeschneiderte Entwicklungsumgebung mit allen Tools und Runtimes bieten, die du für ein bestimmtes Projekt benötigst. Wenn du keine Konfiguration im Repository definierst, verwendet {% data variables.product.prodname_github_codespaces %} eine Standardkonfiguration, die viele der allgemeinen Tools enthält, die dein Team möglicherweise für die Entwicklung deines Projekts benötigt. Weitere Informationen findest du unter [Verwenden der Dev-Containerstandardkonfiguration](#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.
|
||||
|
||||
Die Konfigurationsdateien für einen Dev-Container sind in einem `.devcontainer`-Verzeichnis in deinem Repository enthalten. Du kannst mit {% data variables.product.prodname_vscode %} deine Konfigurationsdateien hinzufügen. Du kannst aus einer Auswahl vordefinierter Konfigurationen für verschiedene Projekttypen wählen. Diese kannst du ohne weitere Konfiguration verwenden, oder die Konfigurationen bearbeiten, um die von ihnen erzeugte Entwicklungsumgebung zu optimieren. Weitere Informationen findest du unter [Verwenden einer vordefinierten Dev-Containerkonfiguration](#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)."
|
||||
|
||||
Alternativ kannst du deine eigenen benutzerdefinierten Konfigurationsdateien hinzufügen. Weitere Informationen findest du unter [Erstellen einer benutzerdefinierten Dev-Containerkonfiguration](#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)."
|
||||
|
||||
Du kannst eine einzelne Dev-Containerkonfiguration für ein Repository, verschiedene Konfigurationen für verschiedene Branches oder mehrere Konfigurationen definieren. Wenn mehrere Konfigurationen verfügbar sind, können Benutzer ihre bevorzugte Konfiguration auswählen, wenn sie einen Codespace erstellen. Dies ist besonders nützlich für große Repositorys, die Quellcode in verschiedenen Programmiersprachen oder für verschiedene Projekte enthalten. Du kannst eine Auswahl von Konfigurationen erstellen, die verschiedenen Teams ermöglichen, in einem Codespace zu arbeiten, der für die von ihnen ausgeführte Arbeit geeignet ist.
|
||||
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)."
|
||||
|
||||
Wenn du einen Codespace auf der Grundlage einer Vorlage erstellst, kannst du mit einer Konfigurationsdatei oder mehreren Konfigurationsdateien für Entwicklercontainer in deinem Arbeitsbereich beginnen. Um deine Umgebung weiter zu konfigurieren, kannst du diesen Dateien Einstellungen hinzufügen oder Einstellungen daraus entfernen und den Container neu erstellen, um die Änderungen auf den von dir verwendeten Codespace anzuwenden. Wenn Du deinen Codespace in einem Repository auf {% data variables.product.product_name %} veröffentlichst, haben alle Codespaces, die du aus diesem Repository erstellt hast, die von dir definierte Konfiguration. Weitere Informationen findest du unter [Anwenden von Konfigurationsänderungen auf einen Codespace](#applying-configuration-changes-to-a-codespace) und [Erstellen eines Codespace mithilfe einer Vorlage](/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
|
||||
|
||||
Die primäre Datei in einer Dev-Containerkonfiguration ist die `devcontainer.json`-Datei. Mit dieser Datei kannst du die Umgebung von Codespaces bestimmen, die für dein Repository erstellt wurden. Der Inhalt dieser Datei definiert einen Dev-Container, der Frameworks, Tools, Erweiterungen und Portweiterleitung enthalten kann. Die `devcontainer.json`-Datei enthält in der Regel einen Verweis auf eine Dockerfile, die sich für gewöhnlich neben der `devcontainer.json`-Datei befindet.
|
||||
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.
|
||||
|
||||
Wenn du einen Codespace aus einem Repository ohne Datei vom Typ `devcontainer.json` erstellst oder mit der leeren Vorlage von {% data variables.product.company_short %} beginnst, wird die Standardkonfiguration des Entwicklungscontainers verwendet. Weitere Informationen findest du unter [Verwenden der Dev-Containerstandardkonfiguration](#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)."
|
||||
|
||||
Die `devcontainer.json`-Datei befindet sich in der Regel im `.devcontainer`-Verzeichnis deines Repositorys. Alternativ kannst du sie direkt im Stamm des Repositorys finden; in diesem Fall muss der Dateiname mit einem Punkt beginnen: `.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`.
|
||||
|
||||
Wenn du eine Auswahl an Dev-Containerkonfigurationen in deinem Repository haben möchtest, müssen sich alle Alternativen zur Datei `.devcontainer/devcontainer.json` (oder `.devcontainer.json`) in ihrem eigenen Unterverzeichnis im Pfad `.devcontainer/SUBDIRECTORY/devcontainer.json` befinden. So könntest du beispielsweise zwei Konfigurationen zur Auswahl haben:
|
||||
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`
|
||||
|
||||
Wenn dein Repository mehrere `devcontainer.json`-Dateien enthält, wird jeder Codespace nur aus einer der Konfigurationen erstellt. Einstellungen können nicht importiert oder zwischen `devcontainer.json`-Dateien vererbt werden. Wenn von einer `devcontainer.json`-Datei in einem benutzerdefinierten Unterverzeichnis andere Dateien abhängig sind, z. B. die Dockerfile oder Skripts, die von Befehlen in der `devcontainer.json`-Datei ausgeführt werden, solltest du diese Dateien gemeinsam im selben Unterverzeichnis unterbringen.
|
||||
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.
|
||||
|
||||
Informationen zum Auswählen deiner bevorzugten Entwicklungscontainerkonfiguration beim Erstellen eines Codespace findest du unter [Erstellen eines Codespace für ein Repository](/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 %}
|
||||
|
||||
#### Verwendung der Datei „devcontainer.json“
|
||||
#### How to use the devcontainer.json
|
||||
|
||||
Es ist sinnvoll, die Datei `devcontainer.json` als Mittel zur „Anpassung“ und nicht zur „Personalisierung“ zu betrachten. Du solltest nur Komponenten einschließen, die alle Mitwirkenden an deiner Codebasis als Standardelemente der Entwicklungsumgebung benötigen, nicht solche, die persönlichen Vorlieben entsprechen. Linter etwa eignen sich gut für die Standardisierung, und jeder sollte sie installieren, darum solltest du sie in deine `devcontainer.json`-Datei aufnehmen. Benutzeroberflächendecorator oder Designs sind eine Frage des persönlichen Geschmacks und sollten nicht in die `devcontainer.json`-Datei aufgenommen werden.
|
||||
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.
|
||||
|
||||
Du kannst deine Codespaces mithilfe von Dotfiles und der Einstellungssynchronisierung personalisieren. Weitere Informationen findest du unter [Personalisieren von {% data variables.product.prodname_github_codespaces %} für dein Konto](/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
|
||||
|
||||
Du kannst eine Dockerfile als Teil deiner Dev-Containerkonfiguration hinzufügen.
|
||||
You can add a Dockerfile as part of your dev container configuration.
|
||||
|
||||
Die Dockerfile-Datei ist eine Textdatei mit Anweisungen, die erforderlich sind, um ein neues Docker-Containerimage zu erstellen. Mit diesem Image wird jedes Mal dann ein Entwicklungscontainer generiert, wenn jemand einen Codespace mithilfe der `devcontainer.json`-Datei erstellt, die auf diese Dockerfile verweist. Die Anweisungen in der Dockerfile beginnen in der Regel mit dem Verweisen auf ein übergeordnetes Image, auf dem das neue Image basiert, das erstellt wird. Darauf folgen die während des Imageerstellungsprozesses ausgeführten Befehle, z. B. zum Installieren von Softwarepaketen.
|
||||
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.
|
||||
|
||||
Die Dockerfile für einen Dev-Container befindet sich in der Regel im `.devcontainer`-Ordner neben der `devcontainer.json`, in der darauf verwiesen wird.
|
||||
The Dockerfile for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis**: Als Alternative zur Verwendung einer Dockerfile kannst du mit der `image`-Eigenschaft in der `devcontainer.json`-Datei direkt auf ein vorhandenes Image verweisen, das du verwenden möchtest. Das hier angegebene Image muss von jeder festgelegten Imagerichtlinie der Organisation zugelassen werden. Weitere Informationen findest du unter [Einschränken des Basisimages für Codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces). Wenn weder eine Dockerfile noch ein Image gefunden wird, wird das Standardcontainerimage verwendet. Weitere Informationen findest du unter [Verwenden der Dev-Containerstandardkonfiguration](#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 %}
|
||||
|
||||
#### Einfaches Dockerfile-Beispiel
|
||||
#### Simple Dockerfile example
|
||||
|
||||
Im folgenden Beispiel werden vier Anweisungen verwendet:
|
||||
The following example uses four instructions:
|
||||
|
||||
`ARG` definiert eine Buildzeitvariable.
|
||||
`ARG` defines a build-time variable.
|
||||
|
||||
`FROM` gibt das übergeordnete Image an, auf dem das generierte Docker-Image basiert.
|
||||
`FROM` specifies the parent image on which the generated Docker image will be based.
|
||||
|
||||
`COPY` kopiert eine Datei und fügt sie dem Dateisystem hinzu.
|
||||
`COPY` copies a file and adds it to the filesystem.
|
||||
|
||||
`RUN` aktualisiert Paketlisten und führt ein Skript aus. Du kannst auch eine `RUN`-Anweisung zum Installieren von Software verwenden, wie in den kommentierten Anweisungen gezeigt. Verwende zum Ausführen mehrerer Befehle `&&`, um die Befehle in einer einzelnen `RUN`-Anweisung zu kombinieren.
|
||||
`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
|
||||
```
|
||||
|
||||
Weitere Informationen zu Dockerfile-Anweisungen findest du in der Docker-Dokumentation unter [Dockerfile-Referenz](https://docs.docker.com/engine/reference/builder).
|
||||
For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation.
|
||||
|
||||
#### Verwenden einer Docker-Datei
|
||||
#### Using a Dockerfile
|
||||
|
||||
Wenn du eine Dockerfile als Teil einer Dev-Containerkonfiguration verwenden möchtest, verweise in deiner `devcontainer.json`-Datei mithilfe der `dockerfile`-Eigenschaft auf sie.
|
||||
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 @@ Wenn du eine Dockerfile als Teil einer Dev-Containerkonfiguration verwenden möc
|
||||
}
|
||||
```
|
||||
|
||||
Wenn du die vorhandene Containerorchestrierung in deinem Entwicklungscontainer verwenden möchtest, stehen dir verschiedene Optionen zur Verfügung. Weitere Informationen findest du auf der Website für Entwicklungscontainer im Abschnitt „Orchestrierungsoptionen“ der [Spezifikation](https://containers.dev/implementors/spec/#orchestration-options).
|
||||
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.
|
||||
|
||||
## Verwenden der Dev-Containerstandardkonfiguration
|
||||
## Using the default dev container configuration
|
||||
|
||||
Wenn du keine Konfiguration in deinem Repository definierst, erstellt {% data variables.product.prodname_dotcom %} einen Codespace mit einem Linux-Standardbasisimage. Dieses Linux-Image enthält eine Reihe von Runtimeversionen für beliebte Sprachen wie Python, Node, PHP, Java, Go, C++, Ruby und .NET Core/C#. Die neuesten oder LTS-Versionen dieser Sprachen werden verwendet. Es gibt auch Tools zur Unterstützung von Data Science und maschinellem Lernen, z. B. JupyterLab und Conda. Im Image sind auch andere Entwicklertools und Hilfsprogramme wie Git, GitHub-CLI, YARN, OpenSSH und vim enthalten. Verwende den `devcontainer-info content-url`-Befehl in deinem Codespaceterminal, und folge der vom Befehl ausgegebenen URL, um alle enthaltenen Sprachen, Runtimes und Tools anzuzeigen.
|
||||
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.
|
||||
|
||||
Informationen zu den Komponenten des Linux-Standardimages findest du im [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal)-Repository.
|
||||
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.
|
||||
|
||||
Die Standardkonfiguration ist eine gute Option, wenn du an einem kleinen Projekt arbeitest, das die von {% data variables.product.prodname_github_codespaces %} bereitgestellten Sprachen und Tools verwendet.
|
||||
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.
|
||||
|
||||
## Verwenden einer vordefinierten Dev-Containerkonfiguration
|
||||
## Using a predefined dev container configuration
|
||||
|
||||
Wenn du {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} oder in einem Webbrowser verwendest, kannst du eine Entwicklercontainerkonfiguration für dein Repository erstellen, indem du aus einer Liste vordefinierter Konfigurationen auswählst. Diese Konfigurationen bieten gebräuchliche Setups für bestimmte Projekttypen und können dir helfen, schnell mit einer Konfiguration zu beginnen, die bereits über die entsprechenden Containeroptionen, {% data variables.product.prodname_vscode %}-Einstellungen und {% data variables.product.prodname_vscode %}-Erweiterungen verfügt, die installiert werden sollen.
|
||||
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.
|
||||
|
||||
Die Verwendung einer vordefinierten Konfiguration ist eine großartige Möglichkeit, wenn zusätzliche Erweiterbarkeit erforderlich ist. Du kannst auch mit einer vordefinierten Konfiguration beginnen und sie nach Bedarf für dein Projekt ändern. Weitere Informationen zu den Definitionen vordefinierter Entwicklungscontainer findest du im [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src)-Repository.
|
||||
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.
|
||||
|
||||
Du kannst entweder beim Arbeiten in einem Codespace oder bei der Arbeit in einem lokalen Repository eine vordefinierte Dev-Containerkonfiguration hinzufügen. Wenn du lokal arbeitest und keine Verbindung mit einem Codespace besteht, muss dazu in {% data variables.product.prodname_vscode_shortname %} die Erweiterung „Dev Containers“ installiert und aktiviert sein. Weitere Informationen zu dieser Erweiterung findest du unter [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). Das folgende Verfahren beschreibt den Prozess, wenn du einen Codespace verwendest. Die Schritte in {% data variables.product.prodname_vscode_shortname %} sind sehr ähnlich, wenn du nicht mit einem Codespace verbunden bist.
|
||||
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. Klicke auf die Definition, die du verwenden möchtest.
|
||||
1. Click the definition you want to use.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Folge den Eingabeaufforderungen, um deine Definition anzupassen. Weitere Informationen zu den Optionen zum Anpassen deiner Definition findest du unter [Hinzufügen zusätzlicher Features zur `devcontainer.json`-Datei](#adding-additional-features-to-your-devcontainerjson-file).
|
||||
1. Klicke auf **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. Wenn du in einem Codespace arbeitest, wende deine Änderungen an, indem du in der Nachricht unten rechts im Fenster auf **Jetzt neu erstellen** klickst. Weitere Informationen zum Neuerstellen deines Containers findest du unter [Anwenden von Änderungen auf deine Konfiguration](#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)."
|
||||
|
||||
|
||||
|
||||
|
||||
### Hinzufügen zusätzlicher Features zu deiner `devcontainer.json`-Datei
|
||||
### Adding additional features to your `devcontainer.json` file
|
||||
|
||||
{% data reusables.codespaces.about-features %} Weitere Informationen findest du unter [Hinzufügen von Features zu einer Datei vom Typ `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)."
|
||||
|
||||
## Erstellen einer benutzerdefinierten Dev-Containerkonfiguration
|
||||
## Creating a custom dev container configuration
|
||||
|
||||
Wenn keine der vordefinierten Konfigurationen deinen Anforderungen entspricht, kannst du eine benutzerdefinierte Konfiguration erstellen, indem du deine eigene `devcontainer.json`-Datei schreibst.
|
||||
If none of the predefined configurations meets your needs, you can create a custom configuration by writing your own `devcontainer.json` file.
|
||||
|
||||
* Wenn du eine einzelne `devcontainer.json`-Datei hinzufügst, die von jedem verwendet wird, der einen Codespace aus deinem Repository erstellt, erstelle die Datei in einem `.devcontainer`-Verzeichnis im Stamm des Repositorys.
|
||||
* Wenn du Benutzern eine Auswahl an Konfigurationen anbieten möchtest, kannst du mehrere benutzerdefinierte `devcontainer.json`-Dateien erstellen, die sich jeweils in einem separaten Unterverzeichnis des `.devcontainer`-Verzeichnisses befinden.
|
||||
* 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 %}
|
||||
|
||||
**Hinweise**:
|
||||
- Du kannst deine `devcontainer.json`-Dateien nicht in Verzeichnissen suchen, die mehr als eine Ebene unter `.devcontainer` liegen. Beispielsweise funktioniert eine Datei unter `.devcontainer/teamA/devcontainer.json`, aber nicht unter `.devcontainer/teamA/testing/devcontainer.json`.
|
||||
- {% data reusables.codespaces.configuration-choice-templates %} Weitere Informationen findest du unter [Einrichten eines Vorlagenrepositorys für {% 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 %}
|
||||
|
||||
Wenn das Repository mehrere `devcontainer.json`-Dateien enthält, werden sie auf der Seite mit den Optionen zur Codespaceerstellung aufgeführt. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/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)."
|
||||
|
||||
|
||||
|
||||
|
||||
### Hinzufügen einer Datei vom Typ `devcontainer.json`
|
||||
### Adding a `devcontainer.json` file
|
||||
|
||||
Wenn dein Repository noch keine Datei vom Typ `devcontainer.json` enthält, kannst du schnell eine solche Datei von {% data variables.product.prodname_dotcom_the_website %} hinzufügen.
|
||||
1. Navigiere zu deinem Repository, und klicke auf die Dropdownliste **{% octicon "code" aria-label="The code icon" %} Code**.
|
||||
1. Klicke auf der Registerkarte **Codespaces** auf die Auslassungspunkte ( **...** ), und wähle dann **Entwicklungscontainer konfigurieren** aus.
|
||||
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**.
|
||||
|
||||
|
||||
|
||||
|
||||
Im Editor wird eine neue `.devcontainer/devcontainer.json`-Datei geöffnet. Die Datei enthält einige anfängliche Eigenschaften, einschließlich eines `features`-Objekts, dem du neue Tools, Bibliotheken oder Runtimes hinzufügen kannst. Weitere Informationen findest du unter [Hinzufügen von Features zu einer Datei vom Typ `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)."
|
||||
|
||||
Wenn dein Repository bereits eine oder mehrere Dateien vom Typ `devcontainer.json` enthält, wird durch Klicken auf **Entwicklungscontainer konfigurieren** die vorhandene `devcontainer.json`-Datei mit der höchsten Priorität gemäß der [Spezifikation](https://containers.dev/implementors/spec/#devcontainerjson) auf containers.dev geöffnet.
|
||||
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.
|
||||
|
||||
### Standardkonfigurationsauswahl während der Codespaceerstellung
|
||||
### Default configuration selection during codespace creation
|
||||
|
||||
Wenn `.devcontainer/devcontainer.json` oder `.devcontainer.json` vorhanden ist, ist es die Standardauswahl in der Liste der verfügbaren Konfigurationsdateien, wenn du einen Codespace erstellst. Wenn keine der Dateien vorhanden ist, wird die Dev-Containerstandardkonfiguration standardmäßig ausgewählt.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
### Bearbeiten der Datei „devcontainer.json“
|
||||
### Editing the devcontainer.json file
|
||||
|
||||
Du kannst die unterstützten Konfigurationsschlüssel In der `devcontainer.json`-Datei hinzufügen und bearbeiten, um Aspekte der Codespaceumgebung festzulegen, z. B. welche {% data variables.product.prodname_vscode_shortname %}-Erweiterungen installiert werden sollen. {% 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 %}
|
||||
|
||||
Die `devcontainer.json`-Datei wird im JSONC-Format (JSON mit Kommentaren) geschrieben. So kannst du Kommentare in die Konfigurationsdatei einfügen. Weitere Informationen findest du unter [Bearbeiten von JSON mit {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments) in der {% data variables.product.prodname_vscode_shortname %}-Dokumentation.
|
||||
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 %}
|
||||
|
||||
**Hinweis**: Wenn du einen Linter verwendest, um die `devcontainer.json`-Datei zu überprüfen, stelle sicher, dass er auf JSONC festgelegt ist, und JSON oder Kommentare nicht als Fehler gemeldet werden.
|
||||
**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 %}
|
||||
|
||||
### Schnittstelleneinstellungen für {% data variables.product.prodname_vscode_shortname %}
|
||||
### Interface settings for {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
Du kannst die Schnittstelleneinstellungen für {% data variables.product.prodname_vscode_shortname %} mit drei Bereichen konfigurieren: Arbeitsbereich, Remote [Codespaces] und Benutzer. Du kannst diese Bereiche im Editor für die {% data variables.product.prodname_vscode_shortname %}-Einstellungen anzeigen.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
Wenn eine Einstellung in mehreren Bereichen definiert ist, haben Arbeitsbereich-Einstellungen Priorität, dann folgt Remote [Codespaces] und darauf Benutzer.
|
||||
If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User.
|
||||
|
||||
Du kannst die Standardschnittstelleneinstellungen für {% data variables.product.prodname_vscode_shortname %} an zwei Orten festlegen.
|
||||
You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places.
|
||||
|
||||
* Die in der `.vscode/settings.json`-Datei deines Repositorys definierten Schnittstelleneinstellungen werden im Codespace als Arbeitsbereichseinstellungen angewendet.
|
||||
* Im `settings`-Schlüssel in der `devcontainer.json`-Datei definierte Schnittstelleneinstellungen werden im Codespace als Remote [Codespaces]-Einstellungen angewendet.
|
||||
* 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.
|
||||
|
||||
## Anwenden von Konfigurationsänderungen auf einen Codespace
|
||||
## Applying configuration changes to a codespace
|
||||
|
||||
Änderungen an einer Konfiguration werden angewendet, wenn du das nächste Mal einen Codespace erstellst. Wenn du jedoch einen Codespace in einem Webbrowser, in {% data variables.product.prodname_vscode_shortname %} oder in einer JetBrains-IDE verwendest, kannst du Konfigurationsänderungen auf den aktuellen Codespace anwenden, indem du den Container neu erstellst.
|
||||
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 %}.
|
||||
|
||||
### Neuerstellen des Entwicklungscontainers im Webclient oder in der Desktopanwendung von {% 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 %}
|
||||
|
||||
|
||||
|
||||
|
||||
- Klicke auf **Erstellungsprotokoll anzeigen**, um den Fehler durch das Überprüfen der Erstellungsprotokolle zu diagnostizieren.
|
||||
- Aktualisiere deine `devcontainer.json`-Datei, um die in den Protokollen identifizierten Fehler zu beheben.
|
||||
- Erstelle deinen Container neu, um die Änderungen anzuwenden.
|
||||
- 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.
|
||||
|
||||
### Neuerstellen des Entwicklungscontainers in einer JetBrains-IDE
|
||||
### Using {% data variables.product.prodname_cli %} to rebuild a dev container
|
||||
|
||||
{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
|
||||
1. Klicke im {% data variables.product.prodname_github_codespaces %}-Toolfenster auf das Symbol „Neu erstellen“.
|
||||
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. Klicke auf **Neu erstellen**, wenn du aufgefordert wirst, zu bestätigen, dass du den Entwicklungscontainer neu erstellen möchtest.
|
||||
1. Öffne den Codespace erneut in deiner 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>.
|
||||
|
||||
|
||||
## Weiterführende Themen
|
||||
## Further reading
|
||||
|
||||
- [Vordefinieren von Codespaces](/codespaces/prebuilding-your-codespaces)
|
||||
- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)"
|
||||
|
||||
@@ -8,12 +8,12 @@ type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Creation and deletion
|
||||
ms.openlocfilehash: 09c3a73ec5e41f0170f1d3cd66df139bb2a497e5
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 4a12c848fa7400ec336f5ad086eb4d2858a431f0
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158693'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180819'
|
||||
---
|
||||
## Erstellen von Codespaces
|
||||
|
||||
@@ -98,4 +98,4 @@ This codespace is currently running in recovery mode due to a container error.
|
||||
```
|
||||
Überprüfe die Erstellungsprotokolle, und aktualisiere nach Bedarf die Entwicklungscontainerkonfiguration. Weitere Informationen findest du unter „[{% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/github-codespaces-logs)“.
|
||||
|
||||
Anschließend kannst du versuchen, den Codespace neu zu starten oder den Container neu zu erstellen. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace).
|
||||
Anschließend kannst du versuchen, den Codespace neu zu starten oder den Container neu zu erstellen. Weitere Informationen zum Neuerstellen des Containers findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace).
|
||||
|
||||
@@ -1,123 +1,123 @@
|
||||
---
|
||||
title: Erste Schritte mit GitHub Copilot in einer JetBrains-IDE
|
||||
title: Getting started with GitHub Copilot in a JetBrains IDE
|
||||
shortTitle: JetBrains IDE
|
||||
intro: 'Erfahre, wie du {% data variables.product.prodname_copilot %} in einer JetBrains-IDE installierst, um beim Schreiben von Kommentaren und Code Vorschläge zu erhalten.'
|
||||
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: de-DE
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179596'
|
||||
---
|
||||
## Informationen zu {% data variables.product.prodname_copilot %} und JetBrains-IDEs
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and JetBrains IDEs
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
Wenn du die JetBrains-IDE verwendest, kannst du Vorschläge aus {% data variables.product.prodname_copilot %} direkt im Editor anzeigen und übernehmen. Diese Anleitung zeigt die Verwendung von {% data variables.product.prodname_copilot %} innerhalb einer JetBrains-IDE für macOS, Windows oder 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.
|
||||
|
||||
## Voraussetzungen
|
||||
## Prerequisites
|
||||
|
||||
{% data reusables.copilot.jetbrains-ides %}
|
||||
|
||||
## Installieren der {% data variables.product.prodname_copilot %}-Erweiterung in deiner JetBrains-IDE
|
||||
## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE
|
||||
|
||||
Um {% data variables.product.prodname_copilot %} in einer JetBrains-IDE zu verwenden, musst du das {% data variables.product.prodname_copilot %}-Plug-In installieren. Das folgende Verfahren führt dich durch die Installation des {% data variables.product.prodname_copilot %}-Plug-Ins in IntelliJ IDEA. Schritte zum Installieren des Plug-Ins in einer anderen unterstützten IDE können sich unterscheiden.
|
||||
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. Klicke in deiner JetBrains-IDE unter dem Menü **Datei** für Windows oder dem Namen deiner IDE für Mac (z. B. **PyCharm** oder **IntelliJ**) auf **Einstellungen** für Windows oder **Voreinstellungen** für Mac.
|
||||
2. Klicke im linken Menü des Dialogfelds **Einstellungen/Voreinstellungen** auf **Plug-Ins**.
|
||||
3. Klicke oben im Dialogfeld **Einstellungen/Voreinstellungen** auf **Marketplace**. Suche in der Suchleiste nach **{% data variables.product.prodname_copilot %}** , und klicke dann auf **Installieren**.
|
||||
|
||||
1. Klicke nach der Installation von {% data variables.product.prodname_copilot %} auf **IDE neu starten**.
|
||||
1. Klicke nach dem Neustart deiner JetBrains-IDE auf das Menü **Extras**. Klicke auf **{% data variables.product.prodname_copilot %}** und dann auf **Anmelden bei {% data variables.product.prodname_dotcom %}** .
|
||||
|
||||
1. Um den Gerätecode zu kopieren und das Geräteaktivierungsfenster zu öffnen, klicke im Dialogfeld „Anmelden bei {% data variables.product.prodname_dotcom %}“ auf **Kopieren und öffnen**.
|
||||
|
||||
1. Ein Geräteaktivierungsfenster wird in deinem Browser geöffnet. Füge den Gerätecode ein, und klicke dann auf **Weiter**.
|
||||
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**.
|
||||
|
||||
- Um den Code in Windows oder Linux einzufügen, drücke<kbd>STRG</kbd>+<kbd>V</kbd>.
|
||||
- Um den Code in macOS einzufügen, drücke <kbd>BEFEHLSTASTE</kbd>+<kbd>V</kbd>.
|
||||
1. {% data variables.product.prodname_dotcom %} fordert die notwendigen Berechtigungen für {% data variables.product.prodname_copilot %} an. Um diese Berechtigungen zu genehmigen, klicke auf **{% data variables.product.prodname_copilot %}-Plug-In autorisieren**.
|
||||
1. Nach Genehmigung der Berechtigungen zeigt deine JetBrains-IDE eine Bestätigung an. Klicke zum Verwenden von {% data variables.product.prodname_copilot %} auf **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**.
|
||||
|
||||
|
||||
|
||||
## Anzeigen deines ersten Vorschlags
|
||||
## Seeing your first suggestion
|
||||
|
||||
{% data reusables.copilot.code-examples-limitations %}
|
||||
|
||||
{% data reusables.copilot.supported-languages %} Die folgenden Beispiele sind in Java geschrieben, andere Sprachen funktionieren jedoch ähnlich.
|
||||
{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly.
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Erstelle in der Java-Datei eine Klasse durch Eingabe von `class Test`.
|
||||
{% data variables.product.prodname_copilot %} schlägt automatisch einen ganzen Klassentext in ausgegrautem Text vor, wie unten gezeigt. Der genaue Vorschlag kann variieren.
|
||||
 {% data reusables.copilot.accept-suggestion %}
|
||||
1. Um {% data variables.product.prodname_copilot %} aufzufordern, einen Funktionstext vorzuschlagen, gib die folgende Zeile unterhalb der Klammer der `main`-Funktion ein. Der genaue Vorschlag kann variieren.
|
||||
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 %} versucht, Kontext und Stil deines Codes zu treffen. Du kannst den vorgeschlagenen Code immer bearbeiten.
|
||||
{% data variables.product.prodname_copilot %} will attempt to match the context and style of your code. You can always edit the suggested code.
|
||||
|
||||
## Anzeigen alternativer Vorschläge
|
||||
## Seeing alternative suggestions
|
||||
|
||||
{% data reusables.copilot.alternative-suggestions %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Um {% data variables.product.prodname_copilot %} aufzufordern, einen Vorschlag anzuzeigen, gib die folgende Zeile in die Java-Datei ein.
|
||||
{% 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 | Nächsten Vorschlag anzeigen | Vorherigen Vorschlag anzeigen |
|
||||
| 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> |
|
||||
| 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 %}
|
||||
|
||||
## Anzeigen mehrerer Vorschläge auf einer neuen Registerkarte
|
||||
## Seeing multiple suggestions in a new tab
|
||||
|
||||
{% data reusables.copilot.suggestions-new-tab %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Um {% data variables.product.prodname_copilot %} aufzufordern, einen Vorschlag anzuzeigen, gib die folgende Zeile in die Java-Datei ein.
|
||||
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. Öffne eine neue Registerkarte mit mehreren zusätzlichen Vorschlägen.
|
||||
- Drücke unter macOS <kbd>Befehlstaste</kbd>+<kbd>Umschalttaste</kbd>+<kbd>A</kbd>, und klicke dann auf **GitHub Copilot öffnen**, oder drücke <kbd>Befehlstaste</kbd>+<kbd>Umschalttaste</kbd>+<kbd>\</kbd>, um die neue Registerkarte sofort zu öffnen.
|
||||
- Drücke unter Windows oder Linux <kbd>STRG</kbd>+<kbd>EINGABETASTE</kbd>, und klicke dann auf **GitHub Copilot öffnen**.
|
||||
|
||||
1. Um einen Vorschlag zu akzeptieren, klicke oberhalb des Vorschlags auf **Lösung annehmen**. Um alle Vorschläge abzulehnen, schließe die Registerkarte.
|
||||
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.
|
||||
|
||||
## Generieren von Codevorschlägen aus Kommentaren
|
||||
## Generating code suggestions from comments
|
||||
|
||||
{% data reusables.copilot.generating-suggestions-from-comments %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. Gib die folgenden Zeilen ein, um {% data variables.product.prodname_copilot %} aufzufordern, eine Implementierung einer Funktion in der Java-Datei vorzuschlagen.
|
||||
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 () {
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Aktivieren und Deaktivieren von {% data variables.product.prodname_copilot %}
|
||||
## Enabling and disabling {% data variables.product.prodname_copilot %}
|
||||
|
||||
Du kannst {% data variables.product.prodname_copilot %} für alle Sprachen oder einzelne Sprachen aktivieren oder deaktivieren. Das Statussymbol von {% data variables.product.prodname_copilot %} im unteren Bereich deines JetBrains-IDE-Fensters gibt an, ob {% data variables.product.prodname_copilot %} aktiviert oder deaktiviert ist. Falls aktiviert, ist das Symbol hervorgehoben. Falls deaktiviert, ist das Symbol abgeblendet.
|
||||
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. Um {% data variables.product.prodname_copilot %} zu aktivieren oder zu deaktivieren, klicke im unteren Panel des JetBrains-Fensters auf das Statussymbol.
|
||||
|
||||
2. Wenn du {% data variables.product.prodname_copilot %} deaktivierst, wirst du gefragt, ob du es global oder für die Sprache der aktuell bearbeiteten Datei deaktivieren möchtest.
|
||||
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.
|
||||
|
||||
- Um Vorschläge von {% data variables.product.prodname_copilot %} global zu deaktivieren, klicke auf **Vervollständigungen deaktivieren**.
|
||||
- Wenn du Vorschläge von {% data variables.product.prodname_copilot %} für die angegebene Sprache deaktivieren möchtest, klicke auf **Vervollständigungen für _SPRACHE_ deaktivieren**.
|
||||
|
||||
- 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_**.
|
||||
|
||||
|
||||
|
||||
## Weitere Informationsquellen
|
||||
## Further reading
|
||||
|
||||
- [Die {% data variables.product.prodname_copilot %}-Website](https://copilot.github.com/)
|
||||
- [Informationen zu {% 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: de-DE
|
||||
ms.lasthandoff: 11/16/2022
|
||||
ms.locfileid: '148167304'
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148183972'
|
||||
---
|
||||
|
||||
|
||||
@@ -10,12 +10,12 @@ redirect_from:
|
||||
type: overview
|
||||
topics:
|
||||
- Projects
|
||||
ms.openlocfilehash: 768234aa5e6c9cfbca6a6144a80ac2868f3316ce
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 3190379652fe1c95b8ea6ec7f864c44b72d9a7f7
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158861'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180761'
|
||||
---
|
||||
## Informationen zu {% data variables.product.prodname_projects_v2 %}
|
||||
|
||||
@@ -43,7 +43,7 @@ Du kannst benutzerdefinierte Felder verwenden, um deinen Issues, Pull Requests u
|
||||
|
||||
Du kannst Tasklisten verwenden, um Hierarchien von Issues zu erstellen, deine Probleme in kleinere Teilaufgaben aufzuteilen und neue Beziehungen zwischen deinen Issues zu erstellen. Weitere Informationen findest du unter „[Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/about-tasklists)“.
|
||||
|
||||
Diese Beziehungen werden für das Problem sowie die Felder „Tracked-by“ und „Tracks“ in deinen Projekten angezeigt. Du kannst nach Issues filtern, die von einem anderen Problem nachverfolgt werden, und du kannst deine Tabellenansichten auch nach dem Feld „Tracked-by“ gruppieren, um alle übergeordneten Probleme mit einer Liste der Unteraufgaben anzuzeigen.
|
||||
Diese Beziehungen werden für das Issue sowie die nachverfolgungsbezogenen Felder in deinen Projekten angezeigt. Du kannst nach Issues filtern, die von einem anderen Problem nachverfolgt werden, und du kannst deine Tabellenansichten auch nach dem Feld „Nachverfolgt von“ gruppieren, um alle übergeordneten Probleme mit einer Liste der Unteraufgaben anzuzeigen.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Informationen zu den Feldern „Nachverfolgungen“ und „Nachverfolgt von“
|
||||
shortTitle: About Tracks and Tracked-by fields
|
||||
shortTitle: About Tracks and Tracked by fields
|
||||
intro: Du kannst die Teilaufgaben der Issues in deinen Projekten anzeigen.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -8,12 +8,12 @@ versions:
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
ms.openlocfilehash: 74cd26d20882a00ac8c7ac1d109cc6810286cec6
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 44c1fcf3ed4495b57a0f2dbe3e92076f0e815502
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159658'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180745'
|
||||
---
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
@@ -31,7 +31,7 @@ Um den Filter zu verwenden, ersetze `<OWNER>` durch den Repositorybesitzer, `<RE
|
||||
|
||||
### Aktivieren des Felds „Nachverfolgt von“
|
||||
|
||||
Du kannst das Feld „Nachverfolgt von“ aktivieren, um zu sehen, welche Issues ein Element in deinem Projekt nachverfolgen.
|
||||
Du kannst das Feld „Nachverfolgt von“ aktivieren, um zu sehen, welche Issues in deinem Projekt ein Element nachverfolgen.
|
||||
|
||||
1. Klicke in der Tabellenansicht im Feld ganz rechts auf {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||
|
||||
@@ -11,12 +11,12 @@ product: '{% data reusables.gated-features.historical-insights-for-projects %}'
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 89f93ace53547fccd69ffb7e6d7b666a6cb48991
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: 809d8492bb1ec7c8cd4eb051b1eaefb00d29097e
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108479'
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158573'
|
||||
---
|
||||
{% ifversion fpt %}
|
||||
|
||||
@@ -30,6 +30,8 @@ ms.locfileid: '148108479'
|
||||
|
||||
Du kannst Erkenntnisse für {% data variables.product.prodname_projects_v2 %} zum Anzeigen, Erstellen und Anpassen von Diagrammen verwenden, in denen die dem Projekt hinzugefügten Elemente als Quelldaten verwendet werden. Du kannst Filter auf das Standarddiagramm anwenden und auch eigene Diagramme erstellen. Wenn du ein Diagramm erstellst, legst du die Filter, den Diagrammtyp und die angezeigten Informationen fest. Das Diagramm steht allen Personen zur Verfügung, die das Projekt anzeigen können. Du kannst zwei Diagrammtypen generieren: aktuelle Diagramme und Verlaufsdiagramme.
|
||||
|
||||
Insights verfolgt Elemente nach, die du archiviert oder gelöscht hast.
|
||||
|
||||
### Informationen zu aktuellen Diagrammen
|
||||
|
||||
Du kannst aktuelle Diagramme erstellen, um deine Projektelemente zu visualisieren. Du kannst z. B. Diagramme erstellen, um anzuzeigen, wie viele Elemente jeder einzelnen Person zugewiesen werden, oder wie viele Issues jeder bevorstehenden Iteration zugewiesen werden.
|
||||
|
||||
@@ -6,12 +6,12 @@ versions:
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /early-access/issues/about-tasklists
|
||||
ms.openlocfilehash: e35065ae4de634bb7a2da815e0a860c7c0b92234
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 69cdde1bb071f963b1a2f58ef1227bc96ab9d869
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159709'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180785'
|
||||
---
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
@@ -27,21 +27,11 @@ Die Issues, die du deinen Aufgabenlisten hinzufügst, werden automatisch mit den
|
||||
|
||||
### Informationen zur Integration in {% data variables.projects.projects_v2 %}
|
||||
|
||||
Im Seitenbereich deines Projekts wird die Position eines Issues in der Hierarchie innerhalb eines Breadcrumb-Menüs angezeigt, sodass du durch die Issues in deinen Aufgabenlisten navigieren kannst. Du kannst auch die Felder „Nachverfolgungen“ und „Nachverfolgt von“ hinzufügen, um die Beziehungen zwischen deinen Issues schnell zu erkennen. Weitere Informationen zu den Feldern „Nachverfolgungen“ und „Nachverfolgt von“ findest du [hier](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields).
|
||||
Im Seitenbereich deines Projekts wird die Position eines Issues in der Hierarchie innerhalb eines Breadcrumb-Menüs angezeigt, sodass du durch die Issues in deinen Aufgabenlisten navigieren kannst. Du kannst auch die Felder „Nachverfolgungen“ und „Nachverfolgt von“ zu deinen Projektansichten hinzufügen, um die Beziehungen zwischen deinen Issues schnell zu erkennen. Weitere Informationen findest du unter [Informationen zu den Feldern „Nachverfolgungen“ und „Nachverfolgt von“](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields).
|
||||
|
||||
## Erstellen von Aufgabenlisten
|
||||
|
||||
Eine Aufgabenliste kann durch Klicken auf die Schaltfläche „Aufgabenliste hinzufügen“ oder durch Bearbeiten des Markdown-Codes des Issues erstellt werden.
|
||||
|
||||
### Erstellen einer Aufgabenliste mithilfe der Schaltfläche „Aufgabenliste hinzufügen“
|
||||
|
||||
Klicke unten in einer Issuebeschreibung, die du bearbeiten kannst, auf die Schaltfläche **{% octicon "checklist" aria-label="The checklist icon" %} Aufgabenliste hinzufügen**, um eine Aufgabenliste hinzuzufügen.
|
||||
|
||||
|
||||
|
||||
### Erstellen einer Aufgabenliste mithilfe von Markdown
|
||||
|
||||
Du kannst Markdown in einer Issuebeschreibung verwenden, um eine Aufgabenliste zu erstellen. Erstelle einen Fenced-Code-Block, und schließe `[tasklist]` neben den öffnenden Graviszeichen ein. Stelle jedem Element `- [ ]` voran, und füge Links zu anderen Issues oder Text ein. Am Anfang deiner Liste kannst du optional einen Titel als Markdownheader einfügen.
|
||||
Du kannst eine Aufgabenliste mithilfe von Markdown in einer Issuebeschreibung verwenden. Erstelle einen Fenced-Code-Block, und schließe `[tasklist]` neben den öffnenden Graviszeichen ein. Anschließend kannst du jedem Element `- [ ]` voranstellen und Links zu anderen Issues oder Text einfügen. Am Anfang deiner Liste kannst du optional einen Titel als Markdownheader einfügen.
|
||||
|
||||
````
|
||||
```[tasklist]
|
||||
@@ -50,10 +40,11 @@ Du kannst Markdown in einer Issuebeschreibung verwenden, um eine Aufgabenliste z
|
||||
- [ ] Draft issue title
|
||||
```
|
||||
````
|
||||
|
||||
Dein Markdown-Code wird von {% data variables.product.product_name %} als Aufgabenliste gerendert. Anschließend kannst du über die Benutzeroberfläche Änderungen vornehmen sowie Issues hinzufügen und entwerfen. Wenn du die Issuebeschreibung bearbeitest, kannst du den Markdown-Code direkt ändern oder ihn kopieren, um die Aufgabenliste in anderen Issues zu duplizieren.
|
||||
|
||||
Du kannst auch auf der Formatierungssymbolleiste auf {% octicon "checklist" aria-label="The checklist icon" %} klicken, um beim Erstellen eines neuen Issues oder beim Bearbeiten einer Issuebeschreibung eine Aufgabenliste einzufügen.
|
||||
|
||||
|
||||
|
||||
## Hinzufügen von Issues zu einer Aufgabenliste
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -15,12 +15,12 @@ topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
shortTitle: Roles in an organization
|
||||
ms.openlocfilehash: c6c345e3d1f0fb2c49aa55e79346bc4ac6567885
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: f9e5d411c7a7a16e22abcc660f2761f1bfd6cf7d
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159173'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180077'
|
||||
---
|
||||
## Informationen zu Rollen
|
||||
{% data reusables.organizations.about-roles %}
|
||||
@@ -80,7 +80,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da
|
||||
{% ifversion fpt or ghec %}
|
||||
<!-- Free/Pro/Team and GHEC versions have extra columns for Moderators and Billing managers-->
|
||||
|
||||
| Organisationsberechtigung | Besitzer | Members | Moderatoren | Abrechnungsmanager | Sicherheitsmanager |
|
||||
| Organisationsberechtigung | Besitzer | Member | Moderatoren | Abrechnungsmanager | Sicherheitsmanager |
|
||||
|:------------------------|:------:|:-------:|:----------:|:----------------:|:-----------------:|
|
||||
| Erstellen von Repositorys (weitere Informationen findest du unter [Einschränken der Erstellung von Repositorys in deiner Organisation](/articles/restricting-repository-creation-in-your-organization)) | **X** | **X** | **X** | | **X** |
|
||||
| Abrechnungsinformationen anzeigen und bearbeiten | **X** | | | **X** | |
|
||||
@@ -121,7 +121,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da
|
||||
| Zuordnen deines Sponsorings zu einer anderen Organisation (weitere Informationen findest du unter [Zuordnen von Sponsorings zu deiner Organisation](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)) | **X** | | | | |
|
||||
| Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites aus Repositorys in der Organisation (weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für deine Organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)) | **X** | | | | |
|
||||
| Verwalten von Sicherheits- und Analyseeinstellungen (weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)) | **X** | | | | **X** |
|
||||
| Anzeigen der Sicherheitsübersicht für die Organisation (siehe [Informationen zu Sicherheitsübersichten](/code-security/security-overview/about-the-security-overview)) | **X** | | | | **X** |{% ifversion ghec %}
|
||||
| Anzeigen der Sicherheitsübersicht für die Organisation (Informationen unter [Informationen zur Sicherheitsübersicht](/code-security/security-overview/about-the-security-overview)) | **X** | | | | **X** |{% ifversion ghec %}
|
||||
| Aktivieren und Erzwingen der [einmaligen SAML-Anmeldung](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | |
|
||||
| [Verwalten des SAML-Benutzerzugriffs auf deine Organisation](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | |
|
||||
| Verwalten der SSH-Zertifizierungsstellen einer Organisation (weitere Informationen findest du unter [Verwalten der SSH-Zertifizierungsstellen deiner Organisation](/articles/managing-your-organizations-ssh-certificate-authorities)) | **X** | | | | |{% endif %}
|
||||
@@ -145,7 +145,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da
|
||||
{% elsif ghes or ghae %}
|
||||
<!-- GHES 3.3+ and eventual GHAE release don't have the extra columns for Moderators and Billing managers. -->
|
||||
|
||||
| Aktion in der Organisation | Besitzer | Members | Sicherheitsmanager |
|
||||
| Aktion in der Organisation | Besitzer | Member | Sicherheitsmanager |
|
||||
|:--------------------|:------:|:-------:|:-------:|
|
||||
| Personen zum Beitritt zur Organisation einladen | **X** | | |
|
||||
| Einladungen zum Beitritt zu der Organisation bearbeiten und zurückziehen | **X** | | |
|
||||
@@ -167,7 +167,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da
|
||||
| Kann die Rolle des *Maintainers für ein Team* zugewiesen werden | **X** | **X** | **X** |
|
||||
| Repositorys übertragen | **X** | | |
|
||||
| Verwalten von Sicherheits- und Analyseeinstellungen (weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)) | **X** | | **X** |{% ifversion ghes %}
|
||||
| Anzeigen der Sicherheitsübersicht für die Organisation (siehe [Informationen zu Sicherheitsübersichten](/code-security/security-overview/about-the-security-overview)) | **X** | | **X** |{% endif %}{% ifversion ghes %}
|
||||
| Anzeigen der Sicherheitsübersicht für die Organisation (Informationen unter [Informationen zur Sicherheitsübersicht](/code-security/security-overview/about-the-security-overview)) | **X** | | **X** |{% endif %}{% ifversion ghes %}
|
||||
| Verwalten von {% data variables.product.prodname_dependabot_security_updates %} (Informationen unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)) | **X** | | **X** |{% endif %}
|
||||
| Verwalten der SSH-Zertifizierungsstellen einer Organisation (weitere Informationen findest du unter [Verwalten der SSH-Zertifizierungsstellen deiner Organisation](/articles/managing-your-organizations-ssh-certificate-authorities)) | **X** | | |
|
||||
| Erstellen von Projektboards (Informationen unter [Berechtigungen für Projektboards einer Organisation](/articles/project-board-permissions-for-an-organization)) | **X** | **X** | **X** |
|
||||
@@ -186,12 +186,12 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da
|
||||
| [Exportieren einer Liste der Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | |
|
||||
| Verwalten von Standardbezeichnungen (weitere Informationen findest du unter [Verwalten von Standardbezeichnungen für Repositorys in deiner Organisation](/articles/managing-default-labels-for-repositories-in-your-organization)) | **X** | | |{% ifversion pull-request-approval-limit %}
|
||||
| Verwalten von Pull Request-Überprüfungen in der Organisation (weitere Informationen findest du unter [Verwalten von Pull Request-Überprüfungen in deiner Organisation](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)) | **X** | | | |{% endif %}
|
||||
{% ifversion ghae %}| Verwalten der Liste zugelassener IP-Adressen (weitere Informationen findest du unter [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen](/admin/configuration/restricting-network-traffic-to-your-enterprise)) | **X** | | |{% endif %}
|
||||
{% ifversion ghae %}| Verwalten von IP-Zulassungslisten (siehe [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)) | **X** | | |{% endif %}
|
||||
|
||||
{% else %}
|
||||
<!-- GHES and GHAE older versions don't have columns for Moderators, Billing managers or Security managers. -->
|
||||
|
||||
| Aktion in der Organisation | Besitzer | Members |
|
||||
| Aktion in der Organisation | Besitzer | Member |
|
||||
|:--------------------|:------:|:-------:|
|
||||
| Personen zum Beitritt zur Organisation einladen | **X** | |
|
||||
| Einladungen zum Beitritt zu der Organisation bearbeiten und zurückziehen | **X** | |
|
||||
@@ -227,11 +227,11 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da
|
||||
| [Anzeigen von Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository) | **X** | |
|
||||
| [Exportieren einer Liste der Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |
|
||||
| Verwalten von Standardbezeichnungen (weitere Informationen findest du unter [Verwalten von Standardbezeichnungen für Repositorys in deiner Organisation](/articles/managing-default-labels-for-repositories-in-your-organization)) | **X** | |
|
||||
{% ifversion ghae %}| Verwalten der Liste zugelassener IP-Adressen (weitere Informationen findest du unter [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen](/admin/configuration/restricting-network-traffic-to-your-enterprise)) | **X** | |{% endif %}
|
||||
{% ifversion ghae %}| Verwalten von IP-Zulassungslisten (siehe [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)) | **X** | |{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Weiterführende Themen
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
|
||||
- [Projektboardberechtigungen für eine Organisation](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)
|
||||
|
||||
@@ -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: Schnellstartanleitung für GitHub Packages
|
||||
intro: 'Veröffentlichen auf {% data variables.product.prodname_registry %} mit {% 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: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '147878955'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Einführung
|
||||
## Introduction
|
||||
|
||||
In diesem Leitfaden erstellst du einen {% data variables.product.prodname_actions %}-Workflow, um deinen Code zu testen und dann in {% data variables.product.prodname_registry %} zu veröffentlichen.
|
||||
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 %}.
|
||||
|
||||
## Veröffentlichen deines Pakets
|
||||
## Publishing your package
|
||||
|
||||
1. Erstelle ein neues Repository für {% data variables.product.prodname_dotcom %}, indem du `.gitignore` für Node hinzufügst. Weitere Informationen findest du unter [Erstellen eines neuen Repositorys](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository).
|
||||
2. Klone das Repository auf deinen lokalen Computer.
|
||||
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. Erstelle eine `index.js` Datei, und füge eine einfache Benachrichtigung hinzu, um „Hallo Welt!“ zu sagen.
|
||||
3. Create an `index.js` file and add a basic alert to say "Hello world!"
|
||||
{% raw %}
|
||||
```javascript{:copy}
|
||||
console.log("Hello, World!");
|
||||
```
|
||||
{% endraw %}
|
||||
4. Initialisiere ein npm-Paket mit `npm init`. Gib dein Paket im Paketinitialisierungs-Assistenten mit dem Namen _`@YOUR-USERNAME/YOUR-REPOSITORY`_ ein, und lege das Testskript auf `exit 0` fest. Dadurch wird eine `package.json`-Datei mit Informationen zu deinem Paket generiert.
|
||||
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. Führe `npm install` aus, um die `package-lock.json`-Datei zu generieren. Committe deine Änderungen und pushe sie dann in {% 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. Erstelle das Verzeichnis `.github/workflows`. Erstelle in diesem Verzeichnis eine Datei namens `release-package.yml`.
|
||||
7. Kopiere den folgenden YAML-Inhalt in die `release-package.yml`-Datei{% ifversion ghes or ghae %}, wobei du `YOUR-HOSTNAME` durch den Namen deines Unternehmens{% endif %} ersetzt.
|
||||
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 @@ In diesem Leitfaden erstellst du einen {% data variables.product.prodname_action
|
||||
- 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 @@ In diesem Leitfaden erstellst du einen {% data variables.product.prodname_action
|
||||
- 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. Teile NPM mit, in welchem Bereich und welcher Registrierung Pakete mit einer der folgenden Methoden veröffentlicht werden sollen:
|
||||
- Füge eine NPM-Konfigurationsdatei für das Repository hinzu, indem du eine `.npmrc`-Datei im Stammverzeichnis mit folgendem Inhalt erstellst: {% 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 %}
|
||||
- Bearbeite die `package.json`-Datei, und gib den `publishConfig`-Schlüssel an: {% 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. Committe deine Änderungen und pushe sie in {% 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. Der von dir erstellte Workflow wird ausgeführt, wenn ein neues Release im Repository erstellt wird. Wenn die Tests bestanden werden, wird das Paket in {% data variables.product.prodname_registry %}veröffentlicht.
|
||||
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 %}.
|
||||
|
||||
Um dies zu testen, navigiere zur Registerkarte **Code** in deinem Repository, und erstelle ein neues Release. Weitere Informationen findest du unter „[Verwalten von Releases in einem Repository](/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)."
|
||||
|
||||
## Anzeigen eines veröffentlichten Pakets
|
||||
## Viewing your published package
|
||||
|
||||
Du kannst alle Pakete anzeigen, die du veröffentlicht hast.
|
||||
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 %}
|
||||
|
||||
## Installieren eines veröffentlichten Pakets
|
||||
## Installing a published package
|
||||
|
||||
Nachdem du das Paket veröffentlicht hast, solltest du es als projektübergreifende Abhängigkeit verwenden. Weitere Informationen findest du unter „[Arbeiten mit der npm-Registrierung](/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)."
|
||||
|
||||
## Nächste Schritte
|
||||
## Next steps
|
||||
|
||||
Der Basisworkflow, den du gerade hinzugefügt hast, wird jedes Mal ausgeführt, wenn ein neues Release in deinem Repository erstellt wird. Dies ist jedoch längst nicht alles, was du mit {% data variables.product.prodname_registry %} tun kannst. Du kannst dein Paket mit einem einzelnen Workflow in mehreren Registrierungen veröffentlichen, den Workflow auslösen, um ihn bei verschiedenen Ereignissen wie einer zusammengeführten Pullanforderung auszuführen, Container verwalten usw.
|
||||
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.
|
||||
|
||||
Durch Kombination von {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %} kannst du nahezu jeden Aspekt deiner Anwendungsentwicklungsprozesse automatisieren. Wollen Sie loslegen? Hier sind einige hilfreiche Ressourcen zum Ausführen der nächsten Schritte mit {% data variables.product.prodname_registry %} und {% 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 %}:
|
||||
|
||||
- „[Informationen zu {% data variables.product.prodname_registry %}](/packages/learn-github-packages)“ – ausführliches Tutorial zu GitHub Packages
|
||||
- „[Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)“ – ausführliches Tutorial zu GitHub Actions
|
||||
- „[Arbeiten mit einer {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)“ – spezifische Anwendungsfälle und Beispiele
|
||||
- "[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: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145131445'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181302'
|
||||
---
|
||||
## Informationen zur Gist-API
|
||||
|
||||
@@ -38,7 +38,7 @@ Außerdem wird nicht nur der Inhalt einer bestimmten Datei abgeschnitten, sonder
|
||||
|
||||
Dies sind die unterstützten Medientypen zum Abrufen von Gist-Inhalten.
|
||||
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.VERSION.base64
|
||||
application/vnd.github.raw
|
||||
application/vnd.github.base64
|
||||
|
||||
Weitere Informationen findest du unter [Medientypen](/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: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147060618'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181245'
|
||||
---
|
||||
## Informationen zur Git-Blob-API
|
||||
|
||||
Ein Git-Blob (Binary Large Object) ist der Objekttyp, der zum Speichern des Inhalts jeder Datei in einem Repository verwendet wird. Der SHA-1-Hash der Datei wird berechnet und im Blobobjekt gespeichert. Diese Endpunkte ermöglichen dir das Lesen und Schreiben von [Blobobjekten](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) in deine Git-Datenbank auf {% data variables.product.product_name %}. Blobs nutzen [diese benutzerdefinierten Medientypen](#custom-media-types-for-blobs). Weitere Informationen zur Verwendung von Medientypen in der API findest du [hier](/rest/overview/media-types).
|
||||
Ein Git-Blob (Binary Large Object) ist der Objekttyp, der zum Speichern des Inhalts jeder Datei in einem Repository verwendet wird. Der SHA-1-Hash der Datei wird berechnet und im Blobobjekt gespeichert. Diese Endpunkte ermöglichen dir das Lesen und Schreiben von [Blobobjekten](https://git-scm.com/book/en/v2/Git-Internals-Git-Objects) in deine Git-Datenbank auf {% data variables.product.product_name %}. Blobs nutzen [diese benutzerdefinierten Medientypen](#custom-media-types-for-blobs). Weitere Informationen zur Verwendung von Medientypen in der API findest du [hier](/rest/overview/media-types).
|
||||
|
||||
### Benutzerdefinierte Medientypen für Blobs
|
||||
|
||||
Dies sind die unterstützten Medientypen für Blobs.
|
||||
|
||||
application/json
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.raw
|
||||
|
||||
Weitere Informationen findest du unter [Medientypen](/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.
|
||||
intro: 'Die Gitignore-API ruft `.gitignore`-Vorlagen ab, mit denen Dateien und Verzeichnisse ignoriert werden können.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -11,16 +11,21 @@ topics:
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /rest/reference/gitignore
|
||||
ms.openlocfilehash: e830b0f00d60f3eb121fa2a99a910b073780700e
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181268'
|
||||
---
|
||||
## Informationen zur Gitignore-API
|
||||
|
||||
## About the Gitignore API
|
||||
Wenn du ein neues Repository in {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} über die API erstellst, kannst du eine [GITIGNORE-Vorlage](/github/getting-started-with-github/ignoring-files) festlegen, die beim Erstellen auf das Repository angewendet werden soll. Die API für GITIGNORE-Vorlagen listet Vorlagen aus dem [.gitignore-Repository](https://github.com/github/gitignore) auf {% data variables.product.product_name %} auf und ruft diese ab.
|
||||
|
||||
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).
|
||||
### Benutzerdefinierte Medientypen für GITIGNORE-Vorlagen
|
||||
|
||||
### Custom media types for gitignore
|
||||
|
||||
You can use this custom media type when getting a gitignore template.
|
||||
Du kannst diesen benutzerdefinierten Medientyp beim Abrufen einer GITIGNORE-Vorlage verwenden.
|
||||
|
||||
application/vnd.github.raw
|
||||
|
||||
For more information, see "[Media types](/rest/overview/media-types)."
|
||||
Weitere Informationen findest du unter [Medientypen](/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: de-DE
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147673638'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184399'
|
||||
---
|
||||
|
||||
|
||||
@@ -4,12 +4,12 @@ intro: 'Dein {% data variables.product.pat_v2 %} kann Anforderungen an die folge
|
||||
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: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107237'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184221'
|
||||
---
|
||||
## Aktionen
|
||||
|
||||
@@ -37,28 +37,6 @@ ms.locfileid: '148107237'
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
|
||||
## Apps
|
||||
|
||||
- [`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: '148107237'
|
||||
- [`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 (Überprüfungen)
|
||||
## 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überprüfung
|
||||
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
- [`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)
|
||||
|
||||
## Migrationen
|
||||
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
- [`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)
|
||||
|
||||
## Seiten
|
||||
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
- [`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: '148107237'
|
||||
|
||||
## Geheimnisüberprüfung
|
||||
|
||||
- [`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: '148107237'
|
||||
- [`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: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145109175'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184233'
|
||||
---
|
||||
|
||||
|
||||
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: Pull-Request-Review-Kommentare
|
||||
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: de-DE
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181291'
|
||||
---
|
||||
## Informationen zur API für Pull Request-Review-Kommentare
|
||||
|
||||
## 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)."
|
||||
Pull Request-Review-Kommentare sind Kommentare zu einem Teil des vereinheitlichten Formats, der während einer Pull Request-Review vorgenommen wurde. Commit- und Issue-Kommentare unterscheiden sich von Pull Request-Review-Kommentaren. Du wendest Commit-Kommentare direkt auf einen Commit an und du wendest Issue-Kommentare an, ohne auf einen Teil des vereinheitlichten Formats zu verweisen. Weitere Informationen findest du unter [Erstellen eines Commit-Kommentars](/rest/reference/commits#create-a-commit-comment) und [Erstellen eines Issue-Kommentars](/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: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145109100'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181299'
|
||||
---
|
||||
## Informationen zur Pull Request-API
|
||||
|
||||
@@ -26,12 +26,12 @@ Jeder Pull Request ist ein Issue, aber nicht jedes Issue ist ein Pull Request. A
|
||||
|
||||
Die folgenden Medientypen werden für Pull Requests unterstützt.
|
||||
|
||||
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
|
||||
|
||||
Weitere Informationen findest du unter [Benutzerdefinierte Medientypen](/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: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145109096'
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: '148184056'
|
||||
---
|
||||
## Informationen zur API für Pull Request-Reviews
|
||||
|
||||
Bei Pull Request-Reviews handelt es sich um Gruppen von Pull Request-Reviewkommentaren zu einem Pull Request, die mit einem Status und einem optionalen Textkommentar gruppiert werden.
|
||||
|
||||
{% 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: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147060330'
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181298'
|
||||
---
|
||||
## Informationen zur Repositoryinhalts-API
|
||||
|
||||
@@ -26,8 +26,8 @@ Um das Roh-oder gerenderte HTML-Format (sofern unterstützt) anzufordern, verwen
|
||||
|
||||
[READMEs](/rest/reference/repos#get-a-repository-readme), [Dateien](/rest/reference/repos#get-repository-content) und [Symlinks](/rest/reference/repos#get-repository-content) unterstützen die folgenden benutzerdefinierten Medientypen:
|
||||
|
||||
application/vnd.github.VERSION.raw
|
||||
application/vnd.github.VERSION.html
|
||||
application/vnd.github.raw
|
||||
application/vnd.github.html
|
||||
|
||||
Verwende den Medientyp `.raw`, um den Inhalt der Datei abzurufen.
|
||||
|
||||
@@ -35,7 +35,7 @@ Bei Markupdateien wie Markdown oder AsciiDoc kannst du den gerenderten HTML-Code
|
||||
|
||||
[Alle Objekte](/rest/reference/repos#get-repository-content) unterstützen den folgenden benutzerdefinierten Medientyp:
|
||||
|
||||
application/vnd.github.VERSION.object
|
||||
application/vnd.github.object
|
||||
|
||||
Verwende den Medientypparameter `object`, um den Inhalt unabhängig vom Inhaltstyp in einem einheitlichen Objektformat abzurufen. Anstelle eines Arrays von Objekten für ein Verzeichnis ist die Antwort beispielsweise ein Objekt mit einem `entries`-Attribut mit dem Array von Objekten.
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: a0c8b24bacdd41e32d9b8bdd0d8850e7a6ada557
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: a9f12214edcef8a107ad9c447fea7207cfdc48f4
|
||||
ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "145103971"
|
||||
ms.lasthandoff: 11/28/2022
|
||||
ms.locfileid: "148184090"
|
||||
---
|
||||
Wenn ein gleichzeitiger Auftrag oder ein Workflow in die Warteschlange gestellt wird, wenn ein anderer Auftrag oder Workflow, der dieselbe Übereinstimmungsgruppe im Repository verwendet, in Bearbeitung ist, wird `pending` der Warteschlangeauftrag oder der Workflow ausgeführt. Alle zuvor anhängigen Aufträge oder Workflows in der Parallelitätsgruppe werden abgebrochen. Du kannst auch mit `cancel-in-progress: true` alle derzeit ausgeführten Aufträge oder Workflows in derselben Parallelitätsgruppe abbrechen.
|
||||
|
||||
@@ -26,7 +26,7 @@ concurrency: ci-${{ github.ref }}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.ref }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
@@ -38,7 +38,7 @@ Wenn du den Gruppennamen mit einer Eigenschaft erstellst, die nur für bestimmte
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.head_ref || github.run_id }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
@@ -53,7 +53,7 @@ Um nur die Ausführung desselben Workflows abzubrechen, kannst du die `github.wo
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
concurrency:
|
||||
concurrency:
|
||||
group: ${{ github.workflow }}-${{ github.ref }}
|
||||
cancel-in-progress: true
|
||||
```
|
||||
|
||||
@@ -1,11 +1,16 @@
|
||||
{% ifversion ghae %}
|
||||
To allow your self-hosted runners to communicate with {% data variables.product.prodname_dotcom %}, add the IP address or IP address range of your self-hosted runners to the IP allow list. For more information, see "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
|
||||
{% else %}
|
||||
{% warning %}
|
||||
---
|
||||
ms.openlocfilehash: 16f0a067759f387d360529b7c79b30558bf5f220
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180124"
|
||||
---
|
||||
{% ifversion ghae %} Damit Deine selbstgehosteten Runner mit {% data variables.product.prodname_dotcom %} kommunizieren können, füge die IP-Adresse oder den IP-Adressenbereich Deiner selbstgehosteten Runner zur IP-Zulassungsliste hinzu. Weitere Informationen findest Du „[Hinzufügen einer zulässigen IP-Adresse](#adding-an-allowed-ip-address)“.
|
||||
{% else %} {% warning %}
|
||||
|
||||
**Warning**: If you use an IP allow list and would also like to use {% data variables.product.prodname_actions %}, you must use self-hosted runners{% ifversion actions-hosted-runners %} or {% data variables.product.prodname_dotcom %}-hosted larger runners with a static IP address range{% endif %}. For more information, see "[Hosting your own runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)" {% ifversion actions-hosted-runners %} or "[Using larger runners](/actions/using-github-hosted-runners/using-larger-runners)"{% endif %}.
|
||||
**Warnung:** Wenn du eine Liste zugelassener IP-Adressen verwendest und auch {% data variables.product.prodname_actions %} verwenden möchtest, musst du selbstgehostete Runner{% ifversion actions-hosted-runners %} oder in {% data variables.product.prodname_dotcom %} gehostete größere Runner mit einem statischen IP-Adressbereich{% endif %} verwenden. Weitere Informationen findest du unter [Hosten deiner eigenen Runner](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners) {% ifversion actions-hosted-runners %} oder [Verwenden größerer Runner](/actions/using-github-hosted-runners/using-larger-runners).{% endif %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
To allow your self-hosted {% ifversion actions-hosted-runners %}or larger hosted{% endif %} runners to communicate with {% data variables.product.prodname_dotcom %}, add the IP address or IP address range of your runners to the IP allow list that you have configured for your enterprise.
|
||||
{% endif %}
|
||||
Damit deine selbstgehosteten{% ifversion actions-hosted-runners %} oder größeren gehosteten{% endif %} Runnern mit {% data variables.product.prodname_dotcom %} kommunizieren können, fügst du die IP-Adresse oder den IP-Adressbereich deiner Runner in der Liste zugelassener IP-Adressen hinzu, die du für dein Unternehmen konfiguriert hast. {% endif %}
|
||||
|
||||
@@ -1,9 +1,17 @@
|
||||
---
|
||||
ms.openlocfilehash: b40c432907d00f7bf7cf33a1f379ea3318ae8aa2
|
||||
ms.sourcegitcommit: cb39c15ab6ccfacf49f4b114b77e3b920fdddf70
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180669"
|
||||
---
|
||||
<table style="width:100%">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:35%"><b>Runner image</b></th>
|
||||
<th style="width:25%"><b>YAML workflow label</b></th>
|
||||
<th style="width:40%"><b>Notes</b></th>
|
||||
<th style="width:35%"><b>Runner-Image</b></th>
|
||||
<th style="width:25%"><b>YAML-Workflow-Kennzeichnung</b></th>
|
||||
<th style="width:40%"><b>Hinweise</b></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@@ -12,10 +20,10 @@
|
||||
Windows Server 2022
|
||||
</td>
|
||||
<td>
|
||||
<code>windows-latest</code> or <code>windows-2022</code>
|
||||
<code>windows-latest</code> oder <code>windows-2022</code>
|
||||
</td>
|
||||
<td>
|
||||
The <code>windows-latest</code> label currently uses the Windows Server 2022 runner image.
|
||||
Die <code>windows-latest</code>-Bezeichnung verwendet derzeit das Windows Server 2022-Runner-Image.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -43,21 +51,21 @@ Ubuntu 22.04
|
||||
Ubuntu 20.04
|
||||
</td>
|
||||
<td>
|
||||
<code>ubuntu-latest</code> or <code>ubuntu-20.04</code>
|
||||
<code>ubuntu-latest</code> oder <code>ubuntu-20.04</code>
|
||||
</td>
|
||||
<td>
|
||||
The <code>ubuntu-latest</code> label is currently transitioning to the Ubuntu 22.04 runner image. During the transition, the label might refer to the runner image for either Ubuntu 20.04 or 22.04. For more information, see <a href="https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/">this {% data variables.product.prodname_dotcom %} blog post</a>.
|
||||
Die Bezeichnung <code>ubuntu-latest</code> wird derzeit auf das Ubuntu 22.04-Runnerimage umgestellt. Während des Übergangs kann die Bezeichnung auf das Runnerimage für Ubuntu 20.04 oder 22.04 verweisen. Weitere Informationen findest du in <a href="https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/">diesem {% data variables.product.prodname_dotcom %}-Blogbeitrag</a>.
|
||||
</rd>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
Ubuntu 18.04 <sup>[deprecated]</sup>
|
||||
Ubuntu 18.04 <sup>[veraltet]</sup>
|
||||
</td>
|
||||
<td>
|
||||
<code>ubuntu-18.04</code>
|
||||
</td>
|
||||
<td>
|
||||
Migrate to <code>ubuntu-20.04</code> or <code>ubuntu-22.04</code>. For more information, see <A href="https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/">this GitHub blog post</A>.
|
||||
Migriere zu <code>ubuntu-20.04</code> oder <code>ubuntu-22.04</code>. Weitere Informationen findest du in diesem <A href="https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/">Blogbeitrag auf GitHub</A>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -73,21 +81,21 @@ macOS Monterey 12
|
||||
macOS Big Sur 11
|
||||
</td>
|
||||
<td>
|
||||
<code>macos-latest</code> or <code>macos-11</code>
|
||||
<code>macos-latest</code> oder <code>macos-11</code>
|
||||
</td>
|
||||
<td>
|
||||
The <code>macos-latest</code> label is currently transitioning to the macOS Monterey 12 runner image. During the transition, the label might refer to the runner image for either macOS 11 or 12. For more information, see <a href="https://github.blog/changelog/2022-10-03-github-actions-jobs-running-on-macos-latest-are-now-running-on-macos-12/">this {% data variables.product.prodname_dotcom %} blog post</a>.
|
||||
Die Bezeichnung <code>macos-latest</code> wird derzeit auf das macOS Monterey 12-Runnerimage umgestellt. Während des Übergangs kann die Bezeichnung auf das Runnerimage für macOS 11 oder 12 verweisen. Weitere Informationen findest du in <a href="https://github.blog/changelog/2022-10-03-github-actions-jobs-running-on-macos-latest-are-now-running-on-macos-12/">diesem {% data variables.product.prodname_dotcom %}-Blogbeitrag</a>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
macOS Catalina 10.15 <sup>[deprecated]</sup>
|
||||
macOS Catalina 10.15 <sup>[veraltet]</sup>
|
||||
</td>
|
||||
<td>
|
||||
<code>macos-10.15</code>
|
||||
</td>
|
||||
<td>
|
||||
Migrate to <code>macOS-11</code> or <code>macOS-12</code>. For more information, see <A href="https://github.blog/changelog/2022-07-20-github-actions-the-macos-10-15-actions-runner-image-is-being-deprecated-and-will-be-removed-by-8-30-22/">this GitHub blog post</A>.
|
||||
Migriere zu <code>macOS-11</code> oder <code>macOS-12</code>. Weitere Informationen findest du in diesem <A href="https://github.blog/changelog/2022-07-20-github-actions-the-macos-10-15-actions-runner-image-is-being-deprecated-and-will-be-removed-by-8-30-22/">Blogbeitrag auf GitHub</A>.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@@ -95,12 +103,12 @@ Migrate to <code>macOS-11</code> or <code>macOS-12</code>. For more information,
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** The `-latest` runner images are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor.
|
||||
**Hinweis:** Die `-latest`-Runner-Images sind die neuesten stabilen Images, die {% data variables.product.prodname_dotcom %} bereitstellt, und entsprechen möglicherweise nicht der neuesten Version des Betriebssystems, die beim Betriebssystemanbieter erhältlich ist.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support.
|
||||
**Warnung:** Beta- und veraltete Images werden „wie gesehen“, „mit allen Mängeln“ und „wie verfügbar“ bereitgestellt und sind von der Vereinbarung zum Servicelevel und der Garantie ausgeschlossen. Beta-Images werden möglicherweise nicht vom Kundendienst abgedeckt.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -1,116 +1,192 @@
|
||||
---
|
||||
ms.openlocfilehash: e0bf1f4b7bbd5fcb145a6e869dd442fd8e53108a
|
||||
ms.sourcegitcommit: b4996daba2e75b3368f39316e6929602f13b961b
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/31/2022
|
||||
ms.locfileid: "148120534"
|
||||
---
|
||||
| Kategoriename | BESCHREIBUNG
|
||||
| Category name | Description
|
||||
|------------------|-------------------
|
||||
{%- ifversion fpt or ghec %} | `account` | Enthält Aktivitäten im Zusammenhang mit einem Organisationskonto.
|
||||
| `advisory_credit` | Enthält Aktivitäten im Zusammenhang mit Angaben dazu, von welchen Mitwirkenden Inhalte für Sicherheitsempfehlungen in der {% data variables.product.prodname_advisory_database %} stammen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dotcom %}-Sicherheitshinweisen](/github/managing-security-vulnerabilities/about-github-security-advisories).
|
||||
{%- endif %} | `artifact` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_actions %}-Artefakten für Workflowausführungen.
|
||||
{%- ifversion audit-log-streaming %} | `audit_log_streaming` | Enthält Aktivitäten im Zusammenhang mit Streamingüberwachungsprotokollen für Organisationen in einem Unternehmenskonto.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `billing` | Enthält Aktivitäten im Zusammenhang mit der Abrechnung einer Organisation.
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | Enthält Aktivitäten im Zusammenhang mit Geschäftseinstellungen für ein Unternehmen.
|
||||
{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_advanced_security` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_GH_advanced_security %} in einem Unternehmen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise).
|
||||
| `business_secret_scanning` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_secret_scanning %} in einem Unternehmen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/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` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur {% data variables.product.prodname_secret_scanning %} in einem Unternehmen.
|
||||
{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_secret_scanning_push_protection` | Enthält Aktivitäten im Zusammenhang mit dem Pushschutzfeature von {% data variables.product.prodname_secret_scanning %} in einem Unternehmen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/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`| Enthält Aktivitäten im Zusammenhang mit der benutzerdefinierten Nachricht, die angezeigt wird, wenn der Pushschutz in einem Unternehmen ausgelöst wird. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise).
|
||||
{%- endif %} | `checks` | Enthält Aktivitäten im Zusammenhang mit Überprüfungssammlungen und -ausführungen.
|
||||
{%- ifversion fpt or ghec %} | `codespaces` | Enthält Aktivitäten im Zusammenhang mit den Codespaces einer Organisation.
|
||||
{%- endif %} | `commit_comment` | Enthält Aktivitäten im Zusammenhang mit dem Aktualisieren oder Löschen von Commitkommentaren.
|
||||
{%- ifversion ghes %} | `config_entry` | Enthält Aktivitäten im Zusammenhang mit Konfigurationseinstellungen. Diese Ereignisse sind nur im Überwachungsprotokoll des Websiteadministrators sichtbar.
|
||||
{%- endif %} | `dependabot_alerts` | Umfasst Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_alerts %} in vorhandenen Repositorys Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
|
||||
| `dependabot_alerts_new_repos` | Enthält Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_alerts %} in neuen Repositorys, die in der Organisation erstellt wurden.
|
||||
| `dependabot_repository_access` | Enthält Aktivitäten im Zusammenhang mit den privaten Repositorys in einer Organisation, auf die {% data variables.product.prodname_dependabot %} zugreifen darf.
|
||||
{%- ifversion fpt or ghec or ghes %} | `dependabot_security_updates` | Enthält Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_security_updates %} in vorhandenen Repositorys. Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates).
|
||||
| `dependabot_security_updates_new_repos` | Enthält Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_security_updates %} für neue Repositorys, die in der Organisation erstellt wurden.
|
||||
{%- endif %} | `dependency_graph` | Enthält Konfigurationsaktivitäten auf Organisationsebene für Abhängigkeitsdiagramme für Repositorys. Weitere Informationen findest du unter [Informationen zum Abhängigkeitsdiagramm](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph).
|
||||
| `dependency_graph_new_repos` | Enthält Konfigurationsaktivitäten auf Organisationsebene für neue Repositorys, die in der Organisation erstellt wurden.
|
||||
{%- ifversion fpt or ghec %} | `discussion` | Enthält Aktivitäten im Zusammenhang mit Teamdiskussionen.
|
||||
| `discussion_comment` | Enthält Aktivitäten im Zusammenhang mit Kommentaren, die in Diskussionen auf einer Teamseite veröffentlicht wurden.
|
||||
| `discussion_post` | Enthält Aktivitäten im Zusammenhang mit Diskussionen, die auf einer Teamseite veröffentlicht wurden.
|
||||
| `discussion_post_reply` | Enthält Aktivitäten im Zusammenhang mit Antworten auf Diskussionen, die auf einer Teamseite veröffentlicht wurden.
|
||||
{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_github_connect %}.
|
||||
| `enterprise` | Enthält Aktivitäten im Zusammenhang mit Unternehmenseinstellungen.
|
||||
{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | Enthält Aktivitäten im Zusammenhang mit überprüften Unternehmensdomänen.
|
||||
| `enterprise_installation` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_github_app %}s, die einer {% data variables.product.prodname_github_connect %}-Unternehmensverbindung zugeordnet sind.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `environment` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_actions %}-Umgebungen.
|
||||
{%- endif %} {%- ifversion ghae %} | `external_group` | Enthält Aktivitäten im Zusammenhang mit Okta-Gruppen.
|
||||
| `external_identity` | Enthält Aktivitäten im Zusammenhang mit einem Benutzer in einer Okta-Gruppe.
|
||||
{%- endif %} | `gist` | Enthält Aktivitäten im Zusammenhang mit Gists.
|
||||
| `hook` | Enthält Aktivitäten im Zusammenhang mit Webhooks.
|
||||
| `integration` | Enthält Aktivitäten im Zusammenhang mit Integrationen in einem Konto.
|
||||
| `integration_installation` | Enthält Aktivitäten im Zusammenhang mit Integrationen, die in einem Konto installiert sind.
|
||||
| `integration_installation_request` | Enthält Aktivitäten im Zusammenhang mit Anforderungen, die von Organisationsmitgliedern an Besitzer*innen gesendet werden, um Integrationen zur Verwendung innerhalb der Organisation genehmigen zu lassen.
|
||||
{%- ifversion ghec or ghae %} | `ip_allow_list` | Enthält Aktivitäten im Zusammenhang mit dem Aktivieren oder Deaktivieren der IP-Zulassungsliste für eine Organisation.
|
||||
| `ip_allow_list_entry` | Enthält Aktivitäten im Zusammenhang mit dem Erstellen, Löschen und Bearbeiten eines IP-Zulassungslisteneintrags für eine Organisation.
|
||||
{%- endif %} | `issue` | Enthält Aktivitäten im Zusammenhang mit dem Anheften, Übertragen oder Löschen eines Issues in einem Repository.
|
||||
| `issue_comment` | Enthält Aktivitäten im Zusammenhang mit dem Anheften, Übertragen oder Löschen von Issuekommentaren.
|
||||
| `issues` | Enthält Aktivitäten im Zusammenhang mit dem Aktivieren oder Deaktivieren der Issueerstellung für eine Organisation.
|
||||
{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | Enthält Aktivitäten im Zusammenhang mit der Unterzeichnung der {% data variables.product.prodname_marketplace %}-Entwicklervereinbarung.
|
||||
| `marketplace_listing` | Enthält Aktivitäten im Zusammenhang mit dem Auflisten von Apps in {% data variables.product.prodname_marketplace %}.
|
||||
{%- endif %} | `members_can_create_pages` | Enthält Aktivitäten zum Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für Repositorys in der Organisation. Weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für deine Organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization).
|
||||
| `members_can_create_private_pages` | Enthält Aktivitäten zum Verwalten der Veröffentlichung privater {% data variables.product.prodname_pages %}-Websites für Repositorys in der Organisation.
|
||||
| `members_can_create_public_pages` | Enthält Aktivitäten zum Verwalten der Veröffentlichung öffentlicher {% data variables.product.prodname_pages %}-Websites für Repositorys in der Organisation.
|
||||
{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | Enthält Aktivitäten im Zusammenhang mit der Aktivierung oder Deaktivierung der Repositoryerstellung für eine Organisation.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | Enthält Konfigurationsaktivitäten auf Organisationsebene, mit denen Organisationsmitglieder Abhängigkeitseinblicke anzeigen können.
|
||||
| `migration` | Enthält Aktivitäten zum Übertragen von Daten von einem *Quellspeicherort* (z. B. einer {% data variables.product.prodname_dotcom_the_website %}-Organisation oder einer {% data variables.product.prodname_ghe_server %}-Instanz) an eine {% data variables.product.prodname_ghe_server %}-*Zielinstanz*.
|
||||
{%- endif %} | `oauth_access` | Enthält Aktivitäten im Zusammenhang mit OAuth-Zugriffstoken.
|
||||
| `oauth_application` | Enthält Aktivitäten im Zusammenhang mit OAuth-Apps.
|
||||
{%- ifversion fpt or ghec %} | `oauth_authorization` | Enthält Aktivitäten im Zusammenhang mit der Autorisierung von OAuth-Apps.
|
||||
{%- endif %} | `org` | Enthält Aktivitäten im Zusammenhang mit der Organisationsmitgliedschaft.
|
||||
{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | Enthält Aktivitäten im Zusammenhang mit der Autorisierung von Anmeldeinformationen für die Verwendung mit SAML Single Sign-On.
|
||||
{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur Geheimnisüberprüfung in einer Organisation. Weitere Informationen findest du unter [Definieren benutzerdefinierter Muster für Geheimnisüberprüfungen](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning).
|
||||
| `org.secret_scanning_push_protection` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern für die Geheimnisüberprüfung in einer Organisation. Weitere Informationen findest du unter [Schützen von Pushs mit Geheimnisüberprüfung](/code-security/secret-scanning/protecting-pushes-with-secret-scanning).
|
||||
{%- endif %} | `organization_default_label` | Enthält Aktivitäten im Zusammenhang mit Standardbezeichnungen für Repositorys in einer Organisation.
|
||||
{%- ifversion fpt or ghec or ghes %} | `organization_domain` | Enthält Aktivitäten im Zusammenhang mit überprüften Organisationsdomänen.
|
||||
| `organization_projects_change` | Enthält Aktivitäten im Zusammenhang mit organisationsweiten Projektboards in einem Unternehmen.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | Enthält Aktivitäten im Zusammenhang mit überprüften benutzerdefinierten Domänen für {% data variables.product.prodname_pages %}.
|
||||
| `payment_method` | Enthält Aktivitäten im Zusammenhang mit der Zahlungsweise einer Organisation für {% data variables.product.prodname_dotcom %}.
|
||||
| `prebuild_configuration` | Enthält Aktivitäten im Zusammenhang mit Prebuildkonfigurationen für {% data variables.product.prodname_github_codespaces %}.
|
||||
{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` | Enthält Aktivitäten im Zusammenhang mit Pre-Receive-Hook-Umgebungen.
|
||||
| `pre_receive_hook` | Enthält Aktivitäten im Zusammenhang mit Pre-Receive-Hooks.
|
||||
{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | Enthält Aktivitäten im Zusammenhang mit der Aktivierung des privaten Modus für ein Unternehmen.
|
||||
{%- endif %} | `private_repository_forking` | Enthält Aktivitäten im Zusammenhang mit der Zulassung von Forks privater und interner Repositorys für ein Repository, eine Organisation oder ein Unternehmen.
|
||||
{%- ifversion fpt or ghec %} | `profile_picture` | Enthält Aktivitäten im Zusammenhang mit dem Profilbild einer Organisation.
|
||||
{%- endif %} | `project` | Enthält Aktivitäten im Zusammenhang mit Projektboards.
|
||||
| `project_field` | Enthält Aktivitäten im Zusammenhang mit der Felderstellung und -löschung in einem Projektboard.
|
||||
| `project_view` | Enthält Aktivitäten im Zusammenhang mit der Ansichtserstellung und -löschung in einem Projektboard.
|
||||
| `protected_branch` | Enthält Aktivitäten im Zusammenhang mit geschützten Branches.
|
||||
| `public_key` | Enthält Aktivitäten im Zusammenhang mit SSH-Schlüsseln und Bereitstellungsschlüsseln.
|
||||
| `pull_request` | Enthält Aktivitäten im Zusammenhang mit Pull Requests.
|
||||
| `pull_request_review` | Enthält Aktivitäten im Zusammenhang mit Pull Request-Überprüfungen.
|
||||
| `pull_request_review_comment` | Enthält Aktivitäten im Zusammenhang mit Pull Request-Überprüfungskommentaren.
|
||||
| `repo` | Enthält Aktivitäten im Zusammenhang mit den Repositorys, die einer Organisation gehören.
|
||||
{%- ifversion fpt or ghec %} | `repository_advisory` | Enthält Aktivitäten auf Repositoryebene im Zusammenhang mit Sicherheitshinweisen in der {% data variables.product.prodname_advisory_database %}. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dotcom %}-Sicherheitshinweisen](/github/managing-security-vulnerabilities/about-github-security-advisories).
|
||||
| `repository_content_analysis` | Enthält Aktivitäten im Zusammenhang mit der [Aktivierung oder Deaktivierung der Datenverwendung für ein privates Repository](/articles/about-github-s-use-of-your-data).
|
||||
| `repository_dependency_graph` | Enthält Aktivitäten auf Repositoryebene im Zusammenhang mit dem Aktivieren oder Deaktivieren des Abhängigkeitsdiagramms für ein {% ifversion fpt or ghec %}privates {% endif %}Repository. Weitere Informationen findest du unter [Informationen zum Abhängigkeitsdiagramm](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph).
|
||||
{%- endif %} | `repository_image` | Enthält Aktivitäten im Zusammenhang mit Bildern für ein Repository.
|
||||
| `repository_invitation` | Enthält Aktivitäten im Zusammenhang mit Einladungen zum Beitreten zu einem Repository.
|
||||
| `repository_projects_change` | Enthält Aktivitäten im Zusammenhang mit der Aktivierung von Projekten für ein Repository oder für alle Repositorys in einer Organisation.
|
||||
{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning` | Enthält Aktivitäten auf Repositoryebene im Zusammenhang mit der Geheimnisüberprüfung. Weitere Informationen findest du unter [Informationen zur Geheimnisüberprüfung](/github/administering-a-repository/about-secret-scanning).
|
||||
{%- endif %}{%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur Geheimnisüberprüfung in einem Repository. Weitere Informationen findest du unter [Definieren benutzerdefinierter Muster für Geheimnisüberprüfungen](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning). {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur Geheimnisüberprüfung in einem Repository. Weitere Informationen findest du unter [Schützen von Pushs mit Geheimnisüberprüfung](/code-security/secret-scanning/protecting-pushes-with-secret-scanning).
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Enthält Aktivitäten, mit denen Organisationsmitglieder die Sichtbarkeit von Repositorys für die Organisation ändern können.
|
||||
{%- endif %} | `repository_vulnerability_alert` | Enthält Aktivitäten im Zusammenhang mit [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
|
||||
{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | Enthält Konfigurationsaktivitäten auf Repositoryebene für {% data variables.product.prodname_dependabot_alerts %}.
|
||||
| `required_status_check` | Enthält Aktivitäten im Zusammenhang mit den erforderlichen Statusüberprüfungen für geschützte Branches.
|
||||
{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | Enthält Aktivitäten im Zusammenhang mit der Einschränkung von E-Mail-Benachrichtigungen an genehmigte oder überprüfte Domänen für ein Unternehmen.
|
||||
{%- endif %} {%- ifversion custom-repository-roles %} | `role` | Enthält Aktivitäten im Zusammenhang mit [benutzerdefinierten Repositoryrollen](/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` | Enthält Konfigurationsaktivitäten auf Organisationsebene zur Geheimnisüberprüfung in vorhandenen Repositorys. Weitere Informationen findest du unter [Informationen zur Geheimnisüberprüfung](/github/administering-a-repository/about-secret-scanning).
|
||||
| `secret_scanning_new_repos` | Enthält Konfigurationsaktivitäten auf Organisationsebene für die Geheimnisüberprüfung für neue Repositorys, die in der Organisation erstellt wurden.
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | Enthält Aktivitäten im Zusammenhang mit der Registrierung und Entfernung von Sicherheitsschlüsseln.
|
||||
{%- endif %} {%- ifversion fpt or ghec %} | `sponsors` | Enthält Ereignisse im Zusammenhang mit Sponsorschaltflächen (siehe [Anzeigen einer Sponsorschaltfläche in deinem Repository](/articles/displaying-a-sponsor-button-in-your-repository)).
|
||||
{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | Enthält Aktivitäten im Zusammenhang mit einer SSH-Zertifizierungsstelle in einer Organisation oder einem Unternehmen.
|
||||
| `ssh_certificate_requirement` | Enthält Aktivitäten, mit denen festgelegt wird, dass Mitglieder SSH-Zertifikate verwenden müssen, um auf Organisationsressourcen zuzugreifen.
|
||||
{%- endif %} | `staff` | Enthält Aktivitäten im Zusammenhang mit einem Websiteadministrator, der eine Aktion ausführt.
|
||||
| `team` | Enthält Aktivitäten im Zusammenhang mit Teams in einer Organisation.
|
||||
| `team_discussions` | Enthält Aktivitäten im Zusammenhang mit der Verwaltung von Teamdiskussionen für eine Organisation.
|
||||
{%- ifversion ghec %} | `team_sync_tenant` | Enthält Aktivitäten im Zusammenhang mit der Teamsynchronisierung mit einem IdP für ein Unternehmen oder eine Organisation.
|
||||
{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | Enthält Aktivitäten im Zusammenhang mit der zweistufigen Authentifizierung.
|
||||
{%- endif %} | `user` | Enthält Aktivitäten im Zusammenhang mit Benutzer*innen in einem Unternehmen oder einer Organisation.
|
||||
{%- ifversion ghec or ghes %} | `user_license` | Enthält Aktivitäten im Zusammenhang mit Benutzer*innen, die einen lizenzierten Arbeitsplatz in einem Unternehmen belegen, dessen Mitglied sie sind.
|
||||
{%- endif %} | `workflows` Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_actions %}-Workflows.
|
||||
{%- 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: de-DE
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: "148182306"
|
||||
---
|
||||
Bei kompilierten Sprachen wie Java,{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %}{% ifversion codeql-go-autobuild %} Go,{% endif %} C, C++ und C# analysiert {% data variables.product.prodname_codeql %} den gesamten Code, der während der Workflowausführung erstellt wurde. Um die Menge des zu analysierenden Codes zu begrenzen, kannst du durch die Angabe eigener Kompilierungsschritte in einem `run`-Block nur den Code kompilieren, den du analysieren möchtest. Durch die Angabe deiner eigenen Buildschritte mithilfe der Filter `paths` und `paths-ignore` für die Ereignisse `pull_request` und `push` kannst du die Schritte wie gewünscht kombinieren, um sicherzustellen, dass dein Workflow nur ausgeführt wird, wenn der bestimmte Code geändert wird. Weitere Informationen findest du unter [Workflowsyntax für {% 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)."
|
||||
Für Sprachen wie{% ifversion codeql-go-autobuild %}{% else %} Go,{% endif %} JavaScript, Python und TypeScript, die {% data variables.product.prodname_codeql %} ohne Kompilierung des Quellcodes analysiert, kannst du zusätzliche Konfigurationsoptionen angeben, um den Umfang des zu analysierenden Codes zu begrenzen. Weitere Informationen findest du unter [Angeben von zu überprüfenden Verzeichnissen](/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: de-DE
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: "148182274"
|
||||
---
|
||||
Wenn bei `autobuild` ein Fehler auftritt oder du andere Quelldateien als die durch den Prozess `autobuild` erstellten Dateien analysieren möchtest, musst du den Schritt `autobuild` aus dem Workflow entfernen und manuell Buildschritte hinzufügen. Für C/C++-, C#-, Go,{% ifversion codeql-kotlin-beta %} Kotlin- {% endif %} und Java-Projekte analysiert {% data variables.product.prodname_codeql %} den Quellcode, der von den von dir angegebenen Buildschritten erstellt wird.
|
||||
|
||||
|
||||
@@ -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: de-DE
|
||||
ms.lasthandoff: 11/25/2022
|
||||
ms.locfileid: "148182290"
|
||||
---
|
||||
Für die unterstützten kompilierten Sprachen kannst du den Code mithilfe der `autobuild`-Aktion im {% data variables.code-scanning.codeql_workflow %} erstellen. So wird vermieden, dass du explizite Buildbefehle für C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %}{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %} und Java angeben musst.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 17226308ffb5d7144dfe62d79f1f6cd3a1f63819
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180857"
|
||||
---
|
||||
1. Greife auf {% data variables.product.prodname_vscode_command_palette_shortname %} mit <kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac) oder <kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux) zu.
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 0083a6bd4cd85d02754b449ecccdfa22f52cc358
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180858"
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**Tipp:** Führe gelegentlich eine vollständige Neuerstellung durchführen, um deinen Cache zu löschen und deinen Container mit neuen Images neu zu erstellen. Weitere Informationen findest du unter [Durchführen einer vollständigen Neuerstellung eines Containers](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container).
|
||||
|
||||
{% endtip %}
|
||||
@@ -1,5 +1,13 @@
|
||||
1. Access the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
|
||||
---
|
||||
ms.openlocfilehash: 9a1e503111789036b99e1f31b9078bb28e4d57f8
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180839"
|
||||
---
|
||||
1. Greife auf die {% data variables.product.prodname_vscode_command_palette_shortname %} zu (<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac)/<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)), und beginne dann mit der Eingabe „rebuild“. Wähle **Codespaces: Container neu erstellen** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
{% indented_data_reference reusables.codespaces.full-rebuild-tip %}
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: cdfaf83aa2910a79f44435c6674a9b2ba53d9ec3
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 3d5f9723fc9c1778d8e98d24b3997710a468c12b
|
||||
ms.sourcegitcommit: aa67bb5ad7aa6804c5def4390e30adcc7cf96ea1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159665"
|
||||
ms.lasthandoff: 11/15/2022
|
||||
ms.locfileid: "148165193"
|
||||
---
|
||||
Verifizierte Schüler*innen und Studierende können {% data variables.product.prodname_github_codespaces %} bis zu einer festgelegten Nutzungsmenge pro Monat für persönliche Konten kostenlos nutzen. Die Speichermenge und Anzahl von Kernstunden, die von Schüler*innen und Studierenden pro Monat genutzt werden können, entspricht der jeweils bei {% data variables.product.prodname_pro %}-Konten enthaltenen Menge bzw. Anzahl. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces).
|
||||
Verifizierte Schüler und Studierende können {% data variables.product.prodname_github_codespaces %} bis zu 180 Kernstunden pro Monat für persönliche Konten kostenlos nutzen. Die Speichermenge und Anzahl von Kernstunden, die von Schüler*innen und Studierenden pro Monat genutzt werden können, entspricht der jeweils bei {% data variables.product.prodname_pro %}-Konten enthaltenen Menge bzw. Anzahl. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces).
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: ba5b61ae2e9f24ddaf725f419d6955c2165bdd07
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180128"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** Die Unterstützung von OpenID Connect (OIDC) und CAP (Richtlinie für bedingten Zugriff) für {% data variables.product.prodname_emus %} ist nur für Azure AD erhältlich.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,6 +1,14 @@
|
||||
1. After {% data variables.product.product_name %} redirects you to your IdP, sign in, then follow the instructions to give consent and install the {% data variables.product.prodname_emu_idp_oidc_application %} application. After Azure AD asks for permissions for {% data variables.product.company_short %} {% data variables.product.prodname_emus %} with OIDC, enable **Consent on behalf of your organization**, then click **Accept**.
|
||||
---
|
||||
ms.openlocfilehash: af0baef0abb9baffb7c9356f6f14aa9a0b9754f3
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180149"
|
||||
---
|
||||
1. Nachdem {% data variables.product.product_name %} dich zu deinem Identitätsanbieter umgeleitet hat, meldest du dich dort an und befolgst dann die Anweisungen, um deine Einwilligung zu erteilen und die {% data variables.product.prodname_emu_idp_oidc_application %}-Anwendung zu installieren. Wenn Azure AD die Berechtigungen für {% data variables.product.company_short %} {% data variables.product.prodname_emus %} mit OIDC anfordert, aktivierst du **Zustimmung im Namen Ihrer Organisation** und klickst dann auf **Annehmen**.
|
||||
{% warning %}
|
||||
|
||||
**Warning:** You must sign in to Azure AD as a user with global admin rights in order to consent to the installation of the {% data variables.product.prodname_emu_idp_oidc_application %} application.
|
||||
**Warnung:** Du musst dich bei Azure AD als Benutzer mit globalen Administratorrechten anmelden, um in die Installation der {% data variables.product.prodname_emu_idp_oidc_application %}-Anwendung einzuwilligen.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -1,5 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 699a28a2443778018ea25e0060e621da9427b4ef
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148179973"
|
||||
---
|
||||
{% warning %}
|
||||
|
||||
**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% ifversion ghes %}, even if the pull request is in a private repository, or if private mode is enabled. To prevent unauthorized access to the images, ensure that you restrict network access to the systems that serve the images, including {% data variables.location.product_location %}{% endif %}.{% ifversion ghae %} To prevent unauthorized access to image URLs on {% data variables.product.product_name %}, consider restricting network traffic to your enterprise. For more information, see "[Restricting network traffic to your enterprise with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)."{% endif %}
|
||||
**Warnung:** Wenn du einem Pull Request oder einem Kommentar zu einem Issue ein Bild als Anlage hinzufügst, kann jeder die anonymisierte Bild-URL ohne Authentifizierung anzeigen{% ifversion ghes %}, selbst wenn sich der Pull Request in einem privaten Repository befindet oder der private Modus aktiviert ist. Um den nicht autorisierten Zugriff auf die Bilder zu verhindern, stelle sicher, dass du den Netzwerkzugriff auf die Systeme beschränkst, die die Bilder bereitstellen, einschließlich {% data variables.location.product_location %}{% endif %}.{% ifversion ghae %} Um den nicht autorisierten Zugriff auf Bild-URLs auf {% data variables.product.product_name %} zu verhindern, solltest du den Netzwerkdatenverkehr an dein Unternehmen einschränken. Weitere Informationen findest du unter [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).{% endif %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
You can create an IP allow list by adding entries that each contain an IP address or address range. After you finish adding entries, you can check whether a particular IP address would be allowed by any of the enabled entries in your list.
|
||||
---
|
||||
ms.openlocfilehash: ba27097b12d25f6c6b9688f764e380eb2fc937b1
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180037"
|
||||
---
|
||||
Du kannst eine Liste zugelassener IP-Adressen erstellen, indem du Einträge hinzufügst, die jeweils eine IP-Adresse oder einen Adressbereich enthalten. Nachdem du Einträge hinzugefügt hast, kannst du überprüfen, ob eine bestimmte IP-Adresse durch einen der aktivierten Einträge in deiner Liste zugelassen wird.
|
||||
|
||||
Before the list restricts access to {% ifversion ghae %}your enterprise{% else %}private assets owned by organizations in your enterprise{% endif %}, you must also enable allowed IP addresses.
|
||||
Bevor die Liste den Zugriff auf {% ifversion ghae %}dein Unternehmen{% else %}private Ressourcen im Besitz von Organisationen in deinem Unternehmen{% endif %} beschränkt, musst du auch zulässige IP-Adressen aktivieren.
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
You can edit an entry in your IP allow list. If you edit an enabled entry, changes are enforced immediately.
|
||||
---
|
||||
ms.openlocfilehash: a6a2388e469c6283bbe0f9f7855044f45829584e
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180069"
|
||||
---
|
||||
Du kannst einen Eintrag in deiner IP-Zulassungsliste bearbeiten. Wenn du einen aktivierten Eintrag bearbeitest, werden die Änderungen sofort wirksam.
|
||||
|
||||
After you finish editing entries, you can check whether your allow list will permit a connection from a particular IP address after you enable the list.
|
||||
Nachdem du die Bearbeitung von Einträgen abgeschlossen hast, kannst du nach der Aktivierung der Liste überprüfen, ob deine Liste zugelassener IP-Adressen eine Verbindung von einer bestimmten IP-Adresse zulässt.
|
||||
@@ -1,3 +1,11 @@
|
||||
After you create an IP allow list, you can enable allowed IP addresses. When you enable allowed IP addresses, {% data variables.product.company_short %} immediately enforces any enabled entries in your IP allow list.
|
||||
---
|
||||
ms.openlocfilehash: a2310aaf4dbdde14b2a644c33f850731dd44ce46
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180085"
|
||||
---
|
||||
Nachdem du eine IP-Zulassungsliste erstellt hast, kannst du zulässige IP-Adressen aktivieren. Wenn du zulässige IP-Adressen aktivierst, erzwingt {% data variables.product.company_short %} sofort alle aktivierten Einträge in deiner IP-Zulassungsliste.
|
||||
|
||||
Before you enable your IP allow list, you can check whether your allow list will permit a connection from a particular IP address. For more information, see "[Checking if an IP address is permitted](#checking-if-an-ip-address-is-permitted)."
|
||||
Bevor du deine Liste zugelassener IP-Adressen aktivierst, kannst du überprüfen, ob deine Liste zugelassener IP-Adressen eine Verbindung von einer bestimmten IP-Adresse zulässt. Weitere Informationen findest du unter [Überprüfen, ob eine IP-Adresse zulässig ist](#checking-if-an-ip-address-is-permitted).
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: 5eaf0aa831a27f61216ae9574df61fe7445f2f94
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: 48ae9b37a06105b30d9d4bc5d50bc0795443417e
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: "148109617"
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180021"
|
||||
---
|
||||
1. Gib unter „IP-Adresse überprüfen“ eine IP-Adresse ein.
|
||||
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
To enforce the IP allow list, you must first add IP addresses to the list, then enable the IP allow list. After you complete your list, you can check whether a particular IP address would be allowed by any of the enabled entries in the list.
|
||||
---
|
||||
ms.openlocfilehash: bd068fb8f85d583d4fa5badb014a3fb5617199ad
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180150"
|
||||
---
|
||||
Um die IP-Zulassungsliste zu erzwingen, musst Du der Liste zuerst IP-Adressen hinzufügen und danach die IP-Zulassungsliste aktivieren. Nachdem du deine Liste fertiggestellt hast, kannst du überprüfen, ob eine bestimmte IP-Adresse durch einen der aktivierten Einträge in der Liste zugelassen wird.
|
||||
|
||||
You must add your current IP address, or a matching range, before you enable the IP allow list.
|
||||
Du musst Deine aktuelle IP-Adresse oder einen passenden Adressbereich hinzufügen, bevor Du die Liste der zulässigen IP-Adressen aktivierst.
|
||||
|
||||
@@ -1,11 +1,5 @@
|
||||
---
|
||||
ms.openlocfilehash: 5c02cf240a1d23e9549a534381d9914bd8dc0ebd
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145101599"
|
||||
---
|
||||
Wenn du die Positivliste aktivierst, werden die von dir konfigurierten IP-Adressen sofort zu den Positivlisten der Organisationen in deinem Unternehmen hinzugefügt. Wenn du die Positivliste deaktivierst, werden die Adressen aus den Positivlisten der Organisationen entfernt.
|
||||
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.
|
||||
|
||||
Du kannst festlegen, dass alle IP-Adressen, die für in deinem Unternehmen installierte {% data variables.product.prodname_github_apps %} konfiguriert sind, automatisch zu deiner Positivliste hinzugefügt werden. Die Person, die eine {% data variables.product.prodname_github_app %} erstellt, kann eine Positivliste für die Anwendung konfigurieren, die alle IP-Adressen angibt, an denen die Anwendung ausgeführt wird. Indem du deine Positivliste so konfigurierst, dass sie von dieser Positivliste erbt, vermeidest du, dass Verbindungsanforderungen von der Anwendung abgelehnt werden. Weitere Informationen findest du unter [Zulassen des Zugriffs durch 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,10 +1,8 @@
|
||||
---
|
||||
ms.openlocfilehash: 2f27cc8f89cfa028a5e07512c1528152a9bd4941
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "145107791"
|
||||
---
|
||||
1. Um optional von den Mitgliedern zu verlangen, SSH-Zertifikate zu verwenden, wähle **SSH-Zertifikate verlangen** aus, und klicke dann auf **Speichern**.
|
||||
|
||||
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,10 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: 989d63ee95229407cd3c3b05f5cfb41bd9038aee
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 23da81a1051f71cceb256e281271dc5eff03d7b2
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159621"
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180753"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
---
|
||||
ms.openlocfilehash: 0e58e5904bbff65341fbe4221fa03ea96e032c42
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: a45f36a89c0e8881fa181cc31f03a6a9cf034aa9
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "145090906"
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181288"
|
||||
---
|
||||
### Benutzerdefinierte Medientypen
|
||||
|
||||
Die folgenden Medientypen werden für diese API unterstützt:
|
||||
|
||||
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
|
||||
|
||||
Weitere Informationen zu Medientypen findest du unter [Benutzerdefinierte Medientypen](/rest/overview/media-types).
|
||||
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
ms.openlocfilehash: eb4b729cf490728306961ff3d2ef2835700c8735
|
||||
ms.sourcegitcommit: 80edcdbff4726de4d196584fcb603bca2efffd1f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181807"
|
||||
---
|
||||
Diese Tabelle zeigt das Verhalten von Warnungen für die einzelnen Methoden, mit denen ein Benutzer einen Pushschutzblock umgehen kann.
|
||||
|
||||
| Grund der Umgehung | Warnungsverhalten |
|
||||
|-----------------------|------------------------------------------------------|
|
||||
| Wird in Tests verwendet. | {% data variables.product.prodname_dotcom %} erstellt eine geschlossene Warnung, die als „In Tests verwendet“ aufgelöst wurde. |
|
||||
| Ist ein falsch positives Ergebnis. | {% data variables.product.prodname_dotcom %} erstellt eine geschlossene Warnung, die als „False Positive“ aufgelöst wurde. |
|
||||
| Wird später behoben. | {% data variables.product.prodname_dotcom %} erstellt eine offene Warnung. |
|
||||
@@ -1,127 +1,135 @@
|
||||
Partner | Supported secret
|
||||
---
|
||||
ms.openlocfilehash: 59e78cbf492110a8949c27e867bf195ae5605307
|
||||
ms.sourcegitcommit: bddda0c0814770ee64e378692891931c618247ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: "148181763"
|
||||
---
|
||||
Partner | Unterstütztes Geheimnis
|
||||
--- | ---
|
||||
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
|
||||
Adafruit IO | Adafruit IO-Schlüssel
|
||||
Adobe | Adobe-Gerätetoken
|
||||
Adobe | Adobe-Diensttoken
|
||||
Adobe | Kurzlebiges Zugriffstoken für Adobe
|
||||
Adobe | JSON Web Token für Adobe
|
||||
Alibaba Cloud | Paar aus Zugriffsschlüssel-ID und -Geheimnis für Alibaba Cloud
|
||||
Amazon Web Services (AWS) | Paar aus Zugriffsschlüssel-ID und geheimem Zugriffsschlüssel für Amazon AWS
|
||||
Atlassian | API-Token für Atlassian
|
||||
Atlassian | JSON Web Token für Atlassian
|
||||
Azure | Anwendungsgeheimnis für Azure Active Directory
|
||||
Azure | Azure Batch-Schlüssel identifizierbar
|
||||
Azure | Azure CosmosDB-Schlüssel identifizierbar
|
||||
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
|
||||
Azure | Azure ML Studio-Webdienstschlüssel (klassisch)
|
||||
Azure | SAS-Token für Azure
|
||||
Azure | Azure Search-Administratorschlüssel
|
||||
Azure | Azure Search-Abfrageschlüssel
|
||||
Azure | Zertifikat für die Azure-Dienstverwaltung
|
||||
Azure | Azure SQL-Verbindungszeichenfolge
|
||||
Azure | Azure Storage-Kontoschlüssel
|
||||
Checkout.com | Geheimer Produktionsschlüssel für Checkout.com
|
||||
Checkout.com | Geheimer Testschlüssel für Checkout.com
|
||||
Chief | Chief Tools-Token
|
||||
Clojars | Bereitstellungstoken für Clojars
|
||||
CloudBees CodeShip | Anmeldeinformationen für CloudBees CodeShip
|
||||
Contributed Systems | Anmeldeinformation für Contributed Systems
|
||||
Databricks | Zugriffstoken für Databricks
|
||||
Datadog | API-Schlüssel für Datadog
|
||||
DevCycle | DevCycle-Client-API-Schlüssel
|
||||
DevCycle | DevCycle-Server-API-Schlüssel
|
||||
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
|
||||
DigitalOcean | OAuth-Token für DigitalOcean
|
||||
DigitalOcean | Aktualisierungstoken für DigitalOcean
|
||||
DigitalOcean | Systemtoken für DigitalOcean
|
||||
Discord | Token für Discord-Bot
|
||||
Doppler | Persönliches Token für Doppler
|
||||
Doppler | Diensttoken für Doppler
|
||||
Doppler | Token für Doppler CLI
|
||||
Doppler | SCIM-Token für Doppler
|
||||
Doppler | Überprüfungstoken für Doppler
|
||||
Dropbox | Zugriffstoken für Dropbox
|
||||
Dropbox | Kurzlebiges Zugriffstoken für Dropbox
|
||||
Dynatrace | Zugriffstoken für Dynatrace
|
||||
Dynatrace | Internes Token für 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
|
||||
Finicity | App-Schlüssel für Finicity
|
||||
Frame.io | JSON Web Token für Frame.io
|
||||
Frame.io| Entwicklertoken für Frame.io
|
||||
FullStory| API-Schlüssel für FullStory
|
||||
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
|
||||
GitHub | OAuth-Zugriffstoken für GitHub
|
||||
GitHub | Aktualisierungstoken für GitHub
|
||||
GitHub | Zugriffstoken für GitHub App-Installation
|
||||
GitHub | Privater SSH-Schlüssel für GitHub
|
||||
GoCardless | Zugriffstoken für GoCardless Live
|
||||
GoCardless | Zugriffstoken für GoCardless Sandbox
|
||||
Google Cloud | API-Schlüssel für Google
|
||||
Google Cloud | ID des privaten Schlüssels für Google Cloud
|
||||
Hashicorp Terraform | API-Token für Terraform Cloud/Enterprise
|
||||
Hubspot | API-Schlüssel für Hubspot
|
||||
Hubspot | Persönlicher Zugriffsschlüssel für Hubspot-API
|
||||
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
|
||||
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
|
||||
Ionic | Aktualisierungstoken für Ionic
|
||||
JD Cloud | Zugriffsschlüssel für JD Cloud
|
||||
Linear | API-Schlüssel für Linear
|
||||
Linear | OAuth-Zugriffstoken für Linear
|
||||
MailChimp | API-Schlüssel für Mailchimp
|
||||
MailChimp | API-Schlüssel für Mandrill
|
||||
Mailgun | API-Schlüssel für Mailgun
|
||||
MessageBird | API-Schlüssel für MessageBird
|
||||
Meta | Zugriffstoken für Facebook
|
||||
npm | Zugriffstoken für npm
|
||||
NuGet | API-Schlüssel für NuGet
|
||||
Octopus Deploy | API-Schlüssel für Octopus Deploy
|
||||
OpenAI | API-Schlüssel für OpenAI
|
||||
Palantir | JSON Web Token für Palantir
|
||||
PlanetScale | Kennwort für PlanetScale-Datenbank
|
||||
PlanetScale | OAuth-Token für PlanetScale
|
||||
PlanetScale | Diensttoken für PlanetScale
|
||||
Plivo | Authentifizierungs-ID und -token für Plivo
|
||||
postman | API-Schlüssel für Postman
|
||||
Prefect | API-Schlüssel für Prefect
|
||||
Prefect | Benutzer-API-Token für Prefect
|
||||
Proctorio | Consumerschlüssel für Proctorio
|
||||
Proctorio | Bindungsschlüssel für Proctorio
|
||||
Proctorio | Registrierungsschlüssel für Proctorio
|
||||
Proctorio | Geheimer Schlüssel für Proctorio
|
||||
Pulumi | Zugriffstoken für Pulumi
|
||||
PyPI | API-Token für PyPI
|
||||
Infodatei | API-Zugriffsschlüssel für ReadMe
|
||||
redirect.pizza | API-Token für redirect.pizza
|
||||
RubyGems | API-Schlüssel für RubyGems
|
||||
Samsara | API-Token für Samsara
|
||||
Samsara | OAuth-Zugriffstoken für Samsara
|
||||
SendGrid | SendGrid-API-Schlüssel
|
||||
Sendinblue | API-Schlüssel für Sendinblue
|
||||
Sendinblue | SMTP-Schlüssel für Sendinblue
|
||||
Shopify | Gemeinsam verwendetes Geheimnis für Shopify-App
|
||||
Shopify | Zugriffstoken für Shopify
|
||||
Shopify | Benutzerdefiniertes App-Zugriffstoken für Shopify
|
||||
Shopify | Privates App-Kennwort für Shopify
|
||||
Slack | API-Token für Slack
|
||||
Slack | Eingehende Webhook-URL für Slack
|
||||
Slack | Webhook-URL für Shopify-Workflow
|
||||
SSLMate | API-Schlüssel für SSLMate
|
||||
SSLMate | Clustergeheimnis für SSLMate
|
||||
Stripe | Geheimer Schlüssel für Stripe-Live-API
|
||||
Stripe | Geheimer API-Schlüssel (Test) für Stripe
|
||||
Stripe | Eingeschränkter API-Schlüssel (Live) für Stripe
|
||||
Stripe | Eingeschränkter API-Schlüssel (Test) für Stripe
|
||||
Supabase | Dienstschlüssel für Supabase
|
||||
Tencent Cloud | Geheimnis-ID für Tencent Cloud
|
||||
Tencent WeChat | API-App-ID für Tencent WeChat
|
||||
Twilio | Kontozeichenfolgenbezeichner für Twilio
|
||||
Twilio | API-Schlüssel für Twilio
|
||||
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
|
||||
Uniwise | API-Schlüssel für WISEflow
|
||||
Valour | Zugriffstoken für Valour
|
||||
Yandex | Yandex.Cloud-API-Schlüssel
|
||||
Yandex | Yandex.Cloud-IAM-Cookie
|
||||
Yandex | Yandex.Cloud-IAM-Token
|
||||
Yandex | Yandex.Dictionary-API-Schlüssel
|
||||
Yandex | Geheimnis für Yandex.Cloud-Zugriff
|
||||
Yandex | Yandex.Passport-OAuth-Token
|
||||
Zuplo | Consumer-API für Zuplo
|
||||
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: 251049400fe7254dd3be991c1612faaa05efeb96
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180140"
|
||||
---
|
||||
1. Optional kannst du zusätzliche 2FA-Methoden konfigurieren, um das Risiko einer Kontosperrung zu verringern. Weitere Informationen zum Konfigurieren der einzelnen zusätzlichen Methoden findest du unter [Konfigurieren der Zwei-Faktor-Authentifizierung mit GitHub Mobile](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) und [Konfigurieren der Zwei-Faktor-Authentifizierung mit einem Sicherheitsschlüssel](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key).
|
||||
|
||||
@@ -1,235 +1,267 @@
|
||||
meta:
|
||||
default_description: "Erste Schritte, Problembehandlung und optimale Nutzung von GitHub. Dokumentation für neue Benutzer, Entwickler, Administratoren und alle Produkte von 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: GitHub-Dokumentation
|
||||
github_docs: GitHub Docs
|
||||
contact: Contact
|
||||
notices:
|
||||
ghae_silent_launch: GitHub AE ist derzeit begrenzt freigegeben.
|
||||
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
|
||||
' ist derzeit als Release Candidate verfügbar. Weitere Informationen findest du unter <a href="/admin/overview/about-upgrades-to-new-releases">Informationen zu Upgrades auf neue Releases</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:
|
||||
"Wir veröffentlichen regelmäßig Aktualisierungen unserer Dokumentation, und die Übersetzung dieser Seite ist möglicherweise noch nicht abgeschlossen. Die aktuellsten Informationen findest du in der <a id=\"to-english-doc\" href=\"/en\">englischen Dokumentation</a>."
|
||||
early_access: "📣 Bitte <b>gib diese URL nicht öffentlich weiter</b>. Diese Seite enthält Inhalte über eine Funktion, auf die frühzeitig zugegriffen werden kann."
|
||||
release_notes_use_latest: "Bitte verwende das neueste Release, um die aktuellen Sicherheits- und Leistungsvorteile und Fehlerbehebungen zu erhalten."
|
||||
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: "📣 Dies ist nicht das <a href=\"#{{ latestPatch }}\">aktuelle Patchrelease</a> von Enterprise Server."
|
||||
ghes_release_notes_upgrade_release_only: "📣 Dies ist nicht das <a href=\"/enterprise-server@{{ latestRelease }}/admin/release-notes\">aktuelle Release</a> von Enterprise Server."
|
||||
ghes_release_notes_upgrade_patch_and_release: "📣 Dies ist nicht das <a href=\"#{{ latestPatch }}\">aktuelle Patchrelease</a> dieser Releasereihe und nicht das <a href=\"/enterprise-server@{{ latestRelease }}/admin/release-notes\">aktuelle Release</a> von Enterprise Server."
|
||||
sign_up_cta: Registrieren
|
||||
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: Wählen Sie eine Sprache
|
||||
product_picker_default_text: Alle Produkte
|
||||
version_picker_default_text: Version auswählen
|
||||
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 begann mit dem Rollout dieser Änderungen für Unternehmen am
|
||||
banner_text: GitHub began rolling these changes out to enterprises on
|
||||
search:
|
||||
need_help: Sie brauchen Hilfe?
|
||||
placeholder: GitHub-Dokumentation durchsuchen
|
||||
loading: Laden
|
||||
no_results: Keine Ergebnisse gefunden
|
||||
search_results_for: Ergebnisse suchen für
|
||||
no_content: Kein Inhalt
|
||||
matches_displayed: Angezeigte Übereinstimmungen
|
||||
search_error: "Beim Versuch, die Suche durchzuführen, ist ein Fehler aufgetreten."
|
||||
description: "Gib einen Suchbegriff ein, um ihn in der GitHub-Dokumentation zu finden."
|
||||
label: GitHub-Dokumentation durchsuchen
|
||||
results_found: "{n} Ergebnisse in {s} ms gefunden"
|
||||
results_page: "Dies ist Seite {page} von {pages}."
|
||||
nothing_found: Nichts gefunden 😿
|
||||
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: Nach Produkt erkunden
|
||||
explore_by_product: Explore by product
|
||||
version_picker: Version
|
||||
description: Hilfe zu jeder Phase deiner GitHub-Reise.
|
||||
description: Help for wherever you are on your GitHub journey.
|
||||
toc:
|
||||
getting_started: Erste Schritte
|
||||
popular: Beliebt
|
||||
guides: Anleitungen
|
||||
whats_new: Neues
|
||||
getting_started: Getting started
|
||||
popular: Popular
|
||||
guides: Guides
|
||||
whats_new: What's new
|
||||
videos: Videos
|
||||
all_changelogs: Alle Änderungsprotokollbeiträge
|
||||
all_changelogs: All changelog posts
|
||||
pages:
|
||||
article_version: 'Artikelversion'
|
||||
miniToc: Inhalt dieses Artikels
|
||||
contributor_callout: Dieser Artikel wurde bereitgestellt und wird gepflegt von
|
||||
all_enterprise_releases: Alle Enterprise Server-Releases
|
||||
about_versions: Informationen zu Versionen
|
||||
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: Hoppla!
|
||||
something_went_wrong: Offenbar ist ein Fehler aufgetreten.
|
||||
we_track_errors: "Diese Fehler werden automatisch nachverfolgt. Wenn das Problem jedoch fortbesteht, kannst du uns gerne kontaktieren."
|
||||
page_doesnt_exist: Diese Seite ist anscheinend nicht vorhanden.
|
||||
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: Benötigst du weitere Hilfe?
|
||||
contact_support: Support kontaktieren
|
||||
ask_community: GitHub-Community fragen
|
||||
still_need_help: Still need help?
|
||||
contact_support: Contact support
|
||||
ask_community: Ask the GitHub community
|
||||
survey:
|
||||
able_to_find: Hat dir diese Dokumentation geholfen?
|
||||
able_to_find: Did this doc help you?
|
||||
yes: Yes
|
||||
no: No
|
||||
comment_yes_label: "Teile uns mit, was wir gut machen"
|
||||
comment_no_label: "Teile uns mit, was wir besser machen können"
|
||||
comment_yes_label: Let us know what we do well
|
||||
comment_no_label: Let us know what we can do better
|
||||
optional: Optional
|
||||
required: Erforderlich
|
||||
email_placeholder: email@beispiel.com
|
||||
email_label: "Wenn wir dir weitere Fragen stellen dürfen, gib bitte deine E-Mail Adresse an"
|
||||
email_validation: Geben Sie eine gültige E-Mail-Adresse ein.
|
||||
required: Required
|
||||
email_placeholder: email@example.com
|
||||
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: Vielen Dank! Wir haben dein Feedback erhalten.
|
||||
not_support: "Wenn du eine Antwort brauchst, wende dich bitte stattdessen an den Support."
|
||||
privacy_policy: Datenschutzrichtlinie
|
||||
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: "Hilf uns, diese Dokumente perfekt zu machen!"
|
||||
body: Alle GitHub-Dokumente sind Open Source-Dokumente. Ist dir etwas Falsches oder Unklares aufgefallen? Bitte sende einen Pull Request.
|
||||
button: Leiste einen Beitrag
|
||||
or: Oder
|
||||
to_guidelines: "lerne, einen Beitrag zu leisten."
|
||||
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: Implementiert
|
||||
fields: Felder
|
||||
arguments: Argumente
|
||||
implements: Implements
|
||||
fields: Fields
|
||||
arguments: Arguments
|
||||
name: Name
|
||||
type: Typ
|
||||
description: BESCHREIBUNG
|
||||
input_fields: Eingabefelder
|
||||
return_fields: Rückgabefelder
|
||||
implemented_by: Implementiert von
|
||||
values: Werte
|
||||
possible_types: Mögliche Typen
|
||||
preview_notice: Vorschauhinweis
|
||||
deprecation_notice: Einstellungshinweis
|
||||
preview_period: Während der Vorschauzeit kann die API ohne Vorankündigung geändert werden.
|
||||
type: Type
|
||||
description: Description
|
||||
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: 'Um diese Vorschau zu wechseln und auf die folgenden Schemaelemente zuzugreifen, musst du im `Accept`-Header einen benutzerdefinierten Medientyp angeben:'
|
||||
preview_schema_members: 'Elemente des Vorschauschemas'
|
||||
announced: Angekündigt
|
||||
updates: Aktualisierungen
|
||||
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: Standard
|
||||
name: Name
|
||||
in: Geben Sie in
|
||||
type: type
|
||||
description: BESCHREIBUNG
|
||||
notes: Notizen
|
||||
parameters: Parameter
|
||||
response: Antwort
|
||||
example_response: Beispielantwort
|
||||
status_code: Statuscode
|
||||
http_status_code: HTTP-Antwortstatuscodes
|
||||
code_sample: Codebeispiel
|
||||
code_samples: Codebeispiele
|
||||
preview_notice: Vorschauhinweis
|
||||
preview_notices: Vorschauhinweise
|
||||
see_preview_notice: Siehe Vorschauhinweis
|
||||
see_preview_notices: Siehe Vorschauhinweise
|
||||
preview_header_is_required: Dieser Header ist <strong>erforderlich</strong>.
|
||||
preview_notice_to_change: Diese API befindet sich in der Vorschau und kann daher geändert werden.
|
||||
works_with: Funktioniert mit
|
||||
api_reference: REST-API-Referenz
|
||||
enum_description_title: Kann eine der Folgenden sein
|
||||
required: Erforderlich
|
||||
headers: Header
|
||||
query: Abfrageparameter
|
||||
path: Pfadparameter
|
||||
body: Textparameter
|
||||
in: In
|
||||
description: Description
|
||||
notes: Notes
|
||||
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: Alle Rechte vorbehalten
|
||||
terms: Begriffe
|
||||
privacy: Datenschutz
|
||||
security: Sicherheit
|
||||
all_rights_reserved: All rights reserved
|
||||
terms: Terms
|
||||
privacy: Privacy
|
||||
security: Security
|
||||
product:
|
||||
heading: Produkt
|
||||
heading: Product
|
||||
links:
|
||||
features: Features
|
||||
security: Sicherheit
|
||||
security: Security
|
||||
enterprise: Enterprise
|
||||
case_studies: Fallstudien
|
||||
pricing: Preise
|
||||
resources: Ressourcen
|
||||
case_studies: Case Studies
|
||||
pricing: Pricing
|
||||
resources: Resources
|
||||
platform:
|
||||
heading: Plattform
|
||||
heading: Platform
|
||||
links:
|
||||
developer_api: Entwickler-API
|
||||
partners: Partner
|
||||
developer_api: Developer API
|
||||
partners: Partners
|
||||
atom: Atom
|
||||
electron: Elektron
|
||||
electron: Electron
|
||||
github_desktop: GitHub Desktop
|
||||
support:
|
||||
heading: Support
|
||||
links:
|
||||
help: Hilfe
|
||||
community_forum: Communityforum
|
||||
help: Help
|
||||
community_forum: Community Forum
|
||||
training: Training
|
||||
status: Status
|
||||
contact_github: GitHub kontaktieren
|
||||
contact_github: Contact GitHub
|
||||
company:
|
||||
heading: Company
|
||||
links:
|
||||
about: Info
|
||||
about: About
|
||||
blog: Blog
|
||||
careers: Karriere
|
||||
press: Tastenkombination
|
||||
careers: Careers
|
||||
press: Press
|
||||
shop: Shop
|
||||
product_landing:
|
||||
quickstart: Schnellstart
|
||||
reference: Verweis
|
||||
overview: Übersicht
|
||||
guides: Anleitungen
|
||||
code_examples: Codebeispiele
|
||||
search_code_examples: Codebeispiele suchen
|
||||
search_results_for: Ergebnisse suchen für
|
||||
matches_displayed: Angezeigte Übereinstimmungen
|
||||
show_more: Mehr anzeigen
|
||||
explore_people_and_projects: Personen und Projekte erkunden
|
||||
sorry: Leider kein Ergebnis für
|
||||
no_example: "Offenbar haben wir kein Beispiel, das deinem Filter entspricht."
|
||||
try_another: "Probiere einen anderen Filter aus, oder füge dein Codebeispiel hinzu."
|
||||
no_result: Leider entspricht keine Anleitung deinem Filter.
|
||||
learn: "Hier erfährst du, wie du ein Codebeispiel hinzufügst."
|
||||
communities_using_discussions: Communitys auf GitHub.com mit Diskussionen
|
||||
add_your_community: Füge deine Community hinzu
|
||||
sponsor_community: GitHub Sponsors-Community
|
||||
supported_releases: Unterstützte Releases
|
||||
release_notes_for: Versionshinweise für
|
||||
upgrade_from: Upgrade von
|
||||
browse_all_docs: Gesamte Dokumentation durchsuchen
|
||||
browse_all: Alle durchsuchen
|
||||
docs: Dokumentation
|
||||
explore_release_notes: Versionshinweise erkunden
|
||||
view: Alle anzeigen
|
||||
quickstart: Quickstart
|
||||
reference: Reference
|
||||
overview: Overview
|
||||
guides: Guides
|
||||
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: Explore release notes
|
||||
view: View all
|
||||
product_guides:
|
||||
start_path: Lernpfad beginnen
|
||||
learning_paths: '{{ productMap[currentProduct].name }}-Lernpfade'
|
||||
learning_paths_desc: "Lernpfade sind eine Sammlung von Anleitungen, die dir helfen, ein bestimmtes Thema zu erlernen."
|
||||
guides: '{{ productMap[currentProduct].name }}-Anleitungen'
|
||||
more_guides: weitere Anleitungen
|
||||
load_more: Weitere Anleitungen laden
|
||||
all_guides: 'Alle {{ productMap[currentProduct].name }}-Anleitungen'
|
||||
filter_instructions: Filtere die Anleitungenliste mit diesen Steuerelementen
|
||||
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: Thema
|
||||
type: Type
|
||||
topic: Topic
|
||||
all: All
|
||||
guides_found:
|
||||
multiple: '{n} Anleitungen gefunden'
|
||||
one: 1 Anleitung gefunden
|
||||
none: Keine Anleitungen gefunden
|
||||
multiple: '{n} guides found'
|
||||
one: 1 guide found
|
||||
none: No guides found
|
||||
guide_types:
|
||||
overview: Übersicht
|
||||
quick_start: Schnellstart
|
||||
tutorial: Lernprogramm
|
||||
how_to: Schrittanleitung
|
||||
reference: Verweis
|
||||
overview: Overview
|
||||
quick_start: Quickstart
|
||||
tutorial: Tutorial
|
||||
how_to: How-to guide
|
||||
reference: Reference
|
||||
learning_track_nav:
|
||||
prevGuide: Vorherige Anleitung
|
||||
nextGuide: Nächste Anleitung
|
||||
prevGuide: Previous guide
|
||||
nextGuide: Next guide
|
||||
toggle_images:
|
||||
off: "Bilder sind ausgeschaltet, zum Anzeigen klicken"
|
||||
on: "Bilder sind eingeschaltet, zum Ausblenden klicken"
|
||||
hide_single: Bild ausblenden
|
||||
show_single: Bild anzeigen
|
||||
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: Bildlauf nach oben
|
||||
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'
|
||||
|
||||
@@ -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)"
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user