diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md index 5255ee9629..2e9a44e2eb 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md @@ -16,6 +16,26 @@ type: tutorial {% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners).{% endif %} +### Default group for {% data variables.actions.hosted_runner %}s + +Organizations and enterprises with access to {% data variables.actions.hosted_runner %}s will automatically receive a default runner group called "Default Larger Runners" that includes 4 runners of varying sizes. The runners in this group are pre-configured and ready for immediate use. In order to use the runners in this group, you will need to add the label corresponding to the runner of your choice to your workflow file. See the table below for labels. For more information on how to use labels, see "[Running jobs on your runner](/actions/using-github-hosted-runners/using-larger-runners#running-jobs-on-your-runner)." + + +#### Default Runners + +|Description | Label | Image | +| ------- | ------- | ------ | +| 4-cores Ubuntu Runner | `ubuntu-latest-4-cores` | Ubuntu - Latest | +| 8-cores Ubuntu Runner | `ubuntu-latest-8-cores` | Ubuntu - Latest | +| 16-cores Ubuntu Runner | `ubuntu-latest-16-cores` | Ubuntu - Latest | +| 8-cores Windows Runner | `windows-latest-8-cores` | Windows Server - Latest | + +The default {% data variables.actions.hosted_runner %} group is created at the billing entity level. If your organization is part of an enterprise account, the group will be managed on the enterprise level. If your organization does not fall under an enterprise, the group is managed on the organization level. + +You will not be billed for these runners until you use them in your workflows. Once these runners are used, billing works as it normally does. For more information on billing, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners#understanding-billing)." + +The default access for a {% data variables.actions.hosted_runner %} group at the enterprise level is set to automatically share with all organizations in the enterprise, but not all repositories. Organization admins will need to share the default {% data variables.actions.hosted_runner %} group with each repository separately. For {% data variables.actions.hosted_runner %} groups at the organization level, the default access is set to automatically share the group with all repositories. For more information on how to change access policies, and where to view the default {% data variables.actions.hosted_runner %} group, see "[Changing the access policy of a runner group](#changing-the-access-policy-of-a-runner-group)." + {% ifversion ghec or ghes or ghae %} ## Creating a runner group for an organization diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md index e4492c0bb6..aeb477c475 100644 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md @@ -49,7 +49,7 @@ When you create a codespace, a number of steps happen to create and connect you For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)." -For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)." +For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)." If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md index 1f90ae0e98..842a20e971 100644 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md @@ -98,5 +98,5 @@ You can publish an unpublished codespace from the "Your codespaces" page on {% d ## Further reading - "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" -- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" +- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" - "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" \ No newline at end of file diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/index.md b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md index 3ae4748fc5..e2a9a379d0 100644 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/index.md +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md @@ -7,7 +7,6 @@ versions: topics: - Codespaces children: - - /the-codespace-lifecycle - /developing-in-a-codespace - /creating-a-codespace-for-a-repository - /creating-a-codespace-from-a-template diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index cc463fbc81..c9cdeb3891 100644 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -18,7 +18,7 @@ shortTitle: Open an existing codespace {% endjetbrains %} -You can reopen any of your active or stopped codespaces on {% data variables.product.prodname_dotcom_the_website %}, in a JetBrains IDE, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. For more information, see "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)." +You can reopen any of your active or stopped codespaces on {% data variables.product.prodname_dotcom_the_website %}, in a JetBrains IDE, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. For more information, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)." You can view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can: diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md index e7f3fd455e..6602cce6b4 100644 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md @@ -105,4 +105,4 @@ When you restart a codespace you can choose to open it in {% data variables.prod ## Further reading -- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" +- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md b/translations/de-DE/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md deleted file mode 100644 index c241e5f9e7..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Der Codespace-Lebenszyklus -intro: 'Du kannst in einer {% data variables.product.prodname_github_codespaces %}-Umgebung entwickeln und deine Daten während des gesamten Codespace-Lebenszyklus verwalten.' -versions: - fpt: '*' - ghec: '*' -type: overview -topics: - - Codespaces - - Developer -redirect_from: - - /codespaces/developing-in-codespaces/codespaces-lifecycle -ms.openlocfilehash: 660ced63e34c6de8025c65946542baca43534cfe -ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3 -ms.translationtype: HT -ms.contentlocale: de-DE -ms.lasthandoff: 11/22/2022 -ms.locfileid: '148180795' ---- -## Informationen zum Lebenszyklus eines Codespaces - -Der Lebenszyklus eines Codespaces beginnt beim Erstellen des Codespaces und endet, wenn du den Codespace löschst. Du kannst eine Verbindung mit einem aktiven Codespace trennen und erneut herstellen, ohne dass die ausgeführten Prozesse dadurch beeinträchtigt werden. Du kannst einen Codespace beenden und neu starten, ohne Änderungen zu verlieren, die du an deinem Projekt vorgenommen hast. - -## Einen Codespace erstellen - -Wenn du an einem Projekt arbeiten möchtest, kannst du einen neuen Codespace erstellen oder einen vorhandenen Codespace öffnen. Wenn du in {% data variables.product.prodname_github_codespaces %} entwickelst, kannst du einen neuen Codespace anhand eines Branches deines Repositorys erstellen oder einen Codespace mit langer Ausführungsdauer für ein Feature nutzen. {% data reusables.codespaces.starting-new-project-template %} Weitere Informationen findest du unter „[Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)“ und „[Erstellen eines Codespaces aus einer Vorlage](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)“. - -{% data reusables.codespaces.max-number-codespaces %} Wenn du die maximale Anzahl aktiver Codespaces erreichst und versuchst, andere zu starten, wirst du aufgefordert, einen deiner aktiven Codespaces zu beenden. - -Falls du jedes Mal, wenn du an einem Projekt arbeitest, einen neuen Codespace erstellst, solltest du deine Änderungen regelmäßig pushen, damit neue Commits auf {% data variables.product.prodname_dotcom %} verfügbar sind. Wenn du für dein Projekt einen Codespace mit langer Ausführungsdauer verwendest, solltest du Inhalte aus dem Standardbranch deines Repositorys pullen, sobald du mit der Arbeit in deinem Codespace beginnst. Auf diese Weise verfügt deine Umgebung über die aktuellen Commits. Dieser Workflow ist mit der Arbeit an einem Projekt auf deinem lokalen Computer vergleichbar. - -{% data reusables.codespaces.prebuilds-crossreference %} - -## Speichern von Änderungen in einem Codespace - -Wenn du über das Internet eine Verbindung mit einem Codespace herstellst, ist die Funktion für automatisches Speichern automatisch für den Web-Editor aktiviert und so konfiguriert, dass Änderungen nach einer bestimmten Verzögerung gespeichert werden. Wenn du über {% data variables.product.prodname_vscode %} auf deinem Desktop eine Verbindung mit einem Codespace herstellst, musst du die Funktion für automatisches Speichern aktivieren. Weitere Informationen findest du unter [Speichern/Automatisch Speichern](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in der {% data variables.product.prodname_vscode %}-Dokumentation. - -Deine Arbeit wird auf einem virtuellen Computer in der Cloud gespeichert. Du kannst einen Codespace schließen und beenden und später zur gespeicherten Arbeit zurückkehren. Wenn du über Änderungen verfügst, die noch nicht gespeichert wurden, fordert dein Editor dich zum Speichern auf, bevor du das Programm beendest. Wenn dein Codespace jedoch gelöscht wird, wird auch deine Arbeit gelöscht. Um deine Arbeit beizubehalten, musst du deine Änderungen committen und in dein Remoterepository pushen oder deine Arbeit in einem neuen Remoterepository veröffentlichen, wenn du deinen Codespace aus einer Vorlage erstellt hast. Weitere Informationen findest du unter [Verwenden der Quellcodeverwaltung in deinem Codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace). - -## Timeouts für {% data variables.product.prodname_github_codespaces %} - -Wenn ein Codespace ohne Interaktion ausgeführt wird oder du deinen Codespace beendest, ohne ihn explizit anzuhalten, tritt nach einer bestimmten Dauer an Inaktivität ein Timeout auf, und der Codespace wird beendet. Standardmäßig wird ein Codespace nach einer Inaktivitätsperiode von 30 Minuten mit einem Timeout beendet. Du kannst diesen Zeitraum bei Codespaces, die du neu erstellst, jedoch anpassen. Weitere Informationen zum Festlegen des Standard-Timeoutzeitraums für deine Codespaces findest du unter [Festlegen des Timeoutzeitraums für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces). Weitere Informationen zum Anhalten eines Codespaces findest du unter [Anhalten eines Codespaces](#stopping-a-codespace). - -Wenn ein Timeout für einen Codespace auftritt, werden deine Daten zum Zeitpunkt des letzten Speichervorgangs beibehalten. Weitere Informationen findest du unter [Speichern von Änderungen in einem Codespace](#saving-changes-in-a-codespace). - -## Neuerstellen eines Codespaces - -Du kannst deinen Codespace neu erstellen, um Änderungen an deiner Entwicklungscontainerkonfiguration zu implementieren. Für die meisten Anwendungsfälle ist das Erstellen eines neuen Codespaces eine Alternative zum Neuerstellen eines Codespaces. Wenn Du deinen Codespace neu erstellst, verwendet {% data variables.product.prodname_github_codespaces %} standardmäßig Images aus deinem Cache neu, um den Neuerstellungsprozess zu beschleunigen. Alternativ kannst du eine vollständige Neuerstellung durchführen, wodurch der Cache gelöscht und der Container mit neuen Images neu erstellt wird. - -Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace) und [Durchführen einer vollständigen Neuerstellung eines Containers](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container). - -## Beenden eines Codespaces - -{% data reusables.codespaces.stopping-a-codespace %} Weitere Informationen findest du unter „[Beenden und Starten eines Codespaces](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)“. - -## Einen Codespace löschen - -Du kannst einen Codespace für eine bestimmte Aufgabe erstellen und den Codespace sicher löschen, nachdem du deine Änderungen an einen Remotebranch gepusht hast. - -Wenn du versuchst, einen Codespace mit nicht gepushten Git-Commits zu löschen, wirst du in deinem Editor benachrichtigt, dass Änderungen vorliegen, die nicht an einen Remotebranch gepusht wurden. In diesem Fall kannst du alle gewünschten Änderungen pushen und deinen Codespace anschließend löschen, oder du löschst deinen Codespace mitsamt allen ausgecheckten Änderungen. Du kannst deinen Code auch in einen neuen Branch exportieren, ohne einen neuen Codespace zu erstellen. Weitere Informationen findest du unter [Exportieren von Änderungen in einen Branch](/codespaces/troubleshooting/exporting-changes-to-a-branch). - -Codespaces, die angehalten wurden und für einen bestimmten Zeitraum inaktiv bleiben, werden automatisch gelöscht. Standardmäßig werden inaktive Codespaces nach 30 Tagen gelöscht, du kannst allerdings den Aufbewahrungszeitraum für Codespaces anpassen. Weitere Informationen findest du unter [Konfigurieren des automatischen Löschens deiner Codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces). - -Wenn du einen Codespace erstellst, fallen weiterhin Speichergebühren an, bis er gelöscht wird, unabhängig davon, ob er aktiv oder beendet ist. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage). Das Löschen eines Codespaces verringert nicht den aktuellen abrechenbaren Betrag für {% data variables.product.prodname_github_codespaces %}, der während jedes monatlichen Abrechnungszyklus akkumuliert wird. Weitere Informationen findest du unter „[Anzeigen der {% data variables.product.prodname_github_codespaces %}-Nutzung](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)“. - -Weitere Informationen zum Löschen eines Codespaces findest du unter [Löschen eines Codespaces](/codespaces/developing-in-codespaces/deleting-a-codespace). - -## Unterbrechung der Verbindung bei Verwendung von {% data variables.product.prodname_github_codespaces %} - -{% data variables.product.prodname_github_codespaces %} ist eine cloudbasierte Entwicklungsumgebung, für die eine Internetverbindung erforderlich ist. Wenn die Internetverbindung unterbrochen wird, während du in einem Codespace arbeitest, kannst du nicht auf deinen Codespace zugreifen. Alle ausgecheckten Änderungen werden jedoch gespeichert. Sobald die Internetverbindung wiederhergestellt ist, kannst du dich erneut mit deinem Codespace verbinden. Der Codespace weist in diesem Fall den exakt selben Zustand auf wie vor der Verbindungsunterbrechung. Wenn deine Internetverbindung instabil ist, solltest du deine Änderungen häufig committen und pushen. - -Wenn du weißt, dass du häufig offline arbeiten wirst, kannst du deine `devcontainer.json`-Datei mit der Erweiterung [„Dev Containers“](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) für {% data variables.product.prodname_vscode_shortname %} verwenden, um einen lokalen Entwicklungscontainer für dein Repository zu erstellen und anzufügen. Weitere Informationen findest du unter [Entwickeln innerhalb eines Containers](https://code.visualstudio.com/docs/remote/containers) in der {% data variables.product.prodname_vscode %}-Dokumentation. diff --git a/translations/de-DE/content/codespaces/getting-started/index.md b/translations/de-DE/content/codespaces/getting-started/index.md index 0773c5fa05..6d1e57d0b3 100644 --- a/translations/de-DE/content/codespaces/getting-started/index.md +++ b/translations/de-DE/content/codespaces/getting-started/index.md @@ -7,6 +7,7 @@ versions: ghec: '*' children: - /quickstart + - /the-codespace-lifecycle - /deep-dive ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 diff --git a/translations/de-DE/content/codespaces/index.md b/translations/de-DE/content/codespaces/index.md index fb62a3b338..6313c30ef8 100644 --- a/translations/de-DE/content/codespaces/index.md +++ b/translations/de-DE/content/codespaces/index.md @@ -8,7 +8,7 @@ introLinks: featuredLinks: guides: - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization - - /codespaces/developing-in-codespaces/the-codespace-lifecycle + - /codespaces/getting-started/the-codespace-lifecycle - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - /codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces - /billing/managing-billing-for-github-codespaces/about-billing-for-codespaces diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md deleted file mode 100644 index 269175e728..0000000000 --- a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Remote-URL auf GitHub Desktop ändern -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 -versions: - fpt: '*' -shortTitle: Change a remote's URL -ms.openlocfilehash: e06ea68ead9ab79c44d7aaf96f48d6645232b496 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: de-DE -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146058476' ---- -{% mac %} - -{% data reusables.desktop.mac-repository-settings-menu %} -2. Klicke auf **Remote**, und gib unter **Primäres Remoterepository** die gewünschte URL ein. -![Feld „Primäres Remoterepository“](/assets/images/help/desktop/repository-settings-remote.png) {% 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. -![Feld „Primäres Remoterepository“](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} - -{% endwindows %} diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 69643e55bf..1032130e6f 100644 --- a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -10,7 +10,7 @@ children: - /viewing-a-pull-request-in-github-desktop - /viewing-and-re-running-checks-in-github-desktop - /configuring-notifications-in-github-desktop - - /changing-a-remotes-url-from-github-desktop + - /changing-the-remote-url-for-a-repository-from-github-desktop shortTitle: Work with your remote repo ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md deleted file mode 100644 index 11fff5cf94..0000000000 --- a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Ein Remote-Repository für einen Fork konfigurieren -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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Pull requests -shortTitle: Configure a remote -ms.openlocfilehash: d474b56a9b1881d9511ccf9e239bb54e26967784 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: de-DE -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145133853' ---- -{% 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) - ``` diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md index f51d2b19ec..2bf21ec5f6 100644 --- a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md +++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md @@ -14,7 +14,7 @@ topics: - Pull requests children: - /about-forks - - /configuring-a-remote-for-a-fork + - /configuring-a-remote-repository-for-a-fork - /syncing-a-fork - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index d97744b5d7..c9b479247e 100644 --- a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -52,7 +52,7 @@ If the changes from the upstream repository cause conflict then the {% data vari ## Syncing a fork branch from the command line -Before you can sync your fork with an upstream repository, you must [configure a remote that points to the upstream repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) in Git. +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)." {% data reusables.command_line.open_the_multi_os_terminal %} 2. Change the current working directory to your local project. diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index dc70e74cfa..da2f113682 100644 --- a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -14,12 +14,12 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: 3b6822be6551d43b3af55220ac8f39deec8be1df -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: 12265f0627ca6d0feb34244aab1c021b5ae6cc10 +ms.sourcegitcommit: 9315c7dae9a673a2f8958df7632bf1af206a0bed ms.translationtype: HT ms.contentlocale: de-DE -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148106837' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188238' --- Personen mit Administrator- oder Inhaberberechtigungen können eine CODEOWNERS-Datei in einem Repository einrichten. @@ -85,7 +85,7 @@ Bei CODEOWNERS-Pfaden wird die Groß- und Kleinschreibung berücksichtigt, da {% # precedence. When someone opens a pull request that only # modifies JS files, only @js-owner and not the global # owner(s) will be requested for a review. -*.js @js-owner +*.js @js-owner #This is an inline comment. # You can also use email addresses if you prefer. They'll be # used to look up users just like we do for commit author @@ -131,7 +131,7 @@ apps/ @octocat ## CODEOWNERS und Branchschutz Repositorybesitzer können Branchschutzregeln hinzufügen, um sicherzustellen, dass geänderter Code von den Besitzer*innen der geänderten Dateien überprüft wird. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches). -## Weitere Informationsquellen +## Weiterführende Themen - [Erstellen neuer Dateien](/articles/creating-new-files) - [Einladen von Projektmitarbeiter*innen in ein persönliches Repository](/articles/inviting-collaborators-to-a-personal-repository) diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/0.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/0.yml index 8f3df3ef18..c98d49681b 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/0.yml @@ -258,6 +258,8 @@ sections: - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 notes: diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/1.yml index c1e26d10e7..f6ec01151d 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/1.yml @@ -55,6 +55,8 @@ sections: - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 notes: diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/2.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/2.yml index a6e465aae2..c69db675ae 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/2.yml @@ -31,6 +31,8 @@ sections: After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 notes: diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/3.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/3.yml index a15e8170ba..ff8016bc42 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/3.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/3.yml @@ -37,4 +37,6 @@ sections: - | After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4 releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] \ No newline at end of file diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/4.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/4.yml index ebf7d67692..baed742dfc 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/4.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/4.yml @@ -28,4 +28,6 @@ sections: - | After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] \ No newline at end of file diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/5.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/5.yml index f72408ff77..6b426fb007 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/5.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/5.yml @@ -27,4 +27,6 @@ sections: - | After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] \ No newline at end of file diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/6.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/6.yml index c1f8fa7628..bcdc224489 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/6.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/6.yml @@ -32,3 +32,5 @@ sections: After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] \ No newline at end of file diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/7.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/7.yml index 080d90353b..917dd84bfa 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/7.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/7.yml @@ -24,3 +24,5 @@ sections: After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] \ No newline at end of file diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/8.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/8.yml index 6353897f97..b56183ab9c 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-4/8.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/8.yml @@ -24,3 +24,5 @@ sections: After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] \ No newline at end of file diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml b/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml index b5a846e1c3..028b8750b6 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml @@ -27,4 +27,6 @@ sections: - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - Actions services need to be restarted after restoring an appliance from a backup taken on a different host. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' + - | + GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28] \ No newline at end of file diff --git a/translations/log/msft-de-resets.csv b/translations/log/msft-de-resets.csv index 9e2d592f28..c156fea21b 100644 --- a/translations/log/msft-de-resets.csv +++ b/translations/log/msft-de-resets.csv @@ -103,6 +103,7 @@ translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-ti translations/de-DE/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,file deleted because it no longer exists in main translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md,file deleted because it no longer exists in main translations/de-DE/content/codespaces/developing-in-codespaces/renaming-a-codespace.md,file deleted because it no longer exists in main +translations/de-DE/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md,file deleted because it no longer exists in main translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md,file deleted because it no longer exists in main translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,file deleted because it no longer exists in main translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,file deleted because it no longer exists in main @@ -120,6 +121,7 @@ translations/de-DE/content/codespaces/troubleshooting/troubleshooting-port-forwa translations/de-DE/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md,file deleted because it no longer exists in main translations/de-DE/content/codespaces/troubleshooting/working-with-support-for-codespaces.md,file deleted because it no longer exists in main translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md,file deleted because it no longer exists in main +translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md,file deleted because it no longer exists in main translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,file deleted because it no longer exists in main translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md,file deleted because it no longer exists in main translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md,file deleted because it no longer exists in main @@ -183,6 +185,7 @@ translations/de-DE/content/organizations/restricting-access-to-your-organization translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,file deleted because it no longer exists in main translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/index.md,file deleted because it no longer exists in main translations/de-DE/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,file deleted because it no longer exists in main +translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md,file deleted because it no longer exists in main translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md,file deleted because it no longer exists in main translations/de-DE/content/rest/reference/actions.md,file deleted because it no longer exists in main translations/de-DE/content/rest/reference/activity.md,file deleted because it no longer exists in main @@ -1007,7 +1010,7 @@ translations/de-DE/content/repositories/managing-your-repositorys-settings-and-f translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md,rendering error -translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,broken liquid tags +translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error translations/de-DE/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error translations/de-DE/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error