Merge branch 'main' into main
This commit is contained in:
Adam Ross Russell
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Adding labels to issues
|
||||
title: Hinzufügen von Bezeichnungen zu Issues
|
||||
shortTitle: Add labels to issues
|
||||
intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.'
|
||||
intro: 'Du kannst {% data variables.product.prodname_actions %} verwenden, um Issues automatisch zu bezeichnen.'
|
||||
redirect_from:
|
||||
- /actions/guides/adding-labels-to-issues
|
||||
versions:
|
||||
@@ -13,24 +13,28 @@ type: tutorial
|
||||
topics:
|
||||
- Workflows
|
||||
- Project management
|
||||
ms.openlocfilehash: a3523069b9422ecd8107007ca5e00fb0071dd738
|
||||
ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: '148185561'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
## Einführung
|
||||
|
||||
## Introduction
|
||||
In diesem Tutorial wird veranschaulicht, wie du die [`actions/github-script`-Aktion](https://github.com/marketplace/actions/github-script) in einem Workflow verwendest, um neue oder erneut geöffnete Issues zu bezeichnen. Beispielsweise kannst du jedes Mal die Bezeichnung `triage` hinzufügen, wenn ein Issue geöffnet oder erneut geöffnet wird. So kannst du alle Issues, die selektiert werden müssen, durch Filtern nach Issues mit der Bezeichnung `triage` anzeigen.
|
||||
|
||||
This tutorial demonstrates how to use the [`actions/github-script` action](https://github.com/marketplace/actions/github-script) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label.
|
||||
Mit der Aktion `actions/github-script` kannst du die {% data variables.product.prodname_dotcom %}-API problemlos in einem Workflow verwenden.
|
||||
|
||||
The `actions/github-script` action allows you to easily use the {% data variables.product.prodname_dotcom %} API in a workflow.
|
||||
In diesem Tutorial erstellst du zunächst eine Workflowdatei, die die [`actions/github-script`-Aktion](https://github.com/marketplace/actions/github-script) verwendet. Im Anschluss passt du den Workflow an deine Anforderungen an.
|
||||
|
||||
In the tutorial, you will first make a workflow file that uses the [`actions/github-script` action](https://github.com/marketplace/actions/github-script). Then, you will customize the workflow to suit your needs.
|
||||
|
||||
## Creating the workflow
|
||||
## Erstellen des Workflows
|
||||
|
||||
1. {% data reusables.actions.choose-repo %}
|
||||
2. {% data reusables.actions.make-workflow-file %}
|
||||
3. Copy the following YAML contents into your workflow file.
|
||||
3. Kopiere den folgenden YAML-Inhalt in deine Workflowdatei.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Label issues
|
||||
@@ -56,23 +60,23 @@ In the tutorial, you will first make a workflow file that uses the [`actions/git
|
||||
})
|
||||
```
|
||||
|
||||
4. Customize the `script` parameter in your workflow file:
|
||||
- The `issue_number`, `owner`, and `repo` values are automatically set using the `context` object. You do not need to change these.
|
||||
- Change the value for `labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `["help wanted", "good first issue"]`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
|
||||
4. Passe den `script`-Parameter in deiner Workflowdatei an:
|
||||
- Die Werte von `issue_number`, `owner`, und `repo` werden automatisch mithilfe des `context`-Objekts festgelegt. Du musst sie nicht ändern.
|
||||
- Ändere den Wert für `labels` in die Liste der Bezeichnungen, die du dem Issue hinzufügen möchtest. Trenne mehrere Bezeichnungen durch Kommas voneinander ab. Beispiel: `["help wanted", "good first issue"]`. Weitere Informationen zu Bezeichnungen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests).
|
||||
5. {% data reusables.actions.commit-workflow %}
|
||||
|
||||
## Testing the workflow
|
||||
## Testen des Workflows
|
||||
|
||||
Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue.
|
||||
Jedes Mal, wenn ein Issue im Repository geöffnet oder erneut geöffnet wird, fügt dieser Workflow die Bezeichnungen hinzu, die du für das Issue angegeben hast.
|
||||
|
||||
Test out your workflow by creating an issue in your repository.
|
||||
Teste deinen Workflow, indem du ein Issue in deinem Repository erstellst.
|
||||
|
||||
1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
|
||||
2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
|
||||
3. When the workflow completes, the issue that you created should have the specified labels added.
|
||||
1. Erstelle ein Issue in deinem Repository. Weitere Informationen findest du unter [Erstellen eines Issues](/github/managing-your-work-on-github/creating-an-issue).
|
||||
2. Um die Workflowausführung anzuzeigen, die durch das Erstellen des Issues ausgelöst wurde, rufe den Verlauf deiner Workflowausführungen auf. Weitere Informationen findest du unter [Aufrufen des Workflowausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
|
||||
3. Wenn der Workflow abgeschlossen ist, sollten dem erstellten Issue die angegebenen Bezeichnungen hinzugefügt worden sein.
|
||||
|
||||
## Next steps
|
||||
## Nächste Schritte
|
||||
|
||||
- To learn more about additional things you can do with the `actions/github-script` action, see the [`actions/github-script` action documentation](https://github.com/marketplace/actions/github-script).
|
||||
- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)."
|
||||
- [Search GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) for examples of workflows using this action.
|
||||
- Weitere Informationen zu weiteren Optionen für die Aktion `actions/github-script` findest du in der [Dokumentation zur Aktion `actions/github-script`](https://github.com/marketplace/actions/github-script).
|
||||
- Weitere Informationen zu verschiedenen Ereignissen, die deinen Workflow auslösen können, findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#issues).
|
||||
- [Durchsuche GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) nach Beispielen für Workflows, die diese Aktion verwenden.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Removing a label when a card is added to a project board column
|
||||
intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a {% data variables.projects.projects_v1_board %}.'
|
||||
title: 'Entfernen einer Bezeichnung, wenn eine Karte einer Projektboardspalte hinzugefügt wird'
|
||||
intro: 'Mithilfe von {% data variables.product.prodname_actions %} kannst du Bezeichnungen automatisch entfernen, wenn ein Issue oder ein Pull Request einer bestimmten Spalte auf einem {% data variables.projects.projects_v1_board %} hinzugefügt wird.'
|
||||
redirect_from:
|
||||
- /actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column
|
||||
versions:
|
||||
@@ -13,23 +13,27 @@ topics:
|
||||
- Workflows
|
||||
- Project management
|
||||
shortTitle: Remove label when adding card
|
||||
ms.openlocfilehash: d86d9e5ad198c9cf8811b47f2a6c8a7114e20104
|
||||
ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: '148185629'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
## Einführung
|
||||
|
||||
## Introduction
|
||||
In diesem Tutorial wird gezeigt, wie du die [`actions/github-script`-Aktion](https://github.com/marketplace/actions/github-script) zusammen mit einer Bedingung verwendest, um eine Bezeichnung von Issues und Pull Requests zu entfernen, die einer bestimmten Spalte auf einem {% data variables.projects.projects_v1_board %} hinzugefügt werden. Du kannst beispielsweise die Bezeichnung `needs review` entfernen, wenn Projektkarten in die Spalte `Done`verschoben werden.
|
||||
|
||||
This tutorial demonstrates how to use the [`actions/github-script` action](https://github.com/marketplace/actions/github-script) along with a conditional to remove a label from issues and pull requests that are added to a specific column on a {% data variables.projects.projects_v1_board %}. For example, you can remove the `needs review` label when project cards are moved into the `Done` column.
|
||||
In diesem Tutorial erstellst du zunächst eine Workflowdatei, die die [`actions/github-script`-Aktion](https://github.com/marketplace/actions/github-script) verwendet. Im Anschluss passt du den Workflow an deine Anforderungen an.
|
||||
|
||||
In the tutorial, you will first make a workflow file that uses the [`actions/github-script` action](https://github.com/marketplace/actions/github-script). Then, you will customize the workflow to suit your needs.
|
||||
|
||||
## Creating the workflow
|
||||
## Erstellen des Workflows
|
||||
|
||||
1. {% data reusables.actions.choose-repo %}
|
||||
2. Choose a {% data variables.projects.projects_v1_board %} that belongs to the repository. This workflow cannot be used with projects that belong to users or organizations. You can use an existing {% data variables.projects.projects_v1_board %}, or you can create a new {% data variables.projects.projects_v1_board %}. For more information about creating a project, see "[Creating a {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/creating-a-project-board)."
|
||||
2. Wählen ein {% data variables.projects.projects_v1_board %} aus, das zum Repository gehört. Dieser Workflow kann nicht mit Projekten verwendet werden, die Benutzer*innen oder Organisationen gehören. Du kannst ein vorhandenes {% data variables.projects.projects_v1_board %} verwenden oder ein neues {% data variables.projects.projects_v1_board %} erstellen. Weitere Informationen zum Erstellen eines Projekts findest du unter [Erstellen eines {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/creating-a-project-board).
|
||||
3. {% data reusables.actions.make-workflow-file %}
|
||||
4. Copy the following YAML contents into your workflow file.
|
||||
4. Kopiere den folgenden YAML-Inhalt in deine Workflowdatei.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Remove a label
|
||||
@@ -58,28 +62,28 @@ In the tutorial, you will first make a workflow file that uses the [`actions/git
|
||||
})
|
||||
```
|
||||
|
||||
5. Customize the parameters in your workflow file:
|
||||
- In `github.event.project_card.column_id == '12345678'`, replace `12345678` with the ID of the column where you want to un-label issues and pull requests that are moved there.
|
||||
5. Passe die Parameter in deiner Workflowdatei an:
|
||||
- Ersetze `12345678` in `github.event.project_card.column_id == '12345678'` durch die ID der Spalte, in der du Bezeichnungen von Issues und Pull Requests entfernen möchtest, die dorthin verschoben werden.
|
||||
|
||||
To find the column ID, navigate to your {% data variables.projects.projects_v1_board %}. Next to the title of the column, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} then click **Copy column link**. The column ID is the number at the end of the copied link. For example, `24687531` is the column ID for `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
|
||||
Navigiere zu deinem {% data variables.projects.projects_v1_board %}, um die Spalten-ID zu finden. Klicke neben dem Titel der Spalte auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und danach auf **Spaltenlink kopieren**. Bei der Zahl am Ende des kopierten Links handelt es sich um die Spalten-ID. Beispielsweise ist `24687531` die Spalten-ID für `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
|
||||
|
||||
If you want to act on more than one column, separate the conditions with `||`. For example, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` will act whenever a project card is added to column `12345678` or column `87654321`. The columns may be on different project boards.
|
||||
- Change the value for `name` in the `github.rest.issues.removeLabel()` function to the name of the label that you want to remove from issues or pull requests that are moved to the specified column(s). For more information on labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
|
||||
Wenn du mehr als eine Spalte bearbeiten möchtest, trenne die Bedingungen durch `||`. Zum Beispiel wird `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` immer ausgeführt, wenn eine Projektkarte zu Spalte `12345678` oder Spalte `87654321` hinzugefügt wird. Die Spalten können sich auf verschiedenen Projektboards befinden.
|
||||
- Ändere den Wert für `name` in der Funktion `github.rest.issues.removeLabel()` in den Namen der Bezeichnung, die du aus Issues oder Pull Requests entfernen möchtest, die in die angegebene(n) Spalte(n) verschoben werden. Weitere Informationen zu Bezeichnungen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests).
|
||||
6. {% data reusables.actions.commit-workflow %}
|
||||
|
||||
## Testing the workflow
|
||||
## Testen des Workflows
|
||||
|
||||
Every time a project card on a {% data variables.projects.projects_v1_board %} in your repository moves, this workflow will run. If the card is an issue or a pull request and is moved into the column that you specified, then the workflow will remove the specified label from the issue or a pull request. Cards that are notes will not be affected.
|
||||
Jedes Mal, wenn eine Projektkarte in einem {% data variables.projects.projects_v1_board %} in deinem Repository verschoben wird, wird dieser Workflow ausgeführt. Wenn die Karte ein Issue oder ein Pull Request ist und in die von dir angegebene Spalte verschoben wird, wird durch den Workflow die angegebene Bezeichnung entfernt. Karten, bei denen es sich um Notizen handelt, sind nicht betroffen.
|
||||
|
||||
Test your workflow out by moving an issue on your {% data variables.projects.projects_v1_board %} into the target column.
|
||||
Teste deinen Workflow, indem du ein Issue in deinem {% data variables.projects.projects_v1_board %} in die Zielspalte verschiebst.
|
||||
|
||||
1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
|
||||
2. Label the issue with the label that you want the workflow to remove. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
|
||||
3. Add the issue to the {% data variables.projects.projects_v1_board %} column that you specified in your workflow file. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)."
|
||||
4. To see the workflow run that was triggered by adding the issue to the project, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
|
||||
5. When the workflow completes, the issue that you added to the project column should have the specified label removed.
|
||||
1. Öffne ein Issue in deinem Repository. Weitere Informationen findest du unter [Erstellen eines Issues](/github/managing-your-work-on-github/creating-an-issue).
|
||||
2. Beschrifte das Issue mit den Bezeichnungen, die vom Workflow entfernt werden sollen. Weitere Informationen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests).
|
||||
3. Füge das Issue zu der Spalte des {% data variables.projects.projects_v1_board %} hinzu, die du in deiner Workflowdatei angegeben hast. Weitere Informationen findest du unter [Hinzufügen von Issues und Pull Requests zu einem {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board).
|
||||
4. Um die Workflowausführung anzuzeigen, die durch das Hinzufügen des Issues zum Projekt ausgelöst wurde, rufe den Verlauf deiner Workflowausführungen auf. Weitere Informationen findest du unter [Aufrufen des Workflow-Ausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
|
||||
5. Nachdem der Workflow ausgeführt wurde, sollte die angegebene Bezeichnung aus dem Issue entfernt worden sein, das du der Projektspalte hinzugefügt hast.
|
||||
|
||||
## Next steps
|
||||
## Nächste Schritte
|
||||
|
||||
- To learn more about additional things you can do with the `actions/github-script` action, see the [`actions/github-script` action documentation](https://github.com/marketplace/actions/github-script).
|
||||
- [Search GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) for examples of workflows using this action.
|
||||
- Informationen zu weiteren Optionen für die Aktion `actions/github-script` findest du in der [Dokumentation zur Aktion `actions/github-script`](https://github.com/marketplace/actions/github-script).
|
||||
- [Durchsuche GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) nach Beispielen für Workflows, die diese Aktion verwenden.
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
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.'
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,150 +17,192 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: b62ab2a143ed0e7ec57f7e7225a09c0ca713295c
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185043'
|
||||
---
|
||||
## 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 %}
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% 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.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% 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.
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
|
||||
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).
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% 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 %}
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
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.
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
|
||||
{% 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
|
||||
## About your IdP's allow list
|
||||
|
||||
Wenn du {% data variables.product.prodname_emus %} mit OIDC verwendest, kannst du die Liste zugelassener IP-Adressen deines Identitätsanbieters verwenden.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
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.
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
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.
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
|
||||
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).
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/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.
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
|
||||
## Verwenden der Liste zugelassener IP-Adressen von {% data variables.product.company_short %}
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
### 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**.
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
|
||||
Wähle **Liste zugelassener IP-Adressen aktivieren** aus.
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
|
||||
- Wenn du {% data variables.product.prodname_emus %} ohne OIDC verwendest, wählst du **Liste zugelassener IP-Adressen aktivieren** aus.
|
||||
|
||||
1. Klicke auf **Speichern**.
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Eine zugelassene IP-Adresse hinzufügen
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Eine zugelassene IP-Adresse bearbeiten
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% 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.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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Überprüfen der Zulässigkeit einer IP-Adresse
|
||||
### Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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
|
||||
### Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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
|
||||
## Using your identity provider's allow list
|
||||
|
||||
Du kannst die Liste zugelassener IP-Adressen deines Identitätsanbieters verwenden, wenn du {% data variables.product.prodname_emus %} mit OIDC verwendest.
|
||||
{% note %}
|
||||
|
||||
{% 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**.
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
|
||||
1. 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.
|
||||
{% endnote %}
|
||||
|
||||
|
||||
1. Klicke auf **Speichern**.
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Zugelassene IP-Adressen aktivieren
|
||||
## Enabling allowed IP addresses
|
||||
|
||||
{% 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**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## Eine zugelassene IP-Adresse hinzufügen
|
||||
## Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Eine zugelassene IP-Adresse bearbeiten
|
||||
## Editing an allowed IP address
|
||||
|
||||
{% 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.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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Überprüfen der Zulässigkeit einer IP-Adresse
|
||||
## Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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
|
||||
## Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About Server Statistics
|
||||
intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.'
|
||||
title: Informationen zu Serverstatistiken
|
||||
intro: 'Du kannst {% data variables.product.prodname_server_statistics %} verwenden, um deine eigenen aggregierten Daten von {% data variables.product.prodname_ghe_server %} zu analysieren, und uns helfen, {% data variables.product.company_short %}-Produkte zu verbessern.'
|
||||
versions:
|
||||
feature: server-statistics
|
||||
permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.'
|
||||
@@ -8,97 +8,102 @@ redirect_from:
|
||||
- /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics
|
||||
topics:
|
||||
- Enterprise
|
||||
ms.openlocfilehash: 3d17df54cd5dcf9ad102ab5079794a9bcb3e664b
|
||||
ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185185'
|
||||
---
|
||||
## Informationen zu den Vorteilen von {% data variables.product.prodname_server_statistics %}
|
||||
|
||||
## About the benefits of {% data variables.product.prodname_server_statistics %}
|
||||
{% data variables.product.prodname_server_statistics %} können dazu beitragen, die Bedürfnisse deiner Organisation zu antizipieren, die Arbeit deines Teams nachzuvollziehen und den Nutzen darzustellen, den du aus {% data variables.product.prodname_ghe_server %} ziehst.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
Nach der Aktivierung sammelt {% data variables.product.prodname_server_statistics %} aggregierte Daten zur Nutzung bestimmter Features auf deiner Instanz im Laufe der Zeit. Im Gegensatz zu anderen [API-Endpunkten für Administratorstatistiken](/rest/reference/enterprise-admin#admin-stats), die nur Daten für den letzten Tag zurückgeben, stellt {% data variables.product.prodname_server_statistics %} Verlaufsdaten für alle {% data variables.product.prodname_server_statistics %}-Metriken zur Verfügung, die seit der Aktivierung des Features gesammelt wurden. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_server_statistics %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise).
|
||||
|
||||
Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)."
|
||||
Wenn du {% data variables.product.prodname_server_statistics %} aktivierst, trägst du zur Verbesserung von {% data variables.product.prodname_dotcom %} bei. Durch die von dir bereitgestellten aggregierten Daten können wir Erkenntnisse dazu gewinnen, welchen Nutzen {% data variables.product.prodname_dotcom %} unseren Kunden bietet. Anhand dieser Informationen kann {% data variables.product.company_short %} bessere und fundiertere Produktentscheidungen treffen, von denen letztendlich auch du profitierst.
|
||||
|
||||
When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you.
|
||||
## Informationen zur Datensicherheit
|
||||
|
||||
## About data security
|
||||
Wir respektieren deine Daten. Wir geben keine Daten von {% data variables.location.product_location %} weiter, sofern du uns nicht ausdrücklich die Berechtigung dazu erteilt hast.
|
||||
|
||||
We respect your data. We will never transmit data from {% data variables.location.product_location %} unless you have first given us permission to do so.
|
||||
Wir sammeln keine personenbezogenen Daten. Wir sammeln auch keine {% data variables.product.company_short %}-Inhalte wie Code, Issues, Kommentare oder Pull Requests.
|
||||
|
||||
We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content.
|
||||
Nur die Besitzer*innen des verbundenen Unternehmenskontos oder der Organisation in {% data variables.product.prodname_ghe_cloud %} können auf die Daten zugreifen.
|
||||
|
||||
Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data.
|
||||
Nur bestimmte Aggregatmetriken werden aus Repositorys, Issues, Pull Requests und anderen Features gesammelt. Eine Liste der erfassten Aggregatmetriken findest du unter [Erfasste {% data variables.product.prodname_server_statistics %}-Daten](#server-statistics-data-collected).
|
||||
|
||||
Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)."
|
||||
Jegliche Updates an den gesammelten Metriken erfolgen in Featurereleases von {% data variables.product.prodname_ghe_server %} und werden in den [Versionshinweisen von {% data variables.product.prodname_ghe_server %}](/admin/release-notes) erläutert. Darüber hinaus wird dieser Artikel mit sämtlichen Metrikupdates aktualisiert.
|
||||
|
||||
Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates.
|
||||
Weitere Informationen dazu, wie wir {% data variables.product.prodname_server_statistics %}-Daten speichern und schützen, findest du unter [GitHub-Sicherheit](https://github.com/security).
|
||||
|
||||
For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)."
|
||||
### Informationen zur Datenaufbewahrung und -löschung
|
||||
|
||||
### About data retention and deletion
|
||||
{% data variables.product.company_short %} sammelt {% data variables.product.prodname_server_statistics %} Daten, solange deine {% data variables.product.prodname_ghe_server %}-Lizenz aktiv und das {% data variables.product.prodname_server_statistics %}-Feature aktiviert ist.
|
||||
|
||||
{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled.
|
||||
Wenn du deine Daten löschen möchtest, kannst du dich an den GitHub-Support, deine*n {% data variables.product.prodname_dotcom %}-Kundenbetreuer*in oder deinen Customer Success Manager wenden. Im Allgemeinen löschen wir Daten in dem in unseren Datenschutzbestimmungen angegebenen Zeitrahmen. Weitere Informationen findest du in der [Datenschutzerklärung von {% data variables.product.company_short %}](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in der Dokumentation auf {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation.
|
||||
### Informationen zur Datenportabilität
|
||||
|
||||
### About data portability
|
||||
Als Organisations- oder Unternehmensbesitzer*in auf {% data variables.product.prodname_ghe_cloud %} kannst du auf {% data variables.product.prodname_server_statistics %}-Daten zugreifen, indem du diese als CSV- oder JSON-Datei exportierst. Auch der Zugriff über die {% data variables.product.prodname_server_statistics %}-REST-API ist möglich. Weitere Informationen findest du unter [Anfordern von {% data variables.product.prodname_server_statistics %} über die REST-API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api) oder [Exportieren von {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics).
|
||||
|
||||
As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)."
|
||||
## Informationen zum Deaktivieren der Datensammlung
|
||||
|
||||
## About disabling data collection
|
||||
Du kannst das {% data variables.product.prodname_server_statistics %}-Feature jederzeit deaktivieren. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_server_statistics %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise).
|
||||
|
||||
You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)."
|
||||
## Gesammelte {% data variables.product.prodname_server_statistics %}-Daten
|
||||
|
||||
## {% data variables.product.prodname_server_statistics %} data collected
|
||||
Nachdem du {% data variables.product.prodname_server_statistics %} aktiviert hast, werden Metriken mithilfe eines täglichen Auftrags gesammelt, der in {% data variables.location.product_location %} ausgeführt wird. Die Aggregatmetriken werden in deiner Organisation oder deinem Unternehmenskonto in {% data variables.product.prodname_ghe_cloud %} gespeichert, nicht in {% data variables.location.product_location %}.
|
||||
|
||||
After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.location.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.location.product_location %}.
|
||||
Die folgenden Aggregatmetriken werden täglich gesammelt und übertragen und stellen die Gesamtanzahl für den Tag dar.
|
||||
|
||||
The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day.
|
||||
|
||||
CSV column | Name | Description |
|
||||
CSV-Spalte | Name | BESCHREIBUNG |
|
||||
---------- | ---- | ----------- |
|
||||
A | `github_connect.features_enabled` | Array of {% data variables.product.prodname_github_connect %} features that are enabled for your instance (see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features)" ) |
|
||||
B | `host_name` | The hostname for your instance |
|
||||
C | `dormant_users.dormancy_threshold` | The length of time a user must be inactive to be considered dormant |
|
||||
D | `dormant_users.total_dormant_users` | Number of dormant user accounts |
|
||||
E | `ghes_version` | The version of {% data variables.product.product_name %} that your instance is running |
|
||||
F | `server_id` | The UUID generated for your instance
|
||||
G | `collection_date` | The date the metrics were collected |
|
||||
H | `schema_version` | The version of the database schema used to store this data |
|
||||
I | `ghe_stats.comments.total_commit_comments` | Number of comments on commits |
|
||||
J | `ghe_stats.comments.total_gist_comments` | Number of comments on gists |
|
||||
K | `ghe_stats.comments.total_issue_comments` | Number of comments on issues |
|
||||
L | `ghe_stats.comments.total_pull_request_comments` | Number of comments on pull requests |
|
||||
M | `ghe_stats.gists.total_gists` | Number of gists (both secret and public) |
|
||||
N | `ghe_stats.gists.private_gists` | Number of secret gists |
|
||||
O | `ghe_stats.gists.public_gists` | Number of public gists |
|
||||
P | `ghe_stats.hooks.total_hooks` | Number of pre-receive hooks (both active and inactive) |
|
||||
Q | `ghe_stats.hooks.active_hooks` | Number of active pre-receive hooks |
|
||||
R | `ghe_stats.hooks.inactive_hooks` | Number of inactive pre-receive hooks |
|
||||
S | `ghe_stats.issues.total_issues` | Number of issues (both open and closed) |
|
||||
T | `ghe_stats.issues.open_issues` | Number of open issues |
|
||||
U | `ghe_stats.issues.closed_issues` | Number of closed issues |
|
||||
V | `ghe_stats.milestones.total_milestones` | Number of milestones (both open and closed) |
|
||||
W | `ghe_stats.milestones.open_milestones` | Number of open milestones |
|
||||
X | `ghe_stats.milestones.closed_milestones` | Number of closed milestones |
|
||||
Y | `ghe_stats.orgs.total_orgs` | Number of organizations (both enabled and disabled) |
|
||||
Z | `ghe_stats.orgs.disabled_orgs` | Number of disabled organizations |
|
||||
AA | `ghe_stats.orgs.total_teams` | Number of teams |
|
||||
AB | `ghe_stats.orgs.total_team_members` | Number of team members |
|
||||
AC | `ghe_stats.pages.total_pages` | Number of {% data variables.product.prodname_pages %} sites |
|
||||
AD | `ghe_stats.pulls.total_pulls` | Number of pull requests |
|
||||
AE | `ghe_stats.pulls.merged_pulls` | Number of merged pull requests |
|
||||
AF | `ghe_stats.pulls.mergeable_pulls` | Number of pull requests that are currently mergeable |
|
||||
AG | `ghe_stats.pulls.unmergeable_pulls` | Number of pull requests that are currently unmergeable |
|
||||
AH | `ghe_stats.repos.total_repos` | Number of repositories (both upstream repositories and forks) |
|
||||
AI | `ghe_stats.repos.root_repos` | Number of upstream repositories |
|
||||
AJ | `ghe_stats.repos.fork_repos` | Number of forks |
|
||||
AK | `ghe_stats.repos.org_repos` | Number of repositories owned by organizations |
|
||||
AL | `ghe_stats.repos.total_pushes` | Number of pushes to repositories |
|
||||
AM | `ghe_stats.repos.total_wikis` | Number of wikis |
|
||||
AN | `ghe_stats.users.total_users` | Number of user accounts |
|
||||
AO | `ghe_stats.users.admin_users` | Number of user accounts that are site administrators |
|
||||
AP | `ghe_stats.users.suspended_users` | Number of user accounts that are suspended |
|
||||
Ein | `github_connect.features_enabled` | Array von {% data variables.product.prodname_github_connect %}-Funktionen, die für deine Instanz aktiviert sind (siehe „[Informationen zu {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features)“) |
|
||||
B | `host_name` | Der Hostname für deine Instanz |
|
||||
C | `dormant_users.dormancy_threshold` | Die Zeitspanne welche ein Benutzer inaktiv sein muss um als ruhend betrachtet zu werden |
|
||||
D | `dormant_users.total_dormant_users` | Anzahl ruhender Benutzerkonten |
|
||||
E | `ghes_version` | Die Version von {% data variables.product.product_name %}, die von deiner Instanz ausgeführt wird |
|
||||
F | `server_id` | Die für deine Instanz generierte UUID
|
||||
G | `collection_date` | Das Datum, an dem die Metriken erfasst wurden |
|
||||
H | `schema_version` | Die Version des Datenbankschemas, das zum Speichern dieser Daten verwendet wird |
|
||||
I | `ghe_stats.comments.total_commit_comments` | Anzahl der Kommentare zu Commits |
|
||||
J | `ghe_stats.comments.total_gist_comments` | Anzahl der Kommentare zu Gists |
|
||||
K | `ghe_stats.comments.total_issue_comments` | Anzahl der Kommentare zu Problemen |
|
||||
L | `ghe_stats.comments.total_pull_request_comments` | Anzahl der Kommentare zu Pull Requests |
|
||||
M | `ghe_stats.gists.total_gists` | Anzahl der Gists (sowohl geheim als auch öffentlich) |
|
||||
N | `ghe_stats.gists.private_gists` | Anzahl der geheimen Gists |
|
||||
O | `ghe_stats.gists.public_gists` | Anzahl der öffentlichen Gists |
|
||||
P | `ghe_stats.hooks.total_hooks` | Anzahl der Pre-Receive-Hooks (sowohl aktiv als auch inaktiv) |
|
||||
Q | `ghe_stats.hooks.active_hooks` | Anzahl der aktiven Pre-Receive-Hooks |
|
||||
R | `ghe_stats.hooks.inactive_hooks` | Anzahl der inaktiven Pre-Receive-Hooks |
|
||||
E | `ghe_stats.issues.total_issues` | Anzahl der Probleme (sowohl offen als auch geschlossen) |
|
||||
T | `ghe_stats.issues.open_issues` | Anzahl der offenen Probleme |
|
||||
U | `ghe_stats.issues.closed_issues` | Anzahl der geschlossenen Probleme |
|
||||
V | `ghe_stats.milestones.total_milestones` | Anzahl der Meilensteine (sowohl offen als auch geschlossen) |
|
||||
W | `ghe_stats.milestones.open_milestones` | Anzahl der offenen Meilensteine |
|
||||
X | `ghe_stats.milestones.closed_milestones` | Anzahl der geschlossenen Meilensteine |
|
||||
J | `ghe_stats.orgs.total_orgs` | Anzahl der Organisationen (sowohl aktiviert als auch deaktiviert) |
|
||||
Z | `ghe_stats.orgs.disabled_orgs` | Anzahl der deaktivierten Organisationen |
|
||||
AA | `ghe_stats.orgs.total_teams` | Die Anzahl der Teams |
|
||||
AB | `ghe_stats.orgs.total_team_members` | Anzahl der Teammitglieder |
|
||||
Netzbetrieb | `ghe_stats.pages.total_pages` | Anzahl der {% data variables.product.prodname_pages %}-Websites |
|
||||
AD | `ghe_stats.pulls.total_pulls` | Anzahl der Pull Requests |
|
||||
AE | `ghe_stats.pulls.merged_pulls` | Anzahl der zusammengeführten Pull Requests |
|
||||
AF | `ghe_stats.pulls.mergeable_pulls` | Anzahl der Pull Requests, die derzeit zusammengeführt werden können |
|
||||
Verfügbarkeitsgruppe | `ghe_stats.pulls.unmergeable_pulls` | Anzahl der Pull Requests, die derzeit nicht zusammengeführt werden können |
|
||||
AH | `ghe_stats.repos.total_repos` | Anzahl der Repositorys (sowohl Upstreamrepositorys als auch Forks) |
|
||||
KI | `ghe_stats.repos.root_repos` | Anzahl der Upstreamrepositorys |
|
||||
AJ | `ghe_stats.repos.fork_repos` | Anzahl der Forks |
|
||||
AK | `ghe_stats.repos.org_repos` | Anzahl der Repositorys im Besitz von Organisationen |
|
||||
AL | `ghe_stats.repos.total_pushes` | Anzahl der Pushvorgänge an Repositorys |
|
||||
AM | `ghe_stats.repos.total_wikis` | Anzahl der Wikis |
|
||||
AN | `ghe_stats.users.total_users` | Anzahl der Benutzerkonten |
|
||||
AO | `ghe_stats.users.admin_users` | Anzahl der Benutzerkonten, die Websiteadministratoren sind |
|
||||
AP | `ghe_stats.users.suspended_users` | Anzahl der gesperrten Benutzerkonten |
|
||||
|
||||
## {% data variables.product.prodname_server_statistics %} data examples
|
||||
## Beispiele für {% data variables.product.prodname_server_statistics %}-Daten
|
||||
|
||||
To see an example of the headings included in the CSV export for {% data variables.product.prodname_server_statistics %}, download the [{% data variables.product.prodname_server_statistics %} CSV example](/assets/server-statistics-csv-example.csv).
|
||||
Um ein Beispiel für die Überschriften zu sehen, die im CSV-Export für {% data variables.product.prodname_server_statistics %} enthalten sind, lädst du das [CSV-Beispiel {% data variables.product.prodname_server_statistics %}](/assets/server-statistics-csv-example.csv) herunter.
|
||||
|
||||
To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)."
|
||||
Ein Beispiel für die Antwortnutzdaten der {% data variables.product.prodname_server_statistics %}-API findest du unter [Anfordern von {% data variables.product.prodname_server_statistics %} über die REST-API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api).
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Erstellen einer Sicherheitsempfehlung für ein Repository
|
||||
intro: 'Du kannst einen Entwurf eines Sicherheitshinweises erstellen, um privat über die Sicherheitslücke in Deinem Open-Source-Projekt zu diskutieren und sie zu beheben.'
|
||||
title: Creating a repository security advisory
|
||||
intro: You can create a draft security advisory to privately discuss and fix a security vulnerability in your open source project.
|
||||
redirect_from:
|
||||
- /articles/creating-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
|
||||
@@ -15,31 +15,31 @@ topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Create repository advisories
|
||||
ms.openlocfilehash: de22432173f6bf909d001a3f780b0f9943769ec0
|
||||
ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148114037'
|
||||
---
|
||||
Jeder, der über Administratorberechtigungen für ein Repository verfügt, kann einen Sicherheitshinweis erstellen.
|
||||
|
||||
Anyone with admin permissions to a repository can create a security advisory.
|
||||
|
||||
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
|
||||
|
||||
## Erstellen einer Sicherheitsempfehlung
|
||||
## Creating a security advisory
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. Klicke auf **Neue Sicherheitsempfehlung entwerfen**, um das Entwurfsformular für Empfehlungen zu öffnen.
|
||||
|
||||
5. Gib einen Titel für den Sicherheitshinweis ein.
|
||||
{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
|
||||
11. Klicke auf **Entwurf für Sicherheitsempfehlung erstellen**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-advisories %}
|
||||
1. Click **New draft security advisory** to open the draft advisory form. The fields marked with an asterisk are required.
|
||||
|
||||
1. Type a title for your security advisory.
|
||||
{% data reusables.repositories.security-advisory-edit-details %}
|
||||
{% data reusables.repositories.security-advisory-edit-severity %}
|
||||
{% data reusables.repositories.security-advisory-edit-cwe-cve %}
|
||||
{% data reusables.repositories.security-advisory-edit-description %}
|
||||
1. Click **Create draft security advisory**.
|
||||
|
||||
|
||||
## Nächste Schritte
|
||||
## Next steps
|
||||
|
||||
- Du kannst Den Entwurf des Sicherheitshinweises kommentieren, um die Schwachstelle mit Deinem Team zu diskutieren.
|
||||
- Füge Mitarbeiter zum Sicherheitshinweis hinzu. Weitere Informationen findest du unter [Hinzufügen eines Mitarbeiters zu einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory).
|
||||
- Privat mit anderen zusammenarbeiten, um die Schwachstelle in einem temporären privaten Fork zu beheben. Weitere Informationen findest du unter [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability).
|
||||
- Füge Personen hinzu, die eine Anerkennung für einen Beitrag zur Sicherheitsempfehlung erhalten sollen. Weitere Informationen findest du unter [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories).
|
||||
- Veröffentliche den Sicherheitshinweis, um Deine Community über die Sicherheitslücke zu informieren. Weitere Informationen findest du unter [Veröffentlichen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/publishing-a-repository-security-advisory).
|
||||
- Comment on the draft security advisory to discuss the vulnerability with your team.
|
||||
- Add collaborators to the security advisory. For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."
|
||||
- Privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
|
||||
- Add individuals who should receive credit for contributing to the security advisory. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
|
||||
- Publish the security advisory to notify your community of the security vulnerability. For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Stopping and starting a codespace
|
||||
intro: 'You can stop and start your codespace to save resources and to pause work.'
|
||||
title: Beenden und Starten eines Codespaces
|
||||
intro: 'Du kannst deinen Codespace starten und beenden, um Ressourcen einzusparen und die Arbeit zu unterbrechen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,28 +10,33 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Stop a codespace
|
||||
ms.openlocfilehash: 5c34fd5b7d72f52e203cd8f8fdc1871ff6a2f014
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188248'
|
||||
---
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## About stopping and starting a codespace
|
||||
## Informationen zum Beenden und Starten eines Codespaces
|
||||
|
||||
{% data reusables.codespaces.stopping-a-codespace %}
|
||||
|
||||
Regardless of where you created or access your codespaces, you can view and manage them in your browser at https://github.com/codespaces.
|
||||
Unabhängig davon, wo du deine Codespaces erstellt hast oder darauf zugreifst, kannst du sie in deinem Browser unter https://github.com/codespaces anzeigen und verwalten.
|
||||
|
||||
## Stopping a codespace
|
||||
## Beenden eines Codespaces
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-codespaces-page %}
|
||||
1. To the right of the codespace you want to stop, click the elipsis (**...**).
|
||||
1. Click **Stop codespace**.
|
||||
|
||||
1. Klicke rechts neben dem Codespace, den du beenden möchtest, auf die Auslassungspunkte ( **...** ).
|
||||
1. Klicke auf **Codespace beenden**.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -39,7 +44,7 @@ Regardless of where you created or access your codespaces, you can view and mana
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To stop a codespace use the `gh codespace stop` subcommand and then choose the codespace you want to stop from the list that's displayed.
|
||||
Wenn du einen Codespace beenden möchtest, benutze den Unterbefehl `gh codespace stop` und wähle dann den gewünschten Codespace aus der angezeigten Liste aus.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace stop
|
||||
@@ -50,38 +55,38 @@ Regardless of where you created or access your codespaces, you can view and mana
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.vs-code.open-command-palette %}
|
||||
1. Type `stop` and select **Codespaces: Stop Codespace** from the list of options.
|
||||
1. In the list of codespaces, select the codespace you want to stop.
|
||||
1. Gib `stop` ein, und wähle in der Liste der Optionen **Codespaces: Codespace beenden** aus.
|
||||
1. Wähle in der Liste der Codespaces den Codespace aus, den du beenden möchtest.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
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)).
|
||||
Du kannst einen Codespace auf der Seite „Deine Codespaces“ (siehe [Webbrowseranweisungen](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) oder mit {% data variables.product.prodname_cli %} (siehe [CLI-Anweisungen](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)) beenden.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## Restarting a codespace
|
||||
## Neustarten eines Codespaces
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-codespaces-page %}
|
||||
1. Click the name of the codespace you want to restart.
|
||||
|
||||
1. Klicke auf den Namen des Codespaces, den du neu starten möchtest.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
When you restart a codespace you can choose to open it in {% data variables.product.prodname_vscode %} or in your browser.
|
||||
Wenn du einen Codespace neu startest, kannst du ihn wahlweise in {% data variables.product.prodname_vscode %} oder in deinem Browser öffnen.
|
||||
|
||||
- To restart a codespace and open it in {% data variables.product.prodname_vscode %}, use the `gh codespace code` subcommand and then choose the codespace you want to restart from the list that's displayed.
|
||||
- Um einen Codespace neu zu starten und ihn in {% data variables.product.prodname_vscode %} zu öffnen, verwende den Unterbefehl `gh codespace code`. Wähle anschließend in der angezeigten Liste den Codespace aus, den du neu starten möchtest.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace code
|
||||
```
|
||||
|
||||
- To restart a codespace and open it in your browser, use the `gh codespace open --web` subcommand and then choose the codespace you want to restart from the list that's displayed.
|
||||
- Um einen Codespace neu zu starten und ihn in deinem Browser zu öffnen, verwende den Unterbefehl `gh codespace open --web`. Wähle anschließend in der angezeigten Liste den Codespace aus, den du neu starten möchtest.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace open --web
|
||||
@@ -92,8 +97,8 @@ When you restart a codespace you can choose to open it in {% data variables.prod
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.vs-code.open-command-palette %}
|
||||
1. Type `connect` and select **Codespaces: Connect to Codespace** from the list of options.
|
||||
1. In the list of codespaces, select the codespace you want to restart.
|
||||
1. Gib `connect` ein, und wähle in der Liste der Optionen **Codespaces: Mit Codespace verbinden** aus.
|
||||
1. Wähle in der Liste der Codespaces den Codespace aus, den du neu starten möchtest.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -103,6 +108,6 @@ When you restart a codespace you can choose to open it in {% data variables.prod
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## Further reading
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)"
|
||||
- [Der Codespace-Lebenszyklus](/codespaces/getting-started/the-codespace-lifecycle)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
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.'
|
||||
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.'
|
||||
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,71 +16,76 @@ topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
- Fundamentals
|
||||
ms.openlocfilehash: 646f8068e68040f1d12f8155c3ba9e2bdb84c2ca
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185091'
|
||||
---
|
||||
## Informationen zu Entwicklungscontainern
|
||||
|
||||
## About dev containers
|
||||
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.
|
||||
|
||||
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.
|
||||
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).
|
||||
|
||||
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)."
|
||||
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).
|
||||
|
||||
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)."
|
||||
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).
|
||||
|
||||
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)."
|
||||
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.
|
||||
|
||||
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)."
|
||||
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).
|
||||
|
||||
### 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.
|
||||
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.
|
||||
|
||||
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)."
|
||||
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).
|
||||
|
||||
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`.
|
||||
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`.
|
||||
|
||||
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:
|
||||
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:
|
||||
* `.devcontainer/database-dev/devcontainer.json`
|
||||
* `.devcontainer/gui-dev/devcontainer.json`
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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)."
|
||||
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).
|
||||
|
||||
{% data reusables.codespaces.more-info-devcontainer %}
|
||||
|
||||
#### How to use the devcontainer.json
|
||||
#### Verwendung der Datei „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.
|
||||
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.
|
||||
|
||||
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)."
|
||||
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).
|
||||
|
||||
### Dockerfile
|
||||
|
||||
You can add a Dockerfile as part of your dev container configuration.
|
||||
Du kannst eine Dockerfile als Teil deiner Dev-Containerkonfiguration hinzufügen.
|
||||
|
||||
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-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 for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced.
|
||||
Die Dockerfile für einen Dev-Container befindet sich in der Regel im `.devcontainer`-Ordner neben der `devcontainer.json`, in der darauf verwiesen wird.
|
||||
|
||||
{% note %}
|
||||
|
||||
**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)."
|
||||
**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).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
#### Simple Dockerfile example
|
||||
#### Einfaches Dockerfile-Beispiel
|
||||
|
||||
The following example uses four instructions:
|
||||
Im folgenden Beispiel werden vier Anweisungen verwendet:
|
||||
|
||||
`ARG` defines a build-time variable.
|
||||
`ARG` definiert eine Buildzeitvariable.
|
||||
|
||||
`FROM` specifies the parent image on which the generated Docker image will be based.
|
||||
`FROM` gibt das übergeordnete Image an, auf dem das generierte Docker-Image basiert.
|
||||
|
||||
`COPY` copies a file and adds it to the filesystem.
|
||||
`COPY` kopiert eine Datei und fügt sie dem Dateisystem hinzu.
|
||||
|
||||
`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.
|
||||
`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.
|
||||
|
||||
```Dockerfile{:copy}
|
||||
ARG VARIANT="16-buster"
|
||||
@@ -97,11 +102,11 @@ COPY library-scripts/github-debian.sh /tmp/library-scripts/
|
||||
RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
|
||||
```
|
||||
|
||||
For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation.
|
||||
Weitere Informationen zu Dockerfile-Anweisungen findest du in der Docker-Dokumentation unter [Dockerfile-Referenz](https://docs.docker.com/engine/reference/builder).
|
||||
|
||||
#### Using a Dockerfile
|
||||
#### Verwenden einer Docker-Datei
|
||||
|
||||
To use a Dockerfile as part of a dev container configuration, reference it in your `devcontainer.json` file by using the `dockerfile` property.
|
||||
Wenn du eine Dockerfile als Teil einer Dev-Containerkonfiguration verwenden möchtest, verweise in deiner `devcontainer.json`-Datei mithilfe der `dockerfile`-Eigenschaft auf sie.
|
||||
|
||||
```json{:copy}
|
||||
{
|
||||
@@ -111,134 +116,134 @@ To use a Dockerfile as part of a dev container configuration, reference it in yo
|
||||
}
|
||||
```
|
||||
|
||||
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.
|
||||
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).
|
||||
|
||||
## Using the default dev container configuration
|
||||
## Verwenden der Dev-Containerstandardkonfiguration
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
Informationen zu den Komponenten des Linux-Standardimages findest du im [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal)-Repository.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
## Using a predefined dev container configuration
|
||||
## Verwenden einer vordefinierten Dev-Containerkonfiguration
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
{% data reusables.codespaces.command-palette-container %}
|
||||
1. Click the definition you want to use.
|
||||
1. Klicke auf die Definition, die du verwenden möchtest.
|
||||
|
||||
|
||||
|
||||
|
||||
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. 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. 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)."
|
||||
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).
|
||||
|
||||
|
||||
|
||||
|
||||
### Adding additional features to your `devcontainer.json` file
|
||||
### Hinzufügen zusätzlicher Features zu deiner `devcontainer.json`-Datei
|
||||
|
||||
{% 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)."
|
||||
{% 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).
|
||||
|
||||
## Creating a custom dev container configuration
|
||||
## Erstellen einer benutzerdefinierten Dev-Containerkonfiguration
|
||||
|
||||
If none of the predefined configurations meets your needs, you can create a custom configuration by writing your own `devcontainer.json` file.
|
||||
Wenn keine der vordefinierten Konfigurationen deinen Anforderungen entspricht, kannst du eine benutzerdefinierte Konfiguration erstellen, indem du deine eigene `devcontainer.json`-Datei schreibst.
|
||||
|
||||
* 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.
|
||||
* 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.
|
||||
|
||||
{% note %}
|
||||
|
||||
**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)."
|
||||
**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).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
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).
|
||||
|
||||
|
||||
|
||||
|
||||
### Adding a `devcontainer.json` file
|
||||
### Hinzufügen einer Datei vom Typ `devcontainer.json`
|
||||
|
||||
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**.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
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)."
|
||||
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).
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
### Default configuration selection during codespace creation
|
||||
### Standardkonfigurationsauswahl während der Codespaceerstellung
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
### Editing the devcontainer.json file
|
||||
### Bearbeiten der Datei „devcontainer.json“
|
||||
|
||||
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 %}
|
||||
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 %}
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
{% note %}
|
||||
|
||||
**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.
|
||||
**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.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Interface settings for {% data variables.product.prodname_vscode_shortname %}
|
||||
### Schnittstelleneinstellungen für {% 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.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User.
|
||||
Wenn eine Einstellung in mehreren Bereichen definiert ist, haben Arbeitsbereich-Einstellungen Priorität, dann folgt Remote [Codespaces] und darauf Benutzer.
|
||||
|
||||
You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places.
|
||||
Du kannst die Standardschnittstelleneinstellungen für {% data variables.product.prodname_vscode_shortname %} an zwei Orten festlegen.
|
||||
|
||||
* 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.
|
||||
* 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.
|
||||
|
||||
## Applying configuration changes to a codespace
|
||||
## Anwenden von Konfigurationsänderungen auf einen Codespace
|
||||
|
||||
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 %}.
|
||||
Änderungen an einer Konfiguration werden angewendet, wenn du das nächste Mal einen Codespace erstellst. Du kannst deine Änderungen jedoch auf einen vorhandenen Codespace anwenden, indem du den Container neu erstellst. Du kannst dies in einem Codespace im {% data variables.product.prodname_vscode_shortname %}-Webclient oder der Desktopanwendung tun, oder du kannst {% data variables.product.prodname_cli %} verwenden.
|
||||
|
||||
### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application
|
||||
### Neuerstellen des Entwicklungscontainers im Webclient oder in der Desktopanwendung von {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
{% data reusables.codespaces.rebuild-command %}
|
||||
1. {% data reusables.codespaces.recovery-mode %}
|
||||
|
||||
|
||||
|
||||
|
||||
- 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.
|
||||
- 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.
|
||||
|
||||
### Using {% data variables.product.prodname_cli %} to rebuild a dev container
|
||||
### Verwenden von {% data variables.product.prodname_cli %} zur Neuerstellung eines Entwicklungscontainers
|
||||
|
||||
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.
|
||||
Wenn du eine Entwicklungscontainerkonfiguration außerhalb von VS Code (z. B. für {% data variables.product.prodname_dotcom_the_website %} oder in einer JetBrains-IDE) geändert hast, kannst du {% data variables.product.prodname_cli %} verwenden, um den Entwicklungscontainer für einen vorhandenen Codespace neu zu erstellen.
|
||||
|
||||
1. In a terminal, enter the following command.
|
||||
1. Gib in einem Terminal den folgenden Befehl ein:
|
||||
|
||||
```
|
||||
gh cs rebuild
|
||||
```
|
||||
|
||||
Your codespaces are listed.
|
||||
Deine Codespaces werden aufgelistet.
|
||||
|
||||
1. Use the arrow keys on your keyboard to highlight the required codespace, then press <kbd>Enter</kbd>.
|
||||
1. Verwende die Pfeiltasten auf der Tastatur, um den erforderlichen Codespace zu markieren, und drücke dann die <kbd>EINGABETASTE</kbd>.
|
||||
|
||||
|
||||
## Further reading
|
||||
## Weiterführende Themen
|
||||
|
||||
- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)"
|
||||
- [Vordefinieren von Codespaces](/codespaces/prebuilding-your-codespaces)
|
||||
|
||||
@@ -11,12 +11,12 @@ topics:
|
||||
- Codespaces
|
||||
redirect_from:
|
||||
- /codespaces/troubleshooting/troubleshooting-codespaces-clients
|
||||
ms.openlocfilehash: 682160b3b92960487c0709fc411fc2143d18f415
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 35bd9dd859612307c1f9e49ea8ed9771e4f5efcd
|
||||
ms.sourcegitcommit: bf4e3590ab71b0a1bfa8d74b00183f63193acbbf
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159590'
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: '148186171'
|
||||
---
|
||||
{% jetbrains %}
|
||||
|
||||
@@ -54,7 +54,7 @@ Wenn das Problem in {% data variables.product.prodname_vscode %} Stable nicht be
|
||||
|
||||
## Behandeln von Problemen mit {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
Wenn du einen Codespace in der {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung öffnest, wirst du vielleicht einige Unterschiede zur Arbeit in einem lokalen Arbeitsbereich feststellen, aber die Benutzeroberfläche sollte ähnlich sein.
|
||||
Wenn du einen Codespace in der {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung öffnest, wirst du vielleicht einige Unterschiede zur Arbeit in einem lokalen Arbeitsbereich feststellen, aber die Benutzeroberfläche sollte ähnlich sein.
|
||||
|
||||
Wenn Probleme auftreten, kannst du nach bekannten Issues suchen und neue Issues über die {% data variables.product.prodname_vscode_shortname %}-Benutzeroberfläche im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces)-Repository protokollieren.
|
||||
|
||||
@@ -104,6 +104,31 @@ Im Folgenden findest du einige Anhaltspunkte für den Anfang, die du je nach Gr
|
||||
|
||||
1. Klicke auf **Speichern und neu starten**.
|
||||
|
||||
### Client kann unter macOS Ventura nicht geöffnet werden
|
||||
|
||||
Unter macOS Ventura wird beim ersten Versuch, über das JetBrains-Gateway eine Verbindung mit einem Codespace herzustellen, möglicherweise eine Meldung angezeigt, die dich darüber informiert, dass die JetBrains-Clientanwendung „beschädigt ist und nicht geöffnet werden kann“.
|
||||
|
||||
<img src="/assets/images/help/codespaces/jetbrains-ventura-error1.png" alt="Screenshot of the 'cannot be opened' error message" style="width:230px;"/>
|
||||
|
||||
Gehe in diesem Fall wie folgt vor:
|
||||
|
||||
1. Klicke auf **Abbrechen**, um diese Nachricht zu schließen.
|
||||
1. Klicke oben links auf dem Bildschirm auf das Apple-Symbol, und klicke auf **Systemeinstellungen**.
|
||||
1. Klicke auf **Datenschutz und Sicherheit**, und scrolle nach unten zum Abschnitt „Sicherheit“.
|
||||
|
||||
|
||||
|
||||
Es wird eine Meldung angezeigt, die dich darüber informiert, dass die Verwendung des JetBrains-Clients blockiert wurde.
|
||||
|
||||
1. Klicke auf **Trotzdem öffnen**, um den JetBrains-Client zu den erkannten Anwendungen hinzuzufügen.
|
||||
Die Meldung wird erneut angezeigt, aber diesmal mit der Schaltfläche **Öffnen**.
|
||||
|
||||
<img src="/assets/images/help/codespaces/jetbrains-ventura-error2.png" alt="Screenshot of the error message with an 'Open' button" style="width:230px;"/>
|
||||
|
||||
1. Klicke erneut auf **Abbrechen**.
|
||||
1. Wechsle zurück zur JetBrains Gateway-Anwendung, und stelle erneut eine Verbindung mit dem erforderlichen Codespace her.
|
||||
Der JetBrains-Client wird nun erfolgreich geöffnet. Nachdem du die Clientanwendung für die Ausführung auf deinem Mac autorisiert hast, wird die Meldung nicht mehr angezeigt, wenn du in Zukunft eine Verbindung mit deinen Codespaces herstellst.
|
||||
|
||||
### SSH-Verbindungsprobleme
|
||||
|
||||
Um eine Verbindung über den SSH-Server herzustellen, der in deinem Codespace ausgeführt wird, musst du über einen SSH-Schlüssel in deinem `~/.ssh`-Verzeichnis (macOS und Linux) oder `%HOMEPATH%\.ssh`-Verzeichnis (Windows) verfügen, der deinem {% data variables.product.prodname_dotcom %}-Konto bereits hinzugefügt wurde. Wenn du keine Schlüssel in diesem Verzeichnis hast, generiert {% data variables.product.prodname_cli %} Schlüssel für dich. Weitere Informationen findest du unter [Hinzufügen eines neuen SSH-Schlüssels zu deinem {% data variables.product.prodname_dotcom %}-Konto](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account?platform=windows&tool=webui).
|
||||
@@ -115,4 +140,3 @@ Wenn Probleme bei der Schlüsselüberprüfung auftreten, aktualisiere deine Vers
|
||||
Hilfe zu Problemen, die speziell die von dir verwendete JetBrains-IDE oder die JetBrains Gateway-Anwendung betreffen, findest du unter [Produktsupport](https://www.jetbrains.com/support/) auf der JetBrains-Website.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
|
||||
@@ -1,123 +1,125 @@
|
||||
---
|
||||
title: Getting started with GitHub Copilot in a JetBrains IDE
|
||||
title: Erste Schritte mit GitHub Copilot in einer JetBrains-IDE
|
||||
shortTitle: JetBrains IDE
|
||||
intro: 'Learn how to install {% data variables.product.prodname_copilot %} in a JetBrains IDE, and start seeing suggestions as you write comments and code.'
|
||||
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.'
|
||||
product: '{% data reusables.gated-features.copilot %}'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
ms.openlocfilehash: ae879b5834007a34ab0e3a7a45dcae4c1e31bc4f
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185059'
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and JetBrains IDEs
|
||||
## Informationen zu {% data variables.product.prodname_copilot %} und JetBrains-IDEs
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
## Prerequisites
|
||||
## Voraussetzungen
|
||||
|
||||
{% data reusables.copilot.jetbrains-ides %}
|
||||
|
||||
## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE
|
||||
## Installieren der {% data variables.product.prodname_copilot %}-Erweiterung in deiner JetBrains-IDE
|
||||
|
||||
To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} extension. The following procedure will guide you through installation of the {% data variables.product.prodname_copilot %} plugin in IntelliJ IDEA. Steps to install the plugin in another supported IDE may differ.
|
||||
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.
|
||||
|
||||
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**.
|
||||
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**.
|
||||
|
||||
- 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**.
|
||||
|
||||
- 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**.
|
||||
|
||||
|
||||
|
||||
## Seeing your first suggestion
|
||||
## Anzeigen deines ersten Vorschlags
|
||||
|
||||
{% data reusables.copilot.code-examples-limitations %}
|
||||
|
||||
{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly.
|
||||
{% data reusables.copilot.supported-languages %} Die folgenden Beispiele sind in Java geschrieben, andere Sprachen funktionieren jedoch ähnlich.
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
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.
|
||||
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.
|
||||
{% 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 %} will attempt to match the context and style of your code. You can always edit the suggested code.
|
||||
{% data variables.product.prodname_copilot %} versucht, Kontext und Stil deines Codes zu treffen. Du kannst den vorgeschlagenen Code immer bearbeiten.
|
||||
|
||||
## Seeing alternative suggestions
|
||||
## Anzeigen alternativer Vorschläge
|
||||
|
||||
{% data reusables.copilot.alternative-suggestions %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
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 %}
|
||||
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 %}
|
||||
|
||||
| OS | See next suggestion | See previous suggestion |
|
||||
| OS | Nächsten Vorschlag anzeigen | Vorherigen Vorschlag anzeigen |
|
||||
| :- | :- | :- |
|
||||
| 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 %}
|
||||
|
||||
## Seeing multiple suggestions in a new tab
|
||||
## Anzeigen mehrerer Vorschläge auf einer neuen Registerkarte
|
||||
|
||||
{% data reusables.copilot.suggestions-new-tab %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the 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 %}
|
||||
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.
|
||||
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.
|
||||
|
||||
## Generating code suggestions from comments
|
||||
## Generieren von Codevorschlägen aus Kommentaren
|
||||
|
||||
{% data reusables.copilot.generating-suggestions-from-comments %}
|
||||
|
||||
{% data reusables.copilot.create-java-file %}
|
||||
1. To prompt {% data variables.product.prodname_copilot %} to suggest an implementation of a function in the Java file, type the following lines.
|
||||
1. Gib die folgenden Zeilen ein, um {% data variables.product.prodname_copilot %} aufzufordern, eine Implementierung einer Funktion in der Java-Datei vorzuschlagen.
|
||||
```java{:copy}
|
||||
// find all images without alternate text
|
||||
// and give them a red border
|
||||
void process () {
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Enabling and disabling {% data variables.product.prodname_copilot %}
|
||||
## Aktivieren und Deaktivieren von {% data variables.product.prodname_copilot %}
|
||||
|
||||
You can enable or disable {% data variables.product.prodname_copilot %} for all languages, or for individual languages. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of your JetBrains IDE window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
- 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_**.
|
||||
|
||||
- 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**.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [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)
|
||||
- [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)
|
||||
|
||||
@@ -1,34 +1,39 @@
|
||||
---
|
||||
title: Getting started with GitHub Copilot in Neovim
|
||||
title: Erste Schritte mit GitHub Copilot in Neovim
|
||||
shortTitle: Neovim
|
||||
product: '{% data reusables.gated-features.copilot %}'
|
||||
intro: 'Learn how to install {% data variables.product.prodname_copilot %} in Neovim, and start seeing suggestions as you write comments and code.'
|
||||
intro: 'Erfahre, wie du {% data variables.product.prodname_copilot %} in Neovim installierst, um beim Schreiben von Kommentaren und Code Vorschläge zu erhalten.'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
ms.openlocfilehash: 6296ff5b89e86b4b51cbb04bd9ac4ba91863a1ac
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185067'
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and Neovim
|
||||
## Informationen zu {% data variables.product.prodname_copilot %} und Neovim
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
If you use a Neovim, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor.
|
||||
Wenn du Neovim verwendest, kannst du Vorschläge aus {% data variables.product.prodname_copilot %} direkt im Editor anzeigen und übernehmen.
|
||||
|
||||
## Prerequisites
|
||||
## Voraussetzungen
|
||||
|
||||
- To use {% data variables.product.prodname_copilot %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
|
||||
- Um {% data variables.product.prodname_copilot %} verwenden zu können, benötigst du ein aktives {% data variables.product.prodname_copilot %}-Abonnement. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot).
|
||||
|
||||
- To use {% data variables.product.prodname_copilot %} in Neovim you must have Neovim and Node.js version 17 or below installed. For more information, see the [Neovim documentation](https://neovim.io/doc/) and the [Node.js website](https://nodejs.org/en/).
|
||||
- Um {% data variables.product.prodname_copilot %} in Neovim zu verwenden, musst Neovim und höchstens die Node.js-Version 17 installiert sein. Weitere Informationen findest du in der [Neovim-Dokumentation](https://neovim.io/doc/) und auf der [Node.js-Website](https://nodejs.org/en/).
|
||||
|
||||
## Installing the Neovim extension
|
||||
## Die Neovim-Erweiterung installieren
|
||||
|
||||
{% mac %}
|
||||
|
||||
{% data reusables.copilot.install-copilot-in-neovim %}
|
||||
- To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Terminal.
|
||||
- Gib den folgenden Befehl in Terminal ein, um {% data variables.product.prodname_copilot %} mit dem integrierten Plug-In-Manager von Neovim zu installieren:
|
||||
|
||||
git clone https://github.com/github/copilot.vim \
|
||||
~/.config/nvim/pack/github/start/copilot.vim
|
||||
@@ -41,7 +46,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia
|
||||
{% windows %}
|
||||
|
||||
{% data reusables.copilot.install-copilot-in-neovim %}
|
||||
- To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Git Bash.
|
||||
- Gib den folgenden Befehl in Git Bash ein, um {% data variables.product.prodname_copilot %} mit dem integrierten Plug-In-Manager von Neovim zu installieren:
|
||||
|
||||
git clone https://github.com/github/copilot.vim.git `
|
||||
$HOME/AppData/Local/nvim/pack/github/start/copilot.vim
|
||||
@@ -54,7 +59,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia
|
||||
{% linux %}
|
||||
|
||||
{% data reusables.copilot.install-copilot-in-neovim %}
|
||||
- To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command:
|
||||
- Gib den folgenden Befehl ein, um {% data variables.product.prodname_copilot %} mit dem integrierten Plug-In-Manager von Neovim zu installieren:
|
||||
|
||||
git clone https://github.com/github/copilot.vim \
|
||||
~/.config/nvim/pack/github/start/copilot.vim
|
||||
@@ -63,14 +68,14 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
## Learning to use {% data variables.product.prodname_copilot %} in Neovim
|
||||
## Erlernen der Verwendung von {% data variables.product.prodname_copilot %} in Neovim
|
||||
|
||||
For guidance on using {% data variables.product.prodname_copilot %} in Neovim, you can view the plugin documentation. To see the documentation, open Neovim and run the following command.
|
||||
Einen Leitfaden zur Verwendung von {% data variables.product.prodname_copilot %} in Neovim findest du in der Plug-In-Dokumentation. Öffne Neovim, und führe den folgenden Befehl aus, um die Dokumentation anzuzeigen.
|
||||
|
||||
```
|
||||
:help copilot
|
||||
```
|
||||
|
||||
## Further reading
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
|
||||
|
||||
@@ -1,105 +1,109 @@
|
||||
---
|
||||
title: Getting started with GitHub Copilot in Visual Studio Code
|
||||
title: Erste Schritte mit GitHub Copilot in Visual Studio Code
|
||||
shortTitle: Visual Studio Code
|
||||
intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, and start seeing suggestions as you write comments and code.'
|
||||
intro: 'Erfahre, wie du {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %} installierst, um beim Schreiben von Kommentaren und Code Vorschläge zu erhalten.'
|
||||
product: '{% data reusables.gated-features.copilot %}'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
ms.openlocfilehash: 63c670a7cd5263057f79b7761a960854ecac2dd6
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185133'
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_vscode %}
|
||||
## Informationen zu {% data variables.product.prodname_copilot %} und {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
If you use {% data variables.product.prodname_vscode %}, 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 {% data variables.product.prodname_vscode %} for macOS, Windows, or Linux.
|
||||
Wenn du {% data variables.product.prodname_vscode %} 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 von {% data variables.product.prodname_vscode %} für macOS, Windows oder Linux.
|
||||
|
||||
## Prerequisites
|
||||
## Voraussetzungen
|
||||
|
||||
To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, you must have {% data variables.product.prodname_vscode %} installed. For more information, see the [{% data variables.product.prodname_vscode %} download page](https://code.visualstudio.com/Download).
|
||||
Um {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %} zu verwenden, muss {% data variables.product.prodname_vscode %} installiert sein. Weitere Informationen findest du auf der [Downloadseite zu {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/Download).
|
||||
|
||||
## Installing the {% data variables.product.prodname_vscode %} extension
|
||||
## Installation der {% data variables.product.prodname_vscode %}-Erweiterung
|
||||
|
||||
To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vscode %} extension.
|
||||
Um {% data variables.product.prodname_copilot %} zu verwenden, musst du zuerst die {% data variables.product.prodname_vscode %}-Erweiterung installieren.
|
||||
|
||||
1. In the {% data variables.product.prodname_vscode %} Marketplace, go to the [{% data variables.product.prodname_copilot %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) page and click **Install**.
|
||||
|
||||
1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Click **Open {% data variables.product.prodname_vscode %}**.
|
||||
1. In the "Extension: {% data variables.product.prodname_copilot %}" tab in {% data variables.product.prodname_vscode %}, click **Install**.
|
||||
|
||||
1. If you have not previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, you will be prompted to sign in to {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_vscode %}.
|
||||
- If you have previously authorized {% data variables.product.prodname_vscode %} for your account on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_copilot %} will be automatically authorized.
|
||||
|
||||
1. In your browser, {% 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_vscode %}**.
|
||||
1. In {% data variables.product.prodname_vscode %}, in the "{% data variables.product.prodname_vscode %}" dialog box, to confirm the authentication, click **Open**.
|
||||
1. Wechsele im {% data variables.product.prodname_vscode %}-Marketplace zur Seite [{% data variables.product.prodname_copilot %}-Erweiterung](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot), und klicke auf **Installieren**.
|
||||
|
||||
1. Ein Popupfenster mit der Abfrage, ob {% data variables.product.prodname_vscode %} geöffnet werden soll, wird angezeigt. Klicke auf **{% data variables.product.prodname_vscode %} öffnen**.
|
||||
1. Klicke auf der Registerkarte „Erweiterung: {% data variables.product.prodname_copilot %}“ in {% data variables.product.prodname_vscode %} auf **Installieren**.
|
||||
|
||||
1. Wenn du {% data variables.product.prodname_vscode %} noch nicht in deinem {% data variables.product.prodname_dotcom %}-Konto autorisiert hast, wirst du aufgefordert, dich bei {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_vscode %} anzumelden.
|
||||
- Wenn du zuvor {% data variables.product.prodname_vscode %} für dein Konto auf {% data variables.product.prodname_dotcom %} autorisiert hast, wird {% data variables.product.prodname_copilot %} automatisch autorisiert.
|
||||
|
||||
1. In deinem Browser wird {% data variables.product.prodname_dotcom %} die notwendigen Berechtigungen für {% data variables.product.prodname_copilot %} anfordern. Um diese Berechtigungen zu genehmigen, klicke auf **{% data variables.product.prodname_vscode %} autorisieren**.
|
||||
1. Klicke in {% data variables.product.prodname_vscode %} im Dialogfeld „{% data variables.product.prodname_vscode %}“ auf **Öffnen**, um die Authentifizierung zu bestätigen.
|
||||
|
||||
|
||||
## Seeing your first suggestion
|
||||
## Anzeigen deines ersten Vorschlags
|
||||
|
||||
{% data reusables.copilot.code-examples-limitations %}
|
||||
|
||||
{% data reusables.copilot.supported-languages %} The following samples are in JavaScript, but other languages will work similarly.
|
||||
{% data reusables.copilot.supported-languages %} Die folgenden Beispiele sind in JavaScript enthalten, andere Sprachen funktionieren jedoch ähnlich.
|
||||
|
||||
{% data reusables.copilot.create-js-file %}
|
||||
1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary.
|
||||
1. Gib in der JavaScript-Datei den folgenden Funktionsheader ein. {% data variables.product.prodname_copilot %} schlägt automatisch einen ganzen Funktionstext in ausgegrautem Text vor, wie unten gezeigt. Der genaue Vorschlag kann variieren.
|
||||
```javascript{:copy}
|
||||
function calculateDaysBetweenDates(begin, end) {
|
||||
```
|
||||
|
||||
{% data reusables.copilot.accept-suggestion %}
|
||||
 {% data reusables.copilot.accept-suggestion %}
|
||||
|
||||
## Seeing alternative suggestions
|
||||
## Anzeigen alternativer Vorschläge
|
||||
|
||||
{% data reusables.copilot.alternative-suggestions %}
|
||||
|
||||
{% data reusables.copilot.create-js-file %}
|
||||
1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion.
|
||||
1. Gib in der JavaScript-Datei den folgenden Funktionsheader ein. {% data variables.product.prodname_copilot %} zeigt dir einen Vorschlag an.
|
||||
```javascript{:copy}
|
||||
function calculateDaysBetweenDates(begin, end) {
|
||||
```
|
||||
{% data reusables.copilot.see-alternative-suggestions %}
|
||||
|
||||
| OS | See next suggestion | See previous suggestion |
|
||||
| OS | Nächsten Vorschlag anzeigen | Vorherigen Vorschlag anzeigen |
|
||||
| :- | :- | :- |
|
||||
|macOS|<kbd>Option (⌥) or Alt</kbd>+<kbd>]</kbd>|<kbd>Option (⌥) or 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>|
|
||||
1. Alternatively, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions.
|
||||
|macOS|<kbd>Option (⌥) oder ALT</kbd>+<kbd>]</kbd>|<kbd>Option (⌥) oder 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>|
|
||||
1. Alternativ kannst du mit dem Mauszeiger auf den Vorschlag zeigen, um die {% data variables.product.prodname_copilot %}-Befehlspalette zur Anzeige von Vorschlägen auszuwählen.
|
||||
{% data reusables.copilot.accept-or-reject-suggestion %}
|
||||
|
||||
## Seeing multiple suggestions in a new tab
|
||||
## Anzeigen mehrerer Vorschläge auf einer neuen Registerkarte
|
||||
|
||||
{% data reusables.copilot.suggestions-new-tab %}
|
||||
|
||||
{% data reusables.copilot.create-js-file %}
|
||||
1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion.
|
||||
1. Gib in der JavaScript-Datei den folgenden Funktionsheader ein. {% data variables.product.prodname_copilot %} zeigt dir einen Vorschlag an.
|
||||
```javascript{:copy}
|
||||
function calculateDaysBetweenDates(begin, end) {
|
||||
```
|
||||
1. To open a new tab with multiple additional options, press <kbd>Ctrl</kbd>+<kbd>Enter</kbd>.
|
||||
1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab.
|
||||
1. Um eine neue Registerkarte mit mehreren zusätzlichen Optionen zu öffnen, drücke <kbd>STRG</kbd>+<kbd>EINGABETASTE</kbd>.
|
||||
1. Um einen Vorschlag zu akzeptieren, klicke oberhalb des Vorschlags auf **Lösung annehmen**. Um alle Vorschläge abzulehnen, schließe die Registerkarte.
|
||||
|
||||
## Generating code suggestions from comments
|
||||
## Generieren von Codevorschlägen aus Kommentaren
|
||||
|
||||
{% data reusables.copilot.generating-suggestions-from-comments %}
|
||||
|
||||
{% data reusables.copilot.create-js-file %}
|
||||
1. In the JavaScript file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function.
|
||||
1. Gib in der JavaScript-Datei den folgenden Kommentar ein. {% data variables.product.prodname_copilot %} schlägt eine Implementierung der Funktion vor.
|
||||
```javascript{:copy}
|
||||
// find all images without alternate text
|
||||
// and give them a red border
|
||||
function process() {
|
||||
```
|
||||
|
||||
## Using a framework
|
||||
## Verwenden eines Frameworks
|
||||
|
||||
You can also use {% data variables.product.prodname_copilot %} to generate suggestions for APIs and frameworks. The following example uses {% data variables.product.prodname_copilot %} to create a simple Express server that returns the current time.
|
||||
Du kannst auch mit {% data variables.product.prodname_copilot %} Vorschläge für APIs und Frameworks generieren. Im folgenden Beispiel wird mit {% data variables.product.prodname_copilot %} ein einfacher Express-Server erstellt, der die aktuelle Uhrzeit zurückgibt.
|
||||
|
||||
{% data reusables.copilot.create-js-file %}
|
||||
1. In the JavaScript file, type the following comment and then press <kbd>Enter</kbd>. {% data variables.product.prodname_copilot %} will suggest an implementation of the Express app.
|
||||
1. Gib in der JavaScript-Datei den folgenden Kommentar ein, und drücke dann die <kbd>EINGABETASTE</kbd>. {% data variables.product.prodname_copilot %} schlägt eine Implementierung der Express-App vor.
|
||||
```javascript{:copy}
|
||||
// Express server on port 3000
|
||||
1. To accept each line, press <kbd>Tab</kbd>, then <kbd>Enter</kbd>.
|
||||
@@ -107,10 +111,10 @@ You can also use {% data variables.product.prodname_copilot %} to generate sugge
|
||||
```javascript{:copy}
|
||||
// Return the current time
|
||||
```
|
||||
1. To accept each line, press <kbd>Tab</kbd>.
|
||||
1. Um jede Zeile zu akzeptieren, drücke die <kbd>TABULATORTASTE</kbd>.
|
||||
|
||||
{% data reusables.copilot.enabling-or-disabling-in-vsc %}
|
||||
|
||||
## Further reading
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
|
||||
|
||||
@@ -1,84 +1,86 @@
|
||||
---
|
||||
title: Getting started with GitHub Copilot in Visual Studio
|
||||
title: Erste Schritte mit GitHub Copilot in Visual Studio
|
||||
shortTitle: Visual Studio
|
||||
product: '{% data reusables.gated-features.copilot %}'
|
||||
intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, and start seeing suggestions as you write comments and code.'
|
||||
intro: 'Erfahre, wie du {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %} installierst, um beim Schreiben von Kommentaren und Code Vorschläge zu erhalten.'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
ms.openlocfilehash: 353095b0b0490cd12da8d853754b524431605819
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185130'
|
||||
---
|
||||
|
||||
{% data reusables.copilot.copilot-cta-button %}
|
||||
|
||||
## About {% data variables.product.prodname_copilot %} and Visual Studio
|
||||
## Informationen zu {% data variables.product.prodname_copilot %} und Visual Studio
|
||||
|
||||
{% data reusables.copilot.procedural-intro %}
|
||||
|
||||
If you use {% data variables.product.prodname_vs %}, 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 {% data variables.product.prodname_vs %} for Windows.
|
||||
Wenn du {% data variables.product.prodname_vs %} 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 von {% data variables.product.prodname_vs %} für Windows.
|
||||
|
||||
## Prerequisites
|
||||
## Voraussetzungen
|
||||
|
||||
To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must have {% data variables.product.prodname_vs %} 2022 17.2 or later installed. For more information, see the [Visual Studio IDE](https://visualstudio.microsoft.com/vs/) documentation.
|
||||
Um {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %} zu verwenden, muss {% data variables.product.prodname_vs %} 2022 17.2 oder höher installiert sein. Weitere Informationen findest du in der Dokumentation zu [Visual Studio IDE](https://visualstudio.microsoft.com/vs/).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data variables.product.prodname_copilot %} is not currently available for use with Visual Studio for Mac.
|
||||
**Hinweis**: {% data variables.product.prodname_copilot %} ist derzeit nicht für die Verwendung mit Visual Studio für Mac verfügbar.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Installing the {% data variables.product.prodname_vs %} extension
|
||||
## Installation der {% data variables.product.prodname_vs %}-Erweiterung
|
||||
|
||||
To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vs %} extension.
|
||||
1. In the Visual Studio toolbar, click **Extensions**, then click **Manage Extensions**.
|
||||
|
||||
1. In the "Manage Extensions" window, click **Visual Studio Marketplace**, search for the {% data variables.product.prodname_copilot %} extension, then click **Download**.
|
||||
|
||||
1. Close the "Manage Extensions" window, then exit and relaunch {% data variables.product.prodname_vs %}.
|
||||
1. Optionally, to check that {% data variables.product.prodname_copilot %} is installed and enabled, go back to **Manage Extensions**, click **Installed** to view your currently installed extensions, then click **{% data variables.product.prodname_copilot %}** to see status information.
|
||||
|
||||
1. Open or create a new project in {% data variables.product.prodname_vs %}.
|
||||
1. In the "Microsoft {% data variables.product.prodname_vs %}" dialog box, to copy your device activation code, click **OK**.
|
||||
|
||||
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
|
||||
Um {% data variables.product.prodname_copilot %} zu verwenden, musst du zuerst die {% data variables.product.prodname_vs %}-Erweiterung installieren.
|
||||
1. Klicke in der Visual Studio-Symbolleiste auf **Erweiterungen** und dann auf **Erweiterungen verwalten**.
|
||||
|
||||
1. Klicke im Fenster „Erweiterungen verwalten“ auf **Visual Studio Marketplace**, suche nach der {% data variables.product.prodname_copilot %}-Erweiterung, und klicke dann auf **Herunterladen**.
|
||||
|
||||
1. Schließe das Fenster „Erweiterungen verwalten“, und starte {% data variables.product.prodname_vs %} neu.
|
||||
1. Wenn du überprüfen möchtest, ob {% data variables.product.prodname_copilot %} installiert und aktiviert ist, gehe zurück zu **Erweiterungen verwalten**, klicke auf **Installiert**, um deine derzeit installierten Erweiterungen anzuzeigen, und dann auf **{% data variables.product.prodname_copilot %}** , um Statusinformationen zu erhalten.
|
||||
|
||||
1. Öffne ein Projekt in {% data variables.product.prodname_vs %}, oder erstelle ein neues Projekt.
|
||||
1. Um den Geräteaktivierungscode zu kopieren, klicke im Dialogfeld „Microsoft {% data variables.product.prodname_vs %}“ auf **OK**.
|
||||
|
||||
1. Ein Geräteaktivierungsfenster wird in deinem Browser geöffnet. Füge den Gerätecode ein, und klicke dann auf **Weiter**.
|
||||
|
||||
- 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 you approve the permissions, {% data variables.product.prodname_vs %} will show a confirmation.
|
||||
|
||||
- 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. Nachdem du die Berechtigungen genehmigt hast, zeigt {% data variables.product.prodname_vs %} eine Bestätigung an.
|
||||
|
||||
|
||||
## Seeing your first suggestion
|
||||
## Anzeigen deines ersten Vorschlags
|
||||
|
||||
{% data reusables.copilot.code-examples-limitations %}
|
||||
{% data reusables.copilot.supported-languages %} The following samples are in C#, but other languages will work similarly.
|
||||
{% data reusables.copilot.code-examples-limitations %} {% data reusables.copilot.supported-languages %} Die folgenden Beispiele sind in C# geschrieben, andere Sprachen funktionieren jedoch ähnlich.
|
||||
|
||||
{% data reusables.copilot.create-c-file %}
|
||||
1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary.
|
||||
1. Gib in der C#-Datei die folgende Funktionssignatur ein. {% data variables.product.prodname_copilot %} schlägt automatisch einen ganzen Funktionstext in ausgegrautem Text vor, wie unten gezeigt. Der genaue Vorschlag kann variieren.
|
||||
```csharp{:copy}
|
||||
int CalculateDaysBetweenDates(
|
||||
```
|
||||
|
||||
{% data reusables.copilot.accept-suggestion %}
|
||||
 {% data reusables.copilot.accept-suggestion %}
|
||||
|
||||
## Seeing alternative suggestions
|
||||
{% data reusables.copilot.alternative-suggestions %}
|
||||
{% data reusables.copilot.create-c-file %}
|
||||
1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will show you a suggestion.
|
||||
## Anzeigen alternativer Vorschläge
|
||||
{% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-c-file %}
|
||||
1. Gib in der C#-Datei die folgende Funktionssignatur ein. {% data variables.product.prodname_copilot %} zeigt dir einen Vorschlag an.
|
||||
|
||||
```csharp{:copy}
|
||||
int CalculateDaysBetweenDates(
|
||||
```
|
||||
1. If alternative suggestions are available, you can see these alternatives by pressing <kbd>Alt</kbd>+<kbd>]</kbd> (or <kbd>Alt</kbd>+<kbd>[</kbd>).
|
||||
1. Optionally, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions.
|
||||
1. Wenn alternative Vorschläge verfügbar sind, kannst du <kbd>ALT</kbd>+<kbd>]</kbd> (oder <kbd>ALT</kbd>+<kbd>[</kbd>) drücken, um diese Alternativen anzuzeigen.
|
||||
1. Optional kannst du mit dem Mauszeiger auf den Vorschlag zeigen, um die {% data variables.product.prodname_copilot %}-Befehlspalette zur Auswahl von Vorschlägen anzuzeigen.
|
||||
{% data reusables.copilot.accept-or-reject-suggestion %}
|
||||
|
||||
## Generating code suggestions from comments
|
||||
## Generieren von Codevorschlägen aus Kommentaren
|
||||
|
||||
{% data reusables.copilot.generating-suggestions-from-comments %}
|
||||
|
||||
{% data reusables.copilot.create-c-file %}
|
||||
1. In the C# file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function.
|
||||
1. Gib in der C#-Datei den folgenden Kommentar ein. {% data variables.product.prodname_copilot %} schlägt eine Implementierung der Funktion vor.
|
||||
```csharp{:copy}
|
||||
using System.Xml.Linq;
|
||||
|
||||
@@ -91,6 +93,6 @@ To use {% data variables.product.prodname_copilot %}, you must first install the
|
||||
|
||||
{% data reusables.copilot.enabling-or-disabling-vs %}
|
||||
|
||||
## Further reading
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
|
||||
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Ändern der Remote-URL für ein Repository aus GitHub Desktop
|
||||
intro: 'Du kannst die Remote-URL für ein Repository, mit dem du arbeitest, in {% data variables.product.prodname_desktop %} ändern. Dies ist möglicherweise erforderlich, wenn das Repository umbenannt oder der Benutzername oder die Organisation, dem bzw. der das Repository gehört, geändert wurde.'
|
||||
redirect_from:
|
||||
- /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop
|
||||
- /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Change the remote URL for a repository
|
||||
ms.openlocfilehash: e37c4878c13a9de95520f8e9c1edc9bf6416d46a
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188363'
|
||||
---
|
||||
{% mac %}
|
||||
|
||||
{% data reusables.desktop.mac-repository-settings-menu %}
|
||||
2. Klicke auf **Remote**, und gib unter **Primäres Remoterepository** die gewünschte URL ein.
|
||||
 {% data reusables.desktop.repository-settings-save %}
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
{% data reusables.desktop.windows-repository-settings-menu %}
|
||||
2. Klicke auf **Remote**, und gib unter **Primäres Remoterepository** die gewünschte URL ein.
|
||||
 {% data reusables.desktop.repository-settings-save %}
|
||||
|
||||
{% endwindows %}
|
||||
@@ -7,18 +7,18 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ms.openlocfilehash: bba9137fc39c1bc101a75650dcea03e651d37fff
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 27f11aa4ae2693bcc336ecdf4cbfb68d8679d743
|
||||
ms.sourcegitcommit: 74c60a4564bcc17e47b5a67941ac6d9fe13b6a5c
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145089724'
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: '148186163'
|
||||
---
|
||||
## Für GitHub-Apps
|
||||
|
||||
Bestimmte Apps in {% data variables.product.prodname_marketplace %} verfügen über den Badge {% octicon "verified" aria-label="The verified badge" %} sowie über eine QuickInfo mit dem Hinweis, dass die Domäne und die E-Mail-Adresse des Herausgebers verifiziert wurden. Das bedeutet, dass die App im Besitz einer Organisation ist, die folgende Anforderungen erfüllt:
|
||||
|
||||
- Sie hat den Besitz ihrer Domäne bestätigt und verfügt über einen Badge vom Typ „Verifiziert“ für ihr Profil.
|
||||
- Sie hat den Besitz ihrer Domäne bestätigt, und ihr Profil weist den Badge „Verifiziert“ auf.
|
||||
- Sie hat ihre E-Mail-Adresse bestätigt, sodass der Support von {% data variables.product.prodname_dotcom %} die Organisation erreichen kann.
|
||||
- Sie schreibt die zweistufige Authentifizierung für ihre Organisation vor. Weitere Informationen findest du unter [Erfordern der zweistufigen Authentifizierung in deiner Organisation](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization).
|
||||
|
||||
@@ -39,7 +39,7 @@ Informationen zur Suche nach Apps findest du unter [Durchsuchen des {% data vari
|
||||
|
||||
## Für GitHub Actions
|
||||
|
||||
Bei Aktionen mit dem Badge {% octicon "verified" aria-label="The verified badge" %} oder mit dem Badge für überprüfte Ersteller wurde der Ersteller der Aktion von {% data variables.product.prodname_dotcom %} als Partnerorganisation verifiziert.
|
||||
Bei Aktionen mit dem Badge {% octicon "verified" aria-label="The verified badge" %} oder mit dem Badge für verifizierte Ersteller*innen wurde der oder die Ersteller*in der Aktion von {% data variables.product.prodname_dotcom %} als Partnerorganisation bestätigt. Partner können eine E-Mail an <a href="mailto:partnerships@github.com">partnerships@github.com</a> senden, um den Badge für verifizierte Ersteller*innen zu beantragen.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -4,12 +4,12 @@ intro: 'Erfahre, wie du die {% data variables.product.prodname_discussions %} Gr
|
||||
versions:
|
||||
feature: discussions
|
||||
shortTitle: Use GraphQL for Discussions
|
||||
ms.openlocfilehash: 1512082737df4c92942a40007d2c75897edb1061
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: fd296c4e9390cac3500ba7319cb602366a37e262
|
||||
ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147408843'
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: '148185623'
|
||||
---
|
||||
Die {% data variables.product.prodname_discussions %} GraphQL API ermöglicht es dir, Diskussionsbeiträge zu erhalten, zu erstellen, zu bearbeiten und zu löschen. Weitere Informationen zu {% data variables.product.prodname_discussions %} findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
|
||||
|
||||
@@ -72,7 +72,7 @@ enum DiscussionOrderField {
|
||||
|
||||
### Repository.discussionCategories
|
||||
|
||||
Gib die verfügbaren Diskussionskategorien zurück, die in diesem Repository definiert sind. Jedes Repository kann bis zu 10 Kategorien aufweisen. Weitere Informationen zu Diskussionskategorien findest du unter "[Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)."
|
||||
Gib die verfügbaren Diskussionskategorien zurück, die in diesem Repository definiert sind. Jedes Repository kann bis zu 25 Kategorien aufweisen. Weitere Informationen zu Diskussionskategorien findest du unter "[Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)."
|
||||
|
||||
_Unterschrift:_
|
||||
|
||||
@@ -147,7 +147,7 @@ query {
|
||||
}
|
||||
```
|
||||
|
||||
### Diskussion
|
||||
### Diskussion (Discussion)
|
||||
|
||||
<details>
|
||||
<summary>Felder:</summary>
|
||||
@@ -1083,6 +1083,6 @@ Rückgabetypfelder:
|
||||
* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
|
||||
* `discussion: Discussion` Die Diskussion, die den unmarkierten Kommentar enthält.
|
||||
|
||||
## Suchen,
|
||||
## Suche
|
||||
|
||||
Die Diskussion kann von der obersten Ebene `search` Feld zurückgegeben werden. Um nach Diskussionen zu suchen, gibst du `type` als `DISCUSSION` an. Der `SearchResultItemConnection` Typ hat ein `discussionCount` Feld, um die Anzahl der zurückgegebenen Diskussionen zu melden, und der `Discussion` Typ wird der `SearchResultItem` Union hinzugefügt. Weitere Informationen findest du unter "[Abfragen](/graphql/reference/queries#searchresultitemconnection)" und "[Diskussionen durchsuchen](/search-github/searching-on-github/searching-discussions)."
|
||||
|
||||
@@ -9,12 +9,12 @@ topics:
|
||||
- GitHub Apps
|
||||
- OAuth Apps
|
||||
shortTitle: Limit app access requests
|
||||
ms.openlocfilehash: 4ea1bd133dcbabb9e7b3e3cbe65da5ff9c6eabac
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: 6c991ecfbdac75f1bb3bb4fdb5ea3a0692f1d040
|
||||
ms.sourcegitcommit: 30b0931723b704e219c736e0de7afe0fa799da29
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148008167'
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: '148186435'
|
||||
---
|
||||
## Informationen zu Integrationszugriffsanforderungen
|
||||
|
||||
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Konfigurieren eines Remoterepositorys für einen Fork
|
||||
intro: 'Du musst ein Remote-Repository konfigurieren, das auf das vorgelagerte Repository in Git verweist, um [die Synchronisation der in einem Fork vorgenommenen Änderungen](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) mit dem ursprünglichen Repository zu ermöglichen. Damit kannst du auch Änderungen im ursprünglichen Repository mit dem Fork synchronisieren.'
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork
|
||||
- /articles/configuring-a-remote-for-a-fork
|
||||
- /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork
|
||||
- /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork
|
||||
- /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: Configure a remote repository
|
||||
ms.openlocfilehash: 495d3c825356fd69c9130f8a122aa7a8702ff317
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188375'
|
||||
---
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Liste das aktuell konfigurierte Remote-Repository für deine Fork auf.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
|
||||
```
|
||||
3. Lege ein neues *Upstream*-Remoterepository fest, das mit dem Fork synchronisiert wird.
|
||||
```shell
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git
|
||||
```
|
||||
4. Überprüfe das neue vorgelagerte Repository, das du für deinen Fork angegeben hast.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
|
||||
> upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch)
|
||||
> upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push)
|
||||
```
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Syncing a fork
|
||||
intro: Sync a fork of a repository to keep it up-to-date with the upstream repository.
|
||||
title: Einen Fork synchronisieren
|
||||
intro: 'Synchronisiere den Fork eines Repositorys, um ihn auf dem aktuellen Stand mit dem vorgelagerten Repository zu halten.'
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork
|
||||
- /articles/syncing-a-fork
|
||||
@@ -19,44 +19,48 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
permissions: People with write access for a forked repository can sync the fork to the upstream repository.
|
||||
ms.openlocfilehash: 85b149e26cb65a428d7e9b66aea99d6b62430ae0
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188328'
|
||||
---
|
||||
|
||||
## Syncing a fork branch from the web UI
|
||||
## Synchronisieren eines Forks über die Webbenutzeroberfläche
|
||||
|
||||
{% ifversion syncing-fork-web-ui %}
|
||||
1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
|
||||
2. Select the **Sync fork** dropdown.
|
||||
|
||||
3. Review the details about the commits from the upstream repository, then click **Update branch**.
|
||||
|
||||
{% else %}
|
||||
1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
|
||||
2. Select the **Fetch upstream** dropdown.
|
||||
|
||||
3. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
|
||||
{% endif %}
|
||||
1. Navigiere in {% data variables.product.product_name %} zur Hauptseite des geforkten Repositorys, das du mit dem vorgelagerten Repository synchronisieren möchtest.
|
||||
2. Wähle das Dropdownmenü **Fork synchronisieren** aus.
|
||||
|
||||
3. Überprüfe die Details zu den Commits aus dem vorgelagerten Repository, und klicke dann auf **Branch aktualisieren**.
|
||||
 {% else %}
|
||||
1. Navigiere in {% data variables.product.product_name %} zur Hauptseite des geforkten Repositorys, das du mit dem vorgelagerten Repository synchronisieren möchtest.
|
||||
2. Wähle das Dropdownmenü **Vorgelagertes Repository abrufen** aus.
|
||||
|
||||
3. Überprüfe die Details zu den Commits aus dem vorgelagerten Repository, und klicke dann auf **Abrufen und zusammenführen**.
|
||||
{% endif %}
|
||||
|
||||
If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
|
||||
Wenn die Änderungen aus dem vorgelagerten Repository Konflikte verursachen, fordert {% data variables.product.company_short %} dich auf, einen Pull Request zu erstellen, um die Konflikte zu beheben.
|
||||
|
||||
## Syncing a fork branch with the {% data variables.product.prodname_cli %}
|
||||
## Synchronisieren eines Forkbranches mit {% data variables.product.prodname_cli %}
|
||||
|
||||
{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
|
||||
{% data reusables.cli.about-cli %} Weitere Informationen zu {% data variables.product.prodname_cli %} findest du unter [Informationen zu {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli).
|
||||
|
||||
To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments.
|
||||
Verwende zum Aktualisieren des Remoteforks aus dem übergeordneten Element den Unterbefehl `gh repo sync -b BRANCHNAME`, und gib den Forknamen und den Branchnamen als Argument an.
|
||||
|
||||
```shell
|
||||
$ gh repo sync owner/cli-fork -b BRANCH_NAME
|
||||
```
|
||||
|
||||
If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch.
|
||||
Wenn die Änderungen aus dem vorgelagerten Repository Konflikte verursachen, kann {% data variables.product.prodname_cli %} keine Synchronisierung ausführen. Du kannst das Flag `-force` festlegen, um den Zielbranch zu überschreiben.
|
||||
|
||||
## Syncing a fork branch from the command line
|
||||
## Synchronisieren eines Forkbranches über die Befehlszeile
|
||||
|
||||
Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. For more information, see "[Configuring a remote repository for a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)."
|
||||
Bevor du den Fork mit einem vorgelagerten Repository synchronisieren kannst, musst du in Git ein Remoterepository konfigurieren, das auf das vorgelagerte Repository verweist. Weitere Informationen findest du unter [Konfigurieren eines Remoterepositorys für einen Fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork).
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Change the current working directory to your local project.
|
||||
3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
|
||||
2. Ändere das aktuelle Arbeitsverzeichnis in das lokale Projekt.
|
||||
3. Rufe die Branches und die jeweiligen Commits aus dem vorgelagerten Repository ab. Commits in `BRANCHNAME` werden im lokalen Branch `upstream/BRANCHNAME` gespeichert.
|
||||
|
||||
```shell
|
||||
$ git fetch upstream
|
||||
@@ -68,14 +72,14 @@ Before you can sync your fork with an upstream repository, you must configure a
|
||||
> * [new branch] main -> upstream/main
|
||||
```
|
||||
|
||||
4. Check out your fork's local default branch - in this case, we use `main`.
|
||||
4. Sieh dir den lokalen Standardbranch des Forks an. In diesem Fall verwenden wir `main`.
|
||||
|
||||
```shell
|
||||
$ git checkout main
|
||||
> Switched to branch 'main'
|
||||
```
|
||||
|
||||
5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes.
|
||||
5. Führe die Änderungen aus dem vorgelagerten Standardbranch (in diesem Fall `upstream/main`) in deinem lokalen Standardbranch zusammen. Dadurch wird der Standardbranch deines Forks ohne Verlust der lokalen Änderungen mit dem vorgelagerten Repository synchronisiert.
|
||||
|
||||
```shell
|
||||
$ git merge upstream/main
|
||||
@@ -88,7 +92,7 @@ Before you can sync your fork with an upstream repository, you must configure a
|
||||
> create mode 100644 README.md
|
||||
```
|
||||
|
||||
If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation.
|
||||
Wenn dein lokaler Branch noch keine eindeutigen Commits besitzt, führt Git eine schnelle Weiterleitung aus. Weitere Informationen findest du unter [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in der Git-Dokumentation.
|
||||
```shell
|
||||
$ git merge upstream/main
|
||||
> Updating 34e91da..16c56ad
|
||||
@@ -96,10 +100,10 @@ Before you can sync your fork with an upstream repository, you must configure a
|
||||
> README.md | 5 +++--
|
||||
> 1 file changed, 3 insertions(+), 2 deletions(-)
|
||||
```
|
||||
If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)."
|
||||
Wenn dein lokaler Branch eindeutige Commits hatte, musst du möglicherweise Konflikte lösen. Weitere Informationen findest du unter [Informationen zu Mergekonflikten](/github/collaborating-with-pull-requests/addressing-merge-conflicts).
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
|
||||
**Tipp:** Durch Synchronisierung des Forks wird nur die lokale Kopie des Repositorys aktualisiert. Um den Fork auf {% data variables.location.product_location %} zu aktualisieren, musst du [deine Änderungen pushen](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Getting started with the REST API
|
||||
intro: 'Learn how to use the {% data variables.product.prodname_dotcom %} REST API.'
|
||||
title: Erste Schritte mit der REST-API
|
||||
intro: 'Erfahre, wie du die {% data variables.product.prodname_dotcom %}-REST-API verwendest.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -10,33 +10,38 @@ topics:
|
||||
- API
|
||||
shortTitle: Using the API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 66620b01bb488f8c74111b56255ff06702e402e8
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184261'
|
||||
---
|
||||
## Informationen zur {% data variables.product.prodname_dotcom %}-REST-API
|
||||
|
||||
## About the {% data variables.product.prodname_dotcom %} REST API
|
||||
Dieser Artikel beschreibt, wie du die {% data variables.product.prodname_dotcom %}-REST-API mit der {% data variables.product.prodname_cli %}, mit JavaScript oder cURL nutzen kannst. Einen Leitfaden für den schnellen Einstieg findest du unter [Schnellstart für die GitHub-REST-API](/rest/quickstart).
|
||||
|
||||
This article describes how to use the {% data variables.product.prodname_dotcom %} REST API using {% data variables.product.prodname_cli %}, JavaScript, or cURL. For a quickstart guide, see "[Quickstart for GitHub REST API](/rest/quickstart)."
|
||||
Wenn du eine Anforderung an die REST-API sendest, gibst du eine HTTP-Methode und einen Pfad an. Darüber hinaus kannst du auch Anforderungsheader sowie Pfad-, Abfrage- oder Textparameter angeben. Die API gibt den Antwortstatuscode, Antwortheader und potenziell einen Antworttext zurück.
|
||||
|
||||
When you make a request to the REST API, you will specify an HTTP method and a path. Additionally, you might also specify request headers and path, query, or body parameters. The API will return the response status code, response headers, and potentially a response body.
|
||||
Die REST-API-Referenzdokumentation beschreibt die HTTP-Methode, den Pfad und die Parameter für jeden Vorgang. Außerdem werden für jeden Vorgang Beispielanforderungen und -antworten bereitgestellt. Weitere Informationen findest du in der [REST-Referenzdokumentation](/rest).
|
||||
|
||||
The REST API reference documentation describes the HTTP method, path, and parameters for every operation. It also displays example requests and responses for each operation. For more information, see the [REST reference documentation](/rest).
|
||||
Weitere Informationen zu den APIs von {% data variables.product.company_short %} findest du unter [Informationen zu {% data variables.product.company_short %}-APIs](/developers/overview/about-githubs-apis).
|
||||
|
||||
For more information about {% data variables.product.company_short %}'s APIs, see "[About {% data variables.product.company_short %}'s APIs](/developers/overview/about-githubs-apis)."
|
||||
## Ausführen einer Anforderung
|
||||
|
||||
## Making a request
|
||||
|
||||
To make a request, first find the HTTP method and the path for the operation that you want to use. For example, the "Get Octocat" operation uses the `GET` method and the `/octocat` path. For the full reference documentation for this operation, see "[Get Octocat](/rest/meta#get-octocat)."
|
||||
Um eine Anforderung auszuführen, musst du zuerst die HTTP-Methode und den Pfad für den gewünschten Vorgang ermitteln. Der Vorgang „Get Octocat“ verwendet beispielsweise die Methode `GET` und den Pfad `/octocat`. Die vollständige Referenzdokumentation für diesen Vorgang findest du unter [Get Octocat](/rest/meta#get-octocat).
|
||||
|
||||
{% cli %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You must install {% data variables.product.prodname_cli %} in order to use the commands in the {% data variables.product.prodname_cli %} examples. For installation instructions, see the [{% data variables.product.prodname_cli %} repository](https://github.com/cli/cli#installation).
|
||||
**Hinweis**: Du musst die {% data variables.product.prodname_cli %} installieren, um die Befehle in den {% data variables.product.prodname_cli %}-Beispielen verwenden zu können. Anweisungen zur Installation findest du im [{% data variables.product.prodname_cli %}-Repository](https://github.com/cli/cli#installation).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you are not already authenticated to {% data variables.product.prodname_cli %}, you must use the `gh auth login` subcommand to authenticate before making any requests. For more information, see "[Authenticating](#authenticating)."
|
||||
Wenn du noch nicht bei der {% data variables.product.prodname_cli %} authentifiziert bist, musst du dich mit dem Unterbefehl `gh auth login` authentifizieren, bevor du eine Anforderung ausführen kannst. Weitere Informationen findest du unter [Authentifizierung](#authenticating).
|
||||
|
||||
To make a request using {% data variables.product.prodname_cli %}, use the `api` subcommand along with the path. Use the `--method` or `-X` flag to specify the method.
|
||||
Um eine Anforderung mit der {% data variables.product.prodname_cli %} auszuführen, verwende den Unterbefehl `api` zusammen mit dem Pfad. Verwende das Flag `--method` oder `-X`, um die Methode anzugeben.
|
||||
|
||||
```shell
|
||||
gh api /octocat --method GET
|
||||
@@ -48,13 +53,13 @@ gh api /octocat --method GET
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You must install and import `octokit` in order to use the Octokit.js library used in the JavaScript examples. For more information, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme).
|
||||
**Hinweis**: Du musst `octokit` installieren und importieren, um die in den JavaScript-Beispielen verwendete Bibliothek „Octokit.js“ nutzen zu können. Weitere Informationen findest du in der [Octokit.js-Infodatei](https://github.com/octokit/octokit.js/#readme).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
To make a request using JavaScript, you can use Octokit.js. For more information, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme).
|
||||
Um eine Anforderung mithilfe von JavaScript auszuführen, kannst du „Octokit.js“ verwenden. Weitere Informationen findest du in der [Octokit.js-Infodatei](https://github.com/octokit/octokit.js/#readme).
|
||||
|
||||
First, create an instance of `Octokit`.{% ifversion ghes or ghae %} Set the base URL to `{% data variables.product.api_url_code %}`. Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %}
|
||||
Erstelle zunächst eine Instanz von `Octokit`.{% ifversion ghes or ghae %} Lege die Basis-URL auf `{% data variables.product.api_url_code %}` fest. Ersetze `[hostname]` durch den Namen von {% data variables.location.product_location %}.{% endif %}
|
||||
|
||||
```javascript
|
||||
const octokit = new Octokit({ {% ifversion ghes or ghae %}
|
||||
@@ -62,7 +67,7 @@ const octokit = new Octokit({ {% ifversion ghes or ghae %}
|
||||
{% endif %}});
|
||||
```
|
||||
|
||||
Then, use the `request` method to make requests. Pass the HTTP method and path as the first argument.
|
||||
Verwende dann die `request`-Methode, um Anforderungen auszuführen. Übergib die HTTP-Methode und den Pfad als erstes Argument.
|
||||
|
||||
```javascript
|
||||
await octokit.request("GET /octocat", {});
|
||||
@@ -72,9 +77,9 @@ await octokit.request("GET /octocat", {});
|
||||
|
||||
{% curl %}
|
||||
|
||||
Prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `{% data variables.product.api_url_code %}`, to the path to get the full URL: `{% data variables.product.api_url_code %}/octocat`.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %}
|
||||
Füge die Basis-URL für die {% data variables.product.prodname_dotcom %}-REST-API, `{% data variables.product.api_url_code %}`, am Anfang des Pfads ein, um die vollständige URL zu erhalten: `{% data variables.product.api_url_code %}/octocat`.{% ifversion ghes or ghae %} Ersetze `[hostname]` durch den Namen von {% data variables.location.product_location %}.{% endif %}
|
||||
|
||||
Use the `curl` command in your command line. Use the `--request` or `-X` flag followed by the HTTP method. Use the `--url` flag followed by the full URL.
|
||||
Verwende den Befehl `curl` in deiner Befehlszeile. Verwende das Flag `--request` oder `-X`, gefolgt von der HTTP-Methode. Verwende das Flag `--url`, gefolgt von der vollständigen URL.
|
||||
|
||||
```shell
|
||||
curl --request GET \
|
||||
@@ -83,39 +88,39 @@ curl --request GET \
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If you get a message similar to "command not found: curl", you may need to download and install cURL. For more information, see [the cURL project download page](https://curl.se/download.html).
|
||||
**Hinweis**: Wenn du eine Meldung der Art „command not found: curl“ erhältst, musst du cURL möglicherweise herunterladen und installieren. Weitere Informationen findest du auf der [Downloadseite für das cURL-Projekt](https://curl.se/download.html).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
Continue reading to learn how to authenticate, send parameters, and use the response.
|
||||
Lies weiter, um zu erfahren, wie du dich authentifizieren, Parameter senden und die Antwort verwenden kannst.
|
||||
|
||||
## Authenticating
|
||||
## Authentifizierung
|
||||
|
||||
Many operations require authentication or return additional information if you are authenticated. Additionally, you can make more requests per hour when you are authenticated.{% cli %} Although some REST API operations are accessible without authentication, you must authenticate to {% data variables.product.prodname_cli %} in order to use the `api` subcommand.{% endcli %}
|
||||
Viele Vorgänge erfordern eine Authentifizierung oder geben zusätzliche Informationen zurück, wenn du authentifiziert bist. Außerdem kannst du eine größere Anzahl von Anforderungen pro Stunde ausführen, wenn du authentifiziert bist.{% cli %} Obwohl einige REST-API-Vorgänge ohne Authentifizierung zugänglich sind, musst du dich bei der {% data variables.product.prodname_cli %} authentifizieren, um den Unterbefehl `api` verwenden zu können.{% endcli %}
|
||||
|
||||
### About tokens
|
||||
### Informationen zu Token
|
||||
|
||||
You can authenticate your request by adding a token.
|
||||
Du kannst deine Anforderung authentifizieren, indem du ein Token hinzufügst.
|
||||
|
||||
If you want to use the {% data variables.product.company_short %} REST API for personal use, you can create a {% data variables.product.pat_generic %}. The REST API operations used in this article require `repo` scope for {% data variables.product.pat_v1_plural %}{% ifversion pat-v2 %} or, unless otherwise noted, read-only access to public repositories for {% data variables.product.pat_v2 %}s{% endif %}. Other operations may require different scopes{% ifversion pat-v2%} or permissions{% endif %}. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
Wenn du die {% data variables.product.company_short %}-REST-API für den privaten Gebrauch nutzen möchtest, kannst du ein {% data variables.product.pat_generic %} erstellen. Für die in diesem Artikel verwendeten REST-API-Vorgänge wird der Bereich `repo` für persönliche Zugangstoken {% data variables.product.pat_v1_plural %}{% ifversion pat-v2 %} oder, sofern nicht anders angegeben, schreibgeschützter Zugriff auf öffentliche Repositorys für {% data variables.product.pat_v2 %}{% endif %}. Für andere Vorgänge sind möglicherweise andere Bereiche{% ifversion pat-v2%} oder Berechtigungen{% endif %} erforderlich. Weitere Informationen zum Erstellen eines {% data variables.product.pat_generic %} findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
||||
|
||||
If you want to use the API on behalf of an organization or another user, {% data variables.product.company_short %} recommends that you use a {% data variables.product.prodname_github_app %}. If an operation is available to {% data variables.product.prodname_github_apps %}, the REST reference documentation for that operation will say "Works with GitHub Apps." The REST API operations used in this article require `issues` read and write permissions for {% data variables.product.prodname_github_apps %}. Other operations may require different permissions. For more information, see "[Creating a GitHub App](/developers/apps/building-github-apps/creating-a-github-app)", "[Authenticating with GitHub Apps](/developers/apps/building-github-apps/authenticating-with-github-apps), and "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)."
|
||||
Wenn du die API im Namen einer Organisation oder eines anderen Benutzers nutzen möchtest, empfiehlt {% data variables.product.company_short %}, dass du eine {% data variables.product.prodname_github_app %} verwendest. Wenn ein Vorgang für {% data variables.product.prodname_github_apps %} verfügbar ist, findest du in der REST-Referenzdokumentation für diesen Vorgang den Hinweis „Funktioniert mit GitHub Apps“. Für die in diesem Artikel verwendeten REST-API-Vorgänge werden `issues`-Lese- und -Schreibberechtigungen für {% data variables.product.prodname_github_apps %} benötigt. Für andere Vorgänge sind möglicherweise andere Berechtigungen erforderlich. Weitere Informationen findest du unter [Erstellen einer GitHub App](/developers/apps/building-github-apps/creating-a-github-app), [Authentifizierung bei GitHub Apps](/developers/apps/building-github-apps/authenticating-with-github-apps) und [Identifizieren und Autorisieren von Benutzern für GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps).
|
||||
|
||||
If you want to use the API in a {% data variables.product.prodname_actions %} workflow, {% data variables.product.company_short %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. You can grant permissions to the `GITHUB_TOKEN` with the `permissions` key. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token)."
|
||||
Wenn du die API in einem {% data variables.product.prodname_actions %}-Workflow verwenden möchtest, empfiehlt {% data variables.product.company_short %}, dass du dich mit dem integrierten `GITHUB_TOKEN` authentifizierst, anstatt ein Token zu erstellen. Du kannst den `GITHUB_TOKEN` mit dem Schlüssel `permissions` Berechtigungen erteilen. Weitere Informationen findest du unter [Automatische Tokenauthentifizierung](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token).
|
||||
|
||||
### Authentication example
|
||||
### Beispiel für die Authentifizierung
|
||||
|
||||
{% cli %}
|
||||
|
||||
With {% data variables.product.prodname_cli %}, you don't need to create an access token in advance. Use the `auth login` subcommand to authenticate to {% data variables.product.prodname_cli %}:
|
||||
Bei der {% data variables.product.prodname_cli %} ist es nicht nötig, im Voraus ein Zugriffstoken zu erstellen. Verwende den Unterbefehl `auth login`, um dich bei der {% data variables.product.prodname_cli %} zu authentifizieren:
|
||||
|
||||
```shell
|
||||
gh auth login
|
||||
```
|
||||
|
||||
You can use the `--scopes` flag to specify what scopes you want. If you want to authenticate with a token that you created, you can use the `--with-token` flag. For more information, see the [{% data variables.product.prodname_cli %} `auth login` documentation](https://cli.github.com/manual/gh_auth_login).
|
||||
Mit dem Flag `--scopes` kannst du angeben, welche Bereiche du festlegen möchtest. Wenn du dich mit einem von dir erstellten Token authentifizieren möchtest, kannst du das Flag `--with-token` verwenden. Weitere Informationen findest du in der Dokumentation zu [{% data variables.product.prodname_cli %} `auth login`](https://cli.github.com/manual/gh_auth_login).
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -123,17 +128,17 @@ You can use the `--scopes` flag to specify what scopes you want. If you want to
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Treat your access token like a password.
|
||||
**Warnung**: Behandle dein Zugriffstoken wie ein Kennwort.
|
||||
|
||||
To keep your token secure, you can store your token as a secret and run your script through {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
Um dein Token zu schützen, kannst du es als Geheimnis speichern und dein Skript über {% data variables.product.prodname_actions %} ausführen. Weitere Informationen findest du unter [Verschlüsselte Geheimnisse](/actions/security-guides/encrypted-secrets).
|
||||
|
||||
{% ifversion ghec or fpt %}You can also store your token as a {% data variables.product.prodname_codespaces %} secret and run your script in {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %}
|
||||
{% ifversion ghec or fpt %}Du kannst dein Token auch als {% data variables.product.prodname_codespaces %}-Geheimnis speichern und dein Skript in {% data variables.product.prodname_codespaces %} ausführen. Weitere Informationen findest du unter [Verwalten verschlüsselter Geheimnisse für deine Codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces).{% endif %}
|
||||
|
||||
If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely.
|
||||
Wenn diese Optionen nicht verfügbar sind, solltest du einen anderen Dienst wie zum Beispiel die [1Password CLI](https://developer.1password.com/docs/cli/secret-references/) nutzen, um dein Token sicher zu speichern.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
To authenticate with the Octokit.js library, you can pass your token when you create an instance of `Octokit`. Replace `YOUR-TOKEN` with your token.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %}
|
||||
Um dich bei der Octokit.js-Bibliothek zu authentifizieren, kannst du dein Token übergeben, wenn du eine Instanz von `Octokit` erstellst. Ersetze `YOUR-TOKEN` durch dein Token.{% ifversion ghes or ghae %} Replace `[hostname]` durch den Namen von {% data variables.location.product_location %}.{% endif %}
|
||||
|
||||
```javascript
|
||||
const octokit = new Octokit({ {% ifversion ghes or ghae %}
|
||||
@@ -148,17 +153,17 @@ const octokit = new Octokit({ {% ifversion ghes or ghae %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Treat your access token like a password.
|
||||
**Warnung**: Behandle dein Zugriffstoken wie ein Kennwort.
|
||||
|
||||
To help keep your account secure, you can use {% data variables.product.prodname_cli %} instead of cURL. {% data variables.product.prodname_cli %} will take care of authentication for you. For more information, see the {% data variables.product.prodname_cli %} version of this page.
|
||||
Um die Sicherheit deines Kontos zu gewährleisten, kannst du die {% data variables.product.prodname_cli %} anstelle von cURL verwenden. Die {% data variables.product.prodname_cli %} übernimmt die Authentifizierung für dich. Weitere Informationen findest du in der {% data variables.product.prodname_cli %}-Version dieser Seite.
|
||||
|
||||
{% ifversion ghec or fpt %}You can also store your token as a {% data variables.product.prodname_codespaces %} secret and use the command line through {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %}
|
||||
{% ifversion ghec or fpt %}Du kannst dein Token auch als {% data variables.product.prodname_codespaces %}-Geheimnis speichern und die Befehlszeile über {% data variables.product.prodname_codespaces %} verwenden. Weitere Informationen findest du unter [Verwalten verschlüsselter Geheimnisse für deine Codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces).{% endif %}
|
||||
|
||||
If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely.
|
||||
Wenn diese Optionen nicht verfügbar sind, solltest du einen anderen Dienst wie zum Beispiel die [1Password CLI](https://developer.1password.com/docs/cli/secret-references/) nutzen, um dein Token sicher zu speichern.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
With cURL, you will send an `Authorization` header with your token. Replace `YOUR-TOKEN` with your token:
|
||||
Bei cURL sendest du einen `Authorization`-Header mit deinem Token. Ersetze `YOUR-TOKEN` durch dein Token:
|
||||
|
||||
```shell
|
||||
curl --request GET \
|
||||
@@ -168,19 +173,19 @@ curl --request GET \
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.getting-started.bearer-vs-token %}
|
||||
**Hinweis:** {% data reusables.getting-started.bearer-vs-token %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
### Authentication example for {% data variables.product.prodname_actions %}
|
||||
### Authentifizierungsbeispiel für {% data variables.product.prodname_actions %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
You can also use the `run` keyword to execute {% data variables.product.prodname_cli %} commands in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
|
||||
Du kannst auch das Schlüsselwort `run` verwenden, um {% data variables.product.prodname_cli %}-Befehle in deinen {% data variables.product.prodname_actions %}-Workflows auszuführen. Weitere Informationen findest du unter [Workflowsyntax für GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun).
|
||||
|
||||
Instead of using the `gh auth login` command, pass your token as an environment variable called `GH_TOKEN`. {% data variables.product.prodname_dotcom %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
Anstatt den Befehl `gh auth login` zu verwenden, übergibst du dein Token als Umgebungsvariable namens `GH_TOKEN`. {% data variables.product.prodname_dotcom %} empfiehlt, dass du dich mit dem integrierten `GITHUB_TOKEN` authentifizierst, anstatt ein Token zu erstellen. Wenn das nicht möglich ist, speichere dein Token als Geheimnis, und ersetze `GITHUB_TOKEN` im folgenden Beispiel durch den Namen deines Geheimnisses. Weitere Informationen zu `GITHUB_TOKEN` findest du unter [Automatische Tokenauthentifizierung](/actions/security-guides/automatic-token-authentication). Weitere Informationen zu Geheimnissen findest du unter [Verschlüsselte Geheimnisse](/actions/security-guides/encrypted-secrets).
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
@@ -198,18 +203,18 @@ jobs:
|
||||
|
||||
{% javascript %}
|
||||
|
||||
You can also use the `run` keyword to execute your JavaScript scripts in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
|
||||
Du kannst auch das Schlüsselwort `run` verwenden, um deine JavaScript-Skripts in deinen {% data variables.product.prodname_actions %}-Workflows auszuführen. Weitere Informationen findest du unter [Workflowsyntax für GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun).
|
||||
|
||||
{% data variables.product.prodname_dotcom %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
{% data variables.product.prodname_dotcom %} empfiehlt, dass du dich mit dem integrierten `GITHUB_TOKEN` authentifizierst, anstatt ein Token zu erstellen. Wenn das nicht möglich ist, speichere dein Token als Geheimnis, und ersetze `GITHUB_TOKEN` im folgenden Beispiel durch den Namen deines Geheimnisses. Weitere Informationen zu `GITHUB_TOKEN` findest du unter [Automatische Tokenauthentifizierung](/actions/security-guides/automatic-token-authentication). Weitere Informationen zu Geheimnissen findest du unter [Verschlüsselte Geheimnisse](/actions/security-guides/encrypted-secrets).
|
||||
|
||||
The following example workflow:
|
||||
Der nachstehende Beispielworkflow übernimmt folgende Aufgaben:
|
||||
|
||||
1. Checks out the repository content
|
||||
1. Sets up Node.js
|
||||
1. Installs `octokit`
|
||||
1. Stores the value of `GITHUB_TOKEN` as an environment variable called `TOKEN` and runs `.github/actions-scripts/use-the-api.mjs`, which can access that environment variable as `process.env.TOKEN`
|
||||
1. Überprüfen des Repositoryinhalts
|
||||
1. Einrichten von Node.js
|
||||
1. Installieren von `octokit`
|
||||
1. Speichern des Werts von `GITHUB_TOKEN` als Umgebungsvariable namens `TOKEN` und Ausführen des Skripts `.github/actions-scripts/use-the-api.mjs`, das auf diese Umgebungsvariable als `process.env.TOKEN` zugreifen kann
|
||||
|
||||
Example workflow:
|
||||
Beispielworkflow:
|
||||
|
||||
```yaml
|
||||
on:
|
||||
@@ -238,7 +243,7 @@ jobs:
|
||||
node .github/actions-scripts/use-the-api.mjs
|
||||
```
|
||||
|
||||
Example JavaScript script, with the file path `.github/actions-scripts/use-the-api.mjs`:
|
||||
JavaScript-Beispielskript mit dem Dateipfad `.github/actions-scripts/use-the-api.mjs`:
|
||||
|
||||
```javascript
|
||||
import { Octokit } from "octokit";
|
||||
@@ -251,7 +256,7 @@ const octokit = new Octokit({ {% ifversion ghes or ghae %}
|
||||
await octokit.request("GET /octocat", {});
|
||||
```
|
||||
|
||||
Instead of storing your script in a separate file and executing the script from your workflow, you can use the `actions/github-script` action to run a script. For more information, see the [actions/github-script README](https://github.com/actions/github-script).
|
||||
Anstatt dein Skript in einer separaten Datei zu speichern und das Skript von deinem Workflow aus auszuführen, kannst du die `actions/github-script`-Aktion verwenden, um ein Skript auszuführen. Weitere Informationen findest du in der [actions/github-Infodatei](https://github.com/actions/github-script).
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
@@ -270,9 +275,9 @@ jobs:
|
||||
|
||||
{% curl %}
|
||||
|
||||
You can also use the `run` keyword to execute cURL commands in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
|
||||
Du kannst auch das Schlüsselwort `run` verwenden, um cURL-Befehle in deinen {% data variables.product.prodname_actions %}-Workflows auszuführen. Weitere Informationen findest du unter [Workflowsyntax für GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun).
|
||||
|
||||
{% data variables.product.prodname_dotcom %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
{% data variables.product.prodname_dotcom %} empfiehlt, dass du dich mit dem integrierten `GITHUB_TOKEN` authentifizierst, anstatt ein Token zu erstellen. Wenn das nicht möglich ist, speichere dein Token als Geheimnis, und ersetze `GITHUB_TOKEN` im folgenden Beispiel durch den Namen deines Geheimnisses. Weitere Informationen zu `GITHUB_TOKEN` findest du unter [Automatische Tokenauthentifizierung](/actions/security-guides/automatic-token-authentication). Weitere Informationen zu Geheimnissen findest du unter [Verschlüsselte Geheimnisse](/actions/security-guides/encrypted-secrets).
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
@@ -290,13 +295,13 @@ jobs:
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
## Using headers
|
||||
## Verwenden von Headern
|
||||
|
||||
Most operations specify that you should pass an `Accept` header with a value of `application/vnd.github+json`. Other operations may specify that you should send a different `Accept` header or additional headers.
|
||||
Die meisten Vorgänge schreiben vor, dass du einen `Accept`-Header mit dem Wert `application/vnd.github+json` übergeben musst. Bei anderen Vorgängen musst du möglicherweise einen anderen `Accept`-Header oder zusätzliche Header senden.
|
||||
|
||||
{% cli %}
|
||||
|
||||
To send a header with {% data variables.product.prodname_cli %}, use the `--header` or `-H` flag followed by the header in `key: value` format.
|
||||
Um einen Header mit der {% data variables.product.prodname_cli %} zu senden, verwende das Flag `--header` oder `-H`, gefolgt von dem Header im Format `key: value`.
|
||||
|
||||
```shell
|
||||
gh api --header 'Accept: application/vnd.github+json'{% ifversion api-date-versioning %} --header 'X-GitHub-Api-Version:{{ allVersions[currentVersion].latestApiVersion }}'{% endif %} --method GET /octocat
|
||||
@@ -306,7 +311,7 @@ gh api --header 'Accept: application/vnd.github+json'{% ifversion api-date-versi
|
||||
|
||||
{% javascript %}
|
||||
|
||||
The Octokit.js library automatically passes the `Accept: application/vnd.github+json` header. To pass additional headers or a different `Accept` header, add a `headers` property to the object that is passed as a second argument to the `request` method. The value of the `headers` property is an object with the header names as keys and header values as values. For example, to send a `content-type` header with a value of `text/plain`:
|
||||
Die Octokit.js-Bibliothek übergibt automatisch den `Accept: application/vnd.github+json`-Header. Um zusätzliche Header oder einen anderen `Accept`-Header zu übergeben, füge dem Objekt eine `headers`-Eigenschaft hinzu, die als zweites Argument an die `request`-Methode übergeben wird. Der Wert der Eigenschaft `headers` ist ein Objekt mit den Headernamen als Schlüssel und den Headerwerten als Werte. Es folgt ein Beispiel zum Senden eines `content-type`-Headers mit dem Wert `text/plain`:
|
||||
|
||||
```javascript
|
||||
await octokit.request("GET /octocat", {
|
||||
@@ -321,7 +326,7 @@ await octokit.request("GET /octocat", {
|
||||
|
||||
{% curl %}
|
||||
|
||||
To send a header with cURL, use the `--header` or `-H` flag followed by the header in `key: value` format.
|
||||
Um einen Header mit cURL zu senden, verwende das Flag `--header` oder `-H`, gefolgt von dem Header im Format `key: value`.
|
||||
|
||||
```shell
|
||||
curl --request GET \
|
||||
@@ -333,21 +338,19 @@ curl --request GET \
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
## Using path parameters
|
||||
## Verwenden von Pfadparametern
|
||||
|
||||
Path parameters modify the operation path. For example, the "List repository issues" path is `/repos/{owner}/{repo}/issues`. The curly brackets `{}` denote path parameters that you need to specify. In this case, you must specify the repository owner and name. For the reference documentation for this operation, see "[List repository issues](/rest/issues/issues#list-repository-issues)."
|
||||
Pfadparameter ändern den Vorgangspfad. Der Pfad zum Auflisten von Issues für ein Repository lautet beispielsweise `/repos/{owner}/{repo}/issues`. Die geschweiften Klammern `{}` bezeichnen Pfadparameter, die du angeben musst. In diesem Fall musst du den Besitzer und den Namen des Repositorys angeben. Die Referenzdokumentation für diesen Vorgang findest du unter [Auflisten von Issues für ein Repository](/rest/issues/issues#list-repository-issues).
|
||||
|
||||
{% cli %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
{% note %}
|
||||
{% ifversion ghes or ghae %} {% note %}
|
||||
|
||||
**Note:** In order for this command to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, rerun the `gh auth login` command to authenticate to {% data variables.product.prodname_dotcom_the_website %} instead of {% data variables.location.product_location %}.
|
||||
**Hinweis:** Damit dieser Befehl für {% data variables.location.product_location %} funktioniert, musst du `octocat/Spoon-Knife` durch ein Repository im Besitz von {% data variables.location.product_location %} ersetzen. Andernfalls musst du den Befehl `gh auth login` erneut ausführen, um dich bei {% data variables.product.prodname_dotcom_the_website %} statt {% data variables.location.product_location %} zu authentifizieren.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with `octocat` and `{repo}` with `Spoon-Knife`.
|
||||
Um Issues aus dem `octocat/Spoon-Knife` Repository abzurufen, ersetze `{owner}` durch `octocat` und `{repo}` durch `Spoon-Knife`.
|
||||
|
||||
```shell
|
||||
gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues
|
||||
@@ -357,15 +360,13 @@ gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octoca
|
||||
|
||||
{% javascript %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
{% note %}
|
||||
{% ifversion ghes or ghae %} {% note %}
|
||||
|
||||
**Note:** In order for this example to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, create a new `Octokit` instance and do not specify `baseURL`.
|
||||
**Hinweis:** Damit dieses Beispiel für {% data variables.location.product_location %} funktioniert, musst du `octocat/Spoon-Knife` durch ein Repository im Besitz von {% data variables.location.product_location %} ersetzen. Andernfalls erstellst du eine neue `Octokit`-Instanz und gibst `baseURL` nicht an.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
When you make a request with Octokit.js, all parameters, including path parameters, are passed in an object as the second argument to the `request` method. To get issues from the `octocat/Spoon-Knife` repository, specify `owner` as `octocat` and `repo` as `Spoon-Knife`.
|
||||
Wenn du eine Anforderung mit Octokit.js stellst, werden alle Parameter (einschließlich der Pfadparameter) in einem Objekt als zweites Argument an die Methode `request` übergeben. Um Issues aus dem `octocat/Spoon-Knife` Repository abzurufen, gib `owner` als `octocat` und `repo` als `Spoon-Knife` an.
|
||||
|
||||
```javascript
|
||||
await octokit.request("GET /repos/{owner}/{repo}/issues", {
|
||||
@@ -378,15 +379,13 @@ await octokit.request("GET /repos/{owner}/{repo}/issues", {
|
||||
|
||||
{% curl %}
|
||||
|
||||
To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with `octocat` and `{repo}` with `Spoon-Knife`. To build the full path, prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `https://api.github.com`: `https://api.github.com/repos/octocat/Spoon-Knife/issues`.
|
||||
Um Issues aus dem `octocat/Spoon-Knife` Repository abzurufen, ersetze `{owner}` durch `octocat` und `{repo}` durch `Spoon-Knife`. Um den vollständigen Pfad zu erhalten, füge die Basis-URL für die {% data variables.product.prodname_dotcom %}-REST-API am Pfadanfang ein, `https://api.github.com`: `https://api.github.com/repos/octocat/Spoon-Knife/issues`.
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
{% note %}
|
||||
{% ifversion ghes or ghae %} {% note %}
|
||||
|
||||
**Note:** If you want to use {% data variables.location.product_location %} instead of {% data variables.product.prodname_dotcom_the_website %}, use `{% data variables.product.api_url_code %}` instead of `https://api.github.com` and replace `[hostname]` with the name of {% data variables.location.product_location %}. Replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}.
|
||||
**Hinweis:** Wenn du {% data variables.location.product_location %} anstelle von {% data variables.product.prodname_dotcom_the_website %} verwenden möchtest, musst du `{% data variables.product.api_url_code %}` anstelle von `https://api.github.com` verwenden und `[hostname]` durch den Namen von {% data variables.location.product_location %} ersetzen. Ersetze `octocat/Spoon-Knife` durch ein Repository im Besitz von {% data variables.location.product_location %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
```shell
|
||||
curl --request GET \
|
||||
@@ -397,21 +396,21 @@ curl --request GET \
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
The operation returns a list of issues and data about each issue. For more information about using the response, see the "[Using the response](#using-the-response)" section.
|
||||
Der Vorgang liefert eine Liste der Issues sowie Daten zu jedem Issue. Weitere Informationen zur Verwendung der Antwort findest du im Abschnitt [Verwenden der Antwort](#using-the-response).
|
||||
|
||||
## Using query parameters
|
||||
## Verwenden von Abfrageparametern
|
||||
|
||||
Query parameters allow you to control what data is returned for a request. For example, a query parameter may let you specify how many items are returned when the response is paginated.
|
||||
Mithilfe von Abfrageparametern kannst du steuern, welche Daten für eine Anforderung zurückgegeben werden. Mit einem Abfrageparameter kannst du zum Beispiel angeben, wie viele Elemente zurückgegeben werden, wenn die Antwort paginiert wird.
|
||||
|
||||
By default, the "List repository issues" operation returns thirty issues, sorted in descending order by the date they were created. You can use the `per_page` parameter to return two issues instead of 30. You can use the `sort` parameter to sort the issues by the date they were last updated instead of by the date they were created. You can use the `direction` parameter to sort the results in ascending order instead of descending order.
|
||||
Standardmäßig gibt der Vorgang zum Auflisten von Issues für das Repository dreißig Issues zurück, die in absteigender Reihenfolge nach dem Erstellungsdatum sortiert sind. Du kannst mit dem Parameter `per_page` angeben, dass anstelle von 30 Issues zwei Issues zurückgegeben werden. Mit dem Parameter `sort` kannst du die Issues nach dem Datum der letzten Aktualisierung sortieren, anstatt nach dem Erstellungsdatum. Du kannst den Parameter `direction` verwenden, um die Ergebnisse in aufsteigender statt in absteigender Reihenfolge zu sortieren.
|
||||
|
||||
{% cli %}
|
||||
|
||||
For {% data variables.product.prodname_cli %}, use the `-F` flag to pass a parameter that is a number, Boolean, or null. Use `-f` to pass string parameters.
|
||||
Verwende für die {% data variables.product.prodname_cli %} das Flag `-F`, um einen Parameter zu übergeben, bei dem es sich um eine Zahl, einen booleschen Wert oder NULL handelt. Verwende `-f`, um Zeichenfolgenparameter zu übergeben.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data variables.product.prodname_cli %} does not currently accept parameters that are arrays. For more information, see [this issue](https://github.com/cli/cli/issues/1484).
|
||||
**Hinweis**: Die {% data variables.product.prodname_cli %} akzeptiert derzeit keine Parameter, bei denen es sich um Arrays handelt. Weitere Informationen findest du in [diesem Issue](https://github.com/cli/cli/issues/1484).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -423,7 +422,7 @@ gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octoca
|
||||
|
||||
{% javascript %}
|
||||
|
||||
When you make a request with Octokit.js, all parameters, including query parameters, are passed in an object as the second argument to the `request` method.
|
||||
Wenn du eine Anforderung mit Octokit.js stellst, werden alle Parameter (einschließlich der Abfrageparameter) in einem Objekt als zweites Argument an die Methode `request` übergeben.
|
||||
|
||||
```javascript
|
||||
await octokit.request("GET /repos/{owner}/{repo}/issues", {
|
||||
@@ -439,7 +438,7 @@ await octokit.request("GET /repos/{owner}/{repo}/issues", {
|
||||
|
||||
{% curl %}
|
||||
|
||||
For cURL, add a `?` to the end of the path, then append your query parameter name and value in the form `parameter_name=value`. Separate multiple query parameters with `&`.
|
||||
Für cURL fügst du ein `?` am Pfadende ein und hängst dann den Namen und den Wert deines Abfrageparameters in der Form `parameter_name=value` an. Trenne mehrere Abfrageparameter durch `&`.
|
||||
|
||||
```shell
|
||||
curl --request GET \
|
||||
@@ -450,21 +449,21 @@ curl --request GET \
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
The operation returns a list of issues and data about each issue. For more information about using the response, see the "[Using the response](#using-the-response)" section.
|
||||
Der Vorgang liefert eine Liste der Issues sowie Daten zu jedem Issue. Weitere Informationen zur Verwendung der Antwort findest du im Abschnitt [Verwenden der Antwort](#using-the-response).
|
||||
|
||||
## Using body parameters
|
||||
## Verwenden von Textparametern
|
||||
|
||||
Body parameters allow you to pass additional data to the API. For example, the "Create an issue" operation requires you to specify a title for the new issue. It also lets you specify other information, such as text to put in the issue body. For the full reference documentation for this operation, see "[Create an issue](/rest/issues/issues#create-an-issue)."
|
||||
Textparameter ermöglichen es dir, zusätzliche Daten an die API zu übergeben. Beim Vorgang zum Erstellen eines Issues musst du zum Beispiel einen Titel für das neue Issue angeben. Hier kannst du außerdem weitere Informationen angeben, z. B. den Text, der in den Textteil des Issues aufgenommen werden soll. Die vollständige Referenzdokumentation für diesen Vorgang findest du unter [Erstellen eines Issues](/rest/issues/issues#create-an-issue).
|
||||
|
||||
The "Create an issue" operation uses the same path as the "List repository issues" operation in the examples above, but it uses a `POST` method instead of a `GET` method.
|
||||
Der Vorgang zum Erstellen eines Issues verwendet denselben Pfad wie der in den obigen Beispielen gezeigte Vorgang zum Auflisten von Issues im Repository, aber er verwendet anstelle der `GET`-Methode eine `POST`-Methode.
|
||||
|
||||
{% cli %}
|
||||
|
||||
For {% data variables.product.prodname_cli %}, use the `-F` flag to pass a parameter that is a number, Boolean, or null. Use `-f` to pass string parameters.
|
||||
Verwende für die {% data variables.product.prodname_cli %} das Flag `-F`, um einen Parameter zu übergeben, bei dem es sich um eine Zahl, einen booleschen Wert oder NULL handelt. Verwende `-f`, um Zeichenfolgenparameter zu übergeben.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data variables.product.prodname_cli %} does not currently accept parameters that are arrays. For more information, see [this issue](https://github.com/cli/cli/issues/1484).
|
||||
**Hinweis**: Die {% data variables.product.prodname_cli %} akzeptiert derzeit keine Parameter, bei denen es sich um Arrays handelt. Weitere Informationen findest du in [diesem Issue](https://github.com/cli/cli/issues/1484).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -480,13 +479,13 @@ gh api --header 'Accept: application/vnd.github+json' --method POST /repos/octoc
|
||||
|
||||
{% note %}
|
||||
|
||||
If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
Wenn du ein {% data variables.product.pat_v2 %}, verwendest, musst du `octocat/Spoon-Knife` durch ein Repository ersetzen, das sich in deinem Besitz oder im Besitz einer Organisation befindet, der du angehörst. Dein Token muss Zugriff auf dieses Repository haben und über Lese- und Schreibberechtigungen für Issues im Repository verfügen. Weitere Informationen zum Erstellen eines Repositorys findest du unter [Erstellen eines Repositorys](/get-started/quickstart/create-a-repo). Weitere Informationen zum Erteilen von Zugriff und Berechtigungen für ein {% data variables.product.pat_v2 %} findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
When you make a request with Octokit.js, all parameters, including body parameters, are passed in an object as the second argument to the `request` method.
|
||||
Wenn du eine Anforderung mit „Octokit.js“ stellst, werden alle Parameter (einschließlich der Textparameter) in einem Objekt als zweites Argument an die Methode `request` übergeben.
|
||||
|
||||
```javascript
|
||||
await octokit.request("POST /repos/{owner}/{repo}/issues", {
|
||||
@@ -505,13 +504,13 @@ await octokit.request("POST /repos/{owner}/{repo}/issues", {
|
||||
|
||||
{% note %}
|
||||
|
||||
If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
Wenn du ein {% data variables.product.pat_v2 %}, verwendest, musst du `octocat/Spoon-Knife` durch ein Repository ersetzen, das sich in deinem Besitz oder im Besitz einer Organisation befindet, der du angehörst. Dein Token muss Zugriff auf dieses Repository haben und über Lese- und Schreibberechtigungen für Issues im Repository verfügen. Weitere Informationen zum Erstellen eines Repositorys findest du unter [Erstellen eines Repositorys](/get-started/quickstart/create-a-repo). Weitere Informationen zum Erteilen von Zugriff und Berechtigungen für ein {% data variables.product.pat_v2 %} findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
For cURL, use the `--data` flag to pass the body parameters in a JSON object.
|
||||
Bei cURL verwendest du das Flag `--data`, um die Textparameter in einem JSON-Objekt zu übergeben.
|
||||
|
||||
```shell
|
||||
curl --request POST \
|
||||
@@ -526,27 +525,27 @@ curl --request POST \
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
The operation creates an issue and returns data about the new issue. In the response, find the `html_url` of your issue and navigate to your issue in the browser. For more information about using the response, see the "[Using the response](#using-the-response)" section.
|
||||
Der Vorgang erstellt ein Issue und gibt Daten zu dem neuen Issue zurück. Suche in der Antwort nach der `html_url` deines Issues, und navigiere im Browser zu deinem Issue. Weitere Informationen zur Verwendung der Antwort findest du im Abschnitt [Verwenden der Antwort](#using-the-response).
|
||||
|
||||
## Using the response
|
||||
## Verwenden der Antwort
|
||||
|
||||
### About the response code and headers
|
||||
### Informationen zu Antwortcodes und Headern
|
||||
|
||||
Every request will return an HTTP status code that indicates the success of the response. For more information about response codes, see [the MDN HTTP response status code documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status).
|
||||
Jede Anforderung gibt einen HTTP-Statuscode zurück, der den Erfolgsstatus der Antwort anzeigt. Weitere Informationen zu Antwortcodes findest du in der [MDN-Dokumentation zu HTTP-Antwortstatuscodes](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status).
|
||||
|
||||
Additionally, the response will include headers that give more details about the response. Headers that start with `X-` or `x-` are custom to {% data variables.product.company_short %}. For example, the `x-ratelimit-remaining` and `x-ratelimit-reset` headers tell you how many requests you can make in a time period.
|
||||
Außerdem enthält die Antwort Header, die weitere Informationen zur Antwort liefern. Header, die mit `X-` oder `x-` beginnen, gelten speziell für {% data variables.product.company_short %}. Die Header `x-ratelimit-remaining` und `x-ratelimit-reset` informieren dich zum Beispiel darüber, wie viele Anforderungen du in einem bestimmten Zeitraum ausführen kannst.
|
||||
|
||||
{% cli %}
|
||||
|
||||
To view the status code and headers, use the `--include` or `--i` flag when you send your request.
|
||||
Um den Statuscode und die Header anzuzeigen, verwende beim Senden deiner Anforderung das Flag `--include` oder `--i`.
|
||||
|
||||
For example, this request:
|
||||
Betrachte beispielsweise die folgende Anforderung:
|
||||
|
||||
```shell
|
||||
gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues -F per_page=2 --include
|
||||
```
|
||||
|
||||
returns the response code and headers like:
|
||||
Sie gibt den Antwortcode und Header wie folgt zurück:
|
||||
|
||||
```shell
|
||||
HTTP/2.0 200 OK
|
||||
@@ -578,15 +577,15 @@ X-Ratelimit-Used: 4
|
||||
X-Xss-Protection: 0
|
||||
```
|
||||
|
||||
In this example, the response code is `200`, which indicates a successful request.
|
||||
In diesem Beispiel lautet der Antwortcode `200`, d. h. die Anforderung war erfolgreich.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
{% javascript %}
|
||||
|
||||
When you make a request with Octokit.js, the `request` method returns a promise. If the request was successful, the promise resolves to an object that includes the HTTP status code of the response (`status`) and the response headers (`headers`). If an error occurs, the promise resolves to an object that includes the HTTP status code of the response (`status`) and the response headers (`response.headers`).
|
||||
Wenn du eine Anforderung mit „Octokit.js“ ausführst, gibt die Methode `request` eine Zusage zurück. Wenn die Anforderung erfolgreich war, wird die Zusage in ein Objekt aufgelöst, das den HTTP-Statuscode der Antwort (`status`) und die Antwortheader (`headers`) enthält. Wenn ein Fehler auftritt, wird die Zusage in ein Objekt aufgelöst, das den HTTP-Statuscode der Antwort (`status`) und die Antwortheader (`response.headers`) enthält.
|
||||
|
||||
You can use a `try/catch` block to catch an error if it occurs. For example, if the request in the following script is successful, the script will log the status code and the value of the `x-ratelimit-remaining` header. If the request was not successful, the script will log the status code, the value of the `x-ratelimit-remaining` header, and the error message.
|
||||
Du kannst einen `try/catch`-Block verwenden, um einen eventuell auftretenden Fehler abzufangen. Wenn die Anforderung im folgenden Skript beispielsweise erfolgreich ist, protokolliert das Skript den Statuscode und den Wert des `x-ratelimit-remaining`-Headers. War die Anforderung nicht erfolgreich, protokolliert das Skript den Statuscode, den Wert des `x-ratelimit-remaining`-Headers und die Fehlermeldung.
|
||||
|
||||
```javascript
|
||||
try {
|
||||
@@ -607,9 +606,9 @@ try {
|
||||
|
||||
{% curl %}
|
||||
|
||||
To view the status code and headers, use the `--include` or `--i` flag when you send your request.
|
||||
Um den Statuscode und die Header anzuzeigen, verwende beim Senden deiner Anforderung das Flag `--include` oder `--i`.
|
||||
|
||||
For example, this request:
|
||||
Betrachte beispielsweise die folgende Anforderung:
|
||||
|
||||
```shell
|
||||
curl --request GET \
|
||||
@@ -619,7 +618,7 @@ curl --request GET \
|
||||
--include
|
||||
```
|
||||
|
||||
returns the response code and headers like:
|
||||
Sie gibt den Antwortcode und Header wie folgt zurück:
|
||||
|
||||
```shell
|
||||
HTTP/2 200
|
||||
@@ -649,13 +648,13 @@ content-length: 4936
|
||||
x-github-request-id: 14E0:4BC6:F1B8BA:208E317:62EC2715
|
||||
```
|
||||
|
||||
In this example, the response code is `200`, which indicates a successful request.
|
||||
In diesem Beispiel lautet der Antwortcode `200`, d. h. die Anforderung war erfolgreich.
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
### About the response body
|
||||
### Informationen zum Antworttext
|
||||
|
||||
Many operations will return a response body. Unless otherwise specified, the response body is in JSON format. For example, this request returns a list of issues with data about each issue:
|
||||
Bei vielen Vorgängen wird ein Antworttext zurückgegeben. Sofern nicht anders angegeben, verwendet der Antworttext das JSON-Format. Diese Anforderung liefert zum Beispiel eine Liste von Issues mit Daten zu jedem Issue:
|
||||
|
||||
{% cli %}
|
||||
|
||||
@@ -688,23 +687,23 @@ curl --request GET \
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
Unlike the GraphQL API where you specify what information you want, the REST API typically returns more information than you need. If desired, you can parse the response to pull out specific pieces of information.
|
||||
Im Gegensatz zur GraphQL-API, bei der du die gewünschten Informationen angibst, liefert die REST-API in der Regel mehr Informationen als du benötigst. Falls gewünscht, kannst du die Antwort analysieren, um bestimmte Informationen herauszufiltern.
|
||||
|
||||
{% cli %}
|
||||
|
||||
For example, you can use `>` to redirect the response to a file:
|
||||
Du kannst zum Beispiel `>` verwenden, um die Antwort in eine Datei umzuleiten:
|
||||
|
||||
```shell
|
||||
gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues -F per_page=2 > data.json
|
||||
```
|
||||
|
||||
Then you can use jq to get the title and author ID of each issue:
|
||||
Dann kannst mit jq den Titel und die Autoren-ID für jedes Issue abrufen:
|
||||
|
||||
```shell
|
||||
jq '.[] | {title: .title, authorID: .user.id}' data.json
|
||||
```
|
||||
|
||||
The previous two commands return something like:
|
||||
Die beiden vorherigen Befehle liefern eine Ausgabe ähnlich der folgenden:
|
||||
|
||||
```
|
||||
{
|
||||
@@ -717,13 +716,13 @@ The previous two commands return something like:
|
||||
}
|
||||
```
|
||||
|
||||
For more information about jq, see [the jq documentation](https://stedolan.github.io/jq/) and [jq play](https://jqplay.org/).
|
||||
Weitere Informationen zu jq findest du in der [jq-Dokumentation](https://stedolan.github.io/jq/) und unter [jq play](https://jqplay.org/).
|
||||
|
||||
{% endcli %}
|
||||
|
||||
{% javascript %}
|
||||
|
||||
For example, you can get the title and author ID of each issue:
|
||||
Du kannst zum Beispiel den Titel und die Autoren-ID für jedes Issue abrufen:
|
||||
|
||||
```javascript
|
||||
try {
|
||||
@@ -746,7 +745,7 @@ try {
|
||||
|
||||
{% curl %}
|
||||
|
||||
For example, you can use `>` to redirect the response to a file:
|
||||
Du kannst zum Beispiel `>` verwenden, um die Antwort in eine Datei umzuleiten:
|
||||
|
||||
```shell
|
||||
curl --request GET \
|
||||
@@ -755,13 +754,13 @@ curl --request GET \
|
||||
--header "Authorization: Bearer YOUR-TOKEN" > data.json
|
||||
```
|
||||
|
||||
Then you can use jq to get the title and author ID of each issue:
|
||||
Dann kannst mit jq den Titel und die Autoren-ID für jedes Issue abrufen:
|
||||
|
||||
```shell
|
||||
jq '.[] | {title: .title, authorID: .user.id}' data.json
|
||||
```
|
||||
|
||||
The previous two commands return something like:
|
||||
Die beiden vorherigen Befehle liefern eine Ausgabe ähnlich der folgenden:
|
||||
|
||||
```
|
||||
{
|
||||
@@ -774,12 +773,12 @@ The previous two commands return something like:
|
||||
}
|
||||
```
|
||||
|
||||
For more information about jq, see [the jq documentation](https://stedolan.github.io/jq/) and [jq play](https://jqplay.org/).
|
||||
Weitere Informationen zu jq findest du in der [jq-Dokumentation](https://stedolan.github.io/jq/) und unter [jq play](https://jqplay.org/).
|
||||
|
||||
{% endcurl %}
|
||||
|
||||
## Next steps
|
||||
## Nächste Schritte
|
||||
|
||||
This article demonstrated how to list and create issues in a repository. For more practice, try to comment on an issue, edit the title of an issue, or close an issue. For more information about these operations, see "[Create an issue comment](/rest/issues#create-an-issue-comment)" and "[Update an issue](/rest/issues/issues#update-an-issue)."
|
||||
In diesem Artikel wurde gezeigt, wie du Issues in einem Repository auflisten und erstellen kannst. Um mehr Übung zu bekommen, kannst du versuchen, ein Issue zu kommentieren, den Titel eines Issue zu bearbeiten oder ein Issue zu schließen. Weitere Informationen zu diesen Vorgängen findest du unter [Erstellen eines Kommentars zu einem Issue](/rest/issues#create-an-issue-comment) und [Aktualisieren eines Issues](/rest/issues/issues#update-an-issue).
|
||||
|
||||
For more information about the operations that you can use, see the [REST reference documentation](/rest).
|
||||
Weitere Informationen zu den Vorgängen, die du verwenden kannst, findest du in der [REST-Referenzdokumentation](/rest).
|
||||
|
||||
54
translations/de-DE/content/rest/overview/api-versions.md
Normal file
54
translations/de-DE/content/rest/overview/api-versions.md
Normal file
@@ -0,0 +1,54 @@
|
||||
---
|
||||
title: API-Versionen
|
||||
shortTitle: API Versions
|
||||
intro: 'Bei jeder Anforderung an die REST-API musst du angeben, welche Version der REST-API verwendet werden soll.'
|
||||
versions:
|
||||
feature: api-date-versioning
|
||||
ms.openlocfilehash: c1209120fab4c4cc26962991ad48b76638627db5
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184404'
|
||||
---
|
||||
## Informationen zur API-Versionsverwaltung
|
||||
|
||||
{% data reusables.rest-api.about-api-versions %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## Informationen zur {% data variables.product.prodname_ghe_server %}-Versionsverwaltung und REST-API-Versionsverwaltung
|
||||
|
||||
{% data variables.product.prodname_ghe_server %}-Versionen sind von REST-API-Versionen entkoppelt. Du kannst ein Upgrade deiner {% data variables.product.prodname_ghe_server %}-Version durchführen, aber dieselbe REST-API-Version beibehalten, solange die API-Version in der {% data variables.product.prodname_ghe_server %}-Version enthalten ist. Ebenso kannst du ein Upgrade deiner REST-API-Version durchführen, ohne deine {% data variables.product.prodname_ghe_server %}-Version zu aktualisieren, solange die von dir ausgewählte neue REST-API-Version für deine {% data variables.product.prodname_ghe_server %}-Version verfügbar ist.
|
||||
|
||||
In den {% data variables.product.prodname_ghe_server %}-Versionshinweisen ist angegeben, wenn eine REST-API-Version nicht mehr unterstützt wird. Weitere Informationen findest du in den „[Versionshinweisen](/admin/release-notes)“.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Angeben einer API-Version
|
||||
|
||||
Du solltest den `X-GitHub-Api-Version`-Header verwenden, um eine API-Version anzugeben. Beispiel:
|
||||
|
||||
```shell
|
||||
$ curl {% data reusables.rest-api.version-header %} https://api.github.com/zen
|
||||
```
|
||||
|
||||
Anforderungen ohne `X-GitHub-Api-Version`-Header verwenden standardmäßig die Version `{{ initialRestVersioningReleaseDate }}`.
|
||||
|
||||
Wenn du eine API-Version angibst, die nicht mehr unterstützt wird, wird eine `400` Fehlermeldung angezeigt.
|
||||
|
||||
## Upgrade auf eine neue API-Version
|
||||
|
||||
Bevor du ein Upgrade auf eine neue REST-API-Version durchführst, solltest du das Änderungsprotokoll der Breaking Changes lesen, um zu verstehen, welche Breaking Changes enthalten sind und um weitere Informationen über das Upgrade auf diese bestimmte API-Version zu erhalten. Weitere Informationen findest du unter „[Breaking Changes](/rest/overview/breaking-changes)“.
|
||||
|
||||
Wenn du deine Integration aktualisierst, um die neue API-Version im Header `X-GitHub-Api-Version` anzugeben, musst du auch alle erforderlichen Änderungen vornehmen, damit deine Integration mit der neuen API-Version funktioniert.
|
||||
|
||||
Sobald deine Integration aktualisiert ist, teste sie, um zu überprüfen, ob sie mit der neuen API-Version funktioniert.
|
||||
|
||||
## Unterstützte API-Versionen
|
||||
|
||||
Die folgenden REST-API-Versionen werden derzeit unterstützt:
|
||||
|
||||
{% for apiVersion in allVersions[currentVersion].apiVersions %} {{ apiVersion }} {% endfor %}
|
||||
|
||||
Du kannst auch eine API-Anforderung stellen, um alle unterstützten API-Versionen abzurufen. Weitere Informationen findest du unter „[Abrufen aller API-Versionen](/rest/meta#get-all-api-versions)“.
|
||||
30
translations/de-DE/content/rest/overview/breaking-changes.md
Normal file
30
translations/de-DE/content/rest/overview/breaking-changes.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Aktuelle Änderungen
|
||||
shortTitle: Breaking changes
|
||||
intro: 'Erfahre mehr über die Breaking Changes, die in jeder REST-API-Version vorgenommen wurden.'
|
||||
versions:
|
||||
feature: api-date-versioning
|
||||
ms.openlocfilehash: 674345b82c5da9b0804fe4a0f62450ff4fbbc3e9
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184405'
|
||||
---
|
||||
## Informationen zu Breaking Changes in der REST-API
|
||||
|
||||
{% data reusables.rest-api.about-api-versions %}
|
||||
|
||||
Weitere Informationen zu API-Versionen findest du unter „[API-Versionen](/rest/overview/api-versions)“.
|
||||
|
||||
## Upgrade auf eine neue API-Version
|
||||
|
||||
Bevor du ein Upgrade auf eine neue REST-API-Version durchführst, solltest du den Abschnitt auf dieser Seite lesen, der der neuen API-Version entspricht, um zu verstehen, welche Breaking Changes enthalten sind und um weitere Informationen über das Upgrade auf diese API-Version zu erhalten.
|
||||
|
||||
Wenn du deine Integration aktualisierst, um die neue API-Version im Header `X-GitHub-Api-Version` anzugeben, musst du auch alle erforderlichen Änderungen vornehmen, damit deine Integration mit der neuen API-Version funktioniert.
|
||||
|
||||
Sobald deine Integration aktualisiert ist, teste sie, um zu überprüfen, ob sie mit der neuen API-Version funktioniert.
|
||||
|
||||
## Breaking Changes für {{ initialRestVersioningReleaseDate }}
|
||||
|
||||
Version `{{ initialRestVersioningReleaseDate }}` ist die erste Version der {% data variables.product.product_name %}-REST-API, nachdem die datumsbasierte Versionsverwaltung eingeführt wurde. Diese Version enthält keine Breaking Changes.
|
||||
@@ -5,12 +5,12 @@ versions:
|
||||
feature: pat-v2
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: '{% data variables.product.pat_v2_caps %} permissions'
|
||||
ms.openlocfilehash: 97154c54229f66f3a6b3bf852f7aabab89a0d2ee
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.openlocfilehash: 46a82b0212d4cda2b6883c0b33ba2acb2e50b9d0
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107685'
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184212'
|
||||
---
|
||||
## Informationen zu den erforderlichen Berechtigungen für {% data variables.product.pat_v2 %}
|
||||
|
||||
@@ -65,11 +65,10 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) (Schreiben)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) (Schreiben)
|
||||
- [`POST /orgs/{org}/repos`](/rest/reference/repos#create-an-organization-repository) (Schreiben)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/reference/repos/#update-a-repository) (Schreiben)
|
||||
- [`PATCH /repos/{owner}/{repo}`](/rest/repos/repos#update-a-repository) (Schreiben)
|
||||
- [`DELETE /repos/{owner}/{repo}`](/rest/reference/repos#delete-a-repository) (Schreiben)
|
||||
- [`POST /repos/{owner}/{repo}/forks`](/rest/reference/repos#create-a-fork) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/teams`](/rest/reference/repos#list-repository-teams) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/transfer`](/rest/reference/repos#transfer-a-repository) (Schreiben)
|
||||
- [`POST /user/repos`](/rest/reference/repos#create-a-repository-for-the-authenticated-user) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-a-repository) (Lesen)
|
||||
- [`PUT /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-a-repository) (Schreiben)
|
||||
@@ -130,16 +129,6 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
|
||||
## Prüfungen
|
||||
|
||||
- [`POST /repos/{owner}/{repo}/check-runs`](/rest/reference/checks#create-a-check-run) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#get-a-check-run) (Lesen)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#update-a-check-run) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations`](/rest/reference/checks#list-check-run-annotations) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/check-runs/{check_run_id}/rerequest`](/rest/reference/checks#rerequest-a-check-run) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites`](/rest/reference/checks#create-a-check-suite) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}`](/rest/reference/checks#get-a-check-suite) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/check-suites/{check_suite_id}/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (Schreiben)
|
||||
- [`PATCH /repos/{owner}/{repo}/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (Schreiben)
|
||||
- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#review-pending-deployments-for-a-workflow-run) (Lesen)
|
||||
|
||||
## Codespaces
|
||||
@@ -196,20 +185,12 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`POST /repos/{owner}/{repo}/git/refs`](/rest/reference/git#create-a-reference) (Schreiben)
|
||||
- [`POST /repos/{owner}/{repo}/git/tags`](/rest/reference/git#create-a-tag-object) (Schreiben)
|
||||
- [`POST /repos/{owner}/{repo}/git/trees`](/rest/reference/git#create-a-tree) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/import`](/rest/reference/migrations#get-an-import-status) (Lesen)
|
||||
- [`PUT /repos/{owner}/{repo}/import`](/rest/reference/migrations#start-an-import) (Schreiben)
|
||||
- [`PATCH /repos/{owner}/{repo}/import`](/rest/reference/migrations#update-an-import) (Schreiben)
|
||||
- [`DELETE /repos/{owner}/{repo}/import`](/rest/reference/migrations#cancel-an-import) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/import/authors`](/rest/reference/migrations#get-commit-authors) (Lesen)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/authors/{author_id}`](/rest/reference/migrations#map-a-commit-author) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/import/large_files`](/rest/reference/migrations#get-large-files) (Lesen)
|
||||
- [`PATCH /repos/{owner}/{repo}/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (Schreiben)
|
||||
- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#merge-a-pull-request) (Schreiben)
|
||||
- [`POST /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (Schreiben)
|
||||
- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-commit-comment-reaction) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/reference/repos#list-branches) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository) (Schreiben)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/reference/repos#merge-a-branch) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/branches`](/rest/branches/branches#list-branches) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/branches/branches#sync-a-fork-branch-with-the-upstream-repository) (Schreiben)
|
||||
- [`POST /repos/{owner}/{repo}/merges`](/rest/branches/branches#merge-a-branch) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases`](/rest/reference/code-scanning#list-codeql-databases) (Lesen)
|
||||
- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases/{language}`](/rest/reference/code-scanning#get-codeql-database) (Lesen)
|
||||
- [`PATCH /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#update-a-commit-comment) (Schreiben)
|
||||
@@ -320,7 +301,7 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`GET /repos/{owner}/{repo}/issues`](/rest/reference/issues#list-repository-issues) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/issues`](/rest/reference/issues#create-an-issue) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#get-an-issue) (Lesen)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues/#update-an-issue) (Schreiben)
|
||||
- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#update-an-issue) (Schreiben)
|
||||
- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#lock-an-issue) (Schreiben)
|
||||
- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#unlock-an-issue) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#list-labels-for-an-issue) (Lesen)
|
||||
@@ -409,7 +390,6 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`POST /gists/{gist_id}/forks`](/rest/reference/gists#fork-a-gist) (Lesen)
|
||||
- [`PUT /gists/{gist_id}/star`](/rest/reference/gists#star-a-gist) (Lesen)
|
||||
- [`DELETE /gists/{gist_id}/star`](/rest/reference/gists#unstar-a-gist) (Lesen)
|
||||
- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user) (Lesen)
|
||||
- [`GET /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#check-team-permissions-for-a-repository) (Lesen)
|
||||
- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) (Lesen)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) (Lesen)
|
||||
@@ -439,10 +419,6 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`GET /search/labels`](/rest/reference/search#search-labels) (Lesen)
|
||||
- [`GET /repos/{owner}/{repo}/topics`](/rest/reference/repos#get-all-repository-topics) (Lesen)
|
||||
|
||||
## Benachrichtigungen
|
||||
|
||||
- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user) (Lesen)
|
||||
|
||||
## Organisationsverwaltung
|
||||
|
||||
{% ifversion ghec %}: [`GET /orgs/{org}/audit-log`](/rest/reference/orgs#get-audit-log) (Lesen){% endif %}
|
||||
@@ -467,7 +443,7 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`GET /orgs/{org}/security-managers`](/rest/reference/orgs#list-security-manager-teams) (Lesen)
|
||||
- [`PUT /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#add-a-security-manager-team) (Schreiben)
|
||||
- [`DELETE /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#remove-a-security-manager-team) (Schreiben)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs/#update-an-organization) (Schreiben)
|
||||
- [`PATCH /orgs/{org}`](/rest/reference/orgs#update-an-organization) (Schreiben)
|
||||
- [`GET /orgs/{org}/installations`](/rest/reference/orgs#list-app-installations-for-an-organization) (Lesen)
|
||||
|
||||
## Organisationscodespaces
|
||||
@@ -491,6 +467,7 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
## Benutzerdefinierte Rollen für Organisationen
|
||||
|
||||
- [`GET /organizations/{organization_id}/custom_roles`](/rest/reference/orgs#list-custom-repository-roles-in-an-organization) (Lesen)
|
||||
- [`GET /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs/#get-a-custom-role) (Lesen)
|
||||
- [`PATCH /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#update-a-custom-role) (Schreiben)
|
||||
- [`DELETE /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#delete-a-custom-role) (Schreiben)
|
||||
- [`GET /orgs/{org}/fine_grained_permissions`](/rest/reference/orgs#list-fine-grained-permissions-for-an-organization) (Lesen)
|
||||
@@ -523,13 +500,6 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`POST /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/reference/orgs#redeliver-a-delivery-for-an-organization-webhook) (Schreiben)
|
||||
- [`POST /orgs/{org}/hooks/{hook_id}/pings`](/rest/reference/orgs#ping-an-organization-webhook) (Schreiben)
|
||||
|
||||
## Organisationsprojekte
|
||||
|
||||
- [`PUT /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#add-or-update-team-project-permissions) (Administrator)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#remove-a-project-from-a-team) (Administrator)
|
||||
- [`GET /orgs/{org}/projects`](/rest/reference/projects#list-organization-projects) (Lesen)
|
||||
- [`POST /orgs/{org}/projects`](/rest/reference/projects#create-an-organization-project) (Schreiben)
|
||||
|
||||
## Organisationsgeheimnisse
|
||||
|
||||
- [`GET /orgs/{org}/actions/secrets`](/rest/reference/actions#list-organization-secrets) (Lesen)
|
||||
@@ -640,30 +610,6 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/pings`](/rest/webhooks/repos#ping-a-repository-webhook) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/tests`](/rest/webhooks/repos#test-the-push-repository-webhook) (Lesen)
|
||||
|
||||
## Repositoryprojekte
|
||||
|
||||
- [`GET /projects/{project_id}/collaborators`](/rest/reference/projects#list-project-collaborators) (Schreiben)
|
||||
- [`PUT /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#add-project-collaborator) (Schreiben)
|
||||
- [`DELETE /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#remove-project-collaborator) (Schreiben)
|
||||
- [`GET /projects/{project_id}/collaborators/{username}/permission`](/rest/reference/projects#get-project-permission-for-a-user) (Schreiben)
|
||||
- [`GET /projects/{project_id}`](/rest/reference/projects#get-a-project) (Lesen)
|
||||
- [`PATCH /projects/{project_id}`](/rest/reference/projects#update-a-project) (Schreiben)
|
||||
- [`DELETE /projects/{project_id}`](/rest/reference/projects#delete-a-project) (Schreiben)
|
||||
- [`GET /projects/{project_id}/columns`](/rest/reference/projects#list-project-columns) (Lesen)
|
||||
- [`POST /projects/{project_id}/columns`](/rest/reference/projects#create-a-project-column) (Schreiben)
|
||||
- [`GET /projects/columns/{column_id}`](/rest/reference/projects#get-a-project-column) (Lesen)
|
||||
- [`PATCH /projects/columns/{column_id}`](/rest/reference/projects#update-a-project-column) (Schreiben)
|
||||
- [`DELETE /projects/columns/{column_id}`](/rest/reference/projects#delete-a-project-column) (Schreiben)
|
||||
- [`GET /projects/columns/{column_id}/cards`](/rest/reference/projects#list-project-cards) (Lesen)
|
||||
- [`POST /projects/columns/{column_id}/cards`](/rest/reference/projects#create-a-project-card) (Schreiben)
|
||||
- [`POST /projects/columns/{column_id}/moves`](/rest/reference/projects#move-a-project-column) (Schreiben)
|
||||
- [`GET /projects/columns/cards/{card_id}`](/rest/reference/projects#get-a-project-card) (Lesen)
|
||||
- [`PATCH /projects/columns/cards/{card_id}`](/rest/reference/projects#update-a-project-card) (Schreiben)
|
||||
- [`DELETE /projects/columns/cards/{card_id}`](/rest/reference/projects#delete-a-project-card) (Schreiben)
|
||||
- [`POST /projects/columns/cards/{card_id}/moves`](/rest/reference/projects#move-a-project-card) (Schreiben)
|
||||
- [`GET /repos/{owner}/{repo}/projects`](/rest/reference/projects#list-repository-projects) (Lesen)
|
||||
- [`POST /repos/{owner}/{repo}/projects`](/rest/reference/projects#create-a-repository-project) (Schreiben)
|
||||
|
||||
## Geheimnisscanwarnungen
|
||||
|
||||
- [`GET /orgs/{org}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-organization) (Lesen)
|
||||
@@ -727,6 +673,10 @@ Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm besti
|
||||
- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#update-a-discussion-comment) (Schreiben)
|
||||
- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#delete-a-discussion-comment) (Schreiben)
|
||||
|
||||
## Warnungen zu Sicherheitsrisiken
|
||||
|
||||
- [`GET /orgs/{org}/dependabot/alerts`](/rest/dependabot/alerts#list-dependabot-alerts-for-an-organization) (Lesen)
|
||||
|
||||
## Watching (Überwachung)
|
||||
|
||||
- [`GET /users/{username}/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) (Lesen)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Resources in the REST API
|
||||
intro: 'Learn how to navigate the resources provided by the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
|
||||
title: Ressourcen in der REST-API
|
||||
intro: 'Hier erfährst du, wie du mit den von der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API bereitgestellten Ressourcen umgehst.'
|
||||
redirect_from:
|
||||
- /rest/initialize-the-repo
|
||||
versions:
|
||||
@@ -11,19 +11,23 @@ versions:
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4fd3e2aad72ee0ffc4778a86dc99cd5bb6f9d2c5
|
||||
ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190399'
|
||||
---
|
||||
|
||||
{% ifversion api-date-versioning %}
|
||||
## API version
|
||||
## API-Version
|
||||
|
||||
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)."
|
||||
Die verfügbaren Ressourcen können sich je nach REST-API-Version unterscheiden. Du solltest den `X-GitHub-Api-Version`-Header verwenden, um eine API-Version anzugeben. Weitere Informationen findest du unter [API-Versionen](/rest/overview/api-versions).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Schema
|
||||
|
||||
{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`. All data is
|
||||
sent and received as JSON.
|
||||
{% ifversion fpt or ghec %}Der gesamte API-Zugriff erfolgt über HTTPS und{% else %}auf die API wird{% endif %} über `{% data variables.product.api_url_code %}` zugegriffen. Alle Daten werden im JSON-Format gesendet und empfangen.
|
||||
|
||||
```shell
|
||||
$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
|
||||
@@ -44,55 +48,45 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
|
||||
> X-Content-Type-Options: nosniff
|
||||
```
|
||||
|
||||
Blank fields are included as `null` instead of being omitted.
|
||||
Leere Felder werden mit `null` angegeben anstatt ausgelassen zu werden.
|
||||
|
||||
All timestamps return in UTC time, ISO 8601 format:
|
||||
Alle Zeitstempel werden im UTC-Zeitformat im ISO 8601-Format zurückgegeben:
|
||||
|
||||
YYYY-MM-DDTHH:MM:SSZ
|
||||
|
||||
For more information about timezones in timestamps, see [this section](#timezones).
|
||||
Weitere Informationen zu Zeitzonen in Zeitstempeln findest du in [diesem Abschnitt](#timezones).
|
||||
|
||||
### Summary representations
|
||||
### Zusammenfassungsdarstellungen
|
||||
|
||||
When you fetch a list of resources, the response includes a _subset_ of the
|
||||
attributes for that resource. This is the "summary" representation of the
|
||||
resource. (Some attributes are computationally expensive for the API to provide.
|
||||
For performance reasons, the summary representation excludes those attributes.
|
||||
To obtain those attributes, fetch the "detailed" representation.)
|
||||
Wenn du eine Liste von Ressourcen abrufst, enthält die Antwort eine _Teilmenge_ der Attribute für diese Ressource. Dies ist die „Zusammenfassungsdarstellung“ der Ressource. (Einige Attribute sind für die zu bereitstellende API berechnungsintensiv.
|
||||
Aus Leistungsgründen schließt die Zusammenfassungsdarstellung diese Attribute aus.
|
||||
Um diese Attribute abzurufen, ruf die „detaillierte“ Darstellung ab.)
|
||||
|
||||
**Example**: When you get a list of repositories, you get the summary
|
||||
representation of each repository. Here, we fetch the list of repositories owned
|
||||
by the [octokit](https://github.com/octokit) organization:
|
||||
**Beispiel:** Wenn du eine Liste von Repositorys erhältst, erhältst du die Zusammenfassungsdarstellung jedes Repositorys. Hier wird die Liste der Repositorys abgerufen, die der Organisation [octokit](https://github.com/octokit) gehört:
|
||||
|
||||
GET /orgs/octokit/repos
|
||||
|
||||
### Detailed representations
|
||||
### Detaillierte Darstellungen
|
||||
|
||||
When you fetch an individual resource, the response typically includes _all_
|
||||
attributes for that resource. This is the "detailed" representation of the
|
||||
resource. (Note that authorization sometimes influences the amount of detail
|
||||
included in the representation.)
|
||||
Wenn du eine einzelne Ressource abrufst, enthält die Antwort normalerweise _alle_ Attribute für diese Ressource. Dies ist die „detaillierte“ Darstellung der Ressource. (Beachte, dass die Autorisierung manchmal die Anzahl der Details in der Darstellung beeinflusst.)
|
||||
|
||||
**Example**: When you get an individual repository, you get the detailed
|
||||
representation of the repository. Here, we fetch the
|
||||
[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository:
|
||||
**Beispiel:** Wenn du ein einzelnes Repository erhältst, erhältst du die detaillierte Darstellung des Repositorys. Hier rufst du das Repository [octokit/octokit.rb](https://github.com/octokit/octokit.rb) ab:
|
||||
|
||||
GET /repos/octokit/octokit.rb
|
||||
|
||||
The documentation provides an example response for each API method. The example
|
||||
response illustrates all attributes that are returned by that method.
|
||||
Die Dokumentation enthält eine Beispielantwort für jede API-Methode. Die Beispielantwort zeigt alle Attribute an, die von dieser Methode zurückgegeben werden.
|
||||
|
||||
## Authentication
|
||||
## Authentifizierung
|
||||
|
||||
{% ifversion ghae %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places. This is to prevent the accidental leakage of private repositories to unauthorized users.
|
||||
{% ifversion ghae %} Es wird empfohlen, dich bei der {% data variables.product.product_name %}-REST-API zu authentifizieren, indem du über den [Webanwendungsfluss](/developers/apps/authorizing-oauth-apps#web-application-flow) ein OAuth2-Token erstellst. {% else %} Es gibt zwei Möglichkeiten, die Authentifizierung über die {% data variables.product.product_name %}-REST-API durchzuführen.{% endif %} Anforderungen, die eine Authentifizierung erfordern, geben an einigen Stellen `404 Not Found` anstelle von `403 Forbidden` zurück. Auf diese Weise soll die versehentliche Veröffentlichung privater Repositorys für nicht autorisierte Benutzer*innen verhindert werden.
|
||||
|
||||
### Basic authentication
|
||||
### Standardauthentifizierung
|
||||
|
||||
```shell
|
||||
$ curl -u "username" {% data variables.product.api_url_pre %}
|
||||
```
|
||||
|
||||
### OAuth2 token (sent in a header)
|
||||
### OAuth2-Token (gesendet in einem Header)
|
||||
|
||||
```shell
|
||||
$ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}
|
||||
@@ -100,20 +94,20 @@ $ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_
|
||||
|
||||
{% note %}
|
||||
|
||||
Note: GitHub recommends sending OAuth tokens using the Authorization header.
|
||||
Hinweis: GitHub empfiehlt das Senden von OAuth-Token mithilfe des Autorisierungsheaders.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.getting-started.bearer-vs-token %}
|
||||
**Hinweis:** {% data reusables.getting-started.bearer-vs-token %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications.
|
||||
Informiere dich weiter über [OAuth2](/apps/building-oauth-apps/). Beachte, dass OAuth2-Token mithilfe des [Webanwendungsflow](/developers/apps/authorizing-oauth-apps#web-application-flow) für Produktionsanwendungen abgerufen werden können.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
### OAuth2 key/secret
|
||||
### OAuth2-Schlüssel bzw. -Geheimnis
|
||||
|
||||
{% data reusables.apps.deprecating_auth_with_query_parameters %}
|
||||
|
||||
@@ -121,22 +115,20 @@ Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens c
|
||||
curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos'
|
||||
```
|
||||
|
||||
Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth App to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth App's client secret to your users.
|
||||
Wenn du deine `client_id` und dein `client_secret` verwendest, wirst du _nicht_ als Benutzer*in authentifiziert. Stattdessen wird nur deine OAuth-App identifiziert, um deine Ratenbegrenzung zu erhöhen. Berechtigungen werden nur Benutzer*innen und keinen Anwendungen gewährt. Zudem erhältst du nur Daten, die nicht authentifizierte Benutzer*innen sehen würden. Aus diesem Grund solltest du nur den OAuth2-Schlüssel bzw. das OAuth2-Geheimnis in Server-zu-Server-Szenarios verwenden. Veröffentliche den geheimen Clientschlüssel deiner OAuth-App nicht für deine Benutzer*innen.
|
||||
|
||||
{% ifversion ghes %}
|
||||
You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
{% ifversion ghes %} Im privaten Modus kannst du dich nicht mit deinem OAuth2-Schlüssel bzw. -Geheimnis authentifizieren, und bei einem Authentifizierungsversuch wird `401 Unauthorized` zurückgegeben. Weitere Informationen findest du unter [Aktivieren des privaten Modus](/admin/configuration/configuring-your-enterprise/enabling-private-mode).
|
||||
{% endif %} {% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps).
|
||||
Informiere dich weiter über die [nicht authentifizierte Ratenbegrenzung](#increasing-the-unauthenticated-rate-limit-for-oauth-apps).
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Failed login limit
|
||||
### Grenzwert für fehlgeschlagene Anmeldeversuche
|
||||
|
||||
Authenticating with invalid credentials will return `401 Unauthorized`:
|
||||
Bei der Authentifizierung mit ungültigen Anmeldeinformationen wird `401 Unauthorized` zurückgegeben:
|
||||
|
||||
```shell
|
||||
$ curl -I {% data variables.product.api_url_pre %} -u foo:bar
|
||||
@@ -148,9 +140,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
|
||||
> }
|
||||
```
|
||||
|
||||
After detecting several requests with invalid credentials within a short period,
|
||||
the API will temporarily reject all authentication attempts for that user
|
||||
(including ones with valid credentials) with `403 Forbidden`:
|
||||
Nach der Erkennung mehrerer Anforderungen mit ungültigen Anmeldeinformationen innerhalb eines kurzen Zeitraums lehnt die API vorübergehend alle Authentifizierungsversuche für diese*n Benutzer*in (auch Benutzer*innen mit gültigen Anmeldeinformationen) mit der Fehlermeldung `403 Forbidden` ab:
|
||||
|
||||
```shell
|
||||
$ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae or ghec %}
|
||||
@@ -162,62 +152,55 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae o
|
||||
> }
|
||||
```
|
||||
|
||||
## Parameters
|
||||
## Parameter
|
||||
|
||||
Many API methods take optional parameters. For `GET` requests, any parameters not
|
||||
specified as a segment in the path can be passed as an HTTP query string
|
||||
parameter:
|
||||
Viele API-Methoden verwenden optionale Parameter. Für `GET`-Anforderungen können alle Parameter, die nicht als Segment im Pfad angegeben werden, als HTTP-Abfragezeichenfolgenparameter übergeben werden:
|
||||
|
||||
```shell
|
||||
$ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed"
|
||||
```
|
||||
|
||||
In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner`
|
||||
and `:repo` parameters in the path while `:state` is passed in the query
|
||||
string.
|
||||
In diesem Beispiel werden die Werte „vmg“ und „redcarpet“ für die Parameter `:owner` und `:repo` im Pfad angegeben, während `:state` in der Abfragezeichenfolge übergeben wird.
|
||||
|
||||
For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON
|
||||
with a Content-Type of 'application/json':
|
||||
Für die Anforderungen `POST`, `PATCH`, `PUT` und `DELETE` sollten Parameter, die nicht in der URL enthalten sind, als JSON mit einem Inhaltstyp von „application/json“ codiert werden:
|
||||
|
||||
```shell
|
||||
$ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations
|
||||
```
|
||||
|
||||
## Root endpoint
|
||||
## Stammendpunkt
|
||||
|
||||
You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports:
|
||||
Du kannst eine `GET`-Anforderung an den Stammendpunkt stellen, um alle Endpunktkategorien abzurufen, die die REST-API unterstützt:
|
||||
|
||||
```shell
|
||||
$ curl {% ifversion fpt or ghae or ghec %}
|
||||
-u USERNAME:TOKEN {% endif %}{% ifversion ghes %}-u USERNAME:PASSWORD {% endif %}{% data variables.product.api_url_pre %}
|
||||
```
|
||||
|
||||
## GraphQL global node IDs
|
||||
## Globale GraphQL-Knoten-IDs
|
||||
|
||||
See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations.
|
||||
Weitere Informationen zum Suchen von [-Elementen über die REST-API und die Verwendung in GraphQL-Vorgängen findest du in der Anleitung zur ](/graphql/guides/using-global-node-ids)Verwendung globaler Knoten-IDs`node_id`.
|
||||
|
||||
## Client errors
|
||||
## Clientfehler
|
||||
|
||||
There are three possible types of client errors on API calls that
|
||||
receive request bodies:
|
||||
Es gibt drei mögliche Arten von Clientfehlern bei API-Aufrufen, die Anforderungstexte erhalten:
|
||||
|
||||
1. Sending invalid JSON will result in a `400 Bad Request` response.
|
||||
1. Das Senden ungültiger JSON-Daten führt zu einer `400 Bad Request`-Antwort.
|
||||
|
||||
HTTP/2 400
|
||||
Content-Length: 35
|
||||
|
||||
{"message":"Problems parsing JSON"}
|
||||
|
||||
2. Sending the wrong type of JSON values will result in a `400 Bad
|
||||
Request` response.
|
||||
2. Das Senden des falschen Typs von JSON-Werten führt zu einer `400 Bad
|
||||
Request`-Antwort.
|
||||
|
||||
HTTP/2 400
|
||||
Content-Length: 40
|
||||
|
||||
{"message":"Body should be a JSON object"}
|
||||
|
||||
3. Sending invalid fields will result in a `422 Unprocessable Entity`
|
||||
response.
|
||||
3. Das Senden ungültiger Felder führt zu einer `422 Unprocessable Entity`-Antwort.
|
||||
|
||||
HTTP/2 422
|
||||
Content-Length: 149
|
||||
@@ -233,60 +216,47 @@ receive request bodies:
|
||||
]
|
||||
}
|
||||
|
||||
All error objects have resource and field properties so that your client
|
||||
can tell what the problem is. There's also an error code to let you
|
||||
know what is wrong with the field. These are the possible validation error
|
||||
codes:
|
||||
Alle Fehlerobjekte verfügen über Ressourcen- und Feldeigenschaften, damit dein Client genauere Angaben zum Problem machen kann. Es gibt auch einen Fehlercode, um Ihnen mitzuteilen, welches Problem im Zusammenhang mit dem Feld vorliegt. Dies sind die möglichen Überprüfungsfehlercodes:
|
||||
|
||||
Error code name | Description
|
||||
Fehlercodename | BESCHREIBUNG
|
||||
-----------|-----------|
|
||||
`missing` | A resource does not exist.
|
||||
`missing_field` | A required field on a resource has not been set.
|
||||
`invalid` | The formatting of a field is invalid. Review the documentation for more specific information.
|
||||
`already_exists` | Another resource has the same value as this field. This can happen in resources that must have some unique key (such as label names).
|
||||
`unprocessable` | The inputs provided were invalid.
|
||||
`missing` | Eine Ressource ist nicht vorhanden.
|
||||
`missing_field` | Ein erforderliches Feld für eine Ressource wurde nicht festgelegt.
|
||||
`invalid` | Die Formatierung eines Felds ist ungültig. Weitere spezifische Informationen findest du in der Dokumentation.
|
||||
`already_exists` | Eine andere Ressource hat den gleichen Wert wie dieses Feld. Dies kann bei Ressourcen der Fall sein, die einen eindeutigen Schlüssel haben müssen (z. B. Bezeichnungsnamen).
|
||||
`unprocessable` | Die bereitgestellten Eingaben waren ungültig.
|
||||
|
||||
Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error.
|
||||
Ressourcen können auch benutzerdefinierte Überprüfungsfehler senden (wobei `code` `custom` entspricht). Benutzerdefinierte Fehler enthalten immer ein `message`-Feld, in dem der Fehler beschrieben wird. Die meisten Fehler umfassen zudem ein `documentation_url`-Feld, in dem auf Inhalte verwiesen wird, die beim Beheben des Fehlers helfen können.
|
||||
|
||||
## HTTP redirects
|
||||
## HTTP-Umleitungen
|
||||
|
||||
The {% data variables.product.product_name %} REST API uses HTTP redirection where appropriate. Clients should assume that any
|
||||
request may result in a redirection. Receiving an HTTP redirection is *not* an
|
||||
error and clients should follow that redirect. Redirect responses will have a
|
||||
`Location` header field which contains the URI of the resource to which the
|
||||
client should repeat the requests.
|
||||
Die {% data variables.product.product_name %}-REST-API verwendet ggf. die HTTP-Umleitung. Clients sollten davon ausgehen, dass jede Anforderung zu einer Umleitung führen kann. Der Empfang einer HTTP-Umleitung ist *kein* Fehler, und Clients sollten dieser Umleitung folgen. Umleitungsantworten verfügen über ein `Location`-Headerfeld, das den URI der Ressource enthält, für die der Client die Anforderungen wiederholen sollte.
|
||||
|
||||
Status Code | Description
|
||||
Statuscode | BESCHREIBUNG
|
||||
-----------|-----------|
|
||||
`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI.
|
||||
`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests.
|
||||
`301` | Permanente Umleitung. Der URI, den du zum Erstellen der Anforderung verwendet hast, wurde durch den im `Location`-Headerfeld angegebenen URI ersetzt. Diese und alle zukünftigen Anforderungen an diese Ressource sollten an den neuen URI weitergeleitet werden.
|
||||
`302`, `307` | Temporäre Umleitung. Die Anforderung sollte für den im `Location`-Headerfeld angegebenen URI unverändert wiederholt werden, aber die Clients sollten weiterhin den ursprünglichen URI für zukünftige Anforderungen verwenden.
|
||||
|
||||
Other redirection status codes may be used in accordance with the HTTP 1.1 spec.
|
||||
Andere Umleitungsstatuscodes können gemäß der HTTP 1.1-Spezifikation verwendet werden.
|
||||
|
||||
## HTTP verbs
|
||||
## HTTP-Verben
|
||||
|
||||
Where possible, the {% data variables.product.product_name %} REST API strives to use appropriate HTTP verbs for each
|
||||
action. Note that HTTP verbs are case-sensitive.
|
||||
Sofern möglich, bemüht sich die {% data variables.product.product_name %}-REST-API, geeignete HTTP-Verben für jede Aktion zu verwenden. Bei HTTP-Verben muss Groß-/Kleinschreibung beachtet werden.
|
||||
|
||||
Verb | Description
|
||||
Verb | BESCHREIBUNG
|
||||
-----|-----------
|
||||
`HEAD` | Can be issued against any resource to get just the HTTP header info.
|
||||
`GET` | Used for retrieving resources.
|
||||
`POST` | Used for creating resources.
|
||||
`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource.
|
||||
`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero.
|
||||
`DELETE` |Used for deleting resources.
|
||||
`HEAD` | Kann für jede Ressource ausgestellt werden, um nur die HTTP-Headerinformationen abzurufen.
|
||||
`GET` | Wird zum Abrufen von Ressourcen verwendet.
|
||||
`POST` | Wird zum Erstellen von Ressourcen verwendet.
|
||||
`PATCH` | Wird zum Aktualisieren von Ressourcen mit teilweisen JSON-Daten verwendet. Beispielsweise verfügt eine Issue-Ressource über die Attribute `title` und `body`. Eine `PATCH`-Anforderung kann eines oder mehrere der Attribute akzeptieren, um die Ressource zu aktualisieren.
|
||||
`PUT` | Wird zum Ersetzen von Ressourcen oder Sammlungen verwendet. Stelle für `PUT`-Anforderungen ohne `body`-Attribut sicher, dass der `Content-Length`-Header auf null (0) festgelegt wird.
|
||||
`DELETE` |Wird zum Löschen von Ressourcen verwendet.
|
||||
|
||||
## Hypermedia
|
||||
|
||||
All resources may have one or more `*_url` properties linking to other
|
||||
resources. These are meant to provide explicit URLs so that proper API clients
|
||||
don't need to construct URLs on their own. It is highly recommended that API
|
||||
clients use these. Doing so will make future upgrades of the API easier for
|
||||
developers. All URLs are expected to be proper [RFC 6570][rfc] URI templates.
|
||||
Alle Ressourcen verfügen möglicherweise über eine oder mehrere `*_url`-Eigenschaften, die sie mit anderen Ressourcen verknüpfen. Hiermit sollen explizite URLs bereitgestellt werden, damit richtige API-Clients keine URLs selbst erstellen müssen. Es wird dringend empfohlen, dass API-Clients diese verwenden. Auf diese Weise werden zukünftige Upgrades der API für Entwickler*innen einfacher. Es wird erwartet, dass alle URLs ordnungsgemäße [RFC 6570][rfc]-URI-Vorlagen sind.
|
||||
|
||||
You can then expand these templates using something like the [uri_template][uri]
|
||||
gem:
|
||||
Anschließend kannst du diese Vorlagen mithilfe des [uri_template][uri]-Gems erweitern:
|
||||
|
||||
>> tmpl = URITemplate.new('/notifications{?since,all,participating}')
|
||||
>> tmpl.expand
|
||||
@@ -301,60 +271,56 @@ gem:
|
||||
[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
|
||||
[uri]: https://github.com/hannesg/uri_template
|
||||
|
||||
## Pagination
|
||||
## Paginierung
|
||||
|
||||
Requests that return multiple items will be paginated to 30 items by
|
||||
default. You can specify further pages with the `page` parameter. For some
|
||||
resources, you can also set a custom page size up to 100 with the `per_page` parameter.
|
||||
Note that for technical reasons not all endpoints respect the `per_page` parameter,
|
||||
see [events](/rest/reference/activity#events) for example.
|
||||
Anforderungen, die mehrere Elemente zurückgeben, werden standardmäßig auf 30 Elemente paginiert. Du kannst weitere Seiten mit dem `page`-Parameter angeben. Für einige Ressourcen kannst du mit dem `per_page`-Parameter auch eine benutzerdefinierte Seitengröße bis 100 festlegen.
|
||||
Beachte, dass aus technischen Gründen nicht alle Endpunkte den `per_page`-Parameter berücksichtigen (siehe [Ereignisse](/rest/reference/activity#events) für ein Beispiel).
|
||||
|
||||
```shell
|
||||
$ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100'
|
||||
```
|
||||
|
||||
Note that page numbering is 1-based and that omitting the `page`
|
||||
parameter will return the first page.
|
||||
Beachte, dass die Seitennummerierung 1-basiert ist und die erste Seite zurückgegeben wird, wenn der `page`-Parameter ausgelassen wird.
|
||||
|
||||
Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set.
|
||||
With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page.
|
||||
Instead, you can traverse the results by using the `before` or `after` parameters.
|
||||
Einige Endpunkte verwenden die cursorbasierte Paginierung. Ein Cursor ist eine Zeichenfolge, die auf einen Speicherort im Resultset verweist.
|
||||
Bei der cursorbasierten Paginierung gibt es kein festes Konzept von „Seiten“ im Resultset, sodass du nicht zu einer bestimmten Seite navigieren kannst.
|
||||
Stattdessen kannst du die Ergebnisse mithilfe des Parameters `before` oder `after` durchlaufen.
|
||||
|
||||
For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide].
|
||||
Weitere Informationen zur Paginierung findest du im Leitfaden zum [Durchlaufen mit der Paginierung][pagination-guide].
|
||||
|
||||
### Link header
|
||||
### Link-Header
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** It's important to form calls with Link header values instead of constructing your own URLs.
|
||||
**Hinweis:** Es ist wichtig, Aufrufe mit Link-Headerwerten zu erstellen, anstatt eigene URLs zu erstellen.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. For example:
|
||||
Der [Link-Header](https://datatracker.ietf.org/doc/html/rfc5988) enthält Paginierungsinformationen. Beispiel:
|
||||
|
||||
Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next",
|
||||
<{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last"
|
||||
|
||||
_The example includes a line break for readability._
|
||||
_Das Beispiel enthält aus Gründen der Lesbarkeit einen Zeilenumbruch._
|
||||
|
||||
Or, if the endpoint uses cursor-based pagination:
|
||||
Der Endpunkt kann alternativ auch eine cursorbasierte Paginierung verwenden:
|
||||
|
||||
Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next",
|
||||
|
||||
This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570).
|
||||
Dieser `Link`-Antwortheader enthält eine oder mehrere [Hypermedia](/rest#hypermedia)-Linkbeziehungen, von denen einige möglicherweise die Erweiterung als [URI-Vorlagen](https://datatracker.ietf.org/doc/html/rfc6570) erfordern.
|
||||
|
||||
The possible `rel` values are:
|
||||
Dies sind die möglichen `rel`-Werte:
|
||||
|
||||
Name | Description
|
||||
Name | BESCHREIBUNG
|
||||
-----------|-----------|
|
||||
`next` |The link relation for the immediate next page of results.
|
||||
`last` |The link relation for the last page of results.
|
||||
`first` |The link relation for the first page of results.
|
||||
`prev` |The link relation for the immediate previous page of results.
|
||||
`next` |Linkbeziehung für die unmittelbare nächste Seite der Ergebnisse.
|
||||
`last` |Linkbeziehung für die letzte Seite der Ergebnisse.
|
||||
`first` |Linkbeziehung für die erste Seite der Ergebnisse.
|
||||
`prev` |Linkbeziehung für die unmittelbar vorherige Seite der Ergebnisse.
|
||||
|
||||
## Timeouts
|
||||
## Zeitlimits
|
||||
|
||||
If {% data variables.product.prodname_dotcom %} takes more than 10 seconds to process an API request, {% data variables.product.prodname_dotcom %} will terminate the request and you will receive a timeout response like this:
|
||||
Wenn die Verarbeitung einer API-Anforderung durch {% data variables.product.prodname_dotcom %} länger als zehn Sekunden dauert, wird die Anforderung durch {% data variables.product.prodname_dotcom %} beendet, und du erhältst eine Timeoutantwort wie die folgende:
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -362,23 +328,23 @@ If {% data variables.product.prodname_dotcom %} takes more than 10 seconds to pr
|
||||
}
|
||||
```
|
||||
|
||||
{% data variables.product.product_name %} reserves the right to change the timeout window to protect the speed and reliability of the API.
|
||||
{% data variables.product.product_name %} behält sich das Recht vor, das Timeoutfenster zu ändern, um die Geschwindigkeit und Zuverlässigkeit der API zu schützen.
|
||||
|
||||
## Rate limiting
|
||||
## Ratenbegrenzung
|
||||
|
||||
Different types of API requests to {% data variables.location.product_location %} are subject to different rate limits.
|
||||
Die unterschiedlichen Arten von API-Anforderungen an {% data variables.location.product_location %} unterliegen unterschiedlichen Ratenbegrenzungen.
|
||||
|
||||
Additionally, the Search API has dedicated limits. For more information, see "[Search](/rest/reference/search#rate-limit)" in the REST API documentation.
|
||||
Darüber hinaus verfügt die Such-API über dedizierte Grenzwerte. Weitere Informationen findest du unter [Suche](/rest/reference/search#rate-limit) in der REST-API-Dokumentation.
|
||||
|
||||
{% data reusables.enterprise.rate_limit %}
|
||||
|
||||
{% data reusables.rest-api.always-check-your-limit %}
|
||||
|
||||
### Requests from personal accounts
|
||||
### Anforderungen von persönlichen Konten
|
||||
|
||||
Direct API requests that you authenticate with a {% data variables.product.pat_generic %} are user-to-server requests. An OAuth App or GitHub App can also make a user-to-server request on your behalf after you authorize the app. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)," "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)," and "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)."
|
||||
Direkte API-Anforderungen, die du mit einem {% data variables.product.pat_generic %} authentifizierst, sind Benutzer-zu-Server-Anforderungen. Eine OAuth-App oder GitHub-App kann auch eine Benutzer-zu-Server-Anforderung in deinem Namen vornehmen, nachdem du die App autorisiert hast. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token), [Autorisieren von OAuth-Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps) und [Autorisieren von GitHub-Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps).
|
||||
|
||||
{% data variables.product.product_name %} associates all user-to-server requests with the authenticated user. For OAuth Apps and GitHub Apps, this is the user who authorized the app. All user-to-server requests count toward the authenticated user's rate limit.
|
||||
{% data variables.product.product_name %} ordnet den authentifizierten Benutzer*innen alle Benutzer-zu-Server-Anforderungen zu. Für OAuth-Apps und GitHub-Apps sind dies die Benutzer*innen, die die App autorisiert haben. Alle Benutzer-zu-Server-Anforderungen werden zur Ratenbegrenzung der authentifizierten Benutzer*innen hinzugezählt.
|
||||
|
||||
{% data reusables.apps.user-to-server-rate-limits %}
|
||||
|
||||
@@ -388,33 +354,33 @@ Direct API requests that you authenticate with a {% data variables.product.pat_g
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
|
||||
For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the person making requests.
|
||||
Für nicht authentifizierte Anforderungen ermöglicht die Ratenbegrenzung bis zu 60 Anforderungen pro Stunde. Nicht authentifizierte Anforderungen sind der ursprünglichen IP-Adresse und nicht der Person zugeordnet, die Anforderungen erstellt.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Requests from GitHub Apps
|
||||
### Anforderungen über GitHub-Apps
|
||||
|
||||
Requests from a GitHub App may be either user-to-server or server-to-server requests. For more information about rate limits for GitHub Apps, see "[Rate limits for GitHub Apps](/developers/apps/building-github-apps/rate-limits-for-github-apps)."
|
||||
Anforderungen über eine GitHub-App können entweder Benutzer-zu-Server- oder Server-zu-Server-Anforderungen sein. Weitere Informationen zu Ratenbegrenzungen für GitHub-Apps findest du unter [Ratenbegrenzungen für GitHub-Apps](/developers/apps/building-github-apps/rate-limits-for-github-apps).
|
||||
|
||||
### Requests from GitHub Actions
|
||||
### Anforderungen über GitHub Actions
|
||||
|
||||
You can use the built-in `GITHUB_TOKEN` to authenticate requests in GitHub Actions workflows. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
|
||||
Du kannst das integrierte `GITHUB_TOKEN` verwenden, um Anforderungen in GitHub Actions-Workflows zu authentifizieren. Weitere Informationen findest du unter [Automatische Tokenauthentifizierung](/actions/security-guides/automatic-token-authentication).
|
||||
|
||||
When using `GITHUB_TOKEN`, the rate limit is 1,000 requests per hour per repository.{% ifversion fpt or ghec %} For requests to resources that belong to an enterprise account on {% data variables.location.product_location %}, {% data variables.product.prodname_ghe_cloud %}'s rate limit applies, and the limit is 15,000 requests per hour per repository.{% endif %}
|
||||
Bei Verwendung von `GITHUB_TOKEN` beträgt die Ratenbegrenzung 1.000 Anforderungen pro Stunde und Repository.{% ifversion fpt or ghec %} Für Anforderungen an Ressourcen, die zu einem Unternehmenskonto auf {% data variables.location.product_location %} gehören, gilt die Ratenbegrenzung von {% data variables.product.prodname_ghe_cloud %}, und der Grenzwert beträgt 15.000 Anforderungen pro Stunde und Repository.{% endif %}
|
||||
|
||||
### Checking your rate limit status
|
||||
### Überprüfen des Status der Ratenbegrenzung
|
||||
|
||||
The Rate Limit API and a response's HTTP headers are authoritative sources for the current number of API calls available to you or your app at any given time.
|
||||
Die Ratenbegrenzungs-API und die HTTP-Header einer Antwort sind autoritative Quellen für die aktuelle Anzahl von API-Aufrufen, die dir oder deiner App jederzeit zur Verfügung stehen.
|
||||
|
||||
#### Rate Limit API
|
||||
#### Ratenbegrenzungs-API
|
||||
|
||||
You can use the Rate Limit API to check your rate limit status without incurring a hit to the current limit. For more information, see "[Rate limit](/rest/reference/rate-limit)."
|
||||
Du kannst die Ratenbegrenzungs-API verwenden, um den Status der Ratenbegrenzung zu überprüfen, ohne dass diese Anfrage zum aktuellen Grenzwert hinzugezählt wird. Weitere Informationen findest du unter [Ratenbegrenzung](/rest/reference/rate-limit).
|
||||
|
||||
#### Rate limit HTTP headers
|
||||
#### HTTP-Header für die Ratenbegrenzung
|
||||
|
||||
The returned HTTP headers of any API request show your current rate limit status:
|
||||
In den zurückgegebenen HTTP-Headern einer API-Anforderung wird der aktuelle Status der Ratenbegrenzung angezeigt:
|
||||
|
||||
```shell
|
||||
$ curl -I {% data variables.product.api_url_pre %}/users/octocat
|
||||
@@ -426,21 +392,21 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
|
||||
> x-ratelimit-reset: 1372700873
|
||||
```
|
||||
|
||||
Header Name | Description
|
||||
Headername | BESCHREIBUNG
|
||||
-----------|-----------|
|
||||
`x-ratelimit-limit` | The maximum number of requests you're permitted to make per hour.
|
||||
`x-ratelimit-remaining` | The number of requests remaining in the current rate limit window.
|
||||
`x-ratelimit-used` | The number of requests you've made in the current rate limit window.
|
||||
`x-ratelimit-reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
|
||||
`x-ratelimit-limit` | Die maximale Anzahl von Anforderungen, die du pro Stunde stellen darfst.
|
||||
`x-ratelimit-remaining` | Die Anzahl der Anforderungen, die im aktuellen Ratenbegrenzungsfenster verbleiben.
|
||||
`x-ratelimit-used` | Die Anzahl der Anforderungen, die du im aktuellen Ratenbegrenzungsfenster gesendet hast
|
||||
`x-ratelimit-reset` | Die Zeit in [Sekunden seit der UTC-Epoche](http://en.wikipedia.org/wiki/Unix_time), zu der das aktuelle Ratenbegrenzungsfenster zurückgesetzt wird.
|
||||
|
||||
If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object.
|
||||
Wenn du die Zeit in einem anderen Format benötigst, kann jede moderne Programmiersprache diese Anforderung erfüllen. Wenn du beispielsweise die Konsole in deinem Webbrowser öffnest, kannst du die Rückstellzeit einfach als JavaScript-Date-Objekt abrufen.
|
||||
|
||||
``` javascript
|
||||
new Date(1372700873 * 1000)
|
||||
// => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT)
|
||||
```
|
||||
|
||||
If you exceed the rate limit, an error response returns:
|
||||
Wenn du die Ratenbegrenzung überschreitest, wird eine Fehlerantwort zurückgegeben:
|
||||
|
||||
```shell
|
||||
> HTTP/2 403
|
||||
@@ -456,9 +422,9 @@ If you exceed the rate limit, an error response returns:
|
||||
> }
|
||||
```
|
||||
|
||||
### Increasing the unauthenticated rate limit for OAuth Apps
|
||||
### Erhöhen der nicht authentifizierten Ratenbegrenzung für OAuth-Apps
|
||||
|
||||
If your OAuth App needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route.
|
||||
Wenn deine OAuth-App nicht authentifizierte Aufrufe mit einer höheren Ratenbegrenzung vornehmen muss, kannst du die Client-ID und den geheimen Schlüssel deiner App vor der Endpunktroute übergeben.
|
||||
|
||||
```shell
|
||||
$ curl -u my_client_id:my_client_secret -I {% data variables.product.api_url_pre %}/user/repos
|
||||
@@ -472,21 +438,21 @@ $ curl -u my_client_id:my_client_secret -I {% data variables.product.api_url_pre
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls.
|
||||
**Hinweis:** Teile deinen geheimen Clientschlüssel niemals mit anderen Personen, und füge ihn nicht in clientseitigen Browsercode ein. Verwende die hier gezeigte Methode nur für Server-zu-Server-Aufrufe.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Staying within the rate limit
|
||||
### Einhalten der Ratenbegrenzung
|
||||
|
||||
If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests).
|
||||
Wenn du bei Verwendung der Standardauthentifizierung oder OAuth die Ratenbegrenzung überschreitest, kannst du das Problem wahrscheinlich beheben, indem du API-Antworten zwischenspeicherst und [bedingte Anforderungen](#conditional-requests) verwendest.
|
||||
|
||||
### Secondary rate limits
|
||||
### Sekundäre Ratenbegrenzungen
|
||||
|
||||
In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting.
|
||||
Um den Qualitätsdienst für {% data variables.product.product_name %} bereitzustellen, gelten bei Verwendung der API möglicherweise zusätzliche Ratenbegrenzungen für einige Aktionen. Wenn du beispielsweise die API verwendest, um schnell Inhalte zu erstellen, du anstelle der Verwendung von Webhooks offensiv abfragst, mehrere gleichzeitige Anforderungen stellst oder wiederholt berechnungsintensive Daten anforderst, kann dies zu einer sekundären Ratenbegrenzung führen.
|
||||
|
||||
Secondary rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/).
|
||||
Sekundäre Ratenbegrenzungen sollen nicht die legitime Verwendung der API beeinträchtigen. Deine normalen Ratenbegrenzungen sollten die einzige Grenze sein, die du erreichst. Lies die [Anleitung mit bewährten Methoden](/guides/best-practices-for-integrators/), um sicherzustellen, dass du die API ordnungsgemäß verwendest.
|
||||
|
||||
If your application triggers this rate limit, you'll receive an informative response:
|
||||
Wenn deine Anwendung diese Ratenbegrenzung auslöst, erhältst du eine informative Antwort:
|
||||
|
||||
```shell
|
||||
> HTTP/2 403
|
||||
@@ -501,19 +467,17 @@ If your application triggers this rate limit, you'll receive an informative resp
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## User agent required
|
||||
## Benutzer-Agent erforderlich
|
||||
|
||||
All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent`
|
||||
header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your
|
||||
application, for the `User-Agent` header value. This allows us to contact you if there are problems.
|
||||
Alle API-Anforderungen MÜSSEN einen gültigen `User-Agent`-Header enthalten. Anforderungen ohne `User-Agent`-Header werden abgelehnt. Du musst deinen {% data variables.product.product_name %}-Benutzernamen oder den Namen deiner Anwendung für den `User-Agent`-Headerwert verwenden. Auf diese Weise kannst du im Fall von Problemen kontaktiert werden.
|
||||
|
||||
Here's an example:
|
||||
Hier sehen Sie ein Beispiel:
|
||||
|
||||
```shell
|
||||
User-Agent: Awesome-Octocat-App
|
||||
```
|
||||
|
||||
cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response:
|
||||
cURL sendet standardmäßig einen gültigen `User-Agent`-Header. Wenn du einen ungültigen `User-Agent`-Header über cURL (oder über einen alternativen Client) bereitstellst, erhältst du eine `403 Forbidden`-Antwort:
|
||||
|
||||
```shell
|
||||
$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
|
||||
@@ -528,20 +492,15 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Conditional requests
|
||||
## Bedingte Anforderungen
|
||||
|
||||
Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values
|
||||
of these headers to make subsequent requests to those resources using the
|
||||
`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource
|
||||
has not changed, the server will return a `304 Not Modified`.
|
||||
Die meisten Antworten geben einen `ETag`-Header zurück. Viele Antworten geben auch einen `Last-Modified`-Header zurück. Du kannst die Werte dieser Header verwenden, um mithilfe der Header `If-None-Match` bzw. `If-Modified-Since` nachfolgende Anforderungen an diese Ressourcen zu stellen. Wenn die Ressource nicht geändert wurde, gibt der Server `304 Not Modified` zurück.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Note**: Making a conditional request and receiving a 304 response does not
|
||||
count against your [Rate Limit](#rate-limiting), so we encourage you to use it
|
||||
whenever possible.
|
||||
**Hinweis:** Das Senden einer bedingten Anforderung und das Empfangen einer 304-Antwort werden nicht auf deine [Ratenbegrenzung](#rate-limiting) angerechnet, weshalb empfohlen wird, diesen Ansatz nach Möglichkeit immer zu verwenden.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -578,16 +537,12 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T
|
||||
> x-ratelimit-reset: 1372700873
|
||||
```
|
||||
|
||||
## Cross origin resource sharing
|
||||
## Cross-Origin Resource Sharing
|
||||
|
||||
The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from
|
||||
any origin.
|
||||
You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or
|
||||
[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the
|
||||
HTML 5 Security Guide.
|
||||
Die API unterstützt CORS (Cross-Origin Resource Sharing) für AJAX-Anforderungen aus jedem Ursprung.
|
||||
Du kannst die [CORS-W3C-Empfehlung](http://www.w3.org/TR/cors/) oder [diese Einführung](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) im HTML 5-Sicherheitsleitfaden lesen.
|
||||
|
||||
Here's a sample request sent from a browser hitting
|
||||
`http://example.com`:
|
||||
Im Folgenden findest du eine Beispielanforderung, die von einem Browser gesendet wird, der `http://example.com` aufruft:
|
||||
|
||||
```shell
|
||||
$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
|
||||
@@ -596,7 +551,7 @@ Access-Control-Allow-Origin: *
|
||||
Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
|
||||
```
|
||||
|
||||
This is what the CORS preflight request looks like:
|
||||
Die CORS-Preflight-Anforderung lautet wie folgt:
|
||||
|
||||
```shell
|
||||
$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
|
||||
@@ -608,13 +563,9 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ra
|
||||
Access-Control-Max-Age: 86400
|
||||
```
|
||||
|
||||
## JSON-P callbacks
|
||||
## JSON-P-Rückrufe
|
||||
|
||||
You can send a `?callback` parameter to any GET call to have the results
|
||||
wrapped in a JSON function. This is typically used when browsers want
|
||||
to embed {% data variables.product.product_name %} content in web pages by getting around cross domain
|
||||
issues. The response includes the same data output as the regular API,
|
||||
plus the relevant HTTP Header information.
|
||||
Du kannst einen `?callback`-Parameter an einen beliebigen GET-Aufruf senden, um die Ergebnisse in einer JSON-Funktion zu umschließen. Dieser Ansatz wird in der Regel verwendet, wenn Browser {% data variables.product.product_name %}-Inhalte in Webseiten einbetten möchten, indem domänenübergreifende Probleme umgangen werden. Die Antwort enthält die gleiche Datenausgabe wie die reguläre API sowie die relevanten HTTP-Headerinformationen.
|
||||
|
||||
```shell
|
||||
$ curl {% data variables.product.api_url_pre %}?callback=foo
|
||||
@@ -635,7 +586,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
|
||||
> })
|
||||
```
|
||||
|
||||
You can write a JavaScript handler to process the callback. Here's a minimal example you can try out:
|
||||
Du kannst einen JavaScript-Handler schreiben, um den Rückruf zu verarbeiten. Hier findest du ein minimales Beispiel, das du ausprobieren kannst:
|
||||
|
||||
<html>
|
||||
<head>
|
||||
@@ -659,15 +610,13 @@ You can write a JavaScript handler to process the callback. Here's a minimal exa
|
||||
</body>
|
||||
</html>
|
||||
|
||||
All of the headers are the same String value as the HTTP Headers with one
|
||||
notable exception: Link. Link headers are pre-parsed for you and come
|
||||
through as an array of `[url, options]` tuples.
|
||||
Alle Header haben den gleichen Zeichenfolgenwert wie die HTTP-Header mit einer wichtigen Ausnahme: Link. Link-Header werden vorab für dich analysiert und als Array von `[url, options]`-Tupeln angezeigt.
|
||||
|
||||
A link that looks like this:
|
||||
Ein Link wie der folgende ...
|
||||
|
||||
Link: <url1>; rel="next", <url2>; rel="foo"; bar="baz"
|
||||
|
||||
... will look like this in the Callback output:
|
||||
... sieht in der Rückrufausgabe wie folgt aus:
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -689,39 +638,39 @@ A link that looks like this:
|
||||
}
|
||||
```
|
||||
|
||||
## Timezones
|
||||
## Zeitzonen
|
||||
|
||||
Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for such API calls.
|
||||
Einige Anforderungen, die neue Daten erstellen (z. B. das Erstellen eines neuen Commits), ermöglichen es dir, Zeitzoneninformationen bereitzustellen, wenn du Zeitstempel angibst oder generierst. Du wendest die folgenden Regeln in der Reihenfolge ihrer Priorität an, um Zeitzoneninformationen für solche API-Aufrufe zu ermitteln.
|
||||
|
||||
* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
|
||||
* [Using the `Time-Zone` header](#using-the-time-zone-header)
|
||||
* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user)
|
||||
* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information)
|
||||
* [Explizites Bereitstellen eines ISO 8601-Zeitstempels mit Zeitzoneninformationen](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
|
||||
* [Verwenden des `Time-Zone`-Headers](#using-the-time-zone-header)
|
||||
* [Verwenden der letzten bekannten Zeitzone für Benutzer*innen](#using-the-last-known-timezone-for-the-user)
|
||||
* [Standardmäßiges Festlegen auf UTC ohne andere Zeitzoneninformationen](#defaulting-to-utc-without-other-timezone-information)
|
||||
|
||||
Note that these rules apply only to data passed to the API, not to data returned by the API. As mentioned in "[Schema](#schema)," timestamps returned by the API are in UTC time, ISO 8601 format.
|
||||
Beachte, dass diese Regeln nur für Daten gelten, die an die API übergeben werden, und nicht für Daten, die von der API zurückgegeben werden. Wie unter [Schema](#schema) erwähnt liegen von der API zurückgegebene Zeitstempel im UTC-Zeitformat gemäß ISO 8601 vor.
|
||||
|
||||
### Explicitly providing an ISO 8601 timestamp with timezone information
|
||||
### Explizites Bereitstellen eines ISO 8601-Zeitstempels mit Zeitzoneninformationen
|
||||
|
||||
For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits).
|
||||
API-Aufrufe, die das Angeben eines Zeitstempels ermöglichen, wird dieser genaue Zeitstempel verwendet. Ein Beispiel hierfür ist die [Commits-API](/rest/reference/git#commits).
|
||||
|
||||
These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified.
|
||||
Diese Zeitstempel sehen in etwa wie `2014-02-27T15:05:06+01:00` aus. In [diesem Beispiel](/rest/reference/git#example-input) wird gezeigt, wie diese Zeitstempel angegeben werden können.
|
||||
|
||||
### Using the `Time-Zone` header
|
||||
### Verwenden des `Time-Zone`-Headers
|
||||
|
||||
It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
|
||||
Es ist möglich, einen `Time-Zone`-Header zu geben, der eine Zeitzone gemäß der [Liste der Namen aus der Olson-Datenbank](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) definiert.
|
||||
|
||||
```shell
|
||||
$ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md
|
||||
```
|
||||
|
||||
This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp.
|
||||
Dies bedeutet, dass du einen Zeitstempel für den Zeitpunkt generierst, zu dem dein API-Aufruf in der Zeitzone erfolgt, die dieser Header definiert. Die [Inhalts-API](/rest/reference/repos#contents) generiert beispielsweise einen Git-Commit für jede Ergänzung oder Änderung und verwendet die aktuelle Uhrzeit als Zeitstempel. Dieser Header bestimmt die Zeitzone, die zum Generieren dieses aktuellen Zeitstempels verwendet wird.
|
||||
|
||||
### Using the last known timezone for the user
|
||||
### Verwenden der letzten bekannten Zeitzone für Benutzer*innen
|
||||
|
||||
If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website.
|
||||
Wenn kein `Time-Zone`-Header angegeben ist und du einen authentifizierten Aufruf der API vornimmst, verwende die letzte bekannte Zeitzone für die authentifizierten Benutzer*innen. Die letzte bekannte Zeitzone wird aktualisiert, wenn du die {% data variables.product.product_name %}-Website durchsuchst.
|
||||
|
||||
### Defaulting to UTC without other timezone information
|
||||
### Standardmäßiges Festlegen auf UTC ohne andere Zeitzoneninformationen
|
||||
|
||||
If the steps above don't result in any information, we use UTC as the timezone to create the git commit.
|
||||
Wenn die obigen Schritte keine Informationen bereitstellen, verwende UTC als Zeitzone, um den Git-Commit zu erstellen.
|
||||
|
||||
[pagination-guide]: /guides/traversing-with-pagination
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting
|
||||
intro: Learn how to resolve the most common problems people encounter in the REST API.
|
||||
title: Problembehandlung
|
||||
intro: 'Erfahre, wie du die häufigsten Probleme mit der REST-API lösen kannst.'
|
||||
redirect_from:
|
||||
- /v3/troubleshooting
|
||||
versions:
|
||||
@@ -10,78 +10,73 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: ecfa3a360ef9b042d96a1f80a2f0cde49390727f
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148184232'
|
||||
---
|
||||
|
||||
|
||||
|
||||
If you're encountering some oddities in the API, here's a list of resolutions to
|
||||
some of the problems you may be experiencing.
|
||||
Solltest du in der API auf etwas Eigenartiges stoßen, findest du hier eine Liste mit Lösungen für einige mögliche Probleme.
|
||||
|
||||
{% ifversion api-date-versioning %}
|
||||
|
||||
## `400` error for an unsupported API version
|
||||
## Fehler `400` aufgrund nicht unterstützter API-Version
|
||||
|
||||
You should use the `X-GitHub-Api-Version` header to specify an API version. For example:
|
||||
Du solltest den `X-GitHub-Api-Version`-Header verwenden, um eine API-Version anzugeben. Beispiel:
|
||||
|
||||
```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.
|
||||
Wenn du eine nicht vorhandene Version angibst, wird der Fehler `400` ausgelöst.
|
||||
|
||||
For more information, see "[API Versions](/rest/overview/api-versions)."
|
||||
Weitere Informationen findest du unter [API-Versionen](/rest/overview/api-versions).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## `404` error for an existing repository
|
||||
## Fehler `404` für ein vorhandenes Repository
|
||||
|
||||
Typically, we send a `404` error when your client isn't properly authenticated.
|
||||
You might expect to see a `403 Forbidden` in these cases. However, since we don't
|
||||
want to provide _any_ information about private repositories, the API returns a
|
||||
`404` error instead.
|
||||
Der Fehler `404` wird für gewöhnlich ausgegeben, wenn dein Client nicht ordnungsgemäß authentifiziert ist.
|
||||
In diesen Fällen erwartest du möglicherweise einen Fehler vom Typ `403 Forbidden`. Da wir jedoch _keinerlei_ Informationen zu privaten Repositorys angeben möchten, gibt die API stattdessen einen Fehler vom Typ `404` zurück.
|
||||
|
||||
To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), [third-party application restrictions][oap-guide] are not blocking access, and that [the token has not expired or been revoked](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
|
||||
Stelle zur Behandlung des Problems Folgendes sicher: [Du authentifizierst dich ordnungsgemäß](/guides/getting-started/), [dein OAuth-Zugriffstoken verfügt über die erforderlichen Bereiche](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), der Zugriff wird nicht durch [Einschränkungen von Drittanbieteranwendungen][oap-guide] blockiert, und [das Token ist nicht abgelaufen und wurde nicht widerrufen](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
|
||||
|
||||
## Not all results returned
|
||||
## Nicht alle Ergebnisse zurückgegeben
|
||||
|
||||
Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support
|
||||
pagination. If you're making requests and receiving an incomplete set of results, you're
|
||||
probably only seeing the first page. You'll need to request the remaining pages
|
||||
in order to get more results.
|
||||
Die meisten API-Aufrufe, die auf eine Liste von Ressourcen zugreifen (_z._ B. Benutzer, Probleme _usw._) unterstützen die Pagination. Wenn du bei Anforderungen unvollständige Ergebnisse erhältst, siehst du wahrscheinlich nur die erste Seite. Du musst die restlichen Seiten anfordern, um weitere Ergebnisse zu erhalten.
|
||||
|
||||
It's important to *not* try and guess the format of the pagination URL. Not every
|
||||
API call uses the same structure. Instead, extract the pagination information from
|
||||
[the Link Header](/rest#pagination), which is sent with every request.
|
||||
Wichtig: Versuche *nicht*, das Format der Paginierungs-URL zu erraten. Nicht jeder API-Aufruf verwendet die gleiche Struktur. Extrahiere stattdessen die Paginierungsinformationen aus dem [Linkheader](/rest#pagination), der mit jeder Anforderung gesendet wird.
|
||||
|
||||
[oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Basic authentication errors
|
||||
## Standardauthentifizierungsfehler
|
||||
|
||||
On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work.
|
||||
Am 13. November 2020 wurde die Authentifizierung mit Benutzername und Kennwort für die REST-API und für die API für die OAuth-Autorisierung als veraltet eingestuft, und sie funktioniert nicht mehr.
|
||||
|
||||
### Using `username`/`password` for basic authentication
|
||||
### Verwenden von `username`/`password` für die Standardauthentifizierung
|
||||
|
||||
If you're using `username` and `password` for API calls, then they are no longer able to authenticate. For example:
|
||||
Wenn du `username` und `password` für API-Aufrufe verwendest, ist keine Authentifizierung mehr möglich. Beispiel:
|
||||
|
||||
```bash
|
||||
curl -u my_user:my_password https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
Instead, use a [{% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development:
|
||||
Verwende beim Testen von Endpunkten oder bei der lokalen Entwicklung stattdessen ein [{% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line):
|
||||
|
||||
```bash
|
||||
curl -H 'Authorization: Bearer my_access_token' https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header:
|
||||
Bei OAuth-Apps empfiehlt sich die Verwendung des [Webanwendungsflusses](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow), um ein OAuth-Token für den Header des API-Aufrufs zu generieren:
|
||||
|
||||
```bash
|
||||
curl -H 'Authorization: Bearer my-oauth-token' https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
## Timeouts
|
||||
## Zeitlimits
|
||||
|
||||
If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response.
|
||||
Wenn die Verarbeitung einer API-Anforderung durch {% data variables.product.product_name %} länger als zehn Sekunden dauert, wird die Anforderung durch {% data variables.product.product_name %} beendet, und du erhältst eine Timeoutantwort.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 9f7ac09b688bbe2b74a5cba71d2605365b7e7366
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: "148185127"
|
||||
---
|
||||
<a href="https://github.com/github-copilot/signup" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Teste {% data variables.product.prodname_copilot %}</span> {% octicon "link-external" height:16 %}</a>
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 7b782aa3d23143a62b07aedf0a07df3734173d44
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: f58fb9410d93c9e50d33de5f1b12b9d6441ea561
|
||||
ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145133077"
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: "148185616"
|
||||
---
|
||||
Jedes Repository oder jede Organisation kann bis zu 10 Kategorien aufweisen.
|
||||
Jedes Repository oder jede Organisation kann bis zu 25 Kategorien aufweisen.
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
ms.openlocfilehash: dd7c5f37ab5b2d699b47460195e02ae21fca1733
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: "148184398"
|
||||
---
|
||||
Die {% data variables.product.product_name %}-REST-API ist versionsspezifisch. Der API-Versionsname basiert auf dem Datum, an dem die API-Version veröffentlicht wurde. Beispielsweise wurde die API-Version `{{ initialRestVersioningReleaseDate }}` am {{ initialRestVersioningReleaseDateLong }} veröffentlicht.
|
||||
|
||||
Alle Breaking Changes werden in einer neuen API-Version veröffentlicht. Breaking Changes sind Änderungen, die möglicherweise eine Integration unterbrechen können. Zu Breaking Changes gehören:
|
||||
|
||||
- Entfernen eines gesamten Vorgangs
|
||||
- Entfernen oder Umbenennen eines Parameters
|
||||
- Entfernen oder Umbenennen eines Antwortfelds
|
||||
- Hinzufügen eines neuen erforderlichen Parameters
|
||||
- Erforderlichmachen eines zuvor optionalen Parameters
|
||||
- Ändern des Typs eines Parameters oder Antwortfelds
|
||||
- Entfernen von Enumerationswerten
|
||||
- Hinzufügen einer neuen Validierungsregel zu einem vorhandenen Parameter
|
||||
- Ändern der Authentifizierungs- oder Autorisierungsanforderungen
|
||||
|
||||
Alle additiven (Nonbreaking) Changes sind in allen unterstützten API-Versionen verfügbar. Additive Änderungen sind Änderungen, die eine Integration nicht unterbrechen sollten. Zu den additiven Änderungen gehören:
|
||||
|
||||
- Hinzufügen eines Vorgangs
|
||||
- Hinzufügen eines optionalen Parameters
|
||||
- Hinzufügen eines optionalen Anforderungsheaders
|
||||
- Hinzufügen eines Antwortfelds
|
||||
- Hinzufügen eines Antwortheaders
|
||||
- Hinzufügen von Enumerationswerten
|
||||
|
||||
Wenn eine neue REST-API-Version veröffentlicht wird, wird die vorherige API-Version noch mindestens 24 Monate nach der Veröffentlichung der neuen API-Version unterstützt.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 28c0a6c9cde70105e42feef89486c5c893ebbe72
|
||||
ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: "148184393"
|
||||
---
|
||||
{% ifversion api-date-versioning %}--header "X-GitHub-Api-Version:{{ allVersions[currentVersion].latestApiVersion }}"{% endif %}
|
||||
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Restricción del tráfico de red a la empresa con una lista de direcciones IP permitidas
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
shortTitle: Restricting network traffic
|
||||
intro: Puedes restringir el acceso a tu empresa y permitir solo el acceso a los recursos desde direcciones IP especificadas mediante una lista de direcciones IP permitidas.
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,150 +17,192 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: b62ab2a143ed0e7ec57f7e7225a09c0ca713295c
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185047'
|
||||
---
|
||||
## Acerca de las restricciones de tráfico de red
|
||||
|
||||
Predeterminadamente, los usuarios autorizados pueden acceder a tu empresa desde cualquier dirección IP. Puedes restringir el acceso a los recursos {% ifversion ghec %}que pertenezcan a las organizaciones dentro de la cuenta empresarial {% endif %}mediante la configuración de una lista de direcciones IP permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
Si tu empresa usa {% data variables.product.prodname_emus %} con OIDC, puedes elegir si quieres usar la lista de direcciones IP permitidas de {% data variables.product.company_short %} o usar las restricciones de lista de permitidos para el proveedor de identidades (IdP). Si tu empresa no usa {% data variables.product.prodname_emus %} con OIDC, puedes usar la característica de lista de permitidos de {% data variables.product.company_short %}.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
Predeterminadamente, las reglas del grupo de seguridad de redes (NSG) de Azure dejan todo el tráfico entrante abierto en los puertos 22, 80, 443 y 25. Puedes ponerte en contacto con {% data variables.contact.github_support %} para configurar restricciones de acceso para {% data variables.product.product_name %}.
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
|
||||
Para las restricciones que utilizan los NSG de Azure, contacta a {% data variables.contact.github_support %} enviando las direcciones IP que deberán poder acceder a {% data variables.product.product_name %}. Especifica los rangos de direcciones utilizando el formato estándar de CIDR (Enrutamiento sin Clases entre Dominios, por sus siglas en inglés). {% data variables.contact.github_support %} configurará las reglas de cortafuegos adecuadas para restringir el acceso por HTTP, SSH, HTTPS, y SMTP. Para más información, vea "[Recepción de ayuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)".
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Acerca de la lista de direcciones IP permitidas de {% data variables.product.company_short %}
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
Puedes usar la lista de direcciones IP permitidas de {% data variables.product.company_short %} para controlar el acceso a la empresa y a los recursos que pertenecen a las organizaciones de tu empresa.
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
|
||||
{% 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 %}
|
||||
|
||||
## Acerca de la lista de permitidos del proveedor de identidades
|
||||
## About your IdP's allow list
|
||||
|
||||
Si usas {% data variables.product.prodname_emus %} con OIDC, puedes usar la lista de permitidos del proveedor de identidades.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
El uso de la lista de permitidos del proveedor de identidades desactiva las configuraciones de la lista de direcciones IP permitidas de {% data variables.product.company_short %} para todas las organizaciones de tu empresa y desactiva las API de GraphQL para habilitar y administrar listas de direcciones IP permitidas.
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
De forma predeterminada, el proveedor de identidades ejecuta el CAP en el inicio de sesión interactivo de SAML o OIDC inicial a {% data variables.product.company_short %} para cualquier configuración de lista de direcciones IP permitidas que elijas.
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
|
||||
El CAP de OIDC solo se aplica a las solicitudes a la API mediante un token de usuario a servidor, como un token para un {% data variables.product.prodname_oauth_app %} o un {% data variables.product.prodname_github_app %} que actúa en nombre de un usuario. El CAP de OIDC no se aplica cuando un {% data variables.product.prodname_github_app %} usa un token de servidor a servidor. Para obtener más información, consulta "[Autenticación con {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" y "[Acerca de la compatibilidad con la directiva de acceso condicional del proveedor de identidades](/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)".
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/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)."
|
||||
|
||||
Para garantizar un uso sin problemas del CAP de OIDC mientras se sigue aplicando la directiva a los tokens de usuario a servidor, debes copiar todos los intervalos IP de cada {% data variables.product.prodname_github_app %} que la empresa usa en la directiva de proveedor de identidades.
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
|
||||
## Uso de la lista de direcciones IP permitidas de {% data variables.product.company_short %}
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
### Habilitación de la lista de direcciones IP permitidas de {% data variables.product.company_short %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. En "Lista de direcciones IP permitidas", habilita la lista de direcciones IP permitidas.
|
||||
- Si usas {% data variables.product.prodname_emus %} con OIDC, selecciona el menú desplegable y haz clic en **GitHub**.
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
|
||||
Selecciona **Habilitar lista de direcciones IP permitidas**.
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
|
||||
- Si no usas {% data variables.product.prodname_emus %}con OIDC, selecciona **Habilitar lista de direcciones IP permitidas**.
|
||||
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Agregar una dirección IP permitida
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Permitir el acceso mediante {% data variables.product.prodname_github_apps %}
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Editar una dirección IP permitida
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% 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. Haga clic en **Update**(Actualizar).
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Comprobación de permiso para una dirección IP
|
||||
### Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Eliminar una dirección IP permitida
|
||||
### Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## Uso de la lista de permitidos del proveedor de identidades
|
||||
## Using your identity provider's allow list
|
||||
|
||||
Puedes usar la lista de permitidos del proveedor de identidades si usas {% data variables.product.prodname_emus %} con OIDC.
|
||||
{% note %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. En "Lista de direcciones IP permitidas", selecciona la lista desplegable y haz clic en **Proveedor de identidades**.
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
|
||||
1. Opcionalmente, para permitir que los {% data variables.product.company_short %} y {% data variables.product.prodname_oauth_apps %} instalados accedan a la empresa desde cualquier dirección IP, selecciona **Omitir comprobación de proveedor de identidades para aplicaciones**.
|
||||
{% endnote %}
|
||||
|
||||
|
||||
1. Haga clic en **Save**(Guardar).
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Habilitar direcciones IP permitidas
|
||||
## Enabling allowed IP addresses
|
||||
|
||||
{% 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. En "IP allow list", seleccione **Enable IP allow list**.
|
||||
|
||||
4. Haga clic en **Save**(Guardar).
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## Agregar una dirección IP permitida
|
||||
## Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Permitir el acceso mediante {% data variables.product.prodname_github_apps %}
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Editar una dirección IP permitida
|
||||
## Editing an allowed IP address
|
||||
|
||||
{% 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. Haga clic en **Update**(Actualizar).
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Comprobación de permiso para una dirección IP
|
||||
## Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Eliminar una dirección IP permitida
|
||||
## Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
title: Huellas digitales de la clave SSH de GitHub
|
||||
intro: Se pueden utilizar las huellas digitales de clave pública para validar una conexión a un servidor remoto.
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: SSH key fingerprints
|
||||
ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190334'
|
||||
---
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
Estas son las huellas dactilares de la llave pública de {% data variables.product.prodname_dotcom %}:
|
||||
|
||||
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA: en desuso)
|
||||
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
|
||||
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
|
||||
|
||||
You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
|
||||
Puedes agregar las siguientes entradas de clave SSH al archivo `~.ssh/known_hosts` para no tener que comprobar manualmente los hosts de {% data variables.product.prodname_dotcom %}:
|
||||
|
||||
```text
|
||||
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
|
||||
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
|
||||
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|
||||
```
|
||||
|
||||
For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
|
||||
Para obtener más información, consulta "[Obtener información meta de {% data variables.product.prodname_dotcom %}](/rest/meta#get-github-meta-information)".
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using SSH over the HTTPS port
|
||||
intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
|
||||
title: Utilizar SSH a través del puerto HTTPS
|
||||
intro: 'Algunas veces, los firewalls se niegan a permitir conexiones SSH por completo. Si el uso de [clonación HTTPS con almacenamiento en caché de credenciales](/github/getting-started-with-github/caching-your-github-credentials-in-git) no es una opción, puedes intentar clonar usando una conexión SSH hecha a través del puerto HTTPS. La mayoría de las reglas del firewall deberían permitir esto, pero los servidores proxy pueden interferir.'
|
||||
redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
- /github/authenticating-to-github/using-ssh-over-the-https-port
|
||||
@@ -11,14 +11,20 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
shortTitle: Use SSH over HTTPS port
|
||||
ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190326'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
|
||||
**Usuarios de {% data variables.product.prodname_ghe_server %}** : actualmente no se admite el acceso a {% data variables.product.prodname_ghe_server %} por SSH mediante el puerto HTTPS.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
To test if SSH over the HTTPS port is possible, run this SSH command:
|
||||
Para probar si es posible el SSH a través del puerto HTTPS, ejecuta este comando SSH:
|
||||
|
||||
```shell
|
||||
$ ssh -T -p 443 git@ssh.github.com
|
||||
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
|
||||
**Nota**: El nombre de host del puerto 443 es `ssh.{% data variables.command_line.backticks %}`, no `{% data variables.command_line.backticks %}`.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
|
||||
Si eso funcionó, ¡fantástico! Si no es así, es posible que tenga que [seguir nuestra guía de solución de problemas](/articles/error-permission-denied-publickey).
|
||||
|
||||
Now, to clone the repository, you can run the following command:
|
||||
Ahora, para clonar el repositorio, puedes ejecutar el siguiente comando:
|
||||
|
||||
```
|
||||
$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
```
|
||||
|
||||
## Enabling SSH connections over HTTPS
|
||||
## Habilitar conexiones SSH a través de HTTPS
|
||||
|
||||
If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
|
||||
Si puedes acceder a `git@ssh.{% data variables.command_line.backticks %}` mediante SSH en el puerto 443, puede reemplazar los valores SSH para forzar que cualquier conexión a {% data variables.location.product_location %} se ejecute mediante ese servidor y ese puerto.
|
||||
|
||||
To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
|
||||
Para establecerlo en el archivo de configuración de SSH, edite el archivo en `~/.ssh/config` y agregue esta sección:
|
||||
|
||||
```
|
||||
Host {% data variables.command_line.codeblock %}
|
||||
@@ -53,7 +59,7 @@ Port 443
|
||||
User git
|
||||
```
|
||||
|
||||
You can test that this works by connecting once more to {% data variables.location.product_location %}:
|
||||
Puedes probar que esto funcione volviéndote a conectar a {% data variables.location.product_location %}:
|
||||
|
||||
```shell
|
||||
$ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
> provide shell access.
|
||||
```
|
||||
|
||||
## Updating known hosts
|
||||
## Actualización de hosts conocidos
|
||||
|
||||
The first time you interact with GitHub after switching to port 443, you may get a warning message
|
||||
that the host wasn't found in `known_hosts`, or that it was found by another name.
|
||||
La primera vez que interactúes con GitHub después de cambiar al puerto 443, puedes recibir un mensaje de advertencia que indica que no se ha encontrado el host en `known_hosts` o que se ha encontrado con otro nombre.
|
||||
|
||||
```ShellSession
|
||||
> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
|
||||
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
|
||||
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
|
||||
```
|
||||
|
||||
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
|
||||
one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
|
||||
Es seguro responder "sí" a esta pregunta, suponiendo que la huella digital SSH coincida con una de las huellas publicadas de GitHub. Para obtener la lista de huellas digitales, consulta "[Huellas digitales de la clave SSH de GitHub](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)".
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
|
||||
ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179740'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148190065'
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,6 @@ ms.locfileid: '148179740'
|
||||
|
||||
Utiliza la biblioteca oficial de Octokit, o elige entre cualquiera de las bibliotecas de terceros disponibles.
|
||||
|
||||
- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
@@ -131,6 +130,7 @@ Utiliza la biblioteca oficial de Octokit, o elige entre cualquiera de las biblio
|
||||
|**github-flask**|[github-flask (sitio web oficial)](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|**octokit.py**|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Restriction du trafic réseau vers votre entreprise avec une liste d’adresses IP autorisées
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
shortTitle: Restricting network traffic
|
||||
intro: Vous pouvez restreindre l’accès à votre entreprise et autoriser uniquement l’accès à vos ressources à partir d’adresses IP spécifiées à l’aide d’une liste d’adresses IP autorisées.
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,150 +17,192 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: b62ab2a143ed0e7ec57f7e7225a09c0ca713295c
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185042'
|
||||
---
|
||||
## À propos des restrictions du trafic réseau
|
||||
|
||||
Par défaut, les utilisateurs autorisés peuvent accéder à votre entreprise à partir de n’importe quelle adresse IP. Vous pouvez restreindre l’accès aux ressources {% ifversion ghec %}qui sont la propriété d’organisations d’un compte d’entreprise {% endif %}en configurant une liste d’adresses IP spécifiques autorisées. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% 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 %}.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
Par défaut, les règles du groupe de sécurité réseau (NSG) Azure laissent entrer l’ensemble du trafic sur les ports 22, 80, 443 et 25. Vous pouvez contacter le {% data variables.contact.github_support %} pour configurer des restrictions d’accès pour {% data variables.product.product_name %}.
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
|
||||
Pour des restrictions avec des NSG Azure, contactez le {% data variables.contact.github_support %} avec les adresses IP qui doivent être autorisées à accéder à {% data variables.product.product_name %}. Spécifiez des plages d’adresses au format CIDR (Classless Inter-Domain Routing) standard. Le {% data variables.contact.github_support %} configurera les règles de pare-feu adaptées afin de limiter l’accès réseau via HTTP, SSH, HTTPS et SMTP. Pour plus d’informations, consultez « [Obtention d’aide auprès du {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support) ».
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## À propos de la liste d’adresses IP autorisées de {% data variables.product.company_short %}
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
Vous pouvez utiliser la liste d’adresses IP autorisées de {% data variables.product.company_short %} pour contrôler l’accès à votre entreprise et aux ressources appartenant aux organisations de votre entreprise.
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
|
||||
{% 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 %}
|
||||
|
||||
## À propos de la liste d’autorisations de votre IdP
|
||||
## About your IdP's allow list
|
||||
|
||||
Si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC, vous pouvez utiliser la liste d’autorisations de votre IdP.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
L’utilisation de la liste d’autorisations de votre IdP désactive les configurations de liste d’adresses IP autorisées de {% data variables.product.company_short %} pour toutes les organisations de votre entreprise et désactive les API GraphQL pour l’activation et la gestion des listes d’adresses IP autorisées.
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
Par défaut, votre IdP exécute la stratégie d’accès conditionnel sur la connexion SAML ou OIDC interactive initiale à {% data variables.product.company_short %} pour toute configuration de liste d’adresses IP autorisées de votre choix.
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
|
||||
La stratégie d’accès conditionnel OIDC s’applique uniquement aux requêtes adressées à l’API à l’aide d’un jeton utilisateur-à-serveur, tel qu’un jeton pour une {% data variables.product.prodname_oauth_app %} ou une {% data variables.product.prodname_github_app %} agissant pour le compte d’un utilisateur. La stratégie d’accès conditionnel OIDC ne s’applique pas lorsqu’une {% data variables.product.prodname_github_app %} utilise un jeton serveur-à-serveur. Pour plus d’informations, consultez « [Authentification avec des {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation) » et « [À propos de la prise en charge de la stratégie d’accès conditionnel de vos IdP](/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) ».
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/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)."
|
||||
|
||||
Pour garantir une utilisation transparente de la stratégie d’accès conditionnel OIDC tout en appliquant la stratégie aux jetons utilisateur-à-serveur, vous devez copier toutes les plages d’adresses IP de chaque {% data variables.product.prodname_github_app %} que votre entreprise utilise dans la stratégie de votre IdP.
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
|
||||
## Utilisation de la liste d’adresses IP autorisées de {% data variables.product.company_short %}
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
### Activation de la liste d’adresses IP autorisées de {% data variables.product.company_short %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Sous « Liste d’adresses IP autorisées », activez la liste d’adresses IP autorisées.
|
||||
- Si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC, sélectionnez le menu déroulant et cliquez sur **GitHub**.
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
|
||||
Sélectionnez **Activer la liste d’adresses IP autorisées**.
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
|
||||
- Si vous n’utilisez pas de {% data variables.product.prodname_emus %} avec OIDC, sélectionnez **Activer la liste d’adresses IP autorisées**.
|
||||
|
||||
1. Cliquez sur **Enregistrer**.
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Ajout d’une adresse IP autorisée
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Autorisation de l’accès par {% data variables.product.prodname_github_apps %}
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Modification d’une adresse IP autorisée
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% 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. Cliquez sur **Update**.
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Vérification de l’autorisation d’une adresse IP
|
||||
### Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Suppression d’une adresse IP autorisée
|
||||
### Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## Utilisation de la liste d’autorisations de votre fournisseur d’identité
|
||||
## Using your identity provider's allow list
|
||||
|
||||
Vous pouvez utiliser la liste d’autorisations de votre IdP si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC.
|
||||
{% note %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Sous « Liste d’adresses IP autorisées », sélectionnez la liste déroulante et cliquez sur **Fournisseur d’identité**.
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
|
||||
1. Si vous le souhaitez, pour autoriser les {% data variables.product.prodname_oauth_apps %} {% data variables.product.company_short %} installées à accéder à votre entreprise à partir de n’importe quelle adresse IP, sélectionnez **Ignorer la vérification de l’IdP pour les applications**.
|
||||
{% endnote %}
|
||||
|
||||
|
||||
1. Cliquez sur **Enregistrer**.
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Activation des adresses IP autorisées
|
||||
## Enabling allowed IP addresses
|
||||
|
||||
{% 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. Sous « Liste verte d’adresses IP », sélectionnez **Activer la liste verte d’adresses IP**.
|
||||
|
||||
4. Cliquez sur **Enregistrer**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## Ajout d’une adresse IP autorisée
|
||||
## Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Autorisation de l’accès par {% data variables.product.prodname_github_apps %}
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Modification d’une adresse IP autorisée
|
||||
## Editing an allowed IP address
|
||||
|
||||
{% 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. Cliquez sur **Update**.
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Vérification de l’autorisation d’une adresse IP
|
||||
## Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Suppression d’une adresse IP autorisée
|
||||
## Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## Utilisation de {% data variables.product.prodname_actions %} avec une liste verte d’adresses IP
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
title: Empreintes digitales de clé SSH de GitHub
|
||||
intro: Les empreintes digitales de clé publique peuvent être utilisées pour valider une connexion à un serveur distant.
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: SSH key fingerprints
|
||||
ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190329'
|
||||
---
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
Voici des exemples d’empreintes digitales de clé publique de {% data variables.product.prodname_dotcom %} :
|
||||
|
||||
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - déprécié)
|
||||
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
|
||||
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
|
||||
|
||||
You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
|
||||
Vous pouvez ajouter les entrées de clé ssh suivantes à votre fichier `~.ssh/known_hosts` pour éviter de vérifier manuellement les hôtes {% data variables.product.prodname_dotcom %} :
|
||||
|
||||
```text
|
||||
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
|
||||
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
|
||||
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|
||||
```
|
||||
|
||||
For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
|
||||
Pour plus d’informations, consultez « [Obtenir des informations sur Meta {% data variables.product.prodname_dotcom %}](/rest/meta#get-github-meta-information) ».
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using SSH over the HTTPS port
|
||||
intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
|
||||
title: Utilisation de SSH sur le port HTTPS
|
||||
intro: 'Parfois, les pare-feu refusent complètement d’autoriser les connexions SSH. Si vous n’avez pas la possibilité d’utiliser le [clonage HTTPS avec la mise en cache des informations d’identification](/github/getting-started-with-github/caching-your-github-credentials-in-git), vous pouvez tenter un clonage via la une connexion SSH établie sur le port HTTPS. Si la plupart des règles de pare-feu autorisent cela, les serveurs proxy peuvent néanmoins interférer.'
|
||||
redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
- /github/authenticating-to-github/using-ssh-over-the-https-port
|
||||
@@ -11,14 +11,20 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
shortTitle: Use SSH over HTTPS port
|
||||
ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190321'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
|
||||
**Utilisateurs de {% data variables.product.prodname_ghe_server %}** : l’accès à {% data variables.product.prodname_ghe_server %} via SSH sur le port HTTPS n’est pas pris en charge.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
To test if SSH over the HTTPS port is possible, run this SSH command:
|
||||
Pour tester s’il est possible d’utiliser SSH sur le port HTTPS, exécutez cette commande SSH :
|
||||
|
||||
```shell
|
||||
$ ssh -T -p 443 git@ssh.github.com
|
||||
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
|
||||
**Remarque** : Le nom d’hôte pour le port 443 est `ssh.{% data variables.command_line.backticks %}`, pas `{% data variables.command_line.backticks %}`.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
|
||||
Si cela a fonctionné, parfait ! Sinon, vous devrez peut-être [suivre notre guide de résolution des problèmes](/articles/error-permission-denied-publickey).
|
||||
|
||||
Now, to clone the repository, you can run the following command:
|
||||
À présent, pour cloner le dépôt, vous pouvez exécuter la commande suivante :
|
||||
|
||||
```
|
||||
$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
```
|
||||
|
||||
## Enabling SSH connections over HTTPS
|
||||
## Activation des connexions SSH sur HTTPS
|
||||
|
||||
If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
|
||||
Si vous êtes en mesure de vous connecter en mode SSH à `git@ssh.{% data variables.command_line.backticks %}` sur le port 443, vous pouvez remplacer vos paramètres SSH afin que toute connexion à {% data variables.location.product_location %} s’exécute via ce serveur et ce port.
|
||||
|
||||
To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
|
||||
Pour définir cela dans votre fichier de configuration SSH, modifiez le fichier à l’emplacement `~/.ssh/config`, puis ajoutez cette section :
|
||||
|
||||
```
|
||||
Host {% data variables.command_line.codeblock %}
|
||||
@@ -53,7 +59,7 @@ Port 443
|
||||
User git
|
||||
```
|
||||
|
||||
You can test that this works by connecting once more to {% data variables.location.product_location %}:
|
||||
Vous pouvez tester que cela fonctionne en vous reconnectant à {% data variables.location.product_location %} :
|
||||
|
||||
```shell
|
||||
$ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
> provide shell access.
|
||||
```
|
||||
|
||||
## Updating known hosts
|
||||
## Mise à jour des hôtes connus
|
||||
|
||||
The first time you interact with GitHub after switching to port 443, you may get a warning message
|
||||
that the host wasn't found in `known_hosts`, or that it was found by another name.
|
||||
La première fois que vous interagissez avec GitHub après avoir basculé sur le port 443, vous pouvez recevoir un message d’avertissement indiquant que l’hôte est introuvable dans `known_hosts`ou qu’il a été trouvé avec un autre nom.
|
||||
|
||||
```ShellSession
|
||||
> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
|
||||
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
|
||||
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
|
||||
```
|
||||
|
||||
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
|
||||
one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
|
||||
Vous pouvez répondre « oui » à cette question sans problème, en supposant que l’empreinte digitale SSH correspond à l’une des empreintes digitales publiées de GitHub. Pour obtenir la liste des empreintes digitales, consultez « [Empreintes digitales des clés SSH de Github](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints) ».
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
|
||||
ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179735'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148190060'
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,6 @@ ms.locfileid: '148179735'
|
||||
|
||||
Utilisez la bibliothèque Octokit officielle ou choisissez l’une des bibliothèques tierces disponibles.
|
||||
|
||||
- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
@@ -131,6 +130,7 @@ Utilisez la bibliothèque Octokit officielle ou choisissez l’une des biblioth
|
||||
|**github-flask**|[github-flask (site web officiel)](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|**octokit.py**|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ By default, authorized users can access your enterprise from any IP address. You
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
@@ -47,7 +47,7 @@ You can use {% data variables.product.company_short %}'s IP allow list to contro
|
||||
|
||||
## About your IdP's allow list
|
||||
|
||||
If you are using {% data variables.product.prodname_emus %} with OIDC, you can use your IdP's allow list.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
@@ -124,7 +124,11 @@ To ensure seamless use of the OIDC CAP while still applying the policy to user-t
|
||||
|
||||
## Using your identity provider's allow list
|
||||
|
||||
You can use your IdP's allow list if you use {% data variables.product.prodname_emus %} with OIDC.
|
||||
{% note %}
|
||||
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
title: GitHub の SSH キーフィンガープリント
|
||||
intro: パブリックキーフィンガープリントを使用して、リモートサーバへの接続を有効にすることができます。
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: SSH key fingerprints
|
||||
ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190331'
|
||||
---
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
{% data variables.product.prodname_dotcom %} の公開鍵のフィンガープリントは次のとおりです。
|
||||
|
||||
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - 非推奨)
|
||||
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
|
||||
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
|
||||
|
||||
You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
|
||||
`~.ssh/known_hosts` ファイルに次の ssh キー エントリを追加して、{% data variables.product.prodname_dotcom %} ホストの手動による検証を回避できます。
|
||||
|
||||
```text
|
||||
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
|
||||
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
|
||||
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|
||||
```
|
||||
|
||||
For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
|
||||
詳しくは、「[{% data variables.product.prodname_dotcom %} のメタ情報を取得する](/rest/meta#get-github-meta-information)」をご覧ください。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using SSH over the HTTPS port
|
||||
intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
|
||||
title: HTTPS ポートを介して SSH を使用する
|
||||
intro: '時々、ファイアウォールは SSH 接続を完全に許可することを拒否します。 [認証情報キャッシュを使用した HTTPS クローニング](/github/getting-started-with-github/caching-your-github-credentials-in-git) を使用することが選べない場合は、HTTPS ポート経由の SSH 接続を使用してクローンの作成を試みることができます。 ほとんどのファイアウォールルールでこれを許可する必要がありますが、プロキシサーバーが干渉する可能性があります。'
|
||||
redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
- /github/authenticating-to-github/using-ssh-over-the-https-port
|
||||
@@ -11,14 +11,20 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
shortTitle: Use SSH over HTTPS port
|
||||
ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190323'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
|
||||
**{% data variables.product.prodname_ghe_server %} ユーザー**: HTTPS ポートを介した SSH 経由での {% data variables.product.prodname_ghe_server %} へのアクセスは現在サポートされていません。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
To test if SSH over the HTTPS port is possible, run this SSH command:
|
||||
HTTPS ポート経由の SSH が可能かどうかをテストするには、次の SSH コマンドを実行します:
|
||||
|
||||
```shell
|
||||
$ ssh -T -p 443 git@ssh.github.com
|
||||
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
|
||||
**注**: ポート 443 のホスト名は、`{% data variables.command_line.backticks %}` ではなく `ssh.{% data variables.command_line.backticks %}` です。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
|
||||
うまく機能すれば、素晴らしいことです。 そうでない場合は、[トラブルシューティング ガイドに従って](/articles/error-permission-denied-publickey)ください。
|
||||
|
||||
Now, to clone the repository, you can run the following command:
|
||||
ここで、リポジトリをクローンするには、次のコマンドを実行できます。
|
||||
|
||||
```
|
||||
$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
```
|
||||
|
||||
## Enabling SSH connections over HTTPS
|
||||
## HTTPS を介した SSH 接続を有効化する
|
||||
|
||||
If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
|
||||
ポート 443 経由で `git@ssh.{% data variables.command_line.backticks %}` に SSH 接続できる場合は、SSH の設定をオーバーライドして、{% data variables.location.product_location %} への接続をそのサーバーとポートを通して実行するように強制できます。
|
||||
|
||||
To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
|
||||
SSH 構成ファイルでこれを設定するには、`~/.ssh/config` でファイルを編集し、次のセクションを追加します。
|
||||
|
||||
```
|
||||
Host {% data variables.command_line.codeblock %}
|
||||
@@ -53,7 +59,7 @@ Port 443
|
||||
User git
|
||||
```
|
||||
|
||||
You can test that this works by connecting once more to {% data variables.location.product_location %}:
|
||||
{% data variables.location.product_location %} にもう一度接続することで、これが機能することをテストできます。
|
||||
|
||||
```shell
|
||||
$ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
> provide shell access.
|
||||
```
|
||||
|
||||
## Updating known hosts
|
||||
## 既知のホストを更新する
|
||||
|
||||
The first time you interact with GitHub after switching to port 443, you may get a warning message
|
||||
that the host wasn't found in `known_hosts`, or that it was found by another name.
|
||||
ポート 443 に切り替えた後で GitHub を初めて使うときに、`known_hosts` でホストが見つからなかったか、別の名前で見つかったことを示す警告メッセージが、表示されることがあります。
|
||||
|
||||
```ShellSession
|
||||
> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
|
||||
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
|
||||
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
|
||||
```
|
||||
|
||||
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
|
||||
one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
|
||||
SSH のフィンガープリントが公開されている GitHub のフィンガープリントのいずれかと一致するなら、この質問に "はい" と答えても安全です。 フィンガープリントの一覧については、「[GitHub の SSH キーフィンガープリント](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)」をご覧ください。
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
|
||||
ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179737'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148190062'
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,6 @@ ms.locfileid: '148179737'
|
||||
|
||||
公式の Octokit ライブラリを使用するか、利用可能なサードパーティライブラリのいずれかを選択します。
|
||||
|
||||
- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
@@ -131,6 +130,7 @@ ms.locfileid: '148179737'
|
||||
|**github-flask**|[github-flask (公式 Web サイト)](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|**octokit.py**|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ By default, authorized users can access your enterprise from any IP address. You
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
@@ -47,7 +47,7 @@ You can use {% data variables.product.company_short %}'s IP allow list to contro
|
||||
|
||||
## About your IdP's allow list
|
||||
|
||||
If you are using {% data variables.product.prodname_emus %} with OIDC, you can use your IdP's allow list.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
@@ -124,7 +124,11 @@ To ensure seamless use of the OIDC CAP while still applying the policy to user-t
|
||||
|
||||
## Using your identity provider's allow list
|
||||
|
||||
You can use your IdP's allow list if you use {% data variables.product.prodname_emus %} with OIDC.
|
||||
{% note %}
|
||||
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -15,12 +15,12 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: Deleted or changes visibility
|
||||
ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: 95296f33d9163cd1171481386efd0a2351095c39
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146332732'
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: '148191370'
|
||||
---
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
|
||||
@@ -32,7 +32,7 @@ ms.locfileid: '146332732'
|
||||
|
||||
## 퍼블릭 리포지토리 삭제
|
||||
|
||||
퍼블릭 리포지토리를 삭제하면 기존 퍼블릭 포크 중 하나가 새 부모 리포지토리로 선택됩니다. 다른 모든 리포지토리는 이 새 부모에서 포크되고 후속 끌어오기 요청은 이 새 부모로 이동합니다.
|
||||
퍼블릭 리포지토리를 삭제하면 기존 퍼블릭 포크 중 하나가 새 업스트림 리포지토리로 선택됩니다. 다른 모든 리포지토리는 이 새로운 업스트림에서 포크되고 후속 끌어오기 요청은 이 새로운 업스트림 리포지토리로 이동합니다.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -44,9 +44,9 @@ ms.locfileid: '146332732'
|
||||
|
||||
## 퍼블릭 리포지토리를 프라이빗 리포지토리로 변경
|
||||
|
||||
퍼블릭 리포지토리가 프라이빗으로 전환되면 퍼블릭 포크가 새 네트워크로 분할됩니다. 퍼블릭 리포지토리 삭제와 마찬가지로 기존 퍼블릭 포크 중 하나가 새 부모 리포지토리로 선택되고 다른 모든 리포지토리는 이 새 부모에서 포크됩니다. 후속 끌어오기 요청은 이 새 부모로 이동합니다.
|
||||
퍼블릭 리포지토리가 프라이빗으로 전환되면 퍼블릭 포크가 새 네트워크로 분할됩니다. 퍼블릭 리포지토리 삭제와 마찬가지로 기존 퍼블릭 포크 중 하나가 새 업스트림 리포지토리로 선택되고 다른 모든 리포지토리는 이 새로운 업스트림에서 포크됩니다. 후속 끌어오기 요청은 이 새로운 업스트림 리포지토리로 이동합니다.
|
||||
|
||||
즉, 퍼블릭 리포지토리의 포크는 부모 리포지토리를 프라이빗으로 만든 후에도 별도의 리포지토리 네트워크에서 퍼블릭으로 유지됩니다. 이렇게 하면 포크 소유자가 중단 없이 계속 작업하고 협업할 수 있습니다. 이러한 방식으로 퍼블릭 포크를 별도의 네트워크로 이동하지 않은 경우, 해당 포크의 소유자는 이전에 해당 권한이 필요하지 않았더라도 변경 내용을 끌어오고 부모 리포지토리(지금은 프라이빗)에 끌어오기 요청을 제출하기 위한 적절한 [액세스 권한](/articles/access-permissions-on-github)을 얻어야 합니다.
|
||||
즉, 퍼블릭 리포지토리의 포크는 업스트림 리포지토리를 비공개로 만든 후에도 별도의 리포지토리 네트워크에서 공용으로 유지됩니다. 이렇게 하면 포크 소유자가 중단 없이 계속 작업하고 협업할 수 있습니다. 이러한 방식으로 퍼블릭 포크가 별도의 네트워크로 이동되지 않은 경우 해당 포크의 소유자는 이전에 해당 권한이 필요하지 않았음에도 불구하고 변경 내용을 끌어오고 (현재 프라이빗) 업스트림 리포지토리에 끌어오기 요청을 제출할 수 있는 적절한 [액세스 권한을](/articles/access-permissions-on-github) 가져와야 합니다.
|
||||
|
||||
{% ifversion ghes or ghae %} 퍼블릭 리포지토리에서 익명 Git 읽기 권한이 사용하도록 설정되어 있고 리포지토리가 프라이빗으로 설정된 경우, 모든 리포지토리의 포크는 익명 Git 읽기 권한을 잃고 사용되지 않는 기본 설정으로 돌아갑니다. 포크된 리포지토리가 퍼블릭으로 설정되면, 리포지토리 관리자는 익명 Git 읽기 권한을 다시 사용하도록 설정할 수 있습니다. 자세한 내용은 “[리포지토리에 익명 Git 읽기 권한 사용](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)”을 참조하세요.
|
||||
{% endif %}
|
||||
@@ -57,7 +57,7 @@ ms.locfileid: '146332732'
|
||||
|
||||
## 프라이빗 리포지토리를 퍼블릭 리포지토리로 변경
|
||||
|
||||
프라이빗 리포지토리가 퍼블릭으로 설정되면, 각 프라이빗 포크는 독립 실행형 프라이빗 리포지토리로 전환되고 새로운 자체 리포지토리 네트워크의 부모가 됩니다. 프라이빗 포크는 공개적으로 노출되어서는 안 되는 중요한 커밋을 포함할 수 있으므로 자동으로 퍼블릭으로 설정되지 않습니다.
|
||||
프라이빗 리포지토리가 공개되면 각 프라이빗 포크가 독립 실행형 프라이빗 리포지토리로 바뀌고 자체 새 리포지토리 네트워크의 업스트림이 됩니다. 프라이빗 포크는 공개적으로 노출되어서는 안 되는 중요한 커밋을 포함할 수 있으므로 자동으로 퍼블릭으로 설정되지 않습니다.
|
||||
|
||||
### 퍼블릭 리포지토리 삭제
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 리포지토리 간 연결 이해
|
||||
intro: 리포지토리의 네트워크와 포크 및 리포지토리에 의존하는 프로젝트를 확인하여 리포지토리 사이에 존재하는 연결을 더 잘 이해할 수 있습니다.
|
||||
title: Understanding connections between repositories
|
||||
intro: Use the network graph and forks list to understand fork networks.
|
||||
product: '{% data reusables.gated-features.repository-insights %}'
|
||||
redirect_from:
|
||||
- /articles/viewing-a-repository-s-network
|
||||
@@ -22,59 +22,57 @@ versions:
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: Connections between repositories
|
||||
ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147060068'
|
||||
---
|
||||
## 리포지토리의 네트워크 보기
|
||||
|
||||
네트워크 그래프는 루트 리포지토리의 분기 및 네트워크에 고유한 커밋이 포함된 포크 분기를 포함하여 전체 리포지토리 네트워크의 분기 기록을 보여 줍니다.
|
||||
## Viewing a repository's network
|
||||
|
||||
|
||||
The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**팁:** 이전 분기를 보려면 그래프 내에서 클릭하고 끕니다.
|
||||
**Tip:** To see older branches, click and drag within the graph.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 네트워크 그래프 액세스
|
||||
## Accessing the network graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. 왼쪽 사이드바에서 **네트워크** 를 클릭합니다.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Network**.
|
||||
|
||||
|
||||
## 리포지토리의 포크 나열
|
||||
## Listing the forks of a repository
|
||||
|
||||
멤버 그래프는 리포지토리의 모든 포크를 표시합니다.
|
||||
The Members graph displays all the forks of a repository.
|
||||
|
||||
포크는 리포지토리를 포크한 사용자의 사용자 이름 순서로 나열됩니다. 사용자 이름을 클릭하여 사용자의 {% data variables.product.product_name %} 프로필 페이지로 리디렉션하거나 포크 이름을 클릭하여 리포지토리의 특정 포크로 리디렉션할 수 있습니다.
|
||||
Forks are listed alphabetically by the organization or username of the person who forked the repository. You can click on the organization or username to be redirected to the organization or user's {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
### 멤버 그래프 액세스
|
||||
### Accessing the Members graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. 왼쪽 사이드바에서 **포크** 를 클릭합니다.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Forks**.
|
||||
|
||||
|
||||
## 리포지토리의 종속성 보기
|
||||
## Viewing the dependencies of a repository
|
||||
|
||||
종속성 그래프를 사용하여 리포지토리가 종속된 코드를 살펴볼 수 있습니다.
|
||||
You can use the dependency graph to explore the code your repository depends on.
|
||||
|
||||
거의 모든 소프트웨어는 공급망이라고도 하는 다른 개발자가 개발하고 유지 관리하는 코드를 사용합니다. 유틸리티, 라이브러리 및 프레임워크를 예로 들 수 있습니다. 이러한 종속성은 코드의 필수적인 부분이며 해당 버그 또는 취약성이 코드에 영향을 줄 수 있습니다. 이러한 종속성을 검토하고 유지 관리하는 것이 중요합니다.
|
||||
Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.
|
||||
|
||||
종속성 그래프는 리포지토리에 대한 종속성을 시각화하고 살펴보는 적절한 방법을 제공합니다. 자세한 내용은 "[종속성 그래프 정보](/code-security/supply-chain-security/about-the-dependency-graph)" 및 "[리포지토리의 종속성 살펴보기](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)"를 참조하세요.
|
||||
The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)."
|
||||
|
||||
또한 종속성 중 하나에서 보안 취약성이 발견되면 {% data variables.product.company_short %}가 자동으로 경고하도록 리포지토리를 설정할 수도 있습니다. 자세한 내용은 “[{% data variables.product.prodname_dependabot_alerts %} 정보](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”를 참조하세요.
|
||||
You can also set up your repository so that {% data variables.product.company_short %} alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
@@ -1 +1,9 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
---
|
||||
ms.openlocfilehash: 484a4230527deebe6f4aeb24ceabdf95eb75b492
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: "148191332"
|
||||
---
|
||||
{% data variables.enterprise.prodname_managed_users_caps %}은(는) 엔터프라이즈 외부에서 리포지토리를 포크할 수 없습니다. {% data variables.enterprise.prodname_managed_users_caps %}은 엔터프라이즈의 조직이 소유한 프라이빗 또는 내부 리포지토리를 엔터프라이즈 정책에 지정된 대로 사용자 계정 네임스페이스 또는 엔터프라이즈가 소유한 다른 조직으로 포크할 수 있습니다.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: eb538c8746bf9d5ec4cd0e422e50ccc032309812
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: "148191371"
|
||||
---
|
||||
포크는 원래 "업스트림" 리포지토리와 코드 및 표시 유형 설정을 공유하는 새 리포지토리입니다. 포크는 오픈 소스 프로젝트에서 또는 사용자가 업스트림 리포지토리에 대한 쓰기 액세스 권한이 없는 경우와 같이 업스트림 리포지토리에 다시 제안되기 전에 아이디어 또는 변경 내용을 반복하는 데 자주 사용됩니다.
|
||||
@@ -543,6 +543,7 @@ translations/zh-CN/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
@@ -579,7 +580,6 @@ translations/zh-CN/content/admin/identity-and-access-management/using-built-in-a
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
|
||||
@@ -638,7 +638,6 @@ translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
@@ -660,7 +659,6 @@ translations/zh-CN/content/authentication/troubleshooting-commit-signature-verif
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
@@ -924,6 +922,7 @@ translations/zh-CN/content/repositories/releasing-projects-on-github/automatical
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
|
||||
@@ -1060,7 +1059,6 @@ translations/zh-CN/data/reusables/enterprise-accounts/actions-packages-report-do
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags
|
||||
|
||||
|
@@ -483,9 +483,7 @@ translations/de-DE/content/actions/learn-github-actions/expressions.md,rendering
|
||||
translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
|
||||
translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
|
||||
translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
|
||||
translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,broken liquid tags
|
||||
translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
|
||||
translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,broken liquid tags
|
||||
translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
|
||||
translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
|
||||
translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
|
||||
@@ -542,6 +540,7 @@ translations/de-DE/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/de-DE/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/de-DE/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/de-DE/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
@@ -596,7 +595,6 @@ translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-ser
|
||||
translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error
|
||||
translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
|
||||
translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
|
||||
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,rendering error
|
||||
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error
|
||||
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error
|
||||
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
|
||||
@@ -746,6 +744,7 @@ translations/de-DE/content/code-security/security-advisories/global-security-adv
|
||||
translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
|
||||
translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
|
||||
translations/de-DE/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
|
||||
translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md,rendering error
|
||||
translations/de-DE/content/code-security/security-overview/about-the-security-overview.md,rendering error
|
||||
translations/de-DE/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
|
||||
translations/de-DE/content/code-security/security-overview/index.md,rendering error
|
||||
@@ -762,22 +761,16 @@ translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-code
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
|
||||
translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
|
||||
translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
|
||||
translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
|
||||
translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
|
||||
translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
|
||||
translations/de-DE/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
|
||||
translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
|
||||
translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
|
||||
translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
|
||||
translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
|
||||
translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
|
||||
translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags
|
||||
translations/de-DE/content/copilot/quickstart.md,broken liquid tags
|
||||
translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
|
||||
translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
|
||||
@@ -974,7 +967,6 @@ translations/de-DE/content/pull-requests/collaborating-with-pull-requests/propos
|
||||
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error
|
||||
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
|
||||
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
|
||||
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error
|
||||
translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
|
||||
translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
|
||||
translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
|
||||
@@ -1041,15 +1033,12 @@ translations/de-DE/content/rest/enterprise-admin/pre-receive-hooks.md,broken liq
|
||||
translations/de-DE/content/rest/enterprise-admin/repo-pre-receive-hooks.md,broken liquid tags
|
||||
translations/de-DE/content/rest/enterprise-admin/scim.md,rendering error
|
||||
translations/de-DE/content/rest/enterprise-admin/users.md,broken liquid tags
|
||||
translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags
|
||||
translations/de-DE/content/rest/guides/traversing-with-pagination.md,rendering error
|
||||
translations/de-DE/content/rest/guides/working-with-comments.md,broken liquid tags
|
||||
translations/de-DE/content/rest/migrations/source-imports.md,broken liquid tags
|
||||
translations/de-DE/content/rest/overview/api-previews.md,rendering error
|
||||
translations/de-DE/content/rest/overview/other-authentication-methods.md,rendering error
|
||||
translations/de-DE/content/rest/overview/permissions-required-for-github-apps.md,rendering error
|
||||
translations/de-DE/content/rest/overview/resources-in-the-rest-api.md,rendering error
|
||||
translations/de-DE/content/rest/overview/troubleshooting.md,broken liquid tags
|
||||
translations/de-DE/content/rest/packages.md,broken liquid tags
|
||||
translations/de-DE/content/rest/projects/projects.md,broken liquid tags
|
||||
translations/de-DE/content/rest/quickstart.md,broken liquid tags
|
||||
|
||||
|
@@ -565,6 +565,7 @@ translations/es-ES/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/es-ES/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
@@ -662,7 +663,6 @@ translations/es-ES/content/authentication/connecting-to-github-with-ssh/testing-
|
||||
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
|
||||
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
|
||||
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
|
||||
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
@@ -684,7 +684,6 @@ translations/es-ES/content/authentication/troubleshooting-commit-signature-verif
|
||||
translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
|
||||
translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
|
||||
translations/es-ES/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
|
||||
translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error
|
||||
translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
|
||||
translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
|
||||
translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
|
||||
|
@@ -532,6 +532,7 @@ translations/fr-FR/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/fr-FR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
@@ -637,7 +638,6 @@ translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/a
|
||||
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
|
||||
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
|
||||
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
|
||||
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md,rendering error
|
||||
@@ -663,7 +663,6 @@ translations/fr-FR/content/authentication/troubleshooting-ssh/error-agent-admitt
|
||||
translations/fr-FR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
|
||||
translations/fr-FR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error
|
||||
translations/fr-FR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
|
||||
translations/fr-FR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error
|
||||
translations/fr-FR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
|
||||
translations/fr-FR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
|
||||
translations/fr-FR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
|
||||
|
@@ -664,7 +664,6 @@ translations/ja-JP/content/authentication/connecting-to-github-with-ssh/testing-
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
@@ -684,7 +683,6 @@ translations/ja-JP/content/authentication/securing-your-account-with-two-factor-
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error
|
||||
translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
|
||||
translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
|
||||
|
@@ -1039,6 +1039,7 @@ translations/ko-KR/content/repositories/releasing-projects-on-github/automatical
|
||||
translations/ko-KR/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
|
||||
translations/ko-KR/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
|
||||
translations/ko-KR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
|
||||
translations/ko-KR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md,rendering error
|
||||
translations/ko-KR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
|
||||
translations/ko-KR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
|
||||
translations/ko-KR/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md,rendering error
|
||||
@@ -1181,7 +1182,6 @@ translations/ko-KR/data/reusables/enterprise-accounts/billing-microsoft-ea-overv
|
||||
translations/ko-KR/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md,rendering error
|
||||
translations/ko-KR/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
|
||||
translations/ko-KR/data/reusables/enterprise-accounts/emu-cap-validates.md,rendering error
|
||||
translations/ko-KR/data/reusables/enterprise-accounts/emu-forks.md,rendering error
|
||||
translations/ko-KR/data/reusables/enterprise-accounts/emu-only-emails-within-the-enterprise-can-conflict.md,rendering error
|
||||
translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-follow.md,rendering error
|
||||
translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-fork.md,rendering error
|
||||
|
||||
|
@@ -548,6 +548,7 @@ translations/pt-BR/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/pt-BR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
@@ -642,7 +643,6 @@ translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
@@ -664,7 +664,6 @@ translations/pt-BR/content/authentication/troubleshooting-commit-signature-verif
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error
|
||||
translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
|
||||
translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
|
||||
translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
|
||||
|
@@ -584,6 +584,7 @@ translations/ru-RU/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/ru-RU/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
|
||||
|
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Como restringir o tráfego de rede para sua empresa com uma lista de permissões de IP
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
shortTitle: Restricting network traffic
|
||||
intro: Você pode restringir o acesso à sua empresa e permitir o acesso aos seus recursos apenas de endereços IP especificados usando uma lista de permissões de IP.
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,150 +17,192 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: b62ab2a143ed0e7ec57f7e7225a09c0ca713295c
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185040'
|
||||
---
|
||||
## Sobre as restrições de tráfego de rede
|
||||
|
||||
Por padrão, os usuários autorizados podem acessar sua empresa a partir de qualquer endereço IP. Você pode restringir o acesso a recursos {% ifversion ghec %}pertencentes a organizações em uma conta corporativa {% endif %}configurando uma lista de permissões para endereços IP específicos. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
Se a sua empresa usa {% data variables.product.prodname_emus %} com o OIDC, você pode escolher se deseja adotar o recurso de lista de permissões de IP do {% data variables.product.company_short %} ou as restrições da lista de permissões do seu IdP (provedor de identidade). Se sua empresa não usa {% data variables.product.prodname_emus %} com o OIDC, você pode adotar o recurso de lista de permissões do {% data variables.product.company_short %}.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
Por padrão, as regras do grupo de segurança de rede do Azure (NSG) deixam todo o tráfego de entrada aberto nas portas 22, 80, 443 e 25. Você pode entrar em contato com o {% data variables.contact.github_support %} para configurar restrições de acesso ao {% data variables.product.product_name %}.
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
|
||||
Para restrições no uso do Azure NSGs, entre em contato com o {% data variables.contact.github_support %} com os endereços IP que têm permissão para acessar o {% data variables.product.product_name %}. Especifica os intervalos de endereços usando o formato CIDR padrão (Encaminhamento sem Classe entre Domínios). O {% data variables.contact.github_support %} vai configurar as regras de firewall apropriadas para restringir o acesso à rede por meio de HTTP, SSH, HTTPS e SMTP. Para obter mais informações, confira "[Como receber ajuda do {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)".
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Sobre a lista de permissões de IP do {% data variables.product.company_short %}
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
Você pode usar a lista de permissões de IP do {% data variables.product.company_short %} para controlar o acesso à sua empresa e a ativos pertencentes a organizações da sua empresa.
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
|
||||
{% 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 %}
|
||||
|
||||
## Sobre a lista de permissões do seu IdP
|
||||
## About your IdP's allow list
|
||||
|
||||
Se estiver usando o {% data variables.product.prodname_emus %} com o OIDC, você poderá usar a lista de permissões do seu IdP.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
O uso da lista de permissões do seu IdP desativa as configurações da lista de permissões de IP do {% data variables.product.company_short %} para todas as organizações da sua empresa e desativa as APIs do GraphQL para habilitar e gerenciar as listas de permissões de IP.
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
Por padrão, o IdP executa a CAP na entrada inicial interativa do SAML ou do OIDC no {% data variables.product.company_short %} para qualquer configuração de lista de permissões de IP escolhida.
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
|
||||
A CAP do OIDC só se aplica a solicitações à API usando um token de usuário para servidor, como um token para um {% data variables.product.prodname_oauth_app %} ou um {% data variables.product.prodname_github_app %} atuando em nome de um usuário. A CAP do OIDC não se aplica quando um {% data variables.product.prodname_github_app %} usa um token de servidor para servidor. Para obter mais informações, confira "[Como se autenticar com {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" e "[Sobre o suporte para a Política de Acesso Condicional de IdPs](/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)".
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/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)."
|
||||
|
||||
Para garantir o uso contínuo da CAP do OIDC enquanto ainda aplica a política a tokens de usuário para servidor, você deve copiar todos os intervalos de IP de cada {% data variables.product.prodname_github_app %} que sua empresa usa na política do IdP.
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
|
||||
## Como usar a lista de permissões de IP do {% data variables.product.company_short %}
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
### Como habilitar a lista de permissões de IP do {% data variables.product.company_short %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Em "Lista de permissões de IP", habilite a lista de permissões de IP.
|
||||
- Se você estiver usando o {% data variables.product.prodname_emus %} com o OIDC, selecione o menu suspenso e clique em **GitHub**.
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
|
||||
Selecione **Habilitar lista de permissões de IP**.
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
|
||||
- Se você não estiver usando o {% data variables.product.prodname_emus %} com o OIDC, selecione **Habilitar lista de permissões de IP**.
|
||||
|
||||
1. Clique em **Salvar**.
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Adicionar endereços IP permitidos
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Permitindo acesso de {% data variables.product.prodname_github_apps %}
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Editar endereços IP permitidos
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% 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. Clique em **Atualizar**.
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Verificando se um endereço IP é permitido
|
||||
### Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Excluir endereços IP permitidos
|
||||
### Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## Como usar a lista de permissões do seu provedor de identidade
|
||||
## Using your identity provider's allow list
|
||||
|
||||
Você pode adotar a lista de permissões do seu IdP se usar o {% data variables.product.prodname_emus %} com o OIDC.
|
||||
{% note %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Em "Lista de permissões de IP", selecione o menu suspenso e clique em **Provedor de Identidade**.
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
|
||||
1. Como alternativa, para permitir que os {% data variables.product.company_short %} e {% data variables.product.prodname_oauth_apps %} acessem sua empresa de qualquer endereço IP, selecione **Ignorar a verificação do IdP nos aplicativos**.
|
||||
{% endnote %}
|
||||
|
||||
|
||||
1. Clique em **Salvar**.
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Habilitar endereços IP permitidos
|
||||
## Enabling allowed IP addresses
|
||||
|
||||
{% 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. Em "Lista de IPs permitidos", selecione **Habilitar a lista de IPs permitidos**.
|
||||
|
||||
4. Clique em **Salvar**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## Adicionar endereços IP permitidos
|
||||
## Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Permitindo acesso de {% data variables.product.prodname_github_apps %}
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Editar endereços IP permitidos
|
||||
## Editing an allowed IP address
|
||||
|
||||
{% 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. Clique em **Atualizar**.
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Verificando se um endereço IP é permitido
|
||||
## Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Excluir endereços IP permitidos
|
||||
## Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
title: Impressões digitais da chave SSH do GitHub
|
||||
intro: Impressões digitais da chave pública podem ser usadas para validar uma conexão com um servidor remote.
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: SSH key fingerprints
|
||||
ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190327'
|
||||
---
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
Estas são as impressões digitais de chave pública de {% data variables.product.prodname_dotcom %}:
|
||||
|
||||
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA – preterida)
|
||||
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
|
||||
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
|
||||
|
||||
You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
|
||||
Você pode adicionar as seguintes entradas de chave ssh ao arquivo `~.ssh/known_hosts` para evitar verificar manualmente os hosts do {% data variables.product.prodname_dotcom %}:
|
||||
|
||||
```text
|
||||
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
|
||||
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
|
||||
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|
||||
```
|
||||
|
||||
For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
|
||||
Para obter mais informações, confira "[Obter metainformações do {% data variables.product.prodname_dotcom %}](/rest/meta#get-github-meta-information)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using SSH over the HTTPS port
|
||||
intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
|
||||
title: Usar SSH na porta HTTPS
|
||||
intro: 'Às vezes, os firewalls se recusam a permitir conexões SSH completamente. Se usar [clonagem de HTTPS com armazenamento de credenciais em cache](/github/getting-started-with-github/caching-your-github-credentials-in-git) não for uma opção, experimente clonar usando uma conexão SSH na porta HTTPS. A maioria das regras de firewall deve permitir isso, mas o servidores proxy podem interferir.'
|
||||
redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
- /github/authenticating-to-github/using-ssh-over-the-https-port
|
||||
@@ -11,14 +11,20 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
shortTitle: Use SSH over HTTPS port
|
||||
ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190319'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
|
||||
**Usuários {% data variables.product.prodname_ghe_server %}** : acessar {% data variables.product.prodname_ghe_server %} via SSH por porta HTTPS atualmente não tem suporte.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
To test if SSH over the HTTPS port is possible, run this SSH command:
|
||||
Para testar se o SSH na porta HTTPS é possível, execute este comando SSH:
|
||||
|
||||
```shell
|
||||
$ ssh -T -p 443 git@ssh.github.com
|
||||
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
|
||||
**Observação**: o nome do host da porta 443 é `ssh.{% data variables.command_line.backticks %}`, não `{% data variables.command_line.backticks %}`.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
|
||||
Se deu certo, ótimo! Caso contrário, talvez seja necessário [seguir nosso guia de solução de problemas](/articles/error-permission-denied-publickey).
|
||||
|
||||
Now, to clone the repository, you can run the following command:
|
||||
Agora, para clonar o repositório, você pode executar o seguinte comando:
|
||||
|
||||
```
|
||||
$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
```
|
||||
|
||||
## Enabling SSH connections over HTTPS
|
||||
## Habilitar conexões SSH por HTTPS
|
||||
|
||||
If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
|
||||
Se você conseguir usar SSH no `git@ssh.{% data variables.command_line.backticks %}` na porta 443, você poderá substituir as configurações de SSH para forçar qualquer conexão ao {% data variables.location.product_location %} a ser executada nesse servidor e nessa porta.
|
||||
|
||||
To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
|
||||
Para definir isso em seu arquivo de configuração SSH, edite o arquivo em `~/.ssh/config` e adicione esta seção:
|
||||
|
||||
```
|
||||
Host {% data variables.command_line.codeblock %}
|
||||
@@ -53,7 +59,7 @@ Port 443
|
||||
User git
|
||||
```
|
||||
|
||||
You can test that this works by connecting once more to {% data variables.location.product_location %}:
|
||||
Para testar se funciona, conecte-se mais uma vez ao {% data variables.location.product_location %}:
|
||||
|
||||
```shell
|
||||
$ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
> provide shell access.
|
||||
```
|
||||
|
||||
## Updating known hosts
|
||||
## Atualizando hosts conhecidos
|
||||
|
||||
The first time you interact with GitHub after switching to port 443, you may get a warning message
|
||||
that the host wasn't found in `known_hosts`, or that it was found by another name.
|
||||
Na primeira vez que você interagir com o GitHub depois de alternar para a porta 443, talvez receba uma mensagem de aviso informando que o host não foi encontrado no `known_hosts` ou que ele foi encontrado por outro nome.
|
||||
|
||||
```ShellSession
|
||||
> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
|
||||
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
|
||||
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
|
||||
```
|
||||
|
||||
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
|
||||
one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
|
||||
Você pode responder "sim" a essa pergunta, supondo que a impressão digital do SSH corresponde a uma das impressões digitais publicadas do GitHub. Para obter a lista de impressões digitais, confira "[Impressões digitais de chave SSH do Github](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)".
|
||||
|
||||
@@ -10,12 +10,12 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Stop a codespace
|
||||
ms.openlocfilehash: c09cd757ac2667c32c26f9b5e7d7a36b8e5431f9
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.openlocfilehash: 5c34fd5b7d72f52e203cd8f8fdc1871ff6a2f014
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185080'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188245'
|
||||
---
|
||||
{% jetbrains %}
|
||||
|
||||
@@ -110,4 +110,4 @@ Ao reiniciar um codespace, você pode optar por abri-lo no {% data variables.pro
|
||||
|
||||
## Leitura adicional
|
||||
|
||||
- "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
|
||||
- "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle)"
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
|
||||
ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179733'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148190058'
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,6 @@ ms.locfileid: '148179733'
|
||||
|
||||
Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.
|
||||
|
||||
- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
@@ -131,6 +130,7 @@ Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das biblioteca
|
||||
|**github-flask**|[github-flask (site oficial)](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|**octokit.py**|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Ограничение сетевого трафика для предприятия с помощью списка разрешенных IP-адресов
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
shortTitle: Restricting network traffic
|
||||
intro: Вы можете ограничить доступ к организации и разрешить доступ к ресурсам только с указанных IP-адресов с помощью списка разрешенных IP-адресов.
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,150 +17,192 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: b62ab2a143ed0e7ec57f7e7225a09c0ca713295c
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185046'
|
||||
---
|
||||
## Сведения об ограничениях сетевого трафика
|
||||
|
||||
По умолчанию авторизованные пользователи могут получить доступ к предприятию с любого IP-адреса. Вы можете ограничить доступ к ресурсам {% ifversion ghec %}, принадлежащим организациям в корпоративной учетной записи {% endif %}, настроив список разрешений для определенных IP-адресов. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
Если ваше предприятие использует {% data variables.product.prodname_emus %} с OIDC, вы можете выбрать, следует ли использовать функцию списка разрешенных IP-адресов {% data variables.product.company_short %} или использовать ограничения списка разрешений для поставщика удостоверений (IdP). Если ваше предприятие не использует {% data variables.product.prodname_emus %} с OIDC, можно использовать функцию списка разрешений {% data variables.product.company_short %}.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
По умолчанию правила группы безопасности сети (NSG) Azure оставляют весь входящий трафик открытым на портах 22, 80, 443 и 25. Вы можете связаться с {% data variables.contact.github_support %}, чтобы настроить ограничения доступа для {% data variables.product.product_name %}.
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
|
||||
Чтобы ограничить использование групп безопасности сети Azure, обратитесь в {% data variables.contact.github_support %} с IP-адресами, которым должен быть разрешен доступ к {% data variables.product.product_name %}. Укажите диапазоны адресов, используя стандартный формат CIDR (бесклассовая междоменная маршрутизация). {% data variables.contact.github_support %} настроит соответствующие правила брандмауэра, чтобы ограничить сетевой доступ по протоколам HTTP, SSH, HTTPS и SMTP. Дополнительные сведения см. в разделе [Получение помощи от {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support).
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Сведения о списке разрешенных IP-адресов {% data variables.product.company_short %}
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
Список разрешенных IP-адресов {% data variables.product.company_short %} можно использовать для управления доступом к предприятию и ресурсам, принадлежащим организациям предприятия.
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
|
||||
{% 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 %}
|
||||
|
||||
## Сведения о списке разрешений поставщика удостоверений
|
||||
## About your IdP's allow list
|
||||
|
||||
Если вы используете {% data variables.product.prodname_emus %} с OIDC, можно использовать список разрешений поставщика удостоверений.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
Использование списка разрешений поставщика удостоверений отключает конфигурации списка разрешений IP-адресов {% data variables.product.company_short %} для всех организаций на предприятии и отключает API GraphQL для включения списков разрешенных IP-адресов и управления ими.
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
По умолчанию поставщик удостоверений запускает CAP при начальном интерактивном входе SAML или OIDC в {% data variables.product.company_short %} для любой выбранной конфигурации списка разрешенных IP-адресов.
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
|
||||
OIDC CAP применяется только к запросам к API с использованием маркера "пользователь—сервер", например маркера для {% data variables.product.prodname_oauth_app %} или {% data variables.product.prodname_github_app %}, действующего от имени пользователя. Cap OIDC не применяется, если {% data variables.product.prodname_github_app %} использует токен "сервер-сервер". Дополнительные сведения см. в разделах [Проверка подлинности с помощью {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)и [Сведения о поддержке политики условного доступа поставщиков удостоверений](/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).
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/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)."
|
||||
|
||||
Чтобы обеспечить беспроблемное использование OIDC CAP при одновременном применении политики к маркерам от пользователя к серверу, необходимо скопировать все диапазоны IP-адресов из каждого {% data variables.product.prodname_github_app %}, который использует ваше предприятие, в политику поставщика удостоверений.
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
|
||||
## Использование списка разрешенных IP-адресов {% data variables.product.company_short %}
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
### Включение списка разрешенных IP-адресов {% data variables.product.company_short %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. В разделе "Список разрешенных IP-адресов" включите список разрешенных IP-адресов.
|
||||
- Если вы используете {% data variables.product.prodname_emus %} с OIDC, выберите раскрывающееся меню и щелкните **GitHub**.
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
|
||||
Выберите **Включить список разрешенных IP-адресов**.
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
|
||||
- Если вы не используете {% data variables.product.prodname_emus %} с OIDC, выберите **Включить список разрешенных IP-адресов**.
|
||||
|
||||
1. Выберите команду **Сохранить**.
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Добавление разрешенного IP-адреса
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Разрешение доступа {% data variables.product.prodname_github_apps %}
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Изменение разрешенного IP-адреса
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% 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. Нажмите кнопку **Обновить**.
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Проверка допустимости IP-адреса
|
||||
### Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### Удаление разрешенного IP-адреса
|
||||
### Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## Использование списка разрешений поставщика удостоверений
|
||||
## Using your identity provider's allow list
|
||||
|
||||
Вы можете использовать список разрешений поставщика удостоверений, если используете {% data variables.product.prodname_emus %} с OIDC.
|
||||
{% note %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. В разделе "Список разрешенных IP-адресов" выберите раскрывающийся список и щелкните **Поставщик удостоверений**.
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
|
||||
1. При необходимости, чтобы разрешить установленным {% data variables.product.company_short %} и {% data variables.product.prodname_oauth_apps %} доступ к организации с любого IP-адреса, выберите **Пропустить проверку поставщика удостоверений для приложений**.
|
||||
{% endnote %}
|
||||
|
||||
|
||||
1. Выберите команду **Сохранить**.
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Включение разрешенных IP-адресов
|
||||
## Enabling allowed IP addresses
|
||||
|
||||
{% 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. В разделе "Список разрешенных IP-адресов" выберите **Включить список разрешенных IP-адресов**.
|
||||
|
||||
4. Выберите команду **Сохранить**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## Добавление разрешенного IP-адреса
|
||||
## Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Разрешение доступа {% data variables.product.prodname_github_apps %}
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Изменение разрешенного IP-адреса
|
||||
## Editing an allowed IP address
|
||||
|
||||
{% 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. Нажмите кнопку **Обновить**.
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Проверка допустимости IP-адреса
|
||||
## Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## Удаление разрешенного IP-адреса
|
||||
## Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %} со списком разрешенных IP-адресов
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: 使用 IP 允许列表限制到企业的网络流量
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
shortTitle: Restricting network traffic
|
||||
intro: 可以使用 IP 允许列表限制对企业的访问，仅允许从指定的 IP 地址访问资源。
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,150 +17,192 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: b62ab2a143ed0e7ec57f7e7225a09c0ca713295c
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185041'
|
||||
---
|
||||
## 关于网络流量限制
|
||||
|
||||
默认情况下，授权用户可以从任何 IP 地址访问您的企业。 可以通过为特定 IP 地址配置允许列表来限制对{% ifversion ghec %}企业帐户中组织拥有的{% endif %}资源的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
如果你的企业将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，你则可以选择是使用 {% data variables.product.company_short %} 的 IP 允许列表功能，还是为标识提供者 (IdP) 使用允许列表限制。 如果你的企业未将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，你则可以使用 {% data variables.product.company_short %} 的允许列表功能。
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
默认情况下，Azure 网络安全组 (NSG) 规则允许所有入站流量在端口 22、80、443 和 25 打开。 可以联系 {% data variables.contact.github_support %} 为 {% data variables.product.product_name %} 配置访问限制。
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
|
||||
对于使用 Azure NSG 的限制，请联系 {% data variables.contact.github_support %} 以获取应允许访问 {% data variables.product.product_name %} 的 IP 地址。 使用标准 CIDR（无类域间路由）格式指定地址范围。 {% data variables.contact.github_support %} 将配置合适的防火墙规则，以限制通过 HTTP、SSH、HTTPS 和 SMTP 的网络访问。 有关详细信息，请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## 关于 {% data variables.product.company_short %} 的 IP 允许列表
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
可以使用 {% data variables.product.company_short %} 的 IP 允许列表来控制对企业和企业中组织拥有的资产的访问。
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
|
||||
{% 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 %}
|
||||
|
||||
## 关于 IdP 的允许列表
|
||||
## About your IdP's allow list
|
||||
|
||||
如果将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，则可以使用 IdP 的允许列表。
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
使用 IdP 的允许列表会停用企业中所有组织的 {% data variables.product.company_short %} IP 允许列表配置，并停用 GraphQL API 以启用和管理 IP 允许列表。
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
默认情况下，你的 IdP 会在初始交互式 SAML 或 OIDC 登录到 {% data variables.product.company_short %} 时为你所选择的任何 IP 允许列表配置运行 CAP。
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
|
||||
OIDC CAP 仅适用于使用用户到服务器令牌对 API 的请求，例如 {% data variables.product.prodname_oauth_app %} 或代表用户操作的 {% data variables.product.prodname_github_app %} 的令牌。 当 {% data variables.product.prodname_github_app %} 使用服务器到服务器令牌时，OIDC CAP 不适用。 有关详细信息，请参阅“[使用 {% data variables.product.prodname_github_apps %} 进行身份验证](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)”和“[关于对 IdP 条件访问策略的支持](/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)”。
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/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)."
|
||||
|
||||
为了确保在将策略应用到用户到服务器令牌的同时无缝使用 OIDC CAP，必须将企业使用的每个 {% data variables.product.prodname_github_app %} 中的所有 IP 范围复制到 IdP 策略。
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
|
||||
## 使用 {% data variables.product.company_short %} 的 IP 允许列表
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
### 启用 {% data variables.product.company_short %} 的 IP 允许列表
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. 在“IP 允许列表”下，启用 IP 允许列表。
|
||||
- 如果将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，请选择下拉菜单并单击“GitHub”。
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
|
||||
选择“启用 IP 允许列表”。
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
|
||||
- 如果未将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，请选择“启用 IP 允许列表”。
|
||||
|
||||
1. 单击“ **保存**”。
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### 添加允许的 IP 地址
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### 允许 {% data variables.product.prodname_github_apps %} 访问
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### 编辑允许的 IP 地址
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% 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. 单击“更新”。
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### 检查是否允许使用 IP 地址
|
||||
### Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
### 删除允许的 IP 地址
|
||||
### Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %}
|
||||
|
||||
## 使用标识提供者的允许列表
|
||||
## Using your identity provider's allow list
|
||||
|
||||
如果将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，则可以使用 IdP 的允许列表。
|
||||
{% note %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. 在“IP 允许列表”下，选择下拉列表并单击“标识提供者”。
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
|
||||
1. （可选）若要允许已安装的 {% data variables.product.company_short %} 和 {% data variables.product.prodname_oauth_apps %} 从任意 IP 地址访问你的企业，请选择“为应用程序跳过 IdP 检查”。
|
||||
{% endnote %}
|
||||
|
||||
|
||||
1. 单击“ **保存**”。
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## 启用允许的 IP 地址
|
||||
## Enabling allowed IP addresses
|
||||
|
||||
{% 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. 在“IP 允许列表”下，选择“启用 IP 允许列表”。
|
||||
|
||||
4. 单击“ **保存**”。
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## 添加允许的 IP 地址
|
||||
## Adding an allowed IP address
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## 允许 {% data variables.product.prodname_github_apps %} 访问
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## 编辑允许的 IP 地址
|
||||
## Editing an allowed IP address
|
||||
|
||||
{% 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. 单击“更新”。
|
||||
{% 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. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## 检查是否允许使用 IP 地址
|
||||
## Checking if an IP address is permitted
|
||||
|
||||
{% 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 %}
|
||||
{% 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 %}
|
||||
|
||||
## 删除允许的 IP 地址
|
||||
## Deleting an allowed 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.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% 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 %} 使用 IP 允许列表
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About {% data variables.product.prodname_emus %}
|
||||
title: '关于 {% data variables.product.prodname_emus %}'
|
||||
shortTitle: About managed users
|
||||
intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
|
||||
intro: '可以从标识提供者的 {% data variables.product.prodname_dotcom %} 上集中管理企业成员的标识和访问。'
|
||||
redirect_from:
|
||||
- /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
|
||||
@@ -17,48 +17,53 @@ topics:
|
||||
- Enterprise
|
||||
- SSO
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 72d8263029317783e60d8f81f45edc3dbb8b1c8b
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180011'
|
||||
---
|
||||
## 关于 {% data variables.product.prodname_emus %}
|
||||
|
||||
## About {% data variables.product.prodname_emus %}
|
||||
使用 {% data variables.product.prodname_emus %}，可以通过标识提供者 (IdP) 控制企业成员的用户帐户。 IdP 中分配给 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户将会预配为 {% data variables.product.prodname_dotcom %} 上的新用户帐户，并添加到企业中。 可以通过 IdP 控制用户帐户的用户名、配置文件数据、团队成员身份和存储库访问权限。
|
||||
|
||||
With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
|
||||
|
||||
In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
|
||||
在 IdP 中，你可以为每个 {% data variables.enterprise.prodname_managed_user %} 提供用户、企业所有者或计费管理员的角色。 {% data variables.enterprise.prodname_managed_users_caps %} 可以拥有企业内的组织，并且可以将其他 {% data variables.enterprise.prodname_managed_users %} 添加到组织和其中的团队。 有关详细信息，请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)”和“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。
|
||||
|
||||
{% ifversion oidc-for-emu %}
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %} 有关详细信息，请参阅“[关于对 IdP 的条件访问策略的支持](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)”。
|
||||
|
||||
{% endif %}
|
||||
|
||||
You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
|
||||
可以授予 {% data variables.enterprise.prodname_managed_users %} 访问权限以及参与企业内部存储库的能力，但 {% data variables.enterprise.prodname_managed_users %} 无法创建公共内容，也不能与其他用户、组织和企业协作处理 {% data variables.product.prodname_dotcom %} 的其余部分。 有关详细信息，请参阅“[{% data variables.enterprise.prodname_managed_users %} 的功能和限制](#abilities-and-restrictions-of-enterprise-managed-users)”。
|
||||
|
||||
The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
|
||||
企业的 {% data variables.enterprise.prodname_managed_users %} 的用户名及其个人资料信息（例如显示名称和电子邮件地址）通过 IdP 设置，用户无法自行更改。 有关详细信息，请参阅“[用户名和个人资料信息](#usernames-and-profile-information)”。
|
||||
|
||||
Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
|
||||
企业所有者可以在 {% data variables.product.prodname_dotcom %} 上审核所有 {% data variables.enterprise.prodname_managed_users %} 的操作。 有关详细信息，请参阅“[企业的审核日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)”。
|
||||
|
||||
To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
|
||||
若要使用 {% data variables.product.prodname_emus %}，需要启用了 {% data variables.product.prodname_emus %} 的单独企业帐户类型。 有关创建此帐户的详细信息，请参阅“[关于具有托管用户的企业](#about-enterprises-with-managed-users)”。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)."
|
||||
注意：使用 {% data variables.product.prodname_ghe_cloud %} 进行标识和访问管理有多个选项，而 {% data variables.product.prodname_emus %} 并不是每个客户的最佳解决方案。 如需详细了解 {% data variables.product.prodname_emus %} 是否适合你的企业，请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About organization membership management
|
||||
## 关于组织成员身份管理
|
||||
|
||||
Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
|
||||
可手动管理组织成员身份，也可使用 IdP 组自动更新成员身份。 要通过 IdP 管理组织成员身份，必须将成员添加到 IdP 组，并且 IdP 组必须连接到组织内的团队。 有关自动管理组织和团队成员身份的详细信息，请参阅“[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)”。
|
||||
|
||||
The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization.
|
||||
将成员添加到企业拥有的组织的方式（通过 IdP 组或手动）决定了必须如何从组织中删除他们。
|
||||
|
||||
- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
|
||||
- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
|
||||
- 如果将成员手动添加到组织，则必须手动将其删除。 从 IdP 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序中取消分配他们，将暂停用户，但不会将其从组织中删除。
|
||||
- 如果用户由于被添加到映射到组织中的一个或多个团队的 IdP 组而成为该组织的成员，则从与组织关联的所有映射的 IdP 组中删除这些用户会将其从组织中删除。
|
||||
|
||||
To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
|
||||
要了解成员是如何添加到组织中的，可以按类型筛选成员列表。 有关详细信息，请参阅[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)。
|
||||
|
||||
## Identity provider support
|
||||
## 标识提供者支持
|
||||
|
||||
{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
|
||||
{% data variables.product.prodname_emus %} 支持以下 IdP{% ifversion oidc-for-emu %} 和身份验证方法：
|
||||
|
||||
| | SAML | OIDC |
|
||||
|----------------------------------|-----------------------------------------------|-----------------------------------------------|
|
||||
@@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
|
||||
## {% data variables.enterprise.prodname_managed_users %} 的功能和限制
|
||||
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} 只能参与企业中的专用和内部存储库及其用户帐户拥有的专用存储库。 {% data variables.enterprise.prodname_managed_users_caps %} 对更广泛的 {% data variables.product.prodname_dotcom %} 社区具有只读访问权限。 这些针对用户和内容的可见性和访问限制适用于所有请求，包括 API 请求。
|
||||
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises.
|
||||
* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
|
||||
* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
|
||||
* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
|
||||
* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
|
||||
* 不能邀请 {% data variables.enterprise.prodname_managed_users_caps %} 加入企业外部的组织或存储库，也不能邀请 {% data variables.enterprise.prodname_managed_users %} 加入其他企业。
|
||||
* {% data variables.product.prodname_emus %} 不支持外部协作者。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 无法在企业外部的存储库中创建问题或拉取请求、添加评论或添加反应，也不能加注星标、监视或创建分支。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 可以查看 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共存储库，但无法将代码推送到企业外部的存储库。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 和创建的内容只对企业的其他成员可见。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 无法关注企业外部的用户。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 无法创建 Gist 或对 Gist 添加评论。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 无法为 {% data variables.product.prodname_actions %} 创建入门工作流。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 无法在其用户帐户上安装 {% data variables.product.prodname_github_apps %}。
|
||||
* 其他 {% data variables.product.prodname_dotcom %} 用户无法查看、提及或邀请 {% data variables.enterprise.prodname_managed_user %} 进行协作。
|
||||
* 可以选择 {% data variables.enterprise.prodname_managed_users %} 是否能够创建其用户帐户拥有的存储库。 有关详细信息，请参阅“[在企业中实施存储库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)”。
|
||||
* 如果允许 {% data variables.enterprise.prodname_managed_users %} 创建其用户帐户拥有的存储库，则他们只能拥有专用存储库，并且只能邀请其他企业成员协作处理其用户拥有的存储库。
|
||||
* {% data reusables.enterprise-accounts.emu-forks %}
|
||||
* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
|
||||
* 只能在 {% data variables.enterprise.prodname_emu_enterprise %} 拥有的组织中创建专用和内部存储库，具体取决于组织和企业存储库可见性设置。
|
||||
* {% data variables.enterprise.prodname_managed_users_caps %} 在使用 {% data variables.product.prodname_pages %} 方面受到限制。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)”。
|
||||
* {% data reusables.copilot.emus-cannot-use-copilot %}
|
||||
|
||||
## Getting started with {% data variables.product.prodname_emus %}
|
||||
## {% data variables.product.prodname_emus %} 入门
|
||||
|
||||
Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
|
||||
必须先执行一系列配置步骤，开发人员才能将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_emus %} 一起使用。
|
||||
|
||||
1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
|
||||
1. 若要使用 {% data variables.product.prodname_emus %}，需要启用了 {% data variables.product.prodname_emus %} 的单独企业帐户类型。 若要试用 {% data variables.product.prodname_emus %} 或讨论从现有企业迁移的选项，请联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)。
|
||||
|
||||
Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
|
||||
GitHub 销售团队的联系人将与你合作创建新的 {% data variables.enterprise.prodname_emu_enterprise %}。 你需要为将设置企业的用户提供电子邮件地址，以及一个短代码，该代码将用作企业成员用户名的后缀。 {% data reusables.enterprise-accounts.emu-shortcode %} 有关详细信息，请参阅“[用户名和个人资料信息](#usernames-and-profile-information)”。
|
||||
|
||||
2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`.
|
||||
2. 创建企业后，你将收到来自 {% data variables.product.prodname_dotcom %} 的电子邮件，邀请你为企业的设置用户选择密码，该用户将是企业的第一个所有者。 设置密码时，请使用隐身或专用浏览窗口。 设置用户仅用于为企业配置单一登录和 SCIM 预配集成。 成功启用 SSO 后，设置用户将不再有权管理企业帐户。 设置用户的用户名是企业的短代码，后缀为 `_admin`。
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
|
||||
|
||||
{% endnote %}
|
||||
|
||||
3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
|
||||
3. 你以设置用户身份登录后，我们建议你启用双因素身份验证。 有关详细信息，请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。
|
||||
|
||||
1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). We recommend OIDC, which includes support for Conditional Access Policies (CAP). If you require multiple enterprises with {% data variables.enterprise.prodname_managed_users %} provisioned from one tenant, you must use SAML for each enterprise after the first. If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
|
||||
1. 首先，请配置 {% ifversion oidc-for-emu %} 成员如何进行身份验证。 如果使用 Azure Active Directory 作为标识提供者，可以在 OpenID Connect (OIDC) 和安全断言标记语言 (SAML) 之间进行选择。 建议使用 OIDC，其中包括对条件访问策略 (CAP) 的支持。 如果需要从一个租户预配具有 {% data variables.enterprise.prodname_managed_users %} 的多个企业，则必须在第一个之后为每个企业使用 SAML。 如果使用 Okta 作为标识提供者，则可以使用 SAML 对成员进行身份验证。{% else %}SAML SSO 适用于企业。 有关详细信息，请参阅“[为 Enterprise 托管用户配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。{% endif %}
|
||||
|
||||
{% ifversion oidc-for-emu %}
|
||||
|
||||
To get started, read the guide for your chosen authentication method.
|
||||
首先，请阅读所选身份验证方法的指南。
|
||||
|
||||
- "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
- "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
|
||||
- “[为企业托管用户配置 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)”。
|
||||
- “[为企业托管用户配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。
|
||||
|
||||
{% endif %}
|
||||
|
||||
4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
|
||||
4. 配置 SSO 后，可以配置 SCIM 预配。 SCIM 是标识提供者在 {% data variables.product.prodname_dotcom_the_website %} 上创建 {% data variables.enterprise.prodname_managed_users %} 的方式。 有关配置 SCIM 预配的详细信息，请参阅“[为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。
|
||||
|
||||
5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
|
||||
5. 配置身份验证和预配后，可以通过将 IdP 组与团队同步来开始管理 {% data variables.enterprise.prodname_managed_users %} 的组织成员身份。 有关详细信息，请参阅[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)。
|
||||
|
||||
If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
|
||||
如果企业成员必须使用一个工作站同时从 {% data variables.enterprise.prodname_managed_user %} 和个人帐户参与 {% data variables.location.product_location %} 上的存储库，则可以提供支持。 有关详细信息，请参阅“[支持在 {% data variables.product.prodname_dotcom_the_website %} 上具有多个用户帐户的开发人员](#supporting-developers-with-multiple-user-accounts-on-githubcom)”。
|
||||
|
||||
## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
|
||||
## 作为 {% data variables.enterprise.prodname_managed_user %} 进行身份验证
|
||||
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} 必须通过其标识提供者进行身份验证。 若要进行身份验证，{% data variables.enterprise.prodname_managed_user %} 可以访问其 IdP 应用程序门户或使用 {% data variables.product.prodname_dotcom_the_website %} 上的登录页。
|
||||
|
||||
By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
|
||||
默认情况下，当未经身份验证的用户尝试访问使用 {% data variables.product.prodname_emus %} 的企业时，{% data variables.product.company_short %} 会显示 404 错误。 企业所有者可以选择性地启用自动重定向到单一登录 (SSO)，而不会显示 404。 有关详细信息，请参阅“[为企业中的安全设置强制实施策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)."
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} 有关详细信息，请参阅“[管理企业的恢复代码](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)”。
|
||||
|
||||
### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
|
||||
### 通过 {% data variables.product.prodname_dotcom_the_website %} 作为 {% data variables.enterprise.prodname_managed_user %} 进行身份验证
|
||||
|
||||
1. Navigate to [https://github.com/login](https://github.com/login).
|
||||
1. In the "Username or email address" text box, enter your username including the underscore and short code.
|
||||
|
||||
When the form recognizes your username, the form will update. You do not need to enter your password on this form.
|
||||
1. To continue to your identity provider, click **Sign in with your identity provider**.
|
||||
|
||||
1. 导航到 [https://github.com/login](https://github.com/login)。
|
||||
1. 在“用户名或电子邮件地址”文本框中，输入用户名，包括下划线和短代码。
|
||||
 表单识别用户名后将更新。 无需在此表单中输入密码。
|
||||
1. 若要继续访问标识提供者，请单击“使用标识提供者登录”。
|
||||
|
||||
|
||||
## Usernames and profile information
|
||||
## 用户名和个人资料信息
|
||||
|
||||
{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
|
||||
{% data variables.product.product_name %} 通过规范 IdP 提供的标识符自动为每个用户创建用户名。 有关详细信息，请参阅“[外部身份验证的用户名注意事项](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)”。
|
||||
|
||||
A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
|
||||
如果在规范化期间删除 IdP 提供的标识符的唯一部分，则预配用户时可能会发生冲突。 如果由于用户名冲突而无法预配用户，则应修改 IdP 提供的用户名。 有关详细信息，请参阅“[解决用户名问题](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %}
|
||||
|
||||
The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
|
||||
IdP 还提供了 {% data variables.enterprise.prodname_managed_user %} 的个人资料名称和电子邮件地址。 {% data variables.enterprise.prodname_managed_users_caps %} 无法更改 {% data variables.product.prodname_dotcom %} 上的个人资料名称或电子邮件地址，并且 IdP 仅可提供单个电子邮件地址。
|
||||
|
||||
## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
|
||||
## 支持在 {% data variables.location.product_location %} 上具有多个用户帐户的开发人员
|
||||
|
||||
People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
|
||||
团队中的人员可能需要在 {% data variables.location.product_location %} 上参与 {% data variables.enterprise.prodname_emu_enterprise %} 外部的资源。 例如，你可能希望为公司的开放源代码项目维护单独的企业。 由于 {% data variables.enterprise.prodname_managed_user %} 无法参与公共资源，因此用户需要为此工作维护单独的个人帐户。
|
||||
|
||||
People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
|
||||
必须使用一个工作站在 {% data variables.location.product_location %} 上从两个用户帐户进行参与的人员可以配置 Git 以简化该过程。 有关详细信息，请参阅“[管理多个帐户](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)”。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
title: GitHub 的 SSH 密钥指纹
|
||||
intro: 公钥指纹可用于验证与远程服务器的连接。
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: SSH key fingerprints
|
||||
ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190328'
|
||||
---
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
以下是 {% data variables.product.prodname_dotcom %} 的公钥指纹：
|
||||
|
||||
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ`（DSA - 已弃用）
|
||||
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
|
||||
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
|
||||
|
||||
You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
|
||||
可以将以下 ssh 密钥条目添加到 `~.ssh/known_hosts` 文件中，以避免手动验证 {% data variables.product.prodname_dotcom %} 主机：
|
||||
|
||||
```text
|
||||
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
|
||||
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
|
||||
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|
||||
```
|
||||
|
||||
For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
|
||||
有关详细信息，请参阅“[获取 {% data variables.product.prodname_dotcom %} 元信息](/rest/meta#get-github-meta-information)”。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using SSH over the HTTPS port
|
||||
intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
|
||||
title: 在 HTTPS 端口使用 SSH
|
||||
intro: '有时，防火墙会完全拒绝允许 SSH 连接。 如果无法选择使用[具有凭据缓存的 HTTPS 克隆](/github/getting-started-with-github/caching-your-github-credentials-in-git)，可以尝试使用通过 HTTPS 端口建立的 SSH 连接克隆。 大多数防火墙规则应允许此操作，但代理服务器可能会干扰。'
|
||||
redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
- /github/authenticating-to-github/using-ssh-over-the-https-port
|
||||
@@ -11,14 +11,20 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
shortTitle: Use SSH over HTTPS port
|
||||
ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190320'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
|
||||
{% data variables.product.prodname_ghe_server %} 用户：目前不支持经 SSH 通过 HTTPS 端口访问 {% data variables.product.prodname_ghe_server %}。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
To test if SSH over the HTTPS port is possible, run this SSH command:
|
||||
要测试通过 HTTPS 端口的 SSH 是否可行，请运行以下 SSH 命令：
|
||||
|
||||
```shell
|
||||
$ ssh -T -p 443 git@ssh.github.com
|
||||
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
|
||||
注意：端口 443 的主机名为 `ssh.{% data variables.command_line.backticks %}`，而不是 `{% data variables.command_line.backticks %}`。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
|
||||
如果这样有效，万事大吉！ 否则，可能需要[遵循我们的故障排除指南](/articles/error-permission-denied-publickey)。
|
||||
|
||||
Now, to clone the repository, you can run the following command:
|
||||
现在，若要克隆存储库，可以运行以下命令：
|
||||
|
||||
```
|
||||
$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
```
|
||||
|
||||
## Enabling SSH connections over HTTPS
|
||||
## 启用通过 HTTPS 的 SSH 连接
|
||||
|
||||
If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
|
||||
如果你能在端口 443 上通过 SSH 连接到 `git@ssh.{% data variables.command_line.backticks %}`，则可覆盖你的 SSH 设置来强制与 {% data variables.location.product_location %} 的任何连接均通过该服务器和端口运行。
|
||||
|
||||
To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
|
||||
要在 SSH 配置文件中设置此行为，请在 `~/.ssh/config` 编辑该文件，并添加以下部分：
|
||||
|
||||
```
|
||||
Host {% data variables.command_line.codeblock %}
|
||||
@@ -53,7 +59,7 @@ Port 443
|
||||
User git
|
||||
```
|
||||
|
||||
You can test that this works by connecting once more to {% data variables.location.product_location %}:
|
||||
你可以通过再次连接到 {% data variables.location.product_location %} 来测试这是否有效：
|
||||
|
||||
```shell
|
||||
$ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
> provide shell access.
|
||||
```
|
||||
|
||||
## Updating known hosts
|
||||
## 更新已知主机
|
||||
|
||||
The first time you interact with GitHub after switching to port 443, you may get a warning message
|
||||
that the host wasn't found in `known_hosts`, or that it was found by another name.
|
||||
在切换到端口 443 后第一次与 GitHub 交互时，你可能会收到一条警告消息，指出在 `known_hosts` 中找不到主机，或者该主机由其他名称找到。
|
||||
|
||||
```ShellSession
|
||||
> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
|
||||
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
|
||||
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
|
||||
```
|
||||
|
||||
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
|
||||
one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
|
||||
假设 SSH 指纹与 GitHub 发布的指纹之一匹配，那么可以针对这个问题安全地回答“是”。 有关指纹列表，请参阅“[Github 的 SSH 密钥指纹](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)”。
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -15,12 +15,12 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: Deleted or changes visibility
|
||||
ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 95296f33d9163cd1171481386efd0a2351095c39
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/12/2022
|
||||
ms.locfileid: '147886796'
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: '148191354'
|
||||
---
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
|
||||
@@ -32,7 +32,7 @@ ms.locfileid: '147886796'
|
||||
|
||||
## 删除公共仓库
|
||||
|
||||
当您删除公共仓库时，将选择现有的公共复刻之一作为新的父仓库。 所有其他仓库均从这一新的父仓库复刻，并且后续的拉取请求都转到这一新的父仓库。
|
||||
当你删除公共仓库时，将选择现有的公共分支之一作为新的上游存储库。 所有其他存储库均从这一新的上游存储库创建分支，并且后续的拉取请求都转到这一新的上游存储库。
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -44,9 +44,9 @@ ms.locfileid: '147886796'
|
||||
|
||||
## 将公共仓库更改为私有仓库
|
||||
|
||||
如果将公共仓库设为私有，其公共复刻将拆分到新网络中。 与删除公共仓库一样，选择现有的公共分支之一作为新的父仓库，并且所有其他仓库都从这个新的父仓库中复刻。 后续的拉取请求都转到这一新的父仓库。
|
||||
如果将公共仓库设为私有，其公共复刻将拆分到新网络中。 与删除公共存储库一样，选择现有的公共分支之一作为新的上游存储库，并且所有其他存储库都从这个新的上游存储库中创建分支。 后续的拉取请求都转到这一新的上游存储库。
|
||||
|
||||
换句话说，即使将父仓库设为私有后，公共仓库的复刻也将在其各自的仓库网络中保持公开。 这样复刻所有者便可继续工作和协作，而不会中断。 如果公共分支没有通过这种方式移动到单独的网络中，则这些分支的所有者将需要获得适当的[访问权限](/articles/access-permissions-on-github)以从（现在私有的）父存储库中拉取更改并提交拉取请求 - 即使它们以前不需要这些权限。
|
||||
换句话说，即使将上游存储库设为专用后，公共存储库的分支也将在其各自的存储库网络中保持公开。 这样复刻所有者便可继续工作和协作，而不会中断。 如果公共分支没有通过这种方式移动到单独的网络中，这些分支的所有者将需要获得适当的[访问权限](/articles/access-permissions-on-github)以从（现在专用的）上游存储库中拉取更改并提交拉取请求 - 即使它们以前不需要这些权限。
|
||||
|
||||
{% ifversion ghes or ghae %} 如果公共存储库启用了匿名 Git 读取权限并且该存储库设为私有，则所有存储库的分支都将失去匿名 Git 读取权限并恢复为默认的禁用设置。 如果将复刻的仓库设为公共，则仓库管理员可以重新启用 Git 读取权限。 有关详细信息，请参阅“[为存储库启用匿名 Git 读取访问](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。
|
||||
{% endif %}
|
||||
@@ -57,7 +57,7 @@ ms.locfileid: '147886796'
|
||||
|
||||
## 将私有仓库更改为公共仓库
|
||||
|
||||
如果将私有仓库设为公共，则其每个私有复刻都将变为独立的私有仓库并且成为自己新仓库网络的父仓库。 私有复刻绝不会自动设为公共，因为它们可能包含不应公开显示的敏感提交。
|
||||
如果将专用存储库设为公共，则其每个专用分支都将变为独立的专用存储库并且成为自己新的存储库网络的上游存储库。 私有复刻绝不会自动设为公共，因为它们可能包含不应公开显示的敏感提交。
|
||||
|
||||
### 删除公共仓库
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 了解仓库之间的连接
|
||||
intro: 通过查看存储库的网络和分叉以及依赖于存储库的项目，您可以更好地了解存储库之间存在的连接。
|
||||
title: Understanding connections between repositories
|
||||
intro: Use the network graph and forks list to understand fork networks.
|
||||
product: '{% data reusables.gated-features.repository-insights %}'
|
||||
redirect_from:
|
||||
- /articles/viewing-a-repository-s-network
|
||||
@@ -22,59 +22,57 @@ versions:
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: Connections between repositories
|
||||
ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
|
||||
ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/12/2022
|
||||
ms.locfileid: '147060064'
|
||||
---
|
||||
## 查看仓库的网络
|
||||
|
||||
网络图显示整个仓库网络的分支历史记录，包括根仓库的分支和包含网络独有提交的复刻的分支。
|
||||
## Viewing a repository's network
|
||||
|
||||
|
||||
The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
提示：若要查看较旧的分支，请在图中单击并拖动。
|
||||
**Tip:** To see older branches, click and drag within the graph.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 访问网络图
|
||||
## Accessing the network graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. 在左侧边栏中，单击“网络”。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Network**.
|
||||
|
||||
|
||||
## 列出仓库的复刻
|
||||
## Listing the forks of a repository
|
||||
|
||||
成员图显示仓库的所有复刻。
|
||||
The Members graph displays all the forks of a repository.
|
||||
|
||||
复刻按仓库复刻者用户名的字母顺序列出。 您可以单击要重定向到用户 {% data variables.product.product_name %} 个人资料页面的用户名，或者单击要重定向到仓库特定复刻的复刻名称。
|
||||
Forks are listed alphabetically by the organization or username of the person who forked the repository. You can click on the organization or username to be redirected to the organization or user's {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
### 访问成员图
|
||||
### Accessing the Members graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. 在左侧边栏中，单击“分支”。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Forks**.
|
||||
|
||||
|
||||
## 查看仓库的依赖项
|
||||
## Viewing the dependencies of a repository
|
||||
|
||||
您可以使用依赖关系图来浏览仓库所依赖的代码。
|
||||
You can use the dependency graph to explore the code your repository depends on.
|
||||
|
||||
几乎所有软件都依赖于其他开发者开发和维护的代码，常常被称为供应链。 例如，实用程序、库和框架。 这些依赖项是代码不可分割的一部分，其中的任何错误或漏洞都可能影响您的代码。 审查和维护这些依赖项非常重要。
|
||||
Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.
|
||||
|
||||
依赖关系图提供了可视化和探索仓库依赖关系的好方法。 有关详细信息，请参阅“[关于依赖项关系图](/code-security/supply-chain-security/about-the-dependency-graph)”和“[探索存储库的依赖项](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)”。
|
||||
The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)."
|
||||
|
||||
您也可以设置仓库，以便在您的一个依赖项中发现安全漏洞时，{% data variables.product.company_short %} 会自动提醒您。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。
|
||||
You can also set up your repository so that {% data variables.product.company_short %} alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
|
||||
ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179734'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148190059'
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,6 @@ ms.locfileid: '148179734'
|
||||
|
||||
使用官方的 Octokit 库，或者使用任何适用的第三方库。
|
||||
|
||||
- Python → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- Ruby → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- .NET → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- JavaScript → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
@@ -131,6 +130,7 @@ ms.locfileid: '148179734'
|
||||
|**github-flask**|[github-flask（官方网站）](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|githubkit|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|octokit.py|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1,9 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
---
|
||||
ms.openlocfilehash: 484a4230527deebe6f4aeb24ceabdf95eb75b492
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: "148191328"
|
||||
---
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} 无法从企业外部创建分支存储库。 {% data variables.enterprise.prodname_managed_users_caps %} 可以将企业中组织所拥有的专用或内部存储库的分支创建到其用户帐户命名空间或企业拥有的其他组织，具体由企业策略规定。
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: eb538c8746bf9d5ec4cd0e422e50ccc032309812
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: "148191355"
|
||||
---
|
||||
分支是一个新存储库，与原“上游”存储库共享代码和可见性设置。 分支通常用于在向上游存储库提出想法或修改之前进行迭代，比如在开放源代码项目中，或当用户没有对上游存储库的写入权限时。
|
||||
Reference in New Issue
Block a user