Merge pull request #22528 from github/repo-sync

repo sync

Author: Octomerger

content/admin/overview/about-github-for-enterprises.md

@@ -17,7 +17,7 @@ topics:
 
 Developers can store and version control your source code in repositories, using issues and projects to plan and track their work. They can code in a cloud-hosted development environment, {% data variables.product.prodname_github_codespaces %}, then review each other's code changes with pull requests, using code security features to keep secrets and vulnerabilities out of your codebase. Finally, you can automate your build, test, and deployment pipeline with {% data variables.product.prodname_actions %} and host software packages with {% data variables.product.prodname_registry %}.
 
-When businesses adopt {% data variables.product.prodname_enterprise %}, their return on investment (ROI) is high. For example, their developers save 45 minutes per day, and onboarding and training time is reduced by 40%. For more information, see [The Total Economic Impact of {% data variables.product.prodname_enterprise %}](https://resources.github.com/downloads/TEI-of-GitHub-Enterprise.pdf).
+When businesses adopt {% data variables.product.prodname_enterprise %}, their return on investment (ROI) is high. For example, their developers save 45 minutes per day, and onboarding and training time is reduced by 40%. For more information, see [The Total Economic Impact of {% data variables.product.prodname_enterprise %}](https://resources.github.com/forrester/).
 
 To simplify administration for all the stages in the software development lifecycle, we provide a single point of visibility and management called an enterprise account. Enterprise accounts enable you to manage billing and settings, enforce policy, and audit the people with access to your enterprise's resources. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
 

translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md

@@ -271,3 +271,10 @@ jobs:
 From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
 
 ![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)

translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md

@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
 
 When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
 
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
 | Path without subdomain isolation  | Path with subdomain isolation   |
 | --- | --- |
-| `http(s)://HOSTNAME/assets/`      | `http(s)://assets.HOSTNAME/`      |
-| `http(s)://HOSTNAME/avatars/`     | `http(s)://avatars.HOSTNAME/`     |
-| `http(s)://HOSTNAME/codeload/`    | `http(s)://codeload.HOSTNAME/`    |
-| `http(s)://HOSTNAME/gist/`        | `http(s)://gist.HOSTNAME/`        |
-| `http(s)://HOSTNAME/media/`       | `http(s)://media.HOSTNAME/`       |
-| `http(s)://HOSTNAME/pages/`       | `http(s)://pages.HOSTNAME/`       |
-| `http(s)://HOSTNAME/raw/`         | `http(s)://raw.HOSTNAME/`         |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
 {%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/`  | `http(s)://viewscreen.HOSTNAME/`  |
-| `http(s)://HOSTNAME/notebooks/`   | `http(s)://notebooks.HOSTNAME/`   |
-{%- else %}
-| `http(s)://HOSTNAME/render/`      | `http(s)://render.HOSTNAME/`      |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
 {%- endif %}
-| `http(s)://HOSTNAME/reply/`       | `http(s)://reply.HOSTNAME/`       |
-| `http(s)://HOSTNAME/uploads/`     | `http(s)://uploads.HOSTNAME/`     | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
 
 ## Prerequisites
 

translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md

@@ -1,6 +1,6 @@
 ---
-title: Enabling GitHub Actions with MinIO storage
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO storage to store data generated by workflow runs.'
+title: Aktivieren von GitHub Actions mit dem MinIO-Speicher
+intro: 'Du kannst {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_server %} aktivieren und MinIO zum Speichern von Daten verwenden, die durch Workflowausführungen generiert wurden.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   ghes: '*'
@@ -14,36 +14,35 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
   - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage
 shortTitle: MinIO storage
+ms.openlocfilehash: 3d9c6cfca6b81a66185515c8757cef22290ead30
+ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148166569'
 ---
+## Voraussetzungen
 
-## Prerequisites
+Stelle vor dem Aktivieren von {% data variables.product.prodname_actions %} sicher, dass du die folgenden Schritte ausgeführt hast:
 
-Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
+* Erstelle deinen MinIO-Bucket zum Speichern von Daten, die von Workflowausführungen generiert werden. Weitere Informationen zum Installieren und Konfigurieren von MinIO findest du unter [MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html) (Hochleistungsobjektspeicher von MinIO) und [mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html) in der MinIO-Dokumentation.
 
-* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
+  Um Ressourcenkonflikte in der Appliance zu vermeiden, empfehlen wir, MinIO separat von {% data variables.location.product_location %} zu hosten.
 
-  To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
+  {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %}
 
-  {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
-{% data reusables.actions.enterprise-common-prereqs %}
+## Aktivieren von {% data variables.product.prodname_actions %} mit dem MinIO-Speicher
 
-## Enabling {% data variables.product.prodname_actions %} with MinIO storage
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
+1. Wähle unter "Artefakt- und Protokollspeicher" die Option **Amazon S3** aus, und gib die Details des Speicherbuckets ein:
 
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.actions %}
-{% data reusables.actions.enterprise-enable-checkbox %}
-1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
+   * **AWS-Service-URL**: Die URL für deinen MinIO-Service. Beispiel: `https://my-minio.example:9000`.
+   * **AWS S3 Bucket**: Der Name deines S3-Buckets.
+   * **AWS S3-Zugriffsschlüssel und Geheimer AWS S3****-Schlüssel**: `MINIO_ACCESS_KEY` und `MINIO_SECRET_KEY`, verwendet für deine MinIO-Instanz.
 
-   * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
-   * **AWS S3 Bucket**: The name of your S3 bucket.
-   * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
+   ![Optionsschaltfläche zum Auswählen von Amazon S3 Storage und der Felder für die MinIO-Konfiguration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png)
+1. Wähle unter "Artifact & Log Storage" (Artefakte & Protokoll Storage) die Option **Pfadformat erzwingen** aus.
 
-   ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png)
-1. Under "Artifact & Log Storage", select **Force path style**.
-
-   ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png)
-{% data reusables.enterprise_management_console.test-storage-button %}
-{% data reusables.enterprise_management_console.save-settings %}
+   ![Kontrollkästchen „Pfadformat erzwingen“](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.actions.enterprise-postinstall-nextsteps %}