Crowdin translations (translation-batch-1612885307) (github#17760)

* New Crowdin translations by Github Action * Revert broken translated files to content from branch * fix known frontmatter errors * Revert broken translated files to content from branch * fix translation errors Co-authored-by: Crowdin Bot <[email protected]> Co-authored-by: Jason Etcovitch <[email protected]>
Oleksandr00 · Feb 9, 2021 · 5d608c1 · 5d608c1
1 parent a469193
commit 5d608c1
Show file tree

Hide file tree

Showing 837 changed files with 5,896 additions and 3,147 deletions.
diff --git a/...ons/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/...ons/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
 {% data reusables.github-actions.usage-api-requests %}
 - **Auftrags-Matrix** - {% data reusables.github-actions.usage-matrix-limits %}
 
-### Unterstützte Betriebssysteme für selbst-gehostete Runner
+### Supported architectures and operating systems for self-hosted runners
 
 The following operating systems are supported for the self-hosted runner application.
 
@@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica
 
 - macOS 10.13 (High Sierra) oder höher
 
+#### Architectures
+
+The following processor architectures are supported for the self-hosted runner application.
+
+- `x64` - Linux, macOS, Windows.
+- `ARM64` - Linux only.
+- `ARM32` - Linux only.
+
 {% if enterpriseServerVersions contains currentVersion %}
 
 ### Kommunikation zwischen selbst-gehosteten Runnern und {% data variables.product.prodname_dotcom %}

diff --git a/...ent/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/...ent/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -29,7 +29,7 @@ Ein selbst-gehosteter Runner erhält automatisch bestimmte Labels, wenn er zu {%
 
 * `self-hosted`: Standard-Label, welches allen selbst-gehosteten Runnern zugeteilt wird.
 * `Linux`, `windows`, oder `macOS`: Je nach Betriebssystem zugeteilt.
-* `x86`, `x64`, `ARM`oder `ARM64`: Je nach Hardware-Architektur zugeteilt.
+* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
 
 Du kannst die YAML Deines Workflows verwenden, um Jobs an eine Kombination dieser Labels zu senden. In diesem Beispiel ist ein selbst-gehosteter Runner, der allen drei Labels entspricht, berechtigt, den Job auszuführen:
 

diff --git a/...ons/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md b/...ons/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md
diff --git a/...-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/...-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md
@@ -73,7 +73,7 @@ If the server on which you are running
 {% endif %}
 
 #### Enabling code scanning for individual repositories
-After you configure a self-hosted runner, {% if currentVersion == "[email protected]" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file.
+After you configure a self-hosted runner, {% if currentVersion == "[email protected]" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
 
 ### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}
 If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}.

diff --git a/.../content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/.../content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -20,7 +20,7 @@ For encryption in transit, {% data variables.product.product_name %} uses Transp
 
 The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages.
 
-To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and delete your encryption key. Note that deleting your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
+To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
 
 ### Adding or updating an encryption key
 
@@ -48,24 +48,24 @@ Your 2048 bit RSA private key should be in PEM format, for example in a file cal
    curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
    ```
 
-### Deleting your encryption key
+### Disabling your encryption key
 
-To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key.
+To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled.
 
-To unfreeze your enterprise after you've deleted your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
-
-1. To delete your key and disable encryption at rest, use the `DELETE /enterprise/encryption` endpoint.
+1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently.
 
    ```shell
    curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
    ```
 
-2. Optionally, check the status of the delete operation.
+2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest.
 
    ```shell
    curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
    ```
 
+To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
+
 ### Weiterführende Informationen
 
 - "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation 
diff --git a/...de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/...de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -29,6 +29,26 @@ versions:
 
   {% endnote %}
 
+{% if currentVersion ver_gt "[email protected]" and currentVersion ver_lt "[email protected]" %}
+
+### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
+
+Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/[email protected]/admin/release-notes).
+
+Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
+
+| Benutzerlizenzen                                           |                           vCPUs |                         Arbeitsspeicher |                        Attached-Storage | Root-Storage |
+|:---------------------------------------------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
+| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ |       200 GB |
+| 10–3000                                                    |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ |       200 GB |
+| 3000–5000                                                  |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB |       200 GB |
+| 5000–8000                                                  | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB |       200 GB |
+| 8000–10000+                                                | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB |       200 GB |
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
+
 ### Snapshot erstellen
 
 Ein Snapshot ist ein Checkpoint einer virtuellen Maschine (VM) zu einem bestimmten Zeitpunkt. Es wird dringend empfohlen, ein Snapshot zu erstellen, bevor Sie Ihre virtuelle Maschine upgraden, damit Sie bei einem Fehlschlagen eines Upgrades Ihre VM auf den Snapshot zurücksetzen können. Wenn Sie ein Upgrade auf eine neue Feature-Veröffentlichung durchführen, müssen Sie einen VM-Snapshot erstellen. Wenn Sie ein Upgrade auf eine Patch-Veröffentlichung durchführen, können Sie die vorhandene Daten-Disk anhängen.

diff --git a/...hub-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/...hub-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -9,26 +9,42 @@ versions:
   enterprise-server: '>=2.22'
 ---
 
-{% if currentVersion == "[email protected]" %}
-{% note %}
-
-**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/).
-
-{% endnote %}
-{% endif %}
+{% data reusables.actions.enterprise-beta %}
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% if currentVersion ver_gt "[email protected]" %}
 
 This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies.
 
+{% endif %}
+
 ### Review hardware considerations
 
-{% data reusables.actions.enterprise-hardware-considerations %}
+{% if currentVersion == "[email protected]" or currentVersion == "[email protected]" %}
+
+{% note %}
+
+**Note**: {% if currentVersion == "[email protected]" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. Weitere Informationen finden Sie unter „[Upgrade von {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)“.
+
+{% endnote %}
 
 {% endif %}
 
+{% data reusables.actions.enterprise-hardware-considerations %}
+
+For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform.
+
+- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
+- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
+- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
+- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
+- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
+- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
+- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations)
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
 ### External storage requirements
 
 To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage.
@@ -55,7 +71,7 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro
 
 ### Enabling {% data variables.product.prodname_actions %}
 
-{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. [Sign up for the beta](https://resources.github.com/beta-signup/).
+{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/[email protected]/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)."
 
 ### Weiterführende Informationen
 

diff --git a/...ng-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/...ng-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md
@@ -8,40 +8,40 @@ versions:
   free-pro-team: '*'
 ---
 
-### Repositorys klonen
-Repositorys auf {% data variables.product.prodname_dotcom %} existieren als Remote-Repositorys.  Du kannst öffentliche Repositorys klonen, die anderen Personen gehören. Du kannst Dein Repository klonen, um eine lokale Kopie auf Deinem Computer zu erstellen, und die beiden Speicherorte synchronisieren.
+### About local repositories
+Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer.
+
+You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. For more information, see "[Syncing your branch](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)."
+
+When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. Weitere Informationen findest Du unter „[Informationen zu Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)“.
+
+When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)".
 
 Darüber hinaus kannst Du ein Repository direkt über {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} klonen. Weitere Informationen findest Du unter „[Ein Repository von {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_desktop %} klonen](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)“.
 
-{% mac %}
+### Ein Repository klonen
 
 {% data reusables.desktop.choose-clone-repository %}
-  ![Menüoption zum Klonen in der Mac-App](/assets/images/help/desktop/clone-file-menu-mac.png)
 {% data reusables.desktop.cloning-location-tab %}
-  ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-mac.png)
 {% data reusables.desktop.cloning-repository-list %}
-  ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-mac.png)
-4. Klicke auf **Choose...** (Auswählen), und navigiere mithilfe des Finder-Fensters zu einem lokalen Pfad, wo Du das Repository klonen möchtest. ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-mac.png)
-5. Klicke auf **Clone** (Klonen). ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-mac.png)
-
-{% endmac %}
+{% data reusables.desktop.choose-local-path %}
+{% data reusables.desktop.click-clone %}
 
-{% windows %}
+### Repository forken
+If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork.
 
 {% data reusables.desktop.choose-clone-repository %}
-  ![Menüoption zum Klonen in der Windows-App](/assets/images/help/desktop/clone-file-menu-windows.png)
 {% data reusables.desktop.cloning-location-tab %}
-  ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-win.png)
 {% data reusables.desktop.cloning-repository-list %}
-  ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-win.png)
-4. Klicke auf **Choose...** (Auswählen), und navigiere mithilfe des Windows-Explorers zu einem lokalen Pfad, wohin Du das Repository klonen möchtest. ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-win.png)
-5. Klicke auf **Clone** (Klonen). ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-win.png)
+{% data reusables.desktop.choose-local-path %}
+{% data reusables.desktop.click-clone %}
+{% data reusables.desktop.fork-type-prompt %}
 
-{% endwindows %}
+### Managing fork behavior
+You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}.
 
-### Repositorys per Fork kopieren
-Um zu einem Projekt beizutragen, in dem Du keinen Schreibzugriff hast, kannst Du mit {% data variables.product.prodname_desktop %} das Repository per Fork kopieren. Änderungen an Deinem Fork wirken sich nicht auf das ursprüngliche Repository aus. Du kannst per Commit Änderungen in deinen Fork übernehmen und dann in dem ursprünglichen Repository einen Pull-Request mit deinen vorgeschlagenen Änderungen öffnen. Weitere Informationen findest Du unter „[Informationen zu Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)“.
+{% data reusables.desktop.open-repository-settings %}
+{% data reusables.desktop.select-fork-behavior %}
 
-1. Wenn Du ein Repository geklont hast, in dem Du keinen Schreibzugriff hast, und dann versuchst, Änderungen per Commit zu übertragen, warnt {% data variables.product.prodname_desktop %}: „‚You don't have write access to **REPOSITORY**‘ (Du hast keinen Schreibzugriff auf **REPOSITORY**. ‚Click **create a fork**‘ (Klicke **Fork erstellen**).“ ![Einen Fork-Link erstellen](/assets/images/help/desktop/create-a-fork.png)
-3. Klicke „**Fork this repository“ (Dieses Repository per Fork kopieren)**. ![Schaltfläche, um dieses Repo per Fork kopieren](/assets/images/help/desktop/fork-this-repo-button.png)
-4. Um Deinen Fork auf {% data variables.product.prodname_dotcom %} zu sehen, klickst Du in der oberen rechten Ecke von {% data variables.product.prodname_dotcom %} auf Dein Profilbild und dann auf „**Your Repositories“ (Deine Repositorys)**. ![Link zu Deinen Repositorys](/assets/images/help/profile/your-repositories.png)
+### Weiterführende Informationen
+- [Informationen zu Remote-Repositorys](/github/using-git/about-remote-repositories)