repo sync

translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md

@@ -42,8 +42,11 @@ After you configure {% data variables.location.product_location %} to use {% dat
 
 Any VM that you use for {% data variables.product.prodname_dependabot %} runners must meet the requirements for self-hosted runners. In addition, they must meet the following requirements.
 
-- Linux operating system{% ifversion ghes < 3.5 %}
-- Git installed{% endif %}
+- Linux operating system
+- x64 architecture
+{%- ifversion ghes < 3.5 %}
+- Git installed
+{%- endif %}
 - Docker installed with access for the runner users:
   - We recommend installing Docker in rootless mode and configuring the runners to access Docker without `root` privileges.
   - Alternatively, install Docker and give the runner users raised privileges to run Docker.

translations/de-DE/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md

@@ -50,6 +50,8 @@ You can enable a related feature, {% data variables.product.prodname_dependabot_
 
 {% data reusables.dependabot.dependabot-updates-and-actions %}
 
+{% data reusables.dependabot.dependabot-actions-support %}
+
 ## About pull requests for security updates
 
 Each pull request contains everything you need to quickly and safely review and merge a proposed fix into your project. This includes information about the vulnerability like release notes, changelog entries, and commit details. Details of which vulnerability a pull request resolves are hidden from anyone who does not have access to {% data variables.product.prodname_dependabot_alerts %} for the repository.

translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md

@@ -841,6 +841,27 @@ registries:
 ```
 {% endraw %}
 
+{% ifversion dependabot-hex-self-hosted-support %}
+### `hex-repository`
+
+The `hex-repository` type supports an authentication key.
+
+`repo` is a required field, which must match the name of the repository used in your dependency declaration.
+
+The `public-key-fingerprint` is an optional configuration field, representing the fingerprint of the public key for the Hex repository. `public-key-fingerprint` is used by Hex to establish trust with the private repository. The `public-key-fingerprint` field can be either listed in plaintext or stored as a {% data variables.product.prodname_dependabot %} secret.
+
+{% raw %}
+```yaml
+registries:
+   github-hex-repository:
+     type: hex-repository
+     repo: private-repo
+     url: https://private-repo.example.com
+     auth-key: ${{secrets.MY_AUTH_KEY}}
+     public-key-fingerprint: ${{secrets.MY_PUBLIC_KEY_FINGERPRINT}}
+```
+{% endraw %}{% endif %}
+
 ### `maven-repository`
 
 The `maven-repository` type supports username and password.

translations/de-DE/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md

@@ -30,6 +30,8 @@ If a contributor bypasses a push protection block for a secret, {% data variable
 - adds the bypass event to the audit log.{% ifversion secret-scanning-push-protection-email %}
 - sends an email alert to organization owners, security managers, and repository administrators, with a link to the related secret and the reason why it was allowed.{% endif %}
 
+{% data reusables.secret-scanning.bypass-reasons-and-alerts %}
+
 For information on the secrets and service providers supported for push protection, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-push-protection)."
 
 ## Enabling {% data variables.product.prodname_secret_scanning %} as a push protection

translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md

@@ -46,15 +46,15 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
 4. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow , no `CNAME` file is created. For more information about your publishing source, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
-![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png)
-
-{% note %}
-
-**Note:** If your custom domain is an internationalized domain name, you must enter the Punycode encoded version.
-
-For more information on Punycodes, see [Internationalized domain name](https://en.wikipedia.org/wiki/Internationalized_domain_name).
-
-{% endnote %}
+  ![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png)
+
+  {% note %}
+  
+  **Note:** If your custom domain is an internationalized domain name, you must enter the Punycode encoded version.
+  
+  For more information on Punycodes, see [Internationalized domain name](https://en.wikipedia.org/wiki/Internationalized_domain_name).
+  
+  {% endnote %}
 
 5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `<user>.github.io`. If you want to use the subdomain `another.example.com` for your organization site, create a `CNAME` record that points `another.example.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 

translations/de-DE/content/rest/actions/oidc.md

@@ -6,6 +6,7 @@ intro: 'Die {% data variables.product.prodname_actions %} OIDC-API ermöglicht d
 topics:
   - API
 versions:
+  fpt: '*'
   ghec: '*'
   ghes: '>=3.7'
 ms.openlocfilehash: 6857081d29bd89e59c4f6c7ff458fd0afc2cf6ef

translations/de-DE/content/rest/gitignore.md

@@ -21,6 +21,6 @@ When you create a new repository on {% ifversion ghae %}{% data variables.produc
 
 You can use this custom media type when getting a gitignore template.
 
-    application/vnd.github.VERSION.raw
+    application/vnd.github.raw
 
 For more information, see "[Media types](/rest/overview/media-types)."

translations/de-DE/content/rest/pulls/comments.md

@@ -1,5 +1,5 @@
 ---
-title: Pull-Request-Review-Kommentare
+title: Pull request review comments
 shortTitle: Review comments
 intro: ''
 versions:
@@ -11,24 +11,10 @@ topics:
   - API
 miniTocMaxHeadingLevel: 3
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 6d49aa3d5bca7f74a21c1cce32cecd38abe9366d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: de-DE
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147067730'
 ---
-## Informationen zur API für Pull Request-Review-Kommentare
 
-Pull Request-Review-Kommentare sind Kommentare zu einem Teil des vereinheitlichten Formats, der während einer Pull Request-Review vorgenommen wurde. Commit- und Issue-Kommentare unterscheiden sich von Pull Request-Review-Kommentaren. Du wendest Commit-Kommentare direkt auf einen Commit an und du wendest Issue-Kommentare an, ohne auf einen Teil des vereinheitlichten Formats zu verweisen. Weitere Informationen findest du unter [Erstellen eines Commit-Kommentars](/rest/reference/commits#create-a-commit-comment) und [Erstellen eines Issue-Kommentars](/rest/reference/issues#create-an-issue-comment).
+## About the Pull request review comments API
 
-### Benutzerdefinierte Medientypen für Pull Request-Review-Kommentare
+Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
 
-Dies sind die unterstützten Medientypen für Pull Request-Review-Kommentare.
-
-    application/vnd.github.VERSION.raw+json
-    application/vnd.github.VERSION.text+json
-    application/vnd.github.VERSION.html+json
-    application/vnd.github.VERSION.full+json
-
-Weitere Informationen findest du unter [Benutzerdefinierte Medientypen](/rest/overview/media-types).
+{% data reusables.pull_requests.issues-media-types %}

translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md

@@ -64,6 +64,8 @@ Dynatrace | Dynatrace Internal Token | dynatrace_internal_token
 EasyPost | EasyPost Production API Key | easypost_production_api_key
 EasyPost | EasyPost Test API Key | easypost_test_api_key
 Fastly | Fastly API Token | fastly_api_token
+{%- ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
+Figma | Figma {% data variables.product.pat_generic_title_case %} | figma_pat{% endif %}
 Finicity | Finicity App Key | finicity_app_key
 Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key
 Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key
@@ -91,7 +93,12 @@ Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
 Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id </br>google_oauth_client_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
 Grafana | Grafana API Key | grafana_api_key
+Grafana | Grafana Cloud API Key | grafana_cloud_api_key
+Grafana | Grafana Cloud API Token | grafana_cloud_api_token
+Grafana | Grafana Project API Key | grafana_project_api_key
+Grafana | Grafana Project Service Account Token | grafana_project_service_account_token{% endif %}
 HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token
 HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token
 {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
@@ -198,6 +205,8 @@ Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret
 Supabase | Supabase Service Key | supabase_service_key{% endif %}
 Tableau | Tableau {% data variables.product.pat_generic_title_case %} | tableau_personal_access_token
 Telegram | Telegram Bot Token | telegram_bot_token
+{%- ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
+Telnyx | Telnyx API V2 Key | telnyx_api_v2_key{% endif %}
 Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Twilio | Twilio Access Token | twilio_access_token{% endif %}